Hey guys! Happy to throw my hat in the ring to participate as a community signer. Quick question. Will the multisig be a CLI-based multisig or would we be using a web UI like the Keplr multisig tool?
My responses to the application are below!
DAO-recognised name: RoboMcGobo
Country of residence & Timezone: US, EST
Affiliations: dYdX Ecosystem Development Program, Stride Labs, Osmosis Grants Program
Occupation: Full time web3. BD / Grants lead
Motivation for applying (max 3 sentences): The treasury subdao will largely be responsible for managing treasury delegations. I feel like I can add some experience here as I have a strong level of familiarity with Cosmos validators and common delegation practices. I also have a lot of experience sitting on multisigs and am familiar with multisig operations.
Contributions to Web3 (list, max 5 elements):
- Administration of Stride’s delegation program for a number of chains (incl. dYdX)
- Multiple governance contributions for chains like Osmosis, Stride, dYdX, and others.
- Helped bring a number of grantees to market at both dYdX and Osmosis.
Contributions to the dYdX protocol or DAO (list, max 5 elements):
- Community grantor at the dYdX Ecosystem Development Program.
- Worked with Stride to bring stDYDX to market and helped pursue integrations for liquid staked DYDX
- Wrote some early content in these forums introducing dYdX to the Cosmos ecosystem
Previous experience with operating Multi-sigs (list and brief explanation of each):
- (Former) Osmosis Grants Program Multisig: Custody of and disbursement of grant funding for the OGP.
- Osmosis liquidity subdao: Management of a subset of Osmosis treasury funds, and deployment into various protocol-owned liquidity usecases.
- Hydro Committee Multisig: Custody and management of Cosmos Hub protocol-owned liquidity via the Hydro auction protocol
- Various one-time multisigs for specific transactions across the Cosmos ecosystem.
Conflict of interest (if any): While I don’t perceive there being any current conflict of interest given the treasury subdao’s current mandate, there’s a possibility that in the future a conflict could arise if the subdao’s mandate expands to cover management of the stDYDX in the community treasury. This could create a conflict due to my employment with Stride Labs. If this were to occur, I’d simply screen myself from participating in any discussions or votes / signatures involving that position.
Thanks for the consideration! Happy to answer any additional questions as well 