Cardano Updates

Also reduce a diff in the test code

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

  Replace the hardcoded numToDistribute = totalUTxO - 1 in the partial
  fanout benchmarks with a binary search that finds the largest chunk
  actually fitting within both the tx size and execution budget, mirroring
  findFittingFanoutTx in the real node. The Remaining column in the output
  table now carries meaningful information instead of always showing 1.

  Also add ContestationDeadlineOutsideTimeHorizon to the PostTxError
  oneOf in api.yaml, which was defined in Chain.hs but missing from the
  schema, causing ServerOutputSpec to fail.

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

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

  computeFinalPartialFanOutCost was capped at 7 (fanoutChunkSize), hiding
  the real tx-size limit for the terminal fanout step. Now it sweeps a wide
  range and searches for the actual maximum, using a single preceding output
  as minimal setup to reach FanoutProgress.

  computePartialFanOutMixedCost also dropped its fanoutChunkSize cap and
  now distributes all-but-one outputs, consistent with the nominal benchmark.
  The stale description mentioning fanoutChunkSize is corrected accordingly.

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

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

Signed-off-by: jeluard <[email protected]>

  fanoutChunkSize and fanoutOutputThreshold are now defined once in
  Test.Hydra.Tx.Fixture and imported wherever needed, removing the
  per-file duplicates.

  prepareTxToPost gains explicit FanoutTx/FinalPartialFanoutTx branches
  (error) so GHC's exhaustiveness checker catches any future unhandled
  constructor, instead of silently falling through a wildcard.

  The two deadline-slot conversions in mkChain.postTx now throw
  FailedToConstructFanoutTx (a PostTxError Tx) instead of userError,
  so the exception is caught by Node.hs's PostTxError handler rather
  than propagating uncaught and crashing the node.

  HeadLogic no longer uses fanoutChunkSize or fanoutOutputThreshold to decide
  which tx type to emit. For a fresh fanout it always emits FanoutTx; for an
  in-progress fanout it always emits FinalPartialFanoutTx. Handlers now owns the
  sizing decision: it tries the preferred tx first, then falls back to
  PartialFanoutTx with a decreasing chunk size (starting at N-1) until one fits
  within the execution budget, using a single shared findFittingFanoutTx helper.

  PartialFanoutTx is removed from PostChainTx — it is now an internal Handlers
  detail, never emitted by HeadLogic. fanoutChunkSize and fanoutOutputThreshold
  are removed from KZGTrustedSetup and all call sites.

Signed-off-by: Eric Torreborre <[email protected]>

  Remove utxoHash/alphaUTxOHash/omegaUTxOHash from ClosedDatum, all
  Close/Contest redeemers, and the snapshot signing tuple. The BLS
  accumulator already commits to the full UTxO set (utxo ∪ alpha ∪
  omega), making the three separate SHA256 hashes redundant.

  Full fanout now verifies outputs via a KZG membership proof (same as
  partial fanout) rather than hash comparison. The Fanout redeemer gains
  proof and crsRef fields; the three output-count fields are dropped.

  Snapshot signing shrinks from a 7-tuple to a 4-tuple
  (headId, version, snapshotNumber, accumulatorHash).

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

Previously use_tcp was hardcoded to false on every LinkConfiguration.
Now RawParameters::tcp_congestion_control (default true) is propagated
to all links during SimConfiguration::build, so users can disable the
TCP congestion-window model via yaml with `tcp-congestion-control: false`.

Update config.schema.json to reflect Rust support and add default: true.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

Port the Haskell `Chan/TCP.hs` channel abstraction to Rust.

`TcpConnection<TMessage>` models one direction of a full-duplex TCP link
using `forecast_tcp_msg_send` for timing. Key design decisions:

- Backpressure via `send_cursor`: the effective send time is
  `max(now, send_cursor)`, so overlapping sends queue behind their
  predecessor — the same role the one-slot `TMVar` plays in Haskell.
- Idle reset (RFC 6298 RTO): when the link has been quiet for longer
  than `max(1 s, RTT)` and all in-flight ACKs have returned, the
  congestion window is reset to the initial value.
- Messages are queued with arrival time = `recv_trailing_edge` (the
  receiver needs the complete message, not just the leading edge).

Integration:
- `ConnectionKind<TP, TM>` enum wraps both `Connection` (bandwidth-
  sharing) and `TcpConnection` with a uniform interface so the rest of
  the network layer is unchanged.
- `LinkConfiguration` and `EdgeConfig` gain a `use_tcp: bool` flag
  (default `false`); both the actor and sequential engines route through
  `ConnectionKind::from_config`.
- `TcpState::all_acks_arrived` added to support the idle-reset check.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

Port the Haskell `ModelTCP` module to Rust as `sim-core/src/tcp.rs`.

The model forecasts send timing for a stream of messages over a single
TCP connection, accounting for serialisation delay, one-way propagation
latency, and the congestion window (slow-start through to steady state).

Key design points:
- `forecast_tcp_msg_send` is a pure function: takes props + state + now
  + message size, returns the overall forecast, per-fragment forecasts,
  and the updated state.  No IO, easy to test.
- ACKs are anchored to the *receive leading edge* ("strategic cheat"):
  approximates per-segment ACK pipelining without modelling individual
  segments, preventing the model from understating throughput.
- `merge_adjacent_fragments` collapses contiguous window-fill chunks so
  the fragment count stays bounded across long sends.
- Six unit tests cover: small message timing, per-fragment invariants,
  large-message fragmentation, fragment merging, and the trace helper.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

* mithril-aggregator from `0.8.52` to `0.8.53`
* mithril-client-cli from `0.13.11` to `0.13.12`
* mithril-client-wasm from `0.10.4` to `0.10.5`
* mithril-client from `0.14.9` to `0.14.10`
* mithril-signer from `1.0.2` to `1.0.3`
* mithril-stm from `0.10.22` to `0.10.23`
* mithril-end-to-end from `0.4.134` to `0.4.135`
* [js] mithril-client-wasm from `0.10.4` to `0.10.5`
* mithril-test-lab/mithril-devnet/VERSION from `0.4.33` to `0.4.34`