cryptosnif
Origin Dollar (OUSD)
Documentary contract0x2a8e1e676ec238d8a992307b495b45b3feaa5e86
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.
Examined promise
This dossier examines the documented purpose and mechanisms of Origin Dollar (OUSD) on the eip155:1 network. The stated aim is to provide a mechanism where users can earn yield while holding the asset in their wallet. This review focuses strictly on the supplied original summaries, their exact code or documentation versions, and historical limits. It does not verify current market conditions, returns, supply, performance, adoption, or ownership claims. The goal is to explain the stated purpose and concrete research questions for this token based solely on available documentary evidence.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Origin Dollar with the symbol OUSD and contract address 0x2a8e1e676ec238d8a992307b495b45b3feaa5e86. The record specifies 18 decimal places, which concern amount representation and do not measure supply or value. The entry is labeled ERC20 and active within the registry. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts, including 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 requires callers to handle false transfer results 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. 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 states that 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 explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The 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. 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. The supplied original summaries describe pinned primary documentation and software. No live network observation was performed.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The community-maintained description states: "The first stablecoin that earns a yield while it’s still in your wallet" 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. The absence of independent verification means that any assumed functionality or yield generation remains hypothetical until proven by external evidence.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. No public admission of operational status or independent audit has been made. The calculated scores indicate a status of unrated with zero coverage across all dimensions including technology, usage, economics, governance, resilience, and liquidity. Missing essential criteria include identity, supply, and control. Unknown criteria span identity, usage, token-role, supply, concentration, value-capture, control, security, governance, accountability, incidents, continuity, and execution. This verdict reflects the lack of independent operational verification rather than a judgment on the project's inherent safety or fraudulence.
Evidence that would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence, followed by calibration and editorial review, would be required to alter this verdict. Specifically, proof of deployed bytecode matching the documented contract, verification of controller permissions, confirmation of supply mechanics, and evidence of actual user adoption or yield distribution would shift the assessment from unrated to rated. Without such independent verification, the dossier remains limited to the provided documentary records.
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 Origin Dollar (OUSD)
The pinned Trust Wallet Ethereum integration record names Origin Dollar (OUSD) with symbol OUSD, contract 0x2a8e1e676ec238d8a992307b495b45b3feaa5e86 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: "The first stablecoin that earns a yield while it’s still in your wallet" 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.