You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, there is no native support within the AA-SDK for implementing Social Recovery in modular account setups. This is a crucial feature for user-friendly self-custodial wallets, as it addresses a significant pain point: the inability to recover access to an account if the private key is lost. While developers can manually implement recovery mechanisms in smart contracts, doing so requires significant overhead, testing, and customization. A lack of standardized tooling makes this process error-prone and time-intensive.
Describe the solution you would like
I would like the AA-SDK to include a Social Recovery Module or helper tools to facilitate the creation and integration of social recovery mechanisms for accounts built with the SDK. The solution should include:
Guardian Management APIs: Methods to add, remove, or update a list of guardians dynamically and Threshold configurations to set the number of required guardian approvals
Recovery Workflow Integration Built-in utilities to handle initiation, approval, and finalization of recovery requests, ensuring compatibility with modular wallets or ERC-4337 validation logic.
Timelock and Override Features: Support for recovery delays (timelocks) to prevent immediate account takeovers.
SDK-Level Abstractions: Easy-to-use functions for interacting with recovery contracts (e.g., initiating recovery, approving as a guardian).
Describe alternatives you have considered
Solutions like Rhinestone's Social Recovery module provide a well-designed recovery framework but lack direct integration with modular wallet frameworks like ERC-6900. Developers must adapt these modules manually, increasing development time and complexity.
Additional context
This feature aligns with the goals of account abstraction by making smart contract wallets more secure and user-friendly. Social recovery is a key feature for mass adoption, especially for onboarding users unfamiliar with self-custody risks.
Potential Use Cases:
Consumer Wallets: Self-custodial wallets that are recoverable via trusted guardians (family, friends, or hardware devices).
Enterprise Accounts: Multi-signature recovery for organizations, enabling board members or stakeholders to act as guardians.
Onboarding Platforms: Solutions targeting Web2 users transitioning to Web3, providing account recovery similar to traditional password resets.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, there is no native support within the AA-SDK for implementing Social Recovery in modular account setups. This is a crucial feature for user-friendly self-custodial wallets, as it addresses a significant pain point: the inability to recover access to an account if the private key is lost. While developers can manually implement recovery mechanisms in smart contracts, doing so requires significant overhead, testing, and customization. A lack of standardized tooling makes this process error-prone and time-intensive.
Describe the solution you would like
I would like the AA-SDK to include a Social Recovery Module or helper tools to facilitate the creation and integration of social recovery mechanisms for accounts built with the SDK. The solution should include:
Describe alternatives you have considered
Solutions like Rhinestone's Social Recovery module provide a well-designed recovery framework but lack direct integration with modular wallet frameworks like ERC-6900. Developers must adapt these modules manually, increasing development time and complexity.
Additional context
This feature aligns with the goals of account abstraction by making smart contract wallets more secure and user-friendly. Social recovery is a key feature for mass adoption, especially for onboarding users unfamiliar with self-custody risks.
Potential Use Cases:
The text was updated successfully, but these errors were encountered: