Cardano Updates

Signed-off-by: Akhil Repala <[email protected]>

The in-memory store opened "file::memory:?cache=shared", an anonymous
shared-cache URI that SQLite resolves to a single process-global
database. Every store built via New("", ...) therefore shared one set of
tables, so the metadata tests were safe only because they ran serially.

Give each in-memory store a unique database name
("file:dingo_memdb_<N>?mode=memory&cache=shared") so connections within a
store still share, but separate stores are isolated, and mark the
package's tests t.Parallel(). The file-based production path is unchanged.

Cuts the package from ~31s to ~11s (-parallel=8) and the -race run
(make test) from 512s to 257s, race-clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Signed-off-by: Chris Guiney <[email protected]>

Signed-off-by: Tripura Repalle <[email protected]>

added:
* github:input-output-hk/mithril/cb1951a2b95b6f51b728535dfa7c9a42e83ed8ea#mithril-client-cli
* github:input-output-hk/mithril/cb1951a2b95b6f51b728535dfa7c9a42e83ed8ea#mithril-signer
* github:johnalotoski/blockperf/e77333de29e50cff6ce87bf683e58146563e8e4a#blockperf
removed:
* github:cardano-foundation/blockperf/626ad7b8255c6099b52fa05587e639c13d86751a#blockperf
* github:input-output-hk/mithril/a45341db66fcbb5cfac8c25b733bfeac848cd520#mithril-client-cli
* github:input-output-hk/mithril/a45341db66fcbb5cfac8c25b733bfeac848cd520#mithril-signer

Add an icon field rendered by AppIcon on cards and ToolDetail on detail pages (with an onError + colored-initial fallback). Source 79 icons under static/img/tool-icons/; Cardano Peer Connect intentionally has none and falls back cleanly. validation allows the icon key; showcase passes it through.

Reverses the earlier drop: Hydra ships hydra-node (a node you run to host an L2 head), so it belongs under Nodes & Network alongside Dingo and gOuroboros rather than being excluded as "just a protocol".

Dolos is TxPipe a lightweight Cardano "data node" (a third role beyond block producer and relay): follows the chain via Ouroboros and serves ledger data over Blockfrost-compatible REST, gRPC (UTxORPC), and Ouroboros node-to-client. Rust. -> Nodes & Network.

added:
* github:input-output-hk/mithril/cb1951a2b95b6f51b728535dfa7c9a42e83ed8ea#mithril-client-cli
* github:input-output-hk/mithril/cb1951a2b95b6f51b728535dfa7c9a42e83ed8ea#mithril-signer
* github:johnalotoski/blockperf/e77333de29e50cff6ce87bf683e58146563e8e4a#blockperf
removed:
* github:cardano-foundation/blockperf/626ad7b8255c6099b52fa05587e639c13d86751a#blockperf
* github:input-output-hk/mithril/a45341db66fcbb5cfac8c25b733bfeac848cd520#mithril-client-cli
* github:input-output-hk/mithril/a45341db66fcbb5cfac8c25b733bfeac848cd520#mithril-signer

Signed-off-by: Akhil Repala <[email protected]>

Add runAcquiredEbTxsSubscriber, the single writer of pendingTriggers. It
subscribes to the LeiosDb EB-notification channel and drains it forever. For
each AcquiredEbTxs notification (an EB whose closure has just become local) it
calls unblockCertRbsForClosure; an AcquiredEb is the body alone, the closure is
not yet complete, so it is ignored. Reading the notification and updating the
bookkeeping happen in one STM transaction, so no reader sees a CertRB that is
neither held back nor queued.

unblockCertRbsForClosure removes from announcementsMap every CertRB waiting on
the arrived EB and enqueues one reselection per removed CertRB onto
pendingTriggers. getBlockedCertRBs already stops holding these CertRBs back, so
the removal only keeps the map bounded; the enqueue drives the reselection.
Because removal and enqueue commit together, a re-arriving notification for the
same EB finds the entries gone and enqueues nothing, so each CertRB is enqueued
exactly once. A removed CertRB whose cache entry gcPruner already dropped is
skipped: the VolatileDB no longer holds that block, so reconsidering it is a
no-op.

This changes no behaviour: nothing forks the subscriber yet, so it does not run.
The ouroboros-consensus library builds under -Werror.

