- 07 Aug, 2023 1 commit
-
-
Amin Talebi authored
-
- 25 May, 2023 1 commit
-
-
Delweng authored
* internal: replace noarg fmt.Errorf with errors.New Signed-off-by:
jsvisa <delweng@gmail.com> * tests: replace noarg fmt.Errorf with errors.New Signed-off-by:
jsvisa <delweng@gmail.com> * tests: go autoimport Signed-off-by:
jsvisa <delweng@gmail.com> * tests: go autoimport Signed-off-by:
jsvisa <delweng@gmail.com> --------- Signed-off-by:
jsvisa <delweng@gmail.com>
-
- 09 Mar, 2023 1 commit
-
-
Roberto Bayardo authored
Here, the core.Message interface turns into a plain struct and types.Message gets removed. This is a breaking change to packages core and core/types. While we do not promise API stability for package core, we do for core/types. An exception can be made for types.Message, since it doesn't have any purpose apart from invoking the state transition in package core. types.Message was also marked deprecated by the same commit it got added in, 4dca5d4d (November 2016). The core.Message interface was added in December 2014, in commit db494170, for the purpose of 'testing' state transitions. It's the same change that made transaction struct fields private. Before that, the state transition used *types.Transaction directly. Over time, multiple implementations of the interface accrued across different packages, since constructing a Message is required whenever one wants to invoke the state transition. These implementations all looked very similar, a struct with private fields exposing the fields as accessor methods. By changing Message into a struct with public fields we can remove all these useless interface implementations. It will also hopefully simplify future changes to the type with less updates to apply across all of go-ethereum when a field is added to Message. --------- Co-authored-by:
Felix Lange <fjl@twurst.com>
-
- 19 Aug, 2022 1 commit
-
-
ucwong authored
-
- 11 Aug, 2022 1 commit
-
-
lightclient authored
Co-authored-by:
bobpkr <bob.p@krustuniverse.com>
-
- 14 Jul, 2022 1 commit
-
-
lightclient authored
* internal/ethapi: error if tx args includes chain id that doesn't match local * internal/ethapi: simplify code a bit Co-authored-by:
Péter Szilágyi <peterke@gmail.com>
-
- 20 Jan, 2022 1 commit
-
-
Denver authored
* Chore: use same receiver names * Fix syntax issues
-
- 27 Aug, 2021 1 commit
-
-
lightclient authored
Currently, setDefaults overwrites the transaction input value if only input is provided. This causes personal_sendTransaction to estimate the gas based on a transaction with empty data. eth_estimateGas never calls setDefaults so it was unaffected by this.
-
- 23 Aug, 2021 1 commit
-
-
Marius van der Wijden authored
-
- 12 Aug, 2021 1 commit
-
-
Martin Holst Swende authored
-
- 29 Jul, 2021 1 commit
-
-
Martin Holst Swende authored
Ticket #23273 found a flaw where we were unable to sign legacy-transactions using the external signer, even if we're still on non-london network. That's fixed in this PR. Additionally, I found that even when supplying all parameters, it was impossible to sign a london-transaction on an unsynched node. It's a pretty common usecase that someone wants to sign a transaction using an unsynced 'vanilla' node, providing all necessary data. Our setDefaults, however, insisted on checking the current block against the config. This PR therefore adds a case, so that if both MaxPriorityFeePerGas and MaxFeePerGas are provided, we accept them as given. OBS This PR fixes a regression -- on current master, we are unable to sign a london-transaction unless the node is synched, which may break scenarios where geth (or clef) is used as a cold wallet. Fixes #23273
-
- 13 Jul, 2021 1 commit
-
-
gary rong authored
* internal/ethapi: fix transaction APIs * internal/ethapi: fix typo * internal/ethapi: address comments * internal/ethapi: address comment from Peter
-
- 10 Jun, 2021 1 commit
-
-
Péter Szilágyi authored
-
- 09 Jun, 2021 1 commit
-
-
Martin Holst Swende authored
-
- 08 Jun, 2021 1 commit
-
-
Péter Szilágyi authored
* all: rename internal 1559 gas fields, add support for graphql * cmd/evm/testdata, core: use public 1559 gas names on API surfaces
-
- 02 Jun, 2021 1 commit
-
-
Martin Holst Swende authored
* internal/ethapi: add baseFee to RPCMarshalHeader * internal/ethapi: add FeeCap, Tip and correct GasPrice to EIP-1559 RPCTransaction results * core,eth,les,internal: add support for tip estimation in gas price oracle * internal/ethapi,eth/gasprice: don't suggest tip larger than fee cap * core/types,internal: use correct eip1559 terminology for json marshalling * eth, internal/ethapi: fix rebase problems * internal/ethapi: fix rpc name of basefee * internal/ethapi: address review concerns * core, eth, internal, les: simplify gasprice oracle (#25) * core, eth, internal, les: simplify gasprice oracle * eth/gasprice: fix typo * internal/ethapi: minor tweak in tx args * internal/ethapi: calculate basefee for pending block * internal/ethapi: fix panic * internal/ethapi, eth/tracers: simplify txargs ToMessage * internal/ethapi: remove unused param * core, eth, internal: fix regressions wrt effective gas price in the evm * eth/gasprice: drop weird debug println * internal/jsre/deps: hack in 1559 gas conversions into embedded web3 * internal/jsre/deps: hack basFee to decimal conversion * internal/ethapi: init feecap and tipcap for legacy txs too * eth, graphql, internal, les: fix gas price suggestion on all combos * internal/jsre/deps: handle decimal tipcap and feecap * eth, internal: minor review fixes * graphql, internal: export max fee cap RPC endpoint * internal/ethapi: fix crash in transaction_args * internal/ethapi: minor refactor to make the code safer Co-authored-by:
Ryan Schneider <ryanleeschneider@gmail.com> Co-authored-by:
lightclient@protonmail.com <lightclient@protonmail.com> Co-authored-by:
gary rong <garyrong0905@gmail.com> Co-authored-by:
Péter Szilágyi <peterke@gmail.com>
-
- 25 May, 2021 1 commit
-
-
gary rong authored
There are two transaction parameter structures defined in the codebase, although for different purposes. But most of the parameters are shared. So it's nice to reduce the code duplication by merging them together. Co-authored-by:
Martin Holst Swende <martin@swende.se>
-