What is Chain-Fi OAuth?

Chain-Fi OAuth is a user-controlled authentication service for Web3 applications. It enables dApps to authenticate users using their Chain-Fi identity (email/password + mobile 2FA) without requiring direct wallet connections. Built on OAuth 2.0 authorization code flow with enterprise-grade security, permission-based data access, and multi-chain support across Base, Arbitrum, Optimism, Polygon, and Ethereum mainnet.

How does Chain-Fi OAuth work?

Chain-Fi OAuth follows the standard OAuth 2.0 authorization code flow: 1) User clicks "Sign in with Chain-Fi" on your dApp, 2) User authenticates with Chain-Fi (email/password = 1FA, QR code scan = 2FA), 3) User grants permission-based data access, 4) Chain-Fi redirects back with authorization code, 5) Your backend exchanges code for access token, 6) Your backend uses access token to retrieve user data. All authentication happens through Chain-Fi - users never connect wallets directly to your dApp.

What are the benefits of using Chain-Fi OAuth?

Chain-Fi OAuth provides: Unified identity across all dApps (users authenticate once), Multi-factor security (email/password + mobile 2FA), Permission-based data access (users control what data is shared), KYC verification access (verify user identity without exposing personal data), Simple integration (standard OAuth 2.0 protocol), Multi-chain support (works across all supported networks), Privacy-first design (no data mining, explicit consent required), and Enterprise-grade security (CSRF protection, secure token storage, audit logging).

How do I integrate Chain-Fi OAuth into my dApp?

Integrate Chain-Fi OAuth in four steps: 1) Register your application in Chain-Fi developer dashboard to get client ID and client secret, 2) Add "Sign in with Chain-Fi" button that redirects to Chain-Fi authorization endpoint with your client ID and requested scopes, 3) Create callback endpoint that receives authorization code and exchanges it for access token using your client secret, 4) Use access token to call Chain-Fi userinfo endpoint and retrieve authorized user data. Full documentation and code examples are available in the developer portal.

What data can I access through Chain-Fi OAuth?

Available scopes include: profile (basic user information like name and username), email (user email address), activity (user activity history and transaction records), connections (user wallet addresses and connection history), read (read-only access to user data), and write (write access for transaction operations). Users explicitly grant permissions for each scope - no data is shared without explicit consent. You can request multiple scopes, and users can approve or deny each one individually.

Is Chain-Fi OAuth secure?

Yes, Chain-Fi OAuth implements enterprise-grade security: OAuth 2.0 standard protocol with authorization code flow, CSRF protection via state parameter validation, Secure token storage (access tokens are short-lived, refresh tokens stored server-side), Multi-factor authentication (email/password + mobile QR code scan), Encrypted data transmission (AES-256-GCM encryption), Complete audit logging of all authentication events, and Privacy-first design with permission-based access. All tokens are handled server-side and never exposed to frontend JavaScript.

Do users need to connect their wallet to use Chain-Fi OAuth?

No! That's one of the key benefits of Chain-Fi OAuth. Users authenticate with Chain-Fi using email/password (1FA) and mobile QR code scan (2FA). They never need to connect their wallet directly to your dApp. Chain-Fi handles all backend authentication and can access user wallet addresses (if user grants permission) without requiring wallet connection. For transactions, users can optionally provide wallet signature for additional security (3FA), but this is handled through Chain-Fi, not direct wallet connection to your dApp.

Which blockchain networks does Chain-Fi OAuth support?

Chain-Fi OAuth works across all Chain-Fi-supported networks: Base (Coinbase L2), Arbitrum (Optimistic Rollup), Optimism (Optimistic Rollup), Polygon (PoS Chain), and Ethereum mainnet. One OAuth integration works for all networks. User wallet addresses are returned for all networks where the user has bound wallets. You can filter or request specific network addresses based on your dApp's needs.

How do I get started with Chain-Fi OAuth?

To get started: 1) Create a Chain-Fi account (free account creation), 2) Navigate to developer dashboard and register your application, 3) Receive your client ID and client secret, 4) Configure your redirect URIs and requested scopes, 5) Follow the integration guide to add OAuth flow to your dApp, 6) Test in development environment, 7) Deploy to production. Full documentation, code examples, and SDK support are available. The integration typically takes 1-2 hours for experienced developers.

What is the difference between Chain-Fi OAuth and traditional wallet connections?

Traditional wallet connections require users to connect their wallet (MetaMask, WalletConnect, etc.) directly to each dApp. Chain-Fi OAuth provides: Unified identity (authenticate once, access all dApps), Multi-factor security (email/password + mobile 2FA vs. just wallet signature), Permission-based data access (users control what data is shared), KYC verification (access to user verification status), No repeated wallet connections (authenticate with Chain-Fi, not each dApp), and Better UX (familiar email/password login vs. wallet popups). Chain-Fi OAuth is designed for dApps that want secure authentication without wallet connection complexity.

Can I use Chain-Fi OAuth with existing authentication systems?

Yes! Chain-Fi OAuth can be integrated alongside existing authentication systems. You can: Offer Chain-Fi OAuth as an additional login option (alongside email/password, social login, etc.), Use Chain-Fi OAuth for Web3-specific features while keeping traditional auth for other features, Migrate users gradually by offering both options, or Use Chain-Fi OAuth as primary authentication and sync user data to your existing system. The OAuth flow is independent and doesn't interfere with other authentication methods.

How do I handle token refresh with Chain-Fi OAuth?

Chain-Fi OAuth provides refresh tokens for long-term access. When your access token expires, use the refresh token to obtain a new access token: POST to token endpoint with grant_type=refresh_token, refresh_token, client_id, and client_secret. Refresh tokens are long-lived but can be revoked by users. Store refresh tokens securely server-side (never in frontend). Implement automatic token refresh before expiration. Handle refresh token expiration by redirecting user to re-authenticate. Full token management documentation is available in the developer portal.

What happens if a user revokes access to my dApp?

If a user revokes access: Your access tokens and refresh tokens are immediately invalidated, Subsequent API calls will return 401 Unauthorized, You should handle this gracefully by redirecting user to re-authenticate, User can re-authorize your dApp at any time, and All previously granted permissions are reset. Users can revoke access from their Chain-Fi account settings. It's recommended to implement token refresh error handling that detects revoked access and prompts re-authentication.

Can I customize the OAuth authorization screen?

The authorization screen is managed by Chain-Fi to ensure security and consistency. However, you can customize: Application name and description (shown to users), Application logo (displayed on authorization screen), Website URL (linked from authorization screen), and Requested scopes (determines what permissions are requested). The authorization screen shows your app information, requested permissions, and allows users to approve or deny access. This ensures users always see consistent, secure authorization flows.

How do I test Chain-Fi OAuth integration?

To test Chain-Fi OAuth: 1) Register a test application in developer dashboard, 2) Use test redirect URIs (localhost is supported for development), 3) Create test Chain-Fi accounts, 4) Test full OAuth flow (authorization → callback → token exchange → userinfo), 5) Test error scenarios (denied access, invalid codes, expired tokens), 6) Test token refresh flow, 7) Test with different scopes and permissions, 8) Use Chain-Fi's test environment for development. Full testing guide and test credentials are available in the developer documentation.

What are the rate limits for Chain-Fi OAuth API?

Chain-Fi OAuth API rate limits ensure fair usage: Authorization requests: 100 requests per minute per client ID, Token exchange: 60 requests per minute per client ID, Userinfo requests: 120 requests per minute per access token, Refresh token requests: 30 requests per minute per client ID. Rate limits are per client ID (not per user). Exceeding limits returns 429 Too Many Requests with Retry-After header. Enterprise tier applications can request higher rate limits. Rate limit headers are included in all API responses.

Is Chain-Fi OAuth free to use?

Chain-Fi OAuth is included in all Chain-Fi membership tiers. For dApp developers: OAuth integration and API access are free, No per-request fees or transaction fees, Standard rate limits apply (Enterprise tier can request higher limits), and No additional costs beyond standard Chain-Fi membership. For end users: OAuth authentication is free (part of Chain-Fi account), Users need a Chain-Fi account (free account creation), and Membership includes full access to all Chain-Fi services including OAuth. All membership tiers include monthly credits for gasless transactions.

Can I use Chain-Fi OAuth for mobile apps?

Yes! Chain-Fi OAuth works with mobile apps using standard OAuth 2.0 flows: For native mobile apps, use custom URL schemes or universal links for redirects, For React Native/Flutter apps, use deep linking, For mobile web apps, use standard redirect flow, Chain-Fi mobile app provides 2FA via QR code scan, and All OAuth endpoints are mobile-friendly. Mobile apps should use PKCE (Proof Key for Code Exchange) for additional security. Full mobile integration guide is available in the developer documentation.

How does Chain-Fi OAuth handle user privacy?

Chain-Fi OAuth is privacy-first: Permission-based access (users explicitly grant each permission), No data mining (only requested data is shared), Users can revoke access anytime, Minimal data sharing (only what's necessary for your dApp), Encrypted data transmission, No tracking or analytics on user behavior, Users see exactly what data is requested before granting access, and Complete transparency in authorization screen. Chain-Fi never shares user data without explicit consent. Users maintain full control over their data.

What programming languages are supported for Chain-Fi OAuth integration?

Chain-Fi OAuth works with any programming language that can make HTTP requests and handle OAuth 2.0 flows. Popular integrations include: JavaScript/TypeScript (Node.js, React, Vue, Angular), Python (Django, Flask, FastAPI), Go (Gin, Echo), PHP (Laravel, Symfony), Ruby (Rails), Java (Spring Boot), C# (.NET), and Rust. Chain-Fi provides: RESTful API (works with any HTTP client), SDKs for popular languages (JavaScript, Python, Go), Code examples for common frameworks, and Full API documentation. The OAuth 2.0 protocol is language-agnostic.

Can I use Chain-Fi OAuth for enterprise applications?

Yes! Chain-Fi OAuth is designed for enterprise use: Enterprise-grade security (multi-factor authentication, audit logging), Compliance support (KYC verification, data protection), Custom rate limits for Enterprise tier, Priority support and dedicated account management, White-label options (contact for details), Custom integrations and API access, SLA guarantees, and Enterprise onboarding assistance. Enterprise applications can request custom scopes, higher rate limits, and dedicated infrastructure. Contact Chain-Fi sales for enterprise pricing and custom solutions.

What is Chain-Fi OAuth?

Chain-Fi OAuth is a user-controlled authentication service for Web3 applications. It enables dApps to authenticate users using their Chain-Fi identity (email/password + mobile 2FA) without requiring direct wallet connections. Built on OAuth 2.0 authorization code flow with enterprise-grade security, permission-based data access, and multi-chain support across Base, Arbitrum, Optimism, Polygon, and Ethereum mainnet.

How does Chain-Fi OAuth work?

Chain-Fi OAuth follows the standard OAuth 2.0 authorization code flow: 1) User clicks "Sign in with Chain-Fi" on your dApp, 2) User authenticates with Chain-Fi (email/password = 1FA, QR code scan = 2FA), 3) User grants permission-based data access, 4) Chain-Fi redirects back with authorization code, 5) Your backend exchanges code for access token, 6) Your backend uses access token to retrieve user data. All authentication happens through Chain-Fi - users never connect wallets directly to your dApp.

What are the benefits of using Chain-Fi OAuth?

Chain-Fi OAuth provides: Unified identity across all dApps (users authenticate once), Multi-factor security (email/password + mobile 2FA), Permission-based data access (users control what data is shared), KYC verification access (verify user identity without exposing personal data), Simple integration (standard OAuth 2.0 protocol), Multi-chain support (works across all supported networks), Privacy-first design (no data mining, explicit consent required), and Enterprise-grade security (CSRF protection, secure token storage, audit logging).

How do I integrate Chain-Fi OAuth into my dApp?

Integrate Chain-Fi OAuth in four steps: 1) Register your application in Chain-Fi developer dashboard to get client ID and client secret, 2) Add "Sign in with Chain-Fi" button that redirects to Chain-Fi authorization endpoint with your client ID and requested scopes, 3) Create callback endpoint that receives authorization code and exchanges it for access token using your client secret, 4) Use access token to call Chain-Fi userinfo endpoint and retrieve authorized user data. Full documentation and code examples are available in the developer portal.

What data can I access through Chain-Fi OAuth?

Available scopes include: profile (basic user information like name and username), email (user email address), activity (user activity history and transaction records), connections (user wallet addresses and connection history), read (read-only access to user data), and write (write access for transaction operations). Users explicitly grant permissions for each scope - no data is shared without explicit consent. You can request multiple scopes, and users can approve or deny each one individually.

Is Chain-Fi OAuth secure?

Yes, Chain-Fi OAuth implements enterprise-grade security: OAuth 2.0 standard protocol with authorization code flow, CSRF protection via state parameter validation, Secure token storage (access tokens are short-lived, refresh tokens stored server-side), Multi-factor authentication (email/password + mobile QR code scan), Encrypted data transmission (AES-256-GCM encryption), Complete audit logging of all authentication events, and Privacy-first design with permission-based access. All tokens are handled server-side and never exposed to frontend JavaScript.

Do users need to connect their wallet to use Chain-Fi OAuth?

No! That's one of the key benefits of Chain-Fi OAuth. Users authenticate with Chain-Fi using email/password (1FA) and mobile QR code scan (2FA). They never need to connect their wallet directly to your dApp. Chain-Fi handles all backend authentication and can access user wallet addresses (if user grants permission) without requiring wallet connection. For transactions, users can optionally provide wallet signature for additional security (3FA), but this is handled through Chain-Fi, not direct wallet connection to your dApp.

Which blockchain networks does Chain-Fi OAuth support?

Chain-Fi OAuth works across all Chain-Fi-supported networks: Base (Coinbase L2), Arbitrum (Optimistic Rollup), Optimism (Optimistic Rollup), Polygon (PoS Chain), and Ethereum mainnet. One OAuth integration works for all networks. User wallet addresses are returned for all networks where the user has bound wallets. You can filter or request specific network addresses based on your dApp's needs.

How do I get started with Chain-Fi OAuth?

To get started: 1) Create a Chain-Fi account (free account creation), 2) Navigate to developer dashboard and register your application, 3) Receive your client ID and client secret, 4) Configure your redirect URIs and requested scopes, 5) Follow the integration guide to add OAuth flow to your dApp, 6) Test in development environment, 7) Deploy to production. Full documentation, code examples, and SDK support are available. The integration typically takes 1-2 hours for experienced developers.

What is the difference between Chain-Fi OAuth and traditional wallet connections?

Traditional wallet connections require users to connect their wallet (MetaMask, WalletConnect, etc.) directly to each dApp. Chain-Fi OAuth provides: Unified identity (authenticate once, access all dApps), Multi-factor security (email/password + mobile 2FA vs. just wallet signature), Permission-based data access (users control what data is shared), KYC verification (access to user verification status), No repeated wallet connections (authenticate with Chain-Fi, not each dApp), and Better UX (familiar email/password login vs. wallet popups). Chain-Fi OAuth is designed for dApps that want secure authentication without wallet connection complexity.

Can I use Chain-Fi OAuth with existing authentication systems?

Yes! Chain-Fi OAuth can be integrated alongside existing authentication systems. You can: Offer Chain-Fi OAuth as an additional login option (alongside email/password, social login, etc.), Use Chain-Fi OAuth for Web3-specific features while keeping traditional auth for other features, Migrate users gradually by offering both options, or Use Chain-Fi OAuth as primary authentication and sync user data to your existing system. The OAuth flow is independent and doesn't interfere with other authentication methods.

How do I handle token refresh with Chain-Fi OAuth?

Chain-Fi OAuth provides refresh tokens for long-term access. When your access token expires, use the refresh token to obtain a new access token: POST to token endpoint with grant_type=refresh_token, refresh_token, client_id, and client_secret. Refresh tokens are long-lived but can be revoked by users. Store refresh tokens securely server-side (never in frontend). Implement automatic token refresh before expiration. Handle refresh token expiration by redirecting user to re-authenticate. Full token management documentation is available in the developer portal.

What happens if a user revokes access to my dApp?

If a user revokes access: Your access tokens and refresh tokens are immediately invalidated, Subsequent API calls will return 401 Unauthorized, You should handle this gracefully by redirecting user to re-authenticate, User can re-authorize your dApp at any time, and All previously granted permissions are reset. Users can revoke access from their Chain-Fi account settings. It's recommended to implement token refresh error handling that detects revoked access and prompts re-authentication.

Can I customize the OAuth authorization screen?

The authorization screen is managed by Chain-Fi to ensure security and consistency. However, you can customize: Application name and description (shown to users), Application logo (displayed on authorization screen), Website URL (linked from authorization screen), and Requested scopes (determines what permissions are requested). The authorization screen shows your app information, requested permissions, and allows users to approve or deny access. This ensures users always see consistent, secure authorization flows.

How do I test Chain-Fi OAuth integration?

To test Chain-Fi OAuth: 1) Register a test application in developer dashboard, 2) Use test redirect URIs (localhost is supported for development), 3) Create test Chain-Fi accounts, 4) Test full OAuth flow (authorization → callback → token exchange → userinfo), 5) Test error scenarios (denied access, invalid codes, expired tokens), 6) Test token refresh flow, 7) Test with different scopes and permissions, 8) Use Chain-Fi's test environment for development. Full testing guide and test credentials are available in the developer documentation.

What are the rate limits for Chain-Fi OAuth API?

Chain-Fi OAuth API rate limits ensure fair usage: Authorization requests: 100 requests per minute per client ID, Token exchange: 60 requests per minute per client ID, Userinfo requests: 120 requests per minute per access token, Refresh token requests: 30 requests per minute per client ID. Rate limits are per client ID (not per user). Exceeding limits returns 429 Too Many Requests with Retry-After header. Enterprise tier applications can request higher rate limits. Rate limit headers are included in all API responses.

Is Chain-Fi OAuth free to use?

Chain-Fi OAuth is included in all Chain-Fi membership tiers. For dApp developers: OAuth integration and API access are free, No per-request fees or transaction fees, Standard rate limits apply (Enterprise tier can request higher limits), and No additional costs beyond standard Chain-Fi membership. For end users: OAuth authentication is free (part of Chain-Fi account), Users need a Chain-Fi account (free account creation), and Membership includes full access to all Chain-Fi services including OAuth. All membership tiers include monthly credits for gasless transactions.

Can I use Chain-Fi OAuth for mobile apps?

Yes! Chain-Fi OAuth works with mobile apps using standard OAuth 2.0 flows: For native mobile apps, use custom URL schemes or universal links for redirects, For React Native/Flutter apps, use deep linking, For mobile web apps, use standard redirect flow, Chain-Fi mobile app provides 2FA via QR code scan, and All OAuth endpoints are mobile-friendly. Mobile apps should use PKCE (Proof Key for Code Exchange) for additional security. Full mobile integration guide is available in the developer documentation.

How does Chain-Fi OAuth handle user privacy?

Chain-Fi OAuth is privacy-first: Permission-based access (users explicitly grant each permission), No data mining (only requested data is shared), Users can revoke access anytime, Minimal data sharing (only what's necessary for your dApp), Encrypted data transmission, No tracking or analytics on user behavior, Users see exactly what data is requested before granting access, and Complete transparency in authorization screen. Chain-Fi never shares user data without explicit consent. Users maintain full control over their data.

What programming languages are supported for Chain-Fi OAuth integration?

Chain-Fi OAuth works with any programming language that can make HTTP requests and handle OAuth 2.0 flows. Popular integrations include: JavaScript/TypeScript (Node.js, React, Vue, Angular), Python (Django, Flask, FastAPI), Go (Gin, Echo), PHP (Laravel, Symfony), Ruby (Rails), Java (Spring Boot), C# (.NET), and Rust. Chain-Fi provides: RESTful API (works with any HTTP client), SDKs for popular languages (JavaScript, Python, Go), Code examples for common frameworks, and Full API documentation. The OAuth 2.0 protocol is language-agnostic.

Can I use Chain-Fi OAuth for enterprise applications?

Yes! Chain-Fi OAuth is designed for enterprise use: Enterprise-grade security (multi-factor authentication, audit logging), Compliance support (KYC verification, data protection), Custom rate limits for Enterprise tier, Priority support and dedicated account management, White-label options (contact for details), Custom integrations and API access, SLA guarantees, and Enterprise onboarding assistance. Enterprise applications can request custom scopes, higher rate limits, and dedicated infrastructure. Contact Chain-Fi sales for enterprise pricing and custom solutions.

Chain-Fi OAuth

Autenticación Web3 Controlada por el Usuario

Chain-Fi OAuth permite autenticación y autorización de acciones seguras y sin problemas para sus aplicaciones Web3. Los usuarios se autentican con su identidad Chain-Fi (correo electrónico/contraseña + 2FA móvil) y otorgan acceso a paquetes de datos basados en permisos para su dApp o plataforma empresarial.

Basado en los permisos otorgados, su plataforma puede solicitar acciones que se realizarán con la billetera o bóveda del usuario. Seguridad crítica: Las plataformas NUNCA pueden invocar pagos de billetera directamente. Todas las operaciones, incluidos los pagos de billetera, requieren 2FA obligatorio: los usuarios deben firmar primero un código QR con su aplicación móvil Chain-Fi antes de que se invoque cualquier operación de billetera. Solo entonces se envía la carga útil de la billetera para la firma. Las operaciones de bóveda requieren 3FA (2FA + atestación del guardián para el pago de gas). Esta seguridad multicapa solo es posible debido al entorno protegido inteligente de Chain-Fi.

Construido sobre el flujo de código de autorización OAuth 2.0 con seguridad de nivel empresarial. Sus usuarios obtienen una identidad unificada en todas las dApps, mientras que usted obtiene una integración simple que funciona en Base, Arbitrum, Optimism, Polygon y la red principal de Ethereum.

Ver Guía de Integración Saber Más

Marketplace

Featured Collections

AllArtGaming

Cosmic #1234

2.5 ETH

Digital Art #567

1.8 ETH

Pixel Hero #890

3.2 ETH

Chain-Fi App

OAuth 2.0

Protocolo Estándar

2FA/3FA

Seguridad Multifactor

5+ Redes Blockchain

Privacidad

Basado en Permisos

Cómo Funciona Chain-Fi OAuth

Flujo de autenticación simple y seguro que elimina la complejidad de la conexión de billetera

El Usuario Visita Su dApp

El usuario hace clic en "Iniciar sesión con Chain-Fi" en su dApp. Su aplicación redirige al endpoint de autorización de Chain-Fi con su ID de cliente y los alcances solicitados.

Escanear Solicitud de Inicio de Sesión

El usuario escanea el código QR con la aplicación móvil Chain-Fi para iniciar el inicio de sesión. Este es el primer paso del 2FA obligatorio: los usuarios deben autenticarse a través de la aplicación móvil antes de cualquier operación.

Autorizar Permisos para dApp

El usuario revisa y otorga acceso a datos basado en permisos. El usuario ve exactamente qué datos accederá su dApp (perfil, correo electrónico, dirección de billetera, etc.) y puede aprobar o denegar permisos específicos.

El Backend Valida la Conexión

Su backend recibe el código de autorización y valida la solicitud de conexión. El backend intercambia el código por token de acceso y token de actualización usando su secreto de cliente. Todas las operaciones de tokens ocurren en el servidor por seguridad.

Estado de Inicio de Sesión Enviado al Frontend

Después de la validación exitosa, su backend envía el estado de inicio de sesión a su frontend. Su dApp actualiza la interfaz de usuario para mostrar el estado autenticado (por ejemplo, panel de mercado, perfil de usuario, etc.). El usuario ahora está completamente conectado y puede interactuar con su plataforma.

¿Por Qué Elegir Chain-Fi OAuth?

Autenticación de nivel empresarial diseñada para aplicaciones Web3

¿Qué Hace Diferente a Chain-Fi OAuth?

A diferencia de la autenticación Web3 tradicional, Chain-Fi proporciona un entorno seguro y aislado que protege a los usuarios mientras permite una integración perfecta de dApp

2FA Obligatorio Antes de Operaciones de Billetera

A diferencia de MetaMask, WalletConnect o Web3Auth: Las plataformas NUNCA pueden invocar pagos de billetera directamente. Todas las operaciones requieren 2FA obligatorio: los usuarios deben firmar primero un código QR con su aplicación móvil Chain-Fi antes de que se inicie cualquier operación de billetera. Las operaciones de bóveda requieren 3FA (2FA + atestación del guardián). Este paso crítico de seguridad solo es posible debido al entorno protegido inteligente de Chain-Fi.

Prueba y Ejecución de Transacciones

A diferencia del OAuth tradicional (Auth0, Okta): Chain-Fi no solo autentica usuarios: ejecutamos transacciones y proporcionamos prueba verificable de ejecución. Su plataforma recibe hashes de transacciones, números de bloque y prueba criptográfica para actualizar su base de datos o frontend con confianza.

No Se Requiere Conexión de Billetera

A diferencia de Magic Link o Web3Auth: Los usuarios se autentican con correo electrónico/contraseña + 2FA móvil: no se requiere extensión del navegador ni aplicación de billetera. Esto reduce drásticamente la fricción y hace que Web3 sea accesible para usuarios no nativos de cripto mientras mantiene la seguridad de nivel empresarial.

Autorización de Acciones, No Solo Autenticación

A diferencia de los proveedores OAuth estándar: Chain-Fi OAuth permite solicitudes de acciones basadas en permisos. Su plataforma puede solicitar pagos, transferencias u otras acciones de blockchain. Los usuarios inician sesión en el entorno confiable de Chain-Fi, y usted recibe prueba de ejecución, todo sin manejar conexiones de billetera.

Nativo Multi-Cadena

A diferencia de las soluciones de cadena única: Chain-Fi OAuth funciona perfectamente en Base, Arbitrum, Optimism, Polygon y la red principal de Ethereum. Una integración, todas las redes. Los usuarios pueden interactuar con dApps multi-cadena sin gestionar conexiones de billetera separadas por red.

Paquetes de Datos Basados en Permisos

A diferencia del acceso de todo o nada: Los usuarios otorgan explícitamente permisos para paquetes de datos específicos (perfil, correo electrónico, actividad, direcciones de billetera). Basado en estos permisos, su plataforma puede solicitar acciones específicas. Los usuarios mantienen control total sobre qué datos y acciones se comparten.

La Ventaja de Chain-Fi

Chain-Fi OAuth combina la seguridad de las operaciones de billetera aisladas con la conveniencia del OAuth tradicional. A diferencia de las soluciones que requieren conexiones de billetera (arriesgando phishing y acceso no autorizado) o OAuth tradicional (sin capacidades de transacciones blockchain), Chain-Fi proporciona una solución completa: autenticación segura, autorización de acciones y ejecución de transacciones verificable, todo dentro de un entorno confiable y aislado.

🔒 Innovación de Seguridad Crítica: Las plataformas NUNCA pueden invocar pagos de billetera directamente. Cada operación requiere 2FA obligatorio (firma de código QR con la aplicación Chain-Fi) antes de que se inicien las operaciones de billetera. Las operaciones de bóveda requieren 3FA (2FA + atestación del guardián). Esta protección multicapa solo es posible debido al sistema de callback de Chain-Fi: los usuarios siempre firman en el frontend del módulo de Chain-Fi, nunca en el frontend de su cliente.

🏆 Primero en el Mercado: Chain-Fi es el primero en llevar este paquete completo al mercado. Mientras que los competidores ofrecen características individuales (Web3Auth tiene 2FA, D3fenders tiene protección de bóveda, Auth0 tiene OAuth), ninguna otra solución combina OAuth 2.0 + 2FA obligatorio antes de operaciones de billetera + sistema de callback + ejecución de transacciones + operaciones de bóveda 3FA + soporte multi-cadena en una plataforma integrada. Esta es la primera solución OAuth Web3 lista para producción que elimina las conexiones directas de billetera mientras mantiene la seguridad de nivel empresarial.

Guía Rápida de Integración

Comience en minutos con nuestro proceso de integración simple

Step 1

Registrar Su Aplicación

Cree una cuenta Chain-Fi y registre su dApp en el panel de desarrollador. Recibirá:

ID de Cliente (identificador público)
Secreto de Cliente (mantener seguro, solo backend)
Configuración de URI de Redirección
Configuración de Permisos de Alcance

Step 2

Agregar Botón de Autorización

Agregue el botón "Iniciar sesión con Chain-Fi" a su dApp. Redirija a los usuarios a:

https://module.chain-fi.io/oauth/authorize?
  client_id=YOUR_CLIENT_ID
  &redirect_uri=YOUR_CALLBACK_URL
  &response_type=code
  &scope=profile email
  &state=RANDOM_STATE_STRING

Step 3

Manejar Callback

Cree un endpoint de callback que reciba el código de autorización:

POST /api/oauth/token
{
  "code": "authorization_code",
  "client_id": "YOUR_CLIENT_ID",
  "client_secret": "YOUR_CLIENT_SECRET",
  "redirect_uri": "YOUR_CALLBACK_URL",
  "grant_type": "authorization_code"
}

Step 4

Acceder a Datos del Usuario

Use el token de acceso para recuperar información del usuario:

GET /api/oauth/userinfo
Authorization: Bearer ACCESS_TOKEN

Response:
{
  "id": "user_id",
  "email": "user@example.com",
  "name": "User Name",
  "kyc_verified": true,
  "wallet_addresses": [...]
}

Step 5

Solicitar Acciones (Opcional)

Basado en los permisos otorgados, su plataforma puede solicitar acciones que se realizarán con la billetera o bóveda del usuario:

POST /api/oauth/actions/request
{
  "action": "initiate_payment",
  "amount": "100",
  "currency": "ETH",
  "recipient": "0x...",
  "access_token": "user_access_token"
}

Seguridad crítica: El usuario DEBE firmar primero un código QR con su aplicación móvil Chain-Fi (2FA obligatorio) antes de que se inicie cualquier operación de billetera. Las plataformas NUNCA pueden invocar pagos de billetera directamente. Después del 2FA, la carga útil de la billetera se envía para la firma. Las operaciones de bóveda requieren 3FA (2FA + atestación del guardián). Todas las operaciones ocurren exclusivamente dentro del entorno protegido inteligente de Chain-Fi, nunca directamente en su dApp.

Step 6

Recibir Prueba de Transacción

Después de que el usuario autorice la acción en el entorno seguro de Chain-Fi, Chain-Fi ejecuta la transacción y proporciona prueba:

Response:
{
  "transaction_hash": "0x...",
  "block_number": 12345,
  "status": "confirmed",
  "proof": {
    "signature": "...",
    "timestamp": "...",
    "execution_id": "..."
  }
}

Su backend puede usar esta prueba de transacción para actualizar su base de datos o frontend, completando el flujo de acción.

Ver Documentación Completa

Seguridad y Privacidad

Construido con seguridad y privacidad como principios fundamentales

Estándar OAuth 2.0

Flujo de código de autorización estándar de la industria con soporte PKCE. Protocolos de seguridad probados en batalla.

Protección CSRF

La validación del parámetro de estado previene ataques de falsificación de solicitudes entre sitios. Todas las redirecciones se validan.

Almacenamiento Seguro de Tokens

Los tokens de acceso son de corta duración. Los tokens de actualización se almacenan de forma segura en el servidor. Nunca expuestos al frontend.

Privacidad Primero

Los usuarios controlan qué datos se comparten. Acceso basado en permisos con consentimiento explícito. Sin minería de datos.

Datos Encriptados

Todos los datos del usuario encriptados en reposo y en tránsito. Cifrado AES-256-GCM para información sensible.

Registro de Auditoría

Rastro de auditoría completo de todos los eventos de autenticación. Monitoreo de seguridad y detección de amenazas.

Casos de Uso

Perfecto para cualquier aplicación Web3 que necesite autenticación segura

¿Listo para Integrar Chain-Fi OAuth?

Comience a construir autenticación Web3 segura para su dApp. Comience en minutos con nuestra documentación completa y herramientas de desarrollador.

Comenzar

Ver Documentación

Chain-Fi OAuth

Autenticación Web3 Controlada por el Usuario

Featured Collections

Cómo Funciona Chain-Fi OAuth

El Usuario Visita Su dApp

Escanear Solicitud de Inicio de Sesión

Autorizar Permisos para dApp

El Backend Valida la Conexión

Estado de Inicio de Sesión Enviado al Frontend

¿Por Qué Elegir Chain-Fi OAuth?

Seguridad Multifactor

Paquete de Datos Basado en Permisos

Identidad Unificada

Integración Simple

2FA Obligatorio Antes de Operaciones de Billetera

Prueba y Ejecución de Transacciones

Soporte Multi-Cadena

¿Qué Hace Diferente a Chain-Fi OAuth?

2FA Obligatorio Antes de Operaciones de Billetera

Prueba y Ejecución de Transacciones

No Se Requiere Conexión de Billetera

Autorización de Acciones, No Solo Autenticación

Nativo Multi-Cadena

Paquetes de Datos Basados en Permisos

La Ventaja de Chain-Fi

Guía Rápida de Integración

Registrar Su Aplicación

Agregar Botón de Autorización

Manejar Callback

Acceder a Datos del Usuario

Solicitar Acciones (Opcional)

Recibir Prueba de Transacción

Seguridad y Privacidad

Estándar OAuth 2.0

Protección CSRF

Almacenamiento Seguro de Tokens

Privacidad Primero

Datos Encriptados

Registro de Auditoría

Casos de Uso

Plataformas DeFi

Mercados NFT

Juegos Web3

Plataformas DAO

Plataformas de Comercio

dApps Empresariales

¿Listo para Integrar Chain-Fi OAuth?

Chain-Fi OAuth - User-Controlled Web3 Authentication

How Chain-Fi OAuth Works

Integration Guide

Security Features

Use Cases