AIP: Support RIP-7212 for Account Abstraction Wallets (ArbOS 30)

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.

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.

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.

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.

Savvy DAO votes FOR the proposal “AIP: Support RIP-7212 for Account Abstraction Wallets (ArbOS 30).”

See delegate thread: Savvy DAO - Delegate Communication Thread - #45 by SavvyDAO

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.

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 voted for.

Any improvement on the UI/UX to onboard new users is welcomed.

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.

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.

1 Like

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.

1 Like

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.

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!

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.