cryptosnif
IREN (Ondo Tokenized) (IRENon)
Documentary contract0x0b59fdb1a233a7477ea14061004b9dd776e73cb3
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 IREN (Ondo Tokenized) (IRENon) on the Ethereum network. The objective 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 Trust Wallet Ethereum integration record identifies Iren (Ondo Tokenized) with the symbol IRENon at contract address 0x0b59fdb1a233a7477ea14061004b9dd776e73cb3. The record specifies eighteen decimal places for amount representation and labels the entry as ERC20 and active. The community-maintained description states that IRENon is the Ondo Tokenized version of Iren, providing tokenholders economic exposure similar to holding IREN and reinvesting any dividends, while noting that additional restrictions apply. This information originates from a community-maintained registry where inclusion does not imply a direct partnership with listed projects. The general ERC-20 specification defines a standard interface for fungible tokens, including functions for total supply, balance checks, transfers, and allowances. An allowance permits a named spender to use a specified amount, which can be overwritten by subsequent approvals. These interface requirements describe what a conforming implementation should do, but the wallet label establishes no independently checked compliance or actual deployed implementation for this specific contract.
Unknowns
Independent verification of control, beneficial ownership, usage patterns, client adoption, total supply, concentration, liquidity, and complete incident history remains unverified. No live network observation was performed to confirm the deployed bytecode or current controllers. The documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The status of any additional restrictions mentioned in the registry description has not been examined.
Consequences
Because the operational strength remains unproven and scoring coverage is at zero percent, this asset holds an unrated status. Users relying solely on registry descriptions face uncertainty regarding the actual enforcement of restrictions and the reliability of the economic exposure claims. The lack of independent verification means that the stated purpose may not reflect the functional reality of the smart contract on the blockchain.
Verdict
IREN (Ondo Tokenized) is currently unrated with zero percent scoring coverage. The documentary evidence provides only registry claims and standard interface definitions, lacking the independent operational verification required for a safety or utility assessment. The asset's identity is documented, but its operational integrity and investment characteristics remain unknown.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to alter this verdict. Calibration and editorial review following such verification could establish the actual control structures, supply dynamics, and security posture of the contract.
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 Iren (Ondo Tokenized)
The pinned Trust Wallet Ethereum integration record names Iren (Ondo Tokenized) with symbol IRENon, contract 0x0b59fdb1a233a7477ea14061004b9dd776e73cb3 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: "IRENon is the Ondo Tokenized version of Iren, giving tokenholders economic exposure similar to holding IREN 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.