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

fault_proving(global_roots): Populate Blobs table #2667

Merged
merged 4 commits into from
Feb 5, 2025

Conversation

netrome
Copy link
Contributor

@netrome netrome commented Feb 4, 2025

closes #2586

@netrome netrome linked an issue Feb 4, 2025 that may be closed by this pull request
@netrome netrome force-pushed the 2586-fault_provingglobal_roots-populate-blobs-table branch from 2bc87dd to 5db1b99 Compare February 4, 2025 15:57
@netrome netrome self-assigned this Feb 4, 2025
@netrome netrome marked this pull request as ready for review February 4, 2025 15:57
@netrome netrome requested a review from acerone85 February 4, 2025 19:15

// Given
let blob = vec![1, 3, 3, 7];
let blob_id = BlobId::compute(&blob);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what happens when we already have a blob that already exists? should we throw an error or just overwrite it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know the current behavior of the node (whether we allow duplicate blobs or not), but here we should only receive valid transactions. Since blobs are content-addressed it doesn't really matter. We could probably just ignore it, since we already have the blob stored. The behavior should only matter if we have hash collisions, which in practice doesn't happen afaik.

rymnc
rymnc previously approved these changes Feb 5, 2025
Copy link
Member

@rymnc rymnc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor non-blocking question, lgtm

acerone85
acerone85 previously approved these changes Feb 5, 2025
@netrome netrome dismissed stale reviews from acerone85 and rymnc via b4ea7fa February 5, 2025 11:40
@netrome netrome force-pushed the 2586-fault_provingglobal_roots-populate-blobs-table branch from f7b2d7a to b4ea7fa Compare February 5, 2025 11:40
@netrome netrome requested review from rymnc and acerone85 February 5, 2025 11:40
@netrome netrome enabled auto-merge (squash) February 5, 2025 12:09
@netrome netrome merged commit c4404d2 into master Feb 5, 2025
31 of 32 checks passed
@netrome netrome deleted the 2586-fault_provingglobal_roots-populate-blobs-table branch February 5, 2025 12:27
@AurelienFT AurelienFT mentioned this pull request Feb 5, 2025
AurelienFT added a commit that referenced this pull request Feb 5, 2025
## Version 0.41.6

### Added
- [2668](#2668): Expose gas
price service test helpers
- [2621](#2598): Global merkle
root storage updates process upgrade transactions.
- [2650](#2650): Populate
`ProcessedTransactions` table in global merkle root storage.
- [2667](#2667): Populate
`Blobs` table in global merkle root storage.
- [2652](#2652): Global Merkle
Root storage crate: Add Raw contract bytecode to global merkle root
storage when processing Create transactions.

### Fixed
- [2673](#2673): Change read
behavior on the InMemoryTransaction to use offset and allow not equal
buf size (fix CCP and LDC broken from
FuelLabs/fuel-vm#847)
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

Successfully merging this pull request may close these issues.

fault_proving(global_roots): Populate Blobs table
3 participants