Skip to content
BitcoinToolkit

Decentraland (MANA): MANA, LAND, Names and Worlds Are Separate Assets or Rights

Decentraland is a virtual-world platform with tokenized LAND, names and creator items. MANA is its fungible ecosystem token, while the DAO coordinates selected community-controlled contracts and policies. This page focuses on mANA, LAND, Names and Worlds Are Separate Assets or Rights and the checks users need before using the protocol or evaluating the token role.

Use Decentraland assets or governance while understanding network, ownership and DAO boundaries.

Subject:
Decentraland
Market mode:
Snapshot Only
Fee asset:
ETH / POL
Timezone:
UTC

This page does not sell LAND, enter a World, verify a wearable, vote in the DAO, promise creator income, recover an account or provide asset valuation.

Content ownership: BitcoinToolkit Editorial Team Technical references: Official protocol and developer documentation. Review approach: Technical explanations are checked against primary sources and updated when the network or asset changes. Last content review: Data integration last tested:

MANA, LAND, Names and Worlds Are Separate Assets or Rights

A token balance is not a virtual parcel or published scene.

Currency, property and content

MANA is an ERC-20 ecosystem currency. LAND and Estates are coordinate-based NFTs in Genesis City. Names are ENS-linked assets that can provide identity and voting power. Worlds are personal spaces associated with eligible names and exist separately from LAND on the public map.

Verify contract, token ID, coordinates, name and listing before purchase. Scene content referenced by LAND can change while ownership stays onchain. Owning a wearable or parcel does not automatically grant commercial rights to every design or guarantee platform traffic and rental income.

Decentraland Risks Before Completion

LAND and many premium assets remain Ethereum-oriented, while wearables and emotes often use Polygon.

Choose the network for the item

Decentraland marketplace data distinguishes Ethereum and Polygon items. MANA representations and NFT contracts must match the listing network. Some eligible Polygon actions can use a DAO-funded meta-transaction service, but normal host-chain gas still exists and sponsorship can be limited or paused.

Check network, contract, price asset, seller and approval target. Keep ETH or POL when sponsorship is unavailable. Do not transfer LAND to a Polygon wearable route or assume an item is official because it renders in-world. Save marketplace order and blockchain transaction records separately.

DAO Voting and Onchain Execution Are Distinct Steps

Community voting uses Snapshot while selected binding actions require controlled execution.

Voting power and committees

MANA, LAND and Names can contribute voting power under DAO rules. Proposals and votes are recorded through offchain Snapshot mechanisms, then binding actions are executed by a DAO Committee multisig subject to Security Advisory Board controls and delays. The DAO controls selected contracts and funds, not every Decentraland system.

Read proposal category, voting-power snapshot, threshold and implementation path. A passed signal proposal may not change a contract, and a committee transaction can be delayed or canceled. Do not assume holding liquid MANA alone automatically casts a vote or that the DAO can modify the MANA token contract.

Choose the Next Decentraland Check

Match the checklist to a player, buyer, creator or voter. Confirm the item network and contract before relying on an in-world preview, marketplace listing or governance label.

Asset and governance checklist

Players should verify wallet and item compatibility. Buyers should check network, contract, coordinates and listing. Creators should preserve source rights and deployment records. Voters should verify proposal scope, snapshot and execution. Every user should distinguish platform account access from wallet control.

Revoke unused marketplace approvals and ignore fake asset claims. Use Ethereum or Polygon tools for the network holding the item and keep transaction evidence for marketplace support. Account recovery cannot reverse a self-custody transfer.

Browse wallet tools

Decentraland Operating Context

The MANA result needs context

Ethereum records LAND and high-value assets, Polygon supports many wearables and lower-cost actions, content servers deliver world scenes, and Snapshot plus multisig execution implements DAO decisions.

A Decentraland transaction can execute successfully while the application state, contract permission or later exit remains wrong for the user's goal. MANA is the ecosystem asset shown in the snapshot. ETH or POL pays gas unless an eligible transaction is sponsored.

What Decentraland users should verify and why this design differs

Marketplace, sponsorship and governance rules can change. NFT ownership does not guarantee platform traffic or income.

For Decentraland, the practical sequence is Choose network, Fund fee asset, Review action, Execute, Check finality. Confirm the official destination and current network, then inspect the final balance, position, receipt or documented exit state that actually completes the task: Use Decentraland assets or governance while understanding network, ownership and DAO boundaries.

Decentraland Network use FAQ

Is MANA the same as LAND?

No. MANA is fungible; LAND is a parcel NFT.

Are all Decentraland items on one network?

No. Ethereum and Polygon assets coexist.

Does a Snapshot vote execute every change automatically?

No. Binding actions can require committee multisig execution and oversight.

What pays transaction fees when using Decentraland?

Host-chain gas asset (ETH / POL) pays the applicable network fee. Verify the selected network before signing because a later approval, bridge, claim or exit can require another transaction.

Known Limitations

Market Data Methodology

The page uses a CoinGecko aggregated MANA/USD snapshot. No exchange chart is rendered for this entity.

Market Snapshot Source
CoinGecko aggregated market data (MANA/USD)
Cache
Snapshot cache is approximately 60 seconds.
Failure Handling
Verified cached data is labeled Cached or Delayed. Missing values remain unavailable.
Snapshot Status
Fresh
Report Issue
Report a market-data problem →

Technical Sources

Selected primary sources support the operational explanations. Market-provider attribution remains separate.

Editorial Information

Verified technical content, reviewed sources and update history.

Published
Last Review
Data Verification
Sources
Official documentation