Deploy Holder economy
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 foreverHolders burn it to mint, it is one of the two rewards, and the socket pool wraps its pons pool.
- Locked forever
- Locked forever
- ChangeableToken 1 reads <folder>1.json.
- Locked forever
- Changeable
- Changeable0 means no limit.
- Changeable
- Changeable%The rest seeds the stakers' token rewards.
- Changeable%Pons ETH fees and socket trading fees alike. Paid as WETH; the rest goes to your team wallet.
- Changeable%The rest is burned.
- ChangeableGets the ETH not paid to stakers, and the 5% NFT royalty.
- Locked forever%Charged on the ETH a buyer spends in your socket pool. At most 1%.
- Locked forever%Charged on the ETH a seller receives in your socket pool. At most 1%.
Advanced settings (4, sensible defaults filled in)
- ChangeabledaysBetween 0.041666 and 30 days.
- Changeableminutes
- ChangeableOptional: a duration or task weight module. Empty means everyone earns at 1.00x.
- ChangeableOffUsually 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.