Track
We are applying to Track 4 Bridges among Multi-chains
Technical Detail
A detailed technical explanation is in Github public repo README.
Inspiration
We are trying to build the most secure and permissionless cross-chain NFT bridge supported by Connext. We are a very active team and have a good community in the cross-chain space.
We did not have multi-chain storage before, so only simple token URI transfer was supported. For this hackathon, we decided to implement multi-chain storage on IPFS for this hackathon for bringing better data flexibility to NFTHashi.
Also, we want to get better feedback and support in this hackathon.
What it does
We added the IPFS metadata uploading function and add-on logic for content verification for the cross-chain messaging relayer.
For this update, we modified a lot of smart contracts, frontend, and backend.
How we built it
We use NFT storage to access IPFS and use Connext cross-chain messaging.
Challenges we ran into
- It was difficult to add IPFS content verification logic in the relayer, because we need to prevent sending wrong or malicious token metadata when bridging.
- Connext bridge was down in the development period, so we built a workaround relayer too.
Accomplishments that we're proud of
- Successfully build all cross-chain bridge processes with IPFS multi-chain storage.
- We can add this function in the main service too.
What we learned
- How to use IPFS
- How to build a cross-chain messaging relayer
- Cross-chain messaging security is very difficult to achieve.
What's next for NFTHashi
- Mainnet launch
- More secure IPFS content verifier
- Multichain metadata tracking and verifyer
Built With
- connext
- ipfs
- moralis
- nftstorage
Log in or sign up for Devpost to join the conversation.