Lion - dapplion

CC @tuyennhv

In current beacon chain gossip channels that include aggregate-able objects, a SelectionProof is required to prevent too many distinct yet valid messages from being propagated. In a naive implementation of...

This solution is really neat, having an enforceable condition is a great improvement. However, must be noted that for small stakers with a single key this requirement doubles their attestation...

This idea can be extended to sync committee subnets too. But with some mod such that only 1 every N validators have to subscribe.

If I understand correctly, more than improving the error message the CLI should check the contract address in the APM and if it detects it's different than the current one...

Given the type of crowd around Aragon using Google Analytics gives a bad image IMO. Even though Matomo can be as invasive, it isn't that of an immediate turn-off. And...

Following #1114 discussion: @macor161: > @dapplion When I had to propagate content last year for Espresso, it seemed to work but was far from a perfect solution. Did you end...

The intention is to use https://github.com/ipfs/js-ipfsd-ctl which handles all the configuration in a disposable way and therefore this should not be a problem

Do all of us agree on this one? If so it should be done at once since it affects the entire codebase and can be disruptive to parallel work (for...

> Same can be said about `engine-check`. Good catch! Adding it