cryptosnif
Request Network (REQ)
Documentary contract0x8f8221afbb33998d8584a2b05749ba73c37a938a
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 Request Network (REQ) on the Ethereum network. The goal is to explain the stated aims of this token based on available registry records, without assuming independent verification of its operation or safety.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Request with the symbol REQ and contract address 0x8f8221afbb33998d8584a2b05749ba73c37a938a. This record specifies 18 decimal places for amount representation. The community-maintained description labels the entry as ERC20 and active. It states that Request Network is an Ethereum-based decentralized payment system where anyone can request a payment and receive money through secure means. These statements are attributed registry claims from the wallet project's own integration registry, maintained with community submissions. They are not independently verified issuer statements or operational observations. 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 notes that callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. 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 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 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. The documentary mechanism alone cannot establish actual network behavior or investment outcomes. 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.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of live-network validation means the active status is merely a metadata label. No public admission of operational status exists. The dossier attributes the token-specific description to the captured Trust Wallet entry, without adopting promotional claims. The stated purpose is a useful documentary explanation, without implying an independent audit has occurred.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. 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 include identity, usage, token-role, supply, concentration, value-capture, control, security, governance, accountability, incidents, continuity and execution. No critical risks have been identified due to lack of evidence.
What would change it
Reproduced identity checks, independent dated network observations and criterion-specific evidence, followed by calibration and editorial review, would be required to move beyond this unrated status. Current market, return, supply, performance, adoption or ownership claims are absent. No incidents or completed audits are reported. State 0% scoring coverage and unrated status; no public admission. Avoid adding numerical examples or dates absent from these summaries. Preserve critical client end-of-support caveats where supplied. Use connected prose. Registry dossier brief version 2: attribute the token-specific description to the captured Trust Wallet entry, without adopting promotional claims. Explain the general ERC-20 transfer and allowance interface separately and cite its specification; never assume this contract implements it. Give the stated purpose and concrete research questions for this token. Keep the unknowns and unrated verdict brief. Do not repeat the same missing-evidence list in several sections. Define only terms supported by the supplied summaries. The purpose is a useful documentary explanation, without implying an independent audit has occurred.
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 Request
The pinned Trust Wallet Ethereum integration record names Request with symbol REQ, contract 0x8f8221afbb33998d8584a2b05749ba73c37a938a 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 Request Network itself is an Ethereum-based decentralized payment system where anyone can request a payment and receive money through secure means." 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.