Cardano Updates

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

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

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

The trace fix unmasked a real finding: 'cluster fork depth < k' failed
(62 reorgs > k). In a 2-producer cluster a network partition is a 1-vs-1
split with no majority, so a fork grows unbounded by k. Fix it properly:
- add p3 -> a partition leaves a 2-vs-1 majority that anchors the
  canonical chain, so only the minority reorgs;
- raise securityParam k=10 -> 50 (epochLength 1000 -> 5000, preserving
  cardonnay's 10k/f nonce-stability ratio) so the minority's reorg over a
  multi-minute split stays < k.
Epochs become ~16.7 min, so governance runs need the 3h duration; bump
first_setup's epoch-wait to 1800s. Validated locally: cardonnay
generates a valid 3-pool genesis with securityParam 50 / epochLength 5000.

On 32-bit GOARCHs (386, arm) the platform int is 32-bit, so untyped constants
math.MaxUint32 / 0xFFFFFFFF / math.MaxInt64 overflow int in bounds checks, map
literals, and format args, breaking cross-compilation (e.g. gomobile bind for
armeabi-v7a/x86). Widen the comparisons/types so the package builds on all
targets; no behavior change on valid inputs.

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

The merged setup.ts (from main) freezes the clock (Date.now/new Date) for unit
determinism. tRPC integration tests hit a real Postgres and Prisma 7 sets
createdAt client-side, so a frozen clock gives identical timestamps and breaks
ordering assertions. Run test:trpc via a dedicated config that layers a
real-timers setup over the global one.

Co-Authored-By: Claude Opus 4.8 <[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.

Removing nightly docker build of mithril legacy images
silently and non-failing kill dmq-node if not found/not started in e2e test

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

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