Cardano Updates

  UTxO fields are no longer stored on TransactionAppliedToLocalUTxO,
  SnapshotRequested and DecommitRecorded events — aggregate recomputes
  them via pure applyTxTo arithmetic, reducing per-event size to the tx
  itself. localTxs is changed from [tx] to Seq tx to avoid O(n) appends
  on every incoming transaction.

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

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

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

  newLocalUTxO was carried on TransactionAppliedToLocalUTxO,
  SnapshotRequested, and DecommitRecorded but is fully derivable from the
  event's tx (or snapshot fields) plus current state. Aggregate now
  recomputes it via a new IsTx method `applyTxTo` (pure UTxO arithmetic,
  no ledger validation).

  Removes O(N²) on-disk growth on Growing-UTxO workloads. JSON format is
  forward/backward compatible — old event stores still parse.

  Measured (bench-e2e --utxo-size Growing -n 2000):
  - hydra.db:         1.6 GB → 526 MB  (-67%)
  - hydra-node-0.log: 2.1 GB → 1.1 GB  (-48%)
  - avg confirm:      92.9 ms → 84.1 ms (-9%)

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

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

  Three cleanups spotted while reviewing the newLocalUTxO removal:

  - waitApplyTx and waitOnApplicableDecommit no longer pass the validated
    UTxO to their continuations (the callers stopped using it after the
    newLocalUTxO removal). Validation still happens; only the unused
    continuation arg is dropped.

  - pruneTransactions: rewrite from foldl' with `txs <> [tx]` (O(n^2))
    to guarded recursion with `tx : go u' rest` (O(n)). Threading the
    running UTxO through `go` is still required for validity checks
    on dependent txs.

  - TransactionReceived aggregate: replace `allTxs <> fromList [(k,v)]`
    with `Map.insert k v allTxs`. Same big-O class but eliminates the
    intermediate singleton-Map allocation per ReqTx.

  No behavioural change. Constant-factor wins on the per-ReqTx hot path.

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

Unify simple phases into `MonoSimplePhase`

The previous flow assumed Send.run would resolve to the mediator's
keylist-update-response. In practice it always resolved to undefined:
DIDCommConnection.send returned the registered handler's result rather
than the parsed message, and the SDK never asked the mediator for an
inline reply. Per coordinate-mediation 2.0 the mediator only answers
synchronously when the request carries `return_route: "all"`, and
Mercury auto-attaches that header for the piuris in ReturnRouteProtocols
(packages/wasm/didcomm/src/Wrapper.ts) -- but keylist-update was never
on that list. So every keylist-update went out without return_route, the
mediator dispatched the response asynchronously, and the client never
observed it.

Add keylist-update to ReturnRouteProtocols, make DIDCommConnection.send
return the inline response, and rewrite updateKeyListWithDID to send the
message, race the call against a 60 s timeout, assert the response is a
Message with the expected piuri and a thid matching the outgoing id, and
validate the body via MediationKeysUpdateResponse (throws on any
non-success / non-no_change result).

Tests cover success, no_change, client_error, server_error, malformed
body, timeout, wrong piuri, wrong thid and a missing response. A guard
on ReturnRouteProtocols prevents the same kind of regression that
originally introduced this bug (PR #85).

Closes #391

Signed-off-by: Seydi Charyyev <[email protected]>

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

Reverts the two stub commits 0b8d6f6 / 3d649af in stable-haskell/iserv-proxy
(`flake.lock` was bumped to them in haskell.nix commits 3303ea332 /
11c3abf88).  Those commits added local definitions of bionic-absent
symbols (`__cxa_guard_acquire`, `__cxa_guard_release`, `__fadvise64`,
`__getpriority`, `__ldtoa`, `__sflush`, `__vfprintf`,
`async_safe_fatal_no_abort`, `async_safe_format_buffer`) to
`cbits/symbols.aarch64-android.c` to satisfy ld.lld during a link
where they were undefined.  In the current build configuration (NDK
27, current cabal flags, ghc 9.14.1) those symbols already resolve
cleanly without the stubs — and the stubs were displacing the real
bionic / libc++ implementations at runtime, causing the qemu
segfault on aarch64-android iserv-proxy-interpreter that we'd been
tracking as a separate "qemu builder" issue.

Verified `tests.js-template-haskell.build` on
`ghc9141.aarch64-android-prebuilt` passes with the override
`--override-input iserv-proxy github:stable-haskell/iserv-proxy/8cdc446f`
on linux-0 with `--builders ''`: iserv-proxy-interpreter links and
runs under qemu-aarch64 with no segfault.

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