Client: RPC Block Retrieval By Portal Network (experimental)

[holgerd77]

This is a PR on top of the getBlockByPortal branch, since the code is otherwise hard to find.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.46%. Comparing base (d24ca11) to head (dd562c4).
Report is 27 commits behind head on master.

❗ Current head dd562c4 differs from pull request most recent head e62dfe6

Please upload reports for the commit e62dfe6 to get more accurate results.

Additional details and impacted files

Flag	Coverage Δ
blockchain	?
common	?
statemanager	?
util	81.46% <ø> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[ScottyPoi]

Can confirm that portal client starts successfully with client start (tsx bin/cli.ts --enablePortal)

Added some logging to the startup within the client info logs

[acolytec3]

You can also view all the portal debug logs with the DEBUG=*Portal* environmental variable as well. Works like a charm

[ScottyPoi]

The failing test-all-browser test doesn't look like it has anything to do with the changes made in this PR, so I am reluctant to debug it from here...

[acolytec3]

The failing test-all-browser test doesn't look like it has anything to do with the changes made in this PR, so I am reluctant to debug it from here...

Absolutely no relation. Vitest is broken in some obscure way.

[ScottyPoi]

Take note of changes in
f20434f
and
4fe901a

The --enablePortal option has been renamed to --enablePortalHistory to make room for network config options for other networks.

Also added are radius config options for each network. Keep in mind here that you are setting the exponent for the radius. meaning that a --portalHistoryRadius setting of 250 will result in a node radius of 2^250 -1

The radius for each network defaults to 0. A node with a 0 radius can retrieve and store data, but should not accept gossip. A max radius of 2^256-1 will accept ALL gossip.