Sandbox
Sandbox is a Blockchain-Based Virtual World for Buying and Owning Digital LAND
Sandbox is a Polygon LAND purchase workflow in which a verified account chooses Standard or Premium LAND, pays with Polygon SAND and signs from the linked wallet. The decisive checks are chain ID 137, sufficient SAND, an available gas route and a confirmation address matching the account's connected wallet.
The Purchase Decision Starts With Network, Tier And Eligibility
A Polygon-ready wallet, a verified account and a chosen LAND tier decide whether an official LAND sale can move from booking to signature.
Eligibility begins well before the sale opens. Know Your Customer verification can require up to 48 hours, and the purchasing wallet must already be linked. The Sandbox permits one wallet to connect to only one account across its lifetime, although that wallet can reconnect to its original account. MetaMask, Coinbase Wallet and Venly are named connection options, while WalletConnect supports additional compatible wallets. Every route must expose the same Polygon address to the sale page and the signing prompt. That alignment prevents an address mismatch at confirmation.
Use this five-point decision checklist before accepting a temporary booking:
- Account verification shows complete before the active sale begins.
- Polygon Mainnet reports chain ID 137 in the connected wallet.
- The displayed address matches the wallet linked to the account.
- Polygon SAND covers the shown amount, with a gasless allowance or POL available for gas.
- The Standard, Premium or either selection reflects acceptance of a randomly assigned parcel in that class.
Standard And Premium Change Location, Not Parcel Geometry
The Standard-versus-Premium decision changes placement and bundled benefits, while both LAND tiers use the same base parcel geometry on Polygon Mainnet.
Both choices represent a 1x1 LAND. Its buildable base measures 96 by 96 blocks and its height reaches 128 blocks. Each block measures 1 metre on every side and contains 32 by 32 by 32 voxels. Premium therefore does not enlarge the base unit. The Premium label identifies LAND close to or touching partner Estates and includes additional NFTs, while Standard lacks that placement designation and bundle.
The registration interface presents three choices: Standard, Premium and either. Selecting either broadens the acceptable class, while choosing one tier fixes the class that the booking seeks. Neither choice reserves a particular coordinate.
Official sales assign a random LAND within the purchased class. The decision therefore belongs on location category and bundled content rather than parcel dimensions.
Pre-Registration Creates A Ten-Minute Purchase Window
The Sandbox pre-registration choice creates a temporary booking rather than ownership, and an active purchase window lasts exactly 10 minutes.
Registration records interest in Standard, Premium or either before the sale. When the active sale allocates an opportunity, the interface starts the countdown and enables the purchase action. The booking does not transfer an ERC-721 token and creates no Polygon receipt. It only holds an opportunity while the timer runs. Expiry releases that LAND opportunity for another eligible account, so a late signature does not preserve the reservation.
Each completed flow buys one LAND at a time. Another parcel requires another available booking and another transaction, even when the same wallet remains connected. That sequence matters because the SAND balance and gas route are reevaluated for every purchase. A first purchase can therefore reduce the balance below the amount shown for a later tier.
Gas Payment Splits Between Gasless Allowance And POL
Polygon gas readiness determines whether the LAND purchase uses a remaining gasless transaction from The Sandbox or spends POL from the connected wallet.
Every account in The Sandbox receives 10 gasless Polygon transactions per 28-day cycle when the setting is enabled. The purchase page displays the remaining count and renewal date. A count of 0 requires disabling the gasless setting and holding POL for the network fee. One gasless use covers one blockchain transaction; it does not reduce the SAND purchase amount.
SAND and gas occupy separate roles. Polygon SAND is an ERC-20 token with 18 decimal places, while POL is Polygon's native gas token. The sale reads SAND from contract 0xbbba073c31bf03b8acf7c28ef0738decf3695683. Official LAND sales use Polygon rather than Ethereum to reduce gas overhead. Self-funded execution quotes gas in POL, whereas the enabled gasless route relays the transaction. The discontinued SAND gas-forwarding setting is not an available fallback.
What Should The Wallet Show Before You Sign?
The wallet should show Polygon, the connected address and a transaction request whose SAND amount matches the sale panel before you sign.
Two Confirmation Layers
The sale interface and wallet answer different questions. The page identifies the tier, amount, booking timer and gasless balance. The wallet identifies the account that authorizes execution and the network receiving that authorization.
The LAND Sale Panel
The LAND Sale panel should still show an active booking, the chosen Standard or Premium class and the purchase amount in Polygon SAND. Check the countdown before opening the wallet because a delayed approval does not extend the 10-minute window. The connected address shown by the page must equal the address holding the required SAND.
The Wallet Prompt
A self-funded MetaMask or Coinbase Wallet prompt shows Polygon Mainnet and a gas estimate denominated in POL. A gasless route through the platform can present a signature authorization while a relay submits the Polygon transaction. In both paths, the wallet address must match the linked account. The token amount belongs in the LAND Sale confirmation, while the wallet controls execution. Signing changes nothing until the request is submitted and included on Polygon.
A Successful Receipt Changes Two On-Chain Balances
A successful Polygon receipt makes the wallet the recorded owner of one LAND token ID and debits the approved SAND amount.
Polygon LAND uses ERC-721 contract 0x9d305a42A3975Ee4c1C57555BeD5919889DCE63F. An ERC-721 ownership change emits a Transfer event with three indexed values: the previous holder, the receiving wallet and the token ID. That token ID is a 256-bit unsigned integer. The recipient should equal the linked wallet, while the transaction also records the SAND payment path. A self-funded purchase additionally reduces POL by the network fee; a relayed purchase consumes one gasless allowance instead. The address-token pair uniquely identifies the parcel.
An EVM receipt reports status 1 for success and status 0 for reversion. Its transaction hash is 32 bytes, normally displayed as 64 hexadecimal characters after the 0x prefix.
Polygonscan exposes that receipt, event and token ID before an application cache necessarily refreshes. The Sandbox Wallet LAND tab and Map then read the same Polygon ownership state. The on-chain recipient remains the decisive verification point when the page display is still updating.
Wrong-Network Recovery Restores The Purchase Flow
A wrong-network message means the connected wallet session and the purchase page disagree about Polygon, so restoring chain ID 137 resolves the setup.
Select Polygon Mainnet in the wallet, confirm chain ID 137 and reconnect the page to the same linked address. Close any stale Ethereum prompt before reopening the active booking.
If Polygon shows zero SAND while Ethereum shows a balance, switching networks has only changed the view. The Sandbox Bridge must move that ERC-20 balance from Ethereum to Polygon before it becomes spendable in the LAND sale. Bridging belongs before the 10-minute booking because settlement time follows network conditions.
Retry only after the sale panel, wallet network and token balance agree.
A related walkthrough covers Sandbox comparison. This workflow fits a purchase whose verification, tier choice, SAND balance and gas route are prepared before the countdown starts. Those aligned inputs leave the final signature to perform one defined action: assign the booked LAND token to the linked Polygon wallet.
Practical questions about Sandbox
Does importing the Polygon LAND token change ownership after purchase?
No, importing the Polygon LAND token only teaches a wallet interface which contract to display. Ownership already resides in the ERC-721 contract and is tied to the receiving address plus token ID. Add the Polygon LAND contract if MetaMask does not render the asset, then confirm the same token through Polygonscan and The Sandbox Wallet. Importing a contract neither moves the LAND nor creates a second copy.
Is Ethereum SAND accepted when the connected address is identical on Polygon?
No, an identical hexadecimal address does not merge Ethereum and Polygon token balances. The official LAND sale reads Polygon SAND on chain ID 137, so Ethereum SAND remains invisible to that purchase balance. Move the tokens through The Sandbox Bridge before the booking window, or fund the address with Polygon SAND through a supported route. Merely selecting Polygon Mainnet changes the wallet view; it does not transfer tokens between networks.
How many LAND purchases can one verified account complete during a sale?
The account purchases one LAND per completed flow and repeats the process while eligible inventory remains. The platform does not impose a general ownership cap, yet each temporary booking still carries its own 10-minute deadline. A completed transaction does not preserve the previous reservation for another parcel. The next attempt needs a fresh available booking, enough Polygon SAND and another usable gas route.
When is a rejected wallet signature recorded on Polygon?
A rejected signature is not recorded on Polygon because the wallet never submits or authorizes the requested state change. No transaction hash, SAND transfer or LAND Transfer event appears from that rejected action. Return to the sale panel and try again only while the 10-minute booking remains active. If a hash already exists, inspect its receipt instead; status 1 confirms execution while status 0 confirms reversion.
Does reconnecting the linked wallet alter the assigned LAND token ID?
No, reconnecting the same linked wallet does not alter a LAND token ID or its recorded owner. The token ID is a uint256 identifier inside the Polygon ERC-721 contract, and the address-token pair remains the ownership record. Reconnection only restores the account interface's access to that wallet data. If the LAND remains absent, compare the connected address with the receipt's recipient and inspect the transaction on Polygonscan.