Token Generator
HikariTokenFactory is a permissionless ERC-20 deployer. Anyone can launch one of four audited token archetypes by paying the LCAI creation fee — no whitelist, no review queue, no custody.
The factory never holds the new token's supply. It forwards the LCAI fee to HikariFeeCollector, CREATE2-deploys the chosen template, mints the supply directly to the deployer, and emits TokenCreated. Addresses are deterministic and can be computed off-chain.
The four archetypes
Standard
A plain fixed-supply ERC-20. No mint, no burn, no tax, no owner. Auditors should be able to read this contract in 30 seconds — that is the design goal.
Use this when you want a maximally trust-minimized token.
| Parameter | Notes |
|---|---|
name, symbol | ERC-20 standard. |
decimals | 0 – 18 (factory rejects above 18). |
totalSupply | Minted once to the deployer. No further supply changes ever. |
Mintable
Owner-controlled inflation, bounded by an immutable hard cap.
| Parameter | Notes |
|---|---|
initialSupply | Minted at deploy. |
maxSupply | Immutable ceiling — owner-mint reverts above it. |
Ownership uses Ownable2Step: every transfer requires the recipient to call acceptOwnership(), eliminating fat-finger handoffs to an unowned key.
⚠ The owner can dilute holders by minting up to
maxSupply. Always disclose the cap and current circulating supply prominently to anyone trading the token.
Burnable
Holders can burn their own balance via the standard burn(amount) / burnFrom(account, amount) entry points (the latter respects allowances). No mint, no owner, no tax.
Tax
Buy/sell tax routed to a tax recipient.
| Parameter | Notes |
|---|---|
buyTaxBps, sellTaxBps | Basis points (100 bps = 1%). |
| Hard cap | 1,000 bps (10%) per side — immutable. Owner can lower but never raise. |
taxRecipient | Owner-settable; must be non-zero. |
isAmmPair[addr] | Owner-managed flag identifying AMM pair contracts. Transfers from a flagged address charge buy tax; transfers to a flagged address charge sell tax. |
isExcludedFromTax[addr] | Owner-managed exclusions. Defaults exclude the deployer, owner, the contract itself, and the tax recipient so initial liquidity provisioning is not taxed. |
There is no pause and no blacklist in any archetype. By design — those features substantially expand the trust surface and require an additional audit pass before being considered.
⚠ The Tax token owner controls the AMM-pair flag and the tax recipient. Disclose both clearly to anyone trading the token.
Deployment flow
- Pick an archetype on
/generator. - Fill the form. Inline validation enforces the same bounds the contract does.
- Click Deploy — your wallet sends a single transaction with
value = price[archetype]LCAI. - The UI watches for the
TokenCreatedevent and surfaces the new token's address with a copy button and an explorer link.
The factory keeps an append-only allTokens array and an isCreatedHere[token] mapping, so any indexer or UI can prove a token's provenance without trusting our backend.
After deployment
- Add initial liquidity at
/liquidity/addto make your token tradable. - Lock or burn the LP at
/lockfor verifiable on-chain proof of liquidity — useful for community trust on tax-bearing or mintable tokens. - Update the token list by submitting a PR if you want the token discoverable in the swap UI.
Out of scope (intentionally)
- Pausable + Blacklist archetype. Considered and deferred. Adding pause/blacklist to a deployable template is a meaningful audit expansion. Most users distrust those features, and most projects that ship them do so without disclosure.
- Auto-LP memecoin variant. The Tax token routes tax to a recipient — it does not automatically pair-and-add liquidity inside its
_updatehook. Auto-LP introduces re-entrancy and slippage-manipulation surfaces we judge as not worth shipping without a dedicated audit.
If you need either pattern, open an issue or email hikari@hikariswap.com.