For the complete documentation index, see llms.txt. This page is also available as Markdown.

Deploy a PumpCorp for ACE

ACE (Asset Conversion to Equity) lets a token community convert into equity. It is powered by the PumpCorpFactory (src/PumpCorpFactory.sol) and an ACE-configured SAFE extension. The live product is ace.metalex.tech.

When to use this guide

You are an issuer running an ACE-style offering: a structured, typically Regulation S offering open to non-US persons, where investors arrive holding tokens and leave holding ACE SAFEs.

Approach

PumpCorpFactory builds on the same primitives as CyberCorpFactory: it deploys a cyberCORP suite configured for an ACE offering and creates the round. Its main entry points are deployCyberCorp (suite only), deployCyberCorpAndCreateOffer, and deployCyberCorpAndCreateRoundFor, which deploys the suite and creates the round in one transaction — validating that the round's party values match the officer and verifying the officer's escrowed EIP-712 signature over the round parameters. The flow then mirrors a standard cyberRAISE round:

  1. Deploy the PumpCorp through PumpCorpFactory, supplying the offering parameters (pricing, cap, the agreement template, and a non-US / zkPassport ICondition for Regulation S gating).

  2. Investors submit EOIs and are allocated, exactly as in Run a cyberRAISE round.

  3. On allocation, each investor receives an ACE SAFE cyberCERT (its security series is SecuritySeries.ACE).

The deploy* parameter lists are long and not reproduced here — consult the contract source and the deploy scripts (script/deploy-pump-factory.s.sol, script/deploy-pump-factory-full-lifecycle.s.sol), which are the authoritative reference for the current ACE deployment shape.

Last updated

Was this helpful?