Withdraw
The withdrawal function allows users to move their assets from Term Structure to their wallets.
Last updated
The withdrawal function allows users to move their assets from Term Structure to their wallets.
Last updated
Users can initiate a withdrawal request. Click the profile icon and navigate to "Withdraw."
Indicate the type and the amount of tokens to withdraw. Then, click "Withdraw Request."
Click “Sign." Then, a message that says “withdraw request sent” will appear.
Users can initiate a withdrawal request on Term Structure. The Term Structure withdrawal transaction will be bundled into a batch of transactions and committed to Ethereum for verification. Once the transaction is verified, the corresponding amount of tokens will be burned on Term Structure. This process ensures that the withdrawal is secure and properly recorded on Ethereum.
Users can click "check detail" next to the down arrow on the withdrawal page, and they will be directed to the "All History" page. Click the link icon🔗 under "TxID" to view the status of the transaction.
After the Term Structure withdrawal transaction is sent and verified on Ethereum, users can use the Ethereum withdrawal function to claim their assets from the zkTrue-up smart contract. This final step ensures that the assets are properly transferred to your wallet, allowing users to access their funds on the main Ethereum network.
A message that says "Your token has been withdrawn" will appear if the transaction is successful. Users can go to Etherscan to view transaction details.
Users can use Forced Withdrawal to perform the withdrawal process directly on the zkTrue-up contract whenever they experience censorship or any reason. Once the Forced Withdrawal is triggered, the sequencer will execute the request. In case the request is not fulfilled, users can activate evacuation mode and perform the evacuation on Ethereum to protect their assets.
Visit https://docs.ts.finance/zktrue-up/zk-architecture/forced-withdrawal-and-evacuation-mode for more details.
Please use the "Explorer" function, which can be found under "More," to check the status of each individual transaction.
The sequencer in zkTrue-up is responsible for collecting users’ transactions, batching them, and sending them to Ethereum. For the demo app, a round of event-based batch transactions will be triggered and sent to the Prover once the sequencer accumulates 32 event-based transaction records. Therefore, users will need to wait for a specific period of time before they can observe their actions being reflected in the protocol. It is important to note that this number may be adjusted to accommodate various circumstances upon the launch of the mainnet.
To learn more about the rollup services and how transactions are handled and settled, please refer to the doc at https://docs.ts.finance/architecture/rollup-services