cryptosnif
Index Cooperative (INDEX)
Documentary contract0x0954906da0bf32d5479e25f46056d22f08464cab
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
Index Cooperative (INDEX) presents itself as a token governing the global community creating and maintaining crypto index products. This purpose is drawn directly from the Trust Wallet registry entry for contract 0x0954906da0bf32d5479e25f46056d22f08464cab on the Ethereum network. The registry labels this entry as ERC20 active, indicating a classification within the wallet software rather than an operational verification. We examine this stated aim to understand the project's declared intent without assuming its technical or economic reality has been independently confirmed.
Established documentary facts
The primary source for this dossier is the pinned Trust Wallet Ethereum integration record. It identifies the asset by name Index, symbol INDEX, and contract address 0x0954906da0bf32d5479e25f46056d22f08464cab with 18 decimal places. Decimal places refer to how amounts are represented in code and do not measure supply or value. The record sits within the Ethereum blockchain context, identified by symbol ETH in the wallet's network information file. The Trust Wallet Assets README clarifies that this is a community-maintained registry where anyone can submit assets. Inclusion does not imply a partnership with the listed projects, and brand-new tokens are explicitly excluded from submissions. Therefore, this source provides a documentary snapshot of a claimed identity, not a live-network validation of deployment bytecode, controllers, or current operation.
Technical interface context
The registry classifies the token as ERC20. The ERC-20 specification defines a standard interface for fungible tokens in smart contracts. It outlines functions for reading total supply and balances, executing transfers, and managing allowances. An allowance permits a named spender to use a specified amount of tokens; repeated approvals overwrite previous allowances. The standard requires handling false transfer results and emits Transfer and Approval events. Name, symbol, and decimal metadata are optional under this specification. Labeling a contract as ERC20 in a registry establishes no independently checked compliance, actual deployed implementation, controller permissions, or security posture. No token transaction was performed in this review to verify if the contract at 0x0954906da0bf32d5479e25f46056d22f08464cab conforms to these requirements.
Unknowns and limitations
Several critical aspects remain unverified due to the documentary nature of this review. Independent control over the contract, beneficial ownership, actual usage by users, and client adoption are unknown. The token supply, concentration of holdings, liquidity depth, and complete incident history have not been observed. The registry status is a metadata label with no live-network validation. Consequently, we cannot confirm if the contract exists, who controls it, or if it functions as described. The scoring coverage is 0%, resulting in an unrated status because essential criteria such as identity, supply, and control lack evidence.
Consequences of the gap
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Relying solely on registry entries risks conflating a claimed identity with operational reality. Without independent dated network observations, there is no basis to assess the safety, utility, or economic viability of the INDEX token. Users or analysts must treat the registry description as an attributed claim from the community-maintained source, not as an issuer statement or verified fact.
Verdict and path forward
Operational strength remains unproven. The dossier assigns an unrated verdict with 0% scoring coverage. To change this assessment, reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required. These would need to be followed by calibration and editorial review to move beyond the current documentary limits.
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 Index
The pinned Trust Wallet Ethereum integration record names Index with symbol INDEX, contract 0x0954906da0bf32d5479e25f46056d22f08464cab 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: "A token governing the global community creating and maintaining the best crypto index products" 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.