Openfort signer
Non-custodial signer with social login
If you want to check out a live sample app using Openfort signers, check out the live demo with RapidFire.
Configure Authentication Methods#
Navigate to the auth providers page on the Openfort dashboard by selecting your project and then clicking Auth providers Methods in the side bar in the players page. Select the account types you'd like users to be able to login with. For more information on how to enable social logins, check out the dashboard docs.
As soon as you enable each provider from your dashboard, it will automatically appear as an option in the authentication page.
From the Openfort Dashboard for select your desired app, navigate to the developers page in the top bar. On the de tab, find the API keys section. Get your Openfort API keys, you will need it in the next step.
You will find two keys:
- Publishable Key: This value can be safely exposed in a client-side environment.
- Secret Key: This value should never be exposed in a client-side environment. It should be kept secure and used only in a server-side environment. Learn more on how to use it in the server-side guide. You can further secure it for production applications.
To generate non custodial wallets, you will need to create a Shield instance. At the API keys page, scroll down to the Shield section and click on the Create Shield keys button. A one time pop-up will appear with a variable called encryption share. Its very important that you store it safely. You will not be able to see it again.
Then, in your page, you will see two Shield keys:
- Publishable Key: This value can be safely exposed in a client-side environment.
- Secret Key: This value should never be exposed in a client-side environment.
Creating your wallet UI#
The wallet UI is how information is shown to wallet users. Under your wallet UI
folder, install the latest version of Ecosystem SDK using your package manager of choice. Remember to comply with the requirements to benefit from code splitting.
When creating your wallet UI you need to add the ecosystem ID. It can be found in your dashboard in the settings section.
Components:
- Check all the available
OpenfortProvider
configuration methods at OpenfortProvider SDK reference. - Check all the available
EcosystemProvider
configuration methods at EcosystemProvider SDK reference.
Configure Supported Chains#
As you can see above, its required that you configure Wagmi and the chains you plan on enabling for your wallet.
Note that, to enable transaction simulation through asset changes, the Ecosystem SDK internally requires the eth_simulateV1
JSON-RPC method, so you will need to provide an RPC endpoint that supports this method (or disable simulation through the EcosystemProvider using disableTransactionSimulation
).
Sample Openfort authentication#
Using a custom auth provider#
Openfort's cross-app wallets are fully-compatible with any authentication provider that supports JWT-based, stateless authentication.
- Use a custom authentication provider (easy to integrate alongside your existing stack).