Cardano Updates

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Pat Losoponkul <[email protected]>

Co-authored-by: zeme-wana <[email protected]>

Pin cardano_amaru to the producer image published from amaru-bootstrap main
(lambdasistemi/amaru-bootstrap@fba902da), which bundles amaru
feat/testnet-bootstrap: create-snapshots offline mode + bootstrap migration,
runtime era-history/global-parameters, testnet tvar era-history sidecar fix,
and the short-epoch ledger/consensus fixes.

Signed-off-by: Chris Gianelloni <[email protected]>

Signed-off-by: Pat Losoponkul <[email protected]>

Signed-off-by: Pat Losoponkul <[email protected]>

Previously, when starting an analysis from a ledger state, openLedgerDB
loaded the newest snapshot at or before --analyse-from but used an empty
stream, so no blocks were replayed. If no snapshot existed exactly at the
requested slot, the analysis silently started at the older snapshot's tip
instead of at --analyse-from.

Hand openLedgerDB the ImmutableDB and replay blocks on top of the chosen
snapshot up to the replay goal (the --analyse-from point), so the ledger
state is exactly there before the analysis begins. The stream stops at the
first block past the goal, mirroring the StartFromPoint behaviour where
the analyse-from block is the anchor and processing starts after it.

Emit a warning when no snapshot exists exactly at the requested slot, since
the replay from an older snapshot up to the goal can be slow.

Paint the gradient and starburst SVG as layered backgrounds on the hero element instead of a z-index:-1 ::before, which was hidden behind Infima .hero--primary opaque background. The SVG circles are #0033AD and now contrast against the lighter gradient, matching cardano.org/apps.

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]>

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]>

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

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]>