The payout
engine.

ClipperPayout’s 1,737 executable bytes exactly match canonical Disperse after removing the compiler metadata. Its runtime has no storage reads, storage writes or delegate calls. The contract exposes three public payment functions.

Each account below supplied the tokens for its listed batches. Totals cover ClipperPayout and canonical Disperse and retain their token denomination. The four accounts are a selected investigation scope; the contracts accept other callers too.

These are verified transfers between addresses, with dates and exact receipts in the funding download. Gross flows between upstream wallets describe those edges; they are not assigned in full to downstream recipients.

The Safe currently has three owners and a threshold of two. Historical reads verify the owners and required approvals before every funding transaction. Signature recovery identifies the approving keys even when a separate service submits the transaction.

Filter the 154 reconciled batches by payment account or search a date, amount, token or transaction hash. “Relayed / delegated” means the outer submitter differs from the account funding the contract call.

227 transactions rechecked, 76 selected funding and conversion logs, and 154 encoded batches reconciled. The source bundle records exact token contracts, historical control reads and the distinction between account caller and transaction submitter.