Skip to main content

Obsidion Accounts

Obsidion Accounts are modular by design. There is a base account smart contract and other modules are added to improve functionality.

The wallet supports multiple authentication methods, including WebAuthn (Passkeys & biometric authentication), seed phrases for those who old school, and developer mode for testing.

Authentication Methods​

Passkeys​

Passkeys are the default authentication mechanism for Obsidion Wallet. Which leverages your devices secure hardware features.

On apple devices this is the utilises the secure enclave on the device.

  • Stores keys isolated from the main processor.
  • Manages biometric validaton through TouchID/FaceID.
  • Only the credential ID and public key are stored in the browser's local storage.
  • The user must provide TouchID to authorize the use of the key.

Devleoper Authentication Module​

For development and testing purposes, Obsidion has a signerless authentication module.

  • Disclaimer: Private Keys for this authentication method or stored directly in the browsers local storage.

Account Creation Flow

  1. Secret Key Generation
  • A master Secret key is generated. This serves as the root of the users account.
  • For more information see the Aztec Documentation on Keys

  1. Authenticator Initialization Depending on the chosen authentication module (webauthn or dev mode). This is initialized with the authenticator module and the accounts public key.

  2. Account Creation This authenticator is used to create a kernel account using the master key that was generated.