* Protocol Guild has a preference for using "off-the-shelf" components versus deploying custom software. However, because there aren't off-the-shelf solutions to many of the problems they've had to solve, they've ended up deploying some custom contracts so far, in collaboration with teams like 0xSplits and DAOHaus.

* For Season 3, they want to move away from using a multi-sig because there is too much power and security risk tied to a few addresses. Therefore they are working with DAOHaus to deploy a custom Moloch V3 contract for governance.
They are not using many of the features of Moloch V3, including tributes or loot shares and therefore are using it a bit differently from how it is normally used -- in particular, more similar to Gnosis safe for basic member voting.
One thing that PG likes about Moloch versus Safe is that it allows better epoch-based governance of proposals. With Safe, proposals never expire and all members can vote on them. With Moloch V3, votes on a proposal are tied to a snapshot of the governance rights at the time, and the voting has an end-date by default.

* Vesting (streaming) is very important to PG. And in fact they even prefer a "strong" form of vesting, where tokens are locked to be given, but are distributed over time and cannot be clawed-back by the funder. We discussed how this could possibly be accomplished by having the funder do a give to an intermidiary account, also controlled by PG, which would then stream to their Splits configuration over time.

* PG likes 0xSplits overall, but has had two main problems so far:
1) Gas fees are high
2) If they want to replicate onto L2s they end up with a different contract address (new 0xSplits contracts) on each L2.

* The biggest operational problems they have are:
* Management (updating especially) of the member list is a pain.
* Moving funds from L2s to mainnet, or otherwise getting them to members is a pain.

* Architecturally, the member list will be replicated in 3 places in season 3: (1) the 0xSplits contract, (2) a custom registry contract which functions as the main source of truth for member changes and shares over time (3) the Moloch V3 governance contracts. This architecture adds a lot of complexity but seems necessary to them based on their requirements for now.

* Here are some resources from the the PG infrastructure that they suggested we should check out if we would like to learn more:

Contracts Repo: https://github.com/HausDAO/protocol-guild-contracts
Registry Repo (not sure if still being used): https://github.com/HausDAO/baal-shamans/tree/feat/memberRegistry/contracts/memberRegistry

Frontend UI: https://playground.daohaus.eth.limo/
Frontend Repo: https://github.com/HausDAO/protocol-guild