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

Determine how to deal with public log lengths #11636

Open
Tracked by #9119
nventuro opened this issue Jan 30, 2025 · 0 comments
Open
Tracked by #9119

Determine how to deal with public log lengths #11636

nventuro opened this issue Jan 30, 2025 · 0 comments
Labels
C-node Component: Aztec Node C-pxe Component: PXE (Private eXecution Envrionment) team-fairies Nico's team

Comments

@nventuro
Copy link
Contributor

nventuro commented Jan 30, 2025

Public logs currently always have the full length of 13 fields, with non-emitted fields being padded with zeroes. We need to know the actual length in order to not publish unnecessary data to DA (and should not rely on simply trimming back the zeroes, which is what we're temporarly doing as of #11641) and to properly handle the payload when processing logs in contracts.

@nventuro nventuro added team-fairies Nico's team C-pxe Component: PXE (Private eXecution Envrionment) C-node Component: Aztec Node labels Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-node Component: Aztec Node C-pxe Component: PXE (Private eXecution Envrionment) team-fairies Nico's team
Projects
None yet
Development

No branches or pull requests

1 participant