
BRC stands for “Bitcoin Request for Comment.” It refers to community-driven proposals and conventions initiated on the Bitcoin network. Rather than changing Bitcoin’s core protocol, BRC operates at the application layer by standardizing data formats and interpretation methods, enabling new use cases like tokens and NFTs with agreed-upon rules.
In essence, BRC functions as a set of usage instructions and conventions. Developers document operational procedures and data formats, while wallets and indexers read and write according to these guidelines. This ensures different products can interpret on-chain data consistently and work together seamlessly.
The primary distinction between BRC and BIP lies in what they seek to change. BIP (Bitcoin Improvement Proposal) introduces modifications to the Bitcoin protocol or standard processes, impacting consensus or system-level functions. In contrast, BRC is a community convention mainly focused on defining how to implement new features using existing capabilities at the application layer.
BRC’s role is “non-intrusive and standardized expression.” It typically does not require network-wide node upgrades; as long as wallets, indexers, and applications follow the same convention, fungible tokens, NFTs, and other assets can be recognized and used within the Bitcoin ecosystem.
Most BRC proposals rely on Ordinals and inscriptions. Ordinals allow each satoshi (the smallest unit of Bitcoin) to be uniquely numbered and data—such as text or images—to be “attached” to specific sats. Inscriptions refer to embedding such data into transactions, recording it on-chain alongside the relevant sat.
A typical BRC proposal specifies which data to write and in which fields—such as operation type, token symbol, quantity—organized in structured text. Indexers then read these inscription records. Acting like accountants, indexers scan blocks and transactions following BRC rules to determine ownership of tokens or NFTs.
Key aspects of this approach are: First, data is genuinely written onto the Bitcoin blockchain; second, interpretation rules are documented in BRC specifications; third, asset balances and states are determined by indexers adhering to the same rules—which is why alignment in versions and details among indexers is crucial.
BRC proposals generally focus on “how to express assets and actions.”
These proposals are community conventions rather than official protocols. Their adoption depends on support and consistency from wallets, marketplaces, and indexers.
For basic interactions with BRC assets, follow these steps:
BRC adoption focuses primarily on fungible tokens and Bitcoin-native NFTs.
There are three main categories of risk associated with BRC:
Additionally, pay attention to address compatibility and backup security. Mistyped addresses, lost seed phrases, or leaked private keys can result in irreversible loss.
Looking ahead, BRC will continue serving as an “application-layer convention.” Once wallets and marketplaces align on standards, users enjoy smoother experiences while developers iterate more rapidly. The community is also working on optimizing data formats and indexing rules to reduce congestion and misinterpretation.
The relationship with Runes is noteworthy. Introduced in 2024, Runes encode fungible tokens using Bitcoin’s UTXO model to minimize reliance on external indexers—aiming for a more “native on-chain” approach. While BRC focuses on inscriptions and conventions, Runes provide a scalable solution for clear bookkeeping. Both may coexist for different use cases: BRC offers flexible expression for inscription-based assets; Runes deliver clarity for scalable accounting. Wallets and exchanges may support both options in the future, letting users choose based on their needs and fee preferences.
Overall, BRC accelerates application-layer innovation on Bitcoin. By understanding its “non-intrusive standardization” role, mastering wallet-indexer collaboration, factoring in platform support and risk controls, you can confidently utilize tokens and NFTs within the Bitcoin ecosystem.
BRC proposals are community-driven solutions designed to address functional limitations of the Bitcoin network. As Bitcoin’s scripting capabilities are limited and complex applications are challenging natively, BRC enables developers to build NFT, token, and other ecosystem apps by inscribing data directly onto the blockchain. This evolution transforms Bitcoin from a simple payment tool into a programmable platform.
Yes—interacting with BRC assets requires specialized wallets that support Ordinals inscriptions. Common options include Unisat, OKX Wallet, Gate Wallet, among others; these feature built-in management and trading for BRC-20 tokens. Unlike standard Bitcoin wallets, they can recognize and process data inscribed onto UTXOs so users can intuitively view and interact with BRC assets.
High fees stem from two factors: first, each inscription occupies block space on the Bitcoin network; when network congestion occurs, fees spike sharply. Second, actions like minting or transferring assets (e.g., BRC-20 tokens) require multiple on-chain interactions—each incurring a fee. Operating during network off-peak periods (such as weekends) can significantly reduce costs.
BRC proposals follow a community consensus model—mainly discussed and decided by Bitcoin developers, miners, and ecosystem participants rather than traditional voting mechanisms. Ordinary users lack direct voting rights but can influence outcomes indirectly by running full nodes, joining community discussions, or providing feedback in forums. Final adoption depends on developer acceptance and miner support.
BRC and Layer 2 represent distinct expansion paths: BRC extends functionality by inscribing data directly onto the main chain—offering full on-chain verifiability and security but with higher transaction costs. Layer 2 solutions like Lightning are off-chain payment networks featuring rapid transactions with low fees but requiring trust in intermediaries. BRC suits NFT/token applications; Layer 2 excels in high-frequency payments.


