Getting DHN Ready: Why We’re Building DHN v2
Over the first two pieces in this series, we wrote about where crypto regulation is heading and about the standards we believe a serious project should hold itself to. This piece is where those threads meet our own work. We are preparing an upgrade to the DHN token, and we want to explain why — plainly, and before the details arrive. For clarity, we refer to the upgraded contract as DHN v2 in this article. The token itself will continue to be DHN.
Where this comes from
The DHN token has been part of Dohrnii from the start. The contract it runs on today, though, was written for an earlier stage of the project, and it carries one limitation that matters more than any other: it cannot be upgraded. Whatever it does now is, in effect, all it will ever do.
That was a reasonable place to begin. It is no longer enough for where the project is going. As the Academy develops, DHN is intended to support a broader range of platform functionality, which requires a token architecture capable of evolving alongside the product. At the same time, technical expectations around a token — on security and on the ability to adjust to a changing regulatory environment — have moved on since the original contract was deployed.
What DHN v2 is
DHN v2 is, first and foremost, a technical and security upgrade. The central change is that the new contract is built to be upgraded: improvements and new functionality can be added over time, through audited changes, without asking holders to move again.
It is worth being clear about what this is and is not. The specific features we have chosen — upgradeability among them — are our own decisions, made for the project’s own reasons. They are not requirements imposed by MiCA or any other framework; no regulation tells a project to build an upgradeable contract. We are building one because it fits where Dohrnii is heading, and because it gives us room to respond responsibly as expectations evolve.
On transparency
An upgradeable contract is a capable one, and capability invites a fair question: who controls it, and what can they do?
We intend to answer that in writing rather than ask anyone to take it on trust. Alongside the migration, we will publish documentation setting out how the contract is governed — including who can authorise an upgrade, and the terms around any function capable of restricting or affecting an address, such as the conditions under which it applies and the controls placed on it. The contract has also been independently reviewed and audited, and its findings have been addressed. We will include the report with the full migration guide.
None of that is a legal requirement. We treat it as the standard a project of this kind should meet, which is the same standard we set out in the previous article.
Get Dohrnii Labs’s stories in your inbox
Join Medium for free to get updates from this writer.
A note on language: we are approaching this as a compliance-screened migration, by which we mean it goes through our own legal review and preparation before it happens. It is not a status granted or endorsed by any authority.
What it means for holders
For anyone holding DHN, the essential point is continuity. The plan is a one-to-one migration: DHN v1 balances that meet the migration requirements can be moved to the upgraded contract at a 1:1 ratio. The requirements and review process will be explained clearly in the migration guide.
The full details are close. A dedicated migration guide — the exact steps, the timeline, the new contract address, and a clear breakdown of supply — will follow shortly. We will confirm the specifics as the final checks are completed. When that guide is published, one rule will matter above all: use only the contract address and instructions on Dohrnii’s official channels, and treat anything that arrives by direct message as suspect.
What comes next
There is nothing for holders to do today. The purpose of this piece is to give you the picture early, with time to prepare.
Here is the rough timeline. Over the remainder of this month we will publish the full migration guide — the process, the address, the audit report, and the supply figures, in one place — with the migration itself following around the end of August into early September. We will give clear notice before anything begins and confirm each date as it is set.
The short version: DHN is moving to a contract that can grow with the project, the move is designed to be one-to-one, and we will walk through every step before anyone needs to take one.
— Dohrnii Labs
This article is for educational and informational purposes only and is not financial, investment, or legal advice. The features described are Dohrnii’s own design decisions and do not represent MiCA requirements or any form of regulatory approval. Details, timing, and the official contract address will be published separately once finalised and verified. Regulatory frameworks evolve; always verify current requirements with official sources.
More from this series
● Part 1 — MiCA Explained: Europe’s New Rulebook for Crypto-Assets
● Part 2 — Beyond the Baseline: Five Standards We Believe a Serious Crypto Project Should Meet
● Official channels and updates: dohrnii.io
