What is Monero's Chainlocks or checkpointing proposal?

Monero does not have an active feature called ChainLocks that makes blocks final through special signatures. If you have seen “Monero ChainLocks” or a “checkpointing proposal” mentioned, it likely refers to a suggested way to limit blockchain rewrites—not an established part of Monero’s mining rules.

What the proposal would try to solve

Monero uses proof of work: miners spend computing power to compete to add blocks to its transaction history, called the blockchain. Nodes—the computers checking the network’s rules—follow the valid chain with the most accumulated work.

Sometimes, a competing chain replaces recent blocks. This is called a reorganization, or “reorg.” Small reorgs can happen naturally when miners find blocks close together.

A powerful attacker could deliberately create a competing chain to reverse a payment they made. Checkpointing aims to put a boundary on those rewrites: once a block is accepted as a checkpoint, nodes would refuse a competing history that removes it, even if that history has more work.

Why “ChainLocks” needs clarification

ChainLocks is the name of a system associated with Dash, a different cryptocurrency. Selected groups of special servers, called masternode quorums, sign messages identifying an accepted block. Those signatures let nodes reject conflicting blocks without waiting for many more mined blocks.

Monero does not have Dash’s masternode system. Bringing a similar idea to Monero would require a new way to decide:

• Who gets to sign a checkpoint?
• How are signers chosen and replaced?
• What happens if signers disappear or disagree?
• How can nodes reject dishonest signatures without trusting a central operator?

So “add ChainLocks to Monero” is not a simple software switch. It would introduce another source of authority alongside mining. Without a specific proposal text, you should not assume the phrase describes one agreed design.

Checkpoints can mean different things

A hardcoded checkpoint is a known block identifier included in node software. It anchors an older part of the chain. That is different from an ongoing system that signs newly mined blocks.

A rolling checkpoint continually moves that boundary forward. Depending on the design, it might rely on signatures, a voting process, or a rule against replacing blocks beyond a certain depth.

These designs have different risks. Simply refusing deep reorgs can leave nodes stuck on different histories after a network interruption. Signed checkpoints instead raise questions about signer control and availability.

Monero’s historical checkpoint mechanisms or synchronization aids should therefore not be mistaken for a live ChainLocks-style finality system. Finality means a transaction cannot be reversed under the system’s rules and assumptions.

What this means for you

As of 2026, you should not treat Monero payments as protected by Dash-style ChainLocks. Monero’s security still rests on proof of work and its consensus rules—the rules nodes independently enforce.

More confirmations, meaning additional blocks built after a transaction’s block, increase confidence against reversal. They do not create an absolute guarantee. Your wallet showing funds as spendable is also not the same as cryptographic finality.

If you are assessing a particular checkpointing proposal, look for its signer-selection rules, failure handling, and adoption status—not just its promise to stop attacks.

The bottom line

“Monero ChainLocks” is not a deployed Monero feature. Checkpointing proposals seek stronger protection against chain rewrites, but their value depends on who controls the checkpoints and what happens when that mechanism fails.