Wallet Provider / Client / User
In the Okto documentation, you'll frequently encounter three main personas: Wallet Provider(WP), Client, and User. These personas are key to navigating how Okto interacts with developers and users across its platform. Let's break down each of these roles to understand their place in the ecosystem.
Overview
Wallet Provider
A Wallet Provider is the core entity that defines and manages a distinct wallet ecosystem, offering wallet infrastructure and services that Clients integrate.
Client
Client is any developer or company building an application that integrates Okto's services
User
User is any individual who uses a Client's app and, by extension, uses Okto's services
Dive deep into what & how each personas work
Wallet Provider
A Wallet Provider is the entity responsible for the underlying wallet infrastructure and the specific ecosystem of wallets made available to users through Client applications. Okto itself acts as a Wallet Provider (e.g., with Okto AA and Okto EOA wallets), and in the future, other entities might also assume this role within the Okto framework.
What does it do?
- Manages the underlying wallet infrastructure.
- Defines a distinct wallet ecosystem and its interoperability rules.
- Provides wallet services that Client applications integrate for their Users.
- Can set default policies for its ecosystem.
What is it?
- Can be Okto itself (providing Okto AA/EOA wallets) or a third-party entity.
- Forms the foundation upon which Clients build their user-facing applications.
- Each Wallet Provider creates a boundary for direct wallet/asset interoperability between different Wallet Provider ecosystems.
How to identify a wallet provider?
- Users' wallets are tied to a specific Wallet Provider through the Client application and login method they use.
Client
Client is any developer or company building an application that integrates Okto's services
What does it do?
- Builds applications using Okto's API and SDK
- Integrates Okto's wallet and services into their own apps
- Serves as the intermediary bringing Okto's functionalities to end-users
What is it?
- Each Client has a unique Client ID
- Clients receive an API ID and secret for secure integration
- Clients can onboard Users to the Okto ecosystem through their apps
How to identify a client?
- Each Client receives a unique Client ID
- Clients also get an API ID and secret for secure API calls
- This system ensures each Client's app is distinctly recognized on our platform
User
User is any individual who uses a Client's app and, by extension, uses Okto's services
What does it do?
- Interacts with Client applications
- Manages wallets, sends tokens, and engages with blockchain features
- Benefits from the simplified blockchain experience provided by Okto and the Client
What is it?
- Each User has a unique User ID within the Okto ecosystem
- Users can interact with multiple Client apps using the same Okto account
- User experiences are tailored by Clients but powered by Okto
How to identify a user?
- Every User is assigned a unique User ID
- This ID manages their interactions, wallets, and transactions across the Okto ecosystem
- The same User ID works across multiple Client apps, providing a unified experience
- Since Okto is interoperable, the same user ID can be associated with multiple Client apps, allowing Users to have a unified experience across different applications while leveraging the same Okto infrastructure.