Read the details.
Stay in control.
Know which account is acting and what a transaction changes.
The demo wallet is managed
The playground runtime holds test signing accounts and executes the actions you request. The demo wallet is shared by the scene, so other visitors and demo actions can change its balances; it is not a private wallet created for each visitor. Private signer material is not sent to the browser. This is separate from the production collector’s wallet integration.
Only use test funds in the demo. Its stock-style tokens confer no equity, company rights, or redemption claim. Their prices do not track real stock prices.
An error does not prove failure
If submission is interrupted, check the known transaction hash and chain receipt before retrying. The public-testnet runtime records intents, hashes, and receipts; an unresolved action blocks further writes for inspection.
Refreshing a page, clearing browser storage, or deleting an operator journal is not evidence that a transaction failed. Avoid submitting a duplicate action while the first outcome is uncertain.
Understand approvals and custody
A token approval gives a contract permission to spend. An NFT deposit moves custody into the converter and makes that NFT available to others. A simulation checks recent state; it cannot reserve inventory or prevent market movement before execution.
Never share private keys or recovery phrases. Keep operator credentials, reveal salts, encrypted bundles, and encryption keys out of public folders.
Understand the boundaries
Market prices and liquidity can change. Depositing a rare NFT still returns one FLOOR. Application contracts do not offer an admin reversal, discretionary sweep, pause, or upgrade to undo a mistake. Tests and rehearsals are useful evidence, not an independent audit.
The managed-wallet operator server is intended for loopback use. A public viewer/operator deployment needs deliberately scoped authentication; exposing a local operator port is not a publishing plan.