Kc1212/feat/2887/compressed keygen from existing secret tests

[kc1212]

Description of changes

Tested manually also with

cargo run -- -f config/client_local_threshold.toml preproc-key-gen
# save the first preproc ID as PREPROC1
cargo run -- -f config/client_local_threshold.toml key-gen -i $PREPROC1
# save the first key ID as KEYID1

cargo run -- -f config/client_local_threshold.toml preproc-key-gen --from-existing-shares
# save the second preproc ID as PREPROC2
cargo run -- -f config/client_local_threshold.toml key-gen -i $PREPROC2 --compressed # note that we use compressed
# save the second key ID as KEYID2

# now we can run ddec
cargo run -- -f config/client_local_threshold.toml public-decrypt from-args -d euint64 -k ${KEYID2} --num-requests 1 --batch-size 1 --to-encrypt ff

# one can also verify that the types in the public/private storage. but it's not easy to check that the binaries are partially the same in the shares

Issue ticket number and link

PR Checklist

I attest that all checked items are satisfied. Any deviation is clearly justified above.

• Title follows conventional commits (e.g. chore: ...).
• Tests added for every new pub item and test coverage has not decreased.
• Public APIs and non-obvious logic documented; unfinished work marked as TODO(#issue).
• unwrap/expect/panic only in tests or for invariant bugs (documented if present).
• No dependency version changes OR (if changed) only minimal required fixes.
• No architectural protocol changes OR linked spec PR/issue provided.
• No breaking deployment config changes OR devops label + infra notified + infra-team reviewer assigned.
• No breaking gRPC / serialized data changes OR commit marked with ! and affected teams notified.
• No modifications to existing versionized structs OR backward compatibility tests updated.
• No critical business logic / crypto changes OR ≥2 reviewers assigned.
• No new sensitive data fields added OR Zeroize + ZeroizeOnDrop implemented.
• No new public storage data OR data is verifiable (signature / digest).
• No unsafe; if unavoidable: minimal, justified, documented, and test/fuzz covered.
• Strongly typed boundaries: typed inputs validated at the edge; no untyped values or errors cross modules.
• Self-review completed.

Dependency Update Questionnaire (only if deps changed or added)

Answer in the Cargo.toml next to the dependency (or here if updating):

1. Ownership changes or suspicious concentration?
2. Low popularity?
3. Unusual version jump?
4. Lacking documentation?
5. Missing CI?
6. No security / disclosure policy?
7. Significant size increase?

More details and explanations for the checklist and dependency updates can be found in CONTRIBUTING.md

[github-actions]

Consolidated Tests Results 2026-02-25 - 15:59:48

Test Results

14 passed

Details

14 tests
not captured
junit-to-ctrf
build-and-test test-reporter #589
Kc1212/feat/2887/compressed keygen from existing secret tests #438

test-reporter: Run #589

Tests 📝	Passed ✅	Failed ❌	Skipped ⏭️	Pending ⏳	Other ❓	Flaky 🍂	Duration ⏱️
14	14	0	0	0	0	0	not captured

🎉 All tests passed!

Tests

View All Tests

Test Name	Status	Flaky	Duration
full_gen_tests_k8s_default_threshld_sequential_crs	✅		33.3s
test_k8s_threshld_insecure	✅		3m 14s
k8s_test_crs_uniqueness	✅		33.2s
k8s_test_keygen_and_crs	✅		3m 14s
k8s_test_keygen_uniqueness	✅		8m 53s
full_gen_tests_k8s_default_centralzd_sequential_crs	✅		1.8s
test_k8s_centralzd_insecure	✅		2m 58s
full_gen_tests_default_k8s_centralized_sequential_crs	✅		1.8s
k8s_test_centralized_insecure	✅		1m 1s
full_gen_tests_k8s_default_threshld_sequential_crs	✅		32.8s
test_k8s_threshld_insecure	✅		3m 15s
k8s_test_crs_uniqueness	✅		33.1s
k8s_test_keygen_and_crs	✅		3m 13s
k8s_test_keygen_uniqueness	✅		8m 57s

_{🍂 No flaky tests in this run.}

Github Test Reporter by CTRF 💚

🔄 This comment has been updated