Deploy Hold to earn

Heads up: this pons recipe takes 2 transactions. First you deploy everything in one transaction, then you make your PonsFeeSink your fee recipient on pons.

1. Settings
2. Review
3. Deployed

1. Settings

Locked foreverYour pons tokenHolders burn it to mint, and it is one of the two rewards.
Locked foreverCollection name
Locked foreverCollection symbol
ChangeableMetadata folderToken 1 reads <folder>1.json.
Locked foreverMax supply
ChangeableTokens burned per NFT
ChangeableMints per wallet0 means no limit.
ChangeableMint opens
ChangeableShare of each mint payment burned%The rest seeds the stakers' token rewards.
ChangeableShare of ETH fees for stakers%Paid as WETH. The rest goes to your team wallet.
ChangeableShare of token fees for stakers%The rest is burned.
ChangeableTeam walletGets the ETH not paid to stakers, and the 5% NFT royalty.

Advanced settings (4, sensible defaults filled in)

ChangeableSpread each reward deposit overdaysBetween 0.041666 and 30 days.
ChangeableMinimum stake before claimingminutes
ChangeableMultiplier pluginOptional: a duration or task weight module. Empty means everyone earns at 1.00x.
ChangeableAlso try to sweep pending pool feesOffUsually skipped: pons only lets its operator run sweeps that need a swap.

Opens at launch.

Transaction 2 of 2

Make your PonsFeeSink your fee recipient

Until this is done nothing flows: pons keeps paying fees to your current recipient. Claim any fees already credited to you first. They do not move with the recipient.

The exact call

transferCreatorFeeRecipient(<your token>, <your PonsFeeSink>)

On the pons factory 0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e. Only the current fee recipient can send it, and it takes effect immediately.

Available once the recipe is deployed and your sink address is known.