TokenEconomizer
Experience-Driven Black-Box Cost Control for Coding Agents
Use Foundry's Forge, Cast, Anvil, and Chisel tools to build, test, fuzz, debug, deploy, and inspect Ethereum smart contracts.
Developer toolsRust · JavaScriptGitHub @foundry-rsOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Foundry is a blazing fast, portable and modular toolkit for Ethereum application development written in Rust.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Blazing fast, portable and modular toolkit for Ethereum application development, written in Rust.
• Forge — Build, test, fuzz, debug and deploy Solidity contracts.
• Cast — Swiss Army knife for interacting with EVM smart contracts, sending transactions and getting chain data.
• Anvil — Fast local Ethereum development node.
• Chisel — Fast, utilitarian and verbose Solidity REPL.
See the installation guide for more details.
Initialize a new project, build and test:Read the full README ↗
Install | Docs | Benchmarks | Developer Guidelines | Contributing | Crate Docs
Blazing fast, portable and modular toolkit for Ethereum application development, written in Rust.
curl -L https://foundry.paradigm.xyz | bash
foundryup
See the installation guide for more details.
Initialize a new project, build and test:
forge init counter && cd counter
forge build
forge test
Interact with a live network:
cast block-number --rpc-url https://eth.merkle.io
cast balance vitalik.eth --ether --rpc-url https://eth.merkle.io
Fork mainnet locally:
anvil --fork-url https://eth.merkle.io
Read the Foundry Docs to learn more.
With VS Code installed, run forge lsp from your Solidity project's terminal.
Forge opens that project in a VS Code Extension Development Host with its bundled
Solidity extension. No Foundry checkout, extension build, or separate Solar
installation is needed. See the editor guide for setup and
client development.
For other editors, configure the Solidity language server command as
forge lsp --stdio. Bare forge lsp also retains server mode when standard input
is redirected; forge lsp --vscode explicitly opens VS Code. Solar uses
foundry.toml, workspace folders, remappings, and evm_version from the project
automatically.
Solar's default flycheck runs forge lint --json with the same Forge executable
that started the server. Solar's existing initializationOptions.forgePath
option overrides that executable.
forge lsp follows Forge's normal environment setup, global-option parsing, and
command dispatch. In server mode, project dotenv warnings use stderr, leaving
stdout reserved for the LSP transport.
Contributions are welcome and highly appreciated. To get started, check out the contributing guidelines.
Join our Telegram to chat about the development of Foundry.
Having trouble? Check the Foundry Docs, join the support Telegram, or open an issue.