Some of the current constructor arguments being used during contract deployment are making some assumptions and using defaults that only hold true for a development use-case. Going forward, those should be correctly exposed as configuration parameters.
Follow up to #550.
Some of the current constructor arguments being used during contract deployment are making some assumptions and using defaults that only hold true for a development use-case. Going forward, those should be correctly exposed as configuration parameters.