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

CallBundle question, why do we need *core.BlockChain #133

Open
slawomir-pryczek opened this issue Jun 29, 2022 · 0 comments
Open

CallBundle question, why do we need *core.BlockChain #133

slawomir-pryczek opened this issue Jun 29, 2022 · 0 comments

Comments

@slawomir-pryczek
Copy link

Hello, wanted to ask about CallBundle. Why does it need *core.BlockChain when normal call to "DoCall()" function does not. Seems it operates on state, so we could just call DoCall() twice without resetting state in between? What i'm missing.

Can it be skipped or replaced with null?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@slawomir-pryczek