cryptosnif
Freeport-McMoRan (Ondo Tokenized) (FCXon)
Documentary contract0xeb08d539be0f6a6c90ea24276196e348f5688a02
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.
The documented promise
This dossier examines the Freeport-McMoRan (Ondo Tokenized) asset, identified by the symbol FCXon and the Ethereum contract address 0xeb08d539be0f6a6c90ea24276196e348f5688a02. The stated purpose is to provide token holders with economic exposure similar to holding FCX stock while reinvesting any dividends. This mechanism aims to bridge traditional commodity exposure with blockchain-based settlement. The registry entry labels this as an ERC20 token on the eip155:1 network. However, the registry description explicitly notes that additional restrictions apply. This document serves only as a documentary explanation of those stated aims. It does not imply that an independent audit has occurred or that the operational mechanisms function as described.
Established facts
The primary source for this identity is the pinned Trust Wallet Ethereum integration record. This record names Freeport-McMoRan (Ondo Tokenized) with the symbol FCXon and specifies 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record marks the entry as active and labeled ERC20. Its community-maintained description states that FCXon gives tokenholders economic exposure similar to holding FCX and reinvesting any dividends. Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim. These are not independently established issuer statements or operational observations. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification defines 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. 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. 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.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity and complete incident history remain unverified. The registry scope explicitly excludes brand-new tokens from submissions, meaning this source cannot provide an exhaustive inventory of recent launches. Additional token information is optional and unavailable on-chain. 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. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. 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. 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. No independently reviewed criterion observation admitted in this documentary lot covers identity, usage, token-role, supply, concentration, value-capture, control, security, governance, accountability, incidents, continuity or execution.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The registry entries are community-maintained and do not constitute independent verification. Inclusion does not imply a direct partnership with the listed projects. The absence of on-chain data means that supply, reserve, use, concentration and liquidity cannot be assessed from this source. The lack of live-network validation for the active status means the token's current operability is unknown. Without independent dated network observations, the claimed economic exposure and dividend reinvestment mechanics remain unproven. The distinction between the ERC-20 standard interface and the specific deployed contract remains unverified. Callers must handle a false transfer result according to the specification, but whether this contract implements such error handling is unknown. The attribution of claims to the registry prevents treating them as factual operational data. The dossier identifies only the documented subject; deployed bytecode, current controllers and network operation remain unverified.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. The calculated scores indicate a status of unrated with total null, partial null, and coverage zero. Missing essential criteria include identity, supply and control. Unknown criteria include identity, usage, token-role, supply, concentration, value-capture, control, security, governance, accountability, incidents, continuity and execution. Critical risks are empty due to lack of evidence. This verdict reflects the absence of independent verification rather than a negative assessment of the project itself. The documentary record provides a name and a claimed purpose, but no evidence of execution.
Evidence that would change it
Reproduced identity checks, independent dated network observations and criterion-specific evidence, followed by calibration and editorial review, would change this verdict. Verification of deployed bytecode against the claimed interface would establish technical compliance. Independent confirmation of controller permissions and supply distribution would address control and concentration unknowns. Live network transactions demonstrating the claimed dividend reinvestment mechanism would validate the economic purpose. Community-submitted updates to the registry would need to be corroborated by on-chain data to move beyond documentary claims. The exclusion of brand-new tokens from the registry implies that newer implementations might require different verification pathways. Copyright and related rights are waived under CC0, allowing for open verification efforts. The MIT license on scripts and documentation facilitates tooling development for independent analysis. No public admission of operational status exists, so external verification is the sole path to rating.
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 Freeport-McMoRan (Ondo Tokenized)
The pinned Trust Wallet Ethereum integration record names Freeport-McMoRan (Ondo Tokenized) with symbol FCXon, contract 0xeb08d539be0f6a6c90ea24276196e348f5688a02 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: "FCXon is the Ondo Tokenized version of Freeport-McMoRan, giving tokenholders economic exposure similar to holding FCX and reinvesting any dividends. Additional restrictions apply. Learn more at https://ondo.finance/gm." 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.