Foundry v1.7.0 is out!
Highlights: parallelized stateless fuzzing, invariant optimization mode, Osaka default hardfork, Tempo support upstreamed, MPP for 402-gated RPCs, browser wallet support across forge & cast, immutable releases, and more!
$ foundryup --update
$ foundryup
alloy 2.0 very soon, and soon after that we're moving onto foundry 2.0 which will allow foundry to evolve into an SDK not dissimilarly from reth sdk which has enabled everyone in the ecosystem to customize and adapt foundry's internals to secure and improve their dev process
RELEASING RETH 2.0!
Reth is now faster, smaller, and ready for the future of crypto infrastructure.
Gigagas per second has not just been achieved, it's been blown out of the water.
We've put in a ton of work in this, and we're incredibly proud to be sharing this with everyone.
We've added MPP / Tempo Wallet support to Foundry - out on latest nightly.
- foundryup -n tempo
- cast bn -r tempo
- cast send erc20 <...> -r tempo --from `tempo wallet whoami --json-output | jq -r .wallet` (to be made less verbose)
h/t @onbjerg@gndizzy@zerosnacks
hiring to scale security eng at @tempo. come work with @samczsun, @gakonst, and many others smarter than me on:
fuzzing and invariant testing
autonomous bug hunting
continuous security tooling
agentic chaos engineering
it's a weird, exciting time to move fast at the frontier.
mind: blown
claude + foundry fuzzing is very (, very) good, but claude + foundry invariant testing is OP!!!
same invariant as in the QT, but this time discovered via invariant tests - not targeted fuzzing (ofc oneshotted by claude)
instead of trying to guess how the invariant breaks, claude wrote a generic handler that wraps all user-facing, state-changing functions and let the fuzzer do its thing
adding another invariant is trivial, just write the invariant itself - no new repro logic needed
seems like a step-function upgrade in how protocols are tested
huge thanks to the legendary @gndizzy and all the giants building this unbelievable tech
forge-std's v1.14.0 is out, the first release requiring ^0.8.13.
https://t.co/UILvTn5YXi
v1.13.0 is the last release with partial support for 0.6.*, 0.7.* and 0.8.* up to 0.8.13.
https://t.co/IUdFsgnmwF
@baygeeth@CupOJoseph could you please fill a Foundry gh issue with what you'd like to see implemented, would help a lot. Also re 256 runs - it's only a convenience for dev stage, you could bump it at will or even let it run time based if configured with timeout. Thanks
Looking for 3 Rust experts to add to the @tempo team. Once in a career opportunity to build the future of web payments.
Criteria I am looking for (at least 1 of the 3):
- systems/db background
- strong EVM knowledge
- specialisation e.g. compiler / security
Ashby link below.
Foundry has a new release candidate: v1.5.0-rc1!
Highlights include: Solar 🌞 powered AST-seeded fuzzing, improved invariant shrinking, browser wallet support in `cast`, `cast erc20`, distribution of binaries on NPM, and much more!
$ foundryup -i v1.5.0-rc1
Still looking for an incredible compiler engineer that is also a Rust expert that will help us fix Solidity with the Solar project. Cash + equity. Anyone?
You can just run individual foundry tools with one command and not wait for installing what you don't need
s/o @gndizzy for baking this with me on slow fire
As stablecoins grow, so must our devtools.
The easiest thing we could do in Foundry was to add some simple ERC20 convenience utilities.
From an external contributor! Pick any of our open issues and join the club.