Skip to content

ORE v2 (1/n): compatibility vectors + bench baselines#78

Draft
coderdan wants to merge 2 commits into
ore-v2from
feat/ore-v2-test-vectors
Draft

ORE v2 (1/n): compatibility vectors + bench baselines#78
coderdan wants to merge 2 commits into
ore-v2from
feat/ore-v2-test-vectors

Conversation

@coderdan

Copy link
Copy Markdown
Contributor

First PR of the ORE v2 program — see docs/plans/2026-06-12-ore-v2-architecture.md (included in this PR).

What

  • Pinned compatibility vectors for the bit2 scheme (tests/compat_vectors.rs): exact serialised bytes for left and full ciphertexts under fixed keys, plus comparison fixtures over the pinned bytes. Full ciphertexts are made deterministic via a test RNG whose from_entropy is overridden to a fixed seed (the library is already generic over the RNG, so no library changes needed).
  • Criterion baselines on Apple M1 Max recorded in docs/benchmarks/2026-06-13-baseline-main.md.
  • The v2 architecture plan itself.

Why

These vectors are the byte-identity contract for the upcoming core refactor (PR 2): the legacy scheme must keep producing identical bytes because stored ciphertexts in the wild depend on it. The baseline numbers are the reference for the performance PRs (3–5).

Notable baseline observation: per-block encrypt cost is ~47 µs against a sub-µs raw AES floor — the headroom the plan targets is real and large.

coderdan added 2 commits June 16, 2026 19:34
Pins serialised ciphertext bytes (left + full via deterministic test RNG)
and comparison fixtures for the bit2 scheme, as the byte-identity contract
for the v2 refactor. Adds the v2 architecture plan and the criterion
baseline numbers on Apple M1 Max.

Part of the ORE v2 program (docs/plans/2026-06-12-ore-v2-architecture.md, PR 1).
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