We want to share an important update regarding the future of Mimir.
After careful consideration, Mimir will enter a Sunset phase, beginning with a gradual reduction in scope.
What does “Sunset” mean?
Sunset means that Mimir will freeze feature development and move into minimal maintenance mode, followed by a gradual service wind-down when continued operation is no longer sustainable.
This approach is intentional and designed to provide users with clarity and sufficient time to prepare.
Sunset Timeline
Stage 1 – Network Scope Reduction
-
Mimir will not continue to support any bug fix
-
No new features will be developed
Stage 2 – Service Wind-down
-
Stage 2 will begin only when continued operation is no longer sustainable
-
Remaining services will be gradually removed
-
The project will transition toward full archival status
No fixed date is set for Stage 2. We will communicate clearly before any major changes take effect.
What does this mean for users?
-
No new functionality will be added going forward
-
Users should begin planning operational adjustments
-
Multisig and proxy operations can continue via Signet or Polkadot JS
About the future
Within our capacity, we will make a best-effort attempt to continue maintaining core functionality for the primary supported networks using our own resources, for as long as this remains sustainable.
Why are we taking this step?
Over recent months, we have followed guidance to significantly reduce scope, lower budgets, and cut future operating costs. Despite these efforts, retroactive support for work already delivered was ultimately not approved, making long-term sustainability increasingly difficult.
Background timeline (for transparency)
To provide context, we are sharing a brief, factual timeline of events leading to this decision:
-
Nov 25, 2025 – We contacted Web3 Foundation to introduce a new proposal. No response was received.
-
Dec 1, 2025 – Proposal #1799 was submitted. Later the same day, updated W3F guidelines were published.
-
Dec 4, 2025 – During the AAG meeting, W3F became aware that we had difficulty reaching the relevant contacts and proactively followed up.
-
Dec 18, 2025 – We were informed that the proposal could not proceed as it was not milestone-based.
-
Dec 22, 2025 – A new milestone-based proposal was submitted. We were informed that review would resume after the holiday period.
-
Jan 7, 2026 – Feedback indicated that the proposal scope was considered too large.
-
Jan 8, 2026 – We resubmitted with a significantly reduced budget, cutting the original request by nearly half.
-
Jan 12, 2026 – We were formally notified that funding could not be continued.
This timeline is shared to explain the context of our decision, not to assign blame.
Project status
-
The Mimir project will be archived in a clean and transparent state
-
Code and documentation will remain available in archived form
A note to the community
Mimir was built because we believe in Polkadot and in the value of community-built infrastructure. That belief has not changed.
We will continue to act responsibly toward users and the ecosystem for as long as we reasonably can. This sunset marks a pause — not a loss of commitment — and we hope it also creates space for reflection on how critical infrastructure can be sustained in a healthy and collaborative way.
Thank you for your understanding and support.
— The Mimir Team
