cryptosnif
McDonald's (Ondo Tokenized) (MCDon)
Documentary contract0x4c82c8cd9a218612dce60b156b73a36705645e3b
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Promise
This dossier examines the documented purpose and mechanisms of McDonald's (Ondo Tokenized) (MCDon) on the Ethereum network. The goal is to explain the stated aims of this tokenized asset based on available registry records, without verifying live network operation or investment outcomes.
Established facts
The primary documentary record identifies McDonald's (Ondo Tokenized) with the symbol MCDon and contract address 0x4c82c8cd9a218612dce60b156b73a36705645e3b on the Ethereum blockchain, which uses 18 decimal places for amount representation. This entry is labeled as ERC20 active within the Trust Wallet Assets registry. The registry description states that MCDon provides economic exposure similar to holding McDonald's stock and reinvesting dividends. It further explains that Ondo tokenized stocks allow non-US retail and institutional users globally to mint and redeem tokenized U.S. stocks and ETFs around the clock with access to traditional exchange liquidity, subject to additional restrictions. The general ERC-20 specification defines a standard interface for fungible tokens, including functions for total supply, balance checks, transfers, and allowances where a spender is authorized to use funds up to a set limit. These interface requirements describe what a conforming implementation should do, but the wallet label establishes no independently checked compliance or actual deployed implementation status.
Unknowns
Independent verification of control, beneficial ownership, actual usage, client adoption, total supply, concentration, liquidity, and complete incident history remains unverified. The registry scope notes that inclusion does not imply a direct partnership with listed projects and that additional token information is optional and unavailable on-chain. No live network observation was performed to validate the operational strength or security of the deployed bytecode.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The distinction between the generic ERC-20 interface standard and the specific implementation of this token means that claimed features like dividend reinvestment or global minting are attributed registry claims rather than independently established operational observations. Users relying on these descriptions assume risks associated with unverified issuer statements and potential gaps in on-chain data availability.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage due to missing essential criteria including identity verification, supply confirmation, and control assessment. No public admission or independent audit has been provided to support the registry claims.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence regarding control, supply, and usage would be required to move from an unrated status to a scored evaluation. Calibration and editorial review would follow the submission of such verified data.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Observable usage, token necessity and dependencies.
Inspect the evidence
Sources behind this analysis
Trust Wallet: captured Ethereum record for McDonald's (Ondo Tokenized)
The pinned Trust Wallet Ethereum integration record names McDonald's (Ondo Tokenized) with symbol MCDon, contract 0x4c82c8cd9a218612dce60b156b73a36705645e3b and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ERC20 and active. Its community-maintained description states: "MCDon is the Ondo Tokenized version of McDonald's, giving tokenholders economic exposure similar to holding MCD and reinvesting any dividends. Ondo tokenized stocks enable non-US retail and institutional users around the world to instantly mint and redeem tokenized U.S. stocks and ETFs, 24 hours a day, five days a week with full access to traditional exchange liquidity. Additional restrictions apply. Learn more at ondo.finance/global-markets." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. This dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification is separate from this token implementation. Treat the generic application family as a documentary contract subject; its economic niche and scoring criteria remain unclassified and unknown.
Inspect the primary source ↗Trust Wallet Assets: blockchains/ethereum/info/info.json (bbe582d25a22)
The pinned wallet blockchain-information file names the network Ethereum, symbol ETH, and lists its project website and explorer. That named network context accompanies token records in the repository's Ethereum subtree. This identifies the documented integration network without reproducing its operation. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Trust Wallet Assets: README.md (bbe582d25a22)
The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Ethereum ERC-20: pinned token interface specification
The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.