Skip to content

Latest commit

 

History

History
177 lines (122 loc) · 5.71 KB

_INSTRUCTIONS.md

File metadata and controls

177 lines (122 loc) · 5.71 KB
Raw

Instructions - Send & Receive

The following code example will show you how to send, receive and verify the receival of messages using teleporter and foundry. It includes instructions for the local network and fuji testnet.

Local Network

For convenience the private key 56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027 of the default airdrop address is stored in the environment variable $PK. Furthermore, the RPC-url for the C-Chain of your local network is set in the foundry.toml file.

Subnet Configuration

To get started, create a Subnet configuration named "mysubnet":

avalanche subnet create mysubnet

Your Subnet should have Teleporter enabled, the CLI should run an AWM Relayer, and upon Subnet deployment, 1,000,000 tokens should be airdropped to the default ewoq address:

? Choose your VM:
✔ Subnet-EVM
? What version of Subnet-EVM would you like?:
✔ Use latest release version
? Would you like to enable Teleporter on your VM?:
✔ Yes
? Would you like to run AMW Relayer when deploying your VM?:
✔ Yes
Installing subnet-evm-v0.6.4...
subnet-evm-v0.6.4 installation successful
creating genesis for subnet mysubnet
Enter your subnet's ChainId. It can be any positive integer.
ChainId: 012345
Select a symbol for your subnet's native token
Token symbol: NATV
? How would you like to set fees:
✔ Low disk use    / Low Throughput    1.5 mil gas/s (C-Chain's setting)
? How would you like to distribute funds:
✔ Airdrop 1 million tokens to the default ewoq address (do not use in production)
prefunding address 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with balance 1000000000000000000000000
? Advanced: Would you like to add a custom precompile to modify the EVM?:
✔ No
✓ Successfully created subnet configuration

Finally, deploy your Subnet:

avalanche subnet deploy mysubnet
? Choose a network for the operation:
✔ Local Network
Deploying [mysubnet] to Local Network

Setting the Blockchain ID in the Contracts

Make sure to replace the blockchainID in the sender contract src/0-send-receive/senderOnCChain.sol with the ID of your Subnet's blockchain.

🚫 blockchainID of Subnet ≠ chainID of Subnet

You can find the blockchainID of your Subnet with this command:

avalanche subnet describe mysubnet

Take the HEX blockchain ID and replace it sender contract:

teleporterMessenger.sendCrossChainMessage(
    TeleporterMessageInput({
        // Replace with blockchainID of your Subnet (see instructions in Readme)
        destinationBlockchainID: 0x92756d698399805f0088fc07fc42af47c67e1d38c576667ac6c7031b8df05293,
        destinationAddress: destinationAddress,
        
        // ...
    })
);

Deploying the Contracts

After adapting the contracts you can deploy them with forge create:

forge create --rpc-url local-c --private-key $PK src/0-send-receive/senderOnCChain.sol:SenderOnCChain

Save sender address in environment variable

export SENDER_ADDRESS=0x...
forge create --rpc-url mysubnet --private-key $PK src/0-send-receive/receiverOnSubnet.sol:ReceiverOnSubnet

Save receiver address in environment variable

export RECEIVER_ADDRESS=0x...

Sending a Message

You can find <sender_contract_address> in the output of the first and the <receiver_contract_address> of the second forge create command in the line saying Deployed to:.

cast send --rpc-url local-c --private-key $PK $SENDER_ADDRESS "sendMessage(address,string)" $RECEIVER_ADDRESS "Hello"

Verifying Message Receipt

cast call --rpc-url mysubnet $RECEIVER_ADDRESS "lastMessage()(string)"

Fuji Testnet

Creating a Wallet

For deploying on testnet, we cannot use the airdrop wallet, since the private key is commonly known. To create a new wallet that is stored in a keystore, issue the following command. It will prompt you to secure the private key with a password.

cast wallet new .

You should now see a new Keystore in the root of your project looking something like this c3832921-d2e6-4d9a-ba6f-017a37b12571. Rename this file to keystore. For easier use of the keystore we already configured a envorinment variable called KEYSTORE pointing to the keystore file in the working directory.

You can use the wallet stored in the keystore by adding the --keystore flag instead of the --private-key flag.

cast wallet address --keystore $KEYSTORE

Funding your Wallet with Fuji Tokens

Head to the Avalanche Testnet Faucet and fund your keystore address with Fuji AVAX and Dispatch tokens. Use the coupon code avalanche-academy.

Setting the Blockchain ID in the Contracts on Fuji

Make sure to adapt the destinationBlockchainID of your sending contracts to use the blockchain IDs of the Fuji network:

Chain Blockchain ID
Fuji C-Chain 0x7fc93d85c6d62c5b2ac0b519c87010ea5294012d1e407030d6acd0021cac10d5
Dispatch 0x9f3be606497285d0ffbb5ac9ba24aa60346a9b1812479ed66cb329f394a4b1c7

Deploying the Contracts

After adapting the contracts you can deploy them using your keystore wallet:

forge create --rpc-url fuji-c --keystore $KEYSTORE src/0-send-receive/senderOnCChain.sol:SenderOnCChain
forge create --rpc-url dispatch --keystore $KEYSTORE src/0-send-receive/receiverOnSubnet.sol:ReceiverOnSubnet

Sending a Message

cast send --rpc-url fuji-c --keystore $KEYSTORE <sender_contract_address> "sendMessage(address,string)" <receiver_contract_address> "Hello"

Verifying Message Receipt

cast call --rpc-url dispatch <receiver_contract_address> "lastMessage()(string)"