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.

Sign up for GitHub

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

Jump to bottom

Explore combining vm.PrecompileEnvironment and vm.OperationEnvironment #33

Closed
ARR4N opened this issue Sep 18, 2024 · 1 comment
Closed

Explore combining vm.PrecompileEnvironment and vm.OperationEnvironment #33

ARR4N opened this issue Sep 18, 2024 · 1 comment
Assignees
@ARR4N
Labels
enhancement New feature or request

Comments

@ARR4N
Copy link
Collaborator

ARR4N commented Sep 18, 2024

They're already quite similar and are subject to the same nuances around security if introducing access to call other contracts.

Tip

If introducing access to EVM.*Call*() methods, it can be done in the same way as StateDB() is (dependent on the value of ReadOnly().
@ARR4N ARR4N added the enhancement New feature or request label Sep 18, 2024
@ARR4N ARR4N self-assigned this Sep 18, 2024
@ARR4N
Copy link
Collaborator Author

ARR4N commented Sep 25, 2024

Redundant as now done in the PR that introduces vm.OperationEnvironment, #30.

@ARR4N ARR4N closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ARR4N ARR4N

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ARR4N