Sheaf Preview
Preview. Nothing is deployed and no money can move. Every number here is computed from the published rules. Where these numbers come from

Your token, already graduated.

Fund a declared bundle with your own SOL. It buys the whole curve in the transaction that creates your token, then sells under a speed limit the program enforces. At most a quarter of the block per window. Never empty before four hours after launch.

Launch a bundle See how it works
Schedule
  1. SHEAF mints on pump.fun
  2. First Sheaf bundle
The first bundle is funded with the builder’s own SOL, under the same caps as any creator’s. Both dates are scheduled, not fixed.

Bundles

How it works

Three steps. Nothing in between them is discretionary, and no person decides any of it once the bundle is created.

This bundle at a glance

nothing here rates this bundle

Read this before you read anything else. Its trading rule sells and never buys; apart from it, the vault’s one purchase is clear_tier, once after launch, to reach the venue’s 420 SOL fee tier. The program caps it at 5 SOL, toward at most 450 SOL of market cap, on every bundle. It does not support the price, it does not provide depth, and it is not a liquidity provider: on this kind of pool a trading vault is a taker like anyone else.

Details

everything the surface above leaves out
What this program can and cannot do seven instructions
deposits

Seven instructions. No instruction accepts a deposit from any account other than the creator who opened that bundle. Not disabled, not paused. Absent. deposit is called once, by initialize_bundle, with initial_deposit = tvl_cap_quote in the same atomic transaction, which fills the cap before any other transaction can land.

more bundles

who can change it

No one. The upgrade authority is set to None at deploy, so there is no admin, no allowlist and no pause. The honest limit alongside that: nothing stops a different program being deployed at a different address, so this is friction and visibility rather than impossibility.

How the vault trades

Where these numbers come from no RPC, no API key
derivation, not invention

Nothing is deployed, so there is no chain to read. Every figure on this page is produced by running the published rule in docs/STRATEGY.md s2.3 step by step against the curve model in docs/ECONOMICS.md s1, under the parameters in docs/IMPLEMENTATION.md s3.4. Addresses that do not exist print as their derivation, never as invented base58.

the picture on each bundle

checking it yourself, once it is live

Every trade the vault makes is findable from the program ID alone, with no indexer and no API key, through a marker account at findProgramAddress([Buffer.from("vault_trade"), bundle], PROGRAM_ID), one marker per bundle. Call getSignaturesForAddress on it and keep the transactions that succeeded and whose instruction is this program’s crank or clear_tier, and you have every vault swap in order. The second filter is required: anyone can list the marker in an unrelated transaction, and those are not trades.

What nobody here is telling you the disclosure
this is not advice

Nothing on this page says any of this is a good idea. There is no entity behind it and no person who owes you anything. No one is required to keep this running, answer a message, or fix a defect.

whether it makes money

Unmeasured. The rule is published and deterministic, which means you can check what it will do. That is a different claim from it being profitable, and the second claim is not made anywhere on this site.

a fee nobody here controls