Problem Statement
Currently, EmbeddedWallet only supports 3 builtin account types out of the box. We are maintaining a subclass of it to support our custom account account contract, because we want to take advantage of kernelless simulation. However, due to the lack of formal support, our implementation is extremely hacky and fragile, and is often broken with every minor update to the base class.
Proposed Solution
Promote custom account contracts as a first class citizen in EmbeddedWallet. Formally define the interfaces necessary for a custom account contract to gain support, which may include but not limited to:
- Persistence interface in WalletDB
- Stub interface for bypassing authwits during simulation
- TypeScript account class
- Noir account contract
Example Use Case
No response
Alternative Solutions
No response
Additional Context
No response
Problem Statement
Currently, EmbeddedWallet only supports 3 builtin account types out of the box. We are maintaining a subclass of it to support our custom account account contract, because we want to take advantage of kernelless simulation. However, due to the lack of formal support, our implementation is extremely hacky and fragile, and is often broken with every minor update to the base class.
Proposed Solution
Promote custom account contracts as a first class citizen in
EmbeddedWallet. Formally define the interfaces necessary for a custom account contract to gain support, which may include but not limited to:Example Use Case
No response
Alternative Solutions
No response
Additional Context
No response