How to set up multi-signature withdrawal approval on Bybit sub-accounts?

Multi-Signature Withdrawal Configuration

1. Log into the Bybit main account dashboard and navigate to Sub-Accounts → Manage Sub-Accounts.

2. Select the target sub-account and click Security Settings on its detail page.

3. Locate the Withdrawal Approval Policy section and toggle it to Enabled.

4. Choose Multi-Signature Mode from the approval method dropdown menu.

5. Enter the required number of signers (minimum 2, maximum 5) and specify their registered email addresses or internal user IDs.

6. Confirm the configuration by entering the main account’s Google Authenticator code and clicking Submit.

Signer Enrollment Process

1. Each designated signer must have an active Bybit account with completed KYC Level 2 verification.

2. Signers receive an automated invitation email containing a unique enrollment link and a 72-hour validity window.

3. Upon clicking the link, each signer lands on a dedicated consent page displaying the sub-account ID, withdrawal limits, and policy duration.

4. The signer must review and explicitly accept the terms, then complete biometric verification via Face ID or fingerprint scan if enabled on their device.

5. After acceptance, the system generates a unique public key for that signer and registers it in the sub-account’s access control list.

Withdrawal Execution Workflow

1. When a withdrawal request is initiated from the sub-account, the system immediately suspends execution and broadcasts a notification to all enrolled signers.

2. Each signer receives a push alert and email containing the transaction hash, destination address, asset type, amount, and timestamp.

3. Signers must log into their own Bybit accounts, go to Notifications → Pending Approvals, and verify the Merkle root of the withdrawal batch before approving.

4. A minimum of the preconfigured quorum (e.g., 3 out of 5) must approve within 48 hours; otherwise, the request expires and resets.

5. Once quorum is reached, the system validates all signatures against the stored public keys and executes the withdrawal only after confirming on-chain reserve proof via zk-SNARK attestation.

Policy Modification & Revocation

1. Only the main account holder may initiate changes to the multi-signature policy using the same Security Settings interface.

2. Modifying the signer list triggers an automatic deactivation of the current policy and requires full re-enrollment of all new signers.

3. Revoking a signer’s access does not invalidate prior approvals but prevents future participation—revocation takes effect immediately upon confirmation.

4. Any policy update forces regeneration of the sub-account’s withdrawal public key pair, invalidating previously cached signatures.

5. Historical approval logs—including timestamps, IP geolocation tags, and device fingerprints—are retained for 36 months and accessible under Audit Logs → Sub-Account Governance.

Frequently Asked Questions

Q: Can a sub-account initiate withdrawals without any signer approval if the policy is temporarily disabled?A: No. Disabling the multi-signature policy does not revert to single-signer mode—it completely blocks all withdrawal functionality until a valid policy is reactivated.

Q: Do hardware wallet signatures count toward the quorum requirement?A: Not directly. Hardware wallets can be used to sign approval payloads offline, but the resulting signature must be manually submitted through the Bybit web interface by the associated signer account.

Q: Is there a daily cumulative limit enforced at the sub-account level regardless of approval status?A: Yes. Each sub-account inherits the main account’s tier-based withdrawal cap—e.g., Tier 3 accounts are limited to 50 BTC per 24 hours—even when all signers approve.

Q: What happens if a signer’s account is suspended due to security violations during an active approval cycle?A: The system automatically excludes that signer from the current quorum calculation and extends the approval window by 12 hours to accommodate replacement signers.