-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a demo xapp that allows bridging an asset like an NFT from Ethereum, Polygon, or Avalanche to Celo #941
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 2000.0 cUSD (2020.0 USD @ $1.01/cUSD) attached to it as part of the celo-org fund.
|
Hey Eric 👋 Quick question for you: |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 3 weeks, 1 day ago. 1) dhruvjain1122 has been approved to start work. Flow of NFT:-
I'm going to implement a solution to bridge NFT assets between Celo and Polygon. [ ] BridgeRouter contract implemented on the local domain. I read the documentation about Xapp and it does not look hard to create a bridge between eth and Celo for NFTs. backend: a bridge contract to deposit the NFT on chain A or B, another contract to detect if some NFT was deposited and mint ou burn the NFT I will create a xapp where the user will be able to:
I have completed the contracts with tests. But I needed further information for which I had tagged you here. Can you please reply there? #941 (comment) I also was able get the dispatch event in logs in Rinkeby: https://rinkeby.etherscan.io/tx/0xa802d5d2d80c0013416325f3e39bf60aab4da90198d3b8b8f4727c82656f884a#eventlog Solidity Smart Contract to
creating a cross chain nft dapp shouldnt take too long. sending nft from one platform where theyre locked. Then a duplicate nft is issued to the sender I basically plan to create a NFT smart contract both ERC721/1155 in all the listed chains and then create an sdk that allows all of them to interact with each other. The Interaction involves locking or burning of the NFT in the contract on one chain and then transfer it to another. Learn more on the Gitcoin Issue Details page. |
@alecj1240 It'LL be awarded to more than one and up to 3. I'm open to extending it if it makes sense, too. What are you thinking? |
@dhruvjain1122 please ensure the steps are documented and included in the xapp example. With the bridging of an nft, what additional metadata would be included? |
@ericnakagawa I will keep that in mind, thanks for the advice |
@ericnakagawa How does the user pay for the NFT minting fees in another chain, in the source side if so how do we calculate the fees? |
@ericnakagawa could I get your telegram or discord id, I have some questions to ask |
@ericnakagawa Check this out! |
Hi @ericnakagawa I have completed the contracts with tests. But, I had to create a separate repo as I couldn't understand how to add tests in the Monorepo. Should I add you as a collaborator for the same? Currently the Router supports ERC721 transfers. |
I found the XAppConnectionManager for Rinkeby Can you confirm if the above address is the latest one? Also, please share the same for following: Celos Alfajores TestNet I guess I should be able to fetch domain from them but they would be helpful as well. |
I also was able get the dispatch event in logs in Rinkeby: https://rinkeby.etherscan.io/tx/0xa802d5d2d80c0013416325f3e39bf60aab4da90198d3b8b8f4727c82656f884a#eventlog How can I track it on Remote? Any suggestions? @ericnakagawa |
From what I understand no Updates have been pushed to Replicas in past 3 to 4 months on Alfajores, Kovan and Rinkeby. How can I test my XApp @ericnakagawa |
Successfully bridged NFT from PolygonMumbai to Alfajores network. Had to deploy my own Homes and Replicas. Relevant transactions: Transfers token id 1 of native NFT You can see the dispatch event from home. Decode data: {
messageHash: '0x05e97104a73dcbd76e8178483e6f5d209675ff9a7e254b7e334822fc245841ea',
leafIndex: 0,
committedRoot: '0x0000000000000000000000000000000000000000000000000000000000000000',
message: '0x000003e80000000000000000000000009365a6d7c89da1b6f22913aad65f000bb0f55dc900000000000007d00000000000000000000000009365a6d7c89da1b6f22913aad65f000bb0f55dc9000000000000000000000000379a056cb617ede30c56afb54e2f31850580676000000000000000000000000000000000000000000000000000000000000003e800000000000000000000000000000000000000000000000000000000000007d0000000000000000000000000379a056cb617ede30c56afb54e2f318505806760000000000000000000000000fc77079c043b39a64ee9fa70863f25c9a0381d0800000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001'
} Update on Alfajores(200): Call made to Replica. Prove on Alfajores(2000): Call made to Replica. Process on Alfajores(2000): Call made to Replica which calls to Router which mints the non-native NFT. |
Setting up backend support for updates, prove and process for custom deployed Replica and Home. |
@SurroundingArt64 @dhruvjain1122 I can be contacted on Discord at ericnakagawa#0001 and Telegram at @ericnakagawa -- let's connect to review your progress! |
HI @ericnakagawa Will connect on discord. |
Hi guys. Is this still open? I am having trouble with connecting with you guys. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 2000.0 cUSD (1990.92 USD @ $1.0/cUSD) has been submitted by: @ericnakagawa please take a look at the submitted work:
|
Cross chain applications (xapps) using Optics are a new way for moving assets between chains. We are looking for a live (testnet okay) example of this between one or more chains that Optics is running on to demonstrate the usefulness of this functionality.
Current xapp developer documentation can be found here. You may also review the token-bridge xapp docs here.
Review this video that walks through the concepts around xapp development.
This issue will be considered resolved once the following is completed:
The Gitcoin bounty will select multiple winners (up to 3) that fulfill the requirements listed above in the required time period. Up to three developers will be selected to submit solutions.
The text was updated successfully, but these errors were encountered: