You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extract headers (maybe follow the tip of the mainnet chain) from an execution client, and inject them into a trin client, in a way that offers them to other peers on the network.
TODO:
Manually generate private keys and node ids to create ~8 nodes spread around the DHT ~evenly (perhaps run with larger than usual buckets? Only if that's easier than running more nodes, which seems a little unlikely)
make a bridge-splitter daemon that:
at launch:
runs the ~8 trin nodes, with custom ipc path and port (and data directory?)
connects to 3rd-party service: infura? alchemy? etc
listens for new headers to arrive
when a header arrives:
generate header content-key and content-value
call portal_historyStore on all ~8 nodes with the header
get the transactions and uncles to build the block body, from 3rd party
generate block body content-key and content-value
call portal_historyStore on all ~8 nodes with the block body
get the receipts from 3rd party
generate receipts content-key and content-value
call portal_historyStore on all ~8 nodes with the receipts
In trin, after receiving data via portal_historyStore, gossip it to relevant nodes in routing table (with matching radius) -- depends on Propagate Gossip implementation #313
Propagate the data, even if it's not stored locally
It's quick to generate node IDs. I wrote a python script that is generating 10k / second using eth-keys. That was plenty to find these node IDs that seem to be evenly spread:
Extract headers (maybe follow the tip of the mainnet chain) from an execution client, and inject them into a trin client, in a way that offers them to other peers on the network.
TODO:
(and data directory?)portal_historyStore
on all ~8 nodes with the headerportal_historyStore
on all ~8 nodes with the block bodyportal_historyStore
on all ~8 nodes with the receiptstrin
, after receiving data viaportal_historyStore
, gossip it to relevant nodes in routing table (with matching radius) -- depends on Propagate Gossip implementation #313portal_historyOffer
instead ofportal_historyStore
The text was updated successfully, but these errors were encountered: