No captured transaction on hegota-testnet uses signature scheme 2 (P256), so the P256 branch of assertValidFrameTx is exercised only against hand-written input. This is a fact about what the chain has produced so far rather than an omission in the suite, and it closes as soon as such a transaction exists.
What to do: watch for a transaction that carries a scheme 2 entry, then capture it with bunx tsx scripts/capture-fixtures.ts [from-block] [to-block] and add the resulting file under test/fixtures/chain/. The oracle suite picks up new fixtures without further wiring.
The fixture records the client version and genesis hash it was captured against, so do not hand-edit the file. If the capture disagrees with the encoder, the encoder is the side that is wrong, and that is a finding worth its own issue.
Context is in docs/OPEN-ITEMS.md, under the fixture coverage item. CONTRIBUTING.md explains how the three verification oracles work and why a fixture is never edited to make a test pass.
No captured transaction on hegota-testnet uses signature scheme 2 (P256), so the P256 branch of
assertValidFrameTxis exercised only against hand-written input. This is a fact about what the chain has produced so far rather than an omission in the suite, and it closes as soon as such a transaction exists.What to do: watch for a transaction that carries a scheme 2 entry, then capture it with
bunx tsx scripts/capture-fixtures.ts [from-block] [to-block]and add the resulting file undertest/fixtures/chain/. The oracle suite picks up new fixtures without further wiring.The fixture records the client version and genesis hash it was captured against, so do not hand-edit the file. If the capture disagrees with the encoder, the encoder is the side that is wrong, and that is a finding worth its own issue.
Context is in
docs/OPEN-ITEMS.md, under the fixture coverage item.CONTRIBUTING.mdexplains how the three verification oracles work and why a fixture is never edited to make a test pass.