Plomin upgrade readiness
This page outlines the engineering and ecosystem readiness for the Plomin hardfork upgrade
Intersect and the hard fork working group plays the role of coordinator, as a functional servant-leader on behalf of the community and delivery teams working on hard fork activity. The functional teams within Intersect will work with the various committees, working groups, and delivery teams, relaying information here on the knowledge base. Ultimately the date for the hard fork is directly influenced by the community, the relevant constitutional approval and required on-chain voting.
See anything missing or incorrect on this page? - please email hard-fork@intersectmbo.org or raise an issue via Github/HF-WG-Documentation (or pull request - see how-to)
This page is frequently updated and was last updated 01/20/2025
Core Infrastructure Components
Core infrastructure encompasses all technologies included within the Cardano Node, as well as some key tools.
It is required that all Cardano stake pools and relays upgrade to this node version in order to mitigate a potential DoS attack following a hard fork to Protocol Version 10 ("Plomin" hard fork on mainnet). It is recommended that all other node users upgrade to this version. Node users who do not upgrade put themselves at risk of a potential DoS attack following the hard fork.
Node 10.1.4 is a mainnet-ready release of the Cardano node that is capable of crossing the Chang#2 ("Plomin") hard fork.
It adds safeguards at the mempool level to block specific types of transaction that could lead to a DoS attack following the hard fork.
For further details about cardano-node 10.1.4 please see the release notes for node versions 10.1.1, 10.1.2 and 10.1.3.
Note that, although staking rewards will continue to be earned as usual, in order to withdraw their rewards, following the Plomin hard fork, Ada holders will need to delegate to a DRep, which may be one of the pre-defined options, a single key or a Plutus v3 script. Until the hard fork, rewards may be withdrawn normally. Although following the hard fork, rewards may not be withdrawn unless a DRep is delegated to, rewards will continue to accrue to the Ada holder normally, regardless of whether or not a DRep is delegated to.
Readiness and Updating this Page
Readiness is a self-attestation from the community and ecosystem, facilitated at Intersect, of being technically ready for the Plomin upgrade.
Signalling readiness is important, this allows the on-chain governance, SPOs and the ICC in the case of Plomin upgrade, to make an informed decision voting for the governance action to enact the hard fork.
The community is encouraged to participate in updating and maintaining the status’ and details contained within this ecosystem readiness page.
You can do so by suggesting updates via this Intersect GitHub documentation repository, a simple how to guide provided here. Alternatively, if you find any information on this page incorrect or misleading please email: hard-fork@intersectmbo.org and request an update or correction.
Governance Actions
Governance actions need to be enacted/voted on-chain for the hard fork to take place, you can keep track of the applicable governance actions for Plomin upgrade below.
Metadata for all Intersect governance actions can be found here on the Intersect Gitbook repository.
Plomin Hardfork Action Vote Totals
Stake Pool Operators
Below is SPO vote totals for the Plomin Hardfork Initiation governance action, data provided via Koios.
Summary
The stake pool vote threshold to reach is 51% of total stake to vote yes.
Yes
59.10%
No + Not Voted
40.90%
SPO vote summary last updated: 2025-01-20 00:09:39
Details
Yes
396
7.06b
No
4
60.79m
Abstain
2
38.98m
Not Voted
2173
8.74b
SPO vote total last updated: 2025-01-20 00:09:39
Interim Constitutional Committee
Below is ICC vote totals for the Plomin Hardfork Initiation governance action, data provided via Koios.
The constitutional committee vote threshold to reach is 5 out of 7 constitutional votes (> 66.6%).
Constitutional
0
0%
Unconstitutional
0
0%
Abstain
0
0%
Not voted
7
100%
ICC vote total last updated: 2025-01-20 00:09:39
SPOs
Stake pool operators should upgrade to a supported mainnet node 10.1.4 version in readiness for the hard fork. Below we compare the prevalence of Cardano blocks created by Node versions.
As of January 20th, 2025: 86% of blocks created on mainnet, within the current epoch, where created using the hotfixed 10.1.4 version (which reports as 10.2) Live data can be seen via Cardano explorers such as Pooltool.io
Graph Showing Node Version adoption, up to 2025-01-07. Via Markus on X (@C1cADA_Markus).
Exchanges
Exchange readiness is tracked against the top exchanges by ADA liquidity (as reported by Cexplorer/hfs).
For the latest info on Exchanges by Liquidity please visit: Cardanoscan (source) and Cexplorer.
As of January 20th, 2025, 61.26 % of exchange liquidity has been reported as Ready for Plomin hard fork.
Tooling
Tooling readiness is supported from version Node 10.1.1 compatible releases. Where known release repositories have been added to the Notes section.
Tools
Libraries
Indexers
Higher Level Tooling
Wallets
Wallet readiness is tracked against their integration against Cardano Node versions, as well as self-reported readiness
Light Wallets
Hardware Wallets
Full Node / CLI Wallets
DApps & Projects
DApp and project readiness is tracked against self reported readiness. Although this hard fork will remain in the Conway era DApp developers should refer to the latest release notes and confirm readiness for the intra-era hard fork.
DApps listed on this page are self-attested by the community, to add your DApp please email hard-fork@intersectmbo.org or raise a pull request to this public repository via Github/HF-WG-Documentation (see how-to)
Axo
Ready
Danogo
Ready
DripDropz
Ready
Fluid Tokens
Ready
Genius Yield
Ready
Levvy Finance
Ready
Minswap
Ready
NEWM
Ready
Snekdotfun
Ready
Splash
Ready
Summon
Ready
Tempo
Ready
USDM
Ready
Wanchain
Ready
DApps listed on this page are self-attested by the community, to add your DApp please email hard-fork@intersectmbo.org or raise a pull request to this public repository via Github/HF-WG-Documentation (see how-to)
Last updated
