melonask/evm-address-skills

Overview

This skill guides generating deterministic EVM deposit addresses offline using the @evm-address/sdk and CLI. It supports both XPUB (BIP-44) for EOAs and CREATE2 factory-based contract addresses, enabling address derivation without exposing private keys. Use it to create repeatable deposit locations for wallets, custodial systems, or batch operations.

How this skill works

The toolkit derives addresses from public inputs only: an extended public key (XPUB) for BIP-44 EOA derivation or a deployed factory contract plus init data for CREATE2 contract addresses. The SDK exposes generator functions (e.g., createXpubGenerator) and the CLI mirrors those capabilities for offline workflows. No private keys are required or transmitted; derived addresses are deterministic and reproducible.

When to use it

• Generating deposit addresses offline for custodial or exchange systems
• Precomputing addresses for batch sweeping and reconciliation
• Creating counterfactual smart-wallet addresses with CREATE2 before deployment
• Offline cold-storage address generation with zero key exposure
• Integrating deterministic address generation into signing or payment workflows

Best practices

• Keep XPUBs and factory init parameters on air-gapped machines when possible
• Verify derived addresses on a separate, connected machine before accepting funds
• Use CREATE2 when you need pay-to-deploy or pre-funded contract wallets
• Record derivation indices and metadata for reconciliation and audits
• Test derivation logic on testnets before production roll-out

Example use cases

• A custodial wallet precomputes 10,000 deposit addresses from a single XPUB and stores indexes in a DB
• A service generates counterfactual contract wallets via CREATE2 so users can receive tokens before deployment
• An operator runs the CLI offline to produce addresses for monthly batch sweeping operations
• An auditor verifies that on-chain deposits map to deterministic addresses derived from a known XPUB