prepare_token_launch
Read · No sign-in
Get a link that opens a token launch on chaindaddy.io, filled in
Returns only a chaindaddy.io url that opens the launch form with the token's name, ticker, chain and launch contract filled in, and a summary of it. It creates nothing: nothing is launched, stored, paid for or signed by this call. The person reviews every field on the page and confirms the launch in their own wallet there. venue is chaindaddy-launchpad, the default: Chain Daddy's launchpad, which launches the token with its own locked trading pool, nothing up front and its registration free, on EVM chains and Solana. Or chaindaddy-classic: a plain token from Chain Daddy's factory (no pool, a one-time fee, registration included). Any other venue is refused (400).
A launchpad launch on an EVM chain can keep part of the supply for a team, locked: teamPercent (up to 20), split with other people (teamMember), on one schedule or up to four (teamSchedule). The link fills the form's team row in, and the person checks every wallet and schedule there before confirming; none of it can be changed once the token is created. One the launch would refuse is refused here (400). Solana's team share and schedule are fixed, and a plain token has none at launch, so both refuse these three.
INFO
Not offered to ChatGPT or Codex.
| Reads or changes | Reads only |
| Sign-in | No |
| Calls | GET /api/v2/handoff/launch (API Explorer) |
Input
JSON Schema, as the server serves it.
{
"additionalProperties": false,
"properties": {
"chain": {
"description": "The chain to launch on, as a key (base, ethereum, solana, ...) or chain id; the person can add more on the page",
"maxLength": 64,
"type": "string"
},
"name": {
"description": "The token's name (default the ticker)",
"maxLength": 64,
"type": "string"
},
"symbol": {
"description": "The ticker, up to 16 characters (a leading $ is dropped)",
"maxLength": 17,
"minLength": 1,
"type": "string"
},
"teamMember": {
"description": "People the team's tokens are split with, up to 9, each as `<wallet or handle>:<percent of the team's tokens>`: `0xabc…:30`, `@name:20`, `discord:name:10`. The launching wallet keeps the rest. A handle works once its owner has signed in with that account on Chain Daddy. Needs `teamPercent`.",
"items": {
"maxLength": 120,
"type": "string"
},
"maxItems": 9,
"type": "array"
},
"teamPercent": {
"description": "Percent of supply kept for the team, locked, from 0.01 to 20. Alone, all of it goes to the launching wallet, a part every month for 6 months",
"maximum": 20,
"minimum": 0.01,
"type": "number"
},
"teamSchedule": {
"description": "When the team's tokens unlock, up to 4 schedules. Each is `week:<weeks>` (a part every week, 4 weeks or more), `month:<months>` (a part every 30 days, 2 months or more) or `days:<wait>:<last day>` (nothing for `wait` days, 7 or more, then steadily until the last day, 28 or later). The first keeps the rest of the team's tokens; every other one adds `/share:<percent of the team's tokens>`. A schedule is for everyone, by their split, unless it adds `/for:<people>`, a comma list where 0 is the launching wallet and 1, 2, … are the `teamMember` entries in order. Example: `week:4` and `month:12/share:75/for:1` unlock a quarter every week for 4 weeks for everyone, and the rest every month for 12 months for the first `teamMember`. Needs `teamPercent`.",
"items": {
"maxLength": 80,
"type": "string"
},
"maxItems": 4,
"type": "array"
},
"venue": {
"description": "chaindaddy-launchpad (the default, Chain Daddy's launchpad) or chaindaddy-classic (a plain token from Chain Daddy's factory)",
"enum": [
"chaindaddy-launchpad",
"chaindaddy-classic"
],
"type": "string"
}
},
"required": [
"symbol"
],
"type": "object"
}Example
A tools/call request:
{
"name": "prepare_token_launch",
"arguments": {
"symbol": "value"
}
}