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.
// user completes a social sign-in -> JWTconst { 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
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.
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.
zkLogin needs a salt service and a proving service. Inodra runs both, so you integrate a small HTTP API instead of operating infrastructure.
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.
Salt, address derivation and proof generation are three HTTP calls. The same API key and scopes as the rest of Inodra.
Same API keys, same dashboard, same usage analytics as the gateways. Wallets are not a separate account to reconcile.
Register your OAuth client ID, create a key with the zkLogin scope, and ship. Testnet on every plan, mainnet from Team.