Common smart contract mistakes in Decentraland land leasing
Smart contract vulnerabilities like faulty calculations and token approval issues caused numerous security incidents, including a $223 million loss from the Cetus DEX hack. Developers face risks from reentrancy, access control errors, and decimal precision glitches during deployment.
The Decentraland DAO manages the ecosystem through a system of proposals that require community voting to pass. Users gain voting power (VP) based on their total balance of MANA, LAND, and NAME. This power dictates the influence of individual wallets over the platform. Development activity across major blockchain ecosystems shows a significant slowdown in 2026. Weekly commits to open-source repositories fell from 871,000 to 218,000, which represents a 75% decline. Active developers decreased from 8,700 to 4,600, marking a 50% drop. In the EVM ecosystem, development activity plummeted by more than 55% over the last three months, with active developers falling to 4,000. Ethereum itself saw a 54% decline in activity over the last three months, with weekly active developers dropping to around 2,800. The crypto market crash that started on October 11, 2025, contributed to low confidence. AI tools help programmers work more efficiently, which reduces public updates even when projects move forward. The crypto industry is moving into an app era where projects launch as full applications on top of infrastructure, combining multiple layers from the start. Can users maintain influence as development activity continues to drop?
Smart Contract Mistakes
Smart contract flaws present a direct danger to virtual land holdings and MANA assets. Faulty calculations caused 12 identified incidents in smart contract hacks, involving errors in collateralization and reward distributions. Unprotected minting functions in access control failures led to 3 specific incidents. Applications requesting permission to spend tokens through token approval issues resulted in 7 incidents.
| Vulnerability Category | Identified Incidents |
|---|---|
| Faulty Calculations | 12 |
| Token Approvals | 7 |
| Oracle Issues | 4 |
| Reentrancy | 4 |
| Access Control | 3 |
| Rebasing Tokens | 3 |
Developers struggle with logic bugs or improper function access, which caused issues like the Zoth minting function manipulation in March 2025, where an attacker created tokens freely. If a developer uses an incorrect decimal scaling for tokens, the error in code can drain assets. You should check if a platform uses audited libraries like OpenZeppelin instead of custom code to avoid these errors. The Cetus DEX hack in May 2025 shows that a missing overflow check can cost $223 million, leaving users without recourse. Logic errors and flaws in business logic enable exploits that target specific functions. Reentrancy, where a contract calls an external contract before updating its own state, allows recursive exploitation. Examples include the Midas Capital and Orion Protocol hacks. Oracle issues, involving faulty data or manipulable pools, affected projects like Mycelium and BonqDao. Access control errors, such as an unprotected mint function, allow attackers to manipulate contract logic, much like the Zoth incident in March 2025 where an attacker created tokens freely in the system.
Implementation and Security
Successful metaverse development involves using the Decentraland SDK, Builder, and Marketplace to manage virtual worlds. Security remains a priority because once a contract deploys to the blockchain, the code stays immutable. Developers face challenges when integrating tokens with changing supplies, because rebasing tokens can lead to unexpected deviations in value. Reentrancy errors, where a contract gives up control flow to another contract before updating its state, remain a frequent threat. For example, the DAO hack in 2016 used a reentrancy bug to steal 3.6 million ETH. Access control issues, like an unprotected mint function, allow attackers to manipulate contract logic. Errors in decimal precision, such as the zkLend glitch in February 2025, cause significant losses that impact users globally. A developer’s mistake in access control or function visibility can have large consequences for the entire ecosystem. Most developers skip high quality audits before deployment, which leads to many hacks. To prevent these, developers can use static analysis tools like Slither to identify uninitialized variables or missing access controls. Fuzzing tools like Echidna generate random inputs to test contracts under various conditions, while symbolic execution with Mythril explores all possible execution paths to uncover issues. Using the checks-effects-interactions pattern helps prevent reentrancy. Developers should also use frameworks like Foundry to combine fuzzing, static analysis, and gas profiling. Maintaining simple contracts helps reduce risk.
Join the discussion