Update Astria-geth to use geth 1.14.3 #21

bharath-123 · 2024-05-29T16:42:30Z

This PR rebases astria-geth on top of geth 1.14.3. Below are the main changes which affect astria-geth:

There seems to be an overall shift in the Geth code to prefer uint256.NewInt over big.NewInt. There are some places in our codebase where I had to typecast bigInt to uint256. But this usage also seems to be pretty inconsistent overall. I suspect as geth updates, most of the codebase will eventually use uint256.
The block building process under the miner directory used to have a worker struct in pre 1.14 geth. The payloadBuilding process was as method on the worker struct. With geth 1.14 there is a major refactor to simplify the codebase by removing the worker struct. Now we need to define all the methods under the Miner struct. This required some modifications to fillAstriaTransactions and commitAstriaTransactions to be implemented on the Miner struct.
Files Changed
miner/payload_building.go
miner/worker.go
Methods like AddBalance and SubBalance which update the balance of the user in the stateDB now requires to add an extra parameter indicating the reason of change of balance. This is used for live tracing introduced in geth 1.14. This is basically an enum. I added a new value called BalanceIncreaseAstriaDepositTx which indicates a balance increase due to an astria deposit tx.
Files Changed:
core/state_transition.go
tracing/hooks.go
Geth re-worked their testing infra. Integration tests use a SimulatedBackend which mocked the geth RPC. It simulates api calls such as sendTransaction. Pre geth 1.14, when sendTransaction was called with SimulatedBackend, txs bypassed the mempool and were directly added to the block. Post geth 1.14, this is not the case anymore and the txs are sent to the mempool. This breaks certain tests for us, since we rely on txs to come from the Execution API. I have commented out the tests for now but it ll be worth adding a simulated backend which bypasses the tx for our purposes. It ll be useful to test certain codepaths.
The following tests have been commented out:
a. TestWaitDeployed
b. TestGolangBindings
c. TestEthClient/AtFunctions
d. TestForkResendTx

Testing: make test runs without problems. I deployed this astria-evm locally using the monorepo charts and was able to run spamooor scenarios successfully against it.

bharath-123 · 2024-06-04T14:36:11Z

grpc/execution/server.go

-	if merger := eth.Merger(); !merger.PoSFinalized() {
-		merger.FinalizePoS()
-	}


There is some legacy code being removed in geth.

ethereum/go-ethereum#29169

bharath-123 · 2024-06-04T14:36:46Z

grpc/execution/server_test.go

-	require.True(t, balanceDiff.Cmp(big.NewInt(1000000000000000000)) == 0, "Chain destination address balance is not correct")
+	balanceDiff := new(uint256.Int).Sub(chainDestinationAddressBalanceAfter, chainDestinationAddressBalanceBefore)
+	fmt.Printf("Balance diff: %s\n", balanceDiff.String())
+	require.True(t, balanceDiff.Cmp(uint256.NewInt(1000000000000000000)) == 0, "Chain destination address balance is not correct")


examples of some changes to uint256.Int. This is because the stateDB is now returning only uint256s.

bharath-123 · 2024-06-04T14:42:49Z

core/state_transition.go

