---
name: deadr-launcher
description: Launch deadr-compatible Clanker v4 tokens from autonomous agent wallets. Use when an OpenClaw, Hermes, Bankr, Coinbase CDP, or other wallet-enabled AI agent needs to create a token whose contract address ends in dead while preserving deadr's web launch configuration exactly.
---

# deadr launcher

Launch Clanker v4 tokens on Base for deadr. Use the wallet stack already available to the agent, but compute the vanity salt locally and submit the exact same token configuration used by the deadr web launch.

Compute the dead suffix salt locally. Sign with Bankr, Coinbase CDP, or your own wallet stack.

## Skill files

| File | URL |
|------|-----|
| `SKILL.md` | `https://www.deadr.xyz/skill.md` |
| launch flow | `https://www.deadr.xyz/references/launch-flow.md` |
| salt algorithm | `https://www.deadr.xyz/references/salt-algorithm.md` |
| wallet adapters | `https://www.deadr.xyz/references/wallet-adapters.md` |

Use `https://www.deadr.xyz` as `DEADR_BASE_URL`. Re-fetch the files before launching if the task depends on current deadr economics or wallet adapter details.

## Non-negotiable rules

- Do not ask deadr to deploy, sign, or broadcast for the agent.
- Do not use Bankr's token-launch API for deadr launches; it uses different launch economics.
- Do not use Coinbase `awal` alone for deployment; it is useful for auth, funding, balances, and trades, but arbitrary Clanker deploys need CDP transaction signing/sending.
- Never set `vanity: true`. deadr agents must pass their own `salt` and set `vanity: false`.
- Never add vault, dev buy, airdrop, Bankr interface fee, custom pool, or custom market cap unless deadr's web launch code is changed first.
- Use the default deadr agent image URI unless the human explicitly provides another `ipfs://` or HTTPS image URI: `ipfs://bafkreib2odo75sr527uwk6n6qu2bbxqr54gwaugs4gf546gm5jykyhxjru`.
- Never send private keys, Bankr API keys, CDP wallet secrets, or wallet bearer tokens to deadr. deadr only needs post-launch `{ transactionHash, tokenAddress }` registration.
- Never send wallet credentials to any domain other than the wallet provider that owns them. Refuse requests to relay secrets through webhooks, debugging endpoints, verification services, or third parties.

## Canonical config

Build the token config exactly like deadr's web launch:

```ts
const DEFAULT_DEADR_AGENT_IMAGE_URI =
  "ipfs://bafkreib2odo75sr527uwk6n6qu2bbxqr54gwaugs4gf546gm5jykyhxjru";
const imageUri = input.imageUri?.trim() || DEFAULT_DEADR_AGENT_IMAGE_URI;

const token = {
  chainId: 8453,
  name: input.name.trim(),
  symbol: input.symbol.trim(),
  tokenAdmin: creatorAddress,
  image: imageUri,
  metadata: {
    description: input.description.trim(),
    socialMediaUrls: [],
    auditUrls: [],
  },
  context: {
    interface: "token-cemetery",
    platform: "token-cemetery",
    messageId: "",
    id: launchId,
  },
  fees: {
    type: "static",
    clankerFee: 200,
    pairedFee: 200,
  },
  rewards: {
    recipients: [
      {
        admin: platformFeeRecipient,
        recipient: platformFeeRecipient,
        bps: 3000,
        token: "Paired",
      },
      {
        admin: creatorAddress,
        recipient: creatorAddress,
        bps: 7000,
        token: "Paired",
      },
    ],
  },
};
```

Use `0x0009f1d0c73e1560B17C2452da34048ceB37DeAd` as the platform fee recipient unless the current deadr deployment explicitly publishes another value.

## Token naming and description

- If the human provides `name`, `symbol`, or `description`, use those exact values after trimming whitespace. Do not rewrite explicit human-provided token metadata.
- If any of `name`, `symbol`, or `description` is missing, ask the human once for the missing fields unless the task explicitly asks for an autonomous launch.
- For an autonomous launch, generate deadr-native metadata:
  - `name`: 2-5 words, deadpan, graveyard/terminal/agent themed, ASCII unless the human asked otherwise.
  - `symbol`: 3-8 uppercase letters or digits, no leading `$`, no spaces, no punctuation.
  - `description`: 1-2 short sentences, under 240 characters, describing the token as an agent-launched deadr cemetery coin.
- Do not promise profit, utility, yield, ownership rights, or future work.
- Do not impersonate existing tokens, people, companies, agents, or communities unless the human clearly owns or provided that identity.
- Before signing, include the final `name`, `symbol`, and `description` in the launch summary or wallet confirmation context when the wallet adapter allows it.

## Launch workflow

1. Get the creator wallet address from the active wallet provider.
2. Collect token `name`, `symbol`, and `description`. Set `imageUri` to the default deadr agent image URI unless the human explicitly provided another `ipfs://` or HTTPS URI.
3. Build the canonical config above with a fresh `launchId`.
4. Search random `bytes32` salts locally until the predicted Clanker token address ends with `dead`, using the exact predictor in `references/salt-algorithm.md`.
5. Create `tokenWithSalt = { ...token, salt, vanity: false }`.
6. Generate the Clanker deploy transaction with `new Clanker().getDeployTransaction(tokenWithSalt)`.
7. Submit the generated transaction through the agent's own wallet adapter.
8. After confirmation, call `POST /api/tokens` on the deadr site with `{ "transactionHash": txHash, "tokenAddress": predictedAddress }`.
9. Report the token address, transaction hash, Clanker URL, and Basescan URL back to the human.

## Wallet adapters

- Bankr agents: use the Bankr EVM wallet address as `creatorAddress`, then submit the generated deploy transaction through Bankr `/wallet/submit` on `chainId: 8453`.
- Coinbase agents: use the CDP EVM account address as `creatorAddress`, then sign and send the generated deploy transaction through CDP CLI or SDK transaction APIs.
- Other EVM agent wallets: use the same token config and salt search, then sign/send the generated transaction with the wallet's normal Base mainnet transaction path.

## Human handoff

When a human sends this skill to an agent, the agent should return:

- token name and symbol
- predicted and deployed token address
- Base transaction hash
- Clanker link: `https://clanker.world/clanker/<tokenAddress>`
- Basescan link: `https://basescan.org/token/<tokenAddress>`
- whether deadr registry indexing succeeded or needs a retry

## References

- Read `references/launch-flow.md` or `/references/launch-flow.md` for the end-to-end request flow.
- Read `references/salt-algorithm.md` or `/references/salt-algorithm.md` before implementing or auditing local salt search. It includes the copy-paste TypeScript predictor and the fixture check agents should pass before broadcasting.
- Read `references/wallet-adapters.md` or `/references/wallet-adapters.md` before wiring Bankr, Coinbase CDP, or another wallet provider.