Amrit Kummer
Amrit Kummer
@ilyasergey This may require support for user defined data structure, e.g., `struct`.
@vaivaswatha What he meant was we need to add extra fields in `blockchain.json` to incorporate previous block's hash. So, instead of the following `blockchain.json`: ``` [ { "vname": "BLOCKNUMBER", "type":...
There could be another related primitive that we could add: addmod(uint x, uint y, uint k) returns (uint): compute (x + y) % k where the addition is performed with...
There were some changes made to the specification presented in the document you shared. For example, in our scheme, the signing algorithm hashes the public key to prevent certain attacks....
Thanks for this feature request @bguiz. We will keep this feature in mind when we start adding advanced cryptographic primitives.
@vaivaswatha This will require signature verification in the contract. Let us put this on hold. In the future, we may want to support some other crypto primitives beyond hashing such...
@edisonljh You may want to do a multisig wallet contract first? An example is here: https://github.com/gnosis/MultiSigWallet
Reassigning to @jjcnn. Let's start with a multisig first and then we can do a payment channel.
Basically, one would wish to use hmac instead of hash function in a scenario where only specific entities have the right to insert elements in the filter or check for...
Thanks for the feedback and your notes @Sajjon! 1. **Max Number of Nodes:** As you mentioned, validator nodes in Cosmos or other PoS/dPoS chains are very different from the seed...