Skip to content

Some typos #1

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.

Sign up for GitHub

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

Open
just-a-node wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Some typos #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions developer-guide/sdk-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Contract Informations

### INatievHashi721
### INativeHashi721

Required interface of an NativeHashi721 compliant contract.

Expand All @@ -12,7 +12,7 @@ Required interface of an NativeHashi721 compliant contract.

`xSend(address from, address to, uint256 tokenId, uint32 sendToDomain)`

Send cross-messaging request to Connext \_xCall
Send cross-chain messaging request to Connext \_xCall

Bridge `tokenId`to sendToDomain ’s chain from address `from` to address `to`

Expand Down Expand Up @@ -48,7 +48,7 @@ Return the allowed contract address (messageable address)

`setBridgeContract(uint32 domain, address bridgeContract)`

Resister the `domain` to `bridgeContract` mapping
Register the `domain` to `bridgeContract` mapping

Requirement : onlyOwner

Expand Down
8 changes: 4 additions & 4 deletions document/architecture/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Let me describe along with the user flow.
![](<../../.gitbook/assets/Screen Shot 2022-05-25 at 14.44.36.png>)

* Deposit an NFT to NFT Hashi handler contract on Chain A (Origin Chain)
* The handler contract sends the information of NFT or chains to Chain B using xCall supported by Connext. (more info about xCall ⇒ [xapp-starter](https://github.com/connext/xapp-starter)
* The handler contract sends the information of NFT or chains to Chain B using xCall supported by Connext. (more info about xCall ⇒ [xapp-starter](https://github.com/connext/xapp-starter))
* The Handler Contract of Chain B receives the xCall from Chain A
* Compute the contract address from the information of these using Create2.
* If the computed address has not been deployed, the wrapped NFT contract is deployed to the computed contract address and minted. After the second time, the NFT is minted from a contract that has already been deployed.
Expand Down Expand Up @@ -63,12 +63,12 @@ Some initial setup is required when using the NFTs with the bridge function

* Deploy

NFTHashi Native contract must be deployed to all chains you wand to support
* Resister
NFTHashi Native contract must be deployed to all chains you want to support
* Register

In order for NativeHashi721 of different chains to recognize them as NativeHashi721 of the same project, the mapping of the chain's domain ID to the contract address must be registered in the NativeHashi721 of each chain

Detailed initial setup instructions are provided in the Dev Guide

* [Deployment](broken-reference)
* [Resister](broken-reference)
* [Register](broken-reference)
6 changes: 1 addition & 5 deletions operation-guide/how-to-check-nft-bridge-status.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,17 +29,13 @@ For more information about this section, this documentation will help you
* [https://docs.connext.network/Developers/xcall-status](https://docs.connext.network/Developers/xcall-status)



### Check transfer status

Go to connextscan page and search transferId you got before\
[https://testnet.amarok.connextscan.io/](https://testnet.amarok.connextscan.io/tx/0xcd05fea9a1d781cf759748b415d9dc85cb61c1ec33f40c1cc3e6cdc332c671f9?src=search)



If everything goes well and the token was transferred, a screeen like this will appear.\
If everything goes well and the token was transferred, a screen like this will appear.\
The transaction hash in the Execute confirms that the token is minted at the bridge destination.

Immediatery after bridge your NFT, connextscan page will return 404 Error to your browser.

![](<../.gitbook/assets/Screen Shot 2022-06-01 at 20.21.20.png>)