LEP6/host reporter and recheck chain improvements #296
Merged
j-rafique merged 1 commit intoMay 26, 2026
Merged
Conversation
Addresses Matee's prod-gate review on PR #286. F1 (Critical) — host_reporter SHADOW/SOFT idempotency: Previously skipped epoch report when mode != UNSPECIFIED with empty proof rows. This converted a transient local proof-generation gap into missing audit reports → postponement. Fix: gate compound-proof coverage check to FULL mode only; SHADOW/SOFT/UNSPECIFIED submit the epoch report even with empty LEP-6 proof rows (INFO log). F2 (Critical) — transactional proof-row drain: CollectResults(epochID) drained rows before SubmitEpochReport; on tx/RPC failure rows were lost. Fix: requeue proof rows on non- duplicate submit failure via new requeueProofResults helper, with new IsEpochReportDuplicate(err) predicate to avoid requeue on benign duplicate-report errors. F3 (High) — recheck dedup key matches chain: Local PK was (epoch_id, ticket_id, target_account); chain replay protection in x/audit msg_storage_truth uses (epoch, ticket, creator). Fix: collapse local PK to (epoch_id, ticket_id); target_account becomes metadata. Finder seen-map keyed the same; attestor treats ErrLEP6RecheckAlreadyRecorded as success. Non-destructive migration with deterministic row collapse. F4 (Medium) — go.sum drift for lumera v1.12.0: Deferred — chain-side release-engineering issue. Public Go proxy cached original v1.12.0 bytes (h1:prh3k8y...) immutably; the v1.12.0 tag was later force-moved to a different commit (h1:ZtGvnw... in current go.sum). Cannot be resolved from supernode without either restoring the tag pointer on the chain side or republishing as v1.12.1. Validation: - 53/53 unit-test packages PASS - 7/7 LEP-6 system e2e tests PASS (make test-lep6, 1479.84s) including StorageTruthEnforcementLifecycle (F1+F2 path) and NegativePerCaseCorruptionMatrix + CrashRestartMidHeal (F3 path)
j-rafique
changed the base branch from
master
to
supernode/LEP-6-chain-client-extensions
j-rafique
merged commit c28d7ea
into
supernode/LEP-6-chain-client-extensions
8 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.