SLUICE docs
v0.1.0
Live demo Get help
● Reference · Versions

Changelog
what changed, when.

Every release, newest first. The same history is in CHANGELOG.md in the package.

011.0.0 · 2026-09-21

Current First release: the engine and the console.

Built

  • Solana layer in-tree: base58, ed25519 curve check, PDA and associated token address derivation, read-only JSON-RPC with endpoint rotation and backoff, Helius DAS holder enumeration, Dexscreener pair lookup.
  • Token-2022 aware throughout; transfer-fee and transfer-hook extensions detected and warned about.
  • Snapshot at the current slot; a time-weighted variant in the engine.
  • Exclusions with evidence: off-curve detection, an AMM program registry that can be verified on chain, Dexscreener venue labels, an exchange-omnibus heuristic that flags, operator lists.
  • Pro-rata and tiered computation in integer base units, with a largest-remainder rule and an iterating dust rule.
  • Operator fee: empty by default, capped at 200 basis points in code.
  • Merkle tree with domain-separated leaves and proof verification; direct transfers as unsigned batches; a cost model for both routes.
  • Dry run, audit trail with on-chain signature confirmation, reproducibility check, realised rate over a past window.
  • Vocabulary presets, unclaimed policy, recurring schedules.

Not built in this version

  • No on-chain claim program: SLUICE produces the root, proofs and parameters; the program is yours.
  • Claim state is read from signatures you attach, not from the chain.
  • No looking through vaults or LP positions.
  • No retroactive time-weighted windows (they need an archival node).
  • The browser wallet connector is unverified; the claim page falls back to entering an address.
  • No separate claim-page entry point; --wasm web builds fail.
  • Placeholder icons only.

Migration: none, first release.

02How to update

  1. Back upExport the proof bundle of every round you care about.
  2. Keep your changes in GitCommit the original package on a vendor branch before you change anything, then unzip each new version onto that branch and merge it into your own.
  3. Check
    flutter pub get
    flutter analyze
    flutter test
  4. RebuildLocal data stays on the machine; read the entry for your version for any migration.