archetech / archon / 35012706710

92%

main: 95%

Build Type

Pull #1145

github

Committed by macterra

Commit Message

feat(gatekeeper-rs): Port the backdating gate for parity

Mirrors the TypeScript change in the Rust gatekeeper so the two ports
reach the same verdict on every operation: controller_at resolves an
asset operation's controller at the operation's chain position rather
than its own proof.created -- by ordinal for the controller's events on
the operation's registry, by block time for any other -- and falls back
to proof.created when the controller is not anchored, read from its
events rather than inferred from a registry name. The anchor is carried
through new-event import, the verifying replay, and the confirmation
replace path, which now re-verifies against the version the event
chained from. relay_hints downgrades what the relay and restore ingresses
claim to unconfirmed hints, so chain confirmation enters only through
the CID import a mediator drives block by block.

Two integration tests encoded the old contracts. The timestamp test
pushed a confirmed chain event through the relay ingress, which is what
this closes; its subject is build_timestamp reading registration, so it
is a store-seeded unit test now. The confirm-fallback test passed only
because the store resolver's confirm bug reported a pending update as
unconfirmed; with that fixed the Rust fallback has no live trigger, which
is its own issue, and the test is removed.

The parity harness runs the gate end to end on both ports through the
mediator's path: a forgery the chain committed after the rotation is
refused by both, one committed earlier in the rotation's own block is
accepted by both, and a chain event through the relay ingress lands as
a hint on both. The parity services now enable BTC:signet for it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GYGMfX3foBcVqP7AQNXjWj

Pull Request Pull Request #1145: fix(gatekeeper): Reject a backdated proof once the chain has committed the operation

Coverage Stats

4217 of 4846 branches covered (87.02%)

Branch coverage included in aggregate %.

40 of 42 new or added lines in 2 files covered. (95.24%)

12 existing lines in 1 file now uncovered.

8842 of 9285 relevant lines covered (95.23%)

788.53 hits per line