Solidity Patterns on Bitsy Services Wiki

Clones with Immutable Args

Mon, 01 Jan 0001 00:00:00 +0000

Overview#

Minimal proxies (EIP-1167 clones) are the cheapest way to deploy many instances of the same contract. Each clone delegates every call to a shared implementation contract, so you only pay for ~45 bytes of creation code instead of re-deploying the full bytecode.

The limitation is that clones share the implementation’s storage layout, so each instance still needs its own initialiser call to set instance-specific state — and that initialiser writes to storage, which is expensive.

Foundry

Mon, 01 Jan 0001 00:00:00 +0000

Foundry is a fast Solidity development toolkit written in Rust. It includes forge (build, test, deploy), cast (CLI for interacting with contracts), anvil (local testnet node), and chisel (Solidity REPL).

Foundry Book — official documentation
GitHub repository
forge-std — standard library for tests and scripts
Foundry Broadcast — how startBroadcast/stopBroadcast works in deploy scripts

Foundry Broadcast

Mon, 01 Jan 0001 00:00:00 +0000

Foundry scripts use vm.startBroadcast() and vm.stopBroadcast() to mark which parts of a Solidity script should produce real on-chain transactions. A common misconception is that everything between the two calls executes as a single atomic transaction. It does not — each state-changing statement becomes its own transaction.

How broadcast works#

A broadcast block looks like this:

vm.startBroadcast(deployerPrivateKey);

MyToken token = new MyToken();          // tx 1: deploy
token.initialize(owner, supply);        // tx 2: external call

vm.stopBroadcast();

Foundry processes this in two phases: