Skip to content

Rates Engine v0.5.0-rc.65

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 21 May 19:56
· 651 commits to main since this release

[v0.5.0-rc.65] — 2026-05-21

Added

  • defindex decoder now covers the vault-wrapper layer too (#49).
    Phase A (rc.58) decoded ("BlendStrategy","deposit"|"withdraw")
    the strategy contracts. That captured the underlying capital
    movement but from was always the vault contract C-strkey, not
    the end-user. A 2026-05-21 cross-check against Soroban-RPC
    getEvents showed we were at 27% coverage in a 12-hour window
    (and only 14% pre-rc.63 walker), because every user interaction
    flows USER → vault wrapper → strategy contract → Blend pool, and
    we were only seeing the strategy leg. Phase B adds
    ("DeFindexVault","deposit"|"withdraw") decoding for the
    user-facing wrapper layer: depositor / withdrawer (G-strkey),
    amounts / amounts_withdrawn (Vec — multi-asset support),
    df_tokens_minted / df_tokens_burned (share-token deltas).
    Dispatch is still purely topic-based (no contract address
    hardcoding) so every current AND future DeFindex vault wrapper
    the factory spawns (100+ in lifetime per SE) is decoded
    automatically. Audit doc updated with the two-layer model,
    cross-check methodology, and Phase-C+ scope (harvest, rebalance,
    factory create, typed flow hypertable).

Fixed

  • galexie-append.sh no longer skips ledgers on restart (#50).
    The wrapper used to ALWAYS start galexie at "archive tip minus a
    checkpoint margin," which silently created a multi-thousand-ledger
    gap in galexie-live whenever the service was restarted on an
    already-running deployment (the script's own TODO comment had
    flagged this; the 2026-05-21 ZFS topology migration is what tripped
    it — ledgerstream cursor was frozen at L62,669,692 for ~20 min
    before recovery). New behaviour: the wrapper first probes MinIO
    galexie-live via the existing galexie-writer MinIO credentials,
    finds the highest exported LCM, and resumes from
    last_exported + 1. The archive-tip-minus-margin path is preserved
    as the fresh-deploy fallback (empty bucket). Includes
    docs/operations/archival-node-bringup.md step-3 update.