Why do you need to “claim” your assets?

In the new version of ShuttleFlow, a cross-chain transaction needs to interact with both the “from-chain” and “to-chain” because the new ShuttleFlow version removes “token captain” mechanism as the agency.

More details

What does the new version provide?

  • 0 service fee: the “token captain” mechanism is removed and, therefore, there is no more service fee pay for the agency from users pocket.
  • Users will only need to pay the gas fee of both the “from-chain” and “to-chain”.

How’s the new cross-chain procedure looks like?

Taking cross-out USDT from Ethereum to Conflux as an example.

1⃣️ ShuttleFlow will interact with MetaMask to confirm the cross-chain transaction.
2⃣️ Wait until the transaction is confirmed on Ethereum.
3⃣️ ShuttleFlow will then signal the users that their asset is ready to be claimed.

4⃣️ After clicking “Claim”, ShuttleFlow will then interact with Conflux Portal to complete the final asset claiming.

5⃣️ After the transaction is confirmed on Conflux Network, the asset will appear on the wallet address.

How long does it take for the asset to be ready for claiming?

How long it takes for the asset to be ready for claiming depends on the from-chain network. After the from-chain network processed the transaction, users can visit ShuttleFlow to claim their assets.

Users can quit ShuttleFlow after confirming transaction on the from-chain network and claim the asset later.

If I didn’t immediately claim the asset, will it be lost?

When the assets are ready to be “claimed”, users are able to “claim” their assets whenever they want.

Unclaimed assets will be locked in the ShuttleFlow smart contract.

Cautions: please make sure that you use the same Conflux wallet address that you used during the cross-chain operation when you look for your “unclaimed” asset.

**BTC cross-chain operation procedure: **

  1. When cross-chain asset from BTC to Conflux, users need to use their BTC wallet to send assets to the corresponding wallet address on the webpage. After 6 blocks confirmed on BTC network, you can then use your Conflux Portal to ‘claim’ your asset.
  2. When cross-chain asset from Conflux to BTC, ConfluxPortal will request signatures for the transaction. After being signed, you can simply wait for your BTC wallet to receive the asset.


can someone help me with this transaction

1 Like

I make swap on shuttleflow.io and he don’t claim my token

what a shit project

I’m stuck at the same place, but otherwise… It finished BSC chain, but says i need to “claim”, but i can’t find nowhere to claim!

Were you successful by now?

I always want to tell to my friedns about Conflux but conflux and shuttleflow are scammer.

I send 90 ustd to bsc but i dont know here is my money? nobody tell to me about 0.75 eth.
i send 99 cfx to bsc, still waiting for fee but nobody tell to me your tokens is not enought.


Swap failed: Error: [ethjs-rpc] rpc error with payload {“id”:2753177798764,“jsonrpc”:“2.0”,“params”:[“0xf9017ef90138818701830474089480ae6a88ce3351e9f729e8199f2871ba786ad7c5890340aad21b3b7000008204338401db9eb3820405b901045c350838000000000000000000000000000000000000000000000000000ae5d49a9d37ba000000000000000000000000000000000000000000000000000000000000008000000000000000000000000017406531fc3a372e1b1714c60d0536211caa9a410000000000000000000000000000000000000000000000000000000061b59cf900000000000000000000000000000000000000000000000000000000000000030000000000000000000000008d7df9316faa0586e175b5e6d03c6bda76e3d9500000000000000000000000008b8689c7f3014a4d86e4d1d0daaf74a47f5e0f2700000000000000000000000086d2fb177eff4be03a342951269096265b98ac4680a01a431a162b9820a63f0ca046318c323ba0cb0061e1c41f0189214cbab27332b1a036b7035d474f358706523706dcc367cfefc1c17ee4316ce22f94df07d5345878”],“method”:“eth_sendRawTransaction”} {“code”:-32603,“message”:“Invalid parameters: tx”,“data”:"“Failed imported to deferred pool: Transaction Pool is full”",“stack”:"Error: Invalid parameters: tx\n at s (chrome-extension://bjiiiblnpkonoiegdlifcciokocjbhkd/background.js:1:398548)\n at Object.internal (chrome-extension://bjiiiblnpkonoiegdlifcciokocjbhkd/background.js:1:398937)\n at l (chrome-extension://bjiiiblnpkonoiegdlifcciokocjbhkd/background.js:1:394041)\n at chrome-extension://bjiiiblnpkonoiegdlifcciokocjbhkd/bac