Cardano Updates

Change the time for each call so that ghc is forced to run every loop
itteration.

Co-Authored-By: Claude Fable 5 <[email protected]>

Co-Authored-By: Claude Fable 5 <[email protected]>

  When a DecrementTx was applied on-chain before the head was closed
  (snapshotVersion != openVersion), partialFanout passed fullUTxO to
  buildAndVerifyAccumulator. But the closed datum's accumulatorCommitment
  was built from utxoForProof (snapshot UTxO including the decommit set),
  so the check always failed with StaleChainState, leaving the head stuck.

  Separate the accumulator proof input from the distribution set by adding
  a proofUTxO parameter to partialFanout and findFittingFanoutTx. The
  FanoutTx call site now passes utxoForProof as proofUTxO so it matches
  what the closed datum was committed to, while fullUTxO (the actual
  distribution set) is used unchanged for fanout outputs.

Signed-off-by: Sasha Bogicevic <[email protected]>

Feed the ancillary proof input into multi-signature creation and persist the returned verifier data on the certificate.

Carry the prover input into the clerk, return the verifier data alongside the aggregate signature, and accept optional verifier data on verification.

Build the aggregate signature ancillary input from the genesis and parent certificates and store the produced verifier data on the certificate.

Proof-system-agnostic carriers with versioned CBOR to_bytes/from_bytes per CODEC.md; no variants yet.

Add nullable ancillary columns (migration 44) and thread the data through the certificate record conversions.

Wrap the STM ancillary types in ProtocolKey (bytes hex codec), add optional prover and verifier fields to Certificate, and fold them into its hash.

Signed-off-by: Sasha Bogicevic <[email protected]>

The leios-prototype CDDL defines `bitmaps` as

    ; indefinite-length map from 64-tx window index to 64-bit presence
    bitmaps = { * base.word16 => base.word64 }

and the reference relay's parser enforces the indefinite-length form:
sending the definite-length variant triggers an immediate TCP RST
within ~25–45 ms of `MsgLeiosBlockTxsRequest`, which we'd been
working around in our dev-relay configs with
`fetch_policy.eb_txs = "no_fetch"`.

Switch `encode_bitmap` from `e.map(len)` (definite-length) to
`e.begin_map()` + `e.end()` (indefinite-length).  Same pattern as
TxSubmission's indefinite-length inner lists.

Verified against the live Leios dev relay (magic 164,
`leios-node.play.dev.cardano.org`): with the fix in, the relay
accepts `MsgLeiosBlockTxsRequest` and streams back the EB-tx list
without RSTing.  First test: `count=512` transactions delivered for
one EB, zero connection resets.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Clippy 1.92 lints the manual form; introduced on this branch via
DeepReorg behaviour and net-node's state-size log gate.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Diagnosing a wedged catch-up against the public Leios dev relay
required grepping across the orphan / fork-mismatch INFO traffic and
inferring the cause from cache state.  Two new WARNs hand the
diagnosis directly to an operator skimming logs:

- **ChainSync ingress contiguity check** in `record_peer_tip`: when an
  arriving header's `prev_hash` doesn't match the previously-announced
  one's hash, log the (block_no, hash) pair on each side and the
  implied skipped-block count.  Throttled per peer
  (`GAP_WARNING_INTERVAL = 10 s`) so a sustained non-contiguous forward
  doesn't flood the log.  This is the direct signal — the WARN fires
  the moment upstream commits the offence.

- **Stuck-validation rollup** in `retry_select_chain`: when validation
  has been frozen for `STUCK_THRESHOLD = 30 s` and some peer offers a
  strictly-better tip, emit one rollup line summarising stuck duration,
  adopted vs best-peer block_no, the count of entries in that peer's
  replay whose parent_hash we don't have locally, and the peer-chain
  size.  Throttled to one fire per `STUCK_WARNING_INTERVAL = 60 s`.
  This covers the general "stuck for any reason" case and stays
  informative when the ingress check has gone quiet under its
  per-peer cooldown.

Both lines were verified against the dev relay: ingress fires within
~30 s of catch-up reaching the wedge boundary (with the exact missing
block hash prefix in the message), and the rollup fires 30 s later
with `unreachable_parent_hashes > 0`, both throttled correctly under
sustained wedge load.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>