Writing Skills
writing-skills
效率与协作技能,来自 obra/superpowers,查看原文获取完整用途和操作说明。
bitcoin-metaprotocols-brc-20【部署与运维】BRC-20: fungible token standard via JSON inscriptions. Deploy / mint / transfer operations. Permissionless and unaudited; large ecosystem post-2023. USE WHEN: building BRC-20 tooling, evaluating token issuance on Bitcoin, comparing with Runes / Taproot Assets.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Token standard defined via JSON inscriptions. Created May 2023 by @domodata. Originally a "fun experiment", became massive ecosystem.
Each operation is a JSON inscription:
{
"p": "brc-20",
"op": "deploy",
"tick": "ordi",
"max": "21000000",
"lim": "1000"
}
tick = 4-character ticker (case-insensitive). Once deployed, max
supply fixed.
{
"p": "brc-20",
"op": "mint",
"tick": "ordi",
"amt": "1000"
}
Each mint must respect lim and total max. First-come-first-served
until cap.
Step 1: inscribe transfer:
{
"p": "brc-20",
"op": "transfer",
"tick": "ordi",
"amt": "100"
}
Step 2: send the inscription to recipient. Receipt = balance moves.
BRC-20 has no on-chain validation — it's an indexer convention. Each indexer must:
max / lim constraints.Indexers must agree on rules (otherwise different indexers see different balances).
| Aspect | BRC-20 | Runes | Taproot Assets |
|---|---|---|---|
| Activation | May 2023 | April 2024 (halving) | 2023 |
| Mechanism | JSON inscriptions | Native protocol op_returns | Client-side validation |
| State tracking | Off-chain indexer convention | Native (each rune is a UTXO commitment) | Client-side merkle |
| Efficiency | High overhead | Native, smaller | Smaller |
| Validation rules | Indexer-defined | Protocol-defined | Schema-defined |
Most agree: Runes > BRC-20 in efficiency. BRC-20 is "first-mover" but architecturally suboptimal.
As of September 2026: