Passkeys Signer
In this guide, you will learn how to create a Passkey signer that can be added as a Safe owner and used to initialize any of the kits from the Safe{Core} SDK.
Please always use a combination of passkeys and other authentication methods to ensure the security of your users' assets.
Prerequisites
- Node.js and npm (opens in a new tab).
- Passkeys feature is available only in secure contexts (opens in a new tab) (HTTPS), in some or all supporting browsers (opens in a new tab).
Install dependencies
Steps
Imports
Here are the necessary imports for this guide.
In addition, you will need to import a web3 library of your choice to use in the "Get the provider and signer" section. In this guide, we are using viem
.
Create a passkey
Firstly, you need to generate a passkey credential using the WebAuthn API (opens in a new tab) in a supporting browser environment.
After generating the passkeyCredential
object, you need to create the signer. This signer will be a PasskeyArgType
object containing the rawId
and the coordinates
information.
At this point, it's critical to securely store the information in the passkeySigner
object in a persistent service. Losing access to this data will result in the user being unable to access their passkey and, therefore, their Safe Smart Account.
Get the provider and signer
Once the passkey is created, you need the provider
and signer
properties required to instantiate the Safe{Core} SDK kits.
Check how to initialize the Protocol Kit
You can instantiate the provider using viem
and the following imports:
Instantiate SDK
With the provider
and signer
you are ready to instantiate any of the kits from the Safe{Core} SDK and set up or use this signer as a Safe owner.
For example, you can instantiate the protocol-kit
as follows and sign a transaction with the passkey signer:
Recap and further reading
After following this guide, you are able to create a Safe signer using passkeys and get the provider
and signer
required to initialize the kits from the Safe{Core} SDK.