BRC2.0 FAQ in English Translation:
BRC2.0 Frequently Asked Questions
Hello, Bitcoin family! Thank you for your attention to BRC2.0, which is a long-awaited step for BRC20, soon to be launched on the mainnet, implementing smart contracts at the Bitcoin underlying layer.
As Bitcoin's development momentum strengthens, the community has raised some thought-provoking questions about its possibilities, working principles, and future development directions. Here are some of the most common questions and their answers:
BRC2.0 Basics
What is BRC2.0?
BRC2.0 is an upgrade to the original BRC20 token standard, directly introducing EVM-compatible smart contracts on Bitcoin's Layer 1 with native settlement and security.
It brings programmability to Bitcoin, enabling thousands of battle-tested EVM contracts and dApps to be deployed on the main chain.
How is BRC2.0 different from BRC20?
The original BRC20 standard allowed basic token minting and transfer, but lacked programmability. BRC2.0 introduces smart contract functionality, supporting advanced financial applications like DeFi, stablecoins, DFAI, DAO, RWA, etc.
Does BRC2.0 require multi-signature, sequencers, or off-chain approvals?
No. Users can deploy or interact with EVM-compatible contracts through standard Bitcoin transaction inscriptions. No multi-signature wallets, sequencers, or off-chain approvals are needed.
Is BRC2.0 secure?
BRC2.0 is built on Bitcoin's proof-of-work security and decentralization. It follows trusted and extensively tested smart contract standards, ensuring on-chain execution and avoiding external dependencies.
How to deploy smart contracts with BRC2.0?
The deployment process involves a standard Bitcoin transaction writing contract code. Currently, you can do this using Best in Slot's public UI on Signet:
Which wallets support BRC2.0?
Wallets like @Xverseapp, @LeatherBTC, @wallet, @unisat_wallet, @phantom, @oylwallet, and others that can sign Bitcoin transactions can already interact with BRC2.0 to some extent. However, full smart contract functionality may require technical upgrades, especially for wallets not using our API. We will share dedicated compatibility updates and integration guidelines later.
[The translation continues in the same manner for the rest of the document, maintaining the specified terminology translations.]Yes. Most Ethereum-compatible development tools can be used with BRC2.0, which means existing methods for querying contract data (such as through The Graph, Ethers.js, or custom indexers) will be applicable.
If EVM executes smart contracts, and users have ORDI and want to execute smart contract operations, do they need to cross-chain, or can they operate directly?
No, you do not need to cross-chain. As a user, you will likely just need to click a few buttons, and everything will be abstracted away.
Our project is currently developing on Ethereum, Base, Polygon, or other EVM chains using Solidity. Will it be easier to port to BRC2.0 in the future? Does it support proxy contracts and similar functions?
Yes, porting your Solidity project to BRC2.0 will be very simple, and it supports proxy contracts.
Is it possible for BRC20 to upgrade to store data in OP_RETURN? Will contract data be stored in OP_RETURN or in the witness?
It will use witness data, as it is more efficient for relatively large data.
Regarding the BRC20 Balance Server required for BRC2.0, is it open-source or implemented in OPI?
It is already part of the OPI BRC20 indexer. After enabling BRC2.0, it will automatically start the server.
Is the BRC2.0 testnet already online? Where can I try it?
Yes, the BRC2.0 testnet is online on Bitcoin Signet. Now, you can use our public tools to explore, deploy, and interact with smart contracts:
Does Signet allow ordinary users to participate in testing?
Signet is primarily for developers, but interested users are welcome to explore and try it out. However, please note that it is not an incentivized testnet.
Should a specific value be set for the Signet BRC2.0 activation height, or is it random?
We currently set it to 230,000, but this is completely random. The first valid BRC2.0 inscription is at 241,423, so any value below this should be valid. To speed up initial indexing, we may adjust it to 240,000 in the future.
