Implement LES protocol about nethermind HOT 24 CLOSED

Any questions - here / or on Gitter / or I can always jump on a quick zoom call to explain and guide.

from nethermind.

https://github.com/ethereum/devp2p/blob/master/caps/les.md

from nethermind.

Canonical Hash Trie

uses our RLP, Patricia Trie
2 hours the construct, 4 hours testing, 2 hours adding a database and config for it
not sure where the root hashes are stored so some short searching of the details

Bloom Bits

1 hour to understand the concept, 1 hours to implement based in existing Bloom implementation
2 hours of various tests
Compression Algorithm
3 hours coding + testing

BloomBits Trie
I do not understand the spec - a worrying sign - probably up to 12 hours of searching the details / reverse engineering

Client Side Flow Control + The Model
bytes counting to be added - 6 hours with testing
buffer underruns, recharges - 6 hours with testing

The protocol and the required capability / minor refactorings, handler registrations, versioning
harder path of Nethermind - probably around 12 hours

All the new messages serializers with testing
8 hours, maybe less - very repetetive work

I would suggest implementing server side before implementing the client behaviours.

from nethermind.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 3 weeks, 1 day from now.
Please review their action plans below:

1) icodesometime has started work.

• Refactor ISyncPeer implementation from Eth62 into a new SyncPeerProtocolHandlerBase class that extends ProtocolHandlerBase and implements ISyncPeer
• Implement Les protocol, throwing exceptions for unhandled SyncPeer methods, similar to Eth62 subprotocol.
• Add support for Les in capabilities list, etc.

Learn more on the Gitcoin Issue Details page.

from nethermind.

Can you brief the requirements for this task?

from nethermind.

Hi @sanchaymittal,

The requirements are to add LES protocol support to Nethermind code base.
LES is described here: https://github.com/ethereum/devp2p/blob/master/caps/les.md

Is is about adding LesProtocolHandler that will be able to process LES clients (light clients).

Best,
Tomasz

from nethermind.

@tkstanczak Let's do a call Anytime soon.

from nethermind.

jump on gitter and we can arrange - what time zone are you in?

from nethermind.

@tkstanczak I just pm you on Gitter and I'm in India(GMT+5:30) right now.

from nethermind.

ok, so probably best your morning tomorrow as I work night now - or your late evening - just ping me on gitter, thanks

from nethermind.

Hi! has work already begun on this?

from nethermind.

@oogetyboogety , yeah - @sanchaymittal is looking at it

from nethermind.

#1374 Would like to to contribute
#1373 send Eth

from nethermind.

anyone want to work on this? I think that @sanchaymittal is nit going to work on it

from nethermind.

from nethermind.

@tkstanczak I see no activity for quite a few days, can I work on this?

from nethermind.

@iCodeSometime will you continue? that start looked promising

from nethermind.

Issue Status: 1. Open 2. Cancelled

The funding of 3.0 ETH (1836.75 USD @ $612.25/ETH) attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Chat
• $965,467.20 more funded OSS Work available on the Gitcoin Issue Explorer

from nethermind.

I guess that issue should be closed @tkstanczak

from nethermind.

Why? Is it implemented?

from nethermind.

Why? Is it implemented?

I'm not sure, just saw that 3.0 ETH (1836.75 USD @ $612.25/ETH) been cancelled.

from nethermind.

It is not implement, the bounty was cancelled at the request of @tkstanczak

The general consensus is that nobody uses light clients and the focus has shifted to stateless or something, idk.

from nethermind.

The code was removed because it did not work. Also with snap sync the light client in the old form either does not exist or is not on the list of needed deliveries or is planned to replaces by other solutions.

from nethermind.

The code was removed because it did not work.

Then why did you close it as completed? There's an option to close it as "not planned" instead.

from nethermind.