How PACT is meant to work
A plain summary of the design sketched in programs/pact. None of it is deployed: the site runs in practice mode, the $PACT figures are a proposal, and nothing here is financial advice.
Programs
PlanVault
Records a buy and a ladder: sell one third at +10%, one third at +40%, and the remainder at +60%. A price drop sells nothing. In the design a keeper calls Jupiter to sell, with the route limited by transaction size and compute. The sketch does not swap yet.
PactRegistry
A caller’s bond, the wallets they declare, and a join window. In the design, followers escrow during the window, one settle records the fill, and each follower claims a pro-rata share, because one transaction cannot pay many followers. The sketch only keeps the books and holds no follower funds.
AgentPolicy
A spend cap, a mint allowlist, a mandatory ladder, and, as a design goal, a ban on transfers out, which the sketch does not enforce yet. The agent would be paid through x402 only from realized profit; that payment rail is described, not connected.
Price
SOL, USDC, and USDT may use Pyth. Other coins use a pool price that has to hold for at least eight slots, above a liquidity floor, with a minimum out and a default slippage cap of 1%.
Keepers
Anyone can crank a rung. Paid keepers are expected to. TukTuk is an optional backup. Clockwork shut down in October 2023 and is rejected by name in the sketch.
Threats we are designing against
The sketch refuses a Jupiter route longer than 20 accounts, a bundle that is not the single settle, and any keeper named Clockwork. A price drop sells nothing. This site never asks for a seed phrase or an external wallet.
$PACT token proposal
The token would be the bond callers and agents post, the pay for keepers, and a share of fees once the loop is real. Supply is not set. There is no public sale on this site.