@upbond/sdk
    Preparing search index...

    Interface IdTokenClaims

    Decoded id_token claims. sub is the stable user identifier (and the Web3Auth verifierId); the optional profile claims depend on the granted scope. wallet_address is present once the address has been bound to the account. Unlisted claims are exposed via the index signature.

    interface IdTokenClaims {
        email?: string;
        name?: string;
        picture?: string;
        sub: string;
        wallet_accounts?: WalletAccountClaim[];
        wallet_address?: string;
        wallet_public_key?: string;
        [claim: string]: unknown;
    }

    Indexable

    • [claim: string]: unknown
    Index
    email? name? picture? sub wallet_accounts? wallet_address? wallet_public_key?
    email?: string
    name?: string
    picture?: string
    sub: string

    OIDC subject — the stable per-user identifier.

    wallet_accounts?: WalletAccountClaim[]

    All wallets of the user, default entry included (multi-wallet foundation, docs/28; requires the wallet scope).

    wallet_address?: string

    The user's bound wallet address, once set (requires the wallet scope).

    wallet_public_key?: string

    Reserved: the wallet's secp256k1 public key (compressed SEC1 hex; requires the wallet scope). No issuer flow populates this claim today — issuer-side pre-derivation was rejected (docs/34, 2026-08-20): the final TSS key includes ceremony-time client randomness, so it cannot be known before the first ceremony. If a future flow supplies it, both chain addresses derive from it offline: see addressesFromPublicKey / UpbondState.derivedAddresses.

    Settings
    Member Visibility

    On This Page
    Properties