your creator fees, on a clock, with receipts.
A clock in your own GitHub repo checks your pons fee escrow as often as every fifteen minutes and claims the fees credited to your machine wallet. Each claim is split your way: burns, a treasury, and a board only if you choose one. Every run leaves a hash.
ClockWorks has no key to your walletRead-only, with no wallet to connect. It reads where your fees go, what sits unclaimed in the pons escrow, and what a machine would have done with the last 24 hours of fees.
every claim, split your way.
ClockWorks' leg comes off first, and your split shares the rest the same way on every claim. It lives in one public file in your repo. Three presets sit side by side, and none is chosen for you. Native ETH pairs have no burn until 0.5.0, so their presets give the burn's share to the treasury.
burns
Your token, bought on the pool in slices at the pace you set, then burned. Every slice has a hash. Native ETH pairs have no burn until 0.5.0.
treasury
A wallet you name. The software never sends from it.
board
Off until you choose it. Paid once a day at 00:00 UTC, by balance, to the wallets that hold a seat.
your own wallet
Off until you choose it. Keep half sends half of what is left to a wallet of yours.
10% of claimed fees. 5% above the step.
10% of claimed creator fees, and 5% on the part of a UTC day above a step. No setup fee, no subscription. The machine's service leg pays it on chain, and handback ends it.
the step, by pair.
an example day, worked through.
your wallet, your repo, your key.
ClockWorks has no key to your wallet. The machine runs in your repo, on a public clock, and anyone can read what it did.
the key stays with you.
The machine wallet is yours. Its key is a secret in your own GitHub repo. ClockWorks cannot read it and cannot move a coin.
every hash is public.
Each run commits its receipts to your repo, and a status page reads them for anyone: claims, burns, treasury and board.
handback ends it.
One command claims what is credited to the machine and points your fees at a wallet you name.
from your report to a running clock.
Nothing runs until you point your fees at a machine wallet of your own.
- 01read your fee report.
Paste your token address. See where your fees go, what sits unclaimed, and what a machine would have done with the last 24 hours of fees.
- 02pick a split.
Burn and treasury, board, or keep half. The settings page writes it into one public file in your repo.
- 03claim, then point.
Claim what is already credited in the pons escrow first, because a recipient change does not move it. Then point your fees at the machine wallet, signed from your own wallet.
- 04let the clock run.
Your repo claims, splits and burns on its schedule, and commits every receipt.
Read the setup, step by step, or hand your assistant the ClockWorks skill. Questions go to support.
machines on the chain.
Every machine that has paid the ClockWorks service wallet, read from the chain every hour. Client zero is GMERALD, the house machine, and it pays no service share.
ClockWorks ran first on GMERALD, the house token: … slices so far, and every hash is public at gmerald.xyz.
see your fee report.
Read-only, with no wallet, no key and no sign-up. See what sits unclaimed and what a machine would have done with the last 24 hours of fees, before you decide anything.
Holding a token that paid its holders? The book of payouts reads every payout from the chain.