Fix/contract version detection 243#278
Merged
Merged
Conversation
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
1 participant
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.
Implementation Highlights
On-Chain Versioning: Added a get-version read-only function to the sprintfund-core-v3.clar contract to allow the frontend to verify the protocol version.
Detection Service: Built a ContractVersionService that fetches the on-chain version once per session and caches it, reducing RPC overhead.
UI Guarding: Developed a ContractVersionGuard component that automatically disables interactive elements and provides clear, actionable feedback if a version mismatch is detected.
Transaction Gating: Integrated the version guard into all critical wallet interaction points:
Proposal Manifesting: Users cannot submit new proposals if the versions don't match.
Quadratic Voting: Voting controls are locked when a version mismatch is detected to prevent lost transaction fees.
Execution Safety: Proposal execution is gated to ensure the DAO's treasury is only interacted with through verified logic.
Vote Recovery: Users are protected when reclaiming stake costs from previous voting cycles.
Closes #243