Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gasless transfer/stake/unstake #47

Open
aggre opened this issue Feb 3, 2021 · 3 comments
Open

Gasless transfer/stake/unstake #47

aggre opened this issue Feb 3, 2021 · 3 comments
Labels
core Core features of Dev Protocol layers 3rd party service/protocol built on the protocol core usability

Comments

@aggre
Copy link
Member

aggre commented Feb 3, 2021

Many beginners don't have ETH for gas fees. That's a challenge commonly known as the barrier to entry for blockchains (especially Ethereum).

Smart contracts that support meta-transactions (ethereum/EIPs#1776) allow users to interact with the contract by simply signing them in their wallets.

DEV tokens are already deployed and have no upgradability, so creating a paired token to support meta-transactions. For example, MDEV.

  • MDEV is designed to be converted with DEV on a 1:1 basis, and MDEV can achieve gasless transfers with functions like metaTransfer.
  • Staking and unstaking could be made gasless by having the Lockup contract support meta-transactions.

MDEV implementations will not be built into the protocol core because meta-transactions require an off-chain server.

@aggre aggre added core Core features of Dev Protocol layers 3rd party service/protocol built on the protocol core usability labels Feb 3, 2021
@Cold-A-Muse
Copy link

This is an great idea and will definitely help smaller players to support the OSS they like

@kazu80
Copy link
Collaborator

kazu80 commented Feb 3, 2021

I think it's a great idea too.
A little thing care is that users are confused when there are two, MDEV and DEV. I have question is, will users buy MDEV when it come out? I hope MDEV will be used in backend

@aggre
Copy link
Member Author

aggre commented Feb 3, 2021

A little thing care is that users are confused when there are two, MDEV and DEV. I have question is, will users buy MDEV when it come out? I hope MDEV will be used in backend

@kazu80 Users can buy MDEV, but they can convert 1:1 with DEV. So, buying MDEV is synonymous with buying DEV. Someone with a DEV can use the same number of MDEV through a converter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Core features of Dev Protocol layers 3rd party service/protocol built on the protocol core usability
Projects
None yet
Development

No branches or pull requests

3 participants