This is a simple description of how to use this bridge application. For the detailed architecture, or developer guide, please check our documentation http://docs.nfthashi.com/
- What is NFT Hashi?
- How to use NFT Hashi
- How to bridge
- How to check the bridge status
NFTHashi is a trust-minimized cross-chain NFT bridge powered by Connext & Nomad
We support all NFTs even that have already been issued can be bridged to other chains. That means your Punks or BAYC can go beyond Ethereum and can be used on any chain you like We use Connext, and Connext provides trust-minimized cross-chain messaging using optimistic verification provided by Nomad, the most trust-minimized protocol for cross-chain messaging so you can safely bridge your valuable NFTs!
NFTHashi support any NFTs already created. When you deposit an NFT to the contract in Chain A, the NFT is minted in Chain B. When you burn the NFT in Chain B, the deposited NFT is returned.
- Connect your web3 wallet, and select chains you want to bridge
- Select the NFT you want to bridge, and confirm
- Metamask is launched twice: Approve and Bridge.
For more detaild descriptions, see this how-to-use docs https://docs.nfthashi.com/operation-guide/how-to-use-nfthashi
We provide the contract integrated bridge function as SDK for the users who want to create a more advanced NFT utilizing cross-chain. For example, a chain with minted NFTs, a chain with current NFTs, the itinerancy of NFT bridges, and other NFTs whose metadata changes according to these attributes, and so on, will allow for new expressions that have not been possible before! You can create those NFTs easily by installing SDK and inheriting the contract follow the instructions in the document below.
If you want to deploy and use NFT with bridge function by yourself, please refer to Document. https://docs.nfthashi.com/developer-guide/how-to-deploy-your-own-cross-chain-nft
- Copy the transaction hash on the origin chain
- Use this code in subQuery of the origin chain to get “Transaction ID”
{
originTransfers(
where: {
transactionHash: "<your_transaction_hash>"
}
) {
transferId
}
}
-
Use this code in subQuery of the destination chain to get the transaction hash
*It takes about an hour to send message from Chain A to Chain B
{
destinationTransfers(
where: {
transferId: "<your_transfer_id>"
}
) {
executedTransactionHash
}
}
For more information about this section, this documentation will help you
Please contact me if you have any questions, feedback, or are interested in collaborating !! And, we'd love to discuss future directions of Cross-chain NFT, so feel free to chat us!
Run this at root
cd packages/contracts && yarn cpx 'contracts/**/*.sol' dist && yarn cpx package.json dist/ && yarn cpx README.md dist/ && cd dist && npm publish && cd .. && rm -rf dist && cd ../..