Cardano Updates

The pre-fix predicate used 'Map.lookupMax txOffsets'' to read the
peer's recorded tx size for the size check. When the same tx hash
was referenced in two EBs with disagreeing recorded sizes (a
malformed body delivered under one of them, or any inconsistency
between 'missingEbTxs' and 'reverseEbIndexByTx'), the lex-max EB's
size won the lookup and silently vetoed every peer that offered
the closure.

Replace 'lookupMax + ==' with 'Map.filter (size == target)'
followed by 'not (Map.null …)'. The request now carries the
offsets of every entry that agrees with the target's authoritative
size and a peer is selected as soon as any agreement exists.

Adds 'Test.LeiosDemoLogic' covering 'leiosFetchLogicIteration' with ten
data-fixture scenarios via a small Scenario DSL: missing-body
selection (single peer, no offer, per-EB cap, two peers, global and
per-peer byte budgets) and missing-tx selection (single peer, per-tx
cap, tx referenced in multiple EBs with consistent and with divergent
recorded sizes). The last case is red against the current
'choosePeerTx': when a tx hash appears in two EBs with disagreeing
'txBytesSize', the maximal EB's entry vetoes selection and no request
goes out despite a peer offering the closure.

Adds a fyne-free notifications engine that consumes ConnectionManager
events, derives one rule per (kind, param) from a multi-target
SetupPlan (Wallets/DReps/Pools/MonitorEverything), and emits Requests
through a tumbling-window rate limiter that connection alerts bypass.
A Dispatch goroutine in setupTray turns each Request into a native
fyne notification — replacing the inline dispatchNotification. Rule
bodies render through Cardano-aware template helpers (trunc / ada /
outAddr / outAda / field) shared with the Telegram output via
internal/cardanofmt.

Wizard step 3 is rebuilt with three editable target sections plus an
exclusive Monitor Everything toggle, with cross-template validation
hints. SetRules atomically swaps the engine's rule set on
reconfigure (draining stale pre-swap Requests) so changes take
effect without a restart.

Filter persistence lives on TrayConfig (not the sidecar engine's
filter.cardano block) so multi-target plans don't get AND-combined
on transaction events. ToEngineConfig scrubs legacy knobs and a
one-time migration in SetupPlanFromEngineConfig preserves them
across upgrade.

Removes tray/adder_config.go (dead code; setup/codec.go is the live
SetupPlan→YAML path).

Closes #685
Closes #686

Signed-off-by: Ales Verbic <[email protected]>

Adds a fyne-free notifications engine that consumes ConnectionManager
events, derives one rule per (kind, param) from a multi-target
SetupPlan (Wallets/DReps/Pools/MonitorEverything), and emits Requests
through a tumbling-window rate limiter that connection alerts bypass.
A Dispatch goroutine in setupTray turns each Request into a native
fyne notification — replacing the inline dispatchNotification. Rule
bodies render through Cardano-aware template helpers (trunc / ada /
outAddr / outAda / field) shared with the Telegram output via
internal/cardanofmt.

Wizard step 3 is rebuilt with three editable target sections plus an
exclusive Monitor Everything toggle, with cross-template validation
hints. SetRules atomically swaps the engine's rule set on
reconfigure (draining stale pre-swap Requests) so changes take
effect without a restart.

Filter persistence lives on TrayConfig (not the sidecar engine's
filter.cardano block) so multi-target plans don't get AND-combined
on transaction events. ToEngineConfig scrubs legacy knobs and a
one-time migration in SetupPlanFromEngineConfig preserves them
across upgrade.

Removes tray/adder_config.go (dead code; setup/codec.go is the live
SetupPlan→YAML path).

Closes #685
Closes #686

Signed-off-by: Ales Verbic <[email protected]>

Add an integration test that exercises the actual Conway enactment path
rather than a modelled treasury: it seeds a ratified treasury-withdrawal
proposal plus a registered reward account, then runs governance.ProcessEpoch
followed by applyEpochDonations exactly as processEpochRollover sequences
them. It asserts the withdrawal is applied against the pre-donation treasury
(1000 - 400) and the donation is added afterwards (+300 = 900), and that the
withdrawal credits the reward account, closing the #2374 acceptance criterion
that a withdrawal is checked against the treasury value the ledger uses at the
boundary.

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

* fix(blockfrost): Made changes to align blockfrost transaction detail responses with OpenAPI 0.1.88

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

* fix(blockfrost): Fixed the bot comments

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

---------

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

* refactor(ledger): Made changes to decouple mempool provider transaction view

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

* refactor(ledger): Added a new test where it verifies the adapted mempool source feeds pending transaction CBOR into block construction

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

* refactor(ledger): removed the added test

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

---------

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

Conway transaction donations were never tracked, so the treasury (NetworkState)
drifted from the value the ledger would compute, which can make a future
treasury-withdrawal enactment validate against stale local state.

Wire the donation accumulator (added in the previous commit) into the ledger:

- Block processing (delta.apply) sums the Donation() of each valid transaction
  in a block and records it via AddNetworkDonation, keyed by block slot and
  tagged with the current epoch. Invalid (phase-2 failed) transactions do not
  contribute, since their body is not applied.
- The epoch rollover (processEpochRollover) moves the ending epoch's donations
  into the treasury via applyEpochDonations, after governance.ProcessEpoch.
  Ordering donations after enacted withdrawals matches the Conway EPOCH rule:
  a withdrawal is checked against the pre-donation treasury, and the donation
  is reflected for subsequent epochs.
- Chain rollback drops the donation rows after the rollback slot alongside the
  NetworkState rows, so treasury/reserves are restored and re-application
  re-derives the same total.

Tests cover the donation-to-treasury application, the no-donation no-op, and
the acceptance scenario: a treasury withdrawal followed by a donation at the
boundary, then a rollback restoring the prior treasury. DATABASE.md and
ARCHITECTURE.md document the new network_donation table/model.

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

Conway transaction donations need to accumulate during an epoch and move into
the treasury at the epoch boundary, but dingo does not track them. Add the
storage layer for that accumulator:

- NetworkDonation model (slot, epoch, amount), keyed by slot so a rollback can
  drop rows by slot like NetworkState. Amount is a plain integer column so SUM
  aggregates directly across all three backends.
- Store methods AddNetworkDonation (idempotent per slot),
  SumNetworkDonationsForEpoch, and DeleteNetworkDonationsAfterSlot, implemented
  for sqlite/postgres/mysql, plus the Database rollback wrapper.

Wiring into block processing, the epoch boundary, and rollback follows in
subsequent commits.

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

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

Rename the AncillaryGenesisData genesis_message field to genesis_message_preimage and gate it, with its getter, behind the future_snark feature.

Build an empty genesis ancillary data without future_snark and update the dummy accordingly.

Replace the function-level unused_variables allow with a scoped use.