feat: versioned event contracts, add client auth and scoped events#401
Merged
Solomonsolomonsolomon merged 1 commit intoJun 1, 2026
Merged
Conversation
|
@DevALVIN-24 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pr closes #379
Description: This PR upgrades the SDK’s event contract design to be production‑grade:
1.Versioned Event Emission – All events now emit a uint256 version as the first indexed argument, allowing downstream services to safely evolve event schemas.
2.Client Authorization Layer – Introduces authorizedClients mapping and admin‑only grantClient / revokeClient functions. Only addresses granted by the contract admin can be considered “serious clients” for off‑chain event consumption.
3.Scoped Access Modifier – onlyAuthorizedClient is provided for future functions that may need to restrict calls to authorized consumers.
4.Security Enforcement – Management of client permissions is limited to accounts holding the DEFAULT_ADMIN_ROLE (owner), ensuring controlled access.
These enhancements prepare the contract for robust, version‑controlled event streams and secure subscription semantics, moving it out of the demo phase and into a production‑ready offering.