Arbitrum Treasury Management Council - Consolidating Efforts

The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.

We are voting FOR this proposal in the Snapshot voting.

We believe merging the TMC, GMC, and STEP into one council is the right move for Arbitrum’s treasury. We believe this new Council design addresses many of the pain points that arose under TMC, GMC, and STEP. It’s encouraging to see that leftover funds will be used smartly for specialist help where needed, without creating new salaries.

That said, while we support the direction, we want to share some thoughts:

We see this point and agree with what others like @bertani mentioned, the OAT was not originally designed for financial oversight. Over time, it may make sense for the Council to help the OAT develop stronger treasury literacy or bring in a neutral advisor for more technical allocation checks.

We appreciate this clarity and also agree with @Camelot that balancing yield and growth is always a tricky dance. It would be helpful if the Council could share, maybe in future budget requests, a simple rubric that explains when we intentionally lean more toward ecosystem growth vs strict APR targets.

We like the move away from just Dune dashboards. A question: could we have a clear service level for this? For example, that major treasury movements get reflected within 24 hours, and quarterly reports come out within 15 days after each quarter ends. This sets shared expectations for everyone.

We echo this too. It’s good to see the plan to post rationales for SP choices. One practical idea: maybe an open shortlisting or lightweight RFP for big vendor hires could build trust, without adding too much friction.

This works as a hard backstop, but it might help the DAO if we also had a softer option. For example, if there’s a major reallocation, say 10% of AUM or more, perhaps the Council could post it and allow a 5-day comment window before execution.

Finally, we want to echo what @Jose_StableLab suggested, a short post-mortem covering lessons learned from TMC, GMC, and STEP would be really valuable. It would help new contributors understand which parts worked and which bottlenecks to avoid as we shift to this single council.

Overall, we see this as an overdue cleanup that gives the DAO more cohesion and clearer checks than what we had before.

2 Likes