The network functionality

The network works with 4 main component SDKs:

1. The Wallet Provider SDK: Location: User's Interface The SDK is primarily responsible for

   1. Initiating a new Distributed Key Generation with the network for the user along with suitable permissions

   2. Initiating a user session (using an ephemeral session key) with the Backend SDK and subsequently the Network

   3. Authenticating the registration and session initiation requests with the user's EOA

   4. Generating a client signature generation request in a standard format

   5. Authenticating the sign gen request with the user's ephemeral session key signature

2. The Wallet Provider Service SDK: Location: Wallet Provider Backend This SDK is responsible for

   • routing the requests to the network from the client SDK to the Network Aggregator

   • Authenticating its requests to the Network (with an API token)

3. Eigen Layer Aggregator SDK:

   Location: EL Aggregator's Server

   Primary Responsibilities:

   • Aggregating data and requests from various Wallet Providers.

   • During signature generation request, Identifying the quorum of operators to participate in the signature.

4. Eigen Layer Operator SDK:

   Location: EL Operator Servers

   Primary Responsibilities:

   • Validating the frontend sdk (User EoA) and backend sdk (Wallet API Token) auth credentials for each register and session initiation request

   • Creating a new MPC Key for a new user, assigning the permissions as instructed by the FrontEnd SDK

   • Registering a new ephemeral session key for the MPC Key

   • Validating the Ephemeral key signature and Wallet API token for every sign request from the user

   • Validating signature requests according to the permissions issued by the user

   • Performing Distributed signature along with the quorum operators.

High-Level flow with Eigen Layer