cryptosnif
EN ↗
EnglishFrançaisPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Application / CT-UOS-001

Ultra (UOS)

Ethereum · Token contract · Documentation reviewed

Documentary contract0xd13c7342e1ef687c5ad21b27c2b65d772cab5c8c

The verdict

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 evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-06Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

Promise

This dossier examines the documented purpose and mechanisms of Ultra (UOS) on the Ethereum network. The goal is to explain the stated aims of the project as recorded in community-maintained registries, without implying that an independent audit or operational verification has occurred.

Established facts

The pinned Trust Wallet Ethereum integration record identifies Ultra Token with the symbol UOS and contract address 0xd13c7342e1ef687c5ad21b27c2b65d772cab5c8c. The record specifies four decimal places for amount representation. This metadata label does not measure supply or value. The registry description states that Ultra describes itself as a blockchain-based PC game distribution platform. It claims to provide opportunities for gamers and developers by allowing users to buy, play, resell used games and items, and earn money through participation. These statements are attributed registry claims from a community-maintained source. They 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 outlines 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 this standard. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply, or security. The active status in the registry is a metadata label with no live-network validation. The Trust Wallet Assets README confirms this is a community-maintained registry where anyone can submit assets. Inclusion does not imply a direct partnership with listed projects. It explicitly excludes brand-new tokens from submissions, meaning it cannot provide an exhaustive inventory of recent launches. Scripts and documentation use the MIT license. The network context identifies Ethereum, symbol ETH, with its project website and explorer. This source is the wallet project's own integration registry. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. 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 criterion observation admitted in this documentary lot covers identity, usage, token-role, supply, concentration, value-capture, control, security, governance, accountability, incidents, continuity, or execution. The scoring coverage is zero percent. The asset remains unrated. Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.

Consequences

Because the registry entries are community-submitted documentary claims rather than independently verified issuer statements, the described ecosystem functions remain theoretical until observed on-chain. The distinction between the generic ERC-20 interface requirements and the specific implementation of this contract is critical. Without live-network validation, the active status label provides no assurance of operational integrity. The absence of essential evidence regarding identity, supply, and control prevents any assessment of operational strength.

Verdict

Operational strength remains unproven. The asset is unrated with zero percent scoring coverage. The provided summaries attribute the token-specific description to the captured Trust Wallet entry without adopting promotional claims. The general ERC-20 transfer and allowance interface is explained separately based on its specification. No current market, return, supply, performance, adoption, or ownership claims are made. No incidents or completed audits are invented. The verdict reflects the lack of independent verification rather than a judgment of fraud or safety.

What would change it

Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move beyond this documentary status. Calibration and editorial review following such verification could alter the unrated status. Until then, the scope remains limited to the supplied original summaries and their exact code or documentation versions.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Observable usage, token necessity and dependencies.

03 / Evidence

Inspect the evidence

Sources behind this analysis

Trust Wallet: captured Ethereum record for Ultra Token

The pinned Trust Wallet Ethereum integration record names Ultra Token with symbol UOS, contract 0xd13c7342e1ef687c5ad21b27c2b65d772cab5c8c and 4 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: "Ultra describes itself as a blockchain-based, PC game distribution platform designed to provide both gamers and game developers with new opportunities. It consists of an ecosystem where gamers can, on top of buying and playing games, resell their used games and items, and earn money through their participation in Ultra." 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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 98e50e863baf9b3c29105aaa57f36678e4d7544e8fc4d6bf70ae5b5ece72be53

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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 5bf228bbcd577440dc00e5b783b680b0cfdf14504dc9d8b89340ba88d9e95502

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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 51fc8f690972c850271ca0a6086516eae5ed411e94982fcae6534a4d08fccd73

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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 50d0bdc535ed8987ac5c124cb5f9c39606806c97e909aae66ef4b747dd9c93dd

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation