sam bacha

This has been fixed in https://github.com/grafana/tempo/issues/495

ASN.1 BER/PER is pretty standard. for SSZ, my reference is https://github.com/ChainSafe/ssz

Why not Avro? Kafka support is already integrated correct? On Thu, Aug 13, 2020 at 12:28 PM Samuel Stokes wrote: > Messaging Protocols Comparison > > The following contains research...

We are in a similar situation, along with having to replicate proxies / mirroring package registries (go modules / npm). Can vouch for sourcehut: its great service, really though you...

Edit: default branch of `xenial` confused me, as `focal` is what all buildimages use, and if you check the supported software, python 3.8 is listed. https://github.com/netlify/build-image/blob/focal/included_software.md

> Would love to hear thoughts from you @jeromelaurens @sambacha @xcarlo @block-builder-22! We are implementing an RLN based authentication scheme for the purposes of preventing spam. The requirement is that...

> > Would love to hear thoughts from you @jeromelaurens @sambacha @xcarlo @block-builder-22! > > Mainly agree with @jparyani : start simple. I would propose a signed header for authentication...

> > The RLN solves this issue by decoupling availability from reputation: you do not get access based on some capital requirement, you get access based on your existing reputation...

should the `resolution` really just say `pending` for `n+3` blocks?

I would think using the term `finality` would be more apt, as this is the attribute that is actually being used (finalization of transaction meaning X amount of blocks have...