Provide a concise narrative that clearly states each of (a)–(e) below.
ORDI does not solve a conventional protocol problem. It was deployed on March 8, 2023 by pseudonymous developer Domo as a proof-of-concept to test whether Ordinals inscription mechanics could support fungible token behavior on Bitcoin. The BRC-20 standard it introduced uses JSON-formatted inscriptions to define, mint, and transfer tokens natively on the Bitcoin base layer without smart contracts or sidechains.
(Source: Domo BRC-20 Experiment, BRC-20 Tokens: A Primer)
No ORDI-specific operating organization, roadmap, or treasury exists. ORDI was deployed as a fair-launch experiment with no ongoing development team or issuer. The Layer 1 Foundation — a nonprofit coalition co-founded by Domo that describes itself as supporting BRC-20 and other Bitcoin metaprotocols — coordinates indexer governance for the BRC-20 standard at the ecosystem level, but its legal jurisdiction and formal incorporation details are not publicly disclosed. It has no ORDI-specific mandate, budget, or token-administration authority. No organizational body is responsible for ORDI as a token.
ORDI is the first BRC-20 token on Bitcoin. Its deploy inscription sets p = brc-20, op = deploy, tick = ordi, max = 21000000, and lim = 1000. Balances are derived by aggregating deploy, mint, and transfer inscriptions via off-chain indexers rather than smart contract execution. ORDI does not require a sidechain, separate token, or change to Bitcoin's protocol. The entire 21,000,000 supply was minted within one day of deployment, on March 9, 2023, as users inscribed up to the 1,000-token mint limit per inscription.
(Source: ORDI deploy inscription content, Domo BRC-20 Experiment, Ordinal Theory Handbook - Inscriptions)
ORDI functions as a fungible BRC-20 asset on Bitcoin whose lifecycle consists of deploy, mint, and transfer operations. It has no protocol-native utility beyond that role. Domo, the creator, characterized BRC-20 as "a fun experimental standard demonstrating that you can create off-chain balance states with inscriptions" and initially described the tokens as worthless. ORDI carries no governance rights, staking function, fee-sharing mechanism, or formal utility within any protocol.
(Source: ORDI deploy inscription content, Domo BRC-20 Experiment, BRC-20 Tokens: A Primer)
ORDI carries no admin keys, upgrade roles, pause functions, or smart-contract governance. Token validity depends entirely on BRC-20 indexer interpretation of inscription history using first-in-first-out sat tracking and first-ticker precedence rules. The Layer 1 Foundation coordinates indexer governance for the BRC-20 standard at the ecosystem level, but no ORDI-specific control surface exists.
(Source: Ordinal Theory FAQ, Ordinal Theory Handbook - Inscriptions, Domo BRC-20 Experiment)
For each existing entity: Labs/DevCo (e.g., Founder, CEO, CTO, COO), Foundation (e.g., President, Executive Director, CFO, COO), and DAO / onchain governance leadership (if applicable) list the: (a) full names, (b) official titles, (c) and prior experience of key team members. For any non-existent entity, explicitly mention it does not exist. External links may be included but they will not factor into the score.
Full Name | Entity | Official Title | Prior Experience |
|---|---|---|---|
Blockworks note: ORDI has no Labs/DevCo, Foundation, or DAO governance structure. The token was deployed by a pseudonymous developer known as Domo, whose identity remains undisclosed. No additional named team members or organizational roles exist. The underlying Ordinals protocol was built by Casey Rodarmor, a named software engineer and former Bitcoin Core developer, but Rodarmor has no organizational or economic relationship with ORDI. He publicly clarified after Binance's November 2023 listing that "ORDI is not associated with the Ordinals project, The Open Ordinals Institute, or The Ordicord." |
Provide a structured description of the DAO's governance, powers, and economic rights. If a DAO does not exist, state so. Address the lettered items below. Even if there is no DAO, there must be an answer to (d).
No DAO exists. No IP is owned or controlled by any ORDI-specific entity. The BRC-20 standard is maintained at the ecosystem level by the Layer 1 Foundation, not by an ORDI-specific entity.
No DAO, admin key, multisig, governance executor, or contract-level authority exists for ORDI. The token operates via inscription mechanics on Bitcoin with no on-chain administrative control surface.
No locking or staking mechanism exists for ORDI.
ORDI tokenholders have no formal economic rights, revenue claims, treasury access, or governance authority. No value-accrual mechanism of any kind exists.
No dissolution mechanism exists. No entity can wind up or dissolve ORDI; the inscriptions are permanent records on the Bitcoin blockchain.
Blockworks note: No DAO exists for ORDI.
For the Primary Foundation do the following independently. If an entity does not exist, state that explicitly. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist. Definitions: The primary Foundation and DevCo can be explained as those entities which are directly involved in the issuance of the native token at launch.
Not applicable. No Foundation exists.
Not applicable. No Foundation exists.
Not applicable. No Foundation exists.
Not applicable. No Foundation exists.
Not applicable. No Foundation exists.
Not applicable. No Foundation exists.
Blockworks note: No ORDI-specific Foundation entity exists. ORDI was deployed by a pseudonymous individual with no legal wrapper, and no foundation entity was involved in issuance at launch or created afterward.
(Source: ORDI deploy inscription content, ORDI inscription 348020)
For the Primary DevCo do the following independently. If an entity does not exist, state that explicitly. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist. Definitions: The primary Foundation and DevCo can be explained as those entities which are directly involved in the issuance of the native token at launch.
Not applicable. No DevCo exists.
Not applicable. No DevCo exists.
Not applicable. No DevCo exists.
Not applicable. No DevCo exists.
Not applicable. No DevCo exists.
Not applicable. No DevCo exists.
Blockworks note: No ORDI-specific DevCo entity exists. ORDI was deployed by Domo without a corporate or organizational structure of any kind.
(Source: ORDI deploy inscription content, ORDI inscription 348020)
Disclose launch and initial supply details in a single initial allocation schedule covering the token's launch.
The deploy inscription set a maximum supply of 21,000,000 ORDI with a 1,000-token mint limit per inscription. The full 21,000,000 supply was minted within one day of deployment on March 9, 2023. All tokens entered circulation through public fair minting; no tokens were locked at launch.
No issuer allocation schedule exists. No team bucket, investor reserve, treasury, or use-of-funds schedule was established. All 21,000,000 tokens were distributed through open public minting on a first-come, first-served basis at 1,000 tokens per inscription.
No fixed initial offering price was set. ORDI began trading on OTC markets immediately after minting completed on March 9, 2023, at approximately $0.005 per token. No issuer-controlled price-discovery mechanism existed.
ORDI
21,000,000 maximum supply, fixed and fully minted. No inflation schedule, no additional minting capability, and no burn mechanism exist.
No vesting or release schedule exists. All tokens were freely transferable from the time of minting.
Blockworks note: (Source: ORDI deploy inscription content, BRC-20 Tokens: A Primer, Domo BRC-20 Experiment)
Address each of the following sub-items based on the project's airdrop status. If a sub-item does not apply to the project's situation, state that explicitly.
No airdrop planned or conducted: No airdrop has ever been conducted and no airdrop is planned. ORDI was distributed exclusively through open public minting under the BRC-20 deploy/mint model. Any wallet that paid Bitcoin transaction fees to inscribe a mint transaction during the minting window received up to 1,000 ORDI. No issuer-controlled address-level distribution file, Merkle dump, or recipient list was produced because no issuer existed to produce one.
(Source: ORDI deploy inscription content, Domo BRC-20 Experiment, BRC-20 Tokens: A Primer)
Projects must disclose all material terms of market-making arrangements that affect token liquidity. If the project has no agreements or deals with market makers, state that explicitly; doing so earns full credit. For each market maker, include in a table:
If the project has no agreements or deals with market makers, state that explicitly; doing so earns full credit. If no native tokens were loaned or allocated to market makers, state that explicitly; cash/fiat retainers or fees are not required for this item.
Blockworks note: No market maker agreements exist. ORDI has no issuer, legal entity, or treasury capable of entering into market-making arrangements. No tokens were loaned or allocated to market makers. Liquidity on centralized exchanges is provided by independent market participants, not by an issuer.
Projects must disclose all material terms of centralized or decentralized exchange listings that affect token liquidity. For each listing, include in a table:
If the project has no agreements or deals with CEX or DEX, state that explicitly; doing so earns full credit; cash/fiat fee amounts are not required for this item.
Blockworks note: No exchange listing agreements exist on the issuer side. ORDI has no issuer or legal entity capable of entering into listing arrangements. Exchange listings occurred through unilateral exchange decisions, not issuer-negotiated deals.
Key public listing timeline for reference:
No project-side token allocations for listing, native-token listing fees, or formal listing agreements have been disclosed because no issuer exists to disclose them.
(Source: Ordinals (ORDI) Gets Listed on KuCoin! | KuCoin, BRC-20 Tokens: A Primer)
Disclose all prior token sales by the Project — including fundraising rounds, any material OTC sales to investors, and any discounted market-maker sales. For each sale, provide:
If no prior sales occurred, state that explicitly (e.g., "No prior fundraising, OTC, or discounted MM sales have occurred.").
Blockworks note: No prior fundraising, OTC sales, discounted market-maker sales, or early-investor arrangements have occurred. ORDI was distributed exclusively through public fair minting with no priced issuer sale, SAFT, SAFE, or investment instrument of any kind.
If any, list prior exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply. This question is not asking about general protocol, application, or smart contract exploits unless the incident directly affected the native token itself. If no prior incidents, state this explicitly (e.g., "No exploits affecting tokenholders or protocol funds as of YYYY-MM-DD").
Blockworks note: No exploits have affected ORDI tokenholders or protocol funds. ORDI runs no smart contracts, holds no protocol treasury, and controls no pooled funds. The token's inscription-based architecture eliminates the attack surface typical of smart-contract protocols.
The BRC-20 standard has documented ecosystem-level vulnerability classes — including the BRC-20 Pinning Attack identified by CertiK — but no exploit incident affecting ORDI holders' balances has been recorded as of this filing date.
Describe material risk factors across the three categories below. Each category includes prompts to address at a minimum.
(a) Regulatory, Legal & Tax Risks — Describe how evolving laws and regulations could affect the project by answering, at a minimum, questions like:
Impact of Regulatory Change on TGE and Listings: (If applicable) How could evolving or conflicting laws and regulations affect your ability to complete the TGE, deliver tokens to purchasers, and list or maintain the token on trading venues in key jurisdictions?
Entity-Level Regulatory Impact: (If applicable) How could regulatory or legal changes impact your core entities (Foundation, DevCo, DAO, affiliated service providers), including enforcement actions, licensing requirements, or forced changes to structure or operations?
Tokenholder Tax Treatment: (If applicable) What uncertainties exist around how tokenholders may be taxed, and make clear that tokenholders are responsible for understanding their own tax obligations?
Jurisdictional & User Access Restrictions: (If applicable) If the project restricts access for certain jurisdictions or user types (e.g., U.S. persons, sanctioned countries, retail vs. professional), what are those restrictions and what risks do they create for users and for the project?
(b) Protocol, Technology & Security Risks — Describe risks to network and contract reliability, correctness, and safety by answering, at a minimum, questions like:
Bugs and Design Flaws: (If applicable) What bugs, design flaws, or implementation errors could exist in your core protocol code, smart contracts, and any bridges, rollups, or oracles that you depend on, and how could these lead to loss of funds or disruption of the protocol?
Security Measures & Their Limitations: (If applicable) What security measures have you taken (audits, formal verification, bug bounties), and what types of failures might these measures still fail to detect or prevent?
(c) Token Economics, Unlocks & Incentive Risks — Describe how the token's economic design and supply schedule could affect holders by answering, at a minimum, questions like:
Critical Economic Assumptions: (If applicable) Which economic assumptions (e.g., staking yields, fee revenue, liquidity incentives, MEV capture, demand for blockspace) are critical for protocol security, utility, and governance, and what happens if those assumptions fail?
Governance Control over Monetary Policy & Rewards: (If applicable) To what extent can governance change monetary policy, fee parameters, or reward allocations (e.g., inflation rate, treasury flows, incentive programs), and how could such changes adversely affect tokenholders?
ORDI has no issuing entity, legal wrapper, or jurisdiction of incorporation. No regulatory license has been sought or obtained on behalf of ORDI. The SEC has not issued clear guidance on whether BRC-20 tokens qualify as securities, and any future enforcement action or unfavorable classification could materially affect exchange availability and market liquidity. Because no issuer exists, there is no entity positioned to respond to regulatory inquiries, adjust token structure, or implement compliance measures. Tokenholders bear full exposure to regulatory risk without any organizational backstop. Tax treatment of ORDI varies by jurisdiction and is the responsibility of each individual tokenholder. No issuer-side tax guidance, legal opinion, or user-restriction policy has been established.
Domo characterized BRC-20 as experimental at launch and warned that existing infrastructure could mishandle mint and transfer flows. ORDI's balance state is not enforced by Bitcoin consensus; it depends on off-chain indexer interpretation of inscription history. Indexer disagreements, bugs, or changes in interpretation can alter recognized balances without any on-chain recourse. BRC-20 does not use smart contracts, which eliminates smart-contract exploit risk but also means the standard has no formal execution environment, no upgrade path, and limited composability. Bitcoin transaction fees spike during periods of high inscription activity, which can make ORDI transfers prohibitively expensive. Casey Rodarmor launched Runes in April 2024 as a more efficient Bitcoin-native fungible token standard, positioning it as a direct alternative to BRC-20. Sustained developer and exchange migration to Runes represents a long-term structural risk to ORDI's ecosystem relevance.
ORDI's 21,000,000 supply is fixed and fully minted. No additional tokens can be issued. No inflation exists, but no formal value-accrual framework, treasury, burn mechanism, or protocol revenue stream exists either. ORDI's market value is driven entirely by speculative demand and secondary-market trading activity. No vesting schedules, lockups, or concentrated insider allocations exist, but the minting distribution is not publicly mapped at the address level. Early minters who inscribed during the March 8–9, 2023 window may hold concentrations that could affect price if liquidated. No issuer-side data on holder concentration was produced at launch.
This Token Transparency Filing is provided for general informational purposes only and does not verify or warrant the accuracy of individual answers.