aere-network/aere-node
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

RUN-A-NODE and run-node.sh: the follower's emergency-ceiling ERROR line is logged for every imported block since patch 0008 (measured), not once per anchor

Browse Source
This commit is contained in:
Aere Network 2026-10-01 15:24:14 +03:00
parent 063424c490
commit fe41803c07
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
RUN-A-NODE.md
View File

@ -258,9 +258,10 @@ classes missing and 56 with different code, so the comparison can tell them apar
from this recipe, started on a database that ended at block 20,836,227, imported block 20,836,228 and from this recipe, started on a database that ended at block 20,836,227, imported block 20,836,228 and
went on with ten peers and no refusal (20,840,327 within two minutes). went on with ten peers and no refusal (20,840,327 within two minutes).
A follower started with `run-node.sh` logs `AERE-PQC-EMG-CEILING-01` at ERROR level while it A follower started with `run-node.sh` logs `AERE-PQC-EMG-CEILING-01` at ERROR level for every block
imports: that is the emergency seal-count ceiling the script sets for followers (see the comment it imports: that is the emergency seal-count ceiling the script sets for followers (see the comment
above `ANCHOR_MIN_SEALS_CEILING` in the script), not a refusal. A refusal names the block and the above `ANCHOR_MIN_SEALS_CEILING` in the script and the section on the configuration below), not a
refusal. A refusal names the block and the
rule that refused it. rule that refused it.
--- ---
@ -385,7 +386,9 @@ does not set this.
**What you will see in the log, and why it is not an incident.** With this ceiling set, the node **What you will see in the log, and why it is not an incident.** With this ceiling set, the node
prints a red startup banner (`AERE-PQC-EMG-BANNER-01`, "starting with 1 POST-QUANTUM SAFETY prints a red startup banner (`AERE-PQC-EMG-BANNER-01`, "starting with 1 POST-QUANTUM SAFETY
CONTROL lowered") and then one ERROR line **per anchor block**: CONTROL lowered") and then one ERROR line **per imported block** (measured 2026-10-01 on a build with
patch 0008: 148,076 such lines for 148,076 consecutive heights; before patch 0008 it was one line
per anchor block):
``` ```
ERROR | PqEmergencyShoutRule | AERE PQC EMERGENCY [AERE-PQC-EMG-CEILING-01]: height N validated ERROR | PqEmergencyShoutRule | AERE PQC EMERGENCY [AERE-PQC-EMG-CEILING-01]: height N validated

3
run-node.sh
View File

@ -251,7 +251,8 @@ mkdir -p "$DATA_PATH"
# to the current set, not a history-verification property) is relaxed to one. Real anchor blocks # to the current set, not a history-verification property) is relaxed to one. Real anchor blocks
# carry far more than one seal (measured 2026-09-12 on the live chain: 14 to 20 in total, seven to ten # carry far more than one seal (measured 2026-09-12 on the live chain: 14 to 20 in total, seven to ten
# per half since the certificate became hybrid), so all import cleanly. With the ceiling set the node # per half since the certificate became hybrid), so all import cleanly. With the ceiling set the node
# shouts one ERROR per anchor by design (AERE-PQC-EMG-CEILING-01); RUN-A-NODE.md says what that is and # shouts one ERROR per imported block by design (AERE-PQC-EMG-CEILING-01; one per anchor before patch 0008, measured
# 2026-10-01); RUN-A-NODE.md says what that is, how to run without it once synced, and
# what a real refusal looks like instead. A validator, which starts into the full set and # what a real refusal looks like instead. A validator, which starts into the full set and
# proposes, does not set this. # proposes, does not set this.
ANCHOR_MIN_SEALS_CEILING="${AERE_ANCHOR_MIN_SEALS_CEILING:-1}" ANCHOR_MIN_SEALS_CEILING="${AERE_ANCHOR_MIN_SEALS_CEILING:-1}"