Testing IBC on Noble Testnet ⇄ SVM Testnet
I've been testing IBC transfers between the Noble Testnet (Circle's official USDC issuer chain) and SVM Testnet.
The tests demonstrate that assets can move between Noble and SVM permissionlessly through IBC, without a centralized bridge or custodian.
USDC: Noble → SVM
I successfully transferred USDC from Noble Testnet to SVM Testnet.
- 1.0 USDC —
AF4D68417D9BBF6556970D966D46905CDE4DCC47F87367CA2FA81BE14435B817 - 5.0 USDC —
5C3406548645619EC210290B146586FADE1539E6248A7715301B0EC42B5A9102 - 0.1 USDC —
7B3D96B909DF978257970346AFF1CE732DAA98474C5F113D64E7D0936E06E77C
The 5 USDC transfer can be independently verified on SVMSCAN:
https://svmscan.blazeapps.org/txs/5C3406548645619EC210290B146586FADE1539E6248A7715301B0EC42B5A9102
USDS Transfer
I also tested an IBC transfer of 33.5 USDS to SVM.
Transaction:
https://svmscan.blazeapps.org/txs/7075F957B14DEBD24F1A49BFB87B80B5D814E04E887BEEDB35A08604BCEA14DB
This is another example of an asset being transferred through the IBC connection and arriving on SVM.
STEEM: SVM → Noble
I then tested the reverse direction with 100 STEEM transferred from SVM Testnet to Noble Testnet.
Transaction on SVM:
https://svmscan.blazeapps.org/txs/2ECC8196B6DBB8F7DD9C1F2C0581758E444B7BA86C69DA25B31D830F0DDBAB22
The 100 STEEM landed on my Noble address as expected.
The first packet timed out and was automatically refunded, and the second attempt went through successfully. This is normal IBC behavior: when a packet cannot be completed within the timeout period, the funds are returned rather than being lost.
STEEM: Noble → SVM — Round Trip Completed
After receiving the 100 STEEM on Noble, I sent the same 100 STEEM back from Noble to SVM.
Transaction:
https://svmscan.blazeapps.org/txs/5369AD4B1D9FF7CF8997D9F9CD06183D19ACBD75A78A6E5EAD578903A7ACBAD8
The 100 STEEM successfully returned to SVM.
So the complete round trip was:
SVM → Noble → SVM
100 STEEM → 100 STEEM
This is an important test because it demonstrates that the IBC connection is working in both directions, not merely as a one-way transfer.
What This Demonstrates
These tests demonstrate several important things about SVM's IBC connectivity:
- USDC can move from Noble Testnet → SVM Testnet
- USDS can move through the IBC connection
- STEEM can move from SVM Testnet → Noble Testnet
- STEEM can then move back from Noble → SVM
- The assets are transferred using IBC packets and on-chain verification
- There is no centralized bridge operator or custodian holding the funds
- The process is permissionless at the protocol level
Developers can already perform these transfers today using the Hermes relayer.
For developers, the current CLI/relayer workflow is enough to test and build applications.
For regular users, the next step is wallet integration. With support from wallets such as Keplr, the same IBC functionality can eventually become a simple one-click transfer experience rather than requiring users to interact with CLI commands and relayers directly.
Verify It Yourself
You can verify any SVM transaction directly from the command line:
steemvmd query tx <TX_HASH> --node https://steemvmd.steemscanner.com
Or query the RPC directly:
https://steemvmd.steemscanner.com/tx?hash=0x<TX_HASH>
You can also inspect the transactions through SVMSCAN:
5 USDC Noble → SVM
https://svmscan.blazeapps.org/txs/5C3406548645619EC210290B146586FADE1539E6248A7715301B0EC42B5A9102
33.5 USDS → SVM
https://svmscan.blazeapps.org/txs/7075F957B14DEBD24F1A49BFB87B80B5D814E04E887BEEDB35A08604BCEA14DB
100 STEEM SVM → Noble
https://svmscan.blazeapps.org/txs/2ECC8196B6DBB8F7DD9C1F2C0581758E444B7BA86C69DA25B31D830F0DDBAB22
100 STEEM Noble → SVM
https://svmscan.blazeapps.org/txs/5369AD4B1D9FF7CF8997D9F9CD06183D19ACBD75A78A6E5EAD578903A7ACBAD8
These are live testnet transactions and can be independently inspected.