2017-04-04 17:16:29 -05:00
|
|
|
// Copyright 2016 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 misc
|
|
|
|
|
|
|
|
import (
|
|
|
|
"bytes"
|
|
|
|
"errors"
|
|
|
|
"math/big"
|
|
|
|
|
2024-03-22 12:53:53 -05:00
|
|
|
"github.com/ethereum/go-ethereum/core/tracing"
|
2017-04-04 17:16:29 -05:00
|
|
|
"github.com/ethereum/go-ethereum/core/types"
|
core/state: move state log mechanism to a separate layer (#30569)
This PR moves the logging/tracing-facilities out of `*state.StateDB`,
in to a wrapping struct which implements `vm.StateDB` instead.
In most places, it is a pretty straight-forward change:
- First, hoisting the invocations from state objects up to the statedb.
- Then making the mutation-methods simply return the previous value, so
that the external logging layer could log everything.
Some internal code uses the direct object-accessors to mutate the state,
particularly in testing and in setting up state overrides, which means
that these changes are unobservable for the hooked layer. Thus, configuring
the overrides are not necessarily part of the API we want to publish.
The trickiest part about the layering is that when the selfdestructs are
finally deleted during `Finalise`, there's the possibility that someone
sent some ether to it, which is burnt at that point, and thus needs to
be logged. The hooked layer reaches into the inner layer to figure out
these events.
In package `vm`, the conversion from `state.StateDB + hooks` into a
hooked `vm.StateDB` is performed where needed.
---------
Co-authored-by: Gary Rong <garyrong0905@gmail.com>
2024-10-23 01:03:36 -05:00
|
|
|
"github.com/ethereum/go-ethereum/core/vm"
|
2017-04-04 17:16:29 -05:00
|
|
|
"github.com/ethereum/go-ethereum/params"
|
|
|
|
)
|
|
|
|
|
|
|
|
var (
|
2020-05-25 03:21:28 -05:00
|
|
|
// ErrBadProDAOExtra is returned if a header doesn't support the DAO fork on a
|
2017-04-04 17:16:29 -05:00
|
|
|
// pro-fork client.
|
|
|
|
ErrBadProDAOExtra = errors.New("bad DAO pro-fork extra-data")
|
|
|
|
|
|
|
|
// ErrBadNoDAOExtra is returned if a header does support the DAO fork on a no-
|
|
|
|
// fork client.
|
|
|
|
ErrBadNoDAOExtra = errors.New("bad DAO no-fork extra-data")
|
|
|
|
)
|
|
|
|
|
|
|
|
// VerifyDAOHeaderExtraData validates the extra-data field of a block header to
|
|
|
|
// ensure it conforms to DAO hard-fork rules.
|
|
|
|
//
|
|
|
|
// DAO hard-fork extension to the header validity:
|
2022-09-10 06:25:40 -05:00
|
|
|
//
|
|
|
|
// - if the node is no-fork, do not accept blocks in the [fork, fork+10) range
|
|
|
|
// with the fork specific extra-data set.
|
|
|
|
// - if the node is pro-fork, require blocks in the specific range to have the
|
|
|
|
// unique extra-data set.
|
2017-04-04 17:16:29 -05:00
|
|
|
func VerifyDAOHeaderExtraData(config *params.ChainConfig, header *types.Header) error {
|
|
|
|
// Short circuit validation if the node doesn't care about the DAO fork
|
|
|
|
if config.DAOForkBlock == nil {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
// Make sure the block is within the fork's modified extra-data range
|
|
|
|
limit := new(big.Int).Add(config.DAOForkBlock, params.DAOForkExtraRange)
|
|
|
|
if header.Number.Cmp(config.DAOForkBlock) < 0 || header.Number.Cmp(limit) >= 0 {
|
|
|
|
return nil
|
|
|
|
}
|
2017-06-12 07:45:17 -05:00
|
|
|
// Depending on whether we support or oppose the fork, validate the extra-data contents
|
2017-04-04 17:16:29 -05:00
|
|
|
if config.DAOForkSupport {
|
|
|
|
if !bytes.Equal(header.Extra, params.DAOForkBlockExtra) {
|
|
|
|
return ErrBadProDAOExtra
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
if bytes.Equal(header.Extra, params.DAOForkBlockExtra) {
|
|
|
|
return ErrBadNoDAOExtra
|
|
|
|
}
|
|
|
|
}
|
|
|
|
// All ok, header has the same extra-data we expect
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// ApplyDAOHardFork modifies the state database according to the DAO hard-fork
|
|
|
|
// rules, transferring all balances of a set of DAO accounts to a single refund
|
|
|
|
// contract.
|
core/state: move state log mechanism to a separate layer (#30569)
This PR moves the logging/tracing-facilities out of `*state.StateDB`,
in to a wrapping struct which implements `vm.StateDB` instead.
In most places, it is a pretty straight-forward change:
- First, hoisting the invocations from state objects up to the statedb.
- Then making the mutation-methods simply return the previous value, so
that the external logging layer could log everything.
Some internal code uses the direct object-accessors to mutate the state,
particularly in testing and in setting up state overrides, which means
that these changes are unobservable for the hooked layer. Thus, configuring
the overrides are not necessarily part of the API we want to publish.
The trickiest part about the layering is that when the selfdestructs are
finally deleted during `Finalise`, there's the possibility that someone
sent some ether to it, which is burnt at that point, and thus needs to
be logged. The hooked layer reaches into the inner layer to figure out
these events.
In package `vm`, the conversion from `state.StateDB + hooks` into a
hooked `vm.StateDB` is performed where needed.
---------
Co-authored-by: Gary Rong <garyrong0905@gmail.com>
2024-10-23 01:03:36 -05:00
|
|
|
func ApplyDAOHardFork(statedb vm.StateDB) {
|
2017-04-04 17:16:29 -05:00
|
|
|
// Retrieve the contract to refund balances into
|
|
|
|
if !statedb.Exist(params.DAORefundContract) {
|
|
|
|
statedb.CreateAccount(params.DAORefundContract)
|
|
|
|
}
|
|
|
|
|
|
|
|
// Move every DAO account and extra-balance account funds into the refund contract
|
|
|
|
for _, addr := range params.DAODrainList() {
|
core/state: move state log mechanism to a separate layer (#30569)
This PR moves the logging/tracing-facilities out of `*state.StateDB`,
in to a wrapping struct which implements `vm.StateDB` instead.
In most places, it is a pretty straight-forward change:
- First, hoisting the invocations from state objects up to the statedb.
- Then making the mutation-methods simply return the previous value, so
that the external logging layer could log everything.
Some internal code uses the direct object-accessors to mutate the state,
particularly in testing and in setting up state overrides, which means
that these changes are unobservable for the hooked layer. Thus, configuring
the overrides are not necessarily part of the API we want to publish.
The trickiest part about the layering is that when the selfdestructs are
finally deleted during `Finalise`, there's the possibility that someone
sent some ether to it, which is burnt at that point, and thus needs to
be logged. The hooked layer reaches into the inner layer to figure out
these events.
In package `vm`, the conversion from `state.StateDB + hooks` into a
hooked `vm.StateDB` is performed where needed.
---------
Co-authored-by: Gary Rong <garyrong0905@gmail.com>
2024-10-23 01:03:36 -05:00
|
|
|
balance := statedb.GetBalance(addr)
|
|
|
|
statedb.AddBalance(params.DAORefundContract, balance, tracing.BalanceIncreaseDaoContract)
|
|
|
|
statedb.SubBalance(addr, balance, tracing.BalanceDecreaseDaoAccount)
|
2017-04-04 17:16:29 -05:00
|
|
|
}
|
|
|
|
}
|