Deploy the escrow
After locking configuration, deploy a campaign escrow through the factory. Review the factory destination and the locked configuration commitment in the transaction dialog.
Each campaign has its own escrow. The factory registers the creator and campaign key against the deployed escrow address.
Approve and fund
Select Approve & fund reward pool.
Confirm the required approval transactions individually.
Prepare funding again after the approvals are confirmed.
Confirm the funding transaction and wait for recognized escrow state.
| Asset | Approval |
|---|---|
| ERC-20 | Approve the required amount to the campaign escrow. A token may require resetting an existing allowance first. |
| ERC-721 | Approve each configured NFT token ID to the escrow. |
| ERC-1155 | Authorize collection access for the campaign escrow, then deposit the configured edition quantity. |
Activate the campaign
Activate only after the escrow recognizes the complete required funding. Share the campaign page once activation has been indexed. Participation follows the scheduled start and cutoff.
A transaction hash is a tracking reference. The application confirms campaign funding and activation from verified escrow events, rather than accepting a submitted hash as proof.
Cancellation and unclaimed rewards
The escrow enforces when cancellation is allowed. Cancelling does not provide a way to rewrite a finalized distribution.
After the claim deadline, use the refund action to return remaining assets to the configured refund recipient. Token restrictions, transfers, and NFT receivers can affect whether an asset transfer succeeds.