Ship the KitPlate contract on BOT Chain mainnet and open the plate page so makers can open numbered kits and pledgers can pledge and unpledge.
No kit loaded. Open one, or look up a number.
Your pledge on the loaded kit: 0 BOT
Contract pending deploy — the plate is a preview until the kit is live.
A tip jar takes money whether the work happens or not. A plate does not. The maker sets a goal and a date, and the plate only pays out if the pledged total reaches the goal by the deadline. Until then, the money sits in the kit contract, not in anyone's pocket.
The maker cannot collect early and cannot collect a failed kit. If the date passes short of the goal, nothing moves on its own — each pledger calls unpledge and takes back their remaining pledge. There is no protocol cut, no admin drain of another maker's kit, and no token but native BOT.
It goes into the KitPlate contract on BOT Chain mainnet, chainId 677, held against that specific kit. The maker cannot touch it before the deadline, and cannot collect at all if the pledged total stays below the goal.
Call unpledge on the kit. While the kit is open you can take back your remaining pledge at any time; after a failed deadline the same call returns it. Once a kit has been collected, pledges have already paid the maker and unpledge is closed.
Nothing is paid to the maker. The kit does not auto-refund, so each pledger calls unpledge to pull their own remaining pledge back. The maker cannot collect a failed kit.
No. collect is maker-only, only after the deadline, and only when pledged is at least the goal. A short plate stays short and pays nothing to the maker.
The title is 1–80 characters, the goal is in wei and must be above zero, and the deadline must be between 1 hour and 30 days after open. Pledges are native BOT only, and there is no protocol cut.
No. The deployer cannot collect another maker's kit, and there is no owner drain of other kits. A kit's funds move only through the maker's collect or the pledgers' unpledge.
Small shops and solo makers who need the money before the work starts: a print run of enamel plates, a batch of machined parts, a zine, a run of tool rolls. The goal is the number that makes the batch real, and the date is when the decision has to be made.
It also fits people who pledge rather than make: someone who wants a specific kit to exist and is willing to put BOT behind it, knowing they can pull their remaining pledge back if the plate stays short. No charity framing, no gala — just a goal, a date, and a plate that either fills or does not.
Ship the KitPlate contract on BOT Chain mainnet and open the plate page so makers can open numbered kits and pledgers can pledge and unpledge.
Add a plate view that lists open kits with their goal, deadline, and running total, so a pledger can see how short a kit is before adding BOT.
Add a per-address pledge view so each pledger can see what they still hold in each open kit and call unpledge from one screen.
Keep the contract small and the exit clear as the plate fills with more kits, without adding fees or admin rights over other makers' plates.
Open a kit with a BOT goal and a deadline, then let the plate fill or stay short. Pledgers can unpledge their remaining pledge while the kit is open or after a failed deadline, and the maker collects only a filled plate after the date.
Back to the bench