AETHERION BFT v1.0.5

Rewards-router fork. From epoch 21025 (first fork block 6307500, expected around 2026-09-15 14:00 UTC, at ~2 s per block) every epoch-ending block routes the StakeFi share of the emission to native staking through 0x5cf97538B410CB6a2D72989d97A74CcA2af39Fd1.

Every node — validator or full node — must run v1.0.5 before block 6307500. A validator still on an older binary keeps importing blocks but refuses the epoch-ending blocks that carry the new transaction: one such validator slows those blocks, two of four stop the chain. Its data is fine: do not wipe it — install this release and restart the service.

asset	sha256
aetherion-bft-linux-amd64	e277c79e989dbbdc4d52054c86cdda125b008df49c1bce6b37786c56b703045a
aetherion-bft-linux-arm64	ed6fe783b0ab92efee21f6e297dc0b150e3a25a7d17914d50ab4b4062ba4fcfa

Update by hand

ARCH=amd64   # arm64 on ARM servers
cd "$(mktemp -d)"
curl -fsSLO https://github.com/AETHERION-AI-org/aetherion-bft/releases/download/v1.0.5/aetherion-bft-linux-$ARCH
curl -fsSLO https://github.com/AETHERION-AI-org/aetherion-bft/releases/download/v1.0.5/SHA256SUMS
sha256sum --ignore-missing -c SHA256SUMS            # must print: aetherion-bft-linux-$ARCH: OK
sudo cp /usr/local/bin/aetherion-bft /usr/local/bin/aetherion-bft.previous
sudo systemctl stop aetherion-node
sudo mv aetherion-bft-linux-$ARCH /usr/local/bin/aetherion-bft && sudo chmod 0755 /usr/local/bin/aetherion-bft
sudo systemctl start aetherion-node
curl -s -X POST http://127.0.0.1:8545 -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"web3_clientVersion","params":[]}'   # must contain /v1.0.5/

Rollback: sudo systemctl stop aetherion-node && sudo cp /usr/local/bin/aetherion-bft.previous /usr/local/bin/aetherion-bft && sudo systemctl start aetherion-node — only before block 6307500.

Re-running the installer instead also installs v1.0.5. On a validator, choose "Validator" at the node-type prompt — a full-node answer rewrites the service without --seal and the node stops producing blocks.

AETHERION BFT v1.0.4

Stake-gated validator registration. registerSelf is now payable and locks >= minStake in the same call; validator-register gains --amount and sends it as value; the installer registers after sync (registration now activates the node) and uses validator-stake for top-ups / governance operators. Matches the on-chain registry upgrade on chain 100892. Existing validators and the governance path are unaffected.

AETHERION BFT v1.0.3

The network's bootnodes are compiled in.

Install

curl -fsSL https://raw.githubusercontent.com/AETHERION-AI-org/aetherion-bft/main/scripts/install.sh -o /tmp/aetherion-install.sh && sudo bash /tmp/aetherion-install.sh

What changed

A node used to read its bootnodes from genesis.json and nowhere else, so joining was only as reliable as whichever copy of that file you held. All four are built into the binary now and merged with whatever your genesis carries: genesis can add bootnodes, it cannot take these away, and your own entries still get dialed first.

A bootnode is a door to knock on, not an authority. It introduces peers; it cannot vouch for a block.

Verify before running: sha256sum -c SHA256SUMS

AETHERION BFT v1.0.2

Nodes now report the latest block of each peer they can see.

Install

curl -fsSL https://raw.githubusercontent.com/AETHERION-AI-org/aetherion-bft/main/scripts/install.sh -o /tmp/aetherion-install.sh && sudo bash /tmp/aetherion-install.sh

What changed

peers status now prints Latest block for a peer. The syncer already tracked this to decide who to sync from; it simply was not exposed.

This is your node reporting what its peers announced over the sync protocol. It asks them for nothing, and no node reports on itself. Nothing here calls home.

A peer that has announced nothing reads as not announced yet, not as block zero, so a quiet node is not mistaken for a stuck one.

Verify before running: sha256sum -c SHA256SUMS

AETHERION BFT v1.0.1

Permissionless validator registration.

Install

curl -fsSL https://raw.githubusercontent.com/AETHERION-AI-org/aetherion-bft/main/scripts/install.sh -o /tmp/aetherion-install.sh && sudo bash /tmp/aetherion-install.sh

Two commands rather than a pipe into sudo: piping makes the script bash's own stdin, so its prompts end up fighting the script text for your keyboard. Downloading first also lets you read what you are about to run as root.

Anyone can now join the validator set without approval. The chain admits an operator on two facts it verifies itself: a BLS proof-of-possession, and that the caller is the operator. The only barrier is the stake, which costs real AETH.

New: validator-register registers this node on-chain with its own keys. validator-stake locks the deposit. The installer runs both for you.

Verify before running: sha256sum -c SHA256SUMS

AETHERION BFT v1.0.0

First public release of the AETHERION BFT consensus client for the Aetherion Network (chain 100892).

Install

curl -fsSL https://raw.githubusercontent.com/AETHERION-AI-org/aetherion-bft/main/scripts/install.sh | sudo bash

Installs a full node by default and offers a validator path that generates keys, waits for the operator address to be funded, and locks stake.

Binaries

File	Platform
aetherion-bft-linux-amd64	Linux x86_64
aetherion-bft-linux-arm64	Linux ARM64

Verify before running:

sha256sum -c SHA256SUMS

Notable

• validator-pop builds the BLS proof-of-possession the registry verifies on-chain.
• validator-stake locks AETH as validator stake from the node's own key. The key never leaves the machine.
• Genesis for chain 100892 ships in the repository root as genesis.json.