Protocol configurations should be stored in the smart contract

near / mpc

30 stars 6 forks source link

Protocol configurations should be stored in the smart contract #640

Open ChaoticTempest opened 2 weeks ago

ChaoticTempest commented 2 weeks ago

Currently, all timeout configs, and protocol specific configs (triple, presignatures, keygen, ...) are all stored in ENV variables or are hardcoded constants. We should be getting these from the smart contract instead just so that would be our one true source of configs. This allows us to make configuration changes more easily if things were to blow up somewhere

volovyks commented 2 weeks ago

Contract config has a higher priority
Nodes can override config (but they should not under normal circumstances)
If the parameter is not found there should always be a default value on the node (in code)