Roman Shanin
Roman Shanin
Also it's worth noticing that our `Queue` is broken in terms of multisigs. Problem is the following: We have method `check_tx` which treats `false` result of signature check as error...
After meeting with @Arjentix we have two possible solutions for the problem: 1) Revert to initial approach where we allow to put transaction into the queue even if it not...
@mversic sure. After some dissuasion we decided to provide numeric type for Assets similar to commonly encountered NUMERIC type in relational databases (Postgre, MySql, Oracle). This type is decimal point...
Maybe we can use `cargo` as [library](https://doc.rust-lang.org/nightly/nightly-rustc/cargo/).
To me submitting parameters in the struct (or enum) make more sense than current approach which is unnecessary broad atm, it's aligned with the way i wanted to store parameters...
> Genesis or default? > I'd prefer explicit parameters, so I vote for genesis. These parameters could be implemented not just as plain instructions, but as genesis fields which will...
> does it look satisfying and complete for you? Yeah, lgtm
Another benefit comes from how our new state works, which favors granular updates to avoid extensive cloning.
I'm not sure that i fully understand the purpose of this change. Since VRFState looks predetermined from the beginning, so peer that submit genesis could manipulate it. Because it's computed...
Can you provide any sources you used while implementing this approach?