Skip to content

Conversation

JoeGruffins
Copy link
Member

This should let us hook up base for simnet. I think it's a good alternative to using --dev anyway as it is closer to eth mainnet.

@JoeGruffins JoeGruffins force-pushed the basesimnet branch 2 times, most recently from be4b82e to ab1a8e6 Compare July 11, 2025 12:56
@JoeGruffins JoeGruffins marked this pull request as ready for review July 14, 2025 08:12
@martonp
Copy link
Collaborator

martonp commented Jul 14, 2025

How will you hook up base on top of this?

@JoeGruffins
Copy link
Member Author

JoeGruffins commented Jul 15, 2025

How will you hook up base on top of this?

Base needs access to the consensus node and execution node to run. I'm not sure yet if it will run without problems but it does run on top of this. However it requires ignoring some starting validation, so we will need to fork https://github.com/ethereum-optimism/optimism and comment out a couple lines. Then just point it at the endpoints.

With the --dev flag we are not getting the consensus node currently you know.

@martonp
Copy link
Collaborator

martonp commented Jul 15, 2025

Base needs access to the consensus node and execution node to run. I'm not sure yet if it will run without problems but it does run on top of this. However it requires ignoring some starting validation, so we will need to fork https://github.com/ethereum-optimism/optimism and comment out a couple lines. Then just point it at the endpoints.

OK that makes sense, I think this is good.

I'm getting this error when running the harness:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@ethereumjs/util' imported from /Users/marci/git/dcrdex/dex/testing/eth_kurtosis/sign.js
    at new NodeError (node:internal/errors:405:5)
    at packageResolve (node:internal/modules/esm/resolve:916:9)
    at moduleResolve (node:internal/modules/esm/resolve:973:20)
    at defaultResolve (node:internal/modules/esm/resolve:1206:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:404:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:373:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:250:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:39)
    at link (node:internal/modules/esm/module_job:75:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Is this not happening for you? I think you need to install these packages within the docker containers.

@JoeGruffins
Copy link
Member Author

JoeGruffins commented Jul 16, 2025

@martonp did you run npm install in the harness dir first?

@JoeGruffins
Copy link
Member Author

Actually maybe I have that installed globally? I think I need to add it to the package.json, doing that

@JoeGruffins
Copy link
Member Author

@JoeGruffins
Copy link
Member Author

Actually adding base on top of this may be more complicated than I thought.

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