Releases: ackinacki/ackinacki
Releases · ackinacki/ackinacki
Release 0.8.4
v0.8.4 Updated to v0.8.4 (6fb0970)
Release 0.8.2
v0.8.2 Updated to v0.8.2 (95f9dd0)
Release 0.8.1
v0.8.1 Updated to v0.8.1 (1bea3ea)
Release 0.8.0
v0.8.0 Updated to v0.8.0 (9d02dd1)
Release 0.7.8
v0.7.8 Updated to v0.7.8 (019c63b)
Release 0.7.7
[0.7.7] - 2025-09-23
New
- Ability to run several instances with the same NodeID (for upgrade purpose)
Improvements
- MV system updates
- Staking updates
Fixed
- BK signal handling
- Sync fixes
- Graceful shutdown fixes
Release 0.7.6
[0.7.6] - 2025-09-18
New
:8600/v2/bk_set_updateBK endpoint with the full bk set info- Ability to specify BK set in
NodeConfig.bk_set_update_path - BK and Proxy deployment scripts now download the latest bk set from the specified BK node and gracefully restart the node with this BK set
Improvements
- DappId table removed
- Proxy paragraph updated in README.md
Fixed
- Node runs out of ephemeral ports
Release 0.7.5
[0.7.5] - 2025-09-16
Fixed
- Node join issues
Improvements
- Forced entering into syncing state when requesting Node Join
- Staking improvements
- RUST_BACKTRACE removed
Release 0.7.4
[0.7.4] - 2025-09-12
New
/readinessendpoint on BM- Ability to sign Proxy certificate with multiple BK keys from BK set
- Detached attestations
- Added ability to send direct replies without NodeID
- New metrics with prefinalized blocks and authority switch metrics
- GQL server returns account data in
query{blockchain{account{info}}}and account data is now available in Explorer
Improvements
- DEBUG traces turned off by default, export
NODE_VERBOSE=1to enable them. INFO, ERROR logs enabled by default - WAL2 support in BM
- Improvements in staking scripts
- BK ansible role refactored
Fixed
- Node join fixes
- Load of finalized block on start
- Allow BP stop on epoch end
- Attestatio target for reject
bk_set,future_bk_setmetrics fixed- Generate attestation for an old block if needed
Release 0.7.3
[0.7.3] - 2025-09-04
Improvements
- Staking improvemens
Fixed
- SIGHUP signal was handled incorrectly when the node was not in sync