Bumps [github.com/blinklabs-io/gouroboros](https://github.com/blinklabs-io/gouroboros) from 0.180.0 to 0.181.0.
- [Release notes](https://github.com/blinklabs-io/gouroboros/releases)
- [Changelog](https://github.com/blinklabs-io/gouroboros/blob/main/RELEASE_NOTES.md)
- [Commits](https://github.com/blinklabs-io/gouroboros/compare/v0.180.0...v0.181.0)

---
updated-dependencies:
- dependency-name: github.com/blinklabs-io/gouroboros
  dependency-version: 0.181.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [modernc.org/sqlite](https://gitlab.com/cznic/sqlite) from 1.51.0 to 1.52.0.
- [Changelog](https://gitlab.com/cznic/sqlite/blob/master/CHANGELOG.md)
- [Commits](https://gitlab.com/cznic/sqlite/compare/v1.51.0...v1.52.0)

---
updated-dependencies:
- dependency-name: modernc.org/sqlite
  dependency-version: 1.52.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [golang.org/x/sync](https://github.com/golang/sync) from 0.20.0 to 0.21.0.
- [Commits](https://github.com/golang/sync/compare/v0.20.0...v0.21.0)

---
updated-dependencies:
- dependency-name: golang.org/x/sync
  dependency-version: 0.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.52.0 to 0.53.0.
- [Commits](https://github.com/golang/crypto/compare/v0.52.0...v0.53.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-version: 0.53.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

The node-snapshot (tvar) import path derived the current era's epoch size
from the network default (86400), ignoring custom-testnet genesis. Load the
history.<slot>.<hash>.json sidecar (as the .cbor path already does via
make_era_history) and use it to interpret the snapshot, but only for
Testnet(_); public networks keep the snapshot-derived history unchanged.

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

Two sites in amaru-ledger/src/state.rs were doing unchecked Epoch
subtraction on a u64-backed Epoch, producing u64::MAX-1 (or panicking,
depending on overflow checks) when the latest snapshot or the
slot-derived current epoch was below the rewards/leader-schedule
horizon (epoch < 2):

- StakeDistributionObserver::get_pool: `current_epoch - 2` becomes
  saturating_sub(2). Headers validated very early in the chain (or
  with a custom era history that maps slots to low epoch numbers)
  no longer surface a misleading
  "no stake distribution available for pool access 18446744073709551614"
  — the error now correctly says "pool access 0" and points at a
  real missing snapshot.

- initial_stake_distributions: `latest_epoch - Epoch::from(2)` and
  `- Epoch::from(1)` become saturating_sub(2) / saturating_sub(1).
  Bundles produced by amaru-bootstrap from cold-start short-epoch
  testnets (e.g. lambdasistemi/amaru-bootstrap#34's antithesis
  reproducer) where the most_recent_snapshot is epoch 0 or 1 no
  longer hit a u64 underflow on Ledger::new; for_epoch(0) is
  exercised normally and surfaces a sensible StoreError if the
  snapshot is genuinely absent.

This is a defensive correctness improvement only — it does not change
behaviour for any chain past epoch 2. Surfaced by the new live
amaru-run consumer test in lambdasistemi/amaru-bootstrap#35.

Signed-off-by: Paolo Veronelli <[email protected]>
Signed-off-by: paolino <[email protected]>

assert_leader_stake currently computes c = ln(1 - active_slot_coeff)
unconditionally. For genesis params with activeSlotsCoeff = 1.0
(used by the antithesis short-epoch fixture in
lambdasistemi/amaru-bootstrap and by the live consumer test in
lambdasistemi/amaru-bootstrap#35) this is ln(0), and pallas-math's
FixedDecimal::ln panics with "ln of a value in (-inf,0] is undefined".

When f = 1, every slot is leader-elected with probability 1 — the
leader-stake assertion is trivially satisfied for any pool with
non-zero relative stake. Mirroring the pre-existing zero-active-stake
guard added in b69fa13e, short-circuit to Ok before the ln call.

The math is continuous at f -> 1 (exp(x*c) with c -> -inf collapses
to 0, which is < recip_q, so the ordering is LT = Ok), so the guard
does not change behaviour for any f < 1.

Surfaced by the live amaru-run consumer test in
lambdasistemi/amaru-bootstrap#35 once
lambdasistemi/amaru#2 (saturating epoch subtraction) let header
validation reach this code path on a cold-start short-epoch chain.

Signed-off-by: Paolo Veronelli <[email protected]>
Signed-off-by: paolino <[email protected]>

Port of lambdasistemi 36ea009c onto upstream/main's rewritten state.rs.

Generated private testnets (db-synthesizer / amaru-bootstrap) can serve
block headers from the next leader schedule before the stable ledger
has materialized that epoch's snapshot. Add an opt-in forecast on
StakeDistributionObserver::get_pool that falls back to the latest
cached distribution when the requested epoch is strictly newer; only
enabled for NetworkName::Testnet(_).

Public networks (mainnet/preprod/preview) keep the existing strict
lookup behaviour.

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

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