@@ -364,7 +381,7 @@ func (st *StateTransition) preCheck() error {
 func (st *StateTransition) TransitionDb() (*ExecutionResult, error) {
 	// if this is a deposit tx, we only need to mint funds and no gas is used.
 	if st.msg.IsDepositTx {
-		st.state.AddBalance(st.msg.From, st.msg.Value)
+		st.state.AddBalance(st.msg.From, uint256.MustFromBig(st.msg.Value), tracing.BalanceIncreaseAstriaDepositTx)


example of requirement of uint256 and adding tracing reason

bharath-123 · 2024-06-04T14:43:17Z

core/state_transition.go


 		// collect base fee instead of burn
 		if rules.IsLondon && st.evm.Context.Coinbase.Cmp(common.Address{}) != 0 {
 			baseFee := new(big.Int).SetUint64(st.gasUsed())
 			baseFee.Mul(baseFee, st.evm.Context.BaseFee)
-			st.state.AddBalance(st.evm.Context.Coinbase, baseFee)
+			st.state.AddBalance(st.evm.Context.Coinbase, uint256.MustFromBig(baseFee), tracing.BalanceIncreaseRewardTransactionFee)


Update from big.int to uint256

bharath-123 · 2024-06-04T16:24:26Z

miner/payload_building.go

@@ -175,7 +176,10 @@ func (payload *Payload) ResolveFull() *engine.ExecutionPayloadEnvelope {
 }

 // buildPayload builds the payload according to the provided parameters.
-func (w *worker) buildPayload(args *BuildPayloadArgs) (*Payload, error) {
+func (miner *Miner) buildPayload(args *BuildPayloadArgs) (*Payload, error) {


key change: buildPayload is now based on Miner rather than worker.

bharath-123 · 2024-06-04T16:25:59Z

miner/worker.go

@@ -20,57 +20,18 @@ import (
 	"errors"


the worker.go file is now very simplified.

joroshiba · 2024-06-10T15:50:33Z

I think we might need some fresh updates after Elizabeth PR merge, but otherwise LGTM

Co-authored-by: Felix Lange <[email protected]>

* node: fix test if directory already exists * node: remove test

…tion (#29169) * eth: drop support for forward sync triggers and head block packets * consensus, eth: enforce always merged network * eth: fix tx looper startup and shutdown * cmd, core: fix some tests * core: remove notion of future blocks * core, eth: drop unused methods and types

bump pebble

EIP-1559 burns the base fee. This doesn't make sense for rollups. The set fee recipient should collect it.

.github/workflows/pages.yaml

* main: fix: update with new asset proto (#34) feat: support bech32 addresses (#30) fix: Ensure all txs are removed from mempool when block building is interrupted (#29) disallow users from sending deposit txs and blob txs via the rpc (#24) Update Astria-geth to use geth 1.14.3 (#21)

bharath-123 force-pushed the bharath/update-to-1.14 branch 2 times, most recently from 4b8ecbe to b757f5b Compare May 30, 2024 10:45

bharath-123 changed the title ~~Update to geth 1.14~~ Update Astria-geth to use geth 1.14 May 30, 2024

bharath-123 marked this pull request as ready for review May 30, 2024 11:10

bharath-123 requested review from joroshiba, mycodecrafting and noot as code owners May 30, 2024 11:10

Base automatically changed from bharath/add-execution-server-tests to main May 31, 2024 06:25

bharath-123 force-pushed the bharath/update-to-1.14 branch 4 times, most recently from 2b28ac2 to 1fbd448 Compare June 4, 2024 14:19

bharath-123 commented Jun 4, 2024

View reviewed changes

miner/worker.go

@@ -20,57 +20,18 @@ import (

"errors"

Copy link

Contributor Author

bharath-123 Jun 4, 2024

Choose a reason for hiding this comment

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

the worker.go file is now very simplified.

undefinedor and others added 11 commits June 10, 2024 22:19

rpc: remove deprecated method "Notifier.Closed" (#29162)

f57c74a

rlp: using unsafe.Slice instead of SliceHeader (#29067)

9b8cc25

Co-authored-by: Felix Lange <[email protected]>

core: remove useless assignments (#29065)

4e0560a

node: remove test which doesn't do a lot (#29159)

20bac3f

* node: fix test if directory already exists * node: remove test

go.mod: bump pebble db to official release (#29038)

7c92378

bump pebble

internal/ethapi: delete needless error check (#29127)

c400dda

accounts/usbwallet: revert #28945 (#29175)

c39ab8e

rpc: add more test cases for arg types (#29006)

e2829d5

accounts/usbwallet: update hid library (#29176)

1772350

accounts: remove deprecated function NewPlaintextKeyStore (#29171)

d6bf595

bharath-123 added 15 commits June 10, 2024 22:19

updates

464e100

txpool fixes, remove v1alpha1, use forkchoice

4572f89

some cleanup

d4d13bc

think it's good

ea3c033

chore: add some metrics specifically around astria tx execution

2570221

small refactor

7fe7a8a

feat: update protos, config for fees, updated bridging (#1)

63a8f8f

collect the base fee instead of burning it (#5)

6a0a2e2

EIP-1559 burns the base fee. This doesn't make sense for rollups. The set fee recipient should collect it.

add unit tests for execution grpc server

599d715

fix tracer test

816f273

fix tests

382432b

fix merge conflicts in github workflows

771eeba

fix tests

e00d4fd

remove i386 tests

4b3988d

minor fixes

14a96f6

bharath-123 force-pushed the bharath/update-to-1.14 branch from e8ceb69 to 14a96f6 Compare June 10, 2024 17:24

bharath-123 changed the title ~~Update Astria-geth to use geth 1.14~~ Update Astria-geth to use geth 1.14.0 Jun 11, 2024

chore: update forkdiff base to go-ethereum-1.14

a30fd3d

bharath-123 changed the title ~~Update Astria-geth to use geth 1.14.0~~ Update Astria-geth to use geth 1.14.3 Jun 11, 2024

bharath-123 and others added 3 commits June 11, 2024 17:26

minor fix

a13be6d

update forkdiff base to v1.14.3

d82e19a

fix minor merge conflicts

5f9724b

bharath-123 force-pushed the bharath/update-to-1.14 branch from a7ab4e4 to 5f9724b Compare June 11, 2024 13:48

joroshiba reviewed Jun 12, 2024

View reviewed changes

.github/workflows/pages.yaml Show resolved Hide resolved

joroshiba approved these changes Jun 19, 2024

View reviewed changes

joroshiba merged commit 2b8a8ee into main Jun 20, 2024

joroshiba deleted the bharath/update-to-1.14 branch June 20, 2024 15:58

SuperFluffy restored the bharath/update-to-1.14 branch April 30, 2025 12:57

SuperFluffy deleted the bharath/update-to-1.14 branch May 5, 2025 14:21

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update Astria-geth to use geth 1.14.3 #21

Update Astria-geth to use geth 1.14.3 #21

Uh oh!

bharath-123 commented May 29, 2024 •

edited

Loading

Uh oh!

bharath-123 Jun 4, 2024

Uh oh!

bharath-123 Jun 11, 2024

Uh oh!

bharath-123 Jun 4, 2024

Uh oh!

bharath-123 Jun 4, 2024

Uh oh!

bharath-123 Jun 4, 2024

Uh oh!

bharath-123 Jun 4, 2024

Uh oh!

bharath-123 Jun 4, 2024

Uh oh!

joroshiba commented Jun 10, 2024

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

78 participants

Update Astria-geth to use geth 1.14.3 #21

Update Astria-geth to use geth 1.14.3 #21

Uh oh!

Conversation

bharath-123 commented May 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bharath-123 Jun 4, 2024

Choose a reason for hiding this comment

Uh oh!

bharath-123 Jun 11, 2024

Choose a reason for hiding this comment

Uh oh!

bharath-123 Jun 4, 2024

Choose a reason for hiding this comment

Uh oh!

bharath-123 Jun 4, 2024

Choose a reason for hiding this comment

Uh oh!

bharath-123 Jun 4, 2024

Choose a reason for hiding this comment

Uh oh!

bharath-123 Jun 4, 2024

Choose a reason for hiding this comment

Uh oh!

bharath-123 Jun 4, 2024

Choose a reason for hiding this comment

Uh oh!

joroshiba commented Jun 10, 2024

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

78 participants

bharath-123 commented May 29, 2024 •

edited

Loading