deployer

Deploy Continuous Clearing Auction smart contracts via the factory pattern using Foundry.

1|Updated Sep 4, 2025
One-click install
npx skills add https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO --skill deployer-fuzzystodd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployer
Source: https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO/tree/main/skills/deployer
Command: npx skills add https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO --skill deployer-fuzzystodd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a Continuous Clearing Auction (CCA) contract requires correctly encoding complex auction parameters, validating block schedules and pricing, and safely handling private keys. This Skill guides you through the entire CCA deployment workflow with built-in validation and security guardrails. ## Core Features & Use Cases - Guided Factory Deployment: Walks through deploying CCA instances via the ContinuousClearingAuctionFactory using CREATE2 for consistent cross-chain addresses. - Configuration Validation: Enforces rules on block sequences, floor price alignment, tick spacing, supply schedules, and address formats before any transaction is broadcast. - Private Key Safety: Blocks insecure practices like --private-key flags and recommends hardware wallets or encrypted keystores via cast. - Use Case: A token team wants to launch a fair token sale on Base. The Skill validates their JSON configuration, generates the forge script deployment commands, and reminds them to call onTokensReceived() after deployment. ## Quick Start Ask the assistant to deploy a CCA auction with your configuration file, for example: deploy my auction using the config in auction-config.json on Sepolia testnet.

Frequently Asked Questions about deployer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Continuous Clearing Auction contract?▼

Deploy a CCA instance by calling initializeDistribution on the ContinuousClearingAuctionFactory with your token address, amount, ABI-encoded AuctionParameters, and a salt. You must approve the token transfer to the factory first, then call onTokensReceived() on the deployed auction.

What is the CCA factory address for deployment?▼

The recommended factory is version v1.1.0 at address 0xCCccCcCAE7503Cac057829BF2811De42E16e0bD5. It uses CREATE2, so the same address works across all supported chains.

Which chains support CCA deployment?▼

CCA is deployed to canonical addresses on Mainnet (chain ID 1), Unichain (130), Unichain Sepolia (1301), Base (8453), Arbitrum (42161), and Sepolia (11155111). Block times range from 1 second on Unichain to 12 seconds on Mainnet.

How do I securely manage private keys for contract deployment?▼

Use a Ledger or Trezor hardware wallet with the --ledger flag, or import keys into an encrypted keystore with cast wallet import. Never use the --private-key flag, paste keys on the command line, or commit keys to git repositories.

Why does my CCA configuration fail validation?▼

Common failures include invalid block sequences (startBlock must be less than endBlock which must be at most claimBlock), floor prices not aligned to tick spacing multiples, tick spacing below 1% of floor price, or total supply exceeding 1e30 wei. Fee-on-transfer tokens and tokens with fewer than 6 decimals are also unsupported.

Can I deploy a CCA auction without the factory?▼

Yes, you can deploy directly via the constructor by passing the token address, amount, and AuctionParameters struct. However, this approach does not benefit from CREATE2 deterministic addressing that the factory provides across chains.