Choose your signing path

You know at build time which signing path your app uses. This recipe helps you pick and wire it. For the underlying model, see Signing paths.

Do you own the wallet’s domain?

Ask one question: is the passkey’s rpId a domain you control and can serve .well-known files from?

Yes, use own-origin. Set rpId. Signing runs in your app, in code. This is the path for wallet apps and any app that owns its wallet UX.
No, use shared-origin. Set authOrigin, pointing at the operator origin that hosts the wallet. Signing happens in a popup or in-app browser tab at that origin; your app receives only the result.

rpId and authOrigin are mutually exclusive. Set exactly one.

Own-origin

import { createOwnOriginConnection } from "@avokjs/core";

const connection = createOwnOriginConnection({ rpId: "example.com" });

On React Native, also pass the injected passkey module:

import { Passkey } from "react-native-passkey";
import { createOwnOriginConnection } from "@avokjs/react-native";

const connection = createOwnOriginConnection({ rpId: "example.com", passkey: Passkey });

Shared-origin

import { createSharedOriginConnection } from "@avokjs/core";

const connection = await createSharedOriginConnection({ authOrigin: "https://wallet.example.com" });

On React Native, use createNativeSharedOrigin over an in-app browser tab. See React Native setup. Once you have a connection, pass it to createAvokClient. See Create your first wallet.

Host the auth popupBuild and host the single static page that serves shared-origin signing at your origin.

Get started

Concepts

Guides

Reference

Choose your signing path

Do you own the wallet’s domain?

Own-origin

Shared-origin

​Do you own the wallet’s domain?

​Own-origin

​Shared-origin

Do you own the wallet’s domain?

Own-origin

Shared-origin