Decentralised News · 2027 planning series · Reviewed 22 November 2026
What Matters
A Decentraland rental reaching its end date does not, by itself, return the LAND NFT or remove the selected scene operator. A useful handover record distinguishes three outcomes: the NFT returns to the recorded lessor; the lessor changes the operator while the NFT remains in the Rentals contract; or a new rental executes. Each outcome needs its own transaction and state evidence. A calendar reminder can start that review. It cannot complete it.
A studio rents a parcel for an exhibition. The closing date passes, the project team archives its campaign, and the owner expects to resume control. Which account can deploy a replacement scene? Where is the NFT? If the asset is an Estate, do individual parcels still have their own operators? Those questions determine whether the next project can begin.
This guide treats rental handover as an operational decision. It compares the official Marketplace rental documentation with the published contract sources, then supplies a local worksheet for costs and declared evidence. It does not establish demand for a parcel, predict MANA prices or calculate rental returns.
The Signal
Decentraland’s 11 October 2026 incident report describes an offchain listing-status mismatch. Its documented repair matched the asset contract, token ID and lessor as well as the signature. The report says the affected owner’s onchain listing remained valid and no owner funds moved. The lesson for a handover record is specific: a marketplace status label and an identified onchain transition are different evidence. This report documents a repaired issue, not a claim that today’s listings remain affected.
1. Separate custody, tenancy and scene authority
Start with three names: the recorded lessor, the tenant and the chosen deployment operator. They can represent different accounts. A studio might pay rent while appointing a production contractor to publish its scene. The account paying MANA should therefore not be assumed to be the account currently exercising content permissions.
The Rentals repository’s lifecycle explanation describes the NFT moving into the Rentals contract when a rental starts. That custody arrangement matters when reading an NFT explorer: the contract appearing as token owner does not identify the tenant, and it does not mean the lessor has sold the asset.
Keep two meanings of “operator” apart. ERC-721 defines token approvals and operators that can manage NFTs for an owner. Decentraland adds content-update authority. The LAND source separately tracks the per-token update operator and owner-level update managers. Content authority alone is not evidence of NFT transfer authority; an account may separately possess both.
DN’s practical rule is to write the intended outcome before checking addresses. “Owner receives the NFT, the previous project loses content access, and our current production account may publish” is a reviewable objective. “Control returned” hides three separate assertions.
2. Read the right clock
A listing’s expiration determines how long its signed rental offer can be accepted. The rental duration determines the period bought when the rental executes. The Marketplace guide treats these separately and describes payment upfront. An expired listing is not evidence that an already executed rental has ended.
The pinned Rentals source evaluates activity against the block timestamp and stored rental end date; equality still counts as active. The worksheet deliberately asks for the previous lease’s observed status rather than converting a local date into a control result.
For an actual review, record which chain observation supports the end-date conclusion, and which later observation supports the handover. If a new rental has already started, the current rental can be active even though the preceding one ended. Label those records separately. Otherwise a perfectly valid new tenancy can be mistaken for an old lease that never expired.
A useful reminder has an owner and an action: review the completed rental, decide which transition is wanted, and check the result afterward. A reminder saying “access expires automatically” embeds the very assumption that needs verification.
3. Choose the transition you actually want
The repository documentation distinguishes the tenant’s ability to change the operator during an active rental from the lessor’s ability to change it afterward. The previously selected operator can remain able to deploy after expiry. Expiry changes who may direct the next operator change; it does not necessarily perform that change.
| Intended outcome | Evidence to collect | What remains a separate question |
|---|---|---|
| Return the NFT to the recorded lessor | Successful claim for the identified asset; subsequent ownership and rental-state reads | All relevant content permissions, including Estate child parcels |
| Change the operator while keeping rental custody | Successful lessor-directed operator change after expiry; current operator and custody reads | The NFT has not returned to the lessor merely because the desired operator appears |
| Begin a new tenancy | Executed rental matching the asset and parties; new rental terms and intended operator | A new listing alone is not an executed rental |
In the reviewed implementation, claim checks that the caller is the recorded lessor and that the asset is no longer rented, then safely transfers the NFT back. Its operator-changing entry point is named setUpdateOperator; the README uses older setOperator shorthand. Use the applicable deployment’s interface rather than copying a historical function example.
The published rental lifecycle design permits re-rental without an intervening claim. That can suit an owner moving directly between tenants, but it changes the success criterion: the desired result is a correctly recorded new tenancy and operator, not temporary owner custody. A renewed offer, a signed listing and a pending transaction are all intermediate states.
There is also an extension case. The published lifecycle permits an ongoing rental to be extended with the same lessor and tenant. The worksheet models handover after the previous lease ends; it does not classify that same-party extension. Keeping this boundary explicit avoids labeling a permitted extension as a failed post-expiry transition.
4. An Estate needs a parcel-level permission review
The Estate source resets the Estate’s own update operator on transfer and exposes separate methods for internal LAND operators. Those internal parcels are not all transferred merely because the Estate token changes owner. The Rentals source comments and methods explicitly address remaining internal operators and let the appropriate rental party clear or replace them.
This changes the acceptance test for a multi-parcel project. A returned Estate NFT is useful custody evidence. It is insufficient evidence that every relevant content permission has the intended final value. Record the Estate’s composition at the observation point, identify the parcels included in the review, and retain unresolved status for any parcel not checked.
For example, a project may use one contractor for the Estate-wide scene and another for a single parcel. Replacing the first contractor’s role does not prove the second contractor’s role changed. The appropriate response is a targeted permission reconciliation, with the affected parcel identified, rather than a broad statement that the project has been fully offboarded.
Also review separately granted update-manager and NFT-transfer permissions where relevant. Finally, keep scene hosting, source repositories and production credentials in the operational handover. This article’s onchain checks cannot certify those offchain systems. A narrowly accurate record is more useful than a universal “all access removed” label.
5. A contract wallet has two different compatibility questions
For an externally owned account, a conventional signature can be checked against its signing address. ERC-1271 instead lets a contract account validate a signature through its own policy. That policy can depend on state, time or authorized signers. A historical valid signature is therefore not a promise that the same wallet configuration will approve a later action.
The second question is asset receipt. ERC-721 safe-transfer behavior requires a receiving contract to return the expected receiver response. Decentraland’s wallet guidance specifically connects this requirement to recovering LAND through claim. Signature validation and successful NFT receipt are separate capabilities.
Before committing a contract-wallet rental workflow, have its administrator establish who can authorize the listing, who can submit the eventual owner action, and whether the receiving wallet supports the required NFT receipt. Preserve the applicable wallet version and evidence. Naming a wallet brand or showing that it can hold some other token does not answer those questions.
These are preflight decisions, not instructions to send LAND manually to a contract. The worksheet neither constructs transactions nor diagnoses a stranded asset. If a claim fails, its result stays unresolved until the actual failure and subsequent state have been investigated.
6. Bind the record to a network, asset and observation
The official address registry, reviewed on 22 November 2026, lists the Ethereum-mainnet Rentals proxy as 0x3a1469499d0be105d4f77045ca403a5f6dc2f3f5. It separately lists test-network deployments. This is a registry reference, not a destination to use without checking the current application and network.
Our source review pins Rentals to commit b51989f and LAND/Estate to c820aa1. Repository source, a deployment registry and the implementation serving a proxy at a particular block are different records. This article has not attested that current deployed bytecode equals those source revisions, or inspected a reader’s particular token.
For a consequential handover, keep the network, rental contract, asset contract, token ID, recorded parties, relevant transaction and observation block together. Add the intended final operator state and, for an Estate, the parcel list. A colleague should be able to tell what was checked without reconstructing the record from screenshots.
Use the documented listing-match repair as a discipline for evidence: match the asset and parties, not just a familiar signature or an attractive “executed” label. A successful transaction for a different token answers the wrong question. A successful transaction followed by an unknown permission read answers only part of the right one.
7. Budget the rental without turning it into a yield forecast
The basic tenant charge is the accepted MANA price per day multiplied by the chosen days. The payment implementation splits that gross charge between the lessor and the protocol’s fee recipient. We do not insert a current fee percentage or infer the owner’s net receipt. Those require the applicable contract parameters and actual payment evidence.
The DN worksheet keeps three amounts separate: the gross rental charge in MANA, the tenant’s declared transaction budget in ETH, and an optional owner-action budget in ETH. Enter the tenant budget for the transactions your workflow actually requires, including an allowance transaction if needed. The owner’s later claim or operator-change reserve belongs to a different payer.
Optional conversion expresses these amounts in a user-named common unit using declared MANA and ETH rates. It is arithmetic for comparing a budget, not a live quote or a statement that the balances can be exchanged at those rates. The separate-unit result remains useful when no conversion assumption is available.
Excluded costs include creating and maintaining the scene, hosting, external contractors, taxes, exchange spreads, failed-transaction costs beyond your entered reserve, and any other unentered charge. A rental payment also says nothing about attendance, advertising sales or future demand. Those would need a separate business case.
Worked case: a studio closes its exhibition
Synthetic example. Studio A plans a 30-day rental at 18 MANA per day. It allocates 0.006 ETH for its own rental-related transactions. The owner separately reserves 0.004 ETH for a post-expiry action. For illustration only, the project uses 0.30 common units per MANA and 2,000 common units per ETH.
The gross charge is 540 MANA. The studio’s converted planning amount is 162 plus 12, or 174 common units. The owner’s action reserve is 8 common units, reported separately. If the studio revises its transaction budget to 0.020 ETH, its amount becomes 202 common units. None of those numbers estimates profit or owner net rental income.
Now the previous rental has ended according to the declared chain observation, but the owner’s claim is pending. The worksheet reports no completed handover. The prepaid rent and the passage of 30 days do not change that result. If claim later succeeds and custody is reported back with the lessor, the custody finding can advance while an unknown operator review remains unresolved.
Change the asset to an Estate. Even with a matching top-level operator, unknown child-parcel permissions keep the permission finding open. Alternatively, choose re-rental: a newly listed offer still produces no completed transition. Only declared successful execution, matching rental-state evidence, rental-contract custody and the intended permission state support a completed new-tenancy record.
Finally, consider the owner choosing only an operator reassignment. A matching result supports the narrower statement that the desired operator was recorded while the NFT stayed in rental custody. It does not support “NFT returned.” That distinction is the purpose of the worksheet’s separate findings.
DN LAND Rental Handover and Cost Worksheet
Change the illustrative assumptions below. This worksheet runs locally in your browser. It records your declarations; it does not verify evidence, connect to accounts, submit instructions or grant approval.
The initial numbers are synthetic. Unknown evidence remains unresolved. Downloads contain the values you enter; use aliases and avoid private or identifying information.
How to use the record
Enter an alias and a public evidence reference or clearly labeled synthetic scenario. Select the previous lease’s phase, intended transition and execution stage. For a completed action, record whether the receipt and subsequent state match the full identity of the asset and parties. Then supply custody and permission findings independently.
“Matches” means the entered evidence agrees with your stated final policy; it does not require every operator to be the owner’s address. A deliberate new tenant might appoint the same contractor. Conversely, a cleared direct operator field does not settle an Estate’s child-parcel review or other delegates. Unknown evidence is retained, and a conflict is not averaged into a score.
Budget fields are conditional. A missing rate does not prevent a separate-unit calculation. An unknown owner budget is not zero. Explicit zero amounts remain declarations, not observations of free service. The worksheet is a rounded planning model and does not reproduce token-base-unit transaction arithmetic.
DN Alpha Thesis
The useful advantage in a virtual-land rental is a cleanly specified transition. Teams that distinguish the lease clock, NFT custody and content authority can assign the right follow-up action and identify missing evidence before a new project depends on it. A single “expired” badge cannot carry those decisions. Separate findings make the handover inspectable.
Methodology, limits and corrections
Sources were reviewed on 22 November 2026. The article combines official documentation, pinned source-code inspection, standards and a published incident report. The decision method and worked case are DN analysis. We did not execute a rental, inspect a private wallet, test a particular deployment or observe the example’s costs. Documentation describes intended behavior; an actual handover requires current deployment and transaction evidence.
The worksheet evaluates declarations locally. It performs no network lookup, wallet connection, signing, asset transfer or independent permission verification. Its completed-state labels describe the supplied record, not a security certification. New implementations, wallet changes, later transactions and revised Estate composition can require a new review.
Disclosure: the links here are research citations and related DN reading; this worksheet contains no affiliate tracking links. Corrections: send the affected passage, source URL and relevant public observation to press@decentralised.news.
Related DN research: for physical buildings and investor claims, see AI and real-estate tokenization: legal wrappers, valuation and cash flows. For permission to delegate gameplay itself, see six checks before delegating a play-to-earn game to an AI. Those decisions remain separate from the rental handover described here.
Sources and evidence register
Primary sources reviewed on 22 November 2026. The article distinguishes documented facts, DN analysis and synthetic examples. Recheck changeable rules and configurations before acting.
- Decentraland Docs: Rentals — Current public guidance reviewed 22 November 2026: listing and rental periods, upfront MANA, post-expiry operator persistence and contract-wallet receipt requirement.
- Decentraland Rentals repository README — Lifecycle explanation for custody, operator reassignment, claim, re-rental and same-party extension. README method shorthand is not treated as the deployed ABI.
- Rentals.sol — pinned source revision b51989f — Source inspection: rental activity boundary, recorded lessor/tenant checks, claim, batched setUpdateOperator, re-rent/extension and internal Estate operators. No current deployed-bytecode attestation.
- LANDRegistry.sol — pinned source revision c820aa1 — Content update authorization, owner-level update managers and reset of the direct LAND update operator on transfer.
- EstateRegistry.sol — pinned source revision c820aa1 — Estate-level operator reset and separate methods for internal LAND operators; a top-level transfer is not a complete child-permission review.
- Decentraland deployment address registry — Mainnet and test-network address namespaces reviewed 22 November 2026. Registry identity does not attest current proxy implementation or a particular asset.
- ERC-1271: Standard Signature Validation Method for Contracts — Contract-account signature validation may depend on wallet policy, state and time; separate from NFT receipt support.
- ERC-721: Non-Fungible Token Standard — Token ownership and approval interfaces, safe-transfer receiver behavior and the distinction between NFT approvals and application-specific scene roles.
- Decentraland RCA: Rental listings matched by signature alone — Reported 9 October 2026; documented mitigation and solution 11 October 2026. Offchain status mismatch and asset/party matching repair; not evidence of an unresolved current exploit.
- Decentraland ADR-172: Rentals — Lifecycle design dated 10 January 2023. Distinguishes re-rental after expiry from extension during an ongoing rental with the same parties; historical design evidence, not a current deployment attestation.
Frequently asked questions
Does a Decentraland rental end automatically return the LAND?
The rental period can end while the NFT remains in Rentals custody and the selected operator still has content authority. Record the later claim, operator reassignment or executed new rental separately. An expired date alone is not a completed handover.
Can the owner change the operator without claiming the NFT?
The published Rentals lifecycle allows the recorded lessor to change the operator after the rental ends while the asset stays in rental custody. This is different from receiving the NFT back. Check the applicable contract interface and resulting state.
Must LAND be claimed before it can be rented again?
The published lifecycle permits re-rental after expiry without an intervening claim. A signed or displayed listing is not enough: the new rental must execute. The separate same-party extension case during an ongoing rental is outside this worksheet.
Does returning an Estate remove every parcel operator?
A top-level Estate transfer is insufficient evidence of complete permission removal. Internal LAND parcels have separately managed operators. Review the intended permissions for the relevant parcels and preserve unknown status for anything not checked.
Why can a smart wallet need both ERC-1271 and ERC-721 support?
ERC-1271 concerns validation of signatures for a contract account. Recovering an NFT through a safe transfer separately requires compatible receiver behavior under ERC-721. Success at signing a listing does not, by itself, establish successful future asset receipt.
Does the worksheet verify a rental or forecast its return?
No. It classifies your declared handover evidence and calculates a limited cost budget. It makes no wallet connection, submits no transaction and estimates no revenue, occupancy, current token price or owner net rental income. Unknown evidence remains unresolved.