zerosnacks.eth

[zerosnacks.eth @zerosnacks]

Foundry v1.7.1 is out!

A patch release on top of v1.7.0 with cherry-picked correctness fixes across cheatcodes, EVM forking, CLI, forge, and cast. Fixes the --version string and includes additional release-pipeline hardening measures.

$ foundryup --update
$ foundryup

[zerosnacks.eth @zerosnacks]

See the full release notes here: https://t.co/zAEs67Kstc

[zerosnacks.eth @zerosnacks]

Foundry v1.7.1 is out!

A patch release on top of v1.7.0 with cherry-picked correctness fixes across cheatcodes, EVM forking, CLI, forge, and cast. Fixes the --version string and includes additional release-pipeline hardening measures.

$ foundryup --update
$ foundryup

[zerosnacks.eth @zerosnacks]

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

[Georgios Konstantopoulos @gakonst]

thankful to @recmo for creating ruint -- over 17M all time downloads, probably one of the most important crates in the eco

to ensure we can co-maintain ruint for the long run, we've moved the repo to the alloy-rs org we started alongside @_prestwich to foster core, stable and performance primitives for the evm ecosystem

big kudos to @DaniPopes for driving the project forward all this time

https://t.co/FBGBOE2lRn

https://t.co/L0HweZrYSe

[Matt Huang @matthuang]

Using this agentic infra at @paradigm and @tempo has been life changing in a way that's hard to describe.

Individuals aren't just individually more productive, they coalesce differently into a new kind of organization.

[zerosnacks.eth @zerosnacks]

@ngotchac Ah yeah, it will be fixed in v1.7.1: https://t.co/VAJxRf3DFE.

Not to worry, even though the version number displayed appears a bit strange this is the correct release.

[zerosnacks.eth @zerosnacks]

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

[zerosnacks.eth @zerosnacks]

Foundry v1.7 adds automatic MPP handling for HTTP 402-gated RPC endpoints. The transport can pay the challenge with your Tempo wallet and continue the call with no code changes: working across cast, forge script, forge test, anvil --fork-url, and chisel --fork-url.

[zerosnacks.eth @zerosnacks]

Tempo support has been upstreamed from tempoxyz/tempo-foundry into foundry-rs/foundry. The standalone fork is deprecated; a normal foundryup install now ships Tempo support across forge, cast, anvil, and chisel.

[zerosnacks.eth @zerosnacks]

@aviggiano @gakonst Thanks for flagging, we’ll prio this

[Georgios Konstantopoulos @gakonst]

We've just open sourced Schelk, a fast filesystem snapshot and rollback tool for database benchmarking.

We use Schelk every day for making our benchmarking loop fast, making our software even faster.

See below how it works. Genius work by @pepyakin.

[jxom @_jxom]

new eips explorer

https://t.co/ICdjE46zRU

[rusowsky @0xrusowsky]

this also comes with a new SignatureVerifier precompile (TIP1020) which let's u use tempo-compatible sigs in smart contracts! like ecrecover, but more powerful

[Tempo @tempo]

Blockchains still broadcast every transaction publicly. Every stablecoin payment leaks the amount, the sender, and the recipient.

We’re excited to share that Tempo is building Zones for businesses that need privacy: private blockchains that are interoperable with the rest of Tempo for stablecoin use cases like payroll, treasury, and settlement.

[zerosnacks.eth @zerosnacks]

@EkomUkanga @gakonst No, development continues as normal. Alloy 2.0 contains a number of breaking changes we have wanted to make for some time that we can’t ship in a minor version

[Georgios Konstantopoulos @gakonst]

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