Deposits and Withdrawals

Rubin Chain uses a native bridge to move funds between supported source chains and the Rubin main account. Deposits and withdrawals are confirmed by Rubin validators — there is no third-party bridge or relayer in the path.

How it works

Deposit: user sends funds to the bridge contract on the source chain. Rubin validators observe the source chain, wait for finality, and credit the user's Rubin main account. Funds are then moved into the trading subaccount.
Withdrawal: user initiates a withdrawal on Rubin to a destination address. Funds move from the trading subaccount to the main account, then validators sign the withdrawal by consensus. Once enough signatures are collected, the withdrawal is delivered to the destination chain.

Security model

Validator consensus. Each withdrawal is approved by a supermajority (~2/3) of Rubin validators before it leaves the chain.
Timelock on large withdrawals. Withdrawals above a configured threshold are delayed before signing begins, providing a buffer to detect anomalies.
Daily limits. Per-chain and per-asset daily limits cap aggregate withdrawal volume.
Timeouts and refunds. If a withdrawal fails to collect signatures, get relayed, or be confirmed in time, funds are refunded to the user's main account.

How it works

Security model

Pages