Deploy Native Token Remote
Deploy the NativeTokenRemote contract on your L1.
The NativeTokenRemote contract is deployed on your L1. It calls the Native Minter precompile to create native tokens when AVAX is bridged from Fuji.
Understanding NativeTokenRemote
The NativeTokenRemote contract:
- Calls the Native Minter to mint native tokens when receiving bridge messages
- Burns native tokens when users bridge back to Fuji
- Requires collateralization before bridging is enabled
- References the NativeTokenHome on Fuji for security
Initial Reserve Imbalance
When deploying NativeTokenRemote, you set an initial reserve imbalance. This represents native tokens that already exist on your L1 (e.g., from genesis allocations) that aren't yet backed by locked AVAX.
If your L1 was just created with no pre-existing native tokens, you can set this to 0.
Switch to Your L1
Switch your wallet to the L1 you created earlier. Ensure you have native tokens for gas (from genesis allocation or faucet).
Deploy NativeTokenRemote
Use the Deploy Native Token Remote tool below:
- Enter or confirm the Teleporter Registry address on your L1 (should auto-populate if ICM is properly configured)
- Select Fuji C-Chain as the source chain
- Enter the NativeTokenHome address from the previous step
- Set the initial reserve imbalance (use
0if no pre-existing supply)
Make sure you have:
- Connected your Core Wallet to your L1
- Native tokens on your L1 for gas fees
- Your NativeTokenHome address from the previous step
- The Teleporter Registry address on your L1 (required for ICM communication)
Checking requirements...
Save the Contract Address
After deployment, save the Native Token Remote Address. You'll need it for registration and collateralization.
Contract State After Deployment
After deployment, your NativeTokenRemote:
- Is connected to the Teleporter Registry for ICM communication
- Is configured to call the Native Minter precompile
- Knows which NativeTokenHome to communicate with
- Is NOT registered with the home (transfers won't work yet)
- Is NOT collateralized (minting is blocked)
Next Steps
Now you need to register the remote and add collateral to enable bridging.
Is this guide helpful?