Jun 2, 2018

@Fil You are welcome to do so, but parameterizing those values into all uses will be fairly pervasive. Expect a lot of comments. All constants that could vary by coin should be parameterized. There should be a settings class analogous to that of other repos (we want no more than one per repo). There are trade-offs to passing a full settings reference (vs. individual values) into a class, method or function. I'd be looking for consistency here and generally we opt for passing individual values if there is just one or two and no expectation that the set would expand over time, and the settings object if the use is pervasive within another class. If values are used in more than one place in a class we prefer passage via the constructor, and otherwise also to simplify later method calls. The genesis block must also become a setting (base16 encoded canonical/wire serialization). Thanks!