Contractory
Deploy smart
contracts with
precision.
→ solc 0.8.24 — compiling WoodToken.sol
✓ compiled · 1 file · 1.2s
→ constructor("WoodToken", "WOOD", 1_000_000, 18)
→ estimating gas · 0.00042 ETH
✓ deploy tx 0x7f3a…c21e mined @ block 21,904,118
✓ source verified on explorer
Nº 01 — Deployment console · Arc
Overview
Contractory is a deployment workstation for Arc. It folds the whole lifecycle of a smart contract — compilation, constructor configuration, deployment and verification — into a single, deliberate surface built for teams who ship in production.
The problem
Deployment became a ritual of a dozen tools.
Shipping a contract means stitching together a compiler, a script, a wallet, a block explorer and a verification step — each with its own failure mode. The work that matters gets buried under ceremony, and a single missed constructor argument can cost a redeploy.
The solution
One surface, from source to verified.
Contractory reads constructor inputs straight from the compiled ABI, generates typed defaults, and takes a contract from compilation to a verified address without leaving the page. Deployment reverts are caught before they cost you.
Core features
Typed deployment
Constructor inputs are read from the compiled ABI and rendered as typed fields with sensible defaults — no hand-written scripts.
Verification, built in
Source verification runs as part of deployment, not as an afterthought. Every address lands verified on the explorer.
Revert detection
Failing deploys are detected and surfaced before they consume gas, with the revert reason read back plainly.
Standards, covered
ERC-20, ERC-721 and ERC-1155 out of the box, each with its constructor shape understood.
Lifecycle in one place
Deploy, verify and review recent activity from a single console — no context-switching between tools.
Arc-native
Built for Circle's Arc — USDC-native gas, Chain ID 5042002 — with the network's specifics handled for you.
Technology
Built on a deliberate stack.
Product screens
The console, up close.
→ solc 0.8.24 — compiling WoodToken.sol
✓ compiled · 1 file · 1.2s
→ constructor("WoodToken", "WOOD", 1_000_000, 18)
→ estimating gas · 0.00042 ETH
✓ deploy tx 0x7f3a…c21e mined @ block 21,904,118
✓ source verified on explorer
Deploy — typed constructor, live build log
→ solc 0.8.24 — compiling WoodToken.sol
✓ compiled · 1 file · 1.2s
→ constructor("WoodToken", "WOOD", 1_000_000, 18)
→ estimating gas · 0.00042 ETH
✓ deploy tx 0x7f3a…c21e mined @ block 21,904,118
✓ source verified on explorer
Activity — recent deployments & status
Architecture
Source to verified, in four moves.
Compile
solc compiles the contract; the ABI becomes the source of truth for inputs.
Configure
Constructor fields are generated from the ABI and typed automatically.
Deploy
The transaction is submitted to Arc; reverts are detected before gas is spent.
Verify
Source is verified on the explorer as part of the same flow.
Roadmap
Shipping, then sharpening.
Deployment workstation
Typed deploys, verification and revert detection for ERC-20/721/1155 on Arc.
Contract intelligence
Guided fixes and inline analysis for common contract issues.
Team workspaces
Shared deployment history and roles for production teams.
FAQ
Questions, answered.
Which chain does Contractory target?
Circle's Arc — an EVM L1 with USDC-native gas, Chain ID 5042002. The network's specifics are handled inside the tool.
Which token standards are supported?
ERC-20, ERC-721 and ERC-1155, each with its constructor shape understood and generated from the compiled ABI.
Is Contractory open source?
Yes. The repository ships with a README, MIT licence and contribution guidelines.
How does verification work?
Source verification runs as part of the deployment flow, so contracts land verified on the explorer without a separate step.