Skip to content

Latest commit

 

History

History
34 lines (20 loc) · 1.65 KB

SPONSORED-TRANSACTIONS.md

File metadata and controls

34 lines (20 loc) · 1.65 KB
Raw

Sponsored Transactions

In common EVM blockchains the executor of a transaction is the payer of the fees, this complicates the onboarding of new users to the blockchain not just because they would have fund their account in order to start to operate but because they have to be invested in the corresponding token. For removing this restriction, sponsored transactions have been implemented.

Sponsored transactions is a new type of transaction in which a third-party pays the fees of an standard EVM transaction. This could be used for several reasons such as creating a BaaS with a monthly plane fee, onboarding processes, ...

How they work?

Sponsored transactions contains two key elements:

  • Signed transaction: A standard user-signed EVM transaction that would demostrate Stability nodes that the user agreed to execute that transaction
  • Sponsored transaction signature: The sponsor needs to sign the message described below so this proof could be used in Stabiliy nodes.

Sponsor signing message

The message that the sponsor has to sign is the following

I consent to be a sponsor of transaction: ${TransactionHash}

Note:

  • ${TransactionHash} is a 0x prefixed hexadecimal string

API

For executing a sponsored transaction a new a Stability's RPC method has been created and one auxiliary method:

stability_sendSponsoredTransaction:

  • It receives three arguments:
    • Raw signed transaction (same format as in eth_sendRawTransaction)
    • Sponsor address: Sponsor of the transaction
    • Sponsor signaure: Signature of the signing sponsored transaction message
  • It submits a transaction to the mempool as long as the transaction met all the prechecks