Provide a concise narrative that clearly states each of (a)–(e) below.
Monero is designed around private and censorship-resistant digital payments, and its public materials contrast that objective with transparent blockchains where transaction participants and activity can be linked and traced.
(Source: What is Monero (XMR)?, About Monero)
The cited materials describe Monero as an open-source community project with no company or CEO, operated through volunteers, community-funded contributors, workgroups, and a community crowdfunding system that funds proposals and maintains a General Fund for project support.
(Source: FAQ, Workgroups, CCS - Community Crowdfunding System (CCS), GitHub - monero-project/monero)
At a high level, Monero is a decentralized peer-to-peer network whose privacy model relies on Stealth Addresses, Ring Signatures, and RingCT, while consensus and issuance rely on proof-of-work mining, roughly 2-minute block times, and ongoing block rewards.
(Source: What is Monero (XMR)?, GitHub - monero-project/monero, Monero Technical Specification)
Publicly, XMR functions as electronic cash for fast, inexpensive payments, and the protocol uses block rewards plus transaction fees to compensate miners who secure the network.
(Source: What is Monero (XMR)?, FAQ About Monero)
The cited materials indicate that Monero does not rely on a corporate operator. Instead, workgroups manage most project functions, the Core Team stewards infrastructure where centralization cannot be avoided, and protocol development proceeds through open contribution, pull requests, code review, and public coordination channels.
(Source: FAQ, Workgroups, GitHub - monero-project/monero)
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 |
|---|---|---|---|
Riccardo Spagni | DAO | Core Team member; former Lead Maintainer (stepped down 2019) | Active in cryptocurrency since 2011; founded GlobeE, a multi-currency payment processor, in 2017; prior software development background in import/export industry. |
Jeremie Dubois-Lacoste | DAO | Core Team member; General Fund wallet administrator; primary release binary signer | PhD in computer science with academic expertise in combinatorial systems and optimization algorithms; prior academic research career before entering cryptocurrency full-time. |
Francisco Cabañas | DAO | Core Team member (original) | Active in cryptocurrency since 2011; holds a PhD in physics; extensive business background including non-profit experience. |
Blockworks note: No formal DAO or onchain governance leadership body exists for Monero. The Core Team functions as the closest equivalent to a governance leadership body: it is a closed volunteer group that stewards infrastructure, domains, GitHub repositories, the General Fund wallet, and release engineering. Core Team members are listed below. |
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 formal DAO exists for Monero. No DAO-specific IP ownership or control applies.
No formal DAO was identified in cited materials. Publicly observable governance instead appears to run through workgroups, Core Team stewardship over domains, the website, and GitHub repositories, and open-source contributor processes rather than a tokenholder voting body or legal-wrapper DAO.
(Source: FAQ, Workgroups, GitHub - monero-project/monero)
No formal DAO exists for Monero and there is no protocol treasury or issuer-controlled revenue stream. XMR holders have no protocol-level revenue rights or treasury claims. The CCS is funded by community donations allocated to specific contributor proposals; those funds are not controlled by or claimable by general XMR holders. The General Fund is stewarded by the Core Team for project expenses and is likewise not a tokenholder entitlement. Value accrual to XMR holders is a function of the programmatic mining emission schedule: a main emission that produced approximately 18.132 million XMR by May 2022, followed by a permanent tail emission of 0.6 XMR per approximately 2-minute block. No governance mechanism exists by which holders can vote on distributions or redirect fees.
(Source: FAQ, CCS - Community Crowdfunding System (CCS), GitHub - monero-project/monero)
No formal DAO exists for Monero. No dissolution or wind-up mechanism applies.
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.
No primary foundation exists for Monero.
Not applicable. No primary foundation exists for Monero.
Not applicable. No primary foundation exists for Monero.
Not applicable. No primary foundation exists for Monero.
Not applicable. No primary foundation exists for Monero.
Not applicable. No primary foundation exists for Monero.
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.
No primary DevCo exists for Monero.
Not applicable. No primary DevCo exists for Monero.
Not applicable. No primary DevCo exists for Monero.
Not applicable. No primary DevCo exists for Monero.
Not applicable. No primary DevCo exists for Monero.
Not applicable. No primary DevCo exists for Monero.
Disclose launch and initial supply details in a single initial allocation schedule covering the token's launch.
The cited materials do not describe a one-time TGE issuance, lockup, or unlock schedule. Instead, Monero went live on 18 April 2014 with no premine, no instamine, no token sale, and no presale, and supply entered circulation through mined block rewards.
(Source: Monero Technical Specification, About Monero)
The reviewed public launch model points to miners as the initial recipient category: Monero gives the full block reward to miners, and public sources do not describe a launch allocation to a foundation, DevCo, or development treasury.
(Source: About Monero, FAQ)
No fixed initial offering price was identified in cited materials because the same sources describe no token sale or presale at launch.
(Source: Monero Technical Specification, About Monero)
The project publicly labels the asset as XMR.
(Source: What is Monero (XMR)?)
Public sources describe a fixed emission rate rather than a hard fixed cap: the main emission produced about 18.132 million coins by the end of May 2022, tail emission now produces 0.6 XMR per 2-minute block, and the technical specification describes max supply as about 18.293 million XMR plus 0.6 XMR per 2 minutes.
(Source: About Monero, Monero Technical Specification, FAQ)
No issuer-run vesting or release schedule was identified in cited materials. The public record instead describes mining-based issuance and an ongoing block reward regime.
(Source: Monero Technical Specification, FAQ)
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: The cited materials describe Monero as a fair launch with no premine, no instamine, no token sale, and no presale, and they describe issuance through mining and block rewards rather than an allocation-based distribution event. On that reviewed public record, no Monero TGE-linked airdrop was identified in cited sources.
(Source: About Monero, Monero Technical Specification, FAQ)
No public data found in cited sources for any nonpublic address-level airdrop disclosure because no airdrop program was identified in the reviewed verified public record.
(Source: About Monero, Monero Technical Specification, FAQ)
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: Monero has no market maker agreements or token loans. No issuing entity exists with legal standing to enter such arrangements on behalf of the protocol.
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: Monero has no project-side CEX or DEX listing agreements, no token allocations for listings, no listing lockups, and no native-token listing fees. No issuing entity exists to negotiate such arrangements; exchanges list XMR on their own initiative.
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 token sale or presale was identified in cited materials.
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").
The reviewed public incident record identified a 2023-09-01 incident affecting the Community Crowdfunding System (CCS) main wallet.
(Source: Community Crowdfunding System wallet incident)
The public notice states that during a routine transfer the project discovered that the CCS main wallet had been drained, but it also states that the source of the breach had not yet been ascertained.
(Source: Community Crowdfunding System wallet incident)
The notice reports that 2,675.73 XMR, described as the entire CCS main-wallet balance, was drained, while the secondary contributor-payment wallet remained untouched with about 244 XMR.
(Source: Community Crowdfunding System wallet incident)
The public response stated that the General Fund would be used to cover the loss and that contributors with in-progress CCS proposals would remain unaffected.
(Source: Community Crowdfunding System wallet incident)
At the time of the published notice, an internal investigation was ongoing. The CCS wallet incident did not affect the native XMR token supply, the Monero protocol, or individual tokenholder balances. The drained funds were community-donated CCS contributions held in a project-operated wallet, not protocol-controlled resources or user custody. As of May 2025, no exploit affecting the native XMR token supply, protocol consensus layer, or tokenholder balances has been identified in the public record.
(Source: Community Crowdfunding System wallet incident)
The reviewed public notice links to a related GitHub discussion for further details.
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?
Impact of regulatory change on TGE and listings: Monero's TGE-equivalent launch is historical rather than pending, because cited materials describe a 2014 fair launch with no token sale or presale. Even so, evolving reporting and compliance rules remain relevant to listing and service availability because Monero is actively discussed in a public regulatory submission about privacy-preserving networks, and public Monero FAQs state that users acquire XMR through exchanges operating under different compliance models.
(Source: About Monero, Monero Technical Specification, Monero Policy Working Group (MPWG), FAQ)
Entity-level regulatory impact: The cited materials do not identify a company, CEO, foundation, or DevCo running Monero. They instead describe The Monero Project website as a loose collective, state that the website itself does not store, sell, buy, send, or receive Monero, and show that workgroups plus the Core Team steward infrastructure and administer CCS and General Fund donation surfaces. As a result, regulatory or legal pressure on website operators, repositories, hosting, or donation and escrow infrastructure could still affect project coordination and public-facing services even without a conventional issuer entity.
(Source: FAQ Legal | Monero - secure, private, untraceable, Workgroups, A message from the Core Team about the General Fund)
Tokenholder tax treatment: The IRS states that digital assets are property, not currency, that income from digital assets is taxable, that digital-asset transactions may need to be reported on federal returns, and that taxpayers must maintain sufficient records. Tokenholders therefore need to understand their own transaction history and tax obligations for holding, receiving, mining, or disposing of XMR.
(Source: Digital assets)
Jurisdictional & user access restrictions: The cited materials do not identify a project-imposed jurisdiction blacklist in the materials reviewed here, but they do state that Monero is bought through exchanges with different compliance models, including KYC and non-KYC venues. That means user access can vary by venue, jurisdiction, and regulatory posture even where the protocol itself is decentralized.
(Source: FAQ, What is Monero (XMR)?)
Bugs and design flaws: The cited materials show that Monero can still face material privacy or implementation bugs. The 2023 10-block-old decoy-selection post-mortem rated the issue HIGH severity and said affected wallet versions lost sender anonymity for spends exactly 10 blocks old, and the August 26, 2025 find_and_save_rings() post-mortem rated a later wallet privacy bug HIGH severity when using an untrusted remote daemon, said affected versions were v0.12.0.0 to v0.18.4.1, and recommended updating to v0.18.4.2. Public Monero FAQs also show that protocol changes and network upgrades have historically been used to introduce privacy and consensus improvements, which means holders depend on software correctness and upgrade coordination over time.
(Source: Post-Mortem of 10-Block-Old Decoy Selection Bug, Post-Mortem of find_and_save_rings() bug, FAQ)
Security measures and their limitations: The cited materials identify a Vulnerability Response Process and HackerOne intake, an open Research Lab, contributor testing and code review before merges, and signed-hash verification guidance for software downloads, including Monero documentation that says core developers sign the released-binary hash list and identifies BinaryFate as a developer who signs releases. Those measures improve disclosure, review, and release integrity, but the same public sources also show their limits: high-severity privacy bugs still reached users in 2023 and 2025, and download-verification guidance only helps when users actually verify binaries before use.
(Source: Improving Monero, Monero Research Lab (MRL), GitHub - monero-project/monero, Verifying Monero Binaries Signature, Post-Mortem of 10-Block-Old Decoy Selection Bug, Post-Mortem of find_and_save_rings() bug)
Critical economic assumptions: Publicly, Monero's economic model relies on continued demand for XMR, miners continuing to secure the network, and tail emission plus transaction fees remaining sufficient to incentivize mining. The cited materials also emphasize that Monero's value depends on buyers being willing to buy it, so reduced demand or weaker miner participation could pressure market value, liquidity, or security assumptions.
(Source: FAQ, About Monero, Monero Technical Specification)
Governance control over monetary policy and rewards: The cited materials do not identify an issuer or tokenholder voting body that can unilaterally rewrite monetary policy. Instead, public governance appears to run through workgroups, Core Team stewardship, and community-coordinated network upgrades, and the public record shows that consensus changes and proof-of-work changes have historically been introduced through upgrade cycles. That means future monetary or reward changes would depend on community coordination and software adoption rather than on issuer-side commitments, which can create execution and governance uncertainty for holders.
(Source: FAQ, Workgroups, Monero Technical Specification)
This Token Transparency Filing is provided for general informational purposes only and does not verify or warrant the accuracy of individual answers.
