Developers behind the DOM protocol have moved quickly to address governance gaps identified in a recent self-audit, deploying fixes within hours of disclosure while rolling out a new token burn feature.
The issues were found in the dom_staking component, where several functions lacked proper access controls. These included reconfigureToken, forceDistribute and resetDistributionTimer. While the vulnerabilities did not affect the protocol’s fixed supply of one million tokens, they could have been used to disrupt staking activity or alter the timing of token emissions.
The team publicly committed to resolving the problems within 48 hours. According to an update, the patches were completed in around four hours. Access to the affected functions is now restricted to a single authorised deployer identity, with all unauthorised attempts rejected.
Testing was carried out on the live network using both authorised and unauthorised identities. Developers reported that legitimate calls continued to function as expected, while attempts from other accounts were blocked. They also said that system data, including staking balances, minted tokens and burn totals, remained unchanged following the upgrade.
The update comes as the project continues to emphasise its fixed supply model. Previous audits confirmed that token issuance is capped at one million, enforced through both token and staking logic. A planned future step involves transferring control of the token contract to an inaccessible address, which would prevent further changes and lock the supply permanently.
Alongside the security update, the team introduced a new feature aimed at increasing token burns. The “Baptism by Fire” mechanism allows certificate holders to assign a unique name to their asset by permanently removing a set number of tokens from circulation. Each name must be a single, unique word and cannot be changed once assigned.
Early activity suggests initial demand, with several names already claimed shortly after launch. The feature also ties into the protocol’s broader burn mechanics, where tokens are removed through various interactions. Developers have highlighted the potential impact on supply if adoption continues, though actual outcomes will depend on user participation.
Additional updates include a leaderboard tracking activity tied to the platform’s gaming features and a restructured marketplace interface. These changes are part of ongoing efforts to expand user engagement while maintaining core mechanics.
While the rapid patch deployment may reassure some users, governance and security remain areas of close scrutiny across decentralised projects. Quick fixes can address immediate concerns, but longer-term confidence often depends on consistent oversight and transparent processes.
For now, the team is positioning the latest update as evidence of both responsiveness and commitment to its roadmap. The combination of security adjustments and new features reflects a development cycle that continues to evolve alongside user activity.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion