Sign messages

To request signatures or transactions from a connected wallet, you can either:

use the wallet's EIP-1193 provider to send JSON-RPC requests to the wallet directly.
pass the wallet to a library like viem, ethers, or wagmi.
for the embedded signer specifically, use Openfort's native signMessage and sendTypedMessage methods.

The guide below explains how to request signatures and transactions via the Openfort native methods.

Signing messages#

To request a signature from a user, use the signMessage method.

When invoked, signMessage will request an EIP-191 personal_sign signature from the embedded signer, and returns a Promise for the user's signature as a string.

client.tsx

openfortConfig.ts

import openfort from "./openfortConfig"
// This example assumes you have already checked that Openfort 'embeddedState' is 
// `ready` and the user is `authenticated`
async function signMessageButton(message:string) {
  await openfort.signMessage(message);
}

Signing typed data#

To have a user sign an EIP-712 typed data signature, use the signTypedData method.

When invoked, signTypedData will request an EIP-721 eth_signTypedData_v4 signature from the embedded signer, and returns a Promise for the user's signature as a string.

client.tsx

openfortConfig.ts

import openfort from "./openfortConfig"
// This example assumes you have already checked that Openfort 'embeddedState' is 
// `ready` and the user is `authenticated`
async function signTypedMessageButton(domain: any, types: any, value: any) {
  await openfort.signTypedData(domain, types, value);
}

Examples#

NextJS Sample Embedded Signer

An integration with Google OAuth using Firebase Auth as a third party auth provider to create a non-custodial embedded signer.

Unity Sample Android Embedded Signer

An integration with Google Play Games using Firebase Auth as a third party auth provider to create a non-custodial embedded signer.

Unity Sample WebGL Embedded Signer

An integration with Openfort Auth with non-custodial embedded signer.