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

feat(blobs): begin reading tx effects from blobs, rather than from data provided in propose transaction #10056

Open
Maddiaa0 opened this issue Nov 20, 2024 · 0 comments
Open

feat(blobs): begin reading tx effects from blobs, rather than from data provided in propose transaction #10056

Maddiaa0 opened this issue Nov 20, 2024 · 0 comments
Assignees
@Maddiaa0
Labels
C-node Component: Aztec Node

Comments

@Maddiaa0
Copy link
Member

Maddiaa0 commented Nov 20, 2024 •
edited
Loading

Overview

Rather than reading tx effects from calldata, we will read tx effects from blobs. This involves calling the https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Beacon/getBlobSidecars http method on the beacon client.

Relevant Links

Part of larger meta issue #9101 (comment)

See engineering designs document: AztecProtocol/engineering-designs#41
@Maddiaa0 Maddiaa0 added team-alpha C-node Component: Aztec Node and removed team-alpha labels Nov 20, 2024
@Maddiaa0 Maddiaa0 self-assigned this Nov 20, 2024
@MirandaWood MirandaWood mentioned this issue Dec 16, 2024
Open
@Maddiaa0 Maddiaa0 mentioned this issue Jan 16, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Maddiaa0 Maddiaa0

Labels
C-node Component: Aztec Node
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Maddiaa0