Introduction
zk-pad is a launchpad on BNB Smart Chain (BSC) for donation coins and meme coins. It sends trading fees to a beneficiary whose identity and receiving wallet are not published on-chain.
Live on BSC mainnet
zk-pad is deployed on BNB Smart Chain mainnet (chain 56). The protocol is administered by a single key, not yet a multisig or timelock; see the trust assumptions and the risk disclosure. The official contract addresses are on the addresses page.
The problem
Donation coins and "celebrity" coins usually fail in one of two ways:
- The beneficiary is left out. Anyone can launch a coin named after a person or a cause. The fees go to whoever launched it, and the named person never sees any of it.
- The beneficiary is exposed. When fees do go to the named person, they go to a public wallet. Everyone can see the balance, follow the money and pressure the beneficiary: "sell", "don't sell", "buy back", "promote the coin". The beneficiary is held hostage by the holders.
A beneficiary also usually has to show up on-chain: hold BNB for gas, link a wallet, sign transactions in public. Many people the coin is meant to support never will.
What zk-pad does
| Goal | How zk-pad does it |
|---|---|
| Fees reach the beneficiary automatically and forever | Liquidity is locked permanently in the launch pool. A fee hook routes 75% of every trading fee to the beneficiary's account in the FeeVault. |
| The beneficiary's identity and wallet stay private | The beneficiary is an opaque 32-byte id, never an address. Only the holder of the beneficiary's key can claim: the person the creator gave the claim link to (the claim portal rotates its key before their first action), the beneficiary who gave the creator a payout code (their own key, which the creator never sees), or, for a social-account escrow, the account owner after a bind. |
| Everything else stays auditable | Every fee accrual, every claim and every admin action is a public on-chain event. |
| The beneficiary never needs BNB or a public wallet | Claims are signed off-chain and submitted by relayers, who take their fee from the claimed amount. Funds can go straight into a Railgun private balance. |
| No rug pulls | Fixed 1B supply, no mint, no tax, no blacklist, no owner powers over balances, and liquidity that has no withdraw path. |
How it works at a glance
- A creator launches a coin. It trades on a PancakeSwap Infinity pool from the first second, with no bonding curve and no migration step. See single-sided liquidity.
- The creator chooses a total fee F between 1% and 5%. Every swap pays F. 25% of it goes to the protocol and 75% goes to the beneficiary. PancakeSwap's own fee of about 0.03% is charged on top. See fees.
- The beneficiary's share is credited to an opaque beneficiary id in the
FeeVault. The id is a hash commitment to a secret key (a stealth key) or to a social account. See the privacy model. - The beneficiary claims with an off-chain signature. A relayer submits it and pays the gas. Fees can be consolidated into USDT and shielded into Railgun, so the final destination is a private balance.
Who this documentation is for
- Traders: start with the trader guide and the fee explainer.
- Creators: read the creator guide before you launch, especially the section on choosing a beneficiary type.
- Beneficiaries: if you received a claim link, read the beneficiary guide first. If a coin was launched for your X, GitHub, Telegram, Farcaster or Discord account, read the social escrow guide. Social escrows cannot be claimed yet: no attestors are registered at launch.
- Developers and auditors: the architecture, contract reference and trust assumptions pages.
What zk-pad does not do
- It does not hide trades, holders or fee amounts. Those are public, like any DEX trade.
- It does not hide who a coin is about. A coin's name, ticker and image often announce the beneficiary. zk-pad hides the beneficiary's wallet and, when the creator does not advertise it, the beneficiary's identity. See what is and is not hidden.
- It does not invent new cryptography. Final-destination privacy comes from Railgun, an existing, independently audited privacy system.