dGEN1 Wallet Architecture
A primer on how the keystorage works
The dGEN1 wallet implements a robust security model to ensure private keys are protected and only used under authorized conditions. The private key exists in the Trusted Execution Environment (TEE) and can never be removed, even by software updates.
dGEN1 Wallet Architecture Overview The dGEN1 wallet enables secure transaction signing by separating public request handling from private key operations in the Trusted Execution Environment (TEE). Apps interact with a public wallet service, while sensitive signing occurs only after biometric verification via the SystemUI.
Workflow:
App Request – The app sends a transaction request to the public wallet service.
User Prompt – The public wallet service triggers the SystemUI to prompt the user for signing approval.
Biometric Verification – SystemUI validates the user’s biometrics.
Secure Signing – The private wallet service in the TEE executes the signature.
dGEN1 Account Abstraction / EOA Emulation Along with having the same security guarantees as a hardware wallet, the way the wallet signs is separate from it being a smart contract wallet. We've implemented ERC-4337 to give the actual wallet a contract address that brings super powers that regular EOA’s don’t have. A few of those include gas sponsorship, full onchain recovery, multi-transactions, and support for signing in apps that also have 4337 support.
However we've added a few more UX upgrades we think you'll love:
EOA emulation, meaning you can still connect to sites that haven't updated to support 4337. This also means your dGEN1 wallet isn't siloed to just a single app or 4337 apps. It's completely interoperable.
Multi-chain / L2 login connections: The dGEN1 wallet is live on every chain at all times, auto-connecting to the L2 that you need. No need to switch networks, it just defaults to the one used by the app.
Cross-chain Gas paymaster: 4337 opens the possibilty for a gas paymaster, but we've enabled a separate account to sponsor your gas on ALL L2s. As long as you fill your "gas account" with some funds, you never need to bridge or even have the native gas token of any L2.
OS-Level App Transactions: Since the wallet is built into the OS, you don't need to switch apps to sign a transaction, or use an in-app browser anymore. The Terminal screen shows the current transaction and can be signed without leaving your app.
Browser & App Store support: Both the Firefox browser and Apps from the app store are able to connect to the OS-level wallet, so you have the option to connect directly in-app to the dGEN1 wallet.
Human Readable Transactions: We've enabled transaction decoding on the device level, so any transaction shows changes to your wallet, or assets in/out. You no longer need to trust the app UI, you can just see the transactions on your device if needed.
Light node: Not a part of the wallet, but worth noting that the local light node proxy, when active, defaults your transactions through this local RPC. If any service is down, you will always have a backup on your device.
We will soon be releasing an interactive video to show these features as well!
Contact the team for any questions on discord or email at [email protected]
Last updated