Add Tron and Solana platform adapters#23
Draft
Agusx1211 wants to merge 3 commits into
Draft
Conversation
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.
Adds native platform adapters for Tron and Solana/SVM, keeping EVM as the default while routing platform-specific operations through explicit adapters.
The Tron path adds TronWeb-backed calls, transactions, deployments, address normalization, energy estimation, and platform-specific tests. The Solana path includes program discovery, native actions and resolvers, authority-free program reservation, Squads-controlled buffers and proposals, execution, and program verification.
This lets Catapult projects select
tronorsvminnetworks.yamlwithout pretending either chain exposes EVM semantics.Validated with
pnpm build,pnpm lint, and the targeted Solana test suites (19 tests passed). The full Jest suite was also attempted, but this environment does not have the expected EVM node at127.0.0.1:8545, so the EVM integration suites could not complete.