feat: add config checker for multisig/DAO info#101
Merged
Seth-Schmidt merged 6 commits intomainfrom Apr 20, 2026
Merged
Conversation
- Added `get-multisig-info` script to report owners and thresholds for Gnosis Safe multisigs, Aragon DAO plugins, and Solana Squads. - Updated `.env.example` with new environment variables for multisig addresses. - Included `@sqds/multisig` package in dependencies and updated `package-lock.json`. - Enhanced README with usage instructions for the new script.
Seth-Schmidt
changed the title
- Added functionality to retrieve and verify the AdminModule information for the Gateway Safe. - Updated README to include details about the new AdminModule environment variable and its usage. - Modified the `get-multisig-info` script to check for enabled modules and validate the AdminModule's configuration.
jatZama
reviewed
Apr 17, 2026
….example - Updated README to differentiate between the Squads multisig account PDA and the vault ID, providing clear instructions on where to find each. - Enhanced .env.example with additional comments to prevent confusion regarding the multisig account's purpose. - Added notes in the get-multisig-info script to emphasize the distinction and avoid potential errors when retrieving multisig data.
jatZama
approved these changes
Apr 20, 2026
Seth-Schmidt
deleted the
feature/pro-302-config-checker-for-multisigdao-infos
branch
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.
Summary
Adds
get-multisig-infoto the chains-config-checker, reporting owners and thresholds for all deployed governancewallets:
getOwners()/getThreshold()and cross-checks that all Safesshare identical owners and threshold
Granted/Revokedevents forEXECUTE_PERMISSIONon the DAO, with an on-chainhasPermission()sanity check. Correctly filters out uninstalledplugins (e.g. the setup multisig)
@sqds/multisigfor members and thresholdChanges
utils/get-multisig-info.js: new scriptpackage.json: added npm script +@sqds/multisigdependency.env.example: added Safe, Aragon DAO, and Squads env varsREADME.md: documented usage, env vars, and example outputNOTE: The gateway safe module and admin module owner check from this issue is also included in this PR since they are related: https://linear.app/zama/issue/PRO-303/config-check-for-contracts-owners-delegate-module