cryptosnif
Usual USD (USD0)
Documentary contract0x73a15fed60bf67631dc6cd7bc5b6e8da8190acf5
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 Usual USD (USD0) on the Ethereum network. The objective is to explain the stated aims of this asset as recorded in community-maintained registries, without verifying its live operation or investment outcomes.
Established facts
The Trust Wallet Ethereum integration record identifies Usual USD with the symbol USD0 at contract address 0x73a15fed60bf67631dc6cd7bc5b6e8da8190acf5. This entry specifies 18 decimal places for amount representation and labels the token as ERC20 and active. The registry description states that USD0 is a stablecoin fully backed 1:1 by Real-World Assets like US Treasury Bills. It claims to provide a stable, secure asset independent of traditional banking systems, fully transferable, and accessible within the DeFi ecosystem. As the core stability asset of Usual, it supports transparency by maintaining real-time reserves. These statements are attributed registry claims, not independently established issuer statements or operational observations. The general ERC-20 specification defines a standard interface for fungible tokens, including total supply reads, balance checks, transfers, and allowances. An allowance permits a named spender to use a specified amount, which can be overwritten by repeated approval. Name, symbol, and decimal metadata are optional in this standard. A wallet ERC20 label establishes no independently checked compliance or actual deployed implementation. The Ethereum network context accompanies these token records, identifying the blockchain environment without validating its operation.
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 active status is a metadata label with no live-network validation. No token transaction was performed in this review.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The registry scope excludes brand-new tokens from submissions and does not imply a direct partnership with listed projects. Inclusion does not guarantee exhaustive inventory or operational verification. Any economic niche and scoring criteria remain unclassified and unknown based on current evidence.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. Critical missing essential data includes identity, supply, and control verification.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required. Calibration and editorial review must follow any new verification to update the status.
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 Usual USD
The pinned Trust Wallet Ethereum integration record names Usual USD with symbol USD0, contract 0x73a15fed60bf67631dc6cd7bc5b6e8da8190acf5 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: "USD0 is a stablecoin fully backed 1:1 by Real-World Assets (RWA) like US Treasury Bills. It provides users with a stable, secure asset that is independent of traditional banking systems, fully transferable, and accessible within the DeFi ecosystem. As the core stability asset of Usual, USD0 supports transparency and security by maintaining real-time reserves, offering a non-fractional, reliable alternative to stablecoins like USDT and USDC." 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.