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

Explore retaining support for legacy transaction types via a precompile #65

Open
pipermerriam opened this issue Jun 16, 2021 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@pipermerriam
Copy link
Contributor

We want, and maybe need to fully deprecate the legacy transaction types. This is motivated, or potentially required under state expiry. One common objection to this is that there may be transactions that were signed by cold wallets and then put into cold storage to be broadcast at some later time. Similarly, there are hardware wallets that support the current transaction type which may not be updated.

One route to deprecating these legacy transaction types at the consensus protocol level while still retaining support for them would be a precompile. Suppose you have some legacy transaction L. The idea would be that you would wrap it up in one of the new supported transaction types, and then within the EVM send it to the precompile which would handle dispatching the transaction at the EVM level.

This needs to be investigated to see whether it is viable, determine roughly how it would work, and understand any trade-offs that it might have.

@pipermerriam pipermerriam added the help wanted Extra attention is needed label Jun 16, 2021
@rodrigoherrerai
Copy link

Is anybody working on this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants