Sandbox

Sandbox Compatibility Checks Match Creation, Ownership, and Publishing to Their Requirements

Sandbox connects free creation tools with wallet-based ownership, SAND transactions, and LAND publishing, so compatibility depends on the task. A player can explore without committing assets, while a creator must match the account, wallet, network, ownership, and publishing state required for the intended result.

In short: Choose the intended action first, then match its wallet, network, ownership, and publishing requirements before signing a transaction.

Match the Starting State to the Intended Action

The intended action determines the required starting state. Playing, building, owning tokens, purchasing assets, and publishing to the map use related tools, but they do not share one universal set of prerequisites. Begin with the intended result, then stop at the first boundary that requires a wallet, token, or owned asset.

Free Play and Creation

An account is enough to begin playing and to create voxel art or Experiences with the free software. Game Maker supports building and testing Experiences, while VoxEdit produces compatible voxel assets. Neither activity requires an immediate LAND purchase or blockchain transaction.

Ownership and Transactions

A connected cryptocurrency wallet becomes necessary when the task involves owning tokens, making transactions, claiming eligible rewards, or using blockchain assets. The correct completion evidence depends on the action: a saved Experience appears in the workspace, a token appears under the connected address, and a published project reaches its chosen page or map state.

LAND is not required for every creative path. An Experience can be shared through the Game Maker Gallery, and an Experience Page can be published without LAND. Map publication crosses separate LAND-access and asset-rights boundaries that must be satisfied before launch.

Keep Wallet, Account, and Network States Aligned

The connected address controls which SAND, LAND, avatars, and other NFTs the account can display and use. A wallet may only be associated with one The Sandbox account, although it can be reconnected to that same account. Funds and NFTs remain in the connected wallet rather than in the platform account. Disconnecting it changes platform visibility without moving its contents.

Network selection determines whether compatible tokens are available for a particular transaction. SAND and LAND exist on Ethereum and Polygon, official LAND sales use Polygon, and some marketplace items may remain on Ethereum. Changing the network shown by a wallet does not bridge an asset; a bridge transaction moves supported tokens between the two blockchain layers.

The wallet confirmation screen provides the final boundary before commitment. Check the active network, token, amount, destination or contract, and gas requirement there. After signing, do not begin a dependent action until the expected asset appears under the intended address and network. A public wallet address can be inspected, but passwords and recovery phrases must remain private.

Separate Creation From On-Chain Commitment

Creation begins with editable project files and platform tools rather than a token purchase. Blockchain ownership becomes relevant when a creator wants to transact, mint eligible work, control access with NFTs, or publish through owned LAND.

Build and Test Before Buying

Game Maker provides a no-code environment for building and testing Experiences. VoxEdit assets can be used in a creator’s own Experience without first being minted as NFTs. This route lets the project reach a playable test state before LAND, marketplace assets, or transaction fees become part of the decision.

View full-size image

Publish at the Appropriate Level

An Experience Page provides a shareable project presence without requiring LAND. Map publication has stricter conditions because the Experience must be located on virtual property. Publishing an Experience on the map requires access to LAND large enough for the build and the right to use every included asset; creator-uploaded and free Basic assets do not need to be minted. An asset that worked during testing may still fail that ownership check.

Monetization follows the rights and token state of the chosen route. Creators may mint eligible assets for marketplace use or design access around supported NFTs, while LAND can host discoverable Experiences. Publication alone does not promise revenue, and testing an asset does not grant the right to publish it.

Read SAND, LAND, and Asset Roles Correctly

SAND is the ecosystem’s fungible ERC-20 utility token and medium of exchange. It is used for platform purchases and governance participation, and its documented maximum supply is 3 billion tokens. Its market value can change because SAND is not designed as a stablecoin.

LAND represents distinct virtual property through the ERC-721 standard. Each parcel has an individual map location rather than being interchangeable with every other parcel. The documented LAND total is 166,464 parcels. Ownership matters for map publication, but it does not replace the separate requirement to own assets used in the Experience.

Entities and equipment created for Experiences can be minted under the ERC-1155 standard. These roles should not be collapsed into one generic NFT category: LAND supplies a location, assets supply usable content, and SAND supports transactions. The token standard helps identify an asset type, but it does not prove that a listing is genuine.

Confirm Each Boundary Before a Transaction or Launch

The following checks keep a reversible setup from becoming an incompatible transaction or blocked publication:

• Define whether the immediate task is play, creation, ownership, purchase, or map publication.
• Confirm that the intended account shows the correct connected wallet address.
• Match the asset’s blockchain layer to the network required by the action.
• Verify access to LAND large enough for the Experience and permission to publish every included asset.
• Read the wallet prompt for the token, amount, destination, network, and gas requirement.

A failed check is a stop condition, not a reason to sign and troubleshoot later. Preserve unfinished creative work in the workspace, correct the mismatched account or network state, and confirm the new state before continuing. This matters because a completed blockchain transaction may not be reversible.

Use Observable State to Resolve Edge Cases

Compatibility failures often appear as missing balances, unavailable assets, or a blocked launch. The visible symptom identifies the boundary to inspect before another action is attempted.

Wrong Network or Incomplete Bridge

An Ethereum balance does not become a Polygon balance when the wallet view changes. A supported asset must complete its bridge transfer before it can be used on the destination layer. The reliable end state is the expected token under the same wallet address on the destination network, with the transfer recorded as complete.

Missing Asset Rights

An asset available during testing may belong to a marketplace listing rather than the creator’s wallet. Experience Manager can expose this gap before map publication. The creator must own the required asset or remove it from the publishable build; a successful preview does not satisfy the ownership condition.

Wallet Changes and Hidden Content

A disconnected wallet takes its visible SAND, LAND, NFTs, claims, and rewards out of the account view without deleting them from the blockchain. Reconnecting the same wallet restores access to its on-chain assets, but time-bound claims or rewards still depend on the contracts that created them. Connecting a different address shows that address’s contents instead, and a wallet previously assigned to another account cannot be reassigned.

When LAND or asset ownership blocks a map launch, the Gallery or a free Experience Page remains a lower-commitment publishing route. Those options support testing and sharing, while LAND publication adds an owned location and stricter asset checks.