Repository navigation
Help needed: retrieving subnet tokens from Hyperlane ICA (happy to compensate!) #8444
Replies: 4 comments 2 replies
|
Hey @razvan-dam , thanks for reaching out and this is definitely not an ideal experience. We have reached out to TaoFi team to hopefully bring back up the UI. Below is some AI output that should give you some indication of how you could recover, since this is TaoFi's integration, we cannot take responsability over this unfortunately, but I hope this helps BackgroundWhen you used TaoFi, their contract (SwapBridgeAndCallFromMain at 0xc3697b332688b762bcba6765a5b16fe5e8d8034f on Base) created a Hyperlane Interchain Account (ICA) on Subtensor EVM specifically for your wallet. The ICA address is 0x5CbA68BB2B9918F1404C93941eA7F88A9d622d0a. TaoFi's contract has a public remoteCall() function that anyone can call. When called from your Base wallet, it uses your address as a salt to derive the correct ICA — meaning only you can move these funds. The transfer() function is whitelisted for all three of your AlphaTokens. Your current balances in the ICA What you need
Transaction detailsFor both transactions below:
Transaction 1: TEST (transfers 1.0 of each token) We recommend sending this first to verify everything works before moving the full balance. Calldata: This transfers exactly 1.0 token of each (SN-33, SN-44, SN-62) to your wallet on Subtensor EVM. After sending, wait ~2 minutes for the Hyperlane message to be relayed, then check your balance at Transaction 2: FULL BALANCE (transfers everything) Only send this after Transaction 1 succeeds and you've confirmed receipt. Calldata: Note: If the test transfer reduces balances, the full balance calldata above will attempt to transfer the original amounts and will fail for the ~1.0 tokens already moved. In that case, re-query balances and rebuild. For safety, you could just run the full transfer without the test — both have been simulated successfully. How we assembled the calldata (for verification) Step 1 — Each inner call is Step 2 — The outer call is remoteCall((bytes32 router, bytes32 ism, (bytes32 to, uint256 value, bytes data)[] calls, bytes hookMetadata)) (selector 0xa325fd4e) where:
Step 3 — The salt is automatically derived inside the contract as bytes32(uint256(uint160(msg.sender))) — i.e., your Base wallet address. This ensures only you can control your ICA. Source code reference: SwapBridgeAndCallFromMain.sol line 174 — remoteCall() function. Both calldata blobs have been simulated against Base mainnet using cast call --from 0x3e5C...0715 and both pass successfully. After recovery Your AlphaTokens will arrive at your wallet on Subtensor EVM (address 0x3e5C1a1E9A2DDDe585436f2fB634090b667F0715 — same as your Base wallet, same private key). From there you can hold, unstake via TaoFi's StakingManager, or trade as you wish. |
|
@nambrot this is brilliant! Thanks so much for this! I'll try to work it out tomorrow and keep you posted. |
|
Hey @nambrot, just wanted to say thanks again for this. When I first reached out I’d pretty much written those tokens off, so really wasn’t expecting that level of help. The step-by-step made it very straightforward, and it worked exactly as you said! Thanks so much! Saved me a decent chunk of money and a lot of stress. One quick ask, with TaoFi now shut, how could I unstake subnet tokens or swap them for TAO/stables? Thank you, Razvan |
|
Hi @nambrot Still struggling to extract the Bitensor subnet tokens through the Taofi ap. Have been using Grok to guide me through the 1. using taof app. 2. Call data option describe above. With option 1 here is the Grok summary: "The Hyperlane message was delivered to your ICA on Bittensor EVM, but the recipient contract (your ICA) failed to execute the inner payload (handle() call). The error “cannot estimate gas; transaction may fail or may require manual gas limit” is a generic wrapper that almost always means the inner transaction on Bittensor EVM is reverting. Most likely causes right nowThe approve step for your SN-4 token to the SwapAndStake router is failing or the allowance is already too low. The subsequent unstake/swap call is reverting (e.g. insufficient liquidity, slippage too tight, or the router/StakingManager logic changed after Astrid’s acquisition). The calldata generated by the current Taofi/Astrid UI has become slightly incompatible with the live contracts" Best way forward? |
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I used TaoFi to buy Bittensor subnet tokens from Base last year. TaoFi was acquired by Astrid and the swap interface stopped working end of February 2026. My tokens are sitting in a Hyperlane Interchain Account on Bittensor EVM and I need to get them out.
I've done the forensics and have everything mapped out. Just need help constructing the right calldata to either:
(a) unstake the alpha tokens → swap to USDC → bridge back to Base, or
(b) transfer the tokens out of the ICA to a wallet I can trade from directly on Bittensor EVM
Here's what I have:
Example buy transaction:
The buy flow was: USDC bridged to ICA → approved to SwapAndStake → swapped via UniswapV3Pool for WTAO → WTAO burned → SN tokens minted to ICA. I need to reverse this.
My wallet is on MPCVault (multisig), which supports custom calldata on Base. I need to know what to send to the InterchainAccountRouter on Base to instruct my ICA to execute the sell.
Any help hugely appreciated! Happy to compensate for anyone's time.
Thanks,
Razvan
All reactions