You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One solution to more frequent auctions for testing (#7249) would be to give a value for StartFrequency in the config file when starting the chain. But the config.auctionParams in startAuctioneer isn't wired up to the config file.
The connections between initial governance parameter values (and contract terms) and config file options is incomplete and ad-hoc.
Plus, the value for StartFrequency includes the timerBrand, and we can't put objects such as that directly in JSON config files. Likewise bignums, ratios. We have various ad-hoc conventions for building objects from JSON data in config files.
Design
a uniform mechanism to set the initial value of any governance parameter
perhaps a small expression language... akin to Justin, but embedded in JSON. the smartWallet callPipe is similar.
@dckc is aware of this, but for others following along, minSubmissionCount is addressed somewhat in #7583. If it needs to be modified in other places, that PR demonstrates an approach that works.
Problem
One solution to more frequent auctions for testing (#7249) would be to give a value for
StartFrequency
in the config file when starting the chain. But theconfig.auctionParams
in startAuctioneer isn't wired up to the config file.The connections between initial governance parameter values (and contract terms) and config file options is incomplete and ad-hoc.
Plus, the value for
StartFrequency
includes thetimerBrand
, and we can't put objects such as that directly in JSON config files. Likewise bignums, ratios. We have various ad-hoc conventions for building objects from JSON data in config files.Design
JSON
. the smartWalletcallPipe
is similar.Goals (optional):
The text was updated successfully, but these errors were encountered: