Skip to content
New issue

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

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

Already on GitHub? # to your account

Add nested call limit #465

Merged
merged 1 commit into from
Mar 1, 2023
Merged

Add nested call limit #465

merged 1 commit into from
Mar 1, 2023

Conversation

Dentosal
Copy link
Member

@Dentosal Dentosal commented Mar 1, 2023

@Dentosal Dentosal added documentation Improvements or additions to documentation comp:FVM Component: FuelVM labels Mar 1, 2023
@Dentosal Dentosal requested a review from Voxelot March 1, 2023 20:17
@Dentosal Dentosal self-assigned this Mar 1, 2023
@Dentosal Dentosal merged commit 6d7c95a into master Mar 1, 2023
@Dentosal Dentosal deleted the nested-call-limit branch March 1, 2023 20:43
@adlerjohn
Copy link
Contributor

How is this limit tracked in the VM? The current setup of the VM is that it's entirely fraud provable with only working memory and registers.

@Voxelot
Copy link
Member

Voxelot commented Mar 3, 2023

Well all the callframes should be in memory right? So you could scan over those in a similar way to re-entrancy detection as part of the fraud-proof.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
comp:FVM Component: FuelVM documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants