# Lampros DAO Delegate Communication Thread **URL:** \ **Category:** Delegate Statements\ **Tags:** delegation, delegate-statements\ **Created:** [September 5, 2024, 6:25am UTC](https://forum.arbitrum.foundation/t/lampros-dao-delegate-communication-thread/26642 "2024-09-05T06:25:53Z")\ **Posts on this page:** 1\ **Showing post:** 44
**Author:** ![Euphoria](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/euphoria/32/14303_2.png) [@Euphoria](https://forum.arbitrum.foundation/u/Euphoria)\ **Post date:** [September 2, 2025, 9:24am UTC](https://forum.arbitrum.foundation/t/lampros-dao-delegate-communication-thread/26642/44 "2025-09-02T09:24:11Z")
# Snapshot Votes * * * 1. **[[CONSTITUTIONAL] AIP: ArbOS Version 50 Dia](https://snapshot.box/#/s:arbitrumfoundation.eth/proposal/0x33754da4006d0ef38666ec5d5e85fd0966a891a594ab9dc21f23beedea2d330b/discussion)** **Voted - FOR** **Reason -** > [@\[CONSTITUTIONAL\] AIP: ArbOS Version 50 Dia](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/11): > > 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. > > Firstly, thank you to the @offchain team for putting this together and engaging in the thread. We read the post end-to-end and compared the changes against what builders on One and Nova depend on today. > > > [@\[CONSTITUTIONAL\] AIP: ArbOS Version 50 Dia](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/1): > > > > Dia adds support for relevant Execution Layer (EL) changes from Ethereum’s upcoming [Fusaka upgrade](https://eips.ethereum.org/EIPS/eip-7607) (Q4 2025), enabling [EIP-2537](https://eips.ethereum.org/EIPS/eip-2537), a few bug fixes, and a handful of new features, such as a new feature called Native Mint/Burn. > > We agree with the direction. Staying close to Ethereum reduces maintenance risk, and enabling BLS12-381 and CLZ brings real wins for developers. Keeping the pricing work to measurement only is also a prudent choice at this stage. > > > [@\[CONSTITUTIONAL\] AIP: ArbOS Version 50 Dia](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/1): > > > > For Arbitrum One & Arbitrum Nova we are proposing a 32 million gas limit (L2 execution gas, not including L1 gas) per transaction, which is the same as the current block gas limit. > > Since the per-transaction cap equals the block limit, we kindly ask for a short note with recent chain data to back this choice: P95 and P99 gas used per transaction over the last 90 days, any instances where a single transaction filled most of a block, and a brief check that large single transactions do not impact sequencing fairness. If these numbers show headroom, the 32M setting is easy to support; if they suggest pressure, we can discuss a safer margin now rather than later. > > > [@\[CONSTITUTIONAL\] AIP: ArbOS Version 50 Dia](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/1): > > > > A Constraint-Based Pricing Change: STF instrumentation to track multi-gas > > Measuring first is the right approach. To help everyone review before any later activation, it would be helpful to expose a minimal telemetry surface for the new counters (compute, storage access, storage growth, history growth), either via JSON-RPC or a Prometheus endpoint, and to share a short outline of the activation playbook when you return: which parameters can change, how changes would roll out, what checks define “go / no-go,” and how a revert would work if needed. This keeps the next step predictable for node operators and the DAO. > > > [@\[CONSTITUTIONAL\] AIP: ArbOS Version 50 Dia](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/1): > > > > Native Token Mint/Burn is proposed to be included in ArbOS 50 Dia for the benefit of Arbitrum Orbit chains > > We support including it in the codebase while keeping One and Nova unchanged. For completeness, please confirm there is no configuration path that could enable Mint/Burn on One or Nova in this release, and share the audit artifacts for the Dia diff when ready. For Orbit chains that opt in, a short operator checklist and the clean migration path if a bridge provider changes would be useful. A concise “assumptions matrix” that maps token/bridge choices to added trust would also help teams make informed decisions. > > > [@\[CONSTITUTIONAL\] AIP: ArbOS Version 50 Dia](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/1): > > > > **A few bug fixes** > > These fixes are welcome. A brief regression summary noting the test coverage and any expected effect on batch posting costs or node resource usage would make planning easier for infra teams. If there is no material impact, stating that clearly is helpful. > > We understand activation could land after Fusaka due to constitutional timings. That is fine if the audit report, the RC metrics snapshot, and the upgrade notes are public before Tally. * * * # Tally Votes * * * 1. **[[CONSTITUTIONAL] Remove Cost Cap, Update Executors, Disable Legacy USDT Bridge](https://www.tally.xyz/gov/arbitrum/proposal/51852039695020109312343918128899814224888993575448130385109956762385891284115?govId=eip155:42161:0xf07DeD9dC292157749B6Fd268E37DF6EA38395B9)** **Voted - FOR** **Reason -** > [@\[Constitutional\] AIP: Disable Legacy Tether Bridge](https://forum.arbitrum.foundation/t/constitutional-aip-disable-legacy-tether-bridge/29503/36): > > 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 Tally voting. > > The current on-chain proposal makes three sensible changes that improve sustainability, operations, and user safety. Removing the amortized cost cap on Arbitrum Nova aligns fees with real L1 posting costs after EIP-4844, ends a recurring subsidy, and fits Nova’s current role as Orbit adoption grows. Updating the DAO’s Upgrade Executors to include `executeCall()` reduces overhead for future upgrades while keeping `execute()` available, and the published Trail of Bits review on the new path gives comfort on security intent. Disabling the legacy USDT bridge and consolidating on USDT0 removes a source of confusion and edge-case risk for contracts that cannot handle the legacy auto-withdraw behavior. > > We also want to acknowledge [L2BEAT’s rationale](https://forum.arbitrum.foundation/t/constitutional-aip-disable-legacy-tether-bridge/29503/34) and thank them for their technical review of the executable payload. Their team confirmed that the targets and params match the stated intent, that the DAO addresses and ProxyAdmin references match the deployment list, that the correct Inbox contracts are used for Arbitrum One and Nova, and that the constitutional L1 timelock and delay align with the execution timeline. We value this kind of independent payload verification. We also note their point about the tradeoffs of bundling. In principle, we prefer single-topic on-chain votes when feasible. In this case, we believe the net effect of the bundle is clearly positive and supports the DAO’s long-term interests, so we are comfortable voting FOR while recognizing that some delegates have reservations about the USDT0 trust assumptions separate from this execution. > > The Nova change reduces deficits, the executor upgrade streamlines governance work, and the bridge change improves user safety. Taken together, the proposal strengthens the network’s sustainability and operational clarity. Hence, we will vote FOR. --- _[View the full topic](https://forum.arbitrum.foundation/t/lampros-dao-delegate-communication-thread/26642)._