Skip to content

Conversation

@ch4r10t33r
Copy link
Collaborator

No description provided.

For 2^8 lifetime, always regenerate from seed instead of loading SSZ keys.
This avoids epoch configuration mismatches between keygen and sign steps.

The issue: 2^8 keygen uses 2 active epochs (2*128=256), but the SSZ file
from a previous run might have different active epochs, causing verification
to fail.

Solution: Skip SSZ loading for 2^8 and always use seed-based regeneration.
This ensures keygen -> sign flow works correctly in CI.

2^18 and 2^32 continue to use pre-generated keys when available.

All tests pass:
- benchmark.py for 2^8, 2^18, 2^32
- inspect_pregenerated_keys.py (uses 2^32 keys)
- Remove lengthy reasoning comments (e.g., 'But wait', 'Actually, I think')
- Simplify 'CRITICAL' and 'CRITICAL DEBUG' comments to concise statements
- Remove verbose RNG state matching explanations in cross_lang_zig_tool.zig
- Preserve essential technical documentation
- No functional changes, all tests passing
@ch4r10t33r ch4r10t33r merged commit 331e4c2 into blockblaz:master Dec 3, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant