cryptosnif
SP500 tokenized stock (xStock) (SPYX)
Documentary contract0x90a2a4c76b5d8c0bc892a69ea28aa775a8f2dd48
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 SP500 tokenized stock (xStock) with symbol SPYX on the Ethereum network. The analysis is limited to the provided registry records and does not constitute an independent verification of current network operation, deployed bytecode, or active controllers.
Established facts
The Trust Wallet Ethereum integration record identifies the asset as SP500 tokenized ETF (xStock) with the ticker SPYX and contract address 0x90a2a4c76b5d8c0bc892a69ea28aa775a8f2dd48. The record specifies eighteen decimal places for amount representation. This metadata label indicates ERC20 compatibility and an active status within the wallet interface. The general ERC20 standard defines a fungible token interface including total supply queries, balance checks, direct transfers, and allowance mechanisms where a spender is authorized to transfer funds on behalf of the owner. The registry source is community-maintained and explicitly states that inclusion does not imply a partnership with the listed projects. The network context confirms the Ethereum blockchain identity with its native ETH symbol. These are documentary claims from the registry and do not represent independently verified issuer statements or live network observations.
Unknowns
Independent control structures, beneficial ownership, actual usage patterns, client adoption rates, precise supply distribution, concentration risks, liquidity depth, and complete incident history remain unverified. The registry description contains conflicting information regarding the operating platform and market data which has not been reconciled through independent observation. No deployed implementation rights, reserve backing, or security audit results have been established.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of independent verification means that the stated aims in the registry entry cannot be confirmed as operational reality. Users relying solely on this registry label lack assurance regarding the technical compliance, economic validity, or safety of the asset beyond the metadata classification.
Verdict
Operational strength remains unproven. The asset is unrated with zero percent scoring coverage across all dimensions. Critical missing evidence includes identity verification, supply confirmation, and control structure documentation. The dossier provides no basis for assigning a reliability score or endorsing the asset.
Evidence that would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence covering technology, usage, economics, governance, resilience, and liquidity would be required to alter this verdict. Calibration and editorial review following such verification would be necessary to assign a meaningful score.
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 SP500 tokenized ETF (xStock)
The pinned Trust Wallet Ethereum integration record names SP500 tokenized ETF (xStock) with symbol SPYX, contract 0x90a2a4c76b5d8c0bc892a69ea28aa775a8f2dd48 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: "SP500 tokenized ETF (xStock) (SPYX) is a cryptocurrency and operates on the Solana platform. SP500 tokenized ETF (xStock) has a current supply of 15,999.19889527. The last known price of SP500 tokenized ETF (xStock) is 662.57535897 USD and is up 0.48 over the last 24 hours. It is currently trading on 29 active market(s) with $2,070,018.72 traded over the last 24 hours. More information can be found at https://assets.backed.fi/products/sp500-xstock." 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.