Meta Transactions in RSK

The user (without balance) use an sponsor system to invoke an smart contract from his/her proxy contract
  1. The user sends the intention (which contract to invoke, with which data) to an sponsor system. The intention should be signed by the user RSK account, but this account usually has no balance
  2. The sponsor system checks the validity of the intention, and then sends a real transaction to a proxy contract. Each external user has an associated proxy contract. In my sample, the mapping of user address to proxy contract is maintained by a proxy manager, but this functionality is not a requirement.
  3. The proxy contract validates that the intention was signed by its assigned external user, and then invokes a call to the final smart contract (the smart contract the original user wants to invoke)

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store