Managing SubDAO Members¶
This guide covers practical member management for current Sage governance flows.
Why This Matters¶
Member controls determine who can propose, approve, and execute improvements. Good member operations directly affect library quality and upgrade velocity.
Where This Fits in the Loop¶
This guide is part of Govern and Curate: discover -> publish -> govern -> reward -> improve.
Step 1: Inspect Current DAO Governance State¶
Use this to confirm current governance mode and active proposal activity before changing responsibilities.
Step 2: Choose the Right Operating Model¶
- Personal DAO: one operator, fastest control loop.
- Team DAO: operator-based control (often multisig).
- Community DAO: token-vote governance with broader participation.
Use the mode that matches your coordination needs and risk tolerance.
Step 3: Manage Membership via Governance Process¶
Current best practice is to use governance proposals for role/membership changes:
sage governance proposals create \
--proposal-type custom \
--dao 0xYourDAO \
--target 0xTargetContract \
"Update membership controls"
Then run standard governance flow:
sage governance proposals list --dao 0xYourDAO
sage governance proposals vote <proposal-id> for --dao 0xYourDAO
sage governance proposals execute <proposal-id> --dao 0xYourDAO
Step 4: Validate Post-Change State¶
Confirm changes are reflected and no conflicting proposals remain active.
Safety Checklist¶
- Use conservative changes first, then iterate.
- Avoid overlapping membership proposals in the same voting window.
- Keep proposal descriptions explicit so voters understand blast radius.
- For team DAOs, verify multisig signer set before and after changes.