SOME ONE IS STEALING MY CRYPTO

.cargo/config.toml

@@ -1,6 +1,7 @@
 [alias]
 cheats = "test -p foundry-cheatcodes-spec --features schema tests::"
 test-debugger = "test -p forge --test cli manual_debug_setup -- --include-ignored --nocapture"
+bless-lints = "test -p forge --test ui -- --bless"
 
 # Increase the stack size to 10MB for Windows targets, which is in line with Linux
 # (whereas default for Windows is 1MB).

.config/nextest.toml

@@ -1,18 +1,72 @@
 [test-groups]
-chisel-serial = { max-threads = 1 }
+# The on-chain deploy+verify tests share one funded deployer per network and one Etherscan key.
+# Running them concurrently collides on the account nonce and trips Etherscan's 3 calls/sec limit.
+deploy-verify = { max-threads = 1 }
+# The Tempo canaries fork public endpoints that rate limit concurrent replays.
+tempo-canary = { max-threads = 1 }
 
 [profile.default]
 retries = { backoff = "exponential", count = 2, delay = "5s", jitter = true }
-slow-timeout = { period = "1m", terminate-after = 3 }
+slow-timeout = { period = "30s", terminate-after = 3 }
+# Exclude flaky tests from regular CI runs - they run in nightly test-flaky workflow.
+# Exclude the on-chain deploy+verify tests too - they spend testnet funds and depend on external
+# verifier services, so they run in the nightly test-deploy-verify workflow.
+default-filter = "not test(/flaky_/) and not test(/deploy_verify_/)"
 
 [[profile.default.overrides]]
-filter = "test(/ext_integration|can_test_forge_std/)"
+filter = "test(/ext_integration/)"
 slow-timeout = { period = "5m", terminate-after = 4 }
 
+# The symbolic conformance and limits suites only do work with SYMBOLIC_CONFORMANCE and
+# SYMBOLIC_LIMITS set, as the nightly test-flaky workflow does; the stateful invariant cases there
+# take minutes in debug builds.
+[[profile.default.overrides]]
+filter = "test(/symbolic_conformance::|symbolic_limits::/)"
+slow-timeout = { period = "5m", terminate-after = 4 }
+
+# Integration-style CLI tests can exceed the default 90s timeout on slower
+# Windows, macOS, and ARM runners while shelling out to forge/solc/git.
+[[profile.default.overrides]]
+filter = "test(/(^|::)bind_event_module_name_shadowing$/) | test(/(^|::)bind_event_module_prefix_does_not_shadow_aliases$/) | test(/(^|::)can_bind_e2e$/) | test(/(^|::)test_clone_/) | test(/(^|::)can_deploy_and_simulate_25_txes_concurrently$/) | test(/(^|::)can_deploy_25_txes_concurrently_across_full_blocks$/) | test(/(^|::)can_deploy_25_txes_concurrently_with_interval_mining$/) | test(/(^|::)can_deploy_25_txes_concurrently_with_mixed_mining$/) | test(/(^|::)chisel_can_run_with_live_logs_flag$/) | test(/(^|::)session_wrapper_uses_project_config_for_cast_session$/)"
+slow-timeout = { period = "5m", terminate-after = 4 }
+
+[[profile.default.overrides]]
+filter = "test(/tempo_canary::/)"
+test-group = "tempo-canary"
+
+# Do not re-run so that `cargo cheats` is ran locally.
 [[profile.default.overrides]]
 filter = "package(foundry-cheatcodes-spec)"
 retries = 0
 
-[[profile.default.overrides]]
-filter = "package(chisel)"
-test-group = "chisel-serial"
+# Profile for running flaky tests (used by nightly CI and for local debugging)
+# Run with: cargo nextest run --profile flaky
+[profile.flaky]
+default-filter = "test(/flaky_/)"
+retries = { backoff = "exponential", count = 5, delay = "10s", jitter = true }
+slow-timeout = { period = "60s", terminate-after = 3 }
+
+# The fork smoke tests report an unreachable endpoint by skipping instead of failing, so keep
+# their output on success to show which chains a run actually exercised.
+[[profile.flaky.overrides]]
+filter = "test(/fork_chains::/)"
+success-output = "final"
+
+# The network read tests report an unreachable endpoint or an unusable block by skipping instead
+# of failing, so keep their output on success to show which networks a run actually exercised.
+[[profile.flaky.overrides]]
+filter = "test(/read_networks::/)"
+success-output = "final"
+
+# Profile for the on-chain deploy+verify tests (used by the nightly test-deploy-verify workflow).
+# Requires <NETWORK>_RPC_URL plus TESTNET_DEPLOYER_PRIVATE_KEY to do anything.
+# Run with: cargo nextest run --profile deploy-verify
+[profile.deploy-verify]
+default-filter = "test(/deploy_verify_/)"
+retries = 1
+# A deploy plus verifier round trip is minutes, not seconds.
+slow-timeout = { period = "120s", terminate-after = 5 }
+
+[[profile.deploy-verify.overrides]]
+filter = "test(/deploy_verify_/)"
+test-group = "deploy-verify"

.gitattributes

@@ -1,9 +1,13 @@
 crates/cheatcodes/assets/*.json linguist-generated
-testdata/cheats/Vm.sol linguist-generated
+testdata/utils/Vm.sol linguist-generated
 
 # See <https://git-scm.com/docs/gitattributes#_defining_a_custom_hunk_header>
 *.rs diff=rust
 crates/lint/testdata/* text eol=lf
+crates/lint/testdata/*.stderr whitespace=-blank-at-eof
+testdata/fixtures/**/* eol=lf
 
 dprint.json linguist-language=JSON-with-Comments
-.devcontainer/devcontainer.json linguist-language=JSON-with-Comments
+.devcontainer/devcontainer.json linguist-language=JSON-with-Comments
+
+.env.example linguist-language=Dotenv

.github/CODEOWNERS

@@ -1 +1 @@
-* @danipopes @klkvr @mattsse @grandizzy @yash-atreya @zerosnacks
+* @danipopes @mattsse @grandizzy @0xrusowsky @mablr @figtracer @stevencartavia

.github/CRATE_CHECKS_FAILURE_TEMPLATE.md

@@ -0,0 +1,10 @@
+---
+title: "bug: nightly crate-checks workflow failed"
+labels: P-normal, T-bug
+---
+
+The nightly crate-checks workflow has failed. Either one or more crates don't compile in isolation (`cargo hack check`), likely a missing dependency or feature flag masked by Cargo's workspace feature unification, or a unit test failed under default features, which regular CI never builds because it always enables `base` and `monad`.
+
+Check the [crate-checks workflow page]({{ env.WORKFLOW_URL }}) for details.
+
+This issue was raised by the workflow at `.github/workflows/crate-checks.yml`.

.github/DEPLOY_VERIFY_FAILURE_TEMPLATE.md

@@ -0,0 +1,14 @@
+---
+title: "bug: deploy + verify workflow failed"
+labels: P-normal, T-bug
+---
+
+The nightly on-chain deploy + verify workflow has failed. This exercises `forge create` followed by `forge verify-contract` against Hoodi, Sepolia, Base Sepolia, Arbitrum Sepolia, Monad testnet and Robinhood testnet, using Etherscan, Sourcify and Blockscout.
+
+The most common cause is the shared deployer running out of testnet funds. The deployer is `0x14459e92f32B68125525B5e3cdF3A239618e40D8`, held in the `FUNDED_TESTNET_PKEY` secret, and the workflow logs its balance on every network before running the tests. Monad testnet drains fastest, at roughly 0.08 MON per run. Top it up from a faucet to fix.
+
+Other likely causes are a testnet RPC being down, a verifier service being unavailable, or Etherscan rate limiting.
+
+Check the [deploy + verify workflow page]({{ env.WORKFLOW_URL }}) for details.
+
+This issue was raised by the workflow at `.github/workflows/test-deploy-verify.yml`.

.github/DEPLOY_VERIFY_REFUND_TEMPLATE.md

@@ -0,0 +1,20 @@
+---
+title: "chore: refund the testnet deploy+verify deployer"
+labels: P-normal, T-chore
+---
+
+The shared deployer for the nightly on-chain deploy + verify workflow is running low on at least one network. The tests may still be passing right now; this is raised early so the account can be topped up before they start failing.
+
+Refund `{{ env.DEPLOYER }}` on:
+
+```
+{{ env.LOW_NETWORKS }}
+```
+
+Each entry is `NETWORK=current(min threshold)`. Thresholds are set at roughly twenty more runs at the measured per-run burn, so there is room to act. Monad testnet drains fastest at about 0.08 MON per run; the L2s are effectively free and should only appear here if something has gone wrong.
+
+The key lives in the `FUNDED_TESTNET_PKEY` secret and holds testnet funds only. Public faucets cover every network involved.
+
+Check the [deploy + verify workflow page]({{ env.WORKFLOW_URL }}) for the full balance report.
+
+This issue was raised by the workflow at `.github/workflows/test-deploy-verify.yml`.

.github/FLAKY_TEST_FAILURE_TEMPLATE.md

@@ -0,0 +1,10 @@
+---
+title: "bug: flaky tests workflow failed"
+labels: P-normal, T-bug
+---
+
+The nightly flaky tests workflow has failed. This indicates external API rate limiting, RPC reliability issues, or other intermittent failures that may affect users.
+
+Check the [flaky tests workflow page]({{ env.WORKFLOW_URL }}) for details.
+
+This issue was raised by the workflow at `.github/workflows/test-flaky.yml`.