Add RFP-027: LEZ Node API - #205
Open
fryorcraken wants to merge 1 commit into
Open
fryorcraken wants to merge 1 commit into
fryorcraken wants to merge 1 commit into
Conversation
Define the LEZ node API: the global, non-wallet functions an integrator uses to read chain state and submit signed transactions. Wallet and key management, transaction construction and signing are out of scope and will be defined separately. Include the two appendices the RFP's requirements rest on: the as-built API surfaces the gap analysis is drawn from, and the ecosystem survey of how comparable chains expose node APIs to integrators. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Sep 18, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Defines the LEZ node API: the global, non-wallet functions an integrator uses to read chain state and submit signed transactions. Wallet and key management, transaction construction and signing are out of scope here and are defined separately.
Includes the two appendices the requirements rest on:
appendix/logos-api-surfaces.md— the as-built API surfaces the gap analysis is drawn from.appendix/blockchain-api-sdk-ecosystem.md— how comparable chains expose node APIs to integrators.Note for reviewers
This PR was split out of #200. The SDK architecture half is in a stacked follow-up PR, which also carries the five draft RFP rows (RFP-028 to RFP-032) for the components this architecture implies.
RFP-027 links to
appendix/integrating-logos-technology-stack.mdin two places (lines 79 and 1140). That appendix arrives in the follow-up PR, so those two links resolve once both have merged. Merging this one first is intended.🤖 Generated with Claude Code