• 

  Logo

Bridging Borders in Web3.0

Why

Getting TestNet tokens can often be difficult for developers. Building great projects shouldn't come with the extra headache of trying to acquire TestNet tokens so we wanted to change that to make life just a little easier for developers.

Our project journey began with a diverse team spanning the USA, Nigeria, and Pakistan, fueled by a shared passion for exploring the possibilities of Web3.0 technologies. As a collective, our motivation was to not only apply our theoretical knowledge in a real-world setting but also to learn, collaborate, and stretch the limits of our skills.

Bridging Gaps

Inspiration:

The inspiration came from the excitement of applying our skills globally. Building a tool that benefits developers around the world came as an exciting challenge. Connecting with professionals from different corners of the world through asynchronous collaboration offered a unique opportunity to blend programming, design, and management skills. Each team member, regardless of their background, found motivation in the prospect of contributing to a project that transcended geographical boundaries and had the potential to be something useful for the world.

Learning:

As the project unfolded, our learning experiences were as diverse as our team. From seasoned developers to a UI/UX designer, and a beginner navigating the web3.0 world, each of us gained valuable insights. The project became a learning ground for programming, system design, project management, and the intricacies of web3.0, NFTs, DEX, and smart contracts. The journey itself became an educational odyssey. We each leaned on each other for support and made it a point to collaboratively use our strengths. The teamwork that was required to build this can't stressed enough.

The Work

Building:

Leveraging our collective expertise, we embarked on the project, utilizing programming languages, system design principles, and agile methodologies. The virtual collaboration platform, Discord, facilitated seamless communication despite the physical distances. As a team, we blended our skills, transcending borders and time zones to create a cohesive project. It definitely was a collaborative effort that required each team member to put forth their unique skillsets to bring this project home.

Challenges:

Our journey was not without challenges. Adapting to asynchronous collaboration, managing different time zones, and navigating the uncharted territories of web3.0 and Chainlink posed initial hurdles. The need for flexibility and effective communication became evident, pushing us to refine our project management strategies. As a team, we faced and embraced challenges, ultimately turning them into opportunities for growth. The initial goal was to build a bridge between TestNet's and MainNets using CCIP but had to shift gears to forming a TestNet to TestNet bridge. This shift halfway through the project led to some difficulties as well as team member changes but we were able to persist and complete the project.

Availability of testnet tokens and the cost to use CCIP with testnet tokens made this project particularly challenging, burning through 6 Matic in a single test when the faucet drips out a fraction of that, facing similar issues with Avax.

In the end, our project story is a testament to the power of collaboration, adaptability, and continuous learning in the ever-evolving landscape of Web3.0. The diverse perspectives of our team, originating from the USA, Nigeria, and Pakistan, contributed to a project that not only bridged geographical borders but also explored the frontiers of technology and knowledge.

Built With

• avalanche
• ccip
• css
• go
• html
• next.js
• polygon
• solidity
• tailwindcss
• typescript