Craft and customize your wallet
Openfort ecosystem wallets come with a default set of screens for authentication, session key confirmation, sign typed message, configuration, and transaction confirmation. These screens are designed to be customizable to fit your brand and user experience. Openfort provides helpers to the most popular frameworks to make it easier to integrate the ecosystem wallets.

Wallet Routes#
Whenever the users of a wallet make a request, this request is eventually received by the Wallet UI which is in charge of directing the user to the correct screen.
The Wallet UI expects the following routes to exist in your project:
Route | Description |
---|---|
/sign/personal-sign | personal_sign |
/sign/eth-sign-typed-data-v-4 | eth_signTypedData_v4 |
/sign/eth-send-transaction | eth_signTransaction |
/sign/eth-request-accounts | eth_requestAccounts |
/sign/wallet-show-calls | wallet_showCallsStatus |
/sign/wallet-send-calls | wallet_sendCalls |
/sign/wallet-grant-permissions | wallet_grantPermissions |
/ | Loading screen |
Wallet Window Strategy#
The Ecosystem SDK
supports two window modes, popup
and iframe
, which can be configured through the prop windowStrategy
when creating the wallet SDK with @openfort/ecosystem-js/client
.
iframe#
The wallet is embedded in the page. In mobile no new tab is required to show the wallet action.
DESKTOP | MOBILE |
---|---|
Popup#
The wallet is opened in a new window both in mobile and desktop.
DESKTOP | MOBILE |
---|---|
Here's how the windowStrategy is set in the Rapidfire ID
sample wallet:
Wallet UI Customization#
The Ecosystem SDK
uses ConnectKit themes, and offers the same theming and customization options. You can edit fonts, colors, and other styling via the theme and customTheme props of EcosystemProvider
. For more detail on themes, see the ConnectKit docs.