Multi-chain IDO launchpad and growth platform with KYC-gated token sales (DAO Pad), Strong Holder Offerings (SHOs), and tier-based allocation via DAO token staking. Smart contracts (vesting, SHO deposit, staking) are open-source under github.com/daomaker; allocation eligibility runs off-chain through KYC + tier weighting, then on-chain claim/vesting.
- 01KYC-gated retail IDOs and SHOs
- 02tier-weighted allocation flows (DAO token stake = tier)
- 03vested token claims post-TGE
- 04multi-chain (EVM) launchpad participation
- 05fundraising for early-stage projects with retail distribution
- pnpm add viem ethers
| Variable | Scope | Description |
|---|---|---|
| EVM_RPC_URL | Server | Ethereum / BNB Chain / Polygon RPC depending on which DAO Maker deployment your IDO uses. |
| DAOMAKER_VESTING_ADDRESS | Client | Per-IDO vesting contract address from `daomaker/tokens-vesting-contract`. Published on the project's DAO Maker page at TGE. |
| DAOMAKER_API_KEY | Server | Optional — partner API key for DAO Maker's KYC/allocation backend. Required only for projects integrating IDO flows server-side. |
DAO Maker does not publish a first-party JS SDK; integrate directly against its open-source contracts. For SHO participation, call `deposit(uint256 amount)` on the project's `sho-deposit-contract` during the deposit window after the user has been allocated and KYC-passed off-chain. For TGE claims, point at the project-specific deployment of `tokens-vesting-contract` and call `claim()` (or `claim(scheduleId)` on multi-tranche schedules) — the contract enforces cliff + linear vesting on-chain. For DAO-token tier staking, use `dao-staking` (venture-yield contract) with `stake(amount, lockId)` to earn a tier multiplier. Allocation amounts and KYC status are read from DAO Maker's partner API, not from chain.
- ⚑KYC is mandatory for token sales — DAO Maker geofences and verifies via off-chain partners; users from restricted jurisdictions (US, sanctioned countries, etc.) cannot participate even if they reach the contract.
- ⚑Tier multipliers and per-tier allocation caps live off-chain in DAO Maker's backend — your on-chain `deposit` will revert if the user is not whitelisted, which looks identical to a generic revert; surface the KYC/tier status from the API before submitting.
- ⚑Vesting contract addresses are per-IDO and not deterministic — never hard-code; pull the address from the project's IDO config or DAO Maker's API to avoid sending claims to the wrong contract.
- ⚑SHO `refund` window is short (typically days); if you miss the refund deadline, locked deposit converts to vested allocation that may be illiquid for months.
- ⚑Cross-chain post-listing: DAO Maker IDOs frequently launch on BNB Chain or Ethereum but list on multiple DEXs across chains via project-side bridging; LP and price discovery often differ per chain at TGE.
- ⚑Rug-pull/scam IDO filtering is the platform's responsibility but not a guarantee — surface the project's audit, team doxx, and prior DAO Maker track record before letting users commit.
- ⚑Pricing of the DAO token itself is volatile; tier eligibility based on `staked DAO` USD value can drop a user out of a tier mid-sale if price moves — re-validate tier on each step.