Soph

hey @gupadhyaya yeah that will work yeah, aren't we taking too much space in the DB by saving the all validator snapshot at each block ?

Hi @gupadhyaya so I tried the new RPC, and looks like on v1 has been implemented. v2 also work but it still uses hex and not int for the block...

same issue for validatorallinformation ``` curl --location --request POST 'https://api.s0.os.hmny.io/' --header 'Content-Type: application/json' --data-raw '{ "jsonrpc":"2.0", "method":"hmyv2_getAllValidatorInformationByBlockNumber", "params": [1, 1000], "id":1 }' {"jsonrpc":"2.0","id":1,"error":{"code":-32602,"message":"invalid argument 1: hex string without 0x prefix"}}...

Tested successfully in localnet where I had to : 1) prevent broadcast of crosslink 2) define localnet HIP32Epoch activation to 0 see the validator information showing all the signed/to-sign at...

@Frozen please fix the conflict and i can re test with the latest version before we can all approve an merge

can we move that under tracking repo instead, also I would involve @hypnagonia. Right now my concern is that I didn't see any of those deliverables hopefully @hypnagonia did

there is a slow appearance of all the HRC20 token

@rlan35 today a partner (Edy Senjaya) requested for one of the above feature : Another question, in regards to reward claim feature, how can i get a list of claimed...

@SebastianJ @rlan35 do you know what is the purpose of that error message ? I feel like it doesn't need to be specified ? also i never understood why there...

@Frozen can you review the conflict and @GheisMohammadi comment