- send directly through your own RPC path
- sponsor submission through Swig’s paymaster route
Sponsor submission
Useswig.transactions.sponsor(...) when your server should hand the signed
transaction to Swig’s sponsor path:
TypeScript
When sponsor submission fits
Use it when:- your product wants gasless or paymaster-backed flows
- your backend already owns the post-signing submission step
- you want one server-owned path for ordered transaction submission
Transaction categories still matter
These categories tell you what can go straight to send or sponsor:clientAuthorityTransactions/client_authority_transactionsmust be client-signed firstfeePayerOnlyTransactions/fee_payer_only_transactionscan go straight to your fee payer or sponsor pathoperatorSignedTransactions/operator_signed_transactionsare already operator-signed and just need final submission handling

