* interop: dataflow refactor v2
Co-authored-by: Axel Kingsley <axel.kingsley@gmail.com>

* interop: many refactor-fixes, make action test pass

* op-e2e: fix lint

* op-service: RPC event-stream util, for subscription and polling flexibility

* op-node: update interop managed-mode RPC events to use RPC stream util

* op-supervisor: subscribe or poll for managed-node events

* op-service: stream fallback util

* op-node: fix interop managed L1 traversal

* op-supervisor: enable action tests to pull events

* op-e2e: fix interop action test

* lint

* fix unit test

* Fixes from E2E tests
- Reset Engine even when in Managed Mode
- Use correct wrapped subscription
- Export wrapped subscription type
- Close Controllers on exit

* Controller tests and fixes

---------
Co-authored-by: Axel Kingsley <axel.kingsley@gmail.com>

Move the detection logic to a separate package, and make it testable.
Also make room for more detection mechanisms down the road if needed.

Dump a few potentially interesting addresses as part of the L1 manifest.
In particular, superchain addresses.

Implementation addresses are provided as well, as they might come in
handy for debugging purposes.

Output now looks like:
...
  "l1": {
    "name": "Ethereum",
    "nodes": [
      {
        "cl": "http://127.0.0.1:50973",
        "el": "http://127.0.0.1:50965"
      }
    ],
    "addresses": {
      "delayedWETHImpl": "0x6cc791cd89220c47952885782156e5e8f2833063",
      "disputeGameFactoryImpl": "0x256fa44786f5b9aa47f13639b97a52cbbb8d3b6e",
      "l1CrossDomainMessengerImpl": "0xe70dae11d895c2e508e7d1c0c91dd0f3e4e971c3",
      "l1ERC721BridgeImpl": "0x5a0242103310c7992773430e790c142b7e94ef3a",
      "l1StandardBridgeImpl": "0x8eb57e8ca6e1e3216b4293cc37d621a43c17ec40",
      "mipsSingleton": "0xb5322da185af39b53f8d3cbf40636eb3f1b527f2",
      "opcm": "0xf0f6e276962a776112511c4ea74ad12b4e44cd6b",
      "optimismMintableERC20FactoryImpl": "0x5f554a3eabcc8e2055040d563ef4910e8bacff8d",
      "optimismPortalImpl": "0x9d1da1fef40e2b5f44ed193bd88f1d3ee4a31cc5",
      "preimageOracleSingleton": "0x31502454e4b07ab6f35216fd734aafd816a06110",
      "protocolVersionsImpl": "0xba337ce3e690fdd01b1a830404e8caaae22a0638",
      "protocolVersionsProxy": "0xf2749e312b43529cb35a91e355919a376bd22ce3",
      "proxyAdmin": "0xed3b4bf7e17e47dac37d7bb913196e192dcaf748",
      "superchainConfigImpl": "0xcf99c17529cc22c39551547e323ed9dda6841734",
      "superchainConfigProxy": "0x329cf899464ba580bf047f4b886db342c602f579",
      "systemConfigImpl": "0x5d58414e85fc12d343eb3445dd7417c483d939a9"
    }
  },
...

On Mac and Windows, we should be relatively safe using
host.docker.internal (feature of Docker Desktop)

On Linux, try to find the docker bridge and infer the IP from
there.

* feat: Use encodeCall for type safety

A very common issue (both from experience and observation) is
failing to correctly encode the initializer arguments in
`encodeSystemConfigInitializer()`. This fixes that.

I believe that at one point we needed to be able to pass the 4 bytes
selector in as a string, but that no longer seems to be the case.

* semver

* feat: expand use of encodeCall to rest of OPCM

* semver lock

* cannon arch: move derivable stuff to arch.go

* address comments

This is a code cleanup change.

This moves all the code built on top of Kurtosis SDK into separate
packages for better clarity.

* cannon: Add new state version and start migrating

* cannon: Add new test state for version 4

* cannon: Update cannon commands to use new state version

* cannon: Update cannon embeds command

* cannon: Update Dockerfile to include cannon version 3 binary

- fix the op-challenger image build, as currently
  ops/docker/op-stack-go/Dockerfile defaults to a non-existing tag.

