// Copyright 2020 The go-ethereum Authors
// This file is part of go-ethereum.
//
// go-ethereum is free software: you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
//
// go-ethereum 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 General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with go-ethereum. If not, see <http://www.gnu.org/licenses/>.
package utils
import (
"fmt"
all: activate pbss as experimental feature (#26274)
* all: activate pbss
* core/rawdb: fix compilation error
* cma, core, eth, les, trie: address comments
* cmd, core, eth, trie: polish code
* core, cmd, eth: address comments
* cmd, core, eth, les, light, tests: address comment
* cmd/utils: shorten log message
* trie/triedb/pathdb: limit node buffer size to 1gb
* cmd/utils: fix opening non-existing db
* cmd/utils: rename flag name
* cmd, core: group chain history flags and fix tests
* core, eth, trie: fix memory leak in snapshot generation
* cmd, eth, internal: deprecate flags
* all: enable state tests for pathdb, fixes
* cmd, core: polish code
* trie/triedb/pathdb: limit the node buffer size to 256mb
---------
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: Péter Szilágyi <peterke@gmail.com>
1 year ago
"github.com/ethereum/go-ethereum/eth/ethconfig"
"github.com/ethereum/go-ethereum/internal/flags"
"github.com/urfave/cli/v2"
)
var ShowDeprecated = & cli . Command {
Action : showDeprecated ,
Name : "show-deprecated-flags" ,
Usage : "Show flags that have been deprecated" ,
ArgsUsage : " " ,
Description : "Show flags that have been deprecated and will soon be removed" ,
}
var DeprecatedFlags = [ ] cli . Flag {
NoUSBFlag ,
LegacyWhitelistFlag ,
cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525)
The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.
However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.
Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.
Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.
All in all, compare with the minor performance gain, system robustness
is something we care more.
1 year ago
CacheTrieJournalFlag ,
CacheTrieRejournalFlag ,
LegacyDiscoveryV5Flag ,
all: activate pbss as experimental feature (#26274)
* all: activate pbss
* core/rawdb: fix compilation error
* cma, core, eth, les, trie: address comments
* cmd, core, eth, trie: polish code
* core, cmd, eth: address comments
* cmd, core, eth, les, light, tests: address comment
* cmd/utils: shorten log message
* trie/triedb/pathdb: limit node buffer size to 1gb
* cmd/utils: fix opening non-existing db
* cmd/utils: rename flag name
* cmd, core: group chain history flags and fix tests
* core, eth, trie: fix memory leak in snapshot generation
* cmd, eth, internal: deprecate flags
* all: enable state tests for pathdb, fixes
* cmd, core: polish code
* trie/triedb/pathdb: limit the node buffer size to 256mb
---------
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: Péter Szilágyi <peterke@gmail.com>
1 year ago
TxLookupLimitFlag ,
LightServeFlag ,
LightIngressFlag ,
LightEgressFlag ,
LightMaxPeersFlag ,
LightNoPruneFlag ,
LightNoSyncServeFlag ,
LogBacktraceAtFlag ,
LogDebugFlag ,
MinerNewPayloadTimeoutFlag ,
MinerEtherbaseFlag ,
MiningEnabledFlag ,
}
var (
// Deprecated May 2020, shown in aliased flags section
NoUSBFlag = & cli . BoolFlag {
Name : "nousb" ,
Usage : "Disables monitoring for and managing USB hardware wallets (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
// Deprecated March 2022
LegacyWhitelistFlag = & cli . StringFlag {
Name : "whitelist" ,
Usage : "Comma separated block number-to-hash mappings to enforce (<number>=<hash>) (deprecated in favor of --eth.requiredblocks)" ,
Category : flags . DeprecatedCategory ,
}
// Deprecated July 2023
cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525)
The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.
However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.
Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.
Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.
All in all, compare with the minor performance gain, system robustness
is something we care more.
1 year ago
CacheTrieJournalFlag = & cli . StringFlag {
Name : "cache.trie.journal" ,
Usage : "Disk journal directory for trie cache to survive node restarts" ,
Category : flags . DeprecatedCategory ,
cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525)
The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.
However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.
Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.
Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.
All in all, compare with the minor performance gain, system robustness
is something we care more.
1 year ago
}
CacheTrieRejournalFlag = & cli . DurationFlag {
Name : "cache.trie.rejournal" ,
Usage : "Time interval to regenerate the trie cache journal" ,
Category : flags . DeprecatedCategory ,
}
LegacyDiscoveryV5Flag = & cli . BoolFlag {
Name : "v5disc" ,
Usage : "Enables the experimental RLPx V5 (Topic Discovery) mechanism (deprecated, use --discv5 instead)" ,
Category : flags . DeprecatedCategory ,
cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525)
The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.
However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.
Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.
Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.
All in all, compare with the minor performance gain, system robustness
is something we care more.
1 year ago
}
all: activate pbss as experimental feature (#26274)
* all: activate pbss
* core/rawdb: fix compilation error
* cma, core, eth, les, trie: address comments
* cmd, core, eth, trie: polish code
* core, cmd, eth: address comments
* cmd, core, eth, les, light, tests: address comment
* cmd/utils: shorten log message
* trie/triedb/pathdb: limit node buffer size to 1gb
* cmd/utils: fix opening non-existing db
* cmd/utils: rename flag name
* cmd, core: group chain history flags and fix tests
* core, eth, trie: fix memory leak in snapshot generation
* cmd, eth, internal: deprecate flags
* all: enable state tests for pathdb, fixes
* cmd, core: polish code
* trie/triedb/pathdb: limit the node buffer size to 256mb
---------
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: Péter Szilágyi <peterke@gmail.com>
1 year ago
// Deprecated August 2023
TxLookupLimitFlag = & cli . Uint64Flag {
Name : "txlookuplimit" ,
Usage : "Number of recent blocks to maintain transactions index for (default = about one year, 0 = entire chain) (deprecated, use history.transactions instead)" ,
Value : ethconfig . Defaults . TransactionHistory ,
Category : flags . DeprecatedCategory ,
}
// Light server and client settings, Deprecated November 2023
LightServeFlag = & cli . IntFlag {
Name : "light.serve" ,
Usage : "Maximum percentage of time allowed for serving LES requests (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
LightIngressFlag = & cli . IntFlag {
Name : "light.ingress" ,
Usage : "Incoming bandwidth limit for serving light clients (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
LightEgressFlag = & cli . IntFlag {
Name : "light.egress" ,
Usage : "Outgoing bandwidth limit for serving light clients (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
LightMaxPeersFlag = & cli . IntFlag {
Name : "light.maxpeers" ,
Usage : "Maximum number of light clients to serve, or light servers to attach to (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
LightNoPruneFlag = & cli . BoolFlag {
Name : "light.nopruning" ,
Usage : "Disable ancient light chain data pruning (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
LightNoSyncServeFlag = & cli . BoolFlag {
Name : "light.nosyncserve" ,
Usage : "Enables serving light clients before syncing (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
// Deprecated November 2023
LogBacktraceAtFlag = & cli . StringFlag {
Name : "log.backtrace" ,
Usage : "Request a stack trace at a specific logging statement (deprecated)" ,
Value : "" ,
Category : flags . DeprecatedCategory ,
}
LogDebugFlag = & cli . BoolFlag {
Name : "log.debug" ,
Usage : "Prepends log messages with call-site location (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
// Deprecated February 2024
MinerNewPayloadTimeoutFlag = & cli . DurationFlag {
Name : "miner.newpayload-timeout" ,
Usage : "Specify the maximum time allowance for creating a new payload (deprecated)" ,
Value : ethconfig . Defaults . Miner . Recommit ,
Category : flags . DeprecatedCategory ,
}
MinerEtherbaseFlag = & cli . StringFlag {
Name : "miner.etherbase" ,
Usage : "0x prefixed public address for block mining rewards (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
MiningEnabledFlag = & cli . BoolFlag {
Name : "mine" ,
Usage : "Enable mining (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
MetricsEnabledExpensiveFlag = & cli . BoolFlag {
Name : "metrics.expensive" ,
Usage : "Enable expensive metrics collection and reporting (deprecated)" ,
Category : flags . DeprecatedCategory ,
}
all: remove `personal` RPC namespace (#30704)
This PR is a first step towards removing account management from geth,
and contains a lot of the user-facing changes.
With this PR, the `personal` namespace disappears. **Note**: `personal`
namespace has been deprecated for quite some time (since
https://github.com/ethereum/go-ethereum/pull/26390 1 year and 8 months
ago), and users who have wanted to use it has been forced to used the
flag `--rpc.enabledeprecatedpersonal`. So I think it's fairly
non-controversial to drop it at this point.
Specifically, this means:
- Account/wallet listing
-`personal.getListAccounts`
-`personal.listAccounts`
-`personal.getListWallets`
-`personal.listWallets`
- Lock/unlock
-`personal.lockAccount`
-`personal.openWallet`
-`personal.unlockAccount`
- Sign ops
-`personal.sign`
-`personal.sendTransaction`
-`personal.signTransaction`
- Imports / inits
-`personal.deriveAccount`
-`personal.importRawKey`
-`personal.initializeWallet`
-`personal.newAccount`
-`personal.unpair`
- Other:
-`personal.ecRecover`
The underlying keystores and account managent code is still in place,
which means that `geth --dev` still works as expected, so that e.g. the
example below still works:
```
> eth.sendTransaction({data:"0x6060", value: 1, from:eth.accounts[0]})
```
Also, `ethkey` and `clef` are untouched.
With the removal of `personal`, as far as I know we have no more API
methods which contain credentials, and if we want to implement
logging-capabilities of RPC ingress payload, it would be possible after
this.
---------
Co-authored-by: Felix Lange <fjl@twurst.com>
3 weeks ago
// Deprecated Oct 2024
EnablePersonal = & cli . BoolFlag {
Name : "rpc.enabledeprecatedpersonal" ,
Usage : "This used to enable the 'personal' namespace." ,
Category : flags . DeprecatedCategory ,
}
)
// showDeprecated displays deprecated flags that will be soon removed from the codebase.
func showDeprecated ( * cli . Context ) error {
fmt . Println ( "--------------------------------------------------------------------" )
fmt . Println ( "The following flags are deprecated and will be removed in the future!" )
fmt . Println ( "--------------------------------------------------------------------" )
fmt . Println ( )
for _ , flag := range DeprecatedFlags {
fmt . Println ( flag . String ( ) )
}
fmt . Println ( )
return nil
}