Here is an attempt to backport to the 1.9 branch the fixes made by kimamila on the 1.8 branch : Commits · dev · Yann Autissier / duniter · GitLab
It compiles but does not validate somes tests. If someone can fix it to pass the tests,it could be a solution to maintain 1.9 nodes.
Where are the kimamila fixes?
The 1.9 branch started from the 1.8 and Kimamila added fixes later in the 1.8.7 version that I tried to backport to a 1.9.1 branch.
Well above my level. I’ll pass.
I’ve looked at one of the last commits from kimamila and it doesn’t apply at all. Many things have changed between 1.8 and 1.9 because Eloïs was rewriting duniter in rust.
Anyway I think using backups everytime is not such a good idea. Because looking at the logs I see “corrupted database” errors where the desynchronizations occur, and restarting from backups just keeps the corrupted database along.
I’m giving a try at a full sync again.
I did a full sync as well, I created the backup just now (same naming convention even if not created at 2h00 
).
It’s in a proper state:
./check_bmas_and_gva_sync_for_node_url.sh https://g1-1.9.0.de.brussels.ovh
2026-01-22T07:53:08Z: Node:https://g1-1.9.0.de.brussels.ovh has bmas:901241 gva:901241 [diff:0]
I’ll also keep a copy of that backup with a different name so it doesn’t get automatically deleted:
https://downloads.de.brussels.ovh/keep_auto-backup-g1-1.9.0.de.brussels.ovh-2026-01-22_02-00.tgz
Unfortunately after a full sync there are ‘DB corrupted’ errors again:
2026-01-21T17:10:19+00:00 - error: Unhandled rejection: Error: DB corrupted:Not found origin tx of uxto C89DD4BE8D3BCA8C5EAA1752FAD04421C5F49D8FA9C6A65FAB8B1220AEB77DF8:0
2026-01-21T17:10:19+00:00 - error: Error: DB corrupted:Not found origin tx of uxto C89DD4BE8D3BCA8C5EAA1752FAD04421C5F49D8FA9C6A65FAB8B1220AEB77DF8:0
Desynchronizations occur on these DB errors.
I don’t see such errors yet on my server - but I guess it’s only a matter of time ?
@Pini we have again gva starting to de-sync since 13h56 
I have no clue why our nodes are so much linked together - each time when one of them de-sync; the other as well.
(meanwhile; the xxx.casa nodes in 1.9.0 are still stable)
2026-01-23T12:16:54+00:00 - error: Unhandled rejection: Error: DB corrupted:Not found origin tx of uxto B748B0068EE7F0382BF2CE004AF5935D1653A84C7BD4597A183CDF1E4D57C5B6:1
2026-01-23T12:16:54+00:00 - error: Error: DB corrupted:Not found origin tx of uxto B748B0068EE7F0382BF2CE004AF5935D1653A84C7BD4597A183CDF1E4D57C5B6:1
Same error almost at the same time:
duniter-v1-1.9.0 | 2026-01-23T12:15:37.753371302Z 2026-01-23T12:15:37+00:00 - error: Unhandled rejection: Error: DB corrupted:Not found origin tx of uxto B748B0068EE7F0382BF2CE004AF5935D1653A84C7BD4597A183CDF1E4D57C5B6:1
duniter-v1-1.9.0 | 2026-01-23T12:15:37.753439862Z 2026-01-23T12:15:37+00:00 - error: Error: DB corrupted:Not found origin tx of uxto B748B0068EE7F0382BF2CE004AF5935D1653A84C7BD4597A183CDF1E4D57C5B6:1
duniter-v1-1.9.0 | 2026-01-23T12:15:37.753452742Z at Function.revertBlock (/duniter/app/lib/blockchain/DuniterBlockchain.js:382:28)
duniter-v1-1.9.0 | 2026-01-23T12:15:37.753455542Z at BlockchainContext.revertCurrentBlock (/duniter/app/lib/computation/BlockchainContext.js:110:53)
These errors occur during fork resolution. I have no idea about the root cause.
Thanks indeed @Nicolas80, your node 1.9 resisted 
until today:
