# \[CONSTITUTIONAL\] AIP: ArbOS Version 50 Dia **URL:** \ **Category:** Finalized AIPs\ **Tags:** proposal\ **Created:** [August 19, 2025, 5:23pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835 "2025-08-19T17:23:09Z")\ **Posts on this page:** 19\ **Page:** 2
**Author:** ![gi0rgos](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/gi0rgos/32/14531_2.png) [@gi0rgos](https://forum.arbitrum.foundation/u/gi0rgos)\ **Post date:** [September 17, 2025, 11:14am UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/21 "2025-09-17T11:14:56Z")
Thanks a lot!! I got the first answer! As concerns the second I have read the whole discussion in Ehtereum Magicians and tried to understand the more I could! I appreciate your direct answer. ---
**Author:** ![offchain](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/offchain/32/16618_2.png) [@offchain](https://forum.arbitrum.foundation/u/offchain)\ **Post date:** [September 26, 2025, 5:35pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/22 "2025-09-26T17:35:28Z")
Noting a scope change: ArbOS 50 now introduces an “Effective Block Gas Limit,” defined as `MaxBlockGasLimit + MaxTxGasLimit`. This update has been incorporated into the post above. ---
**Author:** ![offchain](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/offchain/32/16618_2.png) [@offchain](https://forum.arbitrum.foundation/u/offchain)\ **Post date:** [September 29, 2025, 3:55pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/23 "2025-09-29T15:55:38Z")
Tentative timelines of this AIP were updated based on L1 Client releases on September 26th, and the the updated tentative timeline for L1 Fusaka upgrades provided in [All Core Devs Consensus (ACDC) Call #165 held on September 18th, 2025](https://ethereum-magicians.org/t/all-core-devs-consensus-acdc-165-september-18-2025/25351). ---
**Author:** ![GozmanGonzalez](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/gozmangonzalez/32/14717_2.png) [@GozmanGonzalez](https://forum.arbitrum.foundation/u/GozmanGonzalez)\ **Post date:** [September 29, 2025, 11:50pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/24 "2025-09-29T23:50:36Z")
> [@offchain](#): > > ## Abstract > > This AIP proposes to upgrade Arbitrum One and Arbitrum Nova to ArbOS 50 Dia. 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. > > While the goal of the proposed ArbOS 50 Dia upgrade is to eventually be available for adoption by any Arbitrum Chain, this proposal only concerns the Arbitrum One and Arbitrum Nova chains, as these two chains are governed by the ArbitrumDAO. On a high level, an ArbOS upgrade can be interpreted as Arbitrum’s equivalent of a hard fork - more can be read about the subject [here](https://forum.arbitrum.foundation/t/arbitrum-arbos-upgrades/19695). > > Please note that ArbOS Version 50 Dia is a proposed upgrade that builds upon ArbOS 40 Callisto, which has been previously adopted by the ArbitrumDAO - this proposal increments the version number to 50 instead of 4x due to technical details that allow for better Orbit chain customizability, as explained [here](https://docs.arbitrum.io/launch-orbit-chain/how-tos/arbos-upgrade#step-3-schedule-the-arbos-version-upgrade). > > ## Changes that will be included in ArbOS 50 Dia: > > **[EIP-7951](https://eips.ethereum.org/EIPS/eip-7951): Precompile for secp256r1 Curve Support** > > This EIP implements the same functionality and interface as [RIP-7212](https://github.com/ethereum/RIPs/blob/master/RIPS/rip-7212.md), which was activated as part of [ArbOS 31 Bianca](https://forum.arbitrum.foundation/t/aip-arbos-31-bianca-activation-of-arbitrum-stylus-rip-7212-support-nova-fee-router-proposal/25904). The main difference here is to add a point-at-infinity check and to update the comparison step in the signature verification algorithm. Developers should expect the same behavior as the EIP being proposed on Ethereum after Fusaka is activated. > > **[EIP-7825](https://eips.ethereum.org/EIPS/eip-7825): Transaction Gas Limit Cap** > > This EIP introduces a gas cap for individual transactions. The goal is to ensure fairer access to block space and improve network stability. 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. This 32 million gas limit diverges from the EIPs’ proposed limit of 16 million gas per transaction for Ethereum L1. Orbit chains can customize this value according to their chains’ needs. > > **[EIP-7642](https://eips.ethereum.org/EIPS/eip-7642): eth/69 - history expiry and simpler receipts** > > This networking upgrade removes deprecated fields used prior to Ethereum’s Proof of Stake (PoS) transition. We are including this EIP as part of GETH upstream. This is a networking change that impacts mainly L1 nodes. As arbitrum nodes do not have a P2P layer, we do not expect this to have any impact on arbitrum node operators. > > **[EIP-7939](https://eips.ethereum.org/EIPS/eip-7939): Count leading zeros (CLZ) opcode** > > This EIP adds a new CLZ (Count Leading Zeros) opcode to efficiently count the number of zero bits at the start of a 256-bit number. This is a fundamental mathematical operation used in many algorithms, especially for mathematical computations, data compression, and cryptographic operations. Currently, implementing this operation in Solidity requires complex and expensive code - this opcode makes it much cheaper and faster. > > **[EIP-7823](https://eips.ethereum.org/EIPS/eip-7823): Set upper bounds for MODEXP** > > This EIP introduces a 8192-bit (1024 byte) limit on each input to the MODEXP cryptographic precompile. MODEXP has been a source of consensus bugs due to unbounded inputs. By setting practical limits that cover real-world use cases (like RSA verification), this reduces the testing surface area and paves the way for future replacement with more efficient EVM code. > > **[EIP-7883](https://eips.ethereum.org/EIPS/eip-7883): ModExp Gas Cost Increase** > > This EIP increases the gas cost of the ModExp cryptographic precompile to address underpriced operations. It raises the minimum cost from 200 to 500 gas and doubles the costs for large inputs over 32 bytes. > > **[EIP-7910](https://eips.ethereum.org/EIPS/eip-7910): eth\_config JSON-RPC Method** > > This EIP provides a new RPC method that allows the Arbitrum Nitro node to respond with key configuration variables, offering node operators the ability to gain greater confidence that their Nitro nodes are correctly configured and prepared for upcoming forks. In future Nitro releases, we expect to include additional fields specific to Arbitrum chains. This update is at the RPC level and may be enabled later than the ArbOS 50 Dia upgrade. > > **Enable [EIP-2537](https://eips.ethereum.org/EIPS/eip-2537): Precompile for BLS12-381 curve operations** > > As [disclosed previously](https://forum.arbitrum.foundation/t/disclosure-of-support-for-eip-2537-on-arbitrum-one-and-nova/29720), the precompiled contracts for performing various operations over the BLS12-381 elliptic curve, including BLS signature verification, were added but not properly enabled in [ArbOS 40 Callisto](https://docs.arbitrum.io/run-arbitrum-node/arbos-releases/arbos40) as originally expected. ArbOS 50 Dia will now enable EIP-2537. > > **ArbOS Block Limit Change “Effective Block Gas Limit”** > > Since ArbOS 50 introduces a `MaxTxGasLimit`, the State Transition Function (STF) will be relaxed in ArbOS 50 to allow the final transaction in a block to use up to the `MaxTxGasLimit` even if it would cause the block to exceed `MaxBlockGasLimit`. This means that the “Effective Block Gas Limit” is really `MaxBlockGasLimit + MaxTxGasLimit`. In previous versions of ArbOS, the sequencer would skip transactions if the transaction request’s `GasLimit` minus the L1 data posting gas exceeded the gas remaining in the block. > > The new algorithm is more efficient because the sequencer doesn’t need to keep searching through the queue of transactions to find one that fits in the remaining block gas, and can continue to add transactions until the unused block gas is 0. > > This change does not affect the `GasTarget`, and therefore does not affect how much overall gas per second the chain will use - only how transactions using that gas could be divided between different blocks. > > **A few bug fixes** > > - ArbOS Didn’t Get Updated For L1 Calldata Price Increase > - This change standardizes the calculation of gas units for compressed batch calldata across the codebase by replacing hard-coded values with a method call (tokenGasUnits). > > - EIP-7702 Precompile Delegation Behavior Divergence > - Previously, calls to precompiles could execute an INVALID opcode instead of succeeding with no execution. ArbOS 50 Dia will update code to align with EIP-7702 spec to treat precompile code as empty during delegation. > > **A Constraint-Based Pricing Change: STF instrumentation to track multi-gas** > > We have instrumented Arbitrum’s State Transition Function (STF) to track gas usage across multiple resource types including computation, storage access, storage growth, and history growth, rather than only a single total based on opcodes. This work lays the foundation for dynamic, constraint-based pricing where gas fees can adjust based on the most constrained resource at the network level. The goal is to create more stable prices, improve responsiveness to spikes, and allow the network to safely increase throughput without overloading node hardware. In this release, none of the constraints are enabled, so there will be no impact on current gas prices. This update simply adds the ability to measure and record per-resource usage, with actual pricing changes coming in a later version once constraints are configured, benchmarked and tested. > > To read more about this feature, go [here](https://blog.arbitrum.io/dynamic-pricing-explainer/). > > **Native Token Mint/Burn** > > Native Token Mint/Burn is a feature that allows Arbitrum chains to use interoperability-enabled token standards (e.g., LayerZero OFTs, xERC20s, native USDC) as native gas tokens on their chains. Currently, Arbitrum chains are designed to “lock and mint” native gas tokens on the chain’s canonical bridge. However, doing so means that these “locked and minted” native gas tokens cannot interact with third-party cross-chain adapter contracts. This new feature lets an Arbitrum chain delegate minting and burning of its native gas token to a trusted bridge provider (e.g., LayerZero OFT). > > Native Token Mint/Burn is proposed to be included in ArbOS 50 Dia for the benefit of Arbitrum Orbit chains (reducing the need for forks) and to streamline development and testing into a single codebase. There are no plans to enable this feature on Arbitrum One or Arbitrum Nova, consequently this feature will be explicitly left disabled for Arbitrum One and Arbitrum Nova. > > To read more about this feature, go [here](https://arbitrum.notion.site/Enable-Native-Mint-Burn-for-your-chain-s-gas-token-22601a3f59f880be9b99d3d55f982a17). > > ## Fusaka EIPs that are not proposed to be in ArbOS 50 Dia > > Support and implementation for the following EIPs are not planned to be part of ArbOS 50 Dia: > > - [EIP-7594](https://eips.ethereum.org/EIPS/eip-7594), [EIP-7918](https://eips.ethereum.org/EIPS/eip-7918), and [EIP-7892](https://eips.ethereum.org/EIPS/eip-7892), since Arbitrum chains do not have blob data markets (though they do support _posting_ blob data to a non-Arbitrum parent chain) > - [EIP-7917](https://eips.ethereum.org/EIPS/eip-7917), since Arbitrum chains do not have a beacon chain and therefore do not have a peer-to-peer layer like Ethereum does > - [EIP-7934](https://eips.ethereum.org/EIPS/eip-7934), this EIP is to help propagating blocks between nodes. Arbitrum doesn’t do that - it sends messages (which are limited) and each node builds every block by itself > - [EIP-7907](https://eips.ethereum.org/EIPS/eip-7907), since this EIP is no longer Scheduled For Inclusion (SFI) for Fusaka, as agreed upon by client teams during [ACDE #216](https://ethereum-magicians.org/t/allcoredevs-execution-acde-216-july-17-2025/24770/2) on July 17, 2025. We are currently exploring alternative ways to increase the contract size limit that do not interfere with the ability for Arbitrum chains to support EIP-7907 in the future. Please see this [forum post reply](https://forum.arbitrum.foundation/t/non-constitutional-proposal-to-direct-the-arbitrum-foundation-to-implement-an-extended-version-of-eip-7907-and-for-the-dao-to-ratify-its-deployment-on-arbitrum-one/29375/3) for more details about this. > - [EIP-7935](https://eips.ethereum.org/EIPS/eip-7935), since Arbitrum chains already have a default gas target of 28Mgas/s and we have separate, alternative plans for increasing the gas limit through other means, as mentioned [here](https://blog.arbitrum.io/scaling-arbitrum-everywhere/). > > ## Steps to implement > > More detailed information about the specific implementation and versions will be provided closer to the date of the formal on-chain Tally vote. However, this proposal will roughly follow the steps below: > > 1. An AIP outlining the proposed upgrade and specification is proposed to the ArbitrumDAO forum for discussion (this post); > 2. A temperature check vote is held on Snapshot; > 3. Engineering work to scope out and implement the relevant changes for ArbOS 50 Dia into the Nitro node software, relevant rollup contracts, and associated upgrade actions (this work has already begun); > 4. A new version of Nitro and nitro-contracts, if necessary, are released that support ArbOS 50 Dia; > 5. A security audit of all ArbOS 50 Dia relevant changes is conducted by a third-party (Trail of Bits) and the audit report is published for public consumption; > 6. Should the Snapshot vote pass, ArbOS 50 Dia will be deployed to both private devnets & Arbitrum Sepolia for testing; > 7. A formal AIP is proposed to Tally for an on-chain vote; > 8. If the on-chain vote passes, ArbOS 50 Dia will be activated on Arbitrum One and on Arbitrum Nova following the required waiting periods and phases, as outlined in the [ArbitrumDAO Constitution](https://docs.arbitrum.foundation/concepts/lifecycle-anatomy-aip-proposal). > > **Note on Fusaka hard fork timelines:** > > Similar to the [ArbOS 20 Atlas upgrade](https://docs.arbitrum.io/run-arbitrum-node/arbos-releases/arbos20) and the [Ethereum Dencun hard fork](https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement) in March 2024, the activation timestamp for ArbOS 50 Dia will be targeted for roughly the same timestamp as when Ethereum Mainnet hard forks. At the time of writing and as of the latest [All Core Devs Consensus (ACDC) Call #165 held on September 18th, 2025](https://ethereum-magicians.org/t/all-core-devs-consensus-acdc-165-september-18-2025/25351), the tentative timestamp of the Ethereum Mainnet fork for Fusaka is targeted for the first week of December 2025. The tentative dates for Ethereum Sepolia and Ethereum Hoodi to upgrade to Fusaka are around mid October and late October, respectively. The exact slot for mainnet Ethereum has not yet been chosen. > > Given that the L1 client teams released their Fusaka-supported versions on September 26, 2025 and that the required steps for a [Constitutional AIP can take more than 35 days](https://docs.arbitrum.foundation/concepts/lifecycle-anatomy-aip-proposal) from when it is posted to Tally, there is a likelihood that ArbOS 50 Dia will be activated on Arbitrum One and Arbitrum Nova _after_ Ethereum Mainnet upgrades to Fusaka (if the ArbitrumDAO votes to adopt this proposal). We endeavor to continue making updates to this proposal as timelines become more concrete. This looks like a big step forward. I like how ArbOS 50 Dia lines up with Ethereum’s Fusaka upgrade while also adding things that directly improve how Arbitrum runs. The gas limit cap and the efficiency tweaks make a lot of sense, and enabling EIP-2537 feels long overdue. The Native Mint/Burn feature is also a smart move for Orbit chains. Excited to see how this upgrade smooths things out for both devs and users. ---
**Author:** ![shogun](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/shogun/32/1651_2.png) [@shogun](https://forum.arbitrum.foundation/u/shogun)\ **Post date:** [October 6, 2025, 1:10pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/25 "2025-10-06T13:10:04Z")
_ **The following reflects the views of GMX’s Governance Committee, and is based on the combined research, evaluation, consensus, and ideation of various committee members.** _ We value the development progress of ArbOS 50 Dia’s introduction in incorporating Fusaka EIP’s. We approved this proposal, and have no qualms with the most recent changes on activating these changes to both Arbitrum Nova and One. ---
**Author:** ![paulofonseca](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/paulofonseca/32/15551_2.png) [@paulofonseca](https://forum.arbitrum.foundation/u/paulofonseca)\ **Post date:** [October 16, 2025, 5:33pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/26 "2025-10-16T17:33:48Z")
voted **Against** on this past offchain vote because there hasn’t been enough discussion on this proposal… it’s way too soon to bring it to a vote. ---
**Author:** ![offchain](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/offchain/32/16618_2.png) [@offchain](https://forum.arbitrum.foundation/u/offchain)\ **Post date:** [October 24, 2025, 6:26pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/27 "2025-10-24T18:26:49Z")
We have added a new fix to accompany ArbOS50 Version Dia. This forum post has been updated. ---
**Author:** ![paulofonseca](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/paulofonseca/32/15551_2.png) [@paulofonseca](https://forum.arbitrum.foundation/u/paulofonseca)\ **Post date:** [December 4, 2025, 9:59am UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/28 "2025-12-04T09:59:02Z")
did anyone independently validated the payload of this [onchain proposal](https://www.tally.xyz/gov/arbitrum/proposal/53154361738756237993090798888616593723057470462495169047773178676976253908001?govId=eip155:42161:0xf07DeD9dC292157749B6Fd268E37DF6EA38395B9)? specifically, the fact that it only does what both of these two proposals say it should? [https://snapshot.box/#/s:arbitrumfoundation.eth/proposal/0x33754da4006d0ef38666ec5d5e85fd0966a891a594ab9dc21f23beedea2d330b](https://snapshot.box/#/s:arbitrumfoundation.eth/proposal/0x33754da4006d0ef38666ec5d5e85fd0966a891a594ab9dc21f23beedea2d330b) [https://snapshot.box/#/s:arbitrumfoundation.eth/proposal/0x4a96a91d162975de0d402b83ca8b8a24e808ca357150120fc0d44ae0bf1cc4a5](https://snapshot.box/#/s:arbitrumfoundation.eth/proposal/0x4a96a91d162975de0d402b83ca8b8a24e808ca357150120fc0d44ae0bf1cc4a5) @offchain @krst et all? ---
**Author:** ![krst](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/krst/32/1357_2.png) [@krst](https://forum.arbitrum.foundation/u/krst)\ **Post date:** [December 4, 2025, 10:39am UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/29 "2025-12-04T10:39:41Z")
We will be validating it next week. ---
**Author:** ![paulofonseca](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/paulofonseca/32/15551_2.png) [@paulofonseca](https://forum.arbitrum.foundation/u/paulofonseca)\ **Post date:** [December 4, 2025, 10:46am UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/30 "2025-12-04T10:46:00Z")
Thank you! And just to note that, any vote from delegates that haven’t validated the payload themselves, is a bit irresponsible. Since I can’t validate it myself, I’ll wait for L2BEAT’s assessment before casting my vote. ---
**Author:** ![offchain](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/offchain/32/16618_2.png) [@offchain](https://forum.arbitrum.foundation/u/offchain)\ **Post date:** [December 4, 2025, 10:31pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/31 "2025-12-04T22:31:37Z")
Thanks for raising this. Offchain Labs has independently validated the payload to ensure it matches the intent and scope described in the two Snapshot approvals. For transparency, the payload-generation steps, simulation outputs, and code-diff verification instructions are publicly documented here: • **Payload generation + simulation results** : [https://github.com/ArbitrumFoundation/governance/pull/366](https://github.com/ArbitrumFoundation/governance/pull/366) • **ArbOS 51 code-difference verification guide** : [https://arbitrum.notion.site/Verifying-the-ArbOS-51-Code-Difference-2a501a3f59f8804cb0a0f9a460020a9d](https://arbitrum.notion.site/Verifying-the-ArbOS-51-Code-Difference-2a501a3f59f8804cb0a0f9a460020a9d). We encourage all delegates to perform their own verification. ---
**Author:** ![Zeptimus](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/zeptimus/32/5471_2.png) [@Zeptimus](https://forum.arbitrum.foundation/u/Zeptimus)\ **Post date:** [December 10, 2025, 10:25am UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/32 "2025-12-10T10:25:26Z")
Voting in favor on tally. This is a maintenance proposal and making sure Arbitrum can work with future Ethereum updates. Even though I’m not technical, I can see why it matters to keep ArbOS in line with Ethereum and trust offchainlabs execution. ---
**Author:** ![gi0rgos](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/gi0rgos/32/14531_2.png) [@gi0rgos](https://forum.arbitrum.foundation/u/gi0rgos)\ **Post date:** [December 10, 2025, 3:38pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/33 "2025-12-10T15:38:40Z")
Thank you for the proposal. Since @offchain validated the payload, I am going to vote. Aligned with all the other ArbOS proposals my vote is going to be **FOR**. I do not have something important to add here, so I am keeping it short to avoid noise creation. ---
**Author:** ![dzack23](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/dzack23/32/746_2.png) [@dzack23](https://forum.arbitrum.foundation/u/dzack23)\ **Post date:** [December 11, 2025, 5:27pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/34 "2025-12-11T17:27:32Z")
Verified state changes with governance seatbelt, all looks good and consistent with proposal (and matches shared reports here: [https://github.com/ArbitrumFoundation/governance/pull/366](https://github.com/ArbitrumFoundation/governance/pull/366) ) Voting **For** ---
**Author:** ![Griff](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/griff/32/964_2.png) [@Griff](https://forum.arbitrum.foundation/u/Griff)\ **Post date:** [December 15, 2025, 8:50pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/35 "2025-12-15T20:50:59Z")
Voted yes on both tally and snapshot I’m supporting this upgrade because it keeps us aligned with Ethereum while adding some smart optimizations for Arbitrum. ---
**Author:** ![0xDonPepe](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/0xdonpepe/32/5989_2.png) [@0xDonPepe](https://forum.arbitrum.foundation/u/0xDonPepe)\ **Post date:** [December 15, 2025, 9:11pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/36 "2025-12-15T21:11:30Z")
I voted FOR as this proposal implements necessary data availability improvements at the protocol level, strengthening Arbitrum’s core infrastructure in line with the DAO’s constitutional process. ---
**Author:** ![yoavw](https://avatars.discourse-cdn.com/v4/letter/y/ad7895/32.png) [@yoavw](https://forum.arbitrum.foundation/u/yoavw)\ **Post date:** [December 16, 2025, 1:01pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/37 "2025-12-16T13:01:05Z")
I voted FOR this proposal because it improves Arbitrum and keeps it aligned with Ethereum. ---
**Author:** ![paulofonseca](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/paulofonseca/32/15551_2.png) [@paulofonseca](https://forum.arbitrum.foundation/u/paulofonseca)\ **Post date:** [December 16, 2025, 10:18pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/38 "2025-12-16T22:18:33Z")
voting For on the current onchain vote because this keeps Arbitrum aligned with Ethereum, as it should be. ---
**Author:** ![mihal](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/mihal/32/1365_2.png) [@mihal](https://forum.arbitrum.foundation/u/mihal)\ **Post date:** [December 18, 2025, 6:45pm UTC](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835/39 "2025-12-18T18:45:03Z")
Voting For as this seems like a no-brainer update to optimize Arbitrum and maintain Ethereum alignment. [Previous page](https://forum.arbitrum.foundation/t/constitutional-aip-arbos-version-50-dia/29835.md?page=1)