cryptosnif
Reserve Rights Token (RSR)
Documentary contract0x320623b8e4ff03373931769a31fc52a4e78b5d70
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.
Promised scope
This dossier examines the documented purpose and mechanisms of Reserve Rights Token (RSR) on the Ethereum network. The analysis is limited to the provided registry summaries and does not constitute an independent operational verification, audit, or investment recommendation.
Established facts
The Trust Wallet Ethereum integration record identifies the asset as Reserve Rights with the symbol RSR and contract address 0x320623b8e4ff03373931769a31fc52a4e78b5d70. The record specifies 18 decimal places for amount representation and labels the entry as ERC20 and active. The community-maintained description states the goal is to create accessible and robust currency. This label establishes a documentary identity within the wallet project's registry but does not verify deployed bytecode, current controllers, or live network operation. 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 funds up to a set limit. A repeated approval overwrites that amount. These interface requirements describe what a conforming implementation should do, but the wallet ERC20 label alone establishes no independently checked compliance or actual deployed implementation. The Ethereum network context provides the named environment for this integration, identified by the symbol ETH. The Trust Wallet Assets README describes a community-maintained registry where anyone can submit assets, noting that inclusion does not imply a direct partnership with listed projects.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. No live network observation was performed. The active status is a metadata label with no validation. No deployment bytecode, controller permissions, security audit, or investment return has been established. The specific token implementation details beyond the registry label are unknown.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The distinction between the generic ERC-20 specification and this specific token's implementation remains unverified. Without independent observation, the stated aims in the registry description cannot be confirmed as operational reality. The lack of verified data prevents any assessment of safety, utility, or economic viability.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. Critical missing evidence includes identity verification, supply confirmation, and control structure documentation. The dossier serves as a documentary explanation of registry claims without implying an independent audit has occurred.
Evidence that would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move from an unrated status to a scored assessment. Calibration and editorial review would follow the submission of such verified data. Current registry entries alone are insufficient for a definitive verdict on operational integrity or investment merit.
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 Reserve Rights
The pinned Trust Wallet Ethereum integration record names Reserve Rights with symbol RSR, contract 0x320623b8e4ff03373931769a31fc52a4e78b5d70 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 Reserve team's goal is to make the most accessible, economically strongest, and most robust-to-attack currency." 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.