# Full Withdrawals¶

contract FullWithdrawals is MainStorage, LibConstants, IVerifierActions, MFreezable, MOperator, MUsers

At any point in time, a user may opt to perform a full withdrawal request for a given off-chain vault. Such a request is a different flow than the normal withdrawal flow (see Withdrawals) in the following ways:

1. The user calls a contract function instead of calling an off-chain service API.

2. Upon the successful fulfillment of the operation, the entire vault balance is withdrawn, and it is effectively evicted (no longer belongs to the user). Hence, a full withdrawal request does not include an amount to withdraw.

3. Failure of the offchain exchange to service a full withdrawal request within a given timeframe gives the user the option to freeze the exchange disabling the ability to update its state.

A full withdrawal operation is executed as follows:

1. The user submits a full withdrawal request by calling fullWithdrawalRequest with the vault ID to be withdrawn.

2. Under normal operation of the exchange service, the exchange submits a STARK proof indicating the fulfillment of the withdrawal from the vault.

3. If the exchange fails to service the request (does not submit a valid proof as above), upon the expiration of a FREEZE_GRACE_PERIOD, the user is entitled to freeze the contract by calling freezeRequest and indicating the vaultId for which the full withdrawal request has not been serviced.

4. Upon acceptance of the proof above, the contract adds the withdrawn amount to an on-chain pending withdrawals account under the stark key of the vault owner and the appropriate token ID. At the same time, the full withdrawal request is cleared.

5. The user may then withdraw this amount from the pending withdrawals account by calling the normal withdraw function (see Withdrawals) to transfer the funds to the users Eth or ERC20 account (depending on the token type).

If a user requests a full withdrawal for a vault that is not associated with the StarkKey of the user, the exchange may prove this and the full withdrawal request is cleared without any effect on the vault (and no funds will be released on-chain for withdrawal).

Full withdrawal requests cannot be cancelled by a user.

To avoid the potential attack of the exchange by a flood of full withdrawal requests, the rate of such requests must be limited. In the currently implementation, this is achieved by making the cost of the request exceed 1M gas.

Implements IVerifierActions.clearFullWithdrawalRequest. Uses MFreezable, MOperator, MUsers.

event LogFullWithdrawalRequest(uint256 starkKey, uint256 vaultId)
function fullWithdrawalRequest(uint256 vaultId)
external
notFrozen()
function getFullWithdrawalRequest(uint256 starkKey, uint256 vaultId)
external
view
returns (uint256 res)
function freezeRequest(uint256 vaultId)
external
notFrozen()