Squads multisig vault

Checkout builds a system transfer from the buyer to the vault address, plus the order memo. Bond and verification-fee transfers use the same vault. The database ledger records which part of that balance belongs to a creator, a buyer refund, or a fee bucket. The on-chain vault balance is expected to cover the vault ledger.

Signer keys and the approval threshold are configured in Squads. This repository does not store the signer set or a threshold, so a policy such as 2-of-3 is an operational Squads setting rather than a constant in the program or the API.

Release writes payout rows. A batch takes up to 15 pending rows, writes the transfer list to object storage under payout-batches, and marks them proposed. A Squads signer executes the proposal. Posting the signature marks the batch sent. Recipients that are still unconfigured are left out of the batch.

Dbrq2sACPk98FGzLihajJd4r2Q4jdKNn62GSURndv2kw on devnet can hold a deposit inside its own PDA and pay it out with the same split. That program is tested on every pull request. Live orders do not call it. Custody for the running marketplace is the Squads vault.