I just tested the time it takes to cross-chain from the Bitcoin mainnet to Bitcoin L2 BOB. Currently, with no congestion on the Bitcoin mainnet, it took nearly 1 hour.

During the waiting time, I read the official cross-chain bridge Gateway documentation for BOB. Unlike the bidirectional BitVM cross-chain bridge envisioned in the white paper, the BOB Gateway cross-chain bridge in Phase 1 is a light client cross-chain bridge, and since it is built on the OP Stack, data availability verification relies on the Ethereum mainnet.

Here is the lifecycle of the cross-chain TX from BTC to BOB:

1⃣ The user initiates a cross-chain request by signing with a native segwit Bitcoin address.

2⃣ The user's BTC UTXO is transferred to an LP (currently speculated to be the BOB team's) address.

The OP Return bytecode includes the hash value of this TX.

3⃣ BOB runs a light client on the Bitcoin mainnet (tBTC solution) to verify the legality of the hash value included in the OP Return.

4⃣ The Gateway mints WBTC or swaps it for BTC LRT/LST for the user on BOB L2, and batches the updated state data to the Ethereum mainnet for verification and storage.

It can be seen that the BOB team is putting a lot of effort into optimizing the time and interaction experience of the official cross-chain bridge. However, due to the current Phase 1 solution stack being limited by Bitcoin's programmability and Ethereum's finality, it is unlikely to see short-term improvements in reducing the official bridge cross-chain time.

Unless you are completing tasks for OKX x BOB, which require using the official bridge, it is better to use third-party cross-chain bridges based on a message-liquidity architecture.

免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。