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

Logs are defined both as a set and as a sequence #891

Open
ghareeb-falazi opened this issue Sep 8, 2023 · 1 comment
Open

Logs are defined both as a set and as a sequence #891

ghareeb-falazi opened this issue Sep 8, 2023 · 1 comment

Comments

@ghareeb-falazi
Copy link

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.

@kodyfanz
Copy link
Contributor

kodyfanz commented Feb 6, 2024

This is the way to lead the story from one importance to another, first when saying $R_l$ is a set, this emphasizes the importance of the uniqueness of the log elements, later when saying the sequence $R_l$ is a series of logs entries emphasizes that it is arranged in order. Logs may need to be unique (set) and also processed in specific sequence/series

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

No branches or pull requests

2 participants