Explore Solana Lab · cApp Developer Docs

Use the Lab as a reference application

Open Solana Lab. The public preview is descriptive and inert: it explains scenarios and links to these guides without inheriting installed wallet, RPC, live-price or Local AI authority. A disabled execution control there is expected, not evidence that your provider is broken.

The installed Lab uses the Sidecars packaged with it. A standalone local Lab can explicitly bundle a reviewed runtime; it is not the hosted preview and must not replace missing installed components behind the user's back. Updating this documentation does not update an already-installed Lab or its immutable compiler release.

A useful demonstration path

Start with The Lab, then Network window and Wallets in the installed app. Verify the devnet connection and use Demo payer & receiver to choose two distinct accounts. Prepare demo wallets, or its Guide workflow, reuses existing wallets before creating missing device wallets. You can set either role in Wallets, create a separate receiver without switching the payer, or enter another receiver's public address. No wallet is created on page load, and setup never signs or sends a payment.

Back up new device wallets and check funding. The payer needs the payment asset plus devnet SOL for fees. Before a tiny native SOL payment, Guide and the new-draft controls check whether a fresh receiver needs test SOL too. Original SPL token transfers retain their separate associated-token-account rent checks. Empty or unchanged automatic recipient fields follow the receiver choice; typed recipients and saved payment terms remain unchanged. A read-ready RPC connection, wallet storage and signing authority are separate prerequisites. No Local AI model is required merely to read the guides or run authored guided workflows.

For a compact demonstration, use Service desk → The missing reply → Component library. The first connects a payment to useful local output; the second shows why uncertain outcomes retain identity; the third exposes the reusable parts. State whether each action is local, simulated or devnet before running it.

Scenario	What to show	What it does not prove
Service desk	Save a JSON report order, review/approve/send, observe its bound receipt, then generate the local report.	A production remote merchant ledger or externally hosted report service.
Payout desk	Two to five independent contributor payments, each with its own saved operation and receipt.	An atomic batch; completed children must not be resent to fix one pending child.
Proof studio	Commit the exact text's digest and compare another copy; whitespace matters.	Authorship, truth, ownership or publication of the original document.
Pocket checkout	A saved fictional purchase with explicit devnet payment stages.	Real inventory, custody or automatically verified remote fulfilment.
Collective treasury	Simulated message-bound reviewer quorum followed by a separate wallet-approved devnet transfer.	A multisig wallet or authenticated threshold signatures.
Position studio	Observed price inputs driving deterministic Arena positions and allocation/recovery.	A live market trade or settlement of the simulated position.
The missing reply	Arena records execution and withholds a response; check the original attempt after reload.	A newly performed live transfer or guaranteed provider fault tolerance.
Token/payment-request demos	Exact asset/atomic amount and saved request/reference, separate receiver and verification.	Authentic token identity from a symbol, or automatic mainnet signing.
Policy playground	A normal case and deliberate fee/staleness rejections with specific reasons.	Wallet approval, a balance check or execution of the tested metadata.
Network window / activity	Bounded observations through the configured provider and paged history.	Complete chain history or authorization to send.

A guided service-to-proof journey creates a separate document-commitment transaction with its own approval, send and network fee. A Position studio evidence link is a small scaled devnet transfer that commits the simulation digest; it does not prove that the simulated trade happened or moved its full notional value.

Read the saved result, not just the animation

Use Previous runs and Receipts & activity to reopen the original work. Opening a record must not create another operation. Show saved sender, network, operation/attempt identity, simulation flags, observed state and matching receipt/evidence when relevant. Keep a tracking warning distinct from a missing payment.

Run with Guide, Guide me, Watch demo, New run and Guide workflow offers start a fresh demo session. Earlier records remain in Previous runs and Receipts & activity. Continue with Guide on a saved record opens that exact operation; Next, Retry and faucet return remain in the current run. A new demo never reconciles or resends an earlier unknown payment.

Guide explains each task, the next action and the result to inspect. You approve signing and sending separately, including in Auto mode. Cancelling stops the walkthrough; a payment already sent can still complete and remains in your history. The optional assistant can explain records and suggest a demo, while payment approval stays with you.

Move from demo to your own application

Choose one capability or composition, use the portable client and keep business state outside the generic Sidecars. Replace the Lab's local report/delivery logic with your own authenticated service and durable claim where that is the product requirement. Do not copy bundled demo credentials, device defaults or browser fallback code as an infrastructure standard.

Use composition, the payment recipe, recovery and merchant verification as the shared contracts. The Lab's older #/docs/* bookmarks remain topic-aware entry points to this site; local component inspection and recorded activity remain in the Lab.

Wallet precautions

Devnet device keys are test keys stored unencrypted in app storage. Download a separate backup before funding, and verify the saved file through the provided controls. A backup-file comparison is not proof of a successful restore. A receipt export does not contain recovery keys.

Experimental mainnet wallet management is a separately warned password-encrypted path, not mainnet signing through the built-in payment recipe. It is not an audited wallet, OS keystore or hardware wallet. Never put valuable primary-wallet recovery material into a demonstration, and never fund a devnet test key on mainnet. Losing app storage and the independent backup can lose access; a forgotten encryption password is not recoverable by cApp.

External wallets appear only when the browser/host exposes a compatible provider. A normal WebView may expose none. The presence of a mode or a branded wallet name in documentation does not establish installed Android MWA or a real extension approval run. See Latch for the actual provider boundaries.

When a demonstration does not progress

Situation	Next action
All execution controls are disabled on the website	Confirm that this is the public preview; use the intended installed application to execute.
Installed components are connecting	Retry readiness without clearing records; inspect selected packages and the installed version.
RPC error after components become ready	Open Network window and test the active Conduit settings; do not reset wallets.
Funded payer but recipient validation fails	Check the visible recipient field. Funding the sender does not supply a missing recipient.
Saved receiver was removed or is now the payer	Select a distinct receiver in Wallets, or explicitly prepare the pair again. Retained payments keep their saved recipient.
Fresh receiver needs test SOL	Copy the receiver address from the funding step, use the devnet faucet, then repeat the same check. A faucet deposit does not pay a saved request.
Market Pulse is unavailable	Check the selected Market settings or retry its connection. Wallets and payment pages remain usable; new positions wait for a current observed price.
A demo immediately reuses an earlier result	Update the cApp owner and freshly compile/package the Lab. Current launch controls prepare a new run; use Continue with Guide only for a selected saved record.
Saved run belongs to another sender	Restore/choose its actual authority for unfinished signing, or observe its existing submission. Never rewrite the saved sender.
Receipt exists with a tracking warning	Preserve both facts and refresh observation of the same operation. Do not pay again.
Policy playground rejects an excessive fee or stale request	Inspect whether the intended check failed; that rejection can be the correct result.

Use Help for a bounded issue report. Keep private document text, wallet material and provider credentials out of screenshots and public exports.