release: fuzz campaign for hybrid transport (at least 504 CPU-hours) (#184 R2) #218

Activity

1. djh58

   added

   pq-transportHybrid post-quantum v2 transport (#184)Hybrid post-quantum v2 transport (#184)

   on Oct 5, 2026
2. djh58

   added a parent issue on Oct 5, 2026

   • p2p: add hybrid post-quantum key exchange (ML-KEM-1024) to BIP324 v2 transport #184
3. djh58

   marked this as blocked by 3 issues on Oct 5, 2026

   • fuzz, bench: exercise ML-KEM-1024 per backend (#184 D5) #201
   • net: add PQHandshake: version-contents record parser and per-connection KEM state (#184 E2) #202
   • fuzz: add a stateful malicious-peer target for hybrid negotiation (#184 G4) #211
4. djh58

   marked this as blocking on Oct 5, 2026

   • release: 14-day mainnet canary on release-candidate builds (#184 R5) #220
5. djh58

   removed a parent issue on Oct 5, 2026

   • p2p: add hybrid post-quantum key exchange (ML-KEM-1024) to BIP324 v2 transport #184
6. djh58

   removed

   pq-transportHybrid post-quantum v2 transport (#184)Hybrid post-quantum v2 transport (#184)

   on Oct 5, 2026
7. djh58

   closed this as a duplicateof release: hybrid v2 transport release gate and default-on (#184 part 9) #222 on Oct 5, 2026
8. djh58

   unmarked this as blocked by 3 issues on Oct 5, 2026

   • fuzz, bench: exercise ML-KEM-1024 per backend (#184 D5) #201
   • net: add PQHandshake: version-contents record parser and per-connection KEM state (#184 E2) #202
   • fuzz: add a stateful malicious-peer target for hybrid negotiation (#184 G4) #211
9. djh58

   unmarked this as blocking on Oct 5, 2026

   • release: 14-day mainnet canary on release-candidate builds (#184 R5) #220