💡Architecture
System architecture on which Guardian Smart Wallet is built.
Architecture Walkthrough
Util Contracts
The wallet SDK is a rollup to thirdweb's smart wallet (ERC-4337) contracts. We've added the following contracts to extend it's functionality:
| Contract | Description |
|---|---|
The factory contract that issues Guardian smart accounts for your users. A dApp owner will be deploying this factory contract. | |
This is the smart contract that powers the smart wallet by offering features like executing single or batched transactions, locking account assets, and updating the owner of the smart account in case of an account recovery is made. | |
Used by the user to assign guardians for smart wallet accounts | |
Powers the guardian interactions, like attending to account lock & recovery requests for the account they are guarding. | |
Adds features like creating account lock requests and evaluating consensus on them followed by locking/unlocking the account assets. | |
One of the most important contracts adding features like creating account recovery requests and evaluating consensus on them. Once the consensus is achieved, a new embedded wallet is created and made the owner of the smart contract holding all user assets, thus recovering the account. |
Stakeholders
| Title | Description |
|---|---|
dApp developer/owner | The entity that owns the dApp and will be issuing Guardian smart wallets for its users |
Users | The users of the dApp for whom the smart wallets will be issued. |
Guardians | The trusted people a user allots as guardians, to their smart wallets. They will help users in account locking and recovery operations. |
Last updated