BCNS - BaseChain Name Service
A decentralized, human-readable name service for the Base blockchain that simplifies wallet interactions.
Demo
About
Why are you participating for Based LatAm? We are participating in this hackathon to contribute to the growth of decentralized technology in the LatAm region. Blockchain adoption is rapidly growing, and we believe that user-friendly services like BCNS can make blockchain technology more accessible to communities in LatAm. Our connection to the region is rooted in the understanding of how important financial inclusion and simplifying technology are for broad adoption in underbanked areas.
How it's made
What challenges are you focusing on? We are addressing the challenge of usability in blockchain interactions. Wallet addresses are long, complex, and difficult to remember, which makes blockchain less approachable to everyday users. This issue can hinder adoption in emerging markets like LatAm, where ease of use is crucial for onboarding new users. How does your submission address this challenge? BCNS solves the usability problem by providing a decentralized name service for Base blockchain users, allowing them to register simple, human-readable names like alice.base instead of using complex wallet addresses. This simplifies interactions on the blockchain, making it easier to send/receive funds, interact with dApps, and engage in decentralized finance (DeFi). By reducing the barrier of technical complexity, BCNS can boost blockchain adoption in LatAm. Challenges we ran into One technical hurdle we encountered was integrating the frontend with the Base blockchain smart contract using Web3. Initially, there were issues with resolving names and registering them due to inconsistencies between the frontend and the smart contract's event handling. We overcame this by debugging the event logs, ensuring the contract emits the correct events and that our frontend listens for these events in real-time. We also faced challenges with gas fee optimization during name registration, but adjusting the contract’s logic to batch operations helped mitigate this.