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

Update validate_and_execute.adoc #1096

Merged
merged 2 commits into from
Feb 5, 2024
+1 −1
Merged

Update validate_and_execute.adoc #1096

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a4e854c
Update validate_and_execute.adoc
dor-starkware Jan 30, 2024
1a6ee4f
Minor edit.
stoobie Feb 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...knet/modules/architecture_and_concepts/pages/Accounts/validate_and_execute.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ When the `__validate__` function fails, no fee will

There are some limitations set on the `__validate__` function. The purpose of these limitations is twofold:

* We want to avoid the sequencer having to do a lot of work only to discover that the validation failed and the sequencer is then not eligible to charge a fee (if this was possible, the sequencer would be completely exposed to DOS attacks). Validation, while now abstract and in control of the account owner rather than the protocol, should still be a simple operation. This is why in the future, Starknet will place max steps limitation upon the `__validate__` function.
* We want to avoid the sequencer having to do a lot of work only to discover that the validation failed and the sequencer is then not eligible to charge a fee (if this was possible, the sequencer would be completely exposed to DOS attacks). Validation, while now abstract and in control of the account owner rather than the protocol, should still be a simple operation. This is why a maximum steps limitation on the `__validate__` function is currently in place on the Starknet network. For more information, see xref:tools:limits_and_triggers.adoc[Current limits].

* Even if the validation is simple, we could still face the following attack:
** An attacker fills the mempool with transactions that are valid at time T.
Expand Down
Loading