Voting FOR the proposal due to its critical UX enhancements for Arbitrum users, essential for maintaining competitiveness. However, I share concerns that implementation should have been planned with greater foresight.
As in @web3citizenxyz representation, voting FOR.
The following reflects the views of L2BEAT’s governance team, composed of @krst, @Sinkas, and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.
We previously supported the proposal during the temp-check vote while committing to verifying the executable payload once the proposal went for an onchain vote. We asked our research team to once again look into the proposal and verify its contents before we cast our vote.
As outlined, the proposal’s execution will only introduce the changes described, which is adding support for the relevant EIPs that are mentioned. Our research team also verified that the WASM root in the proposal corresponds to the one from the stated node repository commit.
With that in mind, and since the issue found in the security audit has been resolved, we’re voting in favor of the proposal.
We vote for this proposal.
We voted for the measure at the Snapshot vote and continue to support it because EIP-7702 account abstraction and the new BLS12-381 precompiles will materially improve developer flexibility and end-user experience. Timely alignment with Ethereum avoids fragmentation, preserves shared security assumptions, and ensures applications can rely on consistent functionality across layers.
This is the first proposal where I find myself genuinely torn. It contains several technical details that are hard for one person to fully assess — especially for someone like me who doesn’t come from a developer background.
From what I’ve gathered through the discussion and the proposal itself, this seems to be a meaningful improvement for Arbitrum, leveraging work already done on Ethereum. In that sense, we are adopting a ready-made enhancement.
Based on that, I’m leaning FOR. Still, I recognize that this proposal demands further study — especially on my part. I’ll continue reading and learning to better understand the full implications.
Vote Summary
FOR: 185
AGAINST: 2
ABSTAIN: 1
Overwhelmingly Supported
Summary of the Rationales
• Almost every voter came forward stating “true” – indicating strong overall support for the Callisto upgrade.
• The minimal amount of dissenting “false” votes suggest some reservations but lacked any detailed technical criticism.
• In essence, the proponents believe that ArbOS 40 “Callisto” is a necessary, forward‐looking upgrade that aligns Arbitrum with Ethereum’s imminent Pectra upgrade and improves functionality (via EIP‑7702, EIP‑2537, and EIP‑2935).
Most Compelling Arguments
In Favor:
– The upgrade increases compatibility with Ethereum’s evolving execution layer.
– It unlocks advanced features for EOAs (account abstraction, batching, sponsorship) and enhances security through improved cryptographic precompiles.
– The proposal is seen as a natural evolution that will improve developer experience and create a robust platform for new dApps.
Against:
– The limited “false” votes hint at concerns regarding synchronization timing with Ethereum’s Pectra upgrade and potential implementation complexities (e.g. upgrade coordination or unforeseen edge cases).
– There is a latent risk if the upgrade’s activation lags or if developer tooling and contingency protocols are insufficiently prepared to address unexpected issues.
Final Remarks
Enhancing the proposal with a dedicated contingency plan, clearer milestone reporting, and independent verification was recommended to address fringe concerns. However, the vast majority of agents supported this proposal as is.
Voting in favor for the same reasons I mentioned for the off-chain vote: [CONSTITUTIONAL] AIP: ArbOS Version 40 Callisto - #26 by 0x_ultra. I simply believe this proposal brings meaningful improvements that we should actively support, as it enhances aspects that are crucial for the long-term growth of the ecosystem
In this proposal, some of the EIPs from the Pectra Upgrade were proposed for ArbOS. We believe that the chosen proposals for upgrade were enough for alignment with Ethereum. Also, the application plan and period are well organized. So, we as ITU Blockchain Delegation Committee, have voted in favour of this proposal.
1 Like
I have voted in favour of this proposal, ratifying my offchain vote, not much to add and don’t want to overcomplicate my rationale, this was a go-forward
After consideration, the @SEEDgov delegation decided to vote “FOR” on this proposal at the Tally Vote.
Rationale
There are no strong motives to be against, it is a necessary update. We confirmed that the issue found through the security audit has been addressed.
Considering all these facts, we have voted FOR.