Use sendTransaction for RPC providers to wrap the tx in a fee bump transaction

[janewang]

What problem does your feature solve?

To support smart wallets and sponsored transactions, we aim to provide developers with an endpoint for submitting transactions that sponsor transaction fees for Soroban. Developers using third-party providers will need to use their API key to post to this endpoint (standard implementation by third party providers). If the credit balance for sponsored transaction is available for their API key, that balance could be drawn down overtime.

What would you like to see?

RPC providers are use their API key generated to decide if they want to fee bump this transaction.

The transaction submission endpoint enables developers to experiment with soroban as well as for dapps and wallet builders to sponsor the creation of new smart wallets.

Prototype service implemented by @kalepail https://github.com/kalepail/launchtube

[janewang]

Possible scope creep on the standard feature set of a RPC