2024-06-03 06:17:12 -05:00
// Copyright 2024 The go-ethereum Authors
// This file is part of the go-ethereum library.
//
// The go-ethereum library is free software: you can redistribute it and/or modify
// it under the terms of the GNU Lesser General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
//
// The go-ethereum library is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with the go-ethereum library. If not, see <http://www.gnu.org/licenses/>.
package state
import (
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
"maps"
2024-06-03 06:17:12 -05:00
"github.com/ethereum/go-ethereum/common"
"github.com/ethereum/go-ethereum/core/types"
"github.com/ethereum/go-ethereum/trie/trienode"
2024-10-18 10:06:31 -05:00
"github.com/ethereum/go-ethereum/triedb"
2024-06-03 06:17:12 -05:00
)
// contractCode represents a contract code with associated metadata.
type contractCode struct {
hash common . Hash // hash is the cryptographic hash of the contract code.
blob [ ] byte // blob is the binary representation of the contract code.
}
// accountDelete represents an operation for deleting an Ethereum account.
type accountDelete struct {
address common . Address // address is the unique account identifier
origin [ ] byte // origin is the original value of account data in slim-RLP encoding.
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
storages map [ common . Hash ] [ ] byte // storages stores mutated slots, the value should be nil.
2024-06-03 06:17:12 -05:00
storagesOrigin map [ common . Hash ] [ ] byte // storagesOrigin stores the original values of mutated slots in prefix-zero-trimmed RLP format.
}
// accountUpdate represents an operation for updating an Ethereum account.
type accountUpdate struct {
address common . Address // address is the unique account identifier
data [ ] byte // data is the slim-RLP encoded account data.
origin [ ] byte // origin is the original value of account data in slim-RLP encoding.
code * contractCode // code represents mutated contract code; nil means it's not modified.
storages map [ common . Hash ] [ ] byte // storages stores mutated slots in prefix-zero-trimmed RLP format.
storagesOrigin map [ common . Hash ] [ ] byte // storagesOrigin stores the original values of mutated slots in prefix-zero-trimmed RLP format.
}
// stateUpdate represents the difference between two states resulting from state
// execution. It contains information about mutated contract codes, accounts,
// and storage slots, along with their original values.
type stateUpdate struct {
originRoot common . Hash // hash of the state before applying mutation
root common . Hash // hash of the state after applying mutation
accounts map [ common . Hash ] [ ] byte // accounts stores mutated accounts in 'slim RLP' encoding
accountsOrigin map [ common . Address ] [ ] byte // accountsOrigin stores the original values of mutated accounts in 'slim RLP' encoding
storages map [ common . Hash ] map [ common . Hash ] [ ] byte // storages stores mutated slots in 'prefix-zero-trimmed' RLP format
storagesOrigin map [ common . Address ] map [ common . Hash ] [ ] byte // storagesOrigin stores the original values of mutated slots in 'prefix-zero-trimmed' RLP format
codes map [ common . Address ] contractCode // codes contains the set of dirty codes
nodes * trienode . MergedNodeSet // Aggregated dirty nodes caused by state changes
}
// empty returns a flag indicating the state transition is empty or not.
func ( sc * stateUpdate ) empty ( ) bool {
return sc . originRoot == sc . root
}
// newStateUpdate constructs a state update object, representing the differences
// between two states by performing state execution. It aggregates the given
// account deletions and account updates to form a comprehensive state update.
func newStateUpdate ( originRoot common . Hash , root common . Hash , deletes map [ common . Hash ] * accountDelete , updates map [ common . Hash ] * accountUpdate , nodes * trienode . MergedNodeSet ) * stateUpdate {
var (
accounts = make ( map [ common . Hash ] [ ] byte )
accountsOrigin = make ( map [ common . Address ] [ ] byte )
storages = make ( map [ common . Hash ] map [ common . Hash ] [ ] byte )
storagesOrigin = make ( map [ common . Address ] map [ common . Hash ] [ ] byte )
codes = make ( map [ common . Address ] contractCode )
)
// Due to the fact that some accounts could be destructed and resurrected
// within the same block, the deletions must be aggregated first.
for addrHash , op := range deletes {
addr := op . address
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
accounts [ addrHash ] = nil
2024-06-03 06:17:12 -05:00
accountsOrigin [ addr ] = op . origin
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
if len ( op . storages ) > 0 {
storages [ addrHash ] = op . storages
}
2024-06-03 06:17:12 -05:00
if len ( op . storagesOrigin ) > 0 {
storagesOrigin [ addr ] = op . storagesOrigin
}
}
// Aggregate account updates then.
for addrHash , op := range updates {
// Aggregate dirty contract codes if they are available.
addr := op . address
if op . code != nil {
codes [ addr ] = * op . code
}
accounts [ addrHash ] = op . data
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
// Aggregate the account original value. If the account is already
// present in the aggregated accountsOrigin set, skip it.
2024-06-03 06:17:12 -05:00
if _ , found := accountsOrigin [ addr ] ; ! found {
accountsOrigin [ addr ] = op . origin
}
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
// Aggregate the storage mutation list. If a slot in op.storages is
// already present in aggregated storages set, the value will be
// overwritten.
2024-06-03 06:17:12 -05:00
if len ( op . storages ) > 0 {
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
if _ , exist := storages [ addrHash ] ; ! exist {
storages [ addrHash ] = op . storages
} else {
maps . Copy ( storages [ addrHash ] , op . storages )
}
2024-06-03 06:17:12 -05:00
}
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
// Aggregate the storage original values. If the slot is already present
// in aggregated storagesOrigin set, skip it.
2024-06-03 06:17:12 -05:00
if len ( op . storagesOrigin ) > 0 {
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
origin , exist := storagesOrigin [ addr ]
if ! exist {
2024-06-03 06:17:12 -05:00
storagesOrigin [ addr ] = op . storagesOrigin
core, triedb: remove destruct flag in state snapshot (#30752)
This pull request removes the destruct flag from the state snapshot to
simplify the code.
Previously, this flag indicated that an account was removed during a
state transition, making all associated storage slots inaccessible.
Because storage deletion can involve a large number of slots, the actual
deletion is deferred until the end of the process, where it is handled
in batches.
With the deprecation of self-destruct in the Cancun fork, storage
deletions are no longer expected. Historically, the largest storage
deletion event in Ethereum was around 15 megabytes—manageable in memory.
In this pull request, the single destruct flag is replaced by a set of
deletion markers for individual storage slots. Each deleted storage slot
will now appear in the Storage set with a nil value.
This change will simplify a lot logics, such as storage accessing,
storage flushing, storage iteration and so on.
2024-11-22 02:55:43 -06:00
} else {
for key , slot := range op . storagesOrigin {
if _ , found := origin [ key ] ; ! found {
origin [ key ] = slot
}
2024-06-03 06:17:12 -05:00
}
}
}
}
return & stateUpdate {
originRoot : types . TrieRootHash ( originRoot ) ,
root : types . TrieRootHash ( root ) ,
accounts : accounts ,
accountsOrigin : accountsOrigin ,
storages : storages ,
storagesOrigin : storagesOrigin ,
codes : codes ,
nodes : nodes ,
}
}
2024-10-18 10:06:31 -05:00
// stateSet converts the current stateUpdate object into a triedb.StateSet
// object. This function extracts the necessary data from the stateUpdate
// struct and formats it into the StateSet structure consumed by the triedb
// package.
func ( sc * stateUpdate ) stateSet ( ) * triedb . StateSet {
return & triedb . StateSet {
Accounts : sc . accounts ,
AccountsOrigin : sc . accountsOrigin ,
Storages : sc . storages ,
StoragesOrigin : sc . storagesOrigin ,
}
}