What changed, and why it matters
This is a routine version-bump and checkpoint update for the Monero cryptocurrency software. It updates the recommended software version from v0.18.5.3 to v0.18.5.4, refreshes the built-in list of trusted blockchain checkpoints to a newer block height, and updates the corresponding hash that verifies those checkpoints. These changes are part of normal maintenance and do not, by themselves, fix a known security vulnerability.
Treat as a normal maintenance release. Users running Monero nodes should upgrade to v0.18.5.4 to stay current with the latest checkpoints and recommended release. No urgent security patching action is indicated by this commit alone.
Security signals we found
Hardcoded blockchain checkpoint update to a newer block height
Hash-of-checkpoints constant updated to match new checkpoint data
No code logic changes, memory safety fixes, cryptographic fixes, or input validation changes visible in the diff
Evidence from the diff
The commit merges PR #11554 titled ‘src: update checkpoints to match v0.18.5.4’. Changes are limited to: (1) README.md version references updated from v0.18.5.3 to v0.18.5.4; (2) src/blocks/checkpoints.dat binary updated (contents not shown); (3) src/checkpoints/checkpoints.cpp: the latest ADD_CHECKPOINT2 entry moved from height 3774800 to 3784000 with a new block hash and cumulative difficulty; (4) src/cryptonote_core/blockchain.cpp: the expected_block_hashes_hash constant updated to match the new checkpoints.dat. These are standard hardcoded checkpoint updates used to accelerate initial blockchain sync and anchor consensus on the canonical chain.
Changed components
README.md documentationsrc/blocks/checkpoints.datsrc/checkpoints/checkpoints.cppsrc/cryptonote_core/blockchain.cppInspect captured patch +7 / −7
### README.md
@@ -121,8 +121,8 @@ Dates are provided in the format YYYY-MM-DD. The "Minimum" is the software versi
| 1978433 | 2019-11-30 | v12 | v0.15.0.0 | v0.16.0.0 | New PoW based on RandomX, only allow >= 2 outputs, change to the block median used to calculate penalty, v1 coinbases are forbidden, rct sigs in coinbase forbidden, 10 block lock time for incoming outputs
| 2210000 | 2020-10-17 | v13 | v0.17.0.0 | v0.17.3.2 | New CLSAG transaction format
| 2210720 | 2020-10-18 | v14 | v0.17.1.1 | v0.17.3.2 | forbid old MLSAG transaction format
-| 2688888 | 2022-08-13 | v15 | v0.18.0.0 | v0.18.5.3 | ringsize = 16, bulletproofs+, view tags, adjusted dynamic block weight algorithm
-| 2689608 | 2022-08-14 | v16 | v0.18.0.0 | v0.18.5.3 | forbid old v14 transaction format
+| 2688888 | 2022-08-13 | v15 | v0.18.0.0 | v0.18.5.4 | ringsize = 16, bulletproofs+, view tags, adjusted dynamic block weight algorithm
+| 2689608 | 2022-08-14 | v16 | v0.18.0.0 | v0.18.5.4 | forbid old v14 transaction format
| XXXXXXX | XXX-XX-XX | XXX | vX.XX.X.X | vX.XX.X.X | XXX |
X's indicate that these details have not been determined as of commit date.
@@ -284,7 +284,7 @@ Tested on a Raspberry Pi 5B with a clean installation of Raspberry Pi OS (64-bit
```bash
git clone --recursive https://github.com/monero-project/monero.git
cd monero
- git checkout v0.18.5.3
+ git checkout v0.18.5.4
```
* Build:
@@ -343,10 +343,10 @@ Binaries for Windows can be built on Windows using the MinGW toolchain within [M
cd monero
```
-* If you would like a specific [version/tag](https://github.com/monero-project/monero/tags), do a git checkout for that version. eg. 'v0.18.5.3'. If you don't care about the version and just want binaries from master, skip this step:
+* If you would like a specific [version/tag](https://github.com/monero-project/monero/tags), do a git checkout for that version. eg. 'v0.18.5.4'. If you don't care about the version and just want binaries from master, skip this step:
```bash
- git checkout v0.18.5.3
+ git checkout v0.18.5.4
```
* To build Monero, run:
### src/blocks/checkpoints.dat
[binary or diff unavailable]
### src/checkpoints/checkpoints.cpp
@@ -271,7 +271,7 @@ namespace cryptonote
ADD_CHECKPOINT2(3541000, "74c457bed9ceef40f31f43bb8fab804077519d45c910dcad2acf4dd8556195c7", "0x76ff158c682d218");
ADD_CHECKPOINT2(3576000, "5da4891bfd06be270193bd949f2a623a2b0cb0ebfaad21c70a6cb18e418e5b6a", "0x7cb2e203e867b57");
ADD_CHECKPOINT2(3661900, "ac392757a92123f68d63cd72f0d1410f63df1102a53b5d39fc4d53d0998b20a3", "0x8a38f2195826a97");
- ADD_CHECKPOINT2(3774800, "0f4c4c1ca33c35dc56cb764a94e96467df281299e9e5264a5d905309cb806488", "0x9bb1dcfc99f355c");
+ ADD_CHECKPOINT2(3784000, "d2962a542632343fc953760e3e26cc5bb219eb4ed65f5b2e7c6a67251b9a05df", "0x9d3d116d1153593");
return true;
}
### src/cryptonote_core/blockchain.cpp
@@ -5476,7 +5476,7 @@ void Blockchain::cancel()
}
#if defined(PER_BLOCK_CHECKPOINT)
-static const char expected_block_hashes_hash[] = "4871b67b077087affd07094be0f70bfd0d4e4105df126646e0a7524fe02b1d5d";
+static const char expected_block_hashes_hash[] = "1ce21725b4753294c19c98530a27486f1ecbd781443fca64cedebb754454df9b";
void Blockchain::load_compiled_in_block_hashes(const GetCheckpointsCallback& get_checkpoints)
{
if (get_checkpoints == nullptr || !m_fast_sync)Why this scored 21/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.