cryptosnif
EN ↗
EnglishFrançaisPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Application / CT-METAX-001

Meta tokenized stock (xStock) (METAX)

Arbitrum One · Token contract · Documentation reviewed

Documentary contract0x96702be57cd9777f835117a809c7124fe4ec989a

The verdict

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 evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-06Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

Promise

This dossier examines the documented purpose and mechanisms of Meta tokenized stock (xStock), identified by the symbol METAX on the Arbitrum network. The scope is limited to verifying the claims found in community-maintained registry entries against the technical standards they reference. We do not assess current market performance, investment returns, or live operational safety. The goal is to establish what the documentation states versus what remains unverified.

Established facts

The pinned Trust Wallet entry names Meta tokenized stock (xStock), symbol METAX, with documentary address 0x96702be57cd9777f835117a809c7124fe4ec989a on eip155:42161. It records 18 decimal places, which concern amount representation rather than supply or value. The entry labels the asset ARBITRUM and active. These are captured registry labels; current deployment, control and conformance with any token interface remain independently unverified.

Unknowns

Independent control structures, beneficial ownership, actual usage patterns, client adoption rates, verified supply distribution, concentration risks, liquidity depth, and complete incident history remain unverified. No deployed bytecode analysis or live network observation was performed. The active status in the registry is a metadata label without live-network validation. Documentary address matching does not establish current program behavior, deployed control logic, or safety guarantees. The dossier cannot confirm if the token operates as described or if the economic niche aligns with the registry claims.

Consequences

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Relying solely on registry descriptions risks conflating promotional claims with operational reality. Without independent verification of control and security, users cannot assess the integrity of the asset or the validity of the stated economic metrics. The lack of scoring coverage means no risk profile can be assigned based on current evidence.

Verdict

Operational strength remains unproven. The asset is unrated with 0% scoring coverage. The absence of independent verification prevents any conclusion regarding safety, utility, or financial viability. The documented subject is identified, but its operational reality is unknown.

What would change it

Reproduced identity checks confirming the contract address matches the claimed project. Independent dated network observations verifying actual transaction flows and control permissions. Criterion-specific evidence covering identity, supply, control, and security. Calibration and editorial review following the collection of these independent proofs would allow for a scored assessment. Until then, the status remains unrated due to missing essential criteria.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Observable usage, token necessity and dependencies.

03 / Evidence

Inspect the evidence

Sources behind this analysis

Trust Wallet: captured Arbitrum record for Meta tokenized stock (xStock)

The pinned Trust Wallet Arbitrum integration record names Meta tokenized stock (xStock) with symbol METAX, documentary address 0x96702be57cd9777f835117a809c7124fe4ec989a and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ARBITRUM and active. Its community-maintained description states: "Meta tokenized stock (xStock) (METAX) is a cryptocurrency and operates on the Solana platform. Meta tokenized stock (xStock) has a current supply of 1,000. The last known price of Meta tokenized stock (xStock) is 769.51285738 USD and is up 1.36 over the last 24 hours. It is currently trading on 26 active market(s) with $3,617,932.72 traded over the last 24 hours. More information can be found at https://assets.backed.fi/products/meta-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. The dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. The general ERC-20 specification is separate from this token implementation.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 497848538fde0b852248f604a9d1474e782a003e9a1e458c1442971e081297a8

Trust Wallet: pinned Arbitrum directory context

The pinned Trust Wallet arbitrum network-context record identifies the community registry directory for Arbitrum. This supplies documentary network context for entries in the same pinned directory. Promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: b36691383b87cd265a58a3eae6fa8fc8f3719c8f5c80fc35670f3c78719fe386

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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 51fc8f690972c850271ca0a6086516eae5ed411e94982fcae6534a4d08fccd73

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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 50d0bdc535ed8987ac5c124cb5f9c39606806c97e909aae66ef4b747dd9c93dd

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation