Voting FOR the proposal
The vote in the temperature check is not a statement that this proposal is perfect but that in this multistage process, it has the likely potential to have my approval in the next stage when that is posted, including accounting for the feedback that they have provided during the forum discussion and snapshot phases.
For a moment before going into the rationale, let me touch on conflicts, being a core contributor to GMX handling integrations and ecosystem, advisor to Camelot, and more generally, an investor, advisor, and token holder in over 20 Arbitrum protocols listed across multiple DEXs, perceived or actual conflicts of interests will exist. I think itâs better to disclose our potential biases and let people view our comments through that lens; this should apply to builders and all Delegates that may have perceived or actual competing interests.
Camelot has been at the forefront of bringing new protocols into the ecosystem, putting in the groundwork needed to help the chain grow:
Showcasing Arbitrum as a builder-friendly environment.
Giving them visibility to one of the largest communities on Arbitrum and to the communities of the fellow round table members
It links Builders to potential partners across the chains to collaborate (including those outside Camelot).
It supports them with tools built on the DEX that help protocols better manage liquidity, incentives, and community staking.
I believe unequivocally that as a chain and a DAO, we canât afford to wait; time may be our most valuable commodity, and we canât get it back. In the meantime, all other ecosystems and their leadership want to capture the next generation of builders and users and poach existing ones from Arbitrum, depriving us of the momentum built over the last two years.
Suppose there are no incentives, especially those that help existing protocols or those deploying new protocols on Arbitrum. There is a distinct case to make for supporting native protocols, now and in the future; multi-chain DEX view Arbitrum simply as another software deployment without putting in the time and human capital of growing this specific chain and ecosystem; for them, lesser growth on Arbitrum is just redistributed by that same growth moving to another chain which better supported builders and users. That doesnât mean we shouldnât evaluate a multi-recipient grant framework, but we shouldnât ignore the difference in objectives either.
This proposal will likely fail despite supportive statements by many voting against it or abstaining, with the main articulated reason being a direct request to the Arbitrum Dao rather than via a framework (that does not exist). Please take a moment to reflect that the proposers of other frameworks (Foundation, Quest book, and Plurality) have stated that this proposal does not specifically fit into their frameworks and is complimentary to their efforts. The Foundation even explicitly said in their recent blog post that proposals should come to the DAO per the Arbitrum Constitution. Before Camelot posted this proposal, the existence of such a framework for on-chain liquidity programs had yet to be discussed, commissioned, or previously made a priority by the DAO or Foundation.
I believe that the DAO should consider frameworks but deciding not to proceed with a proposal and effectively stop growth efforts is a mistake, given that itâs possible to do both things simultaneously.
While the post above is in my capacity as a Delegate, separately as a contributor at GMX, Iâm left highly confused with how our protocol should engage with the DAO. We have built partnerships and integrations across the chain, with countless protocols built on top of us and relying on us. We have been preparing to engage the DAO directly for support on our V2. Still, in the last few days, the most prominent delegates have articulated that direct proposals should not come to the DAO, liquidity incentives donât contribute positively to the chainâs growth, and Builders should not be permitted to vote for their interest. These comments have left me struggling to understand what role the DAO sees for Builders.
Irrespective of where people stand on Camelotâs proposal, it would be ideal to start a separate discussion to know if the DAO sees any urgency in resolving these matters and understand if Arbitrum DAO will aggressively support, defend and invest in keeping Arbitrum the preferred home for DeFi in the Ethereum ecosystem.
Finally, as a delegate, I focused on the work, making myself regularly available, maintaining frequent dialogue with the Foundation and Off-Chain labs who support them, attending community calls, and providing feedback to submitters of every proposal through chat and direct calls. I wasnât active in our governance forum, which was a shortcoming; I will endeavor to do better, although Iâll probably leave Twitter mostly for others. If we want to improve Arbitrum, we canât wait for others to do the work WE are Arbitrum.
coinflipcanada
Arbitrum Delegate
core contributor GMX