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

Support dry running of transactions in the past #2062

Closed
2 of 6 tasks
xgreenx opened this issue Aug 8, 2024 · 1 comment · Fixed by #2661
Closed
2 of 6 tasks

Support dry running of transactions in the past #2062

xgreenx opened this issue Aug 8, 2024 · 1 comment · Fixed by #2661
Assignees

Comments

@xgreenx
Copy link
Collaborator

xgreenx commented Aug 8, 2024

Requires first #1995 feature to avoid error in the case of the InMemory storage.

Scope draft:

  • Feature is "roughly" implemented on Green's branch (patch files + branch hotfix/dry_run_may_return)
  • Merge master into above
  • Write test which proves that a transaction can't be executed on the tip of the blockchain, but works on block from the past
  • Consider enabling this feature by a flag different than --debug (allow_historical_dry_run, or smth)
  • Option (?)
  • Clean-up code and cover with tests (if needed)
xgreenx added a commit that referenced this issue Aug 8, 2024
Due to race conditions dry run may fail with `InMemory` store. I
disabled the usage of the historical view for dry run case until the
future. #2062

### Before requesting review
- [x] I have reviewed the code myself
@rafal-ch
Copy link
Contributor

rafal-ch commented Dec 30, 2024

Add test scenario:
1. Alice has 100 in block 1
2. Alice transfers 50 to Bob in block 2
3. Dry Run - Alice tries to transfer 75 to Charlie in latest block -> FAIL
4. Dry Run - Alice tries to transfer 75 to Charlie in block 1 -> SUCCESS

@Dentosal Dentosal self-assigned this Feb 3, 2025
@Dentosal Dentosal mentioned this issue Feb 3, 2025
7 tasks
Dentosal added a commit that referenced this issue Feb 10, 2025
Closes #2062

## Description

Support dry running in past blocks. It's behind the
`--historical-execution` flag.
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

Successfully merging a pull request may close this issue.

3 participants