Skip to content

Master#526

Merged
Dargon789 merged 46 commits into
mainfrom
master
May 7, 2026
Merged

Master#526
Dargon789 merged 46 commits into
mainfrom
master

Conversation

@Dargon789
Copy link
Copy Markdown
Owner

Motivation

Solution

PR Checklist

  • Added Tests
  • Added Documentation
  • Breaking changes

dependabot Bot and others added 30 commits April 22, 2026 10:39
Bumps [strum](https://github.com/Peternator7/strum) from 0.27.2 to 0.28.0.
- [Release notes](https://github.com/Peternator7/strum/releases)
- [Changelog](https://github.com/Peternator7/strum/blob/master/CHANGELOG.md)
- [Commits](Peternator7/strum@v0.27.2...v0.28.0)

---
updated-dependencies:
- dependency-name: strum
  dependency-version: 0.28.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
…) (#498)

* chore(deps): bump rui314/setup-mold from 725a8794d15fc7563f59595bd9556495c0564878 to 9c9c13bf4c3f1adef0cc596abc155580bcb04444 (foundry-rs#14442)

chore(deps): bump rui314/setup-mold

Bumps [rui314/setup-mold](https://github.com/rui314/setup-mold) from 725a8794d15fc7563f59595bd9556495c0564878 to 9c9c13bf4c3f1adef0cc596abc155580bcb04444.
- [Commits](rui314/setup-mold@725a879...9c9c13b)

---
updated-dependencies:
- dependency-name: rui314/setup-mold
  dependency-version: 9c9c13bf4c3f1adef0cc596abc155580bcb04444
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update flake.lock (foundry-rs#14458)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

* fix(forge): adjust gas assertion `CounterWithFallback` (foundry-rs#14465)

* chore: update latest benchmarks (foundry-rs#14467)

* ci: split MPP e2e into its own workflow (foundry-rs#14468)

* ci: split MPP e2e into its own workflow

Move the MPP e2e step from ci-tempo.yml into a standalone ci-mpp.yml
workflow so transient HTTP 402 failures from the MPP RPC do not block
the Tempo CI workflow.

Amp-Thread-ID: https://ampcode.com/threads/T-019dceb8-61e5-734f-b047-17665b4ea7d3
Co-authored-by: Amp <amp@ampcode.com>

* ci: rename sanity-check job to tempo-check

Amp-Thread-ID: https://ampcode.com/threads/T-019dceb8-61e5-734f-b047-17665b4ea7d3
Co-authored-by: Amp <amp@ampcode.com>

* ci: rename mpp-e2e job to mpp-check

Amp-Thread-ID: https://ampcode.com/threads/T-019dceb8-61e5-734f-b047-17665b4ea7d3
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>

* Improve GH actions (foundry-rs#14473)

* fix(benches): add repos + extra args support to prevent blocking errors (foundry-rs#14470)

* fix(benches): add repos + extra args support to prevent blocking errors

* fix(ci): set `inputs.repos` default to empty

* fix: remove `--verbose` flags

* fix: exclude `uniswap/v4-core` `TickMathTestTest`

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Bumps [strum](https://github.com/Peternator7/strum) from 0.27.2 to 0.28.0.
- [Release notes](https://github.com/Peternator7/strum/releases)
- [Changelog](https://github.com/Peternator7/strum/blob/master/CHANGELOG.md)
- [Commits](Peternator7/strum@v0.27.2...v0.28.0)

---
updated-dependencies:
- dependency-name: strum
  dependency-version: 0.28.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Bumps [similar-asserts](https://github.com/mitsuhiko/similar-asserts) from 1.7.0 to 2.0.0.
- [Changelog](https://github.com/mitsuhiko/similar-asserts/blob/main/CHANGELOG.md)
- [Commits](mitsuhiko/similar-asserts@1.7.0...2.0.0)

---
updated-dependencies:
- dependency-name: similar-asserts
  dependency-version: 2.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* anvil: unify Tempo nonce markers across send RPCs (foundry-rs#14536)

Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: steven <corderosteven6@gmail.com>
Co-authored-by: stevencartavia <112043913+stevencartavia@users.noreply.github.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>

* fix(forge): `flaky_gas_report_fallback_with_calldata` deployment cost (foundry-rs#14545)

* chore(lint): add missing lints to README (foundry-rs#14551)

* chore(bench): update `benchmark.sh` (foundry-rs#14548)

Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>

* chore(clippy): fix for_kv_map and useless_borrows_in_formatting (foundry-rs#14554)

* chore(clippy): fix for_kv_map and useless_borrows_in_formatting

Amp-Thread-ID: https://ampcode.com/threads/T-019df0f9-62e7-74b8-bd5e-da2acce678fb
Co-authored-by: Amp <amp@ampcode.com>

* chore(clippy): drop redundant borrows in cheatcodes assert formatters

Amp-Thread-ID: https://ampcode.com/threads/T-019df0f9-62e7-74b8-bd5e-da2acce678fb
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>

* fix(ci): use `PATH_USD` fallback fee token in Mail templates (foundry-rs#14546)

* chore(deps): bump the actions-weekly group with 3 updates (foundry-rs#14497)

* refactor(chisel): migrate to solar (foundry-rs#14532)

* feat(lint): add too-many-digits lint (foundry-rs#14549)

* feat: feature-gate optimism deps in common-fmt, common, cast (foundry-rs#14539)

* feat(forge): support per-test network selection via inline config (foundry-rs#14530)

* feat(cli): `--tempo.expires` retry-safe mode (TIP-1009 expiring nonces) (foundry-rs#14521)

* fix(forge): `per_test_network_routing` match undeterministic order (foundry-rs#14557)

output

* chore(ci): run tempo mainnet and testnet checks before devnet (foundry-rs#14556)

* Update flake.lock (foundry-rs#14553)

flake.lock: Update

Flake lock file updates:

• Updated input 'fenix':
    'github:nix-community/fenix/f374034' (2026-04-25)
  → 'github:nix-community/fenix/74c1591' (2026-05-02)
• Updated input 'fenix/rust-analyzer-src':
    'github:rust-lang/rust-analyzer/8954b66' (2026-04-21)
  → 'github:rust-lang/rust-analyzer/64cdaeb' (2026-05-01)
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/01fbdee' (2026-04-23)
  → 'github:NixOS/nixpkgs/c6d6588' (2026-05-01)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

* chore(bench): update benchmark results (foundry-rs#14552)

* fix(forge): ignore ETH_RPC_URL for test forking (foundry-rs#14555)

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* feat(cast): add Tempo keychain policy commands (foundry-rs#14531)

* feat(cast): add tempo keychain policy commands

* fix(cast): address keychain policy review

* fix(cli): fix jsonwebtoken panic (foundry-rs#14562)

`cast` panicked with this message coming from jsonwebtoken:

```
Call CryptoProvider::install_default() before this point to select a provider manually, or make sure exactly one of the
'rust_crypto' and 'aws_lc_rs' features is enabled.
See the documentation of the CryptoProvider type for more information.
```

This seemingly was introduced with the bump of jsonwebtoken to 10. Now
it requires you to pick one backend used by default controlled by the
compile time cargo features or call `CryptoProvider::install_default()`
at the beginning.

I realized that probably it would be better to just select the feature
and I picked `aws_lc_rs` as it seems to be increasingly a default and
we already are using the C toolchain.

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* chore(cli): tidy ETH_RPC_URL handling and add forge regression test (foundry-rs#14559)

Follow-up to foundry-rs#14555:

- Drop the redundant flashbots branch in RpcOpts::dict; self.url(None)
  already returns FLASHBOTS_URL when --flashbots is set, so the
  subsequent overwrite was dead code.
- Inline the resolve_rpc_url helper back into RpcCommonOpts::url; it
  was only called from one place and added unneeded surface area.
- Restore the doc comment on RpcCommonOpts and document why
  ETH_RPC_URL is intentionally not a clap env on the shared field
  (so EvmArgs cannot inherit it).
- Add an integration test that runs forge config with ETH_RPC_URL set
  in the environment and asserts that eth_rpc_url stays None,
  directly exercising the regression scenario from foundry-rs#14538.

Amp-Thread-ID: https://ampcode.com/threads/T-019df243-267f-7779-93e1-5d6686082444

Co-authored-by: zerosnacks <zerosnacks@protonmail.com>
Co-authored-by: Amp <amp@ampcode.com>

* feat(cast): open Tempo wallet fund flow for MPP failures (foundry-rs#14505)

* feat(cast): open Tempo wallet fund flow for MPP failures

* ci(tempo): skip network checks without rpc secrets

* Revert "ci(tempo): skip network checks without rpc secrets"

This reverts commit f8dd701.

* fix(common): address mpp funding review

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* ci: sign release archives, docker images, and publish SBOMs (foundry-rs#14563)

- release.yml: emit per-archive sha256 + SPDX SBOM (Syft), cosign
  keyless sign-blob of the archive, and use actions/attest@v4 for both
  build provenance and SBOM attestations. Upload all artifacts to the
  draft release.
- docker-publish.yml: enable BuildKit SBOM, capture the build digest,
  cosign keyless sign each pushed tag, and publish a Sigstore-signed
  SLSA provenance attestation via actions/attest with push-to-registry.
- SECURITY.md: document how external users verify archives and the
  docker image (gh attestation, cosign, plain sha256, buildx imagetools).
- README.md: link to the new verification section.

* perf(common): short-circuit `find_by_name_or_identifier` instead of `collect` (foundry-rs#14514)

* feat(foundryup): retry GitHub API fetches on transient errors (foundry-rs#14566)

GitHub api.github.com occasionally returns transient 403s on certain VMs
(per-IP rate limiting / WAF hiccups), causing foundryup to fail to
resolve the latest stable / nightly release tag, e.g.:

  foundryup: fetching latest nightly releases from foundry-rs/foundry...
  Error: curl: (56) The requested URL returned error: 403
  foundryup: failed to fetch releases from GitHub API

Add curl/wget retry logic to the `fetch` helper (used exclusively for
GitHub API releases endpoints):

- curl: --retry 5 --retry-delay 2 --retry-max-time 60, plus
  --retry-all-errors when supported (curl 7.71+, feature-detected so
  older curl does not hard-fail). --retry-all-errors is required to
  retry HTTP 403, which is not in curl's default retryable set.
- wget fallback: --tries=5 --waitretry=2
  --retry-on-http-error=403,408,429,5xx.

`fetch` now buffers to a temp file before emitting to stdout, since
curl's --retry-all-errors is unsafe with piped consumers (mid-stream
retries can duplicate bytes). Existing callers pipe into awk/grep.

Tunable via FOUNDRYUP_MAX_RETRIES (default 5).

`download` (binary tarballs, attestations, manpages) is intentionally
left unchanged — those rarely fail and changing them affects the
attestation existence check semantics.

Bumps installer version 1.8.1 -> 1.8.2.


Amp-Thread-ID: https://ampcode.com/threads/T-019df2f5-9b97-717a-b959-cf7cbc7ca3bb

Co-authored-by: Amp <amp@ampcode.com>

* feat(lint): project-wide passes + pragma-inconsistent (foundry-rs#14543)

* feat(lint): project-wide passes + pragma-inconsistent

* rm hashset, msg

* test(lint): exhaustive pragma-inconsistent coverage + clearer testdata names (foundry-rs#14561)

* test(lint): exhaustive coverage for pragma-inconsistent

Follow-up to foundry-rs#14543 expanding test coverage for the cross-file
`pragma-inconsistent` lint across the syntax variants users encounter
in real Solidity projects.

Multi-file scenarios (added as `forgetest!` cases in
`crates/forge/tests/cli/lint.rs`, since they cannot be expressed in a
single `.sol` testdata file):

- Negative (must NOT warn):
  - all files use the same exact pragma (`0.8.20`)
  - all files use the same caret pragma (`^0.8.20`)
  - single file in the project
- Positive (must warn):
  - duplicates among a conflict -- two identical files plus one
    different pragma still emits three warnings
- Mixed:
  - file without an explicit pragma uses the test-utils default
    (`add_raw_source` is used to bypass the auto-injected pragma)

Source bodies are pulled out into module-level `const` raw strings so
rustfmt does not collapse the inline `\n`-escaped strings into wide
horizontal blobs.

Single-file scenarios (added as `.sol` files under
`crates/lint/testdata/` in the existing `//~NOTE:` annotation style):

- `PragmaInconsistentCaretVsTilde.sol`: `^0.8.20` vs `~0.8.20`
- `PragmaInconsistentRangeVsExact.sol`: `>=0.8.0 <0.9.0` vs `0.8.20`
  -- range satisfies exact but lint is intentionally string-based,
  matching SLITHER-W1078
- `PragmaInconsistentOrVsExact.sol`: `0.8.20 || 0.8.21` vs `0.8.20`
- `PragmaInconsistentThreeDistinct.sol`: `>=0.8.0`, `^0.8.0`, `~0.8.0`
  -- verifies the `others` list contains every other variant

* test(lint): rename pragma-inconsistent testdata to describe the case under test

The two testdata files added in foundry-rs#14543 were named `PragmaInconsistent.sol`
and `PragmaInconsistent2.sol`, which made them look like duplicates. They
actually exercise distinct edge cases of the same string-based detection:

- `PragmaInconsistentCaretAboveExact.sol` (was `PragmaInconsistent.sol`):
  caret range whose lower bound is strictly below the exact version
  (`^0.8.0` + `0.8.18`).
- `PragmaInconsistentCaretMatchesExact.sol` (was `PragmaInconsistent2.sol`):
  caret range whose lower bound equals the exact version
  (`^0.8.20` + `0.8.20`) -- the looks-the-same-but-still-distinct case
  that guards SLITHER-W1078 parity (no semver intersection).

Amp-Thread-ID: https://ampcode.com/threads/T-019df243-267f-7779-93e1-5d6686082444
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>

* refactor(script): reuse shared Tempo CLI opts (foundry-rs#14558)

* deps: bump tempo to 6bf9903 (T6 hardfork) + fix alloy-evm 0.34 compat (foundry-rs#14567)

* deps: bump tempo to 6bf9903 (T6 hardfork)

Bumps tempo crates to 6bf9903d, adding the T6 hardfork variant to
TempoHardfork. Without this, cast's tempo_forkSchedule lookup parses
the chain's reported active fork ("T6") into TempoHardfork::FromStr,
fails because T6 was unknown to the enum, and silently returns
is_hardfork_active(T3) = false. That made 'cast keychain auth' fall
back to the legacy authorizeKey selector and revert with
LegacyAuthorizeKeySelectorChanged on any T6 chain.

Also bumps alloy-evm to 0.34 and the optimism git pin to develop
(e3b59e7) so alloy-op-evm picks up an EvmFactory impl built against
alloy-evm 0.34. Removes the now-unused paradigmxyz/reth-core [patch]
entries.

No source changes; lockfile churn is transitive only.

* fix: adapt AnvilBlockExecutor to alloy-evm 0.34.0 breaking changes

- Add Send + 'static bounds to TxResult impl for AnvilTxResult<H>
- Change commit_transaction return type from Result<GasOutput, BlockExecutionError> to GasOutput
- Remove .expect() on commit_transaction call site

Amp-Thread-ID: https://ampcode.com/threads/T-019df322-c0f1-73e7-858c-5ca2d242ddb4

* style: rustfmt commit_transaction signature

Amp-Thread-ID: https://ampcode.com/threads/T-019df322-c0f1-73e7-858c-5ca2d242ddb4

---------

Co-authored-by: Centaur AI <ai@centaur.local>

* docs: add forge lint rule docs (foundry-rs#14571)

* feat(forge): add fuzz run selection (foundry-rs#14522)

* feat(forge): add fuzz run selection

* fix(fuzz): make metadata builder const

* test(fuzz): cover generated seed replay

* fix(forge): persist fuzz worker for run replay

* fix(evm): satisfy clippy in fuzz replay

* fix(fuzz): reuse fuzz run metadata

* forge(lint/docs): validate deployed forge lint docs (foundry-rs#14573)

test: validate deployed forge lint docs

* feat: gate foundry-primitives behind optimism feature (foundry-rs#14572)

* fix(ci): increase permissions for the enhanced attestation writing (foundry-rs#14584)

* increase permissions for artifact writing

* apply write permissions to release-docker

* feat(hardforks, networks): gate optimism behind cargo feature (foundry-rs#14581)

* fix(forge): encode Tempo creates as AA calls (foundry-rs#14585)

* feat(anvil): gate optimism behind cargo feature (foundry-rs#14577)

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* feat(cast): introduce `vaddr` cmd for TIP-1022 (foundry-rs#14508)

* feat(cast): introduce `vaddr` cmd for tip-1022

* fix: doc

* chore: touch-ups

* add tests

* chore: move tests to tempo ci

* feat: add vaddr watch test

* feat: count 0 hadling, add `no_register` flag

* fix: remove sweep subcommand

* fix: make clippy happy

* feat(bench): nightly regression tracking workflow (foundry-rs#14586)

* fix(cli): fix release version strings for immutable tags, bump to 1.7.1 (foundry-rs#14496)

* Fix release version metadata for immutable tags

Amp-Thread-ID: https://ampcode.com/threads/T-019dd617-b29f-7409-8523-9858a1504f17
Co-authored-by: Amp <amp@ampcode.com>

* Derive nightly release suffix from commit SHA

Amp-Thread-ID: https://ampcode.com/threads/T-019dd617-b29f-7409-8523-9858a1504f17
Co-authored-by: Amp <amp@ampcode.com>

* Apply suggestion from @zerosnacks

* Apply suggestion from @zerosnacks

* Apply suggestion from @zerosnacks

* bump to v1.7.1

* avoid appending whole sha hash, not necessary, handle version cmp correctly. after v1.7.1 release we need to bump to v1.7.2 for nightlies following it to compare correctly

* Make foundryVersionCmp tolerate new version format and add tests

- Strip both pre-release ('-nightly', '-dev') and build metadata ('+<sha>.<ts>.<profile>') from SEMVER_VERSION before comparison so the cheatcode keeps working for tagged releases (which have no '-' separator).
- Extract strip_semver_metadata helper and add Rust unit tests covering all SEMVER_VERSION shapes, version_cmp ordering, and parse_version rejection of pre-release/build/garbage input.
- Extend the Solidity test suite for vm.getFoundryVersion()/foundryVersionCmp/foundryVersionAtLeast: validate MAJOR.MINOR.PATCH parseability, build profile value, cmp/atLeast invariant, and error paths for invalid user-supplied versions.

Amp-Thread-ID: https://ampcode.com/threads/T-019dd971-fcb7-7149-9680-f0134130844c
Co-authored-by: Amp <amp@ampcode.com>

* fix(test): drop view from solidity tests using assert helpers and fix fmt

- assertTrue/assertEq aren't view, so testGetFoundryVersionBuildProfile and testFoundryVersionCmpAndAtLeastAreConsistent can't be view either.
- Collapse the buildType assertion onto one line to satisfy forge fmt.

Amp-Thread-ID: https://ampcode.com/threads/T-019dd971-fcb7-7149-9680-f0134130844c
Co-authored-by: Amp <amp@ampcode.com>

* test(version): assert build profile is non-empty instead of debug|release

The dist profile (used for distributed release binaries) is also valid; just require non-empty so any future profile works.

Amp-Thread-ID: https://ampcode.com/threads/T-019dd971-fcb7-7149-9680-f0134130844c
Co-authored-by: Amp <amp@ampcode.com>

* Normalize nightly-<sha> to nightly in release_version

Ensures tarball and Docker nightly artifacts produce the same version
string. The commit identifier is already included in the SemVer build
metadata (after `+`), so collapsing `nightly-<sha>` to `nightly`
avoids duplicating the SHA in the pre-release tag.

Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019df79e-d4c9-707c-85eb-2efbf59160b3

---------

Co-authored-by: Centaur AI <ai@centaur.local>
Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: zerosnacks <zerosnacks@protonmail.com>

* fix(evm): query `state_snapshot.storage` in `ForkDbStateSnapshot::storage_ref` (foundry-rs#14007)

* fix(evm): query `state_snapshot.storage` in `ForkDbStateSnapshot::storage_ref`

* test(evm): cover `ForkDbStateSnapshot::storage_ref` snapshot lookup

* fix(cast): consistent `--json` output for `keychain` subcommands (foundry-rs#14590)

- `keychain rl`: wrap remaining limit in `{"remaining":"..."}` object
  instead of emitting a bare JSON string
- `keychain policy add-call`: emit
  `{"status":"already_present","target":"..."}`
  when the rule already exists, instead of plain text
- `send_keychain_tx`: wrap sponsor hash in `{"sponsor_hash":"0x..."}`
  object when --tempo.print-sponsor-hash is used with --json

Add CLI tests covering the rl and sponsor-hash JSON output shapes.

* feat(tempo): add sponsored transaction plumbing (foundry-rs#14560)

* feat(tempo): add sponsored transaction plumbing

* addressing mablr comments

* fix tempo sponsor signer future layout

* preserve json output for tempo sponsor preview

* fix(cast): `--json` output support for `vaddr` (foundry-rs#14591)

* feat(tempo): add named nonce lanes (foundry-rs#14527)

* fix(cheatcodes): transfer value for payable mock calls (foundry-rs#14547)

* test: updated tests

* fix: execute value transfer

* test: improve

* imp: review item

* test: vm.prank test

* imp: moved mocked-call handling after prank application

---------

Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* feat(lint): add inline-assembly lint (foundry-rs#14575)

* feat(lint): add inline-assembly lint

* lint(inline-assembly): also recognize `/// @solidity memory-safe-assembly` NatSpec

Amp-Thread-ID: https://ampcode.com/threads/T-019df4b6-1b76-734c-9a9b-29db9fb7d461
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>

* refactor(script): remove `ScriptConfig::{fee_token,expires_at}` in favour of `TempoOpts` (foundry-rs#14594)

* feat(evm-core): gate optimism behind cargo feature (foundry-rs#14593)

* fix(cli): resolve Tempo expires once (foundry-rs#14595)

fix(cli): resolve tempo expires once

* feat(cli): gate optimism behind cargo feature (foundry-rs#14596)

* fix(anvil): classify EVM halts as transaction rejections (foundry-rs#14592)

Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* feat: drop optimism deps under no-default-features (foundry-rs#14600)

* fix(forge): `--fuzz-seed` parameter is not effective in `forge coverage` (foundry-rs#14610)

fix --fuzz-seed not effective in forge coverage

* fix(foundryup): mirror tag resolution for install & use (foundry-rs#14611)

* fix(foundryup): mirror tag resolution for install & use

* fix(foundryup): mirror semver version normalization in `use`

`install` auto-prepends `v` to bare semver versions (e.g. `1.7.0` ->
`v1.7.0`) so the on-disk directory is always `v`-prefixed. `use` was
doing a literal lookup, so `foundryup -u 1.7.0` failed even though
`foundryup -i 1.7.0` had succeeded.

Broaden the channel `case` in `use()` to also match bare semver inputs
(`MAJOR.MINOR.PATCH[-prerelease]`) so they go through the same
`resolve_version_and_tag` normalizer. The pattern is intentionally
tighter than `install`'s `[[:digit:]]*` so locally-built versions whose
names happen to start with a digit are still looked up literally.

Amp-Thread-ID: https://ampcode.com/threads/T-019dfc78-8557-712b-9944-bbff9a4a3b76
Co-authored-by: Amp <amp@ampcode.com>

* chore(foundryup): clarify tag-resolution log and error messages

Distinguish the GitHub API tag-resolution phase from the actual binary
download by consistently referring to "release tag(s)" in the
`resolve_version_and_tag` helper's `say` and `err` messages.

Amp-Thread-ID: https://ampcode.com/threads/T-019dfc78-8557-712b-9944-bbff9a4a3b76
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>

* fix(ci): keep no-default builds free of op deps (foundry-rs#14612)

* feat: cast unauthorized flow → wallet.tempo access-key authorization (foundry-rs#14517)

* feat: cast unauthorized flow → wallet.tempo access-key authorization

Amp-Thread-ID: https://ampcode.com/threads/T-019df174-9538-713b-b8c9-5001b1ad4719
Co-authored-by: Amp <amp@ampcode.com>

* fmt

* feat(cast): replace TEMPO_NO_BROWSER env with  flag

* revert token addresses

---------

Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* docs(expect-emit): clarify next-call semantics and warn about caught-revert leak (foundry-rs#14620)

docs(cheatcodes): clarify expectEmit next-call semantics and caught-revert leak

expectEmit is a 'next call' assertion. If the call immediately after expectEmit
reverts and the revert is swallowed by the caller (low-level call or try/catch),
the unmatched expectation can leak forward and be satisfied by a later unrelated
emission, silently turning a broken test green.

Document the constraint on the natspec for both no-arg and topic-checking
overloads, and regenerate cheatcodes.json.

Refs: foundry-rs#14618

Amp-Thread-ID: https://ampcode.com/threads/T-019dfd96-7a03-7249-8c10-af20ee2729f5

Co-authored-by: Amp <amp@ampcode.com>

* fix(cheatcodes): enforce `expectRevert` reverter address for CREATE frames (foundry-rs#14615)

* fix(cheatcodes): enforce `expectRevert` reverter address for CREATE
frames

The reverter address argument to `vm.expectRevert` was silently ignored
when the innermost reverting frame was a CREATE (top-level or nested),
because create_end never populated `expected_revert.reverted_by`.

Mirror call_end's logic in create_end: when the outcome reverts and a
reverter address is expected, record outcome.address (revm guarantees
this is Some(would-be address) whenever the constructor executed).

Adds positive regression tests for top-level and nested-CREATE reverts,
and a negative regression test asserting wrong-reverter now fails.

Co-authored-by: Amp <amp@ampcode.com>

* improve coverage

* add Derek's suggested test cases

* fix: forge fmt for ExpectRevert.t.sol

Amp-Thread-ID: https://ampcode.com/threads/T-019dfdc5-5414-70b6-9f49-cb5797a37a29
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* fix(script): keep plain Tempo broadcasts non-AA (foundry-rs#14616)

* fix(script): don't force Tempo AA fee_token from --network tempo alone

Plain --network tempo (or any selection that just sets the network to
Tempo) does not by itself imply a Tempo AA / type 0x76 transaction.
Defaulting tempo.common.fee_token to PATH_USD_ADDRESS solely from
evm_opts.networks.is_tempo() caused every unsigned broadcast tx to flow
through TempoOpts::apply, which set fee_token on the request and
promoted it to the Tempo AA tx envelope. Signers that only know how to
sign ordinary Ethereum transactions (e.g. the Ledger Ethereum app)
then rejected the transaction with 'received an unexpected empty
response'.

Gate the default on an actual Tempo AA opt-in:

  - --batch (Tempo batch txs are themselves AA and need a fee token), or
  - any explicit --tempo.* flag (sponsor, expiring nonce, nonce key/lane,
    ...) which already forces an AA tx and benefits from a default fee
    token.

Explicit --tempo.fee-token continues to win over the default in all
cases, and non-Tempo networks never default the fee token.

Add unit tests for each scenario.

Amp-Thread-ID: https://ampcode.com/threads/T-019dfd37-2354-712f-95b1-2584fd47ad5e
Co-authored-by: Amp <amp@ampcode.com>

* fix(script): don't force eth_estimateGas on plain Tempo broadcasts

Plain --network tempo produces an ordinary EIP-1559/legacy transaction
(see tempo-alloy::TempoTransactionRequest::output_tx_type), so the local
simulation gas estimate is sufficient. Forcing RPC re-estimation in this
case can surface node-side errors such as 'gas required exceeds
allowance (0)' (Geth-style balance/gasPrice cap from eth_estimateGas)
on flows that previously worked, including Ledger-signed broadcasts
that just got unblocked from the type 0x76 regression.

Match tempo-foundry's behaviour: only force eth_estimateGas on Tempo
when the user has actually opted into Tempo AA semantics (--batch or
any explicit --tempo.* flag).

Extract the gating into needs_tempo_aa_rpc_estimate(...) and add
focused unit tests mirroring the fee-token gating tests.

Amp-Thread-ID: https://ampcode.com/threads/T-019dfd37-2354-712f-95b1-2584fd47ad5e
Co-authored-by: Amp <amp@ampcode.com>

* fix(script): don't re-estimate plain Tempo chain broadcasts

---------

Co-authored-by: Amp <amp@ampcode.com>

* fix(cheatcodes): preserve reverts with `expectEmit` (foundry-rs#14619)

* test: added regression test

* fix: re-order revert handling

* refactor: simplify

* lint: fmt

* polish: tighten comment, extend test with revert reason and custom error

Amp-Thread-ID: https://ampcode.com/threads/T-019dfd96-7a03-7249-8c10-af20ee2729f5
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>

* feat(lint): add tx-origin detector (foundry-rs#14589)

* feat(lint): add tx-origin detector

* test(lint): address tx-origin review feedback

* fix: ui bless

* fix(lint): cover tx-origin index and ternary predicates

* test(lint): bless tx-origin snapshot

---------

Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* refactor(tempo): prepare batch access key txs w/ helper (foundry-rs#14597)

fix(tempo): prepare batch access key txs before estimation

* fix(anvil): respect non-zero genesis block in Otterscan APIs  (foundry-rs#14490)

fix(anvil): respect non-zero genesis block in Otterscan APIs

The three Otterscan address-history endpoints (`ots_searchTransactionsBefore`/`After`, `ots_getTransactionBySenderAndNonce`) hardcoded `unwrap_or(1)` / `unwrap_or_default()` as the lower bound of their block scan, which breaks when `genesis_block_number` is non-zero (e.g. `genesis.json` `number: 73`). Expose `Backend::genesis_number()` and fall back to `genesis_number() + 1` in non-fork mode, mirroring the existing post-fork `f.block_number() + 1` convention.

---------

Co-authored-by: Isagi Yates <isagiyates@gmail.com>
Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: steven <corderosteven6@gmail.com>
Co-authored-by: stevencartavia <112043913+stevencartavia@users.noreply.github.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: figtracer <me@figtracer.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Sergei Shulepov <s.pepyakin@gmail.com>
Co-authored-by: zerosnacks <zerosnacks@protonmail.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: cui <cuiweixie@gmail.com>
Co-authored-by: Centaur AI <ai@centaur.local>
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: Nikki <gutonosa@protonmail.com>
Co-authored-by: srdtrk <59252793+srdtrk@users.noreply.github.com>
Co-authored-by: Mikhail Mikheev <16622558+mmv08@users.noreply.github.com>
Co-authored-by: lazymio <mio@lazym.io>
Co-authored-by: Emma Jamieson-Hoare <emmajam@users.noreply.github.com>
Co-authored-by: VIkions <99107287+vikions@users.noreply.github.com>
Co-authored-by: Aïssata <mikeslowcoder@proton.me>
* anvil: unify Tempo nonce markers across send RPCs (foundry-rs#14536)

Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: steven <corderosteven6@gmail.com>
Co-authored-by: stevencartavia <112043913+stevencartavia@users.noreply.github.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>

* fix(forge): `flaky_gas_report_fallback_with_calldata` deployment cost (foundry-rs#14545)

* chore(lint): add missing lints to README (foundry-rs#14551)

* chore(bench): update `benchmark.sh` (foundry-rs#14548)

Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>

* chore(clippy): fix for_kv_map and useless_borrows_in_formatting (foundry-rs#14554)

* chore(clippy): fix for_kv_map and useless_borrows_in_formatting

Amp-Thread-ID: https://ampcode.com/threads/T-019df0f9-62e7-74b8-bd5e-da2acce678fb
Co-authored-by: Amp <amp@ampcode.com>

* chore(clippy): drop redundant borrows in cheatcodes assert formatters

Amp-Thread-ID: https://ampcode.com/threads/T-019df0f9-62e7-74b8-bd5e-da2acce678fb
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>

* fix(ci): use `PATH_USD` fallback fee token in Mail templates (foundry-rs#14546)

* chore(deps): bump the actions-weekly group with 3 updates (foundry-rs#14497)

* refactor(chisel): migrate to solar (foundry-rs#14532)

* feat(lint): add too-many-digits lint (foundry-rs#14549)

* feat: feature-gate optimism deps in common-fmt, common, cast (foundry-rs#14539)

* feat(forge): support per-test network selection via inline config (foundry-rs#14530)

* feat(cli): `--tempo.expires` retry-safe mode (TIP-1009 expiring nonces) (foundry-rs#14521)

* fix(forge): `per_test_network_routing` match undeterministic order (foundry-rs#14557)

output

* chore(ci): run tempo mainnet and testnet checks before devnet (foundry-rs#14556)

* Update flake.lock (foundry-rs#14553)

flake.lock: Update

Flake lock file updates:

• Updated input 'fenix':
    'github:nix-community/fenix/f374034' (2026-04-25)
  → 'github:nix-community/fenix/74c1591' (2026-05-02)
• Updated input 'fenix/rust-analyzer-src':
    'github:rust-lang/rust-analyzer/8954b66' (2026-04-21)
  → 'github:rust-lang/rust-analyzer/64cdaeb' (2026-05-01)
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/01fbdee' (2026-04-23)
  → 'github:NixOS/nixpkgs/c6d6588' (2026-05-01)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

* chore(bench): update benchmark results (foundry-rs#14552)

* fix(forge): ignore ETH_RPC_URL for test forking (foundry-rs#14555)

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* feat(cast): add Tempo keychain policy commands (foundry-rs#14531)

* feat(cast): add tempo keychain policy commands

* fix(cast): address keychain policy review

* fix(cli): fix jsonwebtoken panic (foundry-rs#14562)

`cast` panicked with this message coming from jsonwebtoken:

```
Call CryptoProvider::install_default() before this point to select a provider manually, or make sure exactly one of the
'rust_crypto' and 'aws_lc_rs' features is enabled.
See the documentation of the CryptoProvider type for more information.
```

This seemingly was introduced with the bump of jsonwebtoken to 10. Now
it requires you to pick one backend used by default controlled by the
compile time cargo features or call `CryptoProvider::install_default()`
at the beginning.

I realized that probably it would be better to just select the feature
and I picked `aws_lc_rs` as it seems to be increasingly a default and
we already are using the C toolchain.

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* chore(cli): tidy ETH_RPC_URL handling and add forge regression test (foundry-rs#14559)

Follow-up to foundry-rs#14555:

- Drop the redundant flashbots branch in RpcOpts::dict; self.url(None)
  already returns FLASHBOTS_URL when --flashbots is set, so the
  subsequent overwrite was dead code.
- Inline the resolve_rpc_url helper back into RpcCommonOpts::url; it
  was only called from one place and added unneeded surface area.
- Restore the doc comment on RpcCommonOpts and document why
  ETH_RPC_URL is intentionally not a clap env on the shared field
  (so EvmArgs cannot inherit it).
- Add an integration test that runs forge config with ETH_RPC_URL set
  in the environment and asserts that eth_rpc_url stays None,
  directly exercising the regression scenario from foundry-rs#14538.

Amp-Thread-ID: https://ampcode.com/threads/T-019df243-267f-7779-93e1-5d6686082444

Co-authored-by: zerosnacks <zerosnacks@protonmail.com>
Co-authored-by: Amp <amp@ampcode.com>

* feat(cast): open Tempo wallet fund flow for MPP failures (foundry-rs#14505)

* feat(cast): open Tempo wallet fund flow for MPP failures

* ci(tempo): skip network checks without rpc secrets

* Revert "ci(tempo): skip network checks without rpc secrets"

This reverts commit f8dd701.

* fix(common): address mpp funding review

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* ci: sign release archives, docker images, and publish SBOMs (foundry-rs#14563)

- release.yml: emit per-archive sha256 + SPDX SBOM (Syft), cosign
  keyless sign-blob of the archive, and use actions/attest@v4 for both
  build provenance and SBOM attestations. Upload all artifacts to the
  draft release.
- docker-publish.yml: enable BuildKit SBOM, capture the build digest,
  cosign keyless sign each pushed tag, and publish a Sigstore-signed
  SLSA provenance attestation via actions/attest with push-to-registry.
- SECURITY.md: document how external users verify archives and the
  docker image (gh attestation, cosign, plain sha256, buildx imagetools).
- README.md: link to the new verification section.

* perf(common): short-circuit `find_by_name_or_identifier` instead of `collect` (foundry-rs#14514)

* feat(foundryup): retry GitHub API fetches on transient errors (foundry-rs#14566)

GitHub api.github.com occasionally returns transient 403s on certain VMs
(per-IP rate limiting / WAF hiccups), causing foundryup to fail to
resolve the latest stable / nightly release tag, e.g.:

  foundryup: fetching latest nightly releases from foundry-rs/foundry...
  Error: curl: (56) The requested URL returned error: 403
  foundryup: failed to fetch releases from GitHub API

Add curl/wget retry logic to the `fetch` helper (used exclusively for
GitHub API releases endpoints):

- curl: --retry 5 --retry-delay 2 --retry-max-time 60, plus
  --retry-all-errors when supported (curl 7.71+, feature-detected so
  older curl does not hard-fail). --retry-all-errors is required to
  retry HTTP 403, which is not in curl's default retryable set.
- wget fallback: --tries=5 --waitretry=2
  --retry-on-http-error=403,408,429,5xx.

`fetch` now buffers to a temp file before emitting to stdout, since
curl's --retry-all-errors is unsafe with piped consumers (mid-stream
retries can duplicate bytes). Existing callers pipe into awk/grep.

Tunable via FOUNDRYUP_MAX_RETRIES (default 5).

`download` (binary tarballs, attestations, manpages) is intentionally
left unchanged — those rarely fail and changing them affects the
attestation existence check semantics.

Bumps installer version 1.8.1 -> 1.8.2.


Amp-Thread-ID: https://ampcode.com/threads/T-019df2f5-9b97-717a-b959-cf7cbc7ca3bb

Co-authored-by: Amp <amp@ampcode.com>

* feat(lint): project-wide passes + pragma-inconsistent (foundry-rs#14543)

* feat(lint): project-wide passes + pragma-inconsistent

* rm hashset, msg

* test(lint): exhaustive pragma-inconsistent coverage + clearer testdata names (foundry-rs#14561)

* test(lint): exhaustive coverage for pragma-inconsistent

Follow-up to foundry-rs#14543 expanding test coverage for the cross-file
`pragma-inconsistent` lint across the syntax variants users encounter
in real Solidity projects.

Multi-file scenarios (added as `forgetest!` cases in
`crates/forge/tests/cli/lint.rs`, since they cannot be expressed in a
single `.sol` testdata file):

- Negative (must NOT warn):
  - all files use the same exact pragma (`0.8.20`)
  - all files use the same caret pragma (`^0.8.20`)
  - single file in the project
- Positive (must warn):
  - duplicates among a conflict -- two identical files plus one
    different pragma still emits three warnings
- Mixed:
  - file without an explicit pragma uses the test-utils default
    (`add_raw_source` is used to bypass the auto-injected pragma)

Source bodies are pulled out into module-level `const` raw strings so
rustfmt does not collapse the inline `\n`-escaped strings into wide
horizontal blobs.

Single-file scenarios (added as `.sol` files under
`crates/lint/testdata/` in the existing `//~NOTE:` annotation style):

- `PragmaInconsistentCaretVsTilde.sol`: `^0.8.20` vs `~0.8.20`
- `PragmaInconsistentRangeVsExact.sol`: `>=0.8.0 <0.9.0` vs `0.8.20`
  -- range satisfies exact but lint is intentionally string-based,
  matching SLITHER-W1078
- `PragmaInconsistentOrVsExact.sol`: `0.8.20 || 0.8.21` vs `0.8.20`
- `PragmaInconsistentThreeDistinct.sol`: `>=0.8.0`, `^0.8.0`, `~0.8.0`
  -- verifies the `others` list contains every other variant

* test(lint): rename pragma-inconsistent testdata to describe the case under test

The two testdata files added in foundry-rs#14543 were named `PragmaInconsistent.sol`
and `PragmaInconsistent2.sol`, which made them look like duplicates. They
actually exercise distinct edge cases of the same string-based detection:

- `PragmaInconsistentCaretAboveExact.sol` (was `PragmaInconsistent.sol`):
  caret range whose lower bound is strictly below the exact version
  (`^0.8.0` + `0.8.18`).
- `PragmaInconsistentCaretMatchesExact.sol` (was `PragmaInconsistent2.sol`):
  caret range whose lower bound equals the exact version
  (`^0.8.20` + `0.8.20`) -- the looks-the-same-but-still-distinct case
  that guards SLITHER-W1078 parity (no semver intersection).

Amp-Thread-ID: https://ampcode.com/threads/T-019df243-267f-7779-93e1-5d6686082444
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>

* refactor(script): reuse shared Tempo CLI opts (foundry-rs#14558)

* deps: bump tempo to 6bf9903 (T6 hardfork) + fix alloy-evm 0.34 compat (foundry-rs#14567)

* deps: bump tempo to 6bf9903 (T6 hardfork)

Bumps tempo crates to 6bf9903d, adding the T6 hardfork variant to
TempoHardfork. Without this, cast's tempo_forkSchedule lookup parses
the chain's reported active fork ("T6") into TempoHardfork::FromStr,
fails because T6 was unknown to the enum, and silently returns
is_hardfork_active(T3) = false. That made 'cast keychain auth' fall
back to the legacy authorizeKey selector and revert with
LegacyAuthorizeKeySelectorChanged on any T6 chain.

Also bumps alloy-evm to 0.34 and the optimism git pin to develop
(e3b59e7) so alloy-op-evm picks up an EvmFactory impl built against
alloy-evm 0.34. Removes the now-unused paradigmxyz/reth-core [patch]
entries.

No source changes; lockfile churn is transitive only.

* fix: adapt AnvilBlockExecutor to alloy-evm 0.34.0 breaking changes

- Add Send + 'static bounds to TxResult impl for AnvilTxResult<H>
- Change commit_transaction return type from Result<GasOutput, BlockExecutionError> to GasOutput
- Remove .expect() on commit_transaction call site

Amp-Thread-ID: https://ampcode.com/threads/T-019df322-c0f1-73e7-858c-5ca2d242ddb4

* style: rustfmt commit_transaction signature

Amp-Thread-ID: https://ampcode.com/threads/T-019df322-c0f1-73e7-858c-5ca2d242ddb4

---------

Co-authored-by: Centaur AI <ai@centaur.local>

* docs: add forge lint rule docs (foundry-rs#14571)

* feat(forge): add fuzz run selection (foundry-rs#14522)

* feat(forge): add fuzz run selection

* fix(fuzz): make metadata builder const

* test(fuzz): cover generated seed replay

* fix(forge): persist fuzz worker for run replay

* fix(evm): satisfy clippy in fuzz replay

* fix(fuzz): reuse fuzz run metadata

* forge(lint/docs): validate deployed forge lint docs (foundry-rs#14573)

test: validate deployed forge lint docs

* feat: gate foundry-primitives behind optimism feature (foundry-rs#14572)

* fix(ci): increase permissions for the enhanced attestation writing (foundry-rs#14584)

* increase permissions for artifact writing

* apply write permissions to release-docker

* feat(hardforks, networks): gate optimism behind cargo feature (foundry-rs#14581)

* fix(forge): encode Tempo creates as AA calls (foundry-rs#14585)

* feat(anvil): gate optimism behind cargo feature (foundry-rs#14577)

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* feat(cast): introduce `vaddr` cmd for TIP-1022 (foundry-rs#14508)

* feat(cast): introduce `vaddr` cmd for tip-1022

* fix: doc

* chore: touch-ups

* add tests

* chore: move tests to tempo ci

* feat: add vaddr watch test

* feat: count 0 hadling, add `no_register` flag

* fix: remove sweep subcommand

* fix: make clippy happy

* feat(bench): nightly regression tracking workflow (foundry-rs#14586)

* fix(cli): fix release version strings for immutable tags, bump to 1.7.1 (foundry-rs#14496)

* Fix release version metadata for immutable tags

Amp-Thread-ID: https://ampcode.com/threads/T-019dd617-b29f-7409-8523-9858a1504f17
Co-authored-by: Amp <amp@ampcode.com>

* Derive nightly release suffix from commit SHA

Amp-Thread-ID: https://ampcode.com/threads/T-019dd617-b29f-7409-8523-9858a1504f17
Co-authored-by: Amp <amp@ampcode.com>

* Apply suggestion from @zerosnacks

* Apply suggestion from @zerosnacks

* Apply suggestion from @zerosnacks

* bump to v1.7.1

* avoid appending whole sha hash, not necessary, handle version cmp correctly. after v1.7.1 release we need to bump to v1.7.2 for nightlies following it to compare correctly

* Make foundryVersionCmp tolerate new version format and add tests

- Strip both pre-release ('-nightly', '-dev') and build metadata ('+<sha>.<ts>.<profile>') from SEMVER_VERSION before comparison so the cheatcode keeps working for tagged releases (which have no '-' separator).
- Extract strip_semver_metadata helper and add Rust unit tests covering all SEMVER_VERSION shapes, version_cmp ordering, and parse_version rejection of pre-release/build/garbage input.
- Extend the Solidity test suite for vm.getFoundryVersion()/foundryVersionCmp/foundryVersionAtLeast: validate MAJOR.MINOR.PATCH parseability, build profile value, cmp/atLeast invariant, and error paths for invalid user-supplied versions.

Amp-Thread-ID: https://ampcode.com/threads/T-019dd971-fcb7-7149-9680-f0134130844c
Co-authored-by: Amp <amp@ampcode.com>

* fix(test): drop view from solidity tests using assert helpers and fix fmt

- assertTrue/assertEq aren't view, so testGetFoundryVersionBuildProfile and testFoundryVersionCmpAndAtLeastAreConsistent can't be view either.
- Collapse the buildType assertion onto one line to satisfy forge fmt.

Amp-Thread-ID: https://ampcode.com/threads/T-019dd971-fcb7-7149-9680-f0134130844c
Co-authored-by: Amp <amp@ampcode.com>

* test(version): assert build profile is non-empty instead of debug|release

The dist profile (used for distributed release binaries) is also valid; just require non-empty so any future profile works.

Amp-Thread-ID: https://ampcode.com/threads/T-019dd971-fcb7-7149-9680-f0134130844c
Co-authored-by: Amp <amp@ampcode.com>

* Normalize nightly-<sha> to nightly in release_version

Ensures tarball and Docker nightly artifacts produce the same version
string. The commit identifier is already included in the SemVer build
metadata (after `+`), so collapsing `nightly-<sha>` to `nightly`
avoids duplicating the SHA in the pre-release tag.

Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019df79e-d4c9-707c-85eb-2efbf59160b3

---------

Co-authored-by: Centaur AI <ai@centaur.local>
Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: zerosnacks <zerosnacks@protonmail.com>

* fix(evm): query `state_snapshot.storage` in `ForkDbStateSnapshot::storage_ref` (foundry-rs#14007)

* fix(evm): query `state_snapshot.storage` in `ForkDbStateSnapshot::storage_ref`

* test(evm): cover `ForkDbStateSnapshot::storage_ref` snapshot lookup

* fix(cast): consistent `--json` output for `keychain` subcommands (foundry-rs#14590)

- `keychain rl`: wrap remaining limit in `{"remaining":"..."}` object
  instead of emitting a bare JSON string
- `keychain policy add-call`: emit
  `{"status":"already_present","target":"..."}`
  when the rule already exists, instead of plain text
- `send_keychain_tx`: wrap sponsor hash in `{"sponsor_hash":"0x..."}`
  object when --tempo.print-sponsor-hash is used with --json

Add CLI tests covering the rl and sponsor-hash JSON output shapes.

* feat(tempo): add sponsored transaction plumbing (foundry-rs#14560)

* feat(tempo): add sponsored transaction plumbing

* addressing mablr comments

* fix tempo sponsor signer future layout

* preserve json output for tempo sponsor preview

* fix(cast): `--json` output support for `vaddr` (foundry-rs#14591)

* feat(tempo): add named nonce lanes (foundry-rs#14527)

* fix(cheatcodes): transfer value for payable mock calls (foundry-rs#14547)

* test: updated tests

* fix: execute value transfer

* test: improve

* imp: review item

* test: vm.prank test

* imp: moved mocked-call handling after prank application

---------

Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* feat(lint): add inline-assembly lint (foundry-rs#14575)

* feat(lint): add inline-assembly lint

* lint(inline-assembly): also recognize `/// @solidity memory-safe-assembly` NatSpec

Amp-Thread-ID: https://ampcode.com/threads/T-019df4b6-1b76-734c-9a9b-29db9fb7d461
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>

* refactor(script): remove `ScriptConfig::{fee_token,expires_at}` in favour of `TempoOpts` (foundry-rs#14594)

* feat(evm-core): gate optimism behind cargo feature (foundry-rs#14593)

* fix(cli): resolve Tempo expires once (foundry-rs#14595)

fix(cli): resolve tempo expires once

* feat(cli): gate optimism behind cargo feature (foundry-rs#14596)

* fix(anvil): classify EVM halts as transaction rejections (foundry-rs#14592)

Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* feat: drop optimism deps under no-default-features (foundry-rs#14600)

* fix(forge): `--fuzz-seed` parameter is not effective in `forge coverage` (foundry-rs#14610)

fix --fuzz-seed not effective in forge coverage

* fix(foundryup): mirror tag resolution for install & use (foundry-rs#14611)

* fix(foundryup): mirror tag resolution for install & use

* fix(foundryup): mirror semver version normalization in `use`

`install` auto-prepends `v` to bare semver versions (e.g. `1.7.0` ->
`v1.7.0`) so the on-disk directory is always `v`-prefixed. `use` was
doing a literal lookup, so `foundryup -u 1.7.0` failed even though
`foundryup -i 1.7.0` had succeeded.

Broaden the channel `case` in `use()` to also match bare semver inputs
(`MAJOR.MINOR.PATCH[-prerelease]`) so they go through the same
`resolve_version_and_tag` normalizer. The pattern is intentionally
tighter than `install`'s `[[:digit:]]*` so locally-built versions whose
names happen to start with a digit are still looked up literally.

Amp-Thread-ID: https://ampcode.com/threads/T-019dfc78-8557-712b-9944-bbff9a4a3b76
Co-authored-by: Amp <amp@ampcode.com>

* chore(foundryup): clarify tag-resolution log and error messages

Distinguish the GitHub API tag-resolution phase from the actual binary
download by consistently referring to "release tag(s)" in the
`resolve_version_and_tag` helper's `say` and `err` messages.

Amp-Thread-ID: https://ampcode.com/threads/T-019dfc78-8557-712b-9944-bbff9a4a3b76
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>

* fix(ci): keep no-default builds free of op deps (foundry-rs#14612)

* feat: cast unauthorized flow → wallet.tempo access-key authorization (foundry-rs#14517)

* feat: cast unauthorized flow → wallet.tempo access-key authorization

Amp-Thread-ID: https://ampcode.com/threads/T-019df174-9538-713b-b8c9-5001b1ad4719
Co-authored-by: Amp <amp@ampcode.com>

* fmt

* feat(cast): replace TEMPO_NO_BROWSER env with  flag

* revert token addresses

---------

Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* docs(expect-emit): clarify next-call semantics and warn about caught-revert leak (foundry-rs#14620)

docs(cheatcodes): clarify expectEmit next-call semantics and caught-revert leak

expectEmit is a 'next call' assertion. If the call immediately after expectEmit
reverts and the revert is swallowed by the caller (low-level call or try/catch),
the unmatched expectation can leak forward and be satisfied by a later unrelated
emission, silently turning a broken test green.

Document the constraint on the natspec for both no-arg and topic-checking
overloads, and regenerate cheatcodes.json.

Refs: foundry-rs#14618

Amp-Thread-ID: https://ampcode.com/threads/T-019dfd96-7a03-7249-8c10-af20ee2729f5

Co-authored-by: Amp <amp@ampcode.com>

* fix(cheatcodes): enforce `expectRevert` reverter address for CREATE frames (foundry-rs#14615)

* fix(cheatcodes): enforce `expectRevert` reverter address for CREATE
frames

The reverter address argument to `vm.expectRevert` was silently ignored
when the innermost reverting frame was a CREATE (top-level or nested),
because create_end never populated `expected_revert.reverted_by`.

Mirror call_end's logic in create_end: when the outcome reverts and a
reverter address is expected, record outcome.address (revm guarantees
this is Some(would-be address) whenever the constructor executed).

Adds positive regression tests for top-level and nested-CREATE reverts,
and a negative regression test asserting wrong-reverter now fails.

Co-authored-by: Amp <amp@ampcode.com>

* improve coverage

* add Derek's suggested test cases

* fix: forge fmt for ExpectRevert.t.sol

Amp-Thread-ID: https://ampcode.com/threads/T-019dfdc5-5414-70b6-9f49-cb5797a37a29
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* fix(script): keep plain Tempo broadcasts non-AA (foundry-rs#14616)

* fix(script): don't force Tempo AA fee_token from --network tempo alone

Plain --network tempo (or any selection that just sets the network to
Tempo) does not by itself imply a Tempo AA / type 0x76 transaction.
Defaulting tempo.common.fee_token to PATH_USD_ADDRESS solely from
evm_opts.networks.is_tempo() caused every unsigned broadcast tx to flow
through TempoOpts::apply, which set fee_token on the request and
promoted it to the Tempo AA tx envelope. Signers that only know how to
sign ordinary Ethereum transactions (e.g. the Ledger Ethereum app)
then rejected the transaction with 'received an unexpected empty
response'.

Gate the default on an actual Tempo AA opt-in:

  - --batch (Tempo batch txs are themselves AA and need a fee token), or
  - any explicit --tempo.* flag (sponsor, expiring nonce, nonce key/lane,
    ...) which already forces an AA tx and benefits from a default fee
    token.

Explicit --tempo.fee-token continues to win over the default in all
cases, and non-Tempo networks never default the fee token.

Add unit tests for each scenario.

Amp-Thread-ID: https://ampcode.com/threads/T-019dfd37-2354-712f-95b1-2584fd47ad5e
Co-authored-by: Amp <amp@ampcode.com>

* fix(script): don't force eth_estimateGas on plain Tempo broadcasts

Plain --network tempo produces an ordinary EIP-1559/legacy transaction
(see tempo-alloy::TempoTransactionRequest::output_tx_type), so the local
simulation gas estimate is sufficient. Forcing RPC re-estimation in this
case can surface node-side errors such as 'gas required exceeds
allowance (0)' (Geth-style balance/gasPrice cap from eth_estimateGas)
on flows that previously worked, including Ledger-signed broadcasts
that just got unblocked from the type 0x76 regression.

Match tempo-foundry's behaviour: only force eth_estimateGas on Tempo
when the user has actually opted into Tempo AA semantics (--batch or
any explicit --tempo.* flag).

Extract the gating into needs_tempo_aa_rpc_estimate(...) and add
focused unit tests mirroring the fee-token gating tests.

Amp-Thread-ID: https://ampcode.com/threads/T-019dfd37-2354-712f-95b1-2584fd47ad5e
Co-authored-by: Amp <amp@ampcode.com>

* fix(script): don't re-estimate plain Tempo chain broadcasts

---------

Co-authored-by: Amp <amp@ampcode.com>

* fix(cheatcodes): preserve reverts with `expectEmit` (foundry-rs#14619)

* test: added regression test

* fix: re-order revert handling

* refactor: simplify

* lint: fmt

* polish: tighten comment, extend test with revert reason and custom error

Amp-Thread-ID: https://ampcode.com/threads/T-019dfd96-7a03-7249-8c10-af20ee2729f5
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>

* feat(lint): add tx-origin detector (foundry-rs#14589)

* feat(lint): add tx-origin detector

* test(lint): address tx-origin review feedback

* fix: ui bless

* fix(lint): cover tx-origin index and ternary predicates

* test(lint): bless tx-origin snapshot

---------

Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>

* refactor(tempo): prepare batch access key txs w/ helper (foundry-rs#14597)

fix(tempo): prepare batch access key txs before estimation

* fix(anvil): respect non-zero genesis block in Otterscan APIs  (foundry-rs#14490)

fix(anvil): respect non-zero genesis block in Otterscan APIs

The three Otterscan address-history endpoints (`ots_searchTransactionsBefore`/`After`, `ots_getTransactionBySenderAndNonce`) hardcoded `unwrap_or(1)` / `unwrap_or_default()` as the lower bound of their block scan, which breaks when `genesis_block_number` is non-zero (e.g. `genesis.json` `number: 73`). Expose `Backend::genesis_number()` and fall back to `genesis_number() + 1` in non-fork mode, mirroring the existing post-fork `f.block_number() + 1` convention.

---------

Co-authored-by: Isagi Yates <isagiyates@gmail.com>
Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: steven <corderosteven6@gmail.com>
Co-authored-by: stevencartavia <112043913+stevencartavia@users.noreply.github.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: figtracer <me@figtracer.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: Sergei Shulepov <s.pepyakin@gmail.com>
Co-authored-by: zerosnacks <zerosnacks@protonmail.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: cui <cuiweixie@gmail.com>
Co-authored-by: Centaur AI <ai@centaur.local>
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: Nikki <gutonosa@protonmail.com>
Co-authored-by: srdtrk <59252793+srdtrk@users.noreply.github.com>
Co-authored-by: Mikhail Mikheev <16622558+mmv08@users.noreply.github.com>
Co-authored-by: lazymio <mio@lazym.io>
Co-authored-by: Emma Jamieson-Hoare <emmajam@users.noreply.github.com>
Co-authored-by: VIkions <99107287+vikions@users.noreply.github.com>
Co-authored-by: Aïssata <mikeslowcoder@proton.me>
Dargon789 and others added 10 commits May 7, 2026 06:52
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Fix formatting in cargo.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Fix indentation for on_fail condition in CI config

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Fix indentation in CircleCI configuration

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* chore(deps): bump taiki-e/install-action from 2.62.21 to 2.62.31 (#139)

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.62.21 to 2.62.31.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/v2.62.21...0005e0116e92d8489d8d96fbff83f061c79ba95a)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
  dependency-version: 2.62.31
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore(deps): bump github/codeql-action from 3 to 4 (#138)

Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3 to 4.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/github/codeql-action/compare/v3...v4)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-version: '4'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore(deps): bump snyk/actions

Bumps [snyk/actions](https://github.com/snyk/actions) from 14818c4695ecc4045f33c9cee9e795a788711ca4 to 9adf32b1121593767fc3c057af55b55db032dc04.
- [Release notes](https://github.com/snyk/actions/releases)
- [Commits](https://github.com/snyk/actions/compare/14818c4695ecc4045f33c9cee9e795a788711ca4...9adf32b1121593767fc3c057af55b55db032dc04)

---
updated-dependencies:
- dependency-name: snyk/actions
  dependency-version: 9adf32b1121593767fc3c057af55b55db032dc04
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update CircleCI config with comments and formatting

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update config.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update and rename ci-say-hello.yml to ci-web3-defi-gamefi.yml (#154)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/ci-web3-defi-gamefi.yml (#155)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/ci_deploy.yml (#158)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/cargo.yml (#159)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* chore(deps): bump taiki-e/install-action from 2.62.31 to 2.62.33 (#162)

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.62.31 to 2.62.33.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/0005e0116e92d8489d8d96fbff83f061c79ba95a...e43a5023a747770bfcb71ae048541a681714b951)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
  dependency-version: 2.62.33
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore(deps): bump actions/checkout from 4 to 5 (#163)

Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v4...v5)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Merge branch 'foundry-rs:master'  (#164)

* Create ci_cargo.yml (#72)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Create config.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Rename ci_cargo.yml to cargo.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* fix(fmt): handle trailing coments between base contracts (#12127)

* fix(fmt): account for ternary operators when estimating size

* fix(fmt): handle comments between inherited base contracts

* test: layout + base inheritance

* feat(forge): add bypass prevrandao (#12125)

* feat(forge): add bypass prevrandao

* Update crates/evm/networks/src/lib.rs

Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>

* changes after review: remove duped code

---------

Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>

* fix(fmt): filter libs when recursing (#12119)

* fix(fmt): account for ternary operators when estimating size

* fix(fmt): filter libs when recursing

* style: clippy

* test: wipe contracts before formatting

* test: explicitly test ignore

* fix(fmt): break try stmts in a fn header-like fashion (#12131)

* chore(deps): bump softprops/action-gh-release from 2.3.4 to 2.4.1

Bumps [softprops/action-gh-release](https://github.com/softprops/action-gh-release) from 2.3.4 to 2.4.1.
- [Release notes](https://github.com/softprops/action-gh-release/releases)
- [Changelog](https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md)
- [Commits](https://github.com/softprops/action-gh-release/compare/62c96d0c4e8a889135c1f3a25910db8dbe0e85f7...6da8fa9354ddfdc4aeace5fc48d7f679b5214090)

---
updated-dependencies:
- dependency-name: softprops/action-gh-release
  dependency-version: 2.4.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* chore(deps): bump taiki-e/install-action from 2.62.28 to 2.62.33 (#161)

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.62.28 to 2.62.33.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/e7ef886cf8f69c25ecef6bbc2858a42e273496ec...e43a5023a747770bfcb71ae048541a681714b951)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
  dependency-version: 2.62.33
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

---------

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* fix(anvil): always disable nonce check (foundry-rs#12144) (#165)

* test: refactor testdata/ tests to be run in `forge test` (#12049)

* test: run forge test on testdata/

* chore: refactor to use common Test contract

* chore: disable testGasMeteringExternal, via-ir

* test: rm unused repros

* fix: paths

* upd

* fmt

* fix more tests

* test: turn testNonExistingContractRevert into expectRevert

* fix some more paths

* legacy assertions

* compile paris with paris

* fix: set configs for fs tests

* fix remaining paths in cheats

* restrict fs permissions

* fix: set runtime evm_version too

* fix vyper

* fix: a couple of repros

* fix: we have storage layouts

* fix: 3223, 3674: set sender

* reorder

* feat: move repros expected failures to snapshots

* feat: migrate remaining repros tests

* feat: rm migrated files

* skip testRevertIfGetUnlinked

* move expected core/ failures

* upd

* move logs/

* move all forgetest tests from it/ to cli/

* fix fork test

* move trace/

* tmp: move fuzz/invariant out of fuzz/

* move fuzz/

* forge fmt

* wips

* fix: both vyper and paris; set src/

* canon

* lib log

* logs

* Revert "fix: set runtime evm_version too"

This reverts commit 7ca544b10047f608d57c74fb3500a5fbe7e2650e.

Contract-level inline config will set evm version for libraries too,
which means we fail on deploying libraries that are compiled with
newer evm version.

* fix: set evm version where needed, per test function

* test: reduce gas wastage

* chore: clippy

* invariant mod.rs

* test: fix linking tests with new utils

* redact_with

* Revert "wips"

This reverts commit ee2c17a3023ca7ce8e7effccf0ea0a0f28f6e510.

* migrate invariant/target{,Abi}

* migrate InvariantAfterInvariant.t.sol

* migrate InvariantAssume.t.sol

* migrate InvariantCalldataDictionary.t.sol, more test utils

* migrate InvariantCustomError.t.sol

* migrate InvariantExcludedSenders.t.sol

* migrate InvariantFixtures.t.sol

* migrate InvariantHandlerFailure.t.sol

* interlude: forgot to use a new file

* migrate InvariantInnerContract.t.sol

* migrate InvariantPreserveState.t.sol

* migrate InvariantReentrancy.t.sol

* migrate InvariantRollFork.t.sol

* migrate InvariantScrapeValues.t.sol

* migrate InvariantSequenceNoReverts.t.sol

* migrate InvariantShrinkBigSequence.t.sol

* migrate InvariantShrinkFailOnRevert.t.sol

* migrate InvariantShrinkWithAssert.t.sol

* migrate InvariantTest1.t.sol

* fix InvariantInnerContract.t.sol

* update new Rlp test

* com

* better com

* nuke tests/it

* test: fix testdata paths in script tester

* test: fix relative paths in test_cmd

* test: redact more in issue_2851

* fix: copy testdata correctly

* trace addrs

* manual retry logic with --retry

* fix nondeterministic output

* debug: fs lock error context

* test: fix project root for windows

* test: skip project root test if unset

* normalize both

* typo

* Revert "typo"

This reverts commit 402bea105c6f38b82664b50ca854f95e456df795.

* Revert "debug: fs lock error context"

This reverts commit e5caeddd1e4cb457d7b24d7d7fdfdb370e2feabf.

* fix

* fix: locked_write_line for windows

* chore: clippy

* fmt

* chore: speed up fuzzed_selected_targets

* other way

* fix nondeterministic output 2

* fix: disable persistence

* test: revert old via-ir

* ci: tweak cache key

* do not run trace test when isolate

---------

Co-authored-by: grandizzy <grandizzy.the.egg@gmail.com>

* fix(anvil): always disable nonce check (#12144)

* deps: bump deps (#12149)

* deps: bump deps

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* minimum Cargo.lock

---------

Co-authored-by: rplusq <rplusq@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com>

---------

Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com>
Co-authored-by: grandizzy <grandizzy.the.egg@gmail.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: Rafael Quintero <32346241+rplusq@users.noreply.github.com>
Co-authored-by: rplusq <rplusq@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>

* Update test.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update test.yml (#167)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update test.yml (#168)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/ci.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update cargo.yml (#171)

CI/CD Configuration Update: The CircleCI configuration file, cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring the CI pipeline utilizes a more recent Rust toolchain.

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/ci_v1.yml (#173)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update cargo.yml (#174)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* chore(deps): bump taiki-e/install-action from 2.62.28 to 2.62.33 (#175)

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.62.28 to 2.62.33.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/v2.62.28...e43a5023a747770bfcb71ae048541a681714b951)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
  dependency-version: 2.62.33
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Delete .circleci/cargo.yml (#179)

I Configuration Removal: The .circleci/cargo.yml file, which defined CircleCI jobs for building and testing Rust projects, has been completely removed from the repository.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/ci_v1.yml (#182)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update config.yml (#183)

Configuration File Cleanup: Removed an unnecessary blank line in the .circleci/config.yml file, improving its formatting and readability.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update config.yml (#187)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/config.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci directory

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update ci_v1.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update Rust Docker image version to 1.89.0

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 76: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* chore(deps): bump alloy-dyn-abi in the cargo group across 1 directory

Bumps the cargo group with 1 update in the / directory: [alloy-dyn-abi](https://github.com/alloy-rs/core).


Updates `alloy-dyn-abi` from 0.8.25 to 0.8.26
- [Release notes](https://github.com/alloy-rs/core/releases)
- [Changelog](https://github.com/alloy-rs/core/blob/v0.8.26/CHANGELOG.md)
- [Commits](https://github.com/alloy-rs/core/compare/v0.8.25...v0.8.26)

---
updated-dependencies:
- dependency-name: alloy-dyn-abi
  dependency-version: 0.8.26
  dependency-type: direct:production
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>

* Create ci-web3-gamefi.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 74: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 83: Uncontrolled data used in path expression

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 93: Uncontrolled data used in path expression

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 76: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 94: Uncontrolled data used in path expression

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 80: Server-side request forgery

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 80: Server-side request forgery

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Create codeql.yml (#208)

* Update ci.yml (#209)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the Rust version in the CI from 1.88.0 to 1.89.0. While this is a good maintenance step, I've identified a potential improvement for your CI configuration. The project's Cargo.toml specifies a Minimum Supported Rust Version (MSRV) of 1.86, but the CI doesn't test against it. I've added a comment suggesting the addition of an MSRV check to prevent compatibility issues.

* Update cargo.yml (#210)

https://github.com/apps/gemini-code-assist
-------------------
Code Review

This pull request downgrades the Rust version in the CI pipeline from 1.88.0 to 1.87.0. This is inconsistent with the project's declared Minimum Supported Rust Version (MSRV) of 1.89 in Cargo.toml. My review highlights this discrepancy and suggests aligning the CI's Rust version with the MSRV to ensure the project's compatibility guarantees are properly tested.

---------------
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Foundry rs maste 1f4b36a (#214)

* Create jekyll.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Create docker-image.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 58: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update .github/workflows/docker-image.yml

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update docker-image.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Revert "chore: fix isolate tests (#10344)"

This reverts commit 70ded2b35f95ee9b4ee94f5e44961914d30a87f7.

* Delete .github/workflows/jekyll.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 19: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>

* Update and rename docker-image.yml to docker.yml (#218)

Streamline the Docker CI workflow by renaming the file and enhancing it with scheduled runs, Buildx multi-platform builds, metadata tagging, conditional pushes, and automated image signing with Cosign.

CI:

Rename and replace the legacy docker-image.yml workflow with docker.yml
Add scheduled cron runs and triggers on pushes to master, semver tags, and PRs
Configure Docker Buildx for multi-platform builds with cache
Extract Docker metadata and conditionally push images to GHCR on non-PR events
Install Cosign and sign published Docker images using ephemeral identity tokens

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update ci.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Create docker-image.yml (#224)

CI:

Introduce docker-image.yml GitHub Actions workflow to checkout code and build Docker image on ubuntu-latest

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update config.yml (#225)

CI:

Insert comment lines to delineate and structure sections in .circleci/config.yml for enhanced clarity

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update sequence.rs (#226)

Enhancements:

Add standalone # lines in sequence.rs to serve as hidden placeholders for rustdoc examples

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update dependencies.yml (#227)

* Update dependencies.yml

Refactor the weekly dependencies workflow to inline cargo update steps, auto-generate commit messages and PR bodies with update logs, and use the create-pull-request action to open update PRs on a dedicated branch.

Enhancements:

Define environment variables for GitHub token, branch name, PR title, and PR body including cargo update logs
Inline checkout, Rust toolchain setup, and cargo update command with log cleanup instead of relying on an external workflow
Craft commit messages and PR bodies dynamically by capturing and formatting cargo update output
Use peter-evans/create-pull-request to push Cargo.lock updates to a 'cargo-update' branch

CI:

Move permissions and GitHub token configuration into the job context
Explicitly set the runner to ubuntu-latest and remove the top-level empty permissions block

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update .github/workflows/dependencies.yml

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>

* Update npm.yml (#228)

CI:

Add comment to the Publish Binary step indicating it runs automatically after a successful release workflow or can be triggered manually with a run_id

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update snyk-container.yml (#229)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update nextest.yml (#230)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update const.ts (#231)

Code Formatting: Removed an extraneous blank line in npm/src/const.ts to improve code cleanliness and consistency.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Revert "Create web3_defi_gamefi.yml (#61)" (#233)

This reverts commit 8575916b7675f246b54daf70cfddccb3f5b97fb0.

* Create deploy.yml (#240)

* Create deploy.yml
CI:

Add GitHub Actions workflow to build the Rust project, run tests, and build a Docker image on pushes to main/master
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 106: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* Update dependencies.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update dependencies.yml (#247)

Improve readability of the GitHub Actions dependencies workflow by adjusting whitespace and adding blank lines
CI:
Add blank line before the workflow name declaration
Insert blank line after the scheduled cron job entry
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update dependencies.yml (#248)

CI:
Remove extraneous blank line in .github/workflows/dependencies.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update test.yml (#249)

CI:
Remove dev branch from test workflow triggers
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update Cargo.lock (#253)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update Cargo.lock (#254)

Chores:
Regenerate Cargo.lock to update dependencies
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Create config.yml (#255)

* Create config.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update .circleci/config.yml

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>

* Update config.yml (#256)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* fix: upgrade tsdown from 0.15.12 to 0.16.1

Snyk has created this PR to upgrade tsdown from 0.15.12 to 0.16.1.

See this package in npm:
tsdown

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/8da85645-409e-46fa-bd46-9b58e7905fb8?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

* Create google.yml (#266)

CI:
Introduce a Google Cloud deployment workflow that builds a Docker image, pushes it to Artifact Registry, and deploys it to a GKE cluster on pushes to the main branches.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update flake.lock (#269)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update flake.nix (#270)

Adjust Nix flake development shell configuration for better cross-platform support and simplify dependencies.

Enhancements:

Remove the dprint dependency from the Nix development shell.
Add conditional AppKit framework linkage on Darwin systems in the Nix shell configuration.
Drop custom hardeningDisable settings from the Nix development shell definition.

https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the Nix flake configuration to improve cross-platform support and simplify dependencies. The changes include removing dprint and hardeningDisable settings, and conditionally adding the AppKit framework for Darwin systems. While most changes are beneficial, removing dprint from the development shell dependencies while its configuration file remains could cause issues for contributors. I've added a comment regarding this potential inconsistency.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update Cargo.toml (#271)

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update nextest.toml (#272)

Adjust test runner configuration for nextest to better handle long-running and specific tests.

Enhancements:

Introduce a dedicated test group that limits chisel-serial tests to a single thread.
Increase the default slow-test timeout period to reduce premature terminations for longer-running tests.
Expand the slow-timeout override filter to include both ext_integration and can_test_forge_std tests.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update dprint.json (#273)

(https://github.com/apps/gemini-code-assist)
Code Review
This pull request updates the dprint.json configuration file. The changes correctly enable formatting for dprint.json itself by modifying the excludes list, update the JSON and Markdown dprint plugins to their latest versions, and add a final newline to the file for POSIX compliance. These are all good maintenance improvements. The changes have been reviewed and appear to be correct and beneficial. No issues were found.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update .github/workflows/apisec-scan.yml

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update counter/README.md

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update .github/ISSUE_TEMPLATE/bug_report.md

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Dependabot/cargo/cargo 38744a1864 (#282)

* chore(deps): bump alloy-dyn-abi in the cargo group across 1 directory

Bumps the cargo group with 1 update in the / directory: [alloy-dyn-abi](https://github.com/alloy-rs/core).


Updates `alloy-dyn-abi` from 0.8.25 to 0.8.26
- [Release notes](https://github.com/alloy-rs/core/releases)
- [Changelog](https://github.com/alloy-rs/core/blob/v0.8.26/CHANGELOG.md)
- [Commits](https://github.com/alloy-rs/core/compare/v0.8.25...v0.8.26)

---
updated-dependencies:
- dependency-name: alloy-dyn-abi
  dependency-version: 0.8.26
  dependency-type: direct:production
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update and rename ci.yml to cargo.yml (#268)

Update CircleCI configuration to use a different Rust toolchain image and rename the workflow file.

Build:

Rename the CircleCI configuration file from ci.yml to cargo.yml.
Change the CircleCI Docker image to use Rust 1.78.0 instead of 1.88.0.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Fix cloning of compiler settings for Vyper input

Replace context.clone().compiler_settings.vyper with 
context.compiler_settings.vyper.clone() to avoid unnecessary 
cloning of the entire VerificationContext. This reduces memory 
allocations when creating VyperInput instances.

Applied to both etherscan and sourcify verification providers.

* Update config.yml (#283)

Summary by Sourcery
Update CircleCI pipeline to use a custom Docker executor and job tailored to the project instead of the example hello-world workflow.

Enhancements:

Introduce a reusable custom executor that pulls from the stable cimg/base Docker image with Docker Hub authentication.
CI:

Replace the sample say-hello job and workflow with a project-specific job and workflow wired to the new custom executor in .circleci/config.yml.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* fix: use network-specific BaseFeeParams for Optimism in Anvil

* Dargon789 patch 1 (#285)

* Update test.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update test.yml (#167)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/ci_v1.yml (#173)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update cargo.yml (#174)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .circleci/config.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 74: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 83: Uncontrolled data used in path expression

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 93: Uncontrolled data used in path expression

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 76: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 94: Uncontrolled data used in path expression

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 80: Server-side request forgery

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update cargo.yml (#210)

https://github.com/apps/gemini-code-assist
-------------------
Code Review

This pull request downgrades the Rust version in the CI pipeline from 1.88.0 to 1.87.0. This is inconsistent with the project's declared Minimum Supported Rust Version (MSRV) of 1.89 in Cargo.toml. My review highlights this discrepancy and suggests aligning the CI's Rust version with the MSRV to ensure the project's compatibility guarantees are properly tested.

---------------
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Fix cloning of compiler settings for Vyper input

Replace context.clone().compiler_settings.vyper with 
context.compiler_settings.vyper.clone() to avoid unnecessary 
cloning of the entire VerificationContext. This reduces memory 
allocations when creating VyperInput instances.

Applied to both etherscan and sourcify verification providers.

---------

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: Gengar <creeptogengar@gmail.com>

* merge gh-master (#287)

* Create config.yml (#236)

Create .circleci/config.yml defining a version 2.1 pipeline with a docker-based "say-hello" job, checkout and echo steps, and a workflow to orchestrate it
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* fix(evm): use timestamp-based blob base fee calculation (#12959)

* fix(evm): use timestamp-based blob base fee calculation

* chore: use patch

* Now BPO1 is default

* bump to hardforks to 0.4.7

---------

Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>

* fix(config): reject bare versions in compilation restrictions (#12955)

fmt

Co-authored-by: tefyosL-sol <gasgoblinn@gmail.com>

* Revert "fix(config): err on unknown profile (#12946)" (#12964)

This reverts commit 6ff4b52e2e572e93d0cd81591b1bd0e6ad9ed507.

* Update crates/config/src/compilation.rs

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: cakevm <cakevm@proton.me>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: Theodore Solis <gasgobling@gmail.com>
Co-authored-by: tefyosL-sol <gasgoblinn@gmail.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Foundry/ethereum ux (#284)

* Potential fix for code scanning alert no. 19: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 61: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 74: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Create config.yml (#105)

* Create cargo.yml (#106)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .github/workflows/docker-image.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Revert "Create cargo.yml (#106)"

This reverts commit 251a2b4fce0c50e3426ffb2022d9abef5b948fa9.

* Create cargo.yml (#213)

https://github.com/apps/gemini-code-assist

Code Review
This pull request introduces a CircleCI workflow to automate formatting checks and tests. My review has identified two main issues in the configuration: redundant steps that would unnecessarily increase job execution time, and a mismatch between the Rust version in the CI environment and the one specified in the project's Cargo.toml. I've provided suggestions to fix these issues for a more efficient and consistent CI process.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* Gamefi defi (#288)

* chore: ignore RUSTSEC-2025-0137 (#12941)

Co-authored-by: Claude <noreply@anthropic.com>

* chore(deps): weekly `cargo update` (#12940)

* chore(deps): weekly `cargo update`

    Updating git repository `https://github.com/rust-cli/rexpect`
    Updating git repository `https://github.com/paradigmxyz/solar.git`
    Skipping git submodule `https://github.com/argotorg/solidity.git` due to update strategy in .gitmodules
    Updating git repository `https://github.com/tempoxyz/tempo`
    Updating git repository `https://github.com/paradigmxyz/reth`
     Locking 71 packages to latest compatible versions
    Updating alloy-chains v0.2.23 -> v0.2.24
    Updating alloy-consensus v1.1.3 -> v1.2.1
    Updating alloy-consensus-any v1.1.3 -> v1.2.1
    Updating alloy-contract v1.1.3 -> v1.2.1
    Updating alloy-dyn-abi v1.5.1 -> v1.5.2
    Updating alloy-eip5792 v1.1.3 -> v1.2.1
    Updating alloy-eips v1.1.3 -> v1.2.1
    Updating alloy-ens v1.1.3 -> v1.2.1
    Updating alloy-genesis v1.1.3 -> v1.2.1
    Updating alloy-json-abi v1.5.1 -> v1.5.2
    Updating alloy-json-rpc v1.1.3 -> v1.2.1
    Updating alloy-network v1.1.3 -> v1.2.1
    Updating alloy-network-primitives v1.1.3 -> v1.2.1
    Updating alloy-primitives v1.5.1 -> v1.5.2
    Updating alloy-provider v1.1.3 -> v1.2.1
    Updating alloy-pubsub v1.1.3 -> v1.2.1
    Updating alloy-rpc-client v1.1.3 -> v1.2.1
    Updating alloy-rpc-types v1.1.3 -> v1.2.1
    Updating alloy-rpc-types-anvil v1.1.3 -> v1.2.1
    Updating alloy-rpc-types-any v1.1.3 -> v1.2.1
    Updating alloy-rpc-types-beacon v1.1.3 -> v1.2.1
    Updating alloy-rpc-types-debug v1.1.3 -> v1.2.1
    Updating alloy-rpc-types-engine v1.1.3 -> v1.2.1
    Updating alloy-rpc-types-eth v1.1.3 -> v1.2.1
    Updating alloy-rpc-types-trace v1.1.3 -> v1.2.1
    Updating alloy-rpc-types-txpool v1.1.3 -> v1.2.1
    Updating alloy-serde v1.1.3 -> v1.2.1
    Updating alloy-signer v1.1.3 -> v1.2.1
    Updating alloy-signer-aws v1.1.3 -> v1.2.1
    Updating alloy-signer-gcp v1.1.3 -> v1.2.1
    Updating alloy-signer-ledger v1.1.3 -> v1.2.1
    Updating alloy-signer-local v1.1.3 -> v1.2.1
    Updating alloy-signer-trezor v1.1.3 -> v1.2.1
    Updating alloy-signer-turnkey v1.1.3 -> v1.2.1
    Updating alloy-sol-macro v1.5.1 -> v1.5.2
    Updating alloy-sol-macro-expander v1.5.1 -> v1.5.2
    Updating alloy-sol-macro-input v1.5.1 -> v1.5.2
    Updating alloy-sol-type-parser v1.5.1 -> v1.5.2
    Updating alloy-sol-types v1.5.1 -> v1.5.2
    Updating alloy-transport v1.1.3 -> v1.2.1
    Updating alloy-transport-http v1.1.3 -> v1.2.1
    Updating alloy-transport-ipc v1.1.3 -> v1.2.1
    Updating alloy-transport-ws v1.1.3 -> v1.2.1
    Updating alloy-trie v0.9.1 -> v0.9.2
    Updating alloy-tx-macros v1.1.3 -> v1.2.1
   Unchanged annotate-snippets v0.12.5 (available: v0.12.10)
   Unchanged anstyle-svg v0.1.11 (available: v0.1.12)
 Downgrading aws-smithy-runtime v1.9.6 -> v1.9.5
    Updating axum-core v0.5.5 -> v0.5.6
    Updating cc v1.2.50 -> v1.2.51
    Updating derive_more v2.1.0 -> v2.1.1
    Updating derive_more-impl v2.1.0 -> v2.1.1
    Updating dtoa v1.0.10 -> v1.0.11
    Updating find-msvc-tools v0.1.5 -> v0.1.6
   Unchanged generic-array v0.14.7 (available: v0.14.9)
   Unchanged icu_collections v2.0.0 (available: v2.1.1)
   Unchanged icu_normalizer v2.0.1 (available: v2.1.1)
   Unchanged icu_normalizer_data v2.0.0 (available: v2.1.1)
   Unchanged icu_properties v2.0.2 (available: v2.1.2)
   Unchanged icu_properties_data v2.0.1 (available: v2.1.2)
   Unchanged idna_adapter v1.1.0 (available: v1.2.1)
    Updating itoa v1.0.15 -> v1.0.17
    Updating jiff v0.2.16 -> v0.2.17
    Updating jiff-static v0.2.16 -> v0.2.17
    Updating libredox v0.1.11 -> v0.1.12
    Updating libz-rs-sys v0.5.4 -> v0.5.5
   Unchanged matchit v0.8.4 (available: v0.8.6)
   Unchanged mdbook v0.4.52 (available: v0.5.2)
    Updating portable-atomic v1.12.0 -> v1.13.0
    Updating proc-macro2 v1.0.103 -> v1.0.104
   Unchanged protobuf v3.3.0 (available: v3.7.2)
   Unchanged protobuf-support v3.3.0 (available: v3.7.2)
   Unchanged rand v0.8.5 (available: v0.9.2)
   Unchanged ratatui v0.29.0 (available: v0.30.0)
    Updating reqwest v0.12.26 -> v0.12.28
    Updating ruint v1.17.0 -> v1.17.1
    Updating rustix v1.1.2 -> v1.1.3
    Updating ryu v1.0.21 -> v1.0.22
    Updating schemars v1.1.0 -> v1.2.0
    Updating schemars_derive v1.1.0 -> v1.2.0
    Updating serde_json v1.0.145 -> v1.0.148
    Updating signal-hook-registry v1.4.7 -> v1.4.8
    Updating syn-solidity v1.5.1 -> v1.5.2
    Updating tempfile v3.23.0 -> v3.24.0
   Unchanged trezor-client v0.1.4 (available: v0.1.5)
   Unchanged unicode-width v0.2.0 (available: v0.2.2)
   Unchanged vergen v8.3.2 (available: v9.0.6)
    Updating zlib-rs v0.5.4 -> v0.5.5
      Adding zmij v1.0.0
note: to see how you depend on a package, run `cargo tree --invert <dep>@<ver>`

* touchups

* touchups

---------

Co-authored-by: mattsse <19890894+mattsse@users.noreply.github.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>

* Update flake.lock (#12939)

flake.lock: Update

Flake lock file updates:

• Updated input 'fenix':
    'github:nix-community/fenix/16642c5' (2025-12-20)
  → 'github:nix-community/fenix/3479aaf' (2025-12-27)
• Updated input 'fenix/rust-analyzer-src':
    'github:rust-lang/rust-analyzer/ea1d299' (2025-12-18)
  → 'github:rust-lang/rust-analyzer/8c5a68e' (2025-12-26)
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/7d853e5' (2025-12-19)
  → 'github:NixOS/nixpkgs/3edc4a3' (2025-12-27)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com>

* fix(chisel): uninitalized variables (#12937)

* chore(deps): bump Swatinem/rust-cache from 2.8.1 to 2.8.2 (#12919)

Bumps [Swatinem/rust-cache](https://github.com/swatinem/rust-cache) from 2.8.1 to 2.8.2.
- [Release notes](https://github.com/swatinem/rust-cache/releases)
- [Changelog](https://github.com/Swatinem/rust-cache/blob/master/CHANGELOG.md)
- [Commits](https://github.com/swatinem/rust-cache/compare/f13886b937689c021905a6b90929199931d60db1...779680da715d629ac1d338a641029a2f4372abb5)

---
updated-dependencies:
- dependency-name: Swatinem/rust-cache
  dependency-version: 2.8.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* chore(deps): bump peter-evans/create-pull-request from 7.0.11 to 8.0.0 (#12918)

Bumps [peter-evans/create-pull-request](https://github.com/peter-evans/create-pull-request) from 7.0.11 to 8.0.0.
- [Release notes](https://github.com/peter-evans/create-pull-request/releases)
- [Commits](https://github.com/peter-evans/create-pull-request/compare/22a9089034f40e5a961c8808d113e2c98fb63676...98357b18bf14b5342f975ff684046ec3b2a07725)

---
updated-dependencies:
- dependency-name: peter-evans/create-pull-request
  dependency-version: 8.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>

* chore: sepolia rpc url (#12945)

chore: sepolia rpc url private

* chore(deps): bump crate-ci/typos from 1.40.0 to 1.40.1 (#12949)

Bumps [crate-ci/typos](https://github.com/crate-ci/typos) from 1.40.0 to 1.40.1.
- [Release notes](https://github.com/crate-ci/typos/releases)
- [Changelog](https://github.com/crate-ci/typos/blob/master/CHANGELOG.md)
- [Commits](https://github.com/crate-ci/typos/compare/2d0ce569feab1f8752f1dde43cc2f2aa53236e06...1a319b54cc9e3b333fed6a5c88ba1a90324da514)

---
updated-dependencies:
- dependency-name: crate-ci/typos
  dependency-version: 1.40.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore(deps): bump DeterminateSystems/determinate-nix-action from 3.15.0 to 3.15.1 (#12950)

chore(deps): bump DeterminateSystems/determinate-nix-action

Bumps [DeterminateSystems/determinate-nix-action](https://github.com/determinatesystems/determinate-nix-action) from 3.15.0 to 3.15.1.
- [Release notes](https://github.com/determinatesystems/determinate-nix-action/releases)
- [Commits](https://github.com/determinatesystems/determinate-nix-action/compare/95732e95d70db3ba1e0adc26a63c5e0375aba78c...1d699fc25db3f9e079cd2f168ca007a4183389be)

---
updated-dependencies:
- dependency-name: DeterminateSystems/determinate-nix-action
  dependency-version: 3.15.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore(deps): bump taiki-e/install-action from 2.65.1 to 2.65.7 (#12951)

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.65.1 to 2.65.7.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/b9c5db3aef04caffaf95a1d03931de10fb2a140f...4c6723ec9c638cccae824b8957c5085b695c8085)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
  dependency-version: 2.65.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* fix(config): err on unknown profile (#12946)

* test: remove duplicate Issue2851 test (#12953)

* chore(cheats): make sign(Wallet) pure (#12912)

* chore(cheats): make sign(Wallet) pure

* ignore

---------

Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>

* fix(evm): use timestamp-based blob base fee calculation (#12959)

* fix(evm): use timestamp-based blob base fee calculation

* chore: use patch

* Now BPO1 is default

* bump to hardforks to 0.4.7

---------

Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>

* fix(config): reject bare versions in compilation restrictions (#12955)

fmt

Co-authored-by: tefyosL-sol <gasgoblinn@gmail.com>

* Revert "fix(config): err on unknown profile (#12946)" (#12964)

This reverts commit 6ff4b52e2e572e93d0cd81591b1bd0e6ad9ed507.

* fix(anvil): use B256 instead of TxHash for block hash parameters (#12961)

Update mod.rs

* Update crates/config/src/compilation.rs

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: mattsse <19890894+mattsse@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: cakevm <cakevm@proton.me>
Co-authored-by: Theodore Solis <gasgobling@gmail.com>
Co-authored-by: tefyosL-sol <gasgoblinn@gmail.com>
Co-authored-by: Desant pivo <pivasdesant@gmail.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>

* Create ci-web3-gamefi.yml (#217) (#289)

Introduce a basic CircleCI pipeline for the web3 GameFi project, providing a custom Docker executor and a stub job within a workflow.

CI:

Add CircleCI config file ci-web3-gamefi.yml with version 2.1 pipeline
Define a custom executor using the cimg/base:stable Docker image with Docker Hub credentials
Create a web3-defi-game-project- job and integrate it into a my-custom-workflow

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Merge pull request #47 (#290)

* Add .circleci/config.yml

* Updated config.yml

* Updated config.yml

* Updated config.yml

* Update test.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 19: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update test.yml (#46)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* chore(deps): bump revm to 24.0.0 (#10601)

* feat: implement add_balance endpoint (#10636)

* fix(bindings): ensure forge bind generates snake_case file names (#10622)

* fix(bindings): ensure forge bind generates snake_case file names

* refactor: use heck crate for snake_case conversion

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* chore: standardize lint help + validate docs existance (#10639)

* feat(cast mktx): add support for "--ethsign" option (#10641)

- Sign transactions using "eth_signTransaction" on local node with unlocked accounts.
- Same TX building logic as in "cast send --unlocked".
- Added a test case to validate the new functionality.

* chore(wallets): improve error message for signer instantiation failure (#10646)

chore(wallets): improve error message on signer instantiation failure

* chore: replaced anvil hardforks with alloy hardforks (#10612)

* chore: replaced anvil hardforks with alloy hardforks

* fixes

* fixes

* fixes

* removed redundant op and alloy hardforks enum

* fixes

* fixes

* bumped alloy hardforks and kept default to prague and isthmus

* bumped alloy-hardforks and fixes

---------

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* fix(`anvil`): latest evm version should be prague (#10653)

* fix(`anvil`): latest evm version should be prague

* fix test

* nit

* chore(deps): bump tracing-subscriber (#51)

Bumps the cargo group with 1 update in the / directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).


Updates `tracing-subscriber` from 0.3.19 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.19...tracing-subscriber-0.3.20)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: direct:production
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update test.yml (#52)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update docker-image.yml (#53)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Create ci_cargo.yml (#59)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Create web3_defi_gamefi.yml (#61)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update dependencies.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 21: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Update dependencies.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update dependencies.yml (#247)

Improve readability of the GitHub Actions dependencies workflow by adjusting whitespace and adding blank lines
CI:
Add blank line before the workflow name declaration
Insert blank line after the scheduled cron job entry
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update dependencies.yml (#248)

CI:
Remove extraneous blank line in .github/workflows/dependencies.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update test.yml (#249)

CI:
Remove dev branch from test workflow triggers
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: pistomat <pistomat@users.noreply.github.com>
Co-authored-by: zark <77061323+zarkk01@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>
Co-authored-by: Ishika Choudhury <117741714+Rimeeeeee@users.noreply.github.com>
Co-authored-by: Yash Atreya <44857776+yash-atreya@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update crates/evm/evm/src/executors/corpus.rs

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Foundry/master test ux (#295)

* Update ci.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update ci.yml (#211)


This pull request updates the Rust version in the CircleCI workflow to 1.89.0. This is a good maintenance task to keep the CI environment up-to-date. I have one suggestion regarding the Docker image tag to potentially simplify future maintenance by automatically adopting patch releases. Overall, the change is correct and beneficial.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update test.yml (#250)

CI:
Include the 'main' branch in the push event triggers for the test workflow
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* fix(fmt): handle trailing coments between base contracts  (#296)

@0xrusowsky @Dargon789 fix(fmt): handle trailing coments between base contracts Revert 142 master (#296)

* Create ci_cargo.yml (#72)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Create config.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Rename ci_cargo.yml to cargo.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* fix(fmt): handle trailing coments between base contracts (#12127)

* fix(fmt): account for ternary operators when estimating size

* fix(fmt): handle comments between inherited base contracts

* test: layout + base inheritance

* Revert "fix(fmt): handle trailing coments between base contracts (#12127)"

This reverts commit b8b5fbb83fa2436063cebc34ddf900abc972b11d.

* Update cargo.yml (#172)

CI/CD Configuration Update: The CircleCI configuration file, .circleci/cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring builds and tests run with the latest stable Rust toolchain.

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Fix cloning of compiler settings for Vyper input

Replace context.clone().compiler_settings.vyper with 
context.compiler_settings.vyper.clone() to avoid unnecessary 
cloning of the entire VerificationContext. This reduces memory 
allocations when creating VyperInput instances.

Applied to both etherscan and sourcify verification providers.

* Remove duplicate logic in TxSigner::address() implementations

---------

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Gengar <creeptogengar@gmail.com>
Co-authored-by: Aganis <aganisgash@gmail.com>

* fix(fmt): handle trailing coments between base contracts  (#296) (#299)

@0xrusowsky @Dargon789 fix(fmt): handle trailing coments between base contracts Revert 142 master (#296)

* Create ci_cargo.yml (#72)



* Create config.yml



* Rename ci_cargo.yml to cargo.yml



* fix(fmt): handle trailing coments between base contracts (#12127)

* fix(fmt): account for ternary operators when estimating size

* fix(fmt): handle comments between inherited base contracts

* test: layout + base inheritance

* Revert "fix(fmt): handle trailing coments between base contracts (#12127)"

This reverts commit b8b5fbb83fa2436063cebc34ddf900abc972b11d.

* Update cargo.yml (#172)

CI/CD Configuration Update: The CircleCI configuration file, .circleci/cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring builds and tests run with the latest stable Rust toolchain.



* Fix cloning of compiler settings for Vyper input

Replace context.clone().compiler_settings.vyper with 
context.compiler_settings.vyper.clone() to avoid unnecessary 
cloning of the entire VerificationContext. This reduces memory 
allocations when creating VyperInput instances.

Applied to both etherscan and sourcify verification providers.

* Remove duplicate logic in TxSigner::address() implementations

---------

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Gengar <creeptogengar@gmail.com>
Co-authored-by: Aganis <aganisgash@gmail.com>

* Update CircleCI configuration for dev stage (#300)

fix Automatic reruns provide a safety net for your CI/CD pipelines by automatically retrying failed steps and/or workflows. Automatic reruns help teams maintain productivity by reducing the need for manual intervention when steps and workflows fail due to temporary issues.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* EIP-4788 implementation

* formatting

* add beacon block root tests

* Update crates/evm/evm/src/executors/trace.rs

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update crates/cast/src/cmd/run.rs

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* feat: upgrade @types/node from 24.10.4 to 25.0.2

Snyk has created this PR to upgrade @types/node from 24.10.4 to 25.0.2.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/8da85645-409e-46fa-bd46-9b58e7905fb8?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

* fix: `svm fails to download solc 0.8.33 on linux/arm64`, bump `svm-rs` (#13007) (#309)

bump svm-rs

Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>

* Ethereumjs/master (#310)

* Potential fix for code scanning alert no. 19: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 61: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Potential fix for code scanning alert no. 74: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Create config.yml (#105)

* Create cargo.yml (#106)

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Delete .github/workflows/docker-image.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Rename ci_cargo.yml to cargo.yml

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* fix(fmt): handle trailing coments between base contracts (#12127)

* fix(fmt): account for ternary operators when estimating size

* fix(fmt): handle comments between inherited base contracts

* test: layout + base inheritance

* Revert "fix(fmt): handle trailing coments between base contracts (#12127)"

This reverts commit b8b5fbb83fa2436063cebc34ddf900abc972b11d.

* Update cargo.yml (#172)

CI/CD Configuration Update: The CircleCI configuration file, .circleci/cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring builds and tests run with the latest stable Rust toolchain.

Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>

* Revert "Create cargo.yml (#106)"

This reverts commit 251a2b4fce0c50e3426ffb2022d9abef5b948fa9.

* Create cargo.yml (#213)

https://github.com/apps/gemini-code-assist

Code Review
This pull request introduces a CircleCI workflow to automate formatting checks and tests. My review has identified two main issues in the configuration: redundant steps that would unnecessarily increase job execution time, and a mismatch between the Rust version in the CI environment and the one specified in the project's Cargo.toml. I've provided suggestions to fix these issues for a more efficient and consistent CI process.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Create docker.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Remove duplicate logic in TxSigner::address() implementations

* fix(fmt): handle trailing coments between base contracts  (#296)

@0xrusowsky @Dargon789 fix(fmt): handle trailin…
Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, we are unable to review this pull request

The GitHub API does not allow us to fetch diffs exceeding 20000 lines

@vercel
Copy link
Copy Markdown

vercel Bot commented May 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
next Canceled Canceled May 7, 2026 2:19am
react Canceled Canceled May 7, 2026 2:19am

@vercel vercel Bot temporarily deployed to Production – next May 7, 2026 02:02 Inactive
@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented May 7, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 7, 2026

Deployment failed with the following error:

Resource is limited - try again in 1 day (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit

@vercel
Copy link
Copy Markdown

vercel Bot commented May 7, 2026

Deployment failed with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This extensive pull request introduces several major updates across the Foundry suite, including enhanced Tempo network support (2D nonce lanes, sponsored transactions, and virtual address operations), the migration of Chisel's type-inference engine to the solar compiler, and the addition of release verification documentation. It also implements feature-gating for Optimism across the workspace and improves fuzz testing by allowing the reproduction of specific runs. The feedback identifies a critical regression in the cheatcode inspector where an early return breaks expectRevert functionality. Additionally, improvements are suggested for the nightly benchmark comparison script regarding robust arithmetic and file handling, as well as a correction to the logic for merging test suite durations in multi-network passes.

Comment thread crates/cheatcodes/src/inspector.rs
Comment thread .github/scripts/compare-nightly.sh Outdated
Comment thread .github/scripts/compare-nightly.sh
Comment thread crates/forge/src/cmd/test/mod.rs Outdated
Dargon789 and others added 4 commits May 7, 2026 09:06
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
@vercel vercel Bot temporarily deployed to Production – react May 7, 2026 02:19 Inactive
@Dargon789 Dargon789 merged commit 12f40d6 into main May 7, 2026
14 of 18 checks passed
@Dargon789 Dargon789 deleted the master branch May 7, 2026 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants