chore(deps): pin signet-sdk to commit before larger update

[Evalir]

For the current PRs to work without a huge rebase, we need to pin signet-sdk to the commit before what's in main, to use the old deps.

[Evalir]

• chore(deps): pin signet-sdk to commit before larger update #95 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[dylanlott]

My PR depends on a branch in the SDK dylan/block-number though, so the pin will need to contain those changes.

[dylanlott]

🎀 Graphite made me write something 🦀

[Evalir]

uhhh that's kinda tough. That means we'll need to update deps and all open PRs will need to rebase, which will be painful.

Any workaround or will y'all eat the bugs?

[Evalir]

Yeah, looking at the open PRs, i think it's best to:

• merge this PR as is
• merge prestwich's PRs
• update to newer sdk/alloy/trevm/reth
• merge your PR

[dylanlott]

My PR is stacked on @prestwich PRs already, so it would be better to stack the builder changes for revm / alloy on top of my submit refactors.

So instead we should:

• Close this PR
• Merge the env and cache integration PRs
• Merge my submit refactors, keeping the signet-sdk dep pointed at dylan/block-number
• Update alloy / revm versions, and fix the bugs that incurs and then set the sdk branch back to main

This will allow alloy and revm update work to occur simultaneously with ongoing submit and simulation debugging.

[prestwich]

main is currently broken. so fixing main is the first priority. I vote for merging this, then restacking the open PRs

[prestwich]

to be clearer, this PR restores the status quo, ie. It explicitly depends on a pre-change sdk commit. So it won't require any changes to open PRs

my preferred is

• merge this
• all open prs
• updates

[Evalir]

ya my point with this pr is to restore status quo—we don't want to merge the ongoing work with red CI

[prestwich]

merging this to unblock the current PRs