cryptosnif
Memento (DEXTF)
Documentary contract0x5f64ab1544d28732f0a24f4713c2c8ec0da089f0
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.
The documented promise
This dossier examines Memento (DEXTF), identified by the asset identity dextf-wallet-ethereum on the eip155:1 network. The stated purpose is to serve as a governance and incentive mechanism for usage, upgrades, and potential changes to the protocol. This description originates from a community-maintained registry entry and represents a project claim rather than an independently verified operational statement. The scope of this review is limited to the documentary record provided; it does not constitute an independent audit or verification of current controllers, deployed bytecode, or live network behavior.
Established facts
The primary source for this dossier is a pinned Trust Wallet Ethereum integration record. This document names DEXTF Token with the symbol DEXTF, assigns the contract address 0x5f64ab1544d28732f0a24f4713c2c8ec0da089f0, and specifies 18 decimal places. Decimal places refer to the granularity of amount representation and do not measure total supply or market value. The record labels the entry as ERC20 and active. The term ERC-20 refers to a standard interface for fungible tokens in smart contracts, defining functions such as totalSupply, balanceOf, transfers, and allowances. An allowance allows a named spender to use a specified amount of tokens on behalf of the owner. The general ERC-20 specification is separate from any specific token implementation. The wallet project identifies the network context as Ethereum, providing a project website and explorer link. The registry itself is community-maintained, allowing anyone to submit assets, though inclusion does not imply a direct partnership with listed projects. The active status is a metadata label without live-network validation.
Unknowns
Operational strength remains unproven due to a lack of independent verification. Several critical factors remain unknown. Independent control over the contract and beneficial ownership are unverified. Actual usage, client adoption, supply distribution, concentration of holdings, and liquidity levels have not been observed. A complete incident history is absent. The registry description contains claims about economic niche and partnerships that are attributed to the project but not established by this dossier. No deployed implementation details, rights, or safety mechanisms were checked. The generic application family of ERC-20 tokens does not guarantee compliance or security for this specific contract. No token transaction was performed during this review.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The reliance on a community-maintained registry means that project descriptions are documentary claims, not independently verified issuer statements. The absence of live-network observation prevents confirmation of whether the contract functions as described or if it operates under different conditions. Users cannot infer safety, performance, or reliability from the registry label alone. The distinction between the general ERC-20 standard and the specific implementation of this token remains unbridged by evidence.
Verdict
Memento (DEXTF) is unrated with 0% scoring coverage. The calculated scores indicate no data points for technology, usage, economics, governance, resilience, or liquidity dimensions. Essential criteria including identity, supply, and control are missing. The verdict reflects the limitation of the available evidence to documentary records only. No public admission of operational status or independent audit results exists. The dossier serves as a documentary explanation of the stated aims, without implying that an independent audit has occurred or that the project meets any safety or performance standards.
Evidence that would change it
The verdict would change if reproduced identity checks confirmed the contract address and deployment details. Independent dated network observations would be required to verify actual usage, control, and incident history. Criterion-specific evidence covering supply, concentration, and security would need to be admitted. Calibration and editorial review based on these new data points would allow for a re-evaluation of the scoring coverage and final rating. Until such evidence is provided, the unrated status and identification of unknowns remain valid.
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 DEXTF Token
The pinned Trust Wallet Ethereum integration record names DEXTF Token with symbol DEXTF, contract 0x5f64ab1544d28732f0a24f4713c2c8ec0da089f0 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 DEXTF token is an ERC20 token built on the Ethereum blockchain designed to be used as a governance and incentive mechanism for usage, upgrades and potential changes to the protocol." 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.