Dear Wormhole Team,
I’m developing a cross-chain music NFT platform using Wormhole
to bridge assets between Algorand and Solana. We’ve encountered
a critical blocker with the Algorand testnet Token Bridge that
appears to be an infrastructure configuration issue.
Issue Summary
The Algorand testnet Token Bridge (App ID: 86525641)
consistently fails with logic eval error: err opcode executed.
Details: app=86525641, pc=281 when attempting ANY operation
(attestAsset, transferTokens) with custom ASAs.
Root Cause Identified
After extensive debugging, we’ve identified that the Token
Bridge contract has ZERO asset opt-ins and cannot receive any
assets:
Token Bridge Status (verified 2025-08-18):
-
App ID: 86525641
-
Address:
MJA77XADFNUTX64FISCY6BAD33EG6LQXECXZ6NHY2ZP6K5FWEOGH6D62HA
-
Balance: 0.1 ALGO (insufficient for opt-ins)
-
Total Assets Opted In: 0
-
Can Receive Assets: NO
Technical Details
-
Environment: Algorand Testnet → Solana Devnet
-
Core Bridge App ID: 86525623 (appears functional)
-
Token Bridge App ID: 86525641 (non-functional)
-
Test ASA: 744069043 (and 33 other test ASAs)
-
Error: Fails at pc=281 during asset validation/opt-in check
-
SDK Version: @wormhole-foundation/sdk v0.9.0
What We’ve Verified
1. Custom ASAs exist and are properly configured
2. Our account holds the assets and can transfer them
3. Token Bridge has NO assets opted in (verified via
accountInformation API)
4. Token Bridge has insufficient ALGO balance for opt-ins (only
0.1 ALGO)
5. The pc=281 error occurs when the contract checks
asset_holding_get and fails
Critical Questions
1. Is the Algorand testnet Token Bridge (86525641) currently
operational? It appears to be in an unconfigured state with no
ability to receive assets.
2. Should the Token Bridge auto-opt-in to assets during
attestation/transfer? If yes, this mechanism appears broken on
testnet.
3. Who maintains the testnet Token Bridge funding and
configuration? It needs ALGO funding and asset opt-ins to
function.
4. Is there an alternative testnet Token Bridge we should use?
Or specific pre-configured test assets?
5. Can you provide the TEAL source or explanation for the
validation at pc=281? This would help understand the exact
failure point.
Impact
This is blocking our production development and testing. Our
platform is 99% complete - only the cross-chain bridge
functionality remains. We’ve invested significant time
debugging what appears to be a testnet infrastructure issue
rather than a code problem.
Requested Actions
1. Immediate: Confirm if Token Bridge 86525641 is the correct
testnet contract
2. Short-term: Fund and configure the testnet Token Bridge to
accept assets
3. Documentation: Provide testnet-specific setup requirements
if any
Reproduction Steps
# Check Token Bridge opt-in status (will show 0 assets)
curl https://testnet-api.algonode.cloud/v2/accounts/MJA77XADFNU
TX64FISCY6BAD33EG6LQXECXZ6NHY2ZP6K5FWEOGH6D62HA
# Attempt any attestAsset or transferTokens operation
# Result: pc=281 error due to no opt-in
We’re happy to provide any additional debugging information or
test transactions. Please advise on the correct path forward
for using Wormhole bridge on Algorand testnet.
Thank you for your assistance with this critical blocker.
Best regards, Jamall Winn