Docs
Browse documentation

Start here

Product

Trust and safety

Reference

DocsProduct

Read-only discovery#

The live MVP Mainnet Beta begins with wallet verification and account reads. No token transaction is authorized during this stage.

Wallet discovery#

The browser discovers compatible Solana mainnet accounts through Wallet Standard. Public wallet access is active, and the interface requires the capabilities used for ownership proof and later transaction approval.

Ownership challenge#

The server creates a unique challenge containing:

  • the Afterlife mainnet verification purpose;
  • the complete wallet address;
  • a unique challenge ID;
  • a five-minute expiry; and
  • an explicit statement that the signature cannot authorize a transaction or move funds.

The wallet signs those text bytes. The server rejects an expired, used, mismatched, or cryptographically invalid challenge before creating or resuming a mainnet-beta session. Mainnet authorization is wallet-bound and short-lived, old bearer cookies are invalidated on re-verification, and challenge creation is rate-limited per wallet.

This message signature proves control of the public key for the session. It is not a burn approval.

Account scan#

After verification, the server reads at confirmed commitment:

  • classic SPL Token accounts;
  • Token-2022 accounts for visibility and exclusion;
  • raw balances and decimal precision;
  • account state and owner/close authority;
  • account rent lamports;
  • token metadata when the provider supports it; and
  • Jupiter metadata and prices for classic SPL mints and SOL;
  • independent DEX Screener market evidence; and
  • Jupiter route availability for eligible SELLABLE positions.

The scan returns the source slot and timestamp. Metadata is sanitized for presentation and a metadata-provider failure does not block account discovery.

Meaning of read-only#

Read-only discovery:

  • does not build, sign, or submit a token transaction;
  • cannot burn or transfer a token by itself; and
  • remains available even while irreversible execution is locked.

It is not private or trustless. Public wallet, account, and mint identifiers are sent to the RPC, metadata, price, and routing services needed for the scan. Missing, stale, conflicting, or unsafe provider data fails closed for conversion.

Continue to Asset exclusions and Security and privacy.