Sandbox LAND acquisition starts by matching the parcel, wallet, network, and transaction details before signing

Prepare one parcel for a verifiable first purchase

Start by identifying whether you are using an official sale or a secondary listing. For a listing with a selectable parcel, record its coordinates, token identifier, network, sale route, and intended receiving address. Match that parcel to the map without moving funds. If an official sale assigns the location, check its LAND type, allocation method, network, payment requirements, and receiving address instead. Continue only when the applicable details agree across the sale interface and wallet.

The unsigned wallet prompt is the final point where you can stop without authorizing the request. If the wallet opens on another network, names a different account, or requests an unexpected action, close the prompt. A listing can be revisited; a confirmed blockchain transfer usually cannot be cancelled by the buyer.

Identifiers that determine what the wallet will receive

Parcel coordinates, token data, and the receiving address identify the virtual parcel, its blockchain record, and where ownership will be recorded.

Parcel coordinates

Coordinates locate the parcel on The Sandbox map. They let you distinguish visually similar listings and inspect the surrounding area without relying on a seller-written name. When a route lets you select a parcel, its coordinates should remain consistent as you move from the map to the sale interface.

Token and contract

LAND is represented by ERC-721 token contracts on both Ethereum and Polygon. The network selects the relevant contract and transaction history. A familiar collection name does not compensate for a different contract, and the same token standard alone does not prove a listing represents genuine LAND.

Wallet and account

The wallet address is the on-chain recipient, while its authorized signer or signers control the token after purchase. The Sandbox account provides the connected interface, but the blockchain records ownership against the wallet address. Connecting a second address can therefore make an acquired parcel appear absent from the account view even while its ownership record remains intact.

What should match before you sign?

Every consequential field should describe the same intended purchase before the wallet receives approval. Check the values in their working context rather than reading only the prominent parcel image or total.

• The coordinates match the parcel selected on the map.
• The LAND contract belongs to the network shown in the wallet.
• The connected address is the wallet meant to receive the NFT.
• The payment asset and available balance are on the required network.
• The wallet prompt shows the expected approval or purchase action.

A mismatch in any one field is enough to stop. Changing networks, accounts, or parcels can alter several other fields, so reopen the transaction only after reviewing the complete set again.

Match the network before checking the balance

A wallet balance has meaning only on the network used by the purchase. SAND held on Ethereum is separate from SAND available for a Polygon transaction, even when the wallet interface displays both under one account. Moving assets between networks is a distinct bridge operation, not part of the LAND purchase itself.

Gas follows the same boundary. A Polygon action may use an available gasless option or require the network’s gas token, while an Ethereum transaction follows Ethereum fee conditions. Read the live wallet request because network traffic and available account features can change the cost.

How do coordinates prove you selected the right parcel?

Coordinates provide a stable map location you can compare across the parcel view and listing. They do not prove authenticity on their own. Pair them with the token contract, network, and token identifier, then return to the map through the expected listing flow. If the location differs, stop before approval rather than treating a similar thumbnail or name as evidence.

Put the wallet into a known state

Before responding to any contract request, confirm the active address, payment balance, and gas option on the required network. This separates wallet setup errors from parcel or marketplace problems.

Confirm the active address

Compare the full connected address with the address intended to hold the NFT. A shortened display is useful for recognition, but the full value resolves addresses with similar beginnings and endings. The connected address should also be the one associated with the account where you expect LAND to appear.

Separate payment from gas

The purchase amount and network fee serve different purposes. Having enough SAND does not necessarily provide the gas asset, and a gasless allowance may not be available for every action. Let the purchase interface and wallet show the applicable requirements before moving funds.

View image file

Protect signing authority

A legitimate purchase needs a wallet signature, never a recovery phrase or private key. Read whether the request is a message signature, token approval, or purchase transaction. Those actions have different effects, and an approval does not itself prove LAND moved to the wallet.

Separate official sales from secondary listings

Official sales apply their current eligibility and allocation rules, while secondary listings identify a specific token offered by its holder. Either route can place an ERC-721 LAND token in the receiving wallet.

Official LAND sales

Official LAND sales have taken place on Polygon since November 2022. A particular sale defines its eligibility, available LAND types, allocation method, payment requirement, and time window. Confirm those live terms before preparing the wallet because an earlier sale’s process may not describe the next one.

The sale interface may distinguish Standard and Premium LAND or determine how a location is assigned. Treat the displayed sale rules as transaction inputs. Do not infer a specific parcel from the LAND type unless the sale explicitly lets you select that parcel.

Secondary listings

A secondary listing identifies an existing token offered by its current holder. Match its coordinates and token data to the map, then inspect the collection contract on the listed network. The seller’s text, imagery, and claimed neighborhood do not replace these identifiers. Listing availability and payment terms can also change before approval.

Read the wallet prompt as transaction data

The wallet prompt is the final view of what your account is being asked to authorize. Check the active network, requesting contract, amount, operation, and any receiving address shown. A separate token approval may precede the purchase and permit contract spending within the displayed terms. Reject any prompt whose data does not match the prepared purchase, then reopen it only from the intended parcel flow.

Recover without repeating an uncertain transaction

If no wallet prompt appears, first confirm the wallet is unlocked and connected to the expected account. Browser privacy, pop-up, or extension settings can prevent the request from opening without creating an on-chain transaction.

A wrong-network prompt should be rejected. Switch to the network required by the parcel route, recheck the balances and contract, and generate a new request. Do not approve first and hope the interface corrects the network later.

An insufficient-balance message may refer to the purchase asset, gas, or both. Identify the missing balance on the selected network before transferring anything. Funds on another chain will not satisfy that requirement automatically.

When a submitted transaction remains pending, use its transaction hash on the relevant chain explorer. Avoid submitting the same purchase again while the first transaction has an unresolved status, since a delayed confirmation can make the duplicate action unnecessary.

If the network marks the transaction as failed, review its failure details and current parcel availability before trying again. If it succeeded, verify ownership even when the account interface has not refreshed.

Confirm the token before taking another action

Completion requires a successful transaction and the purchased LAND token at the intended wallet address. Compare the confirmed contract, network, token identifier, and holder with the listing or completed sale result. The map or account inventory may update later than the blockchain, so an interface delay does not justify another purchase.

Once those details agree, save the transaction hash and parcel coordinates with the wallet record. That evidence distinguishes a completed transfer from a signed request, pending transaction, or stale listing, and it gives the owner a precise starting point for any later bridge, transfer, or publishing task.