Open testinginprod opened 9 months ago
As part of this we should also keep track for various types of accounts
Do you implement this module for multichain landscape ?. For example:
@terryyy-eth this is an implementation detail of the account, x/accounts does not make assumptions around how an account can authenticate, if your account authentication wants to leverage the interchain it can, the implementation detail is up to you as a developer.
Out of curiosity, why would one need a multisig account, as defined in https://github.com/cosmos/cosmos-sdk/tree/aceeaf47206eccf4bcad56729bd695b9eefc18f1/x/accounts/defaults/multisig, when we have the x/group
module?
the multisig is meant to be a light weight and simple, if users would like a custom multisig they can simply add it without needing to modify the groups module. Group is heavy on a chain and complex. We are moving towards simplifying the system and groups may move into a maintenance state
This epic tracks x/accounts development:
MVP
Release (breaking changes we must have before release)
Post-Release (can be added in an additive way without breaking things)
Account Abstraction
Tx Integration (Enshrining)
Tasks needed to integrate account abstraction authentication into the TX execution.
Auxiliary
Defines auxiliary tasks needed:
GetAllAccounts
,IterateAccounts
methods fromx/auth
AccountKeeper
https://github.com/cosmos/cosmos-sdk/pull/19363