Warn on node startup if the removed `-blockprioritysize` option is set
to a non-zero value. Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
This commit is contained in:
parent
dbf52938af
commit
63d08919d1
|
@ -45,7 +45,8 @@ Changes to Block Template Construction
|
|||
- The block template construction algorithm no longer favours transactions that
|
||||
were previously considered "high priority" because they spent older inputs. The
|
||||
`-blockprioritysize` config option, which configured the portion of the block
|
||||
reserved for these transactions, has been removed and is now ignored.
|
||||
reserved for these transactions, has been removed and will now cause a warning
|
||||
if used.
|
||||
|
||||
Removal of Priority Estimation
|
||||
------------------------------
|
||||
|
|
|
@ -1295,6 +1295,10 @@ bool AppInit2(boost::thread_group& threadGroup, CScheduler& scheduler)
|
|||
}
|
||||
#endif
|
||||
|
||||
if (GetArg("-blockprioritysize", 0) != 0) {
|
||||
InitWarning(_("The argument -blockprioritysize is no longer supported."));
|
||||
}
|
||||
|
||||
if (!mapMultiArgs["-nuparams"].empty()) {
|
||||
// Allow overriding network upgrade parameters for testing
|
||||
if (chainparams.NetworkIDString() != "regtest") {
|
||||
|
|
Loading…
Reference in New Issue