-
Notifications
You must be signed in to change notification settings - Fork 499
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
Logs are defined both as a set and as a sequence #891
Comments
This is the way to lead the story from one importance to another, first when saying |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Section 4.3.1 Transaction Receipt, the construct$R_l$ is first defined as a set (i.e., unordered and contains no repititions) and then as a "a sequence (...) a series of log entries", which indicates it is ordered and may contain repititions, i.e., the same event emitted more than once with the same arguments in one smart contract function execution.
The text was updated successfully, but these errors were encountered: