Using OneBalance SCA

Account Overview

This is a Kernel 4337 account with a custom ECDSA root validator module under ERC-7579 modular account. We also support other SCAs as well as 7702, docs for them are coming soon, but you can always reach out directly.

OneBalance SCA account includes three main roles:

1. Admin Role: A single key with on-chain encoded rights to manage all other roles within the account.

2. User Signing Role: Multiple keys for user signing (often called session keys). For an optimal user experience, it is recommended to create a session key for each user and store this externally owned address (EOA) within Privy.

3. Co-signer Role: A unique key held by OneBalance that co-signs each transaction. This is essential to ensure transactions are executed at the destination chain's speed.

Read more about Resource Lock here.

The core setup for a OneBalance smart account involves storing a user signing key within a secure environment which allows required authorization/signing experiece, such as TEE or WaaS solution, such as Turnkey or Privy.

Note: The account that holds the balance and performs transactions is the Smart Contract Account (SCA) address, not any of the roles listed above.