Multi-Sig

Multisig Governance (Gnosis Safe)

The Gnosis Safe multisig serves as the primary governance authority for the Steakhouse ecosystem. It acts as the owner, deployer, and treasury controller across all deployed contracts on each network, ensuring that no single entity can unilaterally modify protocol configurations or move ecosystem funds.

---

Purpose

The multisig provides collective control and accountability for all privileged operations across the Steakhouse system. It replaces individual admin wallets with a decentralized, multi-approval flow for executing governance, upgrades, and treasury management.

Core Goals

• Decentralized Safety: No single private key can alter system parameters or withdraw funds.

• Transparent Governance: All signed actions are visible on-chain via Gnosis Safe transaction history.

• Timelock Integration: The multisig queues privileged updates through the KitchenTimelock, adding a 48-hour public buffer before any change takes effect.

• Cross-Chain Consistency: The same multisig address (or Safe instance) governs deployments on Ethereum, BSC, Arbitrum, and Base.

---

Roles & Responsibilities

Role	Description
Multisig Safe	Primary owner of all deployed Steakhouse contracts. Executes timelocked updates and controls the treasury.
Timelock Contract	Enforces a mandatory 48-hour waiting period before any Safe-initiated update is applied.
Signers	Human or institutional signatories responsible for approving transactions. A majority (M-of-N) threshold must sign to execute.
Treasury Splitter (future)	A downstream contract that will automatically split ETH or BNB inflows among dev, marketing, and ecosystem wallets post-launch.

---

Multisig Setup

Each chain (ETH, BSC, ARB, BASE) uses a corresponding Gnosis Safe instance, deployed with identical signer sets and thresholds. The Safe is configured as:

• Owner: For all core contracts (Kitchen, Factory, BondingCurve, Graduation, Storage, etc.)

• Co-owner: Receives all protocol fees, creation costs, and LP lock payments.

• Deployer: Deploys new modules and upgrades, subject to Timelock governance.

Signers Table

Signer	Role	Address (All EVM)	Description	ENS
Signer 1	Cold Storage Wallet	0x9Cb7B9e1FAcb34885B2E9c5a15d204117Ea5Ae07	Main admin key (Ecosystem + technical keyholder)	mrare.eth
Signer 2	Primary Dev / Governance	0x8aC41Ff10d6465d4B5ecAD8b5A9931264f7B73A2	Manages treasury and fund flow	steaktech.eth
Signer 3	Secondary Dev, Co-Founder / Governance	0xa06b13d486E1e79bE729084707807678D73B1aE2	Secondary governance signer	tbonesteak.eth
Multi-sig	Deployer / Treasury	0x8e4fE6714DbA018B6696EA50a74Ea63c3d01a41f	The ecosystrem controller ⅔ signers required	steakhousefinance.eth

Example Governance Flow

1. Proposal Queued: A signer proposes a configuration change (e.g., new Factory address).

2. Multisig Confirmation: At least 2 of 3 signers approve the transaction inside the Safe.

3. Timelock Queue: The Safe executes a queueTimelock() transaction to schedule the update (48h delay).

4. Execution: After the delay, the Safe calls executeTimelock() to finalize the change.

5. Event Transparency: All steps emit TimelockQueued and TimelockExecuted events for verifiable, public on-chain auditing.