fix(bifrost/solana): align SOL solvency reports to SolvencyBlocks cadence

Problem

Closes #3065 (closed).

SOL solvency reports were using each node's live Solana slot, floored by a hard-coded /10, as the reported solvency Height.

That height is part of the solvency ID hash:

Hash(Chain, PubKey, Coins, Height)

Because SOL nodes naturally see slightly different live slots, reports for the same vault were split across many IDs and could fail to reach consensus. Those pre-consensus reports still accrue observe slash points, but the refund path only runs when the exact voter reaches consensus.

Fix

  • Remove the unrelated SOL solvency /10 height floor.
  • Report SOL solvency Height on the configured SolvencyBlocks cadence.
  • Advance solvencySlotMultiple one cadence boundary at a time, with a fresh-node catch-up case, instead of jumping directly to height / SolvencyBlocks.
  • Bump SOL solvency_blocks default from 50 to 500 so the bucket is comfortably wider than normal SOL slot spread and scan interval drift.
  • Add regression coverage proving ReportSolvency emits the cadence-aligned height when SolvencyBlocks != 10.

Notes

This fixes the height-fragmentation root cause for SOL solvency consensus. Coins are still read from the live finalized tip because SOL account balance reads are not currently pinned to the floored height; if balances change inside a bucket, that can still create separate IDs and should be tracked separately.

Merge request reports

Loading
Loading