- make it easier to point to an alternate kurtosis package (like a
local for for example)

Adjust the definition, based on latest changes in kurtosis
optimism-package.

For the purpose of seeding op-challenger, we need only the proof files.

This change adds a separate target that outputs only these.

Unfortunately, docker outputs can be pretty slow, so avoiding dumping
the heavier binaries makes a significant differente performance-wise.

Now that https://github.com/ethpandaops/optimism-package/pull/116
defines a cannon_prestates_url for each challenger instance, we better
skip rebuilding the same thing multiple times.

Now that we don't use the kurtosis cli, there's no reason to go
through the filesystem to pass a configuration file.

This change reimplements run over the kurtosis SDK instead of shelling
out to the CLI tool, which fixes potential consistency problems with
other uses of the SDK.

Additionally, we split the endpoint detection logic into a separate
entity (will make it a separate package a bit later), and improve the
host handling part by no longer assuming reachability on localhost
(implicitly assuming Docker backend). This is a step toward supporting
k8s backend transparently.

* feat: remove enableLegacyContracts

* feat: remove setUseFaultProofs

* feat: Remove useFaultProofs branch in Deploy._run()

* gas snapshot

* feat: remove useFaultProofs

* Revert "op-batcher: Fix concurrent map write (#13527)"

This reverts commit 90435d07.

* lock channelMgrMutex during recordFailedDARequest

* rename / export pruneSafeBlocks and pruneChannels

mtx on channel_manager too

This prepares the ground for op-challenger needing a URL locator
serving prestate proof files.

A {{localPrestate}} placeholder will expand to a URL that's usable by
op-challenger.

* [op-program] Update releases.json

* [op-program] Tweak verify formatting

This ties together the various capabilities in pkg/ and orchestrates them. The phases are:
- build local artifacts per input template specification
- put them where they can be accessed at runtime by kurtosis
- run the deployment
- collect useful information and output it for downstream consumption

Also provide sample devnet definitions

Those are just starting points. We'll need to come up with definitions
that actually make sense.

Note that there is a temporary workaround for op-deployer image:

We need http locator support, which has been merged into op-deployer,
but the current version at HEAD doesn't quite work with kurtosis yet.

We'll fix that separately, at which point we'll be able to point to a
localDockerBuild of "op-deployer" just as well, if we want to.

* ct/scripts/ChainAssertions: add require revert message
Signed-off-by: jsvisa <delweng@gmail.com>

* ct/scripts/deploy/Deploy: add require revert message
Signed-off-by: jsvisa <delweng@gmail.com>

* ct/scripts/deploy/DeployOwnership: add require revert message
Signed-off-by: jsvisa <delweng@gmail.com>

* ct/scripts/deploy/DeployPeriphery: add require revert message
Signed-off-by: jsvisa <delweng@gmail.com>

* feat(semgrep): enable for all solidity files, except WETH9
Signed-off-by: jsvisa <delweng@gmail.com>

* fix require issues
Signed-off-by: jsvisa <delweng@gmail.com>

* fix(semgrep): run just semgrep to fix the require rules
Signed-off-by: jsvisa <delweng@gmail.com>

---------
Signed-off-by: jsvisa <delweng@gmail.com>

Co-authored-by: Tarun Khasnavis <tarunkhasnavis@Taruns-MacBook-Pro.local>

Added in extra dependency details to the getting started versions script to point people to where to learn more. (#13540)

* attempt...

* fixes

* fix checks

* fix kontrol build

* update DeploymentSummaryFaultProofs kontrol hash

* fixes

* undo unnecessary change

* feat: Reduce diff and usage of OptimismPortal2

* semver

* fix: init test

---------
Co-authored-by: Maurelian <maurelian@protonmail.ch>

* op-proposer: do not propose if outputRoot is the same as last proposed game

* fixed porposer tests

* PR comments

* Fix log message.

---------
Co-authored-by: Adrian Sutton <adrian@symphonious.net>
Co-authored-by: Adrian Sutton <adrian@oplabs.co>

This handles deploying the kurtosis enclave according to spec, and
then stitching together the relevant information to be transmitted for
downstream consumption.