Closed inertia186 closed 6 years ago
The original scope was to capture get_config
from the mainnet, but I thought about it more and that wasn't going to be very helpful. Instead, I've updated the AC to require these fields in txgen.conf
with a default set by constant.
As a community developer trying out a testnet, I might want
tinman
to deal with certain changes toconfig.hpp
without having to also updatetxgen
constants, so that I can run my testnet with different constants likeSTEEM_HARDFORK_REQUIRED_WITNESSES
(as documented in devportal).Right now,
txgen
uses its own constants that may or may not match withconfig.hpp
, if our suggestions are followed on the devportal docs.Specifically:
STEEM_MAX_WITNESSES
STEEM_ADDRESS_PREFIX
STEEM_INIT_MINER_NAME
STEEM_MAX_ACCOUNT_CREATION_FEE
Verbiage on devportal reads:
Our documentation recommends changing
STEEM_HARDFORK_REQUIRED_WITNESSES
which would affecttxgen
behavior aroundNUM_BLOCKS_TO_CLEAR_WITNESS_ROUND
. Also, in theory,STEEM_BLOCK_INTERVAL
doesn't have to be3
.However, the solution is not for
txgen
to check the mainnet blockchainget_config
method (as originally scoped) because these defaults are part of the testnetconfig.hpp
, not the mainnet. So they must be set intxgen.conf
.As an example,
warden.py
already does lookups forget_config
(on the testnet), but this is because it is allowed to make API method calls and the testnet has already been bootstrapped and partially seeded.AC
txgen
interprets these defaults intxgen.conf
if present and falls back to existing constants if not present