Release Notes

Portal Network Tools v0.2.1 (2022-10-04)

Updated content key encoding ssz scheme & test vectors to new spec, removing the chain id. (#44)

Correct the maximum receipt length in SSZ encoding. No specific bug is known to be fixed by this change. (#40)

Update ln -s example in bridge setup guide to use absolute source path. This prevents folks from getting a Too many levels of symbolic links error during setup, because soft links require an absolute source path. (#42)

In order to follow the tip of the chain, you must now specify --latest or -l. See “Run after first installation” under “Run a Bridge Node” (#38)

Publish data from a historical block range with --block-range. See “Backfill historical blocks” under “Run a Bridge Node” (#34)
Add the ability to inject specific content items on-demand with --content-files. See “Inject content manually” under “Run a Bridge Node” (#35)

When receipts fail their check against the expected root hash, save them to a file in a temporary directory (#32)

Officially claim support for python versions up to 3.9 (won’t support 3.10 until a stable web3 version does…) (#29)

- Upgrade ssz to v0.3.0 to get cleaner & faster ssz bytelist decoding
- Apply black formatting to setup.py (#29)
Update project template to get smaller releases, a towncrier duplicate-note fix, CircleCI image upgrade, breaking change newsfragments, and pydocstyle failure explanations. (#30)

Use the portal_historyOffer rpc endpoint of trin, instead of portal_historyStore. This requires a more recent version of trin. Follow the rpc update in trin for more. (#27)
Drop Python3.6 to support the latest ssz v0.3.0, which doesn’t support py3.6. (#29)

Launch the bridge with python -m eth_portal.bridge. (#23)
Add a new script to monitor new headers, with Infura. Also, add utility to encode header fields into serialized RLP object. (#1)
Encode header hash into a Portal History Network content key (#2)
Encode header content key & value, on each new header hash. (#3)
Launch trin nodes with bridge, and push content to them, as new headers arrive. (#4)
Encode the content key for block receipts (#7)
Encode receipt values, tested against header’s receipt root hash (#8)
Encode a group of receipts to its Portal Network content value. Currently assumes that we switch to using an SSZ list from the RLP list. (#10)
Push the block’s receipts out to trin nodes, after detecting a new header. (#11)
In bridge launcher, detect if trin “injector” node is already running, then use it. One benefit is being able to observe the logs on trin during bridge operation. (#14)
Encode the content key for block bodies (#16)
Decode a web3 transaction into a py-evm one, for encoding & hashing (#17)
Encode uncles and transactions into a block body for Portal Network. (#18)
Propagate block bodies on the Portal History Network. (#19)

Add web3 dependency in order to poll for new headers, and py-evm dependency to encode headers to RLP (#1)
Use black as the code formatter, and add to CI for enforcement. Upgrade isort to v5 for compatibility. (#12)