Start
What Pook is
Pook lets you use the Solana protocols you already use from a private balance. You hold assets in Pook, pick a hook such as jupiter.swap, and run it. The protocol is called for you, the result lands back in your private balance, and your wallet is not in the transaction.
The four things in Pook
A private balance. Assets you hold inside Pook, as encrypted notes in Solana Privacy Rings. You enter from a public wallet or a Rings private balance, and leave to either. Notes and the private balance
A hook. A public record that describes one instruction of an existing program: which program, which bytes, which accounts. Publishing one makes that instruction callable from a private balance. The program it describes does not change. Hooks
A run. One action through one hook, as a single transaction. It spends your notes, calls the protocol and deposits what comes back, or it does nothing at all. A relayer submits it, so the chain records the relayer where your wallet would be. Runs
A seat. For a position that stays open, like a loan, the owner the protocol sees is a seat: an address no wallet controls. The right to command it is a note in your balance. Seats
- 1ProofPook verifies the holder’s proof. It binds the hook, the accounts and data, the amount in, the minimum out, the owner of the output, the relayer’s fee and an expiry to this one transaction.
- 2SpendThe holder’s notes are nullified, change returns as a new note, and the amount in moves to the stage.
- 3CallPook calls the protocol exactly as the hook describes, signing as the stage.
- 4CheckPook measures what arrived in the stage. Less than the minimum out fails the whole transaction.
- 5DepositThe run fee and the relayer’s fee come off, and the rest becomes a new note for the owner the proof fixed.
What you can run today
Pook published 9 hooks at launch, across Jupiter, Kamino, Jito.
| Hook | Type | Meaning |
|---|---|---|
jupiter.swap | flow | One asset in, another out, at Jupiter’s route. |
kamino.supply | flow | An asset in, its Kamino deposit token out. |
kamino.withdraw | flow | A Kamino deposit token in, the asset out. |
jito.stake | flow | SOL in, JitoSOL out. |
jito.unstake | flow | JitoSOL in, SOL out. |
kamino.collateral.deposit | seat | Collateral in. The first deposit opens a seat. |
kamino.borrow | seat | Borrows against a seat’s collateral. The borrowed asset comes out. |
kamino.repay | seat | An asset in, the seat’s debt down. |
kamino.collateral.withdraw | seat | Collateral out of a seat. |
Anyone can publish more. The registry lists every hook with its author, its runs and its volume.
Three ways in
From code, a run is one line of @pook/sdk:
await pook.run("jupiter.swap", { in, out, amount })What an observer sees
A run's transaction shows the hook, the assets, the amounts and the relayer. It does not show who ran it or what they hold. What the chain shows lists every public field of every kind of transaction, and the run feed shows runs live as the chain shows them.
How these docs are laid out
- Concepts explain each part once: hooks, runs, notes, seats, relayers, what the chain shows, and the fees.
- Guides take one task from the first step to the state it ends in, in the app and in the SDK.
- Reference holds every exact value: the SDK's exports, the hook schema, the program's accounts, instructions and errors, the API's routes, and the addresses.