TIP-32 Allocating ARB for ARC Multisig Setup and Operations Budget

Proposals Finalized TIPs
1

Summary

As a prominent participant in the Arbitrum ecosystem, Treasure acknowledges the significant responsibility it bears in advocating for the interests of the Treasure Community within Arbitrum, and concurrently, fostering the expansion and prosperity of the overarching Arbitrum DAO.

To fulfill this commitment, the Treasure core council recently established the ARC, a community led group consisting of members from both the Treasure and Arbitrum communities. This initiative aims to facilitate more proactive monitoring, engagement, and active participation in Arbitrum’s governance initiatives. This will allow Treasure core contributors to remain focused on ecosystem growth at Treasure, ensuring Arbitrum and Treasure can both win together.

To support the effective operational functioning of the ARC. This TIP requests 10,000 ARB in funding from the DAO to support:

  1. ARC Multisig Setup
  2. Flexible operational budget

Further details on the specific of these two items are displayed below:

1. ARC Multisig Setup on Hats

_Requested amount: 7,500 ARB (25% of overall cost, with Arbitrum Grant team funding the remaining 75%). Funds to be sent from the Treasure L2 treasury multisig (0x0eB5B03c0303f2F47cD81d7BE4275AF8Ed347576) to Haberdasher Labs multisig (0xc6fD290cFBCEfb7154a9357e410772e1EAb775a0) upon completion of implementation. Project Plan here. _

  • Current Treasury Configuration:
  • Votes within Treasure DAO are managed through its primary Treasury multisig: 0x0eB5B03c0303f2F47cD81d7BE4275AF8Ed347576.
  • The Treasury multisig oversees all funds and product smart contracts within Treasure DAO.
  • Challenges with Current Setup:
  • It’s impractical to add all ARC members as signers to the Treasury multisig.
  • Delegating votes already assigned to the Treasury multisig is not feasible.
  • Proposed Solution: Hats Implementation:
  • Introduce a Hats implementation where a new ARC multisig is endowed with specific permissions, enabling it to vote on behalf of Treasure DAO.
  • Risk Mitigation and Implementation Partner:
  • Engaging Haberdasher Labs, experts in web3 governance implementation and founders of the Hats protocol, to ensure a secure and effective setup.
  • Implementation Cost:
  • The total implementation cost for Haberdasher Labs 30,000 ARB with the Arbitrum Grants team committing to covering 22,500 ARB (75%) and Treasure Contributing 7,500 ARB (25%)
  • Further details
  • Encouraging individuals to review the comprehensive scoping proposal from Haberdasher Labs for a deeper understanding of the implementation’s intricacies.

2. Operations Budget

Requested amount: 2,500 ARB to be sent to the ARC managed multisig (address confirmed after Hats implementation complete)) from the Treasure L2 treasury multisig (0x0eB5B03c0303f2F47cD81d7BE4275AF8Ed347576).

  • Anticipated Operational Costs:
  • Minor operational expenses expected during the first cycle of ARC.
  • We anticipate potential ad-hoc expenses and ongoing costs for licenses and tooling for ARC representatives.
  • Need for a Flexible Budget:
  • Crucial for covering unexpected operational needs promptly and effectively without needing to go to Treasure DAO for each expenditure.
  • Prevents imposing ad-hoc payment burdens on ARC representatives.
  • Need to fund some ongoing tooling and licensing costs. For example, costs for an ARC Notion workspace are currently absorbed by one ARC representative.
  • Operational Budget Request:
  • Requesting 2,500 ARB from the DAO.
  • Intended to cover ongoing license costs and any ad-hoc operational expenditure during the first term of ARC.