Q/01 / CONTINUOUS RUN / DEVNET

Free wallet access

Free wallet access, a saved visual run, and no promised terminal output.

Connect. Sign in. Enter.

Access is free for authenticated wallets. The wallet signs a text message to prove ownership; starting the run does not ask for a blockchain transaction or spending permission.

No token balance, token burn, SOL payment or network fee is required. The continuous run has no completion event, collectible, NFT, token reward or discovery output.

  1. Connect a compatible Solana wallet.
  2. Read and sign the one-use authentication message. The challenge binds the wallet, site origin, configured network and session, and expires after five minutes.
  3. The server verifies the signature and creates a signed-in session. Connecting an address alone is not authentication.
  4. Start the run. The server creates or returns the run belonging to the authenticated wallet and current network.
  5. Pause or return later. Reconnect and sign in with the same wallet to resume the saved run for free.

A message, not a transaction

The authentication signature proves control of the wallet for this site session. It does not transfer or burn tokens, approve a delegate, create an account or submit anything to the blockchain. No SOL is needed for this message signature.

Sessions expire, so a later visit can require another authentication message. A wallet switch or disconnect reconciles the server identity before protected actions resume. It never makes another wallet’s saved run accessible.

Network context

The current configured network is DEVNET. The server and browser labels must agree. Network context scopes the saved run; it does not turn free access into a paid transaction. A run on one network is not silently moved to another.

API boundaries

  • GET /api/run: free-access configuration and the authenticated owner’s saved run.
  • POST /api/run: accept an empty JSON object and create or return the authenticated wallet’s saved run.
  • POST /api/run/quote and POST /api/run/register: retired payment endpoints; HTTP 410.

Historical burn code and receipt records, including the recovery-only status route, are retained separately for audit and recovery. They do not gate the current run or enable new payments. No token mint or amount needs to be configured for free wallet access.

See the security model for session and operational limits.