A deployed contract is only the skeleton. What the sale page looks like, whether buyers receive tokens automatically or have to claim, and which domain the project site answers on are all set in My IDOs → console.
- Open the consoleGo to IDO → My IDOs. The list holds every round you created. Open one to reach its console; progress, remaining allocation and claim status are on the same screen.
- Fill in the project detailsLogo, banner, project description, social links: the content buyers see on the sale page. Save it when you are done. A round with thin project info gives people no way to judge whether to join.
- Paying in a reward token: bind it and depositBind the reward token in the console, then deposit enough of it into the contract to cover every reward. Deposit too little and buyers have nothing to claim once the round closes — the most common way an IDO goes wrong.
- Turn claiming on when you are readyThe claim switch decides when buyers can take their IDO tokens. If you have a lock-up or staged release planned, this is the control you use to pace it.
- Bind the project site domainWith no domain bound, the project site is a platform subdomain (jkhl.gtokensite.com/chain/contract/template) and works as is. To use your own domain, enter it in the console and add a CNAME at your registrar — the full walkthrough is in Domain & DNS setup.
- Tell buyers how to claimReferral rewards paid in the payment token land immediately. Rewards paid in a reward token have to be claimed on the IDO page — they are not pushed to the wallet. Say that in your community up front.
Tip · The domain binding lives in the backend, not on-chain
There is one frontend for sale pages; a backend record pairing domain with this round’s contract decides which project renders. Once DNS resolves, the client can open the site on their own domain. Swapping the contract does not affect the binding, and the domain can be changed at any time. The console does not check resolution for you — open the domain once to confirm it works.