Products / Smart WalletsNew

A social login in. A self-custodial wallet out.

Users sign in with an account they already have and get a Sui wallet, built on native zkLogin. No seed phrase, no extension, and no keys held by you or by us.

Live on Sui mainnet and testnet
SIGN-IN TO WALLET
// user completes a social sign-in -> JWT
const { address, salt } =
await inodra.zklogin.address({ jwt })
const proof =
await inodra.zklogin.prove({
jwt, extendedEphemeralPublicKey,
maxEpoch, jwtRandomness,
})
// they can now sign like any Sui wallet

What people actually build on it.

01

Onboard users who have never held crypto

A player or shopper signs in the way they already do and has a Sui wallet a moment later. No seed phrase to write down, no extension to install.

zkLogin sign-in
02

Let people transact with zero SUI

Pair with the Fuel Station and gas is covered. A new user can make their first on-chain action right after signing in, holding nothing.

Charged Wallets
03

Skip running zkLogin yourself

zkLogin needs a salt service and a proving service. Inodra runs both, so you integrate a small HTTP API instead of operating infrastructure.

salt and proving services

Self-custodial, and you hold nothing.

Derived from the login

The wallet comes from the user's own sign-in through Sui's native zkLogin. Neither you nor Inodra ever hold their keys or their funds.

A small API, not a stack

Salt, address derivation and proof generation are three HTTP calls. The same API key and scopes as the rest of Inodra.

Part of your Inodra project

Same API keys, same dashboard, same usage analytics as the gateways. Wallets are not a separate account to reconcile.

Priced per active user, with proofs included.

Team5,000 users / month
Growth15,000 users / month
Professional20,000 users / month
Business30,000 users / month

Free builds on testnet with 1,000 users a month. Every plan includes 20 proofs per active user per month. Compare every plan ->

Give every user a wallet in one sign-in.

Set up zkLogin

Register your OAuth client ID, create a key with the zkLogin scope, and ship. Testnet on every plan, mainnet from Team.