-
Notifications
You must be signed in to change notification settings - Fork 116
Description
Describe the bug
We are deploying two Avalanche L1 blockchains (following the Teleporter tutorial docs), chain1 and chain2 using the Avalanche CLI v1.8.7. We create chain 1 and chain2. We deploy chain1 and the deployment runs to completion. We deploy chain2 and it runs to completion too. However the previously configured RPC node for chain1 has been removed.
This cause any Teleporter message sending to subsequently fail.
To Reproduce
The following steps can be run using CLI v1.8.6 and v1.8.7:
avalanche network clean
rm -rf ~/.avalanche-cli
avalanche blockchain create chain1 --evm --latest\
--evm-chain-id 1 --evm-token TOKEN1 --evm-defaults\
--proof-of-authority --teleporter --validator-manager-owner 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC
avalanche blockchain create chain2 --evm --latest\
--evm-chain-id 2 --evm-token TOKEN2 --evm-defaults\
--proof-of-authority --teleporter --validator-manager-owner 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC
avalanche blockchain deploy chain1 --local
avalanche blockchain deploy chain2 --local
avalanche teleporter sendMsg chain2 chain1 "Hello World" --local
The ouput from the final command is:
β Use the private key of the Genesis Allocated address 0x155a23D7fae4D1468b188AcF696C099682EE24fd
Delivering message "Hello World" from source blockchain "chain2" (s9Ep8hT1QcfdCnoLGV8UUpDjhQXBnTQwzxgyULBy5VNtHMJMH)
Waiting for message to be delivered to destination blockchain "chain1" (2PnSAvxcueAEuiFRDkc8D2VvjgcY9z8aEruvBvkbBhtYsPse39)
Error: Post "http://127.0.0.1:44859/ext/bc/2PnSAvxcueAEuiFRDkc8D2VvjgcY9z8aEruvBvkbBhtYsPse39/rpc": dial tcp 127.0.0.1:44859: connect: connection refused
In the above example 127.0.0.1:44859 was the RPC node belonging to chain1.
Expected behavior
We expect both RPC nodes belonging to chain1 and chain2 to coexist after the deployment of chain2 and the teleporter sendMessage command to succeed.
Operating System
Ubuntu 24.04
Metadata
Metadata
Assignees
Labels
Type
Projects
Status