Documentation

Using SHARD

Overview

A structure is one deposit of an SPL token, divided into claims. Each claim has an owner wallet, an exact token amount and an unlock schedule. Claims always add up to exactly the deposit; nothing is created out of thin air.

Every claim is a contract in Streamflow's Vesting & Locks program. SHARD deploys no programs of its own. It builds transactions for that existing program and your wallet signs them.

Claims & schedules

Claim types (Liquid, Cliff, Vesting, Treasury, Community) describe purpose. The schedule describes when tokens unlock:

• Immediate: fully redeemable about 90 seconds after creation (the program needs a start time slightly in the future).
• Cliff: everything unlocks on one date.
• Linear vesting: an optional upfront share at the start, then equal unlocks every hour, day, week or 30 days until the end date.

Treasury and Community are labels for who holds the claim; they use the same schedules and never add collateral.

Creating a structure

Connect a wallet, pick a token and amount, add claims, set schedules, review. When you press Create structure, SHARD simulates every claim transaction first. Only if all simulations pass does your wallet show one approval for all of them. Each claim is then submitted and confirmed individually, and you see its signature as it lands.

If a submission expires or fails, Retry submits only the unconfirmed claims again. Each claim's contract address is fixed before the first attempt, so a claim can never be created twice.

Redeeming & transferring

The claim owner can redeem whatever has unlocked at any time, from the Dashboard, My claims or the structure page. The program calculates the unlocked amount itself. The owner can also transfer the claim to another wallet; the schedule and remaining tokens move with it.

Custody & enforcement

Tokens are held in escrow accounts owned by the Streamflow program. SHARD creates claims as cancelableBySender: false, transferableBySender: false, transferableByRecipient: true, canTopup: false. In practice: the creator cannot claw tokens back or move a claim, only the owner can transfer or redeem, and the escrow can never hold more or less than the claim.

SHARD stores nothing about your claims on a server. The interface reads chain state and builds transactions; it never sees or stores private keys.

Fees

SHARD charges nothing. Streamflow charges a token fee (a percentage added on top of each deposit) and a SOL creation fee for every contract, and each claim is one contract. Both are read live from Streamflow's onchain fee oracle and shown before you sign. As of October 2026 that is 0.19% and 0.16 SOL per claim on mainnet, so a structure with four claims costs about 0.64 SOL in creation fees plus account rent and network fees. The creation fee is not refundable.

How data is indexed

Each claim's onchain name starts with SHARD: followed by the structure id, claim type, structure title and claim label. SHARD's server queries the Streamflow program for accounts whose name (byte offset 463) begins with that prefix, groups them by creator and structure id, and caches the result for a few seconds. Claims from another creator can never be injected into your structure.

Network & address

SHARD runs on Solana mainnet only. Every transaction uses real tokens and real SOL, so start with a small amount.

Limitations

• Classic SPL tokens only. Token 2022 mints and native SOL are not enabled yet (wrap SOL to wSOL first).
• Up to 8 claims per structure. Each claim is a separate transaction; they are approved together but confirm independently.
• Claims cannot be edited or cancelled after creation. This is by design.
• No prices: amounts are always shown in token units.
• The SHARD interface has not been audited. Streamflow's program has its own audits; review them before committing significant value.

FAQ

Can SHARD freeze or take my tokens? No. SHARD has no authority over the contracts. Only the program's rules and the claim owner's signature move tokens.

What if this website disappears? Your claims still exist onchain and can be redeemed through any interface that supports Streamflow or directly with the Streamflow SDK.

Why did my structure take a moment to appear? The index refreshes every few seconds. Confirmed claims always appear; nothing confirmed is ever lost.