Funded tokens
At mainnet, every location has a defined $MAPF reward. Nothing is minted at check-in; the vault is funded in advance by protocol revenue.
MAPFOLD is a living atlas shaped by the people who explore it. Every verified public place becomes another page worth walking toward.

Search, tap the map, use GPS, or paste a Maps link. You confirm one server-verified public place—never three unrelated fields.
Submit only one public place. Within each 1 km area, up to 3 eligible points will join the first map. If more than 3 qualify, 3 will be chosen at random after intake closes. Duplicate or abusive submissions are invalid.
Confirmation accepts only a signed server result. Public, legal, safely accessible places only. Never submit a home.
Duplicate or abusive submissions are invalid.
If more than 3 qualify nearby, 3 are chosen at random.
Within 12 hours after intake closes
The current MAPFOLD release accepts and verifies founding public places through the server. $MAPF wallet claims and location payouts remain locked until the official contracts are deployed.
At mainnet, every location has a defined $MAPF reward. Nothing is minted at check-in; the vault is funded in advance by protocol revenue.
Daily draws come only from reviewed parks, commercial districts, exhibitions, and public cultural spaces.
Distance, GPS accuracy, movement history, and device attestation must all pass before a production claim signature is issued.
This is the planned mainnet flow. It will open only after the contracts, verification service, and payout indexer are ready.

After launch, the map will publish locations selected from the reviewed public-place pool.
The production verifier will check position accuracy and movement before accepting an on-site action.
After deployment, a valid server voucher can authorize a payout from the funded vault.
No $MAPF contract address is shown before official deployment. At launch, founding-place intake opens for six hours, followed by verification and a target mainnet release within 12 hours after intake closes.
The verified contract address will be posted on this website and the official X account first
Every eligible public-place submission joins the founding review batch during the opening window
Canonical places, coordinates, density limits, duplicates, and public access are checked before release
The production map is targeted within 12 hours after founding intake closes, subject to final checks
The creator fee activates with the official token launch. The 70% revenue allocation begins only after the MAPFOLD game mainnet launches and funds recurring market buybacks and permanent burns.
The map can only release what the vault can cover. No borrowing. No over-issuance. Buyback-and-burn activity is counted only when it is verifiable onchain.
Every visible point is loaded from the verified intake log. Newly confirmed submissions appear automatically without a frontend redeploy.
Map points are read from the intake API.
Canonical public places currently stored by the server.
If more than three qualify nearby, three are selected after intake.
Submit one exact Google Maps or Apple Maps place link for review.
After the MAPFOLD production game launches, 70% of project revenue is allocated to $MAPF market buybacks and permanent burns. Nothing is counted until the transaction is verifiable onchain.
After the MAPFOLD game mainnet launches, this share of project revenue is allocated to ongoing market buybacks and permanent burns.
Proof appears after confirmed executionThis policy is not a promise of token price or return. A burn is displayed as completed only after its onchain transaction confirms.
These rows are public fields from the intake server. No wallet, reward amount, transaction hash, or payout is shown before one actually exists.
| Place | Region | Batch | Received | Review |
|---|---|---|---|---|
| No verified submissions have been received yet. | ||||
Every $MAPF purchased by the project's announced dev buy wallet is designated for permanent burn and will not be redistributed. A burn is reported as completed only after its onchain transaction confirms.