GGP 3

Update Multisig Signatories and Policy for Treasury and Operational Wallets

Summary

This proposal seeks to update the composition of the Multisig Signatories (MS) for the Treasury Multisig Wallet and any additional operational wallets managed by Goldilocks DAO. The changes are necessary due to personnel changes and to implement a rotation system that ensures better operational efficiency when processing transactions.

The proposal maintains the 4-of-7 signature requirement while updating the signatory roster to reflect current active contributors and improve response times for transaction execution.

Abstract

Effective multisig management requires effective policy with active and responsive signatories. Due to personnel changes and the need for improved transaction processing efficiency, this proposal updates the current multisig composition and policy wording. The new structure will:

  • Replace inactive or departing signatories with active community members

  • Maintain decentralization while improving operational efficiency

  • Improve the policy statement for delegated authority around spending limits

Specification

Current Multisig Composition

The current multisig signatories as established in GGP-1 are:

  1. Ampnoob

  2. 0xGeeb

  3. Lezbrahh

  4. ServiceDAO

  5. Jani (THJ)

  6. Raito (Infrared)

  7. Beartic (Kodiak)

Current Policy Statement “Constraints will be placed on the MS delegations to ensure they are not able to move and execute transactions more than 10% of the treasury value in a month without approval via the relevant governance proposals.”

Proposed Changes - Signatories

Signatories to be removed:

  • Lezbrahh

  • Ratio (Infrared)

  • Beatic (Kodiak)

New signatories to be added:

  • JDP

  • Alma

  • DeFi Ted

Final proposed multisig composition:

  1. Ampnoob

  2. 0xGeeb

  3. DeFi Ted

  4. Alma

  5. Jani (THJ)

  6. ServiceDAO

  7. JDP

Proposed Changes - Policies

Suggested update to policy statement wording “Multisignatories that are delegated a spending authority will not be delegated more than 10% of the treasury operations funds for management of expenses and costs of operations on a per month basis”

Implementation Timeline

  • Upon proposal passing: New signatories will be onboarded

  • Within 48 hours: Transaction to update Safe multisig signatories will be prepared

  • Within 72 hours: Execution of signer changes on all affected wallets

Wallets

  1. Treasury Multisig Wallet Address: 0x4B7AF9a868fd9Cd55EDFc8E1402a545aDA1e31c6 Current threshold: 4 of 7 Proposed threshold: 4 of 7 (unchanged)

  2. Operations Multisig Wallet Address: 0xf5960b86048893bD25766c16aB6Da1aC628D97EE Current threshold: 4 of 7 Proposed threshold: 4 of 7 (unchanged)

  3. RFA Multisig Wallet Address: 0x3B0efb9E4165C56d5b1E8849b38426E1B5615593 Current threshold: 4 of 7 Proposed threshold: 4 of 7

Rationale

Inline with the Goldilocks DAO Governance charter, after an initial 6-month term governance proposals can be submitted to change composition of multisig members as required. With departing members on the multisig it's an opportunity to rotate some of the initial signers to those that can be more active in their participation and include coverage across all time zones. We thank all the signers for their contributions during the initial launch period.

The policy that defines the 10% of treasury transaction limit rule needs redefining as it relates to delegated approval amounts for execution outside of the multisig 4 of 7 where an individual signer is delegated a spending limit, namely to execute transaction for payments related to operational expenses.

GGP-3: Update Prior to Vote

Context Following a review during the RFC stage, it was identified that the Governance Contract had a shorter waiting and voting period applied in previous proposals than what was stated in the governance documentation. To ensure full alignment between the Governance Contract and the documented Governance Process, the following clarifications and adjustments are being added to GGP-3 before it proceeds to vote.

Governance Contract Parameters

The Governance Contract will be updated to: Confirm a 2-day Waiting Period (as per the existing process), and Adjust the Voting Period from 7 days to 5 days to reflect a technical limitation within the current voting contract (maximum ~5.6 days).

Governance Process Updates

GGP-3 will also modify the relevant sections of the Governance Process documentation as follows:

Phase 2: Governance Proposal

From:

Timeframe: Total 11 days

2-day Waiting Period

7-day Voting Period

2-day Timelock

To:

Timeframe: Total 9 days

2-day Waiting Period

5-day Voting Period

2-day Timelock

Under “Process Modifications”

From:

Changes to this governance process require:

Full three-phase process completion

7-day Voting Period

To:

Changes to this governance process require:

Full two-phase process completion

5-day Voting Period

Ratification of Previous Proposals

GGP-3 will also formally ratify all previously executed proposals that were processed using the shorter timeframes, ensuring they remain valid and consistent under the updated parameters.

Summary

This update to GGP-3:

  • Aligns on-chain governance parameters with documented process

  • Reflects the 5-day limit imposed by the current voting contract

  • Updates the wording of the modification process to reflect the two phases

  • Ratifies earlier proposals executed under shorter timeframes.

Executed Proposal

Last updated