Ismail Khoffi
Ismail Khoffi
# Summary The node types section only states who (which node type) is able to _generate_ proofs of invalid erasure coding. Nowhere is explained what happens after generating them. This...
## Summary We currently use the default params of most modules. We should settle on which params we want to launch with. ## Problem Definition The defaults might not be...
Potentially this can be done by following what gai does (I did some testing with Alessio back in the days but I don't remember the details and the process likely...
The specification must include all system-wide parameters. Client side parameters should also be specified in the sense that there should be a recommendation for defaults and where applicable it should...
We currently set the share size (rather arbitrarily) to 256 bytes. IMO this should be increased to maybe 1KB or more. Independent of what I think there must be a...
Not sure if this project is still in active development. If so, you might want to change your VRF implementation. For details see: https://github.com/coniks-sys/coniks-go/issues/175 or https://github.com/google/keytransparency/issues/567
### Celestia Node version 4d986940d662649eba4b0d3daa85268318204ff2 ### OS macosx ### Install tools via makefile ### Others _No response_ ### Steps to reproduce it add a key from ledger (after manually compiling...
There is no way currently to build cel-key with ledger support without modifying the Makefile manually. related: https://github.com/celestiaorg/celestia-app/issues/1658
The macro-generated code always checks the top-level attributes of the wrapping message for `is_registered` instead of on a per field basis :-/ We haven't noticed that so far because the...
For registered types this lib currently just skips over the prefix bytes. This assumes the caller knows which types to decode on the other side. In reality the user doesn't...