Environment
- OS: Ubuntu 24.04
- Node version: v0.4.11-star-dust (commit 89f0260)
- Chain: dirac
- GPU: NVIDIA RTX 5060 ×2
- CPU: 12th Gen Intel Core i7-12700 (20 cores)
- RAM: 62 GB
Bug 1 – Runtime Codec Error on Block Proposal
When running as a validator (--validator) on Dirac, the node panics with:
WARN tokio-runtime-worker runtime::basic_author "Bad input data provided to initialize_block: Codec error"
WARN tokio-runtime-worker basic-authorship "Failed to propose block: Runtime panic: Execution failed: Runtime panicked: unreachable"
The node starts, syncs partially, but cannot propose any blocks. The same wallet and flags work perfectly with v0.4.4.
Steps to reproduce
- Run
quantus-node v0.4.11-star-dust --validator --chain dirac --rewards-preimage <preimage> <other flags>
- Wait for the node to attempt block proposal.
- Observe the codec error in logs.
Expected: Validator proposes blocks normally.
Actual: Panic on every block proposal attempt; node unable to participate in consensus.
Bug 2 – Stale Bootnode (72.61.118.55) in Embedded Chain Spec
The embedded dirac chain spec still contains:
/ip4/72.61.118.55/tcp/30333/p2p/QmXkZyXejhpJ6FG9sPG2CYtpyvtpgADKLY5k24jY8DQYwh
This IP returns a different peer ID than expected. Using --bootnodes with DNS addresses only adds to the built-in list; the stale IP entry cannot be overridden from the command line alone.
Expected: All bootnode entries in dirac.json should be valid and reachable.
Actual: Stale IP causes peer ID mismatch warnings and hinders peer discovery.
Bug 3 – Prometheus Port 9615 Conflict (Non-Fatal)
On startup, the node logs:
ERROR sub-libp2p "Failed to bind Prometheus exporter to 127.0.0.1:9615: Address already in use"
While non-fatal, this is a recurring annoyance. Consider adding a --prometheus-port flag or making the bind failure a warning rather than an error.
Workaround
Revert to v0.4.4 + miner v2.1.2 on the Dirac chain. The node connects to 13 peers and proposes blocks without issue.
Additional Notes
- Genesis hash on v0.4.11 matches Dirac:
0x0abf7f951692b436…01e5 ✓
- Heisenberg chain on v0.4.11 is also unreachable: TCP port 30333 appears to be blocked by Cloudflare for the Heisenberg bootnodes, preventing any peer connections.
Environment
Bug 1 – Runtime Codec Error on Block Proposal
When running as a validator (
--validator) on Dirac, the node panics with:WARN tokio-runtime-worker runtime::basic_author "Bad input data provided to initialize_block: Codec error"
WARN tokio-runtime-worker basic-authorship "Failed to propose block: Runtime panic: Execution failed: Runtime panicked: unreachable"
The node starts, syncs partially, but cannot propose any blocks. The same wallet and flags work perfectly with v0.4.4.
Steps to reproduce
quantus-node v0.4.11-star-dust --validator --chain dirac --rewards-preimage <preimage> <other flags>Expected: Validator proposes blocks normally.
Actual: Panic on every block proposal attempt; node unable to participate in consensus.
Bug 2 – Stale Bootnode (72.61.118.55) in Embedded Chain Spec
The embedded
diracchain spec still contains:/ip4/72.61.118.55/tcp/30333/p2p/QmXkZyXejhpJ6FG9sPG2CYtpyvtpgADKLY5k24jY8DQYwh
This IP returns a different peer ID than expected. Using
--bootnodeswith DNS addresses only adds to the built-in list; the stale IP entry cannot be overridden from the command line alone.Expected: All bootnode entries in
dirac.jsonshould be valid and reachable.Actual: Stale IP causes peer ID mismatch warnings and hinders peer discovery.
Bug 3 – Prometheus Port 9615 Conflict (Non-Fatal)
On startup, the node logs:
ERROR sub-libp2p "Failed to bind Prometheus exporter to 127.0.0.1:9615: Address already in use"
While non-fatal, this is a recurring annoyance. Consider adding a
--prometheus-portflag or making the bind failure a warning rather than an error.Workaround
Revert to v0.4.4 + miner v2.1.2 on the Dirac chain. The node connects to 13 peers and proposes blocks without issue.
Additional Notes
0x0abf7f951692b436…01e5✓