Access

Holder Access

Access is based on the connected wallet's MYTHOS balance on Base. The minimum access tier starts at 5,000,000 MYTHOS.

Minimum Hold

The access gate checks the connected wallet's MYTHOS ERC-20 balance on Base. The first tier starts at 5,000,000 MYTHOS. Higher balances unlock higher daily quota, but the wallet still has to sign in before protected routes respond.

Important

Only the wallet balance matters for access. Holding MYTHOS in another wallet, on another chain, or inside a centralized exchange account will not unlock this session.

Login And Balance Check

Connect

The frontend connects to your wallet and requests a Mythos login message.

Sign

The signature proves wallet ownership. It does not approve tokens or give Nexus spending permission.

Verify

The server verifies the signed session, checks Base chain ID, reads MYTHOS balance, then assigns the active tier.

Fresh Vs Full Quota

Nexus uses previous UTC holder snapshots to reduce wallet-hopping abuse. If a wallet only just became eligible, it receives fresh quota first. Once the balance is covered by a previous UTC snapshot, the wallet receives full quota for the tier it qualifies for.

Fresh accessCurrent balance qualifies, but no prior snapshot confirms it yet.

Partial quotaOlder eligible balance gets full quota; newly increased balance waits for snapshot confirmation.

Full quotaCurrent tier balance is covered by a previous UTC holder snapshot.

Access Failures

Holder required.The connected wallet does not hold enough MYTHOS on Base for the minimum access tier.

Auth not configured.The production server needs a valid MYTHOS auth secret before wallet login can work.

Balance check failed.The Base RPC or token metadata read failed. Retry after a short wait.

Daily limit reached.The wallet exhausted its daily quota for the requested route until the next UTC reset.

Privacy And Storage

Nexus stores the signed session in an HTTP-only cookie. Forge app workspaces are server-backed and tied to the owner wallet when the Forge store is configured. Legacy local browser apps may still appear as a fallback if server storage is unavailable. Chat/session history remains scoped to the wallet/browser session where available.