feat: Add Signer Management & Attestation Tracking Mappings #74
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.
Overview
This PR enhances the
MultiSigContractV2by introducing new storage mappings and structures to manage signer information and attestation tracking. These changes lay the groundwork for more advanced signer coordination and transaction attestation mechanisms within the contract.🔍 Summary of Changes
🧩 New Additions
Signer Management
mapping(address => SignerInfo) public signerInfo;→ Associates each signer address with its corresponding signer metadata structure.
EnumerableSet.AddressSet private activeSigners;→ Tracks all currently active signers in the system, improving signer iteration and validation capabilities.
Attestation Tracking
mapping(address => mapping(uint256 => uint64)) public signerToAttestationId;→ Records the attestation ID for each signer per transaction.
mapping(uint256 => uint64[]) public transactionAttestations;→ Maps transaction IDs to all associated attestation IDs for that transaction.
Code Formatting
forge fmtfor consistent code style and readability.🧠 Motivation
These mappings are critical for enabling structured management of signers and attestations within the multi-signature contract.
They allow for:
🧾 Implementation Details
File modified:
src/MultiSigContractV2.solChanges include: