Sandbox
Sandbox links virtual creation and play with wallet-based ownership, transactions, governance, and verifiable changes in digital state
Sandbox separates what happens inside a player account from changes that affect a wallet, an NFT, or an Experience published on LAND. Playing and building can begin without connecting a cryptocurrency wallet, while ownership, marketplace transactions, rewards, and governance depend on wallet-linked records. Before any consequential action, note the connected wallet, selected network, relevant asset, current status, and intended result. Completion then has a concrete test: the chain confirms the transaction, the Experience Manager reports the relevant action as Ready, or the expected item appears in the correct inventory. An exit is equally specific, such as closing a launched Experience, withdrawing from a closed staking pool, or leaving an asset unchanged.
Key takeaway: Track each change from its starting record to a visible result before committing assets, publishing an Experience, or leaving a closed program.
Playing, creating, and owning produce different records
Each route changes a different kind of record. A player account stores profile and project state. Game Maker saves an Experience, while VoxEdit produces voxel Assets. A connected wallet manages access to an address associated with blockchain tokens and supplies signatures for transactions. LAND provides the location required to launch an Experience on the metaverse map, and the Experience Manager checks whether the project is ready for that location.
- Playing changes progress or eligibility inside an Experience.
- Creating changes a draft, its logic, or the Assets it uses.
- Publishing an Experience Page changes its visibility, while launching changes the Experience’s status on the metaverse map.
- Acquiring or transferring tokens changes a balance or an NFT ownership record.
- Voting records eligible voting power on a proposal.
These routes can overlap without becoming the same process. A creator may test an Asset in a draft before owning its NFT, for example, but the publishing check must later confirm ownership. Likewise, a wallet connection exposes relevant holdings to the account without moving those holdings. The starting record therefore determines both the next action and the evidence needed afterward.
What proves a Sandbox state change is complete?
The system performing the change supplies the proof of completion. A wallet prompt only requests a signature; it does not show a transaction has settled. For an on-chain action, check the transaction status, destination address, network, and resulting token balance or ownership record. For a project change, use the Experience Manager status rather than a wallet balance.
Two interfaces may update at different speeds. A confirmed blockchain record can exist before the account inventory refreshes, while a saved draft can appear in a workspace without creating any blockchain transaction. Publishing introduces another checkpoint: required actions must show Ready before the launch control becomes available. A visible button, submitted request, or disappearing spinner is weaker evidence than the resulting state in the relevant record.
The normal path from draft to a launched Experience
Publishing moves a project through checks tied to the latest saved draft, not to an earlier version that happened to pass.
This publishing case is hypothetical. The 13 Assets, LAND location, wallet holdings, and later replacement are all invented for illustration. A creator starts with a draft using 13 Assets, a chosen LAND location, and a connected wallet that owns those 13 items.
On the normal path, Asset Review finds every item owned and ready, the creator assigns the map location and prepares the Experience Page, and all required actions show Ready. The launch control then becomes available. After the creator launches, the Experience opens at the selected location.
The edge case begins when the creator replaces one Asset after the first review. That earlier review no longer describes the saved draft. The recovery boundary is another Asset Review: the creator must publish a replacement they created, buy the required NFT, or choose another ready Asset they already own. Launch waits until the revised project returns to Ready. If the location must change later, the creator closes the Experience before relocating and launching it again.
Where do SAND and digital assets change hands?
SAND pays for ecosystem purchases, while NFTs such as LAND, avatars, equipment, and creator Assets can move through purchases or transfers. SAND is a fungible ERC-20 utility and governance token, so a wallet balance represents interchangeable units rather than a unique item. An NFT ownership record identifies a particular token or token amount with its holder.
The selected network matters before a signature. Sandbox uses Ethereum and Polygon for blockchain activity, and an item or balance on one network is not automatically usable in a transaction on the other. Network fees may require ETH on Ethereum or POL on Polygon. The live wallet request should identify the action, network, contract interaction, and fee before approval.
Bridging is different from sending an asset to another owner. A supported bridge moves SAND or LAND between the two networks while keeping the asset’s supply and utility unchanged. Its history may show an intermediate checkpoint or another action needed to finish. Completion means the asset appears on the destination network and the bridge record no longer requires input.
Governance, reward claims, and closed staking pools
A current status check matters because holding SAND, claiming an earned reward, voting, and staking are separate actions with different records. Governance uses eligible SAND or LAND holdings to establish voting power, and delegation can assign that power without transferring the underlying tokens. A vote records participation in a proposal; it does not spend the voter’s holdings.
Sandbox staking rewards ended in June 2025. Owners may still withdraw existing staked assets, but leaving them in a closed pool does not restart yield. A withdrawal has its own wallet confirmation and blockchain result, so the relevant endpoint is the returned balance rather than an old reward estimate.
Reward claims follow the terms attached to the event or activity that created them. Eligibility, identity verification, network readiness, and an individual claim deadline can all affect whether a claim can proceed. Check that claim record on its own instead of treating it as a continuation of staking.
How should mismatched records be reconciled?
Start with the record closest to the action, then compare it with the saved starting details. A missing item may reflect the wrong connected wallet, the wrong network, a pending bridge checkpoint, or an account display that has not refreshed. Its absence from one screen does not itself establish a loss.
For a blockchain action, match the wallet address, network, token, and transaction status before attempting anything again. A pending bridge record may identify an additional step, while a completed record establishes where the asset should appear. Submitting a second transfer only because an account view lags can create a separate transaction rather than repair the first one.
Project reconciliation uses the saved Experience, not a chain explorer. Changes to Assets require a fresh Asset Review, and a location change requires the creator to close the launched Experience first. These checks reconnect the current draft with the ownership and location conditions needed for its next state.
Commitments, reversibility, and safe stopping points
Not every change has the same recovery boundary. Draft edits remain revisable, and a creator can close an Experience before changing its location. A wallet signature can instead authorize a purchase, bridge operation, mint, claim, or transfer. The blockchain records the consequences. The last safe stop is the wallet confirmation screen, before the signature is submitted.
That screen should match the intended network, destination, token, and action. A public wallet address can identify a destination, but a recovery phrase or private key authorizes control. Never share either secret. Sandbox support cannot use a platform setting to reverse a completed transfer to an incorrect address.
Account access and asset custody also differ. Disconnecting a wallet may hide its tokens and NFTs from the connected account, yet it does not delete the wallet or the assets inside it. This distinction matters when the goal is to remove access rather than transfer ownership.
Staying in place, transferring, or exiting
An exit begins by deciding whether the goal is to stop an activity, move an asset, or remove account access. Closing an Experience stops its launched state and creates a reversible point for later edits or relocation. Withdrawing from a closed staking pool returns the staked position to the wallet; it does not renew rewards.
Moving an asset requires a different decision. A transfer moves the asset to the receiving address, while a bridge changes the network where the same holder can use the supported asset. Both require a wallet signature and a completion check. Removing the wallet connection only changes what the Sandbox account can display or access, leaving custody with the wallet.
Leaving an asset where it is avoids a new transaction but retains the responsibility of securing that wallet. Transferring commits ownership to another address. Bridging keeps ownership while changing the usable network. When no immediate action is needed, staying in place remains more reversible than signing a transfer; when a supported feature requires the other network, bridge first and verify the destination state before continuing.
Still wondering about Sandbox?
Is SAND a stablecoin?
No, SAND is not designed to maintain a fixed value. It is a utility and governance token whose market price can change with supply, demand, liquidity, and broader market conditions. A wallet balance therefore shows a token quantity, not a stable cash value, and any transaction should use the live amount displayed before confirmation.
Can I share an Experience before I own LAND?
An Experience Page can be published and shared without owning LAND. Launching the playable Experience on the metaverse map is a separate state and requires a suitable LAND location plus ownership of the Assets the project uses. The page proves the project is visible; it does not by itself prove the Experience is launched for players.
What happens if an NFT is sent to the wrong wallet address?
A completed blockchain transfer to an incorrect address cannot be reversed by Sandbox. The receiving address controls the transferred NFT once the network confirms it, so account settings cannot restore it. Check the full destination, selected network, and token before signing; a familiar-looking prefix or truncated address is not enough to establish the destination.
When is an account eligible to vote in Sandbox governance?
An account can vote when its connected holdings meet the DAO participation threshold: at least five SAND or one LAND. Voting power considers eligible holdings on Ethereum and Polygon, and the holder may delegate voting power without transferring the tokens. Proposal timing and snapshot rules still determine whether a balance counts for a particular vote.
Does creating an Asset make it an NFT automatically?
Creating a voxel Asset does not automatically mint it as an NFT. The file can remain in the creator’s Workspace and serve in an Experience without an on-chain token. Minting and listing are separate actions with their own wallet and publishing requirements, so a saved or uploaded Asset is not proof of NFT ownership.
Why might an earned reward be unavailable to claim?
An earned reward may become unavailable when the claim has expired, the account does not meet the stated eligibility rules, or required identity verification is incomplete. Claims also use a specified network and wallet. Check the individual claim record for its deadline and status, because a past reward announcement does not establish that the claim remains open.
Can NFT ownership control access to an Experience?
NFT ownership can control entry to an Experience or access to selected gameplay when the creator configures those restrictions. The rule may require a specific NFT or an avatar from an allowed collection; the avatar must be equipped when that condition applies. Ownership alone does not create gating unless the Experience has a matching access rule.