Skip to content

v0.2.2 — every scenario proven both ways, in both directions

Choose a tag to compare

@mandrigin mandrigin released this 13 Sep 18:28
26c2b2e

v0.2.2 — every scenario proven both ways, in both directions

The whole scenario matrix now passes twice on the same Node methods: through
the Nodes' owner APIs and by pressing the real Basecamp desks, in both
Bitcoin directions (the Taker sells BTC, the Taker sells LEZ), including both
refund cases, overlapping swaps, Node restarts, and the two review
follow-ups on configuration and late-observed claims. Doing that on a stack
that had run for a day exposed and fixed a set of defects in the Nodes, the
desks and the local chain tooling. Fourteen narrated recordings and a
per-scenario reproduction guide ship with the evidence.

What changed

  • The Taker sells LEZ (#41, via #42): the reverse direction end to end.
    The Taker locks LEZ first, the Maker locks Bitcoin, the Taker claims
    Bitcoin; refunds and recovery in that direction; both desks label the legs
    by what the owner locks and claims.
  • Wallet balances (#40): each Node reports its own Bitcoin wallet and LEZ
    owner account (maker_wallet_balances_v1, taker_wallet_balances_v1);
    the desks show them under the account selector.
  • Refund only after the cutoff (#43): the Taker desk offers the refund
    once the Maker's lock cutoff has passed, not at the first observation.
  • Fixes found by the scenario runs (#42), each reproduced on the stack,
    fixed and run again in both directions and both ways:
    • an unsent Maker lock is never sent past the cutoff. The recovery path's
      freshness read consults the chain clock, which trails the wall clock
      (Bitcoin's median time by about an hour on mainnet, ten minutes on
      regtest); a Maker restarted just after its cutoff still locked, and the
      Taker then saw a late lock it could neither claim nor refund against.
    • the Taker's second sell-LEZ lock waits for the previous one at the
      sequencer, not in the finalized view, which the devnet's L1 pauses for
      minutes at a time.
    • a submitted Taker claim stays observed across the claim window's close
      (the #32 follow-up); a Maker past its cutoff still projects a lock it
      sent in time; a Maker lock spent by the Taker's claim, and a Maker LEZ
      funding the Taker has claimed, are still canonical locks; exact and
      discovered LEZ refund lookups trail the finalized tip.
    • the LEZ v0.2.0 indexer kept losing its breakpoints on a restart
      (carried source patch); the Node's sidecar client repeats a request
      whose transport failed; owner replies may be 4 MiB.
    • desks: one silent market read in flight at a time and explicit reads
      never dropped; the refunded Maker leg reported as such; the market
      snapshot and the replies that embed one (publish, withdraw, take, lock,
      claim, refund) use a 4 MiB budget while ordinary calls keep 64 KiB.
  • Configuration regression scenarios (#42, the #28 follow-up):
    node-e2e.py regenerated-config (re-rendered live configuration and a
    Taker restart; the swap reloads and completes) and tampered-config (one
    altered byte in a swap's saved copy; the swap is refused after a restart).
  • Test tooling (#42): deploy/scripts/node-e2e.py all [--direction TakerSellsLez] and deploy/scripts/ui-e2e.sh all [--direction TakerSellsLez] [--record] drive the same scenarios through the APIs and
    through the desks; --record films each scenario with narrated subtitles;
    LEZ_BTC_ACTOR_TRACE=1 names every actor decision; dump-swaps.sh
    keeps both Nodes' state before a reset; up.sh --fresh is one unattended
    clean bring-up (#38); the release jobs pull the pinned builder image (#39).
  • Evidence for the review (#42): docs/evidence/review-2026-09-12/
    answers the ecosystem review index item by item, with the harness
    summaries of every scenario, the recorded swaps' on-chain exports and a
    reproduction guide per scenario (REPRODUCE.md).

Verified

On the release commit: workspace clippy and tests; verify-all with both desk
suites; the nine scenarios plus the two configuration scenarios through the
APIs in both directions (22/22); the seven desk scenarios in both directions
(14/14), on clean history (filmed) and again on a day of accumulated history;
all 14 CI checks. Fast timing profile (cutoff 600 s, refunds 900 s/1200 s,
CSV 6 blocks).

Install

  • Prebuilt stack: download the bundle attached to this release and run
    scripts/start.sh (pulls ghcr.io/gateway-fm/lez-atomic-swaps/lez-*:v0.2.2);
    scripts/start.sh --swap adds one complete swap through the two desks.
  • Basecamp apps: add the catalog
    https://raw.githubusercontent.com/mandrigin/logos-modules-release-base/main/logos-repo.json
    in Basecamp's package manager and install LEZ / BTC Maker and
    LEZ / BTC Taker 0.2.2.

Not in this release

The Maker's offer list still returns the Node's whole offer history, so a
desk snapshot grows with age (a state filter is the next change). The
verified desk path is the bundled VNC environment; a native Basecamp with the
catalog modules is published but not exercised by these runs. XMR and ZEC
pairs are unchanged. Remote signing with external wallets remains a plan (#30).

Entry points