feat: Add Aptos support to facilitator #9
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
Collaborator
jtang17
commented
Jan 23, 2026
jtang17
commented
- Add AptosChainProvider with fee payer signing for sponsored transactions
- Implement v2 exact payment scheme for Aptos (aptos:1, aptos:2)
- Add local patch for aptos-runtimes tokio compatibility
- Support CAIP-2 chain identifiers
- Add AptosChainProvider with fee payer signing for sponsored transactions - Implement v2 exact payment scheme for Aptos (aptos:1, aptos:2) - Add local patch for aptos-runtimes tokio compatibility - Support CAIP-2 chain identifiers
Use aptos-node-v1.39.2 tag instead of commit hash for better readability and maintainability. Functionally equivalent to the previous commit hash fb9e2f4.
Add optional gas sponsorship for Aptos transactions, allowing facilitators to choose between sponsored mode (facilitator pays gas) and non-sponsored mode (client pays own gas). Changes: - Make AptosChainConfig.signer optional, add sponsor_gas boolean flag - Update AptosChainProvider to handle optional fee payer configuration - Update /supported endpoint to include extra.sponsored when enabled - Update settle flow to conditionally sponsor based on configuration - Add validation: signer required when sponsor_gas is true Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Add documentation showing: - Sponsored mode: facilitator pays gas (requires signer) - Non-sponsored mode: client pays gas (no signer needed) Only signer field supports environment variables ($APTOS_PRIVATE_KEY). RPC URL and sponsor_gas are plain config values, consistent with Solana.
Allow RPC URL and sponsor_gas to be configured via environment variables: - APTOS_RPC_URL - RPC endpoint (can include API key in URL) - APTOS_SPONSOR_GAS - true/false for gas sponsorship - APTOS_PRIVATE_KEY - facilitator private key (existing) This provides deployment flexibility to switch between networks and RPC providers without modifying config files.
Add api_key field to AptosChainConfigInner for authenticated RPC access. If provided, API key is sent as Authorization: Bearer header with all requests. Useful for paid RPC providers like Geomi nodes to avoid rate limiting. Example config: api_key = "$APTOS_API_KEY" Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
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.