This proposal adopts RIP-7212 (Rollup Improvement Proposal), a precompile for verifying the secp256r1 curve on Arbitrum One and Arbitrum Nova. Other major L2s have committed to adopting RIP-7212. Adding support for this precompile would enable account abstraction wallets to cheaply verify a type of signature widely used in passkeys and secure enclaves.
Wallet security is one of the most prominent pain points for crypto users today. Adopting RIP-7212 will reduce the costs of using passkey-based wallets on Arbitrum One and Nova, making them more feasible for everyday use and enabling dApp developers and protocols to offer their users improved UX.
Passkey-based wallets offer a better level of security than a typical EOA and seamless cross-device support. Specifically, adding this precompile will reduce the costs of verifying the secp256r1 curve for account abstraction wallets. Passkeys offer a solution that removes the need for personally storing a private key. They leverage WebAuthn, a global standard for passwordless authentication used by Google, Facebook, Microsoft, and all major web browsers. The private key generated when creating a passkey can be encrypted and then stored in the iCloud Keychain (or the Android Keystore for Android devices). The decryption of the private keys happens in a specialized module located in every iPhone (and other smartphones) called the Secure Enclave. The Secure Enclave ensures a user’s private key can never leave the device, transforming a smartphone into a hardware wallet. Users can authorize transactions with biometric features like Touch ID or Face ID when using passkey-based wallets for key management. These qualities add flexibility and significantly improve UX while maintaining high security.
Ethereum currently has a precompile for the secp25k1 curve, which all EOA wallets use as their signature scheme. Account abstraction wallets can use alternative signature schemes, such as the one that passkeys utilize: secp256r1. Without a precompile, verifying this signature onchain is extremely expensive. Adding support for RIP-7212 would decrease the costs of verifying the secp256r1 curve by 99% when compared to current implementations. This makes implementing passkey-based wallets feasible for everyday use. Many wallets, and notably, apps using embedded wallets, have been requesting this feature for over a year.
This proposal is aligned with the Arbitrum community’s mission and values as per the Constitution:
Ethereum-Aligned: RIP-7212 is the first Rollup Improvement Proposal adopted by the broader Ethereum ecosystem. The RIP stakeholders coordinate with Ethereum Core Devs to ensure Ethereum will continue to be compatible with the upgrade.
Accessibility: Many users who are not crypto-native will refuse to write down a seed phrase or buy a dedicated hardware wallet. While options exist to get around those pain points, this upgrade empowers account abstraction wallets to provide high-level security without UX tradeoffs.
Secure: Passkeys and secure enclaves offer hardware-level security since a user’s private key can never leave the device. This is a great alternative to EOAs that does not compromise on usability.
Inclusivity: RIP-7212 was discussed publicly among all major L2s before being adopted. The codebase is open-source, and anyone can implement the upgrade.
RIP (Rollup Improvement Proposal): A process to establish optional norms and standards for L2s to extend the EVM and related tooling while limiting conflicts with the L1 EVM and preventing a proliferation of mutually incompatible standards among L2s.
Precompile: Predefined smart contracts with special addresses that provide specific functionality executed not at the EVM bytecode level but natively by the client.
The specifications of RIP-7212, including test cases, can be found in the RIP repository. If approved, Arbitrum One will use this specification as the reference for implementation.
The Ethereum Magicians Forum discusses design decisions, iterations, and the transformation of the proposal from an EIP (Ethereum Improvement Proposal) to a RIP.
If the Arbitrum DAO approves the AIP, the path would consist of:
This proposal will be included in the vote to upgrade to the next version of ArbOS along with Stylus, which will move to a Snapshot vote once it is production-ready.
NOTE: If this vote passes on Snapshot, the tentative plan is to upgrade Arbitrum Sepolia to arbOS 30 the week of June 10th.
If Arbitrum Sepolia upgrades to arbOS 30, there will be an ecosystem-wide plan to ensure non-breaking compatibility of infrastructure and applications with Stylus, which will take several weeks or months. The ultimate goal is that the experience for EVM developers remains as unchanged as possible if arbOS reaches mainnet. Once enough confidence is reached, there will be an onchain vote to upgrade Arbitrum One and Nova to arbOS 30. The Arbitrum community will be informed of any significant updates as they arise.
This proposal adopts RIP-7212 (Rollup Improvement Proposal), a precompile for verifying the secp256r1 curve on Arbitrum One and Arbitrum Nova. Other major L2s have committed to adopting RIP-7212. Adding support for this precompile would enable account abstraction wallets to cheaply verify a type of signature widely used in passkeys and secure enclaves.
Wallet security is one of the most prominent pain points for crypto users today. Adopting RIP-7212 will reduce the costs of using passkey-based wallets on Arbitrum One and Nova, making them more feasible for everyday use and enabling dApp developers and protocols to offer their users improved UX.
Passkey-based wallets offer a better level of security than a typical EOA and seamless cross-device support. Specifically, adding this precompile will reduce the costs of verifying the secp256r1 curve for account abstraction wallets. Passkeys offer a solution that removes the need for personally storing a private key. They leverage WebAuthn, a global standard for passwordless authentication used by Google, Facebook, Microsoft, and all major web browsers. The private key generated when creating a passkey can be encrypted and then stored in the iCloud Keychain (or the Android Keystore for Android devices). The decryption of the private keys happens in a specialized module located in every iPhone (and other smartphones) called the Secure Enclave. The Secure Enclave ensures a user’s private key can never leave the device, transforming a smartphone into a hardware wallet. Users can authorize transactions with biometric features like Touch ID or Face ID when using passkey-based wallets for key management. These qualities add flexibility and significantly improve UX while maintaining high security.
Ethereum currently has a precompile for the secp25k1 curve, which all EOA wallets use as their signature scheme. Account abstraction wallets can use alternative signature schemes, such as the one that passkeys utilize: secp256r1. Without a precompile, verifying this signature onchain is extremely expensive. Adding support for RIP-7212 would decrease the costs of verifying the secp256r1 curve by 99% when compared to current implementations. This makes implementing passkey-based wallets feasible for everyday use. Many wallets, and notably, apps using embedded wallets, have been requesting this feature for over a year.
This proposal is aligned with the Arbitrum community’s mission and values as per the Constitution:
Ethereum-Aligned: RIP-7212 is the first Rollup Improvement Proposal adopted by the broader Ethereum ecosystem. The RIP stakeholders coordinate with Ethereum Core Devs to ensure Ethereum will continue to be compatible with the upgrade.
Accessibility: Many users who are not crypto-native will refuse to write down a seed phrase or buy a dedicated hardware wallet. While options exist to get around those pain points, this upgrade empowers account abstraction wallets to provide high-level security without UX tradeoffs.
Secure: Passkeys and secure enclaves offer hardware-level security since a user’s private key can never leave the device. This is a great alternative to EOAs that does not compromise on usability.
Inclusivity: RIP-7212 was discussed publicly among all major L2s before being adopted. The codebase is open-source, and anyone can implement the upgrade.
RIP (Rollup Improvement Proposal): A process to establish optional norms and standards for L2s to extend the EVM and related tooling while limiting conflicts with the L1 EVM and preventing a proliferation of mutually incompatible standards among L2s.
Precompile: Predefined smart contracts with special addresses that provide specific functionality executed not at the EVM bytecode level but natively by the client.
The specifications of RIP-7212, including test cases, can be found in the RIP repository. If approved, Arbitrum One will use this specification as the reference for implementation.
The Ethereum Magicians Forum discusses design decisions, iterations, and the transformation of the proposal from an EIP (Ethereum Improvement Proposal) to a RIP.
If the Arbitrum DAO approves the AIP, the path would consist of:
This proposal will be included in the vote to upgrade to the next version of ArbOS along with Stylus, which will move to a Snapshot vote once it is production-ready.
NOTE: If this vote passes on Snapshot, the tentative plan is to upgrade Arbitrum Sepolia to arbOS 30 the week of June 10th.
If Arbitrum Sepolia upgrades to arbOS 30, there will be an ecosystem-wide plan to ensure non-breaking compatibility of infrastructure and applications with Stylus, which will take several weeks or months. The ultimate goal is that the experience for EVM developers remains as unchanged as possible if arbOS reaches mainnet. Once enough confidence is reached, there will be an onchain vote to upgrade Arbitrum One and Nova to arbOS 30. The Arbitrum community will be informed of any significant updates as they arise.
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/34?u=princetonblockchain
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/33?u=tane
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/32?u=maxlomu
we are always in support of better UX
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/34?u=princetonblockchain
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/33?u=tane
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/32?u=maxlomu
we are always in support of better UX
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/31?u=michigan_blockchain
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/30
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/29?u=blockworksresearch
Any improvement on the UI/UX to onboard new users is welcomed.
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/26?u=ocandocrypto
https://forum.arbitrum.foundation/t/savvy-dao-delegate-communication-thread/21266/45?u=savvydao
RIP-7212 (aka EIP-7212) has been proposed as a standardized way for L2s to further support account abstraction wallets. RIP-7212 has already
Absolutely, this will greatly improve UX for SCWs on L2s. Wen Mainnet?
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/20?u=0x_ultra
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/17?u=jojo
Adopting RIP-7212 is essential for reducing costs and enhancing security on Arbitrum One and Nova, making passkey-based wallets more viable.
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/16
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/15?u=larva
Rollup Improvement is necessary and Account Security is of crucial importance.
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/31?u=michigan_blockchain
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/30
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/29?u=blockworksresearch
Any improvement on the UI/UX to onboard new users is welcomed.
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/26?u=ocandocrypto
https://forum.arbitrum.foundation/t/savvy-dao-delegate-communication-thread/21266/45?u=savvydao
RIP-7212 (aka EIP-7212) has been proposed as a standardized way for L2s to further support account abstraction wallets. RIP-7212 has already
Absolutely, this will greatly improve UX for SCWs on L2s. Wen Mainnet?
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/20?u=0x_ultra
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/17?u=jojo
Adopting RIP-7212 is essential for reducing costs and enhancing security on Arbitrum One and Nova, making passkey-based wallets more viable.
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/16
https://forum.arbitrum.foundation/t/aip-support-rip-7212-for-account-abstraction-wallets-arbos-30/23298/15?u=larva
Rollup Improvement is necessary and Account Security is of crucial importance.
+1 from our side as both from a smart wallet builder perspective and AA Infra provider. We support this RIP.
+1 As a wallet provider we definitely support this to give our users an accessible path to easy onboarding!
This seems like a positive trend in L2s progressively enshrining discrete efficiency features in anticipation of their integration into L1. RIP-7212 expands the toolkit around signature verifications. I would therefore support this proposal as a developer looking for more ways to abstract chain interactions on Arbitrum.
It's great to see that RIP-7212 has been adopted by all rollups. LFG!!
+1 from our side as both from a smart wallet builder perspective and AA Infra provider. We support this RIP.
+1 As a wallet provider we definitely support this to give our users an accessible path to easy onboarding!
This seems like a positive trend in L2s progressively enshrining discrete efficiency features in anticipation of their integration into L1. RIP-7212 expands the toolkit around signature verifications. I would therefore support this proposal as a developer looking for more ways to abstract chain interactions on Arbitrum.
It's great to see that RIP-7212 has been adopted by all rollups. LFG!!
I support this RIP. Excited to see it taking off!
We're really excited to support this!
I support this RIP. Excited to see it taking off!
We're really excited to support this!
Hey @jengajojo , the goal is to have individual forum posts (DONE) and temperature checks for each change.
If there is strong consensus from the DAO to adopt all 4 upgrades and changes at the , then the plan as of now is to:
Bundle Stylus, RIP-7212, and the Nova Fee Router changes into one ArbOS v30 upgrade onchain AIP on Tally.
Have a separate onchain AIP for BOLD.
Hey @jengajojo , the goal is to have individual forum posts (DONE) and temperature checks for each change.
If there is strong consensus from the DAO to adopt all 4 upgrades and changes at the , then the plan as of now is to:
Bundle Stylus, RIP-7212, and the Nova Fee Router changes into one ArbOS v30 upgrade onchain AIP on Tally.
Have a separate onchain AIP for BOLD.
If there are varying results on Stylus, RIP-7212 and the Nova Fee Router temperature checks, then we will adjust the bundling accordingly and only include those strong support into the onchain ArbOS v30 AIP.
Hey everyone, here's the recording of the governance call - https://drive.google.com/file/d/1g07Q2dcCunW4fFdWXPTH0XY-1GelhpKL/view?usp=sharing
Hey everyone, a reminder that we'll be hosting a short governance call later today (Monday, 29 April) at 14:30 UTC to walkthrough this proposal, and answer questions if any.
Link to join: https://meet.google.com/jym-zozz-kwf
Hey @jengajojo , the goal is to have individual forum posts (DONE) and temperature checks for each change.
If there is strong consensus from the DAO to adopt all 4 upgrades and changes at the , then the plan as of now is to:
Bundle Stylus, RIP-7212, and the Nova Fee Router changes into one ArbOS v30 upgrade onchain AIP on Tally.
Have a separate onchain AIP for BOLD.
Hey @jengajojo , the goal is to have individual forum posts (DONE) and temperature checks for each change.
If there is strong consensus from the DAO to adopt all 4 upgrades and changes at the , then the plan as of now is to:
Bundle Stylus, RIP-7212, and the Nova Fee Router changes into one ArbOS v30 upgrade onchain AIP on Tally.
Have a separate onchain AIP for BOLD.
If there are varying results on Stylus, RIP-7212 and the Nova Fee Router temperature checks, then we will adjust the bundling accordingly and only include those strong support into the onchain ArbOS v30 AIP.
Hey everyone, here's the recording of the governance call - https://drive.google.com/file/d/1g07Q2dcCunW4fFdWXPTH0XY-1GelhpKL/view?usp=sharing
Hey everyone, a reminder that we'll be hosting a short governance call later today (Monday, 29 April) at 14:30 UTC to walkthrough this proposal, and answer questions if any.
Link to join: https://meet.google.com/jym-zozz-kwf
DAOplomats voted in favor on Snapshot.
This was easy. Adopting the RIP-7212 definitely bridges the UX gap which is always a win-win situation.
The Princeton Blockchain Club is voting FOR supporting RIP-7212 in ArbOS 30.
Adding a precompile for secp256r1 / NIST P-256 would be hugely beneficial for AA wallets. This is really one of the things that would help speed up global crypto adoption, especially for mobile users. The rest of the Ethereum ecosystem is for its inclusion, so we're glad to support it as well!
gm, great to see Arbitrum supporting the RIP 7212. Better UX is how we onboard the next wave of users without compromising their wallet security.
Voting for.
DAOplomats voted in favor on Snapshot.
This was easy. Adopting the RIP-7212 definitely bridges the UX gap which is always a win-win situation.
The Princeton Blockchain Club is voting FOR supporting RIP-7212 in ArbOS 30.
Adding a precompile for secp256r1 / NIST P-256 would be hugely beneficial for AA wallets. This is really one of the things that would help speed up global crypto adoption, especially for mobile users. The rest of the Ethereum ecosystem is for its inclusion, so we're glad to support it as well!
gm, great to see Arbitrum supporting the RIP 7212. Better UX is how we onboard the next wave of users without compromising their wallet security.
Voting for.
We vote FOR the proposal on its Snapshot.
RIP-7212 has been well-supported by the whole Ethereum community and other L2s will certainly introduce it on their chains. This enables more secure smart wallets to be easily utilized on the L2 environments, which is a clear win for the better UX.
We vote FOR the proposal on its Snapshot.
RIP-7212 has been well-supported by the whole Ethereum community and other L2s will certainly introduce it on their chains. This enables more secure smart wallets to be easily utilized on the L2 environments, which is a clear win for the better UX.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We are voting FOR this proposal.
Adopting the widely supported RIP-7212 ensures that Arbitrum doesn’t fall behind relative to other L2s by neglecting user security improvements.
Michigan Blockchain is voting for this proposal. It allows for more security and decreasing verification costs all while ensuring the user experience is benefitted, as passkey wallets make it easier for daily transactions over private-key wallets. Overall great for users.
Blockworks Research will be voting FOR this proposal on Snapshot.
We don’t have much to add to what has already been said within this thread. UX improvements are a huge value-add, and adopting RIP-7212 certainly accomplishes that.
I voted for.
Any improvement on the UI/UX to onboard new users is welcomed.
We will vote in favor of the proposal. There is no reason for us to vote against as this standard will enhance user experience, security, and functionality by integrating account abstraction wallets into ArbOS 3.0, promoting innovation and more sophisticated wallet solutions within the Arbitrum ecosystem.
I decided to vote FOR this proposal.
Once again, the foundation made an incredible effort to ensure we all understand the importance of these updates to the protocol.
Additionally, personal storage of private keys is the most painful aspect of crypto UX today. Improvements in this area are always exciting.
Savvy DAO votes FOR the proposal "AIP: Support RIP-7212 for Account Abstraction Wallets (ArbOS 30)."
See delegate thread: https://forum.arbitrum.foundation/t/savvy-dao-delegate-communication-thread/21266/45?u=savvydao
We support this proposal for Account Abstraction Wallets on Arbitrum. As RIP-7212 continues to gain traction, implementing this will enable more cost-effective signature verification.
Voted "For" as Account Abstraction is a great step for adoption. This will help make wallets more practical for everyday use, enabling decentralized apps, developers, and protocols to offer their users an improved user experience.
On behalf of the UADP:
This is a logical For vote. This aligns with recent Ethereum standards and allows for a better more secure way to use crypto without directly using passkeys to store private keys. Thanks to the team for staying on top of things.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We are voting FOR this proposal.
Adopting the widely supported RIP-7212 ensures that Arbitrum doesn’t fall behind relative to other L2s by neglecting user security improvements.
Michigan Blockchain is voting for this proposal. It allows for more security and decreasing verification costs all while ensuring the user experience is benefitted, as passkey wallets make it easier for daily transactions over private-key wallets. Overall great for users.
Blockworks Research will be voting FOR this proposal on Snapshot.
We don’t have much to add to what has already been said within this thread. UX improvements are a huge value-add, and adopting RIP-7212 certainly accomplishes that.
I voted for.
Any improvement on the UI/UX to onboard new users is welcomed.
We will vote in favor of the proposal. There is no reason for us to vote against as this standard will enhance user experience, security, and functionality by integrating account abstraction wallets into ArbOS 3.0, promoting innovation and more sophisticated wallet solutions within the Arbitrum ecosystem.
I decided to vote FOR this proposal.
Once again, the foundation made an incredible effort to ensure we all understand the importance of these updates to the protocol.
Additionally, personal storage of private keys is the most painful aspect of crypto UX today. Improvements in this area are always exciting.
Savvy DAO votes FOR the proposal "AIP: Support RIP-7212 for Account Abstraction Wallets (ArbOS 30)."
See delegate thread: https://forum.arbitrum.foundation/t/savvy-dao-delegate-communication-thread/21266/45?u=savvydao
We support this proposal for Account Abstraction Wallets on Arbitrum. As RIP-7212 continues to gain traction, implementing this will enable more cost-effective signature verification.
Voted "For" as Account Abstraction is a great step for adoption. This will help make wallets more practical for everyday use, enabling decentralized apps, developers, and protocols to offer their users an improved user experience.
On behalf of the UADP:
This is a logical For vote. This aligns with recent Ethereum standards and allows for a better more secure way to use crypto without directly using passkeys to store private keys. Thanks to the team for staying on top of things.
Im voting FOR...
A widely used signature in passkeys and secure enclaves. This aligns with Ethereum's standards and promotes accessibility, as it simplifies secure transactions without the need for users to manage private keys manually. Additionally, this upgrade ensures high security by leveraging secure enclaves, making everyday use of passkey-based wallets feasible.
Im voting FOR...
A widely used signature in passkeys and secure enclaves. This aligns with Ethereum's standards and promotes accessibility, as it simplifies secure transactions without the need for users to manage private keys manually. Additionally, this upgrade ensures high security by leveraging secure enclaves, making everyday use of passkey-based wallets feasible.
I’m voting "For" this proposal as it will improve account security and will ensure Arbitrum to remains competitive with other L2s.
I voted FOR this proposal on Snapshot. Personal storage of private keys is the most painful aspect crypto UX today. Excited to support this AIP to introduce a more secure option for using crypto without personally storing private keys via passkeys.
Voting "For"
This update fits right into our goals by making things more secure and accessible, using popular WebAuthn standards for smooth, secure logins. With cheaper signature checks, we’re opening the door for more users and innovations, providing safer and easier-to-use wallet choices.
Not only account abstraction is needed, we also need to keep up the pace with competition. As @Bob-Rossi said above, no brainer vote tbh. Voting for.
This proposal enables account abstraction wallets to cheaply verify a type of signature widely used in passkeys and secure enclaves. This has important implications for the Arbitrum to achieve mass adoption. I've voted FOR!
With the increased utilization and adoption of RIP-7212, it makes total sense to add support for this for account abstraction. It's great to see the efforts of the devs come out and our question posed is what other things are being embraced by the general defi community that we would want to integrate with/into?
An interesting proposal, but I would not mix different solutions into one update, given that voting on them could theoretically have different results.
I’m voting "For" this proposal as it will improve account security and will ensure Arbitrum to remains competitive with other L2s.
I voted FOR this proposal on Snapshot. Personal storage of private keys is the most painful aspect crypto UX today. Excited to support this AIP to introduce a more secure option for using crypto without personally storing private keys via passkeys.
Voting "For"
This update fits right into our goals by making things more secure and accessible, using popular WebAuthn standards for smooth, secure logins. With cheaper signature checks, we’re opening the door for more users and innovations, providing safer and easier-to-use wallet choices.
Not only account abstraction is needed, we also need to keep up the pace with competition. As @Bob-Rossi said above, no brainer vote tbh. Voting for.
This proposal enables account abstraction wallets to cheaply verify a type of signature widely used in passkeys and secure enclaves. This has important implications for the Arbitrum to achieve mass adoption. I've voted FOR!
With the increased utilization and adoption of RIP-7212, it makes total sense to add support for this for account abstraction. It's great to see the efforts of the devs come out and our question posed is what other things are being embraced by the general defi community that we would want to integrate with/into?
An interesting proposal, but I would not mix different solutions into one update, given that voting on them could theoretically have different results.
It's very encouraging to see RIP-7212 being embraced by the Arbitrum ecosystem. As delegates, we support this proposal, which is also backed by ecosystems like Polygon, Optimism, and zkSync. Thank you for your efforts, Doğan and @ulerdogan (our guys) <3
Thanks for alerting the community about this RIP. In a separate post, the suggestion is to upgrade One and Nova to BOLD https://forum.arbitrum.foundation/t/aip-bold-permissionless-validation-for-arbitrum/23232 , if that is the case, can this upgrade be included in the BOLD package?
Voting "For"
No brainer upgrade that keeps Arbitrum in line with other L2s, avoiding us falling behind on the tech front. Anytime we can increase security for users we improve the network, we should take the chance. Look forward to this upgrade.
It's very encouraging to see RIP-7212 being embraced by the Arbitrum ecosystem. As delegates, we support this proposal, which is also backed by ecosystems like Polygon, Optimism, and zkSync. Thank you for your efforts, Doğan and @ulerdogan (our guys) <3
Thanks for alerting the community about this RIP. In a separate post, the suggestion is to upgrade One and Nova to BOLD https://forum.arbitrum.foundation/t/aip-bold-permissionless-validation-for-arbitrum/23232 , if that is the case, can this upgrade be included in the BOLD package?
Voting "For"
No brainer upgrade that keeps Arbitrum in line with other L2s, avoiding us falling behind on the tech front. Anytime we can increase security for users we improve the network, we should take the chance. Look forward to this upgrade.
