TempeTechie.eth Delegate Communication Thread

NOVEMBER 2024

Snapshot:

Snapshot Proposal: Adopt a Delegate Code of Conduct & Formalize Operations
Voted: FOR
Reasoning (link):

I vote FOR the proposal. I don’t see any issues with it, and I believe it’s good for the DAO.

As for the Shielded Vote that olimpio mentioned, I think the will of the voters was clear - they support the shielded vote (56.69% approval). The difference in interpretation of this vote may arise from whether you’re more familiar with the “first-past-the-post” voting system or with the “proportional” voting system. Personally, I believe the proportional system better represents the will of the voters, which means it’s fair to sum up the total votes in favor of the shielded vote.

Snapshot Proposal: [Non-Constitutional] Treasury Management v1.2
Voted: FOR
Reasoning (link):

I am generally in favour of the idea of the proposal, but I agree with Tekr0x.eth that we should see a more precise plan (or guardrails) for selling ARB for stablecoins.

One idea is to have a daily limit (as percentage of ARB volume) on ARBs sold. Another is to perhaps also sell part of ETH, not just ARB. And also to extend the timeline of selling ARB (3 months may be too short if we don’t want to impact the price too much).

I also echo 404DAO’s suggestion of having only one committee instead of two.

That said, I’m voting FOR the proposal in the Snapshot voting. But I’d need the changes I mentioned (especially the guardrails for selling ARB) to be implemented in the proposal before supporting it in the Tally vote.

+an update after I asked a question on the Governance Call:

Updating my thoughts based on the feedback by Sam Martin on today’s Governance call.

As per Sam, Entropy will not define in the Tally proposal how exactly ARB will be liquidated for stablecoins. Instead, this will be a task for the TMC committee after (if) the Tally vote passes.

The good thing is that TMC will put their plan of ARB liquidation on the Snapshot vote, so if DAO members don’t agree with it, ARB will not get liquidated in that way.

To me, this is sufficient enough, so I plan to vote FOR the proposal on Tally.

Snapshot proposal: Restitution For Extensively Delayed ArbitrumDAO Minigrant Winners
Voted: AGAINST
Reasoning (link):

Too long delay in ARB payouts is very unfortunate and understandably painful for recipients. But the grant rules were clear about the payment being in ARB tokens. As chamadao said, the proposed restitution would create a dangerous precedent. For that reason, I vote against the proposal.

Snapshot proposal: Hackathon Continuation Program
Voted: FOR
Reasoning (link):

I voted FOR the proposal. I think it’s good to experiment with a program that helps the best hackathon projects grow and succeed even after the hackathon is over.

If this program proves to be successful, it would make sense to do a v2 of the program, but this time perhaps including finalists from past ETHGlobal hackathons. This would create a larger pool of high-quality projects and bring promising teams and developers to the Arbitrum ecosystem.


Tally:

Tally Proposal: (V2) Arbitrum Research & Development Collective
Voted: FOR
Reasoning (link):

I voted FOR this proposal on Tally, especially based on how well ARDC v1 performed with the STIP analysis. The proposed budget is the lowest among the choices that were listed in Snapshot, but I’m sure the DAO could provide some additional funds (through a new proposal) if the need for that will arise.

Tally Proposal: Establishing a DAO Events Budget for 2025
Voted: FOR
Reasoning (link):

I voted FOR this proposal on Tally. I think it provides a better system of organizing and funding DAO-related events.

As for whether to organize an Arbitrum-specific event not attached to any other conference, I think this sounds better on paper than in reality (at this point). I see for myself that when I travel to attend a crypto event, I choose to attend large conferences with many (side) events rather than to attend a smaller specific event with no other events around it (because it’s easier to justify the personal travel cost of attending a larger conference with side events). In the future, when the Arbitrum community grows, it could have its own major conference, but for now, let’s stick with side events attached to some major conference (e.g. an Ethereum conference or a non-crypto conference like krst from L2Beat proposed).


Governance calls in November:

  • I attended the bi-weekly Arbitrum governance call on 19 November 2024.
  • I did not attend the previous call on 5 November due to traveling to Thailand for Devcon 2024.