Skip to the cases

FREE BUILDER CASEBOOK · WORKS OFFLINE

Connect carefully. Review before signing.

A wallet connection, an Academy web login, and a Solana transaction are three different actions. Inspect the network, capability, request, cost, and result before deciding what the application should do.

FORMATIVE · UNSCORED · NOT SAVED

Inspect six browser wallet decisions

Choose the response that respects the learner’s choice and keeps the action scoped to what the evidence supports.

01

CONNECTED · NO SIGNATURE REQUESTED

The page reconnects the learner’s selected account.

Wallet state: Connected to one public account
App action: Read the learner’s public course credential status
Wallet signature: None requested

What may the app conclude?The learner approved all future transaction requests from this site.The app can use the connected public account for the allowed read; this does not sign in to the web account or authorize a transaction.The public key proves the learner’s real-world identity.

Choose an answer before checking.

02

WEB SIGN-IN · NO ON-CHAIN WRITE

The Academy needs proof the user controls this key.

Purpose: Authenticate this wallet to the Academy website
Required proof: Control of the selected signing key for this domain
Course state: Must not be changed by login

Which flow fits?Submit a zero-value transaction on every login so it appears on-chain.Use account connection alone as a fresh signature for this web session.Verify a clearly shown, one-time domain-bound message with a server-issued nonce; expire and consume it once.

Choose an answer before checking.

03

CHAIN MISMATCH · ACTION PAUSED

The app is on Devnet; the selected wallet account is on Mainnet.

RPC endpoint: Devnet
Wallet account chain: Mainnet
Pending action: Build a program transaction

What should the client do?Pause, explain the mismatch, require an intentional supported network selection, then rebuild and re-check the request.Silently change the application to Mainnet and keep the same preview.Open approval for both networks and let the wallet choose one.

Choose an answer before checking.

04

CAPABILITY NOT ADVERTISED · NO SAFE CALL

The selected account lacks the message-signing feature.

Requested action: Off-chain sign-in message
Selected account: Connected; required signing feature not available
Available fallback: No other supported account selected

What is the safe behavior?Explain the missing feature and stop or offer an explicitly described compatible flow; never ask for a recovery phrase or private key.Ask the learner to paste the private key so the site can sign.Call the missing feature anyway and treat any response as authentication.

Choose an answer before checking.

05

MINT REQUEST · COST PREVIEW

A credential mint creates a rent-exempt account on Devnet.

Instruction: Create the learner’s non-transferable credential asset
Funding: Fee plus account creation/storage funding
Issuer policy: Learner signs and pays their own mint

What must the application explain?Say the mint is free because the lesson itself is free.Show the cluster, exact action, fee payer, network fee, and separate account funding before the wallet opens.Promise that the Academy will reimburse all storage costs after approval.

Choose an answer before checking.

06

REJECTION ≠ SUBMISSION TIMEOUT

The wallet declines in one run; RPC times out after submission in another.

Run A: Wallet explicitly rejects before signing or submission
Run B: Signed request submitted; response timed out; signature retained
Required response: Never claim confirmed success without observing it

How should the app handle these outcomes?Immediately resend both requests until the UI reports success.Mark both failed because the browser did not show a confirmation.Stop after Run A is declined; reconcile Run B’s retained signature on its intended cluster before offering a deliberate retry.

Choose an answer before checking.