Tensorplex Review: How to Claim TAO After Deprecation

Tensorplex Stake was a liquid-staking product for Bittensor: users could deposit tTAO on Ethereum and receive stTAO. That product and the related tTAO Bridge are now deprecated. The current service is a manual withdrawal route for people who already hold tTAO or stTAO, not a way to open a new staking position.

The stated aim is to return the underlying TAO to a Bittensor address after the token is burned. If your stTAO is on Base, Tensorplex instructs you to bridge it back to Ethereum first. The site explicitly warns against making new deposits or staking actions. For ongoing Bittensor staking, it points users to Backprop, but you should assess that as a separate service rather than assuming Tensorplex remains active.

The withdrawal has two stated charges: 0.2 TAO plus a 2% withdrawal fee. The site does not give a further fee breakdown, so check the current amount applicable to your position before you initiate a burn. You may also need to account for network and bridge costs when moving tokens; the project does not publish those costs as part of its withdrawal fee.

This is not an instant redemption. Tensorplex says manual requests are processed approximately once every two months, and the website does not show payout status. That means you should be prepared to wait and monitor the Bittensor wallet you declared. If a predictable exit date or a live request tracker matters to you, this process may not suit you. Do not send tokens until you understand the fee and are comfortable with the manual schedule.

The withdrawal flow requires you to burn your tokens and sign a message naming the Bittensor address that should receive TAO. The burn is the critical risk: the instructions say only Ethereum Mainnet transactions are accepted, and warn that burns on another chain are not accepted. For stTAO held on Base, bridge it to Ethereum first as directed.

Tensorplex also warns that the destination must be a Bittensor network address starting with “5”. Sending to an address on another Substrate network can cause permanent loss, with no recovery. No audit is listed for the product, and the withdrawal page does not provide payout-status tracking. These limits do not prove that a withdrawal will fail, but they leave little room to correct a mistake after an irreversible transaction. Verify the network, address, and amount before signing or sending.

Using the remaining service involves an Ethereum wallet, a Bittensor wallet address, and, for stTAO on Base, a bridge transfer back to Ethereum. You send tTAO or stTAO to the specified burn address on Ethereum Mainnet, connect the Ethereum wallet used for that transaction, then sign a message containing your destination SS58 address. The instructions say that the payout itself goes to Bittensor, not back to your Ethereum wallet.

There is no automated payout flow described. Processing happens manually about once every two months, and the site says you will not see payout status there; you need to check your Bittensor wallet for receipt. The instructions mention limited support for withdrawal-related issues during the deprecation period. They do not publish a standard processing time for an individual request, so plan for uncertainty rather than assuming a quick turnaround.

Tensorplex’s main limitation is that the staking service has been sunset. You cannot treat it as an active liquid-staking app, and the site explicitly tells users not to deposit or stake. The remaining exit route involves an irreversible burn, a manually processed request, and a fee of 0.2 TAO plus 2%. Payout status is not displayed on the website.

The product page does not list an audit, and it does not describe a self-service appeal or recovery process if you send tokens on the wrong chain or enter a wrong-network address. Before proceeding, carefully follow the current withdrawal instructions and make sure you control the Ethereum wallet used for the burn and the Bittensor destination wallet. If you cannot verify every step or accept the delay and fee, pause and seek withdrawal-specific support before sending tokens.