engine: specify Trin Execution ClientCode #590
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mkalinin
reviewed
Sep 21, 2024
mkalinin
approved these changes
Sep 22, 2024
Redidacove
pushed a commit
to Redidacove/execution-apis
that referenced
this pull request
Sep 30, 2024
This was referenced Oct 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi all 👋 https://github.com/ethereum/trin/tree/master/trin-execution
We are building an execution client with the initial goal of bridging data into the Portal Networks, without devp2p. So I thought I would make a PR to reserve our own code (which is mentioned in the
identification.mddocument.For context about the
without devp2ppart, a longer term goal would be to build it out so it rely's on the Portal Network instead, for transaction gossip and access to old history/state. Currently we can get everything we need to sync to latest from.era/.era1files and the consensus client itself. Which bypasses the use of devp2p for now, but of course we still need access to the consensus layer through the engine api.