Unlike typical SSO systems tied to centralized identity providers (e.g., Google or Facebook), InterLink SSO uses on-chain, biometric-anchored identity, ensuring each login is performed by a unique, verified human.
Difference between InterLink SSO and centralized identity providers
**Components**
* InterLink SDK (frontend): injected into web/mobile client
* InterLink App (mobile): handles secure biometric confirmation
* Verifier Node: decentralized endpoint (on-chain or light node) that verifies signed payloads
* Credential Resolver (optional): fetches and validates user-bound credentials (e.g., passport, age proof)
**Core Capabilities**
* Biometric-based login (liveness, uniqueness enforced)
* JWT or ZK-style signed assertions of human = true, age > 18, or has\_passport = true
* InterChain identity binding, InterLink ID can be mapped to wallets across EVM, Solana, Cosmos, etc.
* Offline-capable, signatures cached locally; used for dApps with intermittent connectivity
* No PII transmission, biometric and credential data remain on-device, never exposed
**Integration Highlights**
* Web2-ready: SDK available as JavaScript module, RESTful fallback
* Web3-native: Pluggable with WalletConnect, Ethers.js, wagmi
* Mobile-ready: React Native and Flutter bridges supported
* Developer Options: Verify-only (read a Human)
* Challenge flow (return signed payload for replay protection)
* Credential gate logic (use cases: age, residency, document check)
***
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://whitepaper.interlinklabs.ai/interlink-network/interlink-sdk/human-auth-sdk.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.