Gas Station funds transaction fees for sponsored accounts on supported Solana, XRPL, and EVM-compatible ledgers.
- Sponsor accounts provide native tokens for accounts that need gas.
- Configure sponsorship for specific accounts or for a domain.
- Set
includeSubDomainsto include subdomains in domain sponsorship. - Gas Station uses just-in-time funding instead of pre-funding every sponsored account.
- A dedicated bot user signs automated funding transactions.
Gas Station reduces operational friction for users and integrations that hold non-native tokens but do not hold the native token required for transaction fees. Operators can fund one or more sponsor accounts and define which accounts or domains receive fee funding.
For architects, Gas Station affects account design, bot-user governance, sponsor funding, and monitoring. Scope sponsorship deliberately so accounts get automated funding where they need it without granting broader transaction authority than the service requires.
Gas Station currently supports fee funding for non-native asset transactions on selected Solana, XRPL, and EVM-compatible ledgers. A sponsor account can only fund accounts on the same blockchain network. Sponsorship does not remove the need to fund and monitor sponsor accounts.
When a sponsored account needs native gas for a supported transaction, Gas Station:
- Detects that the account needs fee funding.
- Checks whether Gas Station sponsors the account directly or through its domain.
- Estimates the required native-token amount.
- Submits a funding transaction from the sponsor account to the sponsored account.
- Records the sponsorship activity for audit and monitoring.
| Sponsorship type | Description |
|---|---|
account | A sponsor account funds specific account IDs. |
domain | A sponsor account funds accounts in a domain. |
none | Disables sponsorship for the sponsor configuration. |
Account-level sponsorship takes precedence over domain-level sponsorship. When domain-level sponsorship uses includeSubDomains, the sponsorship can apply to child domains.
Gas Station uses a dedicated bot user to sign and submit funding transactions. Configure this bot user with narrowly scoped permissions and policies for automated fee-funding transactions.
If the bot user's funding transactions require manual approvals, those approvals may delay or block automatic sponsorship. Keep the bot user's authority limited to the funding operations Gas Station needs.
Omnibus can use Gas Station for non-native token sweeps from deposit wallets to the omnibus wallet on supported Solana, XRPL, and EVM networks.
When Gas Station funds an Omnibus deposit wallet, Omnibus must ignore the Gas Station account as a deposit source. This prevents Omnibus from processing native-token funding transactions as customer deposits.
Gas Station sponsorship depends on sponsor-account balances and healthy background processing. Monitor:
- Sponsor account balances and configured
alertLimitthresholds. - Funding failures and retry queues.
- Bot-user intent activity.
- Gas Station health and readiness endpoints.
- Telemetry exported through your configured OpenTelemetry pipeline.
| Topic | Documentation |
|---|---|
| Configure sponsorship | Configure gas sponsorship |
| Deployment reference | Gas Station reference |
| Bot users | Configure bot users |
| Omnibus | Omnibus |