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

Jump to bottom

Protocol: Logs #3106

Closed
Tracked by #3083
iAmMichaelConnor opened this issue Oct 27, 2023 · 1 comment · Fixed by #3582
Closed
Tracked by #3083

Protocol: Logs #3106

iAmMichaelConnor opened this issue Oct 27, 2023 · 1 comment · Fixed by #3582
Assignees
@benesjan
Labels
A-documentation Area: relates to documentation A-protocol Area: relates to designing / explaining the protocol

Comments

@iAmMichaelConnor
Copy link
Contributor

iAmMichaelConnor commented Oct 27, 2023 •
edited
Loading

Note: this section is a high-level overview of logs. There will be a separate section describing what each circuit does in-depth.

  • Logs
    • Unencrypted
    • Encrypted
    • Optimisation considerations
      • Logs submitted on-chain need to be sha256-hashed/blob-committed somewhere. In which circuit should this happen? Should each circuit enable n log fields, instead of 1, and forward those log fields via the Data Bus?
@iAmMichaelConnor iAmMichaelConnor mentioned this issue Oct 27, 2023
Closed
@github-project-automation github-project-automation bot moved this to Todo in A3 Oct 27, 2023
@iAmMichaelConnor iAmMichaelConnor added A-documentation Area: relates to documentation A-protocol Area: relates to designing / explaining the protocol labels Oct 27, 2023
@iAmMichaelConnor iAmMichaelConnor added this to the 📝 Yellow Paper milestone Oct 27, 2023
@iAmMichaelConnor iAmMichaelConnor changed the title Logs YP: Logs Oct 27, 2023
@iAmMichaelConnor iAmMichaelConnor changed the title YP: Logs Protocol: Logs Oct 31, 2023
@benesjan benesjan mentioned this issue Dec 5, 2023
Merged
4 tasks
@benesjan
Copy link
Contributor

@iAmMichaelConnor got as far as I could in this PR but it doesn't really satisfy this issue.

benesjan added a commit that referenced this issue Dec 13, 2023
@benesjan
docs: a layout of logs section of yellow paper (#3582)
8c759f6 
Partially #3106

**Note**: There is not much in this PR since I don't really know how
much of what [Mike](https://aztecprotocol.slack.com/team/U02B9GDJKAN)
wrote
[here](https://forum.aztec.network/t/issues-with-logs/2609/4?u=jan) is
final (and I don't really understand what is data bus so don't really
have the knowledge to finish that). I pointed out in the PR what needs
to be discussed and expanded upon.
@LHerskind LHerskind moved this from Todo to Done in A3 Jan 15, 2024
michaelelliot pushed a commit to Swoir/noir_rs that referenced this issue Feb 28, 2024
@benesjan
docs: a layout of logs section of yellow paper (AztecProtocol#3582)
59e8635 
Partially AztecProtocol#3106

**Note**: There is not much in this PR since I don't really know how
much of what [Mike](https://aztecprotocol.slack.com/team/U02B9GDJKAN)
wrote
[here](https://forum.aztec.network/t/issues-with-logs/2609/4?u=jan) is
final (and I don't really understand what is data bus so don't really
have the knowledge to finish that). I pointed out in the PR what needs
to be discussed and expanded upon.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benesjan benesjan

Labels
A-documentation Area: relates to documentation A-protocol Area: relates to designing / explaining the protocol
Projects
A3
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs: a layout of logs section of yellow paper AztecProtocol/aztec-packages
2 participants
@benesjan @iAmMichaelConnor