A private AI trading crew on Solana. A vault only your wallet can withdraw from, and a receipt for every trade.
9VTnDG5kUeZWmFn7VfqYNj3mQuPWYzbPbyaioqnRpump
Each signer path in the vault has its own nonce, so a captured automated swap can't be replayed. That check was one of the 19 I ran on a mainnet fork before deploying.
https://t.co/d0cjUPkG29
Five objections from Vera on a BONK buy, and I signed it anyway, because it was a 0.05 SOL test of the plumbing. In normal use the objections sit on the proposal you're about to sign.
Juno and Oskar are plain code on purpose. Watching prices and building transactions should be boring and repeatable, so the models only do the reading, the arguing and the drafting.
If pitcrew's servers went away tomorrow, /recover would still work. It runs in the browser with @solana/kit, talks to any RPC and never calls my backend. I tested it this morning with the backend off.
Fees are placeholders. The 0.25% on the SOL side of completed swaps and the credit prices are early numbers. The program caps the fee at 1%, and raising that cap would take a program upgrade.
Upgrade authority is still my dev wallet. That's the biggest trust gap in pitcrew right now. The Squads multisig with a 48 hour time lock is created, and moving the key there is one command I haven't run yet.
Some of pitcrew's rules can't be enforced on chain and I'd rather say so. The daily loss limit needs prices and liquidity, so it runs in the backend. The landing page marks every rule as program or backend.
Nobody outside the team has used pitcrew yet. There is no volume, no token and no audit. What exists is a vault program on mainnet, a crew that runs, and receipts from one test wallet.
I built pitcrew so a crew could do the research and the watching while the money stays where only my wallet can move it. Today it ran its first full loop on Solana mainnet, with 0.12 SOL.
https://t.co/xBjmHK34Zb
A spending cap is not a loss limit. An authorized budget can still lose money through trades, and pitcrew is software, not advice. The cap means the crew can't spend past what you signed.
Start in watch mode. Connect a wallet, write a strategy and let the crew research without trading. Fund the vault when you want proposals.
https://t.co/d0cjUPkG29
Write the strategy the way you'd say it. For example: watch new Solana coins with usable liquidity, check holders, ask me before buying, 0.1 SOL per entry, at most three positions, sell half at my first target.
One record per coin and one per position. Pip's claims, Vera's objections, Oskar's triggers and Juno's fills land in the same place, so why a trade happened sits next to what it cost.
Our vault program is upgradeable, and the upgrade key is still the developer wallet. A Squads multisig with a 48 hour time lock is created. The transfer hasn't happened yet, and we'll post its signature when it does.
Credits come back when you ask. The test owner put 3 USDC of credits in on 13 Oct and 2.9966 USDC was refunded on chain the same morning.
https://t.co/3fTxcxXBjv
Pricing, for now. Research and monitoring use prepaid USDC credits, refunded if unused. Completed swaps pay 0.25% on the SOL side, failed swaps pay nothing, and the program caps the fee at 1%. Early numbers.
https://t.co/rwMGR0Bh9L
Before mainnet, the vault program passed 19 of 19 checks on a mainnet fork. Overspend, wrong token, tampered route, replayed transaction and withdrawal by a non-owner were all rejected.
Swaps go through Jupiter and the vault checks the route itself: two accepted instructions, pinned accounts, the exact input amount, and the output measured after the swap. Below the signed minimum, it reverts.
Pause new entries, turn off automation, close positions. These three controls are always on screen. Turning off automation is an on-chain revoke, so it holds even when our servers are down.