OpenZeppelin / OpenZeppelin/compact-tools
`compact-deployer` roadmap
@0xisk is already working on this.
Since May 24, 2026.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 5
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 31
Description
🧐 Motivation
compact-deployer is a developer-preview tool today. It isn't ready for serious testnet usage (rough retries, no resume, thin observability), and it's nowhere near mainnet-safe (raw seed on disk, no multisig, no hardware signer). Without an explicit roadmap, contributors keep ad-hoc-patching the same blockers we already know about.
Tracking the work as two milestones so we can ship the testnet-ready cut first and use it to inform mainnet hardening.
📝 Details
Milestone 1 — Dev-ready for testnets → #
Reliability, retries, resume, multi-contract orchestration, better dry-run + progress UX. Exit when a sample app deploys + invokes a contract on preview end-to-end in CI.
Milestone 2 — Production-ready for mainnet → #
Hardware-signer, multisig, key-derivation, log redaction, verifiable on-chain bytecode, third-party audit. Exit when one mainnet deploy ships via hardware signer and audit P0/P1 findings are closed.
Out of scope
- IDE plugins / GUI launcher
- Cross-chain deployments
- Contract registry / discovery service
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.