feat: Introduce SignerInfo struct for enhanced signer management
#71
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.
PR Description
Summary
This PR introduces a new
SignerInfostruct intoMultiSigContractV2.solto provide a standardized way of tracking metadata and activity related to individual signers. This is a foundational change that lays the groundwork for more robust signer management, governance, and auditing features in future updates.Changes
Added
SignerInfostruct with the following fields:bool active: Indicates if a signer is currently active.uint256 addedAt: Timestamp of when the signer was added.uint256 lastSignedAt: Timestamp of the most recent transaction the signer approved.uint256 totalSigned: Number of transactions signed by this signer.string role: Logical role assigned to the signer (e.g., admin, auditor, member).uint256 reputation: Numeric score for evaluating signer trustworthiness or performance.Formatting
forge fmtfor codebase consistency.Rationale
Impact
Next Steps
SignerInfointo signer management functions (add/remove/update).reputationin decision-making and voting weight mechanics.