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(protocol): check if addresses ever reregistered in SGXProver #15665

Merged
merged 4 commits into from
Feb 6, 2024

Conversation

adaki2004
Copy link
Contributor

One address shall be registered (during attestation) only once, otherwise it could bypass this contract's expiry check by always registering with the same attestation and getting multiple valid instanceIds.

While during proving, it is technically possible to register the old addresses, it is less of a problem, because the instanceId would be the same for those addresses and can be easily deleted without the possibility of re-registering again - while if we dont rate limit at registration level, it could shoot up legit (and same) sgx provers with different instanceIds.

Copy link

vercel bot commented Feb 6, 2024

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

Name Status Preview Updated (UTC)
bridge-ui-v2-a6 ✅ Ready (Inspect) Visit Preview Feb 6, 2024 3:50am

@dantaik dantaik changed the title fix(protocol): Check attestation history feat(protocol): check if addresses ever reregistered Feb 6, 2024
@dantaik dantaik changed the title feat(protocol): check if addresses ever reregistered feat(protocol): check if addresses ever reregistered in SGXProver Feb 6, 2024
@dantaik dantaik enabled auto-merge February 6, 2024 13:43
@dantaik dantaik added this pull request to the merge queue Feb 6, 2024
Merged via the queue into alpha-6 with commit 27c86c1 Feb 6, 2024
15 checks passed
@dantaik dantaik deleted the rate_limit_attestation_register_address branch February 6, 2024 13:59
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.

4 participants