Staking and Dispute Protection

Read StakeVault state, inspect payment-method risk, manage shared stake, and release matured locks.

Product Boundary

Stake to Take backs protected buys with canonical Base USDC at a 1:1 ratio. Venmo and PayPal currently have nonzero risk windows. Cash App remains a supported public payment method, but its current zero window means it does not require stake. Read the live window instead of treating this inventory as permanent.

Access policy and dispute protection are different controls. A payment method can restrict eligible takers without requiring stake.

Read Before Acting

peer stake state <staker> [--taker <address>]
peer stake indexed-state <taker>
peer stake balance <owner>
peer stake locked <owner>
peer stake free <owner>
peer stake claimable <beneficiary>
peer stake admissions-paused
peer stake risk-window --payment-method-hash <hash>
peer stake dispute-protection-enabled --escrow <address> --deposit-id <id> --payment-method <hash>

state is the authoritative contract read. indexed-state adds activity, locks, authorizations, and freshness metadata. Use both when an operator needs current balances plus history.

Stake Writes

peer stake ensure-allowance --amount <usdc>
peer stake deposit --amount <usdc>
peer stake withdraw --amount <usdc>
peer stake claim

Writes preview by default. Add --yes only after reviewing the exact prepared transaction. Free stake withdraws immediately; locked stake cannot be withdrawn until its lock is released.

Shared Stake

Shared stake needs two explicit writes:

The owner runs peer stake authorize --taker <address> --authorized true.
The taker runs peer stake select-owner --owner <address>.

Read the relationship with stake authorization, stake selected-owner, and stake owner. Revoking authorization or running stake clear-owner changes new admissions only. Existing locks keep the owner they opened with.

An upheld dispute on an authorized taker's order can consume the owner's locked stake. Do not authorize an address the owner does not trust.

Matured Locks

The passage of a risk window makes a settled lock eligible for release; it does not execute the release automatically.

peer stake release-matured --intent-hash <bytes32>
peer stake release-matured-batch --intent-hashes '<json-array>'

Use --policy <address> only when pinning a snapshotted DisputeProtectionPolicy deployment. Preview before broadcasting.