API reference

Names below are copied from the fund program's source (programs/fund/src).

Instructions

Instruction	Who signs	Effect
`initialize_fund`	the program's upgrade authority, once	creates `Fund` with assets, routes, parameters, share mint and fee account
`init_vault(index)`	fund authority	creates the vault for asset `index`
`init_set_rules_comp_def`, `init_decide_comp_def`	fund authority	registers the two Arcium circuits
`set_rules`	fund authority	queues sealing of a new rule set; the callback stores it in `PendingRules` with its ready time
`set_rules_callback`	Arcium cluster	stores the sealed rules
`activate_rules`	anyone, after the delay	moves pending rules into `Rules`
`deposit(amount, min_shares)`	depositor	USDC in, shares minted at value per share and moved into the confidential pending balance
`request_decision(computation_offset)`	anyone	values the pool and queues `decide`
`decide_callback`	Arcium cluster	verifies the BLS signature, writes `Order`
`execute`	anyone	carries out the order through a whitelisted route, then checks every band
`redeem(shares, min_out[4])`	holder	burns public shares, pays the same fraction of each vault
`crystallize`	anyone	takes the performance fee above the high-water mark
`set_paused(paused)`	fund authority	pauses deposits, decisions and trades; never redemptions
`propose_authority`, `accept_authority`	fund authority, then the new one	two-step hand-over

There is no instruction that transfers from a vault to an arbitrary account.

Token-2022, 6 decimals, only the confidential transfer extension: auto-approve on, no auditor key, no confidential-transfer authority.

Route	Returns
`GET /api/prices`	USD prices for the eight assets, the slot and the source
`POST /api/rpc`	relayed Solana JSON-RPC (app)