Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/CHANGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,17 @@ lines under the new release.

## Not released yet

Nothing yet.

## community.18.1 — 2026-11-09

Release 18.1 is a point release of 18: the protocol and the version a node announces to its peers are unchanged (the announced minor version stays 18, which cannot express 18.1). It fixes one consensus problem. A node no longer signs a second, different stage-1 message in the same round when a fuller round package replaces the first one. That double signing made the confidants build different blocks, so the node was left in the stage-3 minority and gray-listed. A replacement on the writer side and inside a bootstrap round still signs twice; that is a follow-up.

The Windows and macOS packages of community.18 were not published (no macOS runner was available), so 18.1 is the first release of the 18 line for those systems.

| PR | Change |
|---|---|
| release | community.18.1, a point release of 18: `MINOR_NODE_VERSION` stays 18, the package and the tag carry 4.2.532-community.18.1 |
| #178 | solver: when a confidant enters stage 1 again in the same round after a fuller round package replaced the first one, it sends the stage 1 it already signed again instead of signing a second one with a new timestamp; it signs a new one when the characteristic hash changed, the stored timestamp is not after the last block's, is more than 30 s old or cannot be read; a writer-side replacement and a replacement inside a bootstrap round still sign a second stage 1, as before; new info lines `stage1 resent unchanged` and `stage1 signed again ... reason`, and the package replacement is logged at info level (`docs/consensus-diagnostics.md`, section 5) |

## community.18 — 2026-11-09
Expand Down
7 changes: 6 additions & 1 deletion docs/FEATURES.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ consensus with them. This page lists what it adds; each item links the pull requ
The full list of changes is in [CHANGES.md](CHANGES.md), the operational details in
[differences.md](differences.md).

Everything listed here is in release 4.2.532-community.18 or earlier.
Everything listed here is in release 4.2.532-community.18.1 or earlier.

## Storage

Expand Down Expand Up @@ -138,6 +138,11 @@ Everything listed here is in release 4.2.532-community.18 or earlier.
neighbour would refuse as a duplicate, and asks another one instead: a node syncing among mostly
pruned peers could otherwise wait for ever for its first blocks.
[#136](https://github.com/CreditsCommunity/node/pull/136)
- **One stage 1 per round.** When a fuller round package replaces the first one, a confidant sends
the stage-1 message it already signed instead of signing a second, different one. Two different
stage-1 messages made the confidants build different blocks and left the node in the stage-3
minority. A replacement on the writer side and in a bootstrap round still signs twice.
[#178](https://github.com/CreditsCommunity/node/pull/178)

## Diagnostics

Expand Down
2 changes: 1 addition & 1 deletion docs/differences.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ from the Thrift definitions of the fork
| Field | Value |
|---|---|
| `9: optional i64 networkUuid` | The chain identifier: the first 8 bytes of the hash of block 1, read as a little-endian unsigned 64-bit number (`BlockChain::uuid()`). It is the same on every node of a network, so a client such as a wallet can tell mainnet from a test network. Pruned nodes and nodes started from a snapshot know it too (it is in the checkpoint). Left out while the node does not know it yet (an empty database before block 1). Thrift has no unsigned type: the same 64 bits travel as a signed number, so mainnet, `11024959585341937636`, arrives as `-7421784488367613980`; add 2^64 to a negative value (or mask with `0xFFFFFFFFFFFFFFFF`) to get the unsigned one. |
| `10: optional string communityVersion` | The package version, the first line of the `VERSION` file, for example `4.2.532-community.18`. Without a `VERSION` file it is `4.2.<protocol>.<minor>`. Always set by the community node. |
| `10: optional string communityVersion` | The package version, the first line of the `VERSION` file, for example `4.2.532-community.18.1`. Without a `VERSION` file it is `4.2.<protocol>.<minor>`. Always set by the community node. |

The official node sets neither field, and clients built from the official definitions ignore them,
so a client can detect a community node by the presence of `communityVersion`. A local clone made
Expand Down
16 changes: 8 additions & 8 deletions docs/quick-start.md
Original file line number Diff line number Diff line change
Expand Up @@ -124,16 +124,16 @@ caches.

1. Open the [latest release](https://github.com/CreditsCommunity/node/releases/latest) and download
the Linux package and `SHA256SUMS`:
- `credits-node-4.2.532-community.18-linux-x64.tar.gz` for Ubuntu 24.04, Debian 13 and later
- `credits-node-4.2.532-community.18.1-linux-x64.tar.gz` for Ubuntu 24.04, Debian 13 and later
(glibc 2.38);
- `credits-node-4.2.532-community.18-linux-x64-glibc2.31.tar.gz` for Ubuntu 20.04, Debian 11
- `credits-node-4.2.532-community.18.1-linux-x64-glibc2.31.tar.gz` for Ubuntu 20.04, Debian 11
and later.

2. Check and extract:

```sh
sha256sum -c --ignore-missing SHA256SUMS # must print "OK"
tar -xzf credits-node-4.2.532-community.18-linux-x64.tar.gz
tar -xzf credits-node-4.2.532-community.18.1-linux-x64.tar.gz
cd csnode
```

Expand Down Expand Up @@ -209,12 +209,12 @@ The node's own log is in `csnode/log/`.

## 5. Native on Windows

1. Download `credits-node-4.2.532-community.18-windows-x64.zip` and `SHA256SUMS-windows-macos`
1. Download `credits-node-4.2.532-community.18.1-windows-x64.zip` and `SHA256SUMS-windows-macos`
from the [latest release](https://github.com/CreditsCommunity/node/releases/latest). Check it in
PowerShell and compare with the file:

```powershell
Get-FileHash credits-node-4.2.532-community.18-windows-x64.zip
Get-FileHash credits-node-4.2.532-community.18.1-windows-x64.zip
```

2. Extract the zip, for example to `C:\credits`. Open the `csnode` folder.
Expand All @@ -234,12 +234,12 @@ The package has no Windows service. Run the node in a console window you keep op

## 6. macOS (Apple Silicon)

Download `credits-node-4.2.532-community.18-macos-arm64.tar.gz`, check it with
Download `credits-node-4.2.532-community.18.1-macos-arm64.tar.gz`, check it with
`shasum -a 256 -c --ignore-missing SHA256SUMS-windows-macos`, extract it, then clear the
download quarantine once (the binaries are not signed) and follow the Linux steps:

```sh
tar -xzf credits-node-4.2.532-community.18-macos-arm64.tar.gz
tar -xzf credits-node-4.2.532-community.18.1-macos-arm64.tar.gz
xattr -dr com.apple.quarantine csnode
cd csnode && ./setup.sh
```
Expand All @@ -251,7 +251,7 @@ In the console or the log (`csnode/log/`, or `docker compose logs -f`), look for
1. The banner with the version and your settings:

```
node 4.2.532-community.18 (protocol 532, build ...)
node 4.2.532-community.18.1 (protocol 532, build ...)
storage: pruned, lmdb snapshots: serve on
```

Expand Down
Loading