Skip to content

Releases: Dragonmonk111/layer-sdk

v0.6.0-rc12

Choose a tag to compare

@Dragonmonk111 Dragonmonk111 released this 18 Oct 10:48

v0.6.0-rc12 — catch-up liveness + state-sync hardening

Fixes found during the rc11 soak and an overnight force_state_sync recovery:

  • D6 — catch-up pending-capacity wedge (reproduced twice in the field):
    unsolicited far-tip pushes filled pending_payloads (cap 16,384) so the
    solicited tip+1 payload replies were rejected → execution halted forever.
    Solicited replies now bypass the cap.
  • D7 — peer-mesh metric blind spot: mesh health now counts inbound
    deliveries and fetch-served payloads, not only proposer broadcasts.
  • D8 — state-sync donor decode cap: donor gRPC client raised to 16MiB
    (snapshot chunk 0 is ~7.8MiB at ~2.22M heights; the 4MiB default rejected
    every donor, crash-looping forced syncs).
  • D9 mitigation — invalid donor records are skipped: a donor serving a
    truncated/unverifiable block record no longer aborts the anchor fetch;
    min_anchor_agree byte-identical quorum is still enforced. Observed on
    two independent donors at different heights — root cause tracked in
    g1-ceremony/INCIDENT-2026-10-18-rc12.md.
  • D5 — sealed DKG dealing files ship in generate-testnet-keys
    (X25519 + XChaCha20-Poly1305, recipient-sealed).

Canary: home-vb validator ran this exact binary (2d5a3b5d…) through a live
force_state_sync recovery before release.

Verify with MANIFEST.sha256 after download:

sha256sum -c MANIFEST.sha256

v0.6.0-rc11

Choose a tag to compare

@Dragonmonk111 Dragonmonk111 released this 17 Oct 03:31

G2 post-cutover hardening: state-sync donor-root quorum gate, force_state_sync flag, peer-mesh diagnostics.

v0.6.0-rc10 — G2 candidate

Choose a tag to compare

@Dragonmonk111 Dragonmonk111 released this 15 Oct 10:02

G2 candidate build.

Changes since rc9

  • restart_anchor consensus mechanism — coordinated validator set changes restart from a shared parent (R9 rehearsal: add 4→5, remove 5→4, retired-seat isolation all PASS)
  • Idempotent journal prune — BlobMissing on an already-absent section no longer panics the voter/resolver (post-G1 3-of-4 stress finding)
  • jc-faucet, jc-explorer v2 (archive deep history), jc-status stall alerting

Artifacts

  • slay3rd-linux-amd64 — verify with MANIFEST.sha256 before running
  • install.sh — sh install.sh fetches + verifies + installs

Post-G1 stress notes

A 3-of-4 config (Akash seat retired) halted 14.4h on 2026-10-14 when a second seat crashed on the prune bug fixed here. See g1-ceremony/INCIDENT-AND-BUGS-2026-10-08.md.