Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launch trin nodes & propagate data to them #4

Merged
merged 5 commits into from May 18, 2022
Merged

Launch trin nodes & propagate data to them #4

merged 5 commits into from May 18, 2022

Conversation

carver
Copy link
Contributor

@carver carver commented May 18, 2022

Overall changes:

  • launch trin nodes
  • build web3 instances linking to them
  • push content to the nodes, as it comes in
  • document more
  • naming cleanups

Issues punted, to get this PR wrapped:

  • Attempt to find trin in path. Currently, assumes that a trin binary is in the root of the project directory. I just did a soft link to trin_repo/target/debug/trin
  • Manual confirmation that data is actually being broadcast (AFAIK, data propagation does not yet trigger after portal_historyStore)
  • More OS-agnostic choices for execution. For example, it's currently putting the json-rpc IPC path in /tmp
  • Putting data directory into a ramdisk (probably outside the scope of this repo, but maybe a Dockerfile...)

To-Do

  • Read private keys out of environment variable PORTAL_BRIDGE_KEYS
  • Clean up commit history

Cute Animal Picture

put a cute animal picture link inside the parentheses

- Lots more docs
- Rename PortalInserter to singular
When dealing with the full field list returned by w3.eth.getBlock, call
them block_fields. When working with the restricted set of fields used
only in the header, call it header_fields.
@carver carver merged commit 72b8c42 into main May 18, 2022
@carver carver deleted the launch-trins branch May 18, 2022 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant