https://github.com/austintgriffith/native-meta-transactions

integrate signed message recovery directly in your contracts
https://github.com/austintgriffith/native-meta-transactions

Last synced: 10 months ago
JSON representation

integrate signed message recovery directly in your contracts

• Host: GitHub
• URL: https://github.com/austintgriffith/native-meta-transactions
• Owner: austintgriffith
• Created: 2018-11-29T20:09:38.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2018-12-05T17:15:58.000Z (over 7 years ago)
• Last Synced: 2025-03-30T17:51:15.761Z (over 1 year ago)
• Language: JavaScript
• Homepage:
• Size: 28.3 KB
• Stars: 37
• Watchers: 4
• Forks: 17
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# Native Meta Transactions

integrate signed message recovery directly in your contracts

[Read Full Article here](https://medium.com/gitcoin/native-meta-transactions-e509d91a8482)

---

Most of the meta transaction demos I have built to date revolve around creating a gasless layer on top of existing contracts. To do this there are a few trade offs including extra work on the frontend to track down the real msg.sender. A good example of this is in my EtherJamJam build.

I think it's important to highlight that if you are able to deploy fresh contracts you should probably be building meta transactions directly in your contracts. For instance, if you create a token, you can provide an interface and relay for your users to send their tokens without paying gas. 

Let's build an ERC20 token that gives etherless accounts the ability to transfer() and we'll build a relay that pays the gas.

[![screencast](https://user-images.githubusercontent.com/2653167/49298483-c4d0b600-f47a-11e8-97ae-f539ab5d0bc0.png)](https://youtu.be/tnLsBvzYu_A)