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

feat(entropy): Limit number of hashes #1822

Merged
merged 13 commits into from
Aug 15, 2024
Merged

feat(entropy): Limit number of hashes #1822

merged 13 commits into from
Aug 15, 2024

Conversation

m30m
Copy link
Collaborator

@m30m m30m commented Aug 12, 2024

No description provided.

Copy link

vercel bot commented Aug 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 14, 2024 11:47am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
xc-admin-frontend ⬜️ Ignored (Inspect) Visit Preview Aug 14, 2024 11:47am

Copy link
Contributor

@jayantk jayantk left a comment

Choose a reason for hiding this comment

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

nice!

}


pub async fn update_commitments_if_necessary(
Copy link
Contributor

Choose a reason for hiding this comment

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

nitpick: I think the verb "update" is a bit confusing here because it suggests that the caller could set the commitment to anything they want. A better name would be "advance", which implies that you can only move forward in the same hash chain.

@@ -38,6 +38,11 @@ interface EntropyEvents {
address oldFeeManager,
address newFeeManager
);
event ProviderMaxNumHashesUpdated(
address provider,
uint64 oldMaxNumHashes,

Choose a reason for hiding this comment

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

Small detail, but is there a reason that this is a uint64 when the struct field is only a uint32?

@m30m m30m merged commit 8966444 into main Aug 15, 2024
7 checks passed
@m30m m30m deleted the num-hashes-entropy branch August 15, 2024 04:46
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.

3 participants