Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Update to geth 1.13 #1

Merged
merged 16 commits into from
Mar 26, 2024
Merged

feat: Update to geth 1.13 #1

merged 16 commits into from
Mar 26, 2024

Conversation

amaury1093
Copy link

@amaury1093 amaury1093 commented Mar 26, 2024

Closes: #XXX

Update geth to use 1.13.5.

To make sure I didn't forget anything that Zama did (they updated geth 1.10 to 1.13 on SDK 0.46), I used a git diff tool (Git Tree on VSCode) to compare the following commits on zbc-ethermint:

https://github.com/Inco-fhevm/zbc-ethermint/commit/9ebc339734b9cd1ba59b36942b71da94b4962382 .. https://github.com/Inco-fhevm/zbc-ethermint/commit/0a736a36bff125b559aaa36d2b08d27be80c8033

and make sure all those changes are reflected in this PR.

Once this is merged, there's a PR to update on inco-monorepo: https://github.com/Inco-fhevm/inco-monorepo/pull/13

Description


For contributor use:

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer

For admin use:

  • Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
  • Reviewers assigned
  • Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

@amaury1093 amaury1093 marked this pull request as ready for review March 26, 2024 13:49
Copy link

@kenta-mori3322 kenta-mori3322 left a comment

Choose a reason for hiding this comment

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

@amaury1093
I see that the latest go ethereum version is v1.13.14. Is there any specific reason to use v1.13.5? Rest of the stuff would be looking like a code diff using tools.

@amaury1093
Copy link
Author

I see that the latest go ethereum version is v1.13.14. Is there any specific reason to use v1.13.5?

Main reason is to keep exactly the version that Zama uses: https://docs.zama.ai/fhevm-go/getting-started/integration.


I also tried updating to latest version, but got errors:

../../../go/pkg/mod/github.com/ethereum/go-ethereum@v1.13.14/crypto/kzg4844/kzg4844_gokzg.go:52:49: cannot use (gokzg4844.Blob)(blob) (value of type gokzg4844.Blob) as *gokzg4844.Blob value in argument to context.BlobToKZGCommitment
../../../go/pkg/mod/github.com/ethereum/go-ethereum@v1.13.14/crypto/kzg4844/kzg4844_gokzg.go:64:47: cannot use (gokzg4844.Blob)(blob) (value of type gokzg4844.Blob) as *gokzg4844.Blob value in argument to context.ComputeKZGProof
../../../go/pkg/mod/github.com/ethereum/go-ethereum@v1.13.14/crypto/kzg4844/kzg4844_gokzg.go:86:44: cannot use (gokzg4844.Blob)(blob) (value of type gokzg4844.Blob) as *gokzg4844.Blob value in argument to context.ComputeBlobKZGProof
../../../go/pkg/mod/github.com/ethereum/go-ethereum@v1.13.14/crypto/kzg4844/kzg4844_gokzg.go:97:36: cannot use (gokzg4844.Blob)(blob) (value of type gokzg4844.Blob) as *gokzg4844.Blob value in argument to context.VerifyBlobKZGProof

I can try to fix these errors, but I also think it's fine to pin v1.13.5. What do you think? Is there any big improvement in v1.13.14 that you'd like to include?

@kenta-mori3322
Copy link

kenta-mori3322 commented Mar 26, 2024

@amaury1093 make sense. Already started extacting the core vm from v1.13.14. LGTM. Approved.

@amaury1093 amaury1093 merged commit fd6c811 into develop Mar 26, 2024
19 checks passed
@amaury1093 amaury1093 deleted the am/geth1-13 branch March 26, 2024 17:03
amaury1093 added a commit that referenced this pull request Apr 5, 2024
* update geth

* fix

* use zbc geth

* fix pebble

* Fix statedb

* fix some

* fix x/evm

* make it build

* skip CI

* Fix test name

* Run some tests

* run actions

* skip integration tests

* skip failing test

* enable cancun
amaury1093 added a commit that referenced this pull request Apr 5, 2024
* update geth

* fix

* use zbc geth

* fix pebble

* Fix statedb

* fix some

* fix x/evm

* make it build

* skip CI

* Fix test name

* Run some tests

* run actions

* skip integration tests

* skip failing test

* enable cancun
amaury1093 added a commit that referenced this pull request Apr 15, 2024
* feat: Update to geth 1.13 (#1)

* update geth

* fix

* use zbc geth

* fix pebble

* Fix statedb

* fix some

* fix x/evm

* make it build

* skip CI

* Fix test name

* Run some tests

* run actions

* skip integration tests

* skip failing test

* enable cancun

* feat: Add RPC client for EVM methods

* wip

* Implement basic server and client

* remove useless interface

* Rename

* comments

* chore: add leftovergas to args

* cliean code

* fix build

* fix

* fixes

* chore: remove statedb in ethermint and change it to be rpc call

* Small changes and renames

---------

Co-authored-by: kenta-mori3322 <kenta.mori32@gmail.com>
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.

3 participants