Distribution lifecycle

Fractals Sync is an on-chain distribution engine for any SPL token. It wraps the Jito merkle distributor program and ships two SDK layers:

@fractalshq/jito-distributor-sdk — low-level builders and instruction helpers for the on-chain contract.
@fractalshq/sync (planned) — white-glove distribution toolkit: creation + claim flows, pricing helpers, and auth integration so partners can drop in Sync with minimal wiring.

Product pillars

Reusable cohorts. Upload CSVs, keep project-wide recipient lists in sync, label addresses, and reuse splits across distributions without reformatting each time.
Managed auth. Sync runs SIWS (via @fractalshq/auth-core + @fractalshq/auth-react) so your backend just adds a global route handler and inherits secure wallet sessions.
Universal transaction constructor. Partners call the Sync API (@fractalshq/sync) and receive a fully formed transaction (compute budget, PDAs, funding, memos, assertions) without touching on-chain plumbing.
Predictable claims. End-user claims cost up to ~$0.50; Token-2022 wrappers are handled automatically.

Lifecycle summary

Create distribution. Sync aggregates accounts, computes the merkle root, derives PDAs, and returns a single transaction that initializes + funds the distribution. Dive into the Create distribution flow for instruction-level detail (with mermaid chart).
Serve proofs. Sync hosts the merkle tree (or you can fetch it through our API) so recipients request their proof + amount safely.
Claim rewards. Users call our claim endpoint or embed the claim widget; under the hood we wrap Token-2022 mints if needed and submit newClaim. Explore Claim flow for account layout and failure cases.

Typical on-chain cost for the create transaction is 0.00460056 SOL (2,561,280 lamports for the vault + 2,039,280 lamports for the clawback). At SOL = $110 that’s about $0.51 USD.

Accounts at play

Distributor PDA: holds the merkle root, vesting window, admin list, and total allocation.
Vault ATA: SPL token account owned by the distributor; stores the tokens to be claimed.
Clawback PDA: receives remaining funds after clawbackStartTs if admins claw back.
Recipient proof leaf: address + amount + proof index stored off-chain and served via API.

Reference packages/jito-sdk/README.md for the finalized low-level SDK and packages/distributor/README.md for contract internals. Everything else is orchestrated through the higher-level @fractalshq/sync API so you can ship distributions without touching Solana-specific details.