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

[Tracking] SVM: Generic over Transaction Type #2108

Closed
7 tasks done
Tracked by #2198
apfitzge opened this issue Jul 12, 2024 · 2 comments
Closed
7 tasks done
Tracked by #2198

[Tracking] SVM: Generic over Transaction Type #2108

apfitzge opened this issue Jul 12, 2024 · 2 comments
Assignees

Comments

@apfitzge
Copy link

apfitzge commented Jul 12, 2024

Problem

Tracking issue for project to make SVM generic over the new SVMTransaction and SVMMessage traits.

The goal here is that we can make SVM unaware of the exact transaction type so long as it provides specific set of functionality, as defined by those traits.
This allows us to use more efficient transaction types where necessary, for example in block-production we can write a transaction type that is much faster to deserialize.

Proposed Solution

Living list of tasks here to support tracking all issues/prs related to goal of making SVM generic over the SVMTransaction and SVMMessage traits.

@apfitzge apfitzge self-assigned this Jul 12, 2024
@apfitzge
Copy link
Author

This work is following the addition of the SVMMessage and SVMTransaction traits in #1918.

@apfitzge apfitzge changed the title SVM: Generic over Transaction Type [Tracking] SVM: Generic over Transaction Type Jul 18, 2024
@apfitzge
Copy link
Author

@buffalojoec I think we should probably also update the docs for svm since with #2615 the argument is no longer necessarily SanitizedTransaction - though those are still permitted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant