Skip to main content

User Authentication

The network can verify if the request came from the User, by verifying the authentication data attached to the request.

EOA

User signs the request to the network using Externally Owned Account, for example by using the MetaMask wallet, by calling signTypedData.

Passkey

The Network supports user Passkey registration. Each node will hold the User's Passkey data. Meaning each note involved in the request will verify the user request signed by the Passkey.

Social Login

On the roadmap

With social login, Users will be able to register to the network by external services, like GMail, and authenticate the requests by providing tokens from those services.

Session keys

By default each request coming from the User must be authenticated, for example by EOA signing.

That means upon every single message signing the user is prompted to verify the request and sign. There are use-cases where number of signs is so high, that constant User interaction is highly undesired.

Therefore Silent Network brings Session Keys functionality, it's session-based authentication (with predefined expiry) that requires user interaction only during DKG. Afterward, Application can perform DSGs without any user intervention. This significantly improves user experience by eliminating repetitive transaction approval prompts.

Some use cases include:

  • Currency exchange - where the operations must be done quickly and frequently
  • Agent2Agent communication - passing the Session Key to the Agent allowing to do operations on Users behalf

User is still in full control of session keys, can revoke the sessions, create new ones.

Note that Session Keys together with Permissions opens a wide field of opportunities, bringing UX and the security together.