What is ChainGuard OAuth?

ChainGuard OAuth is a user-controlled authentication service for Web3 applications. It enables dApps to authenticate users using their ChainGuard 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 ChainGuard OAuth work?

ChainGuard OAuth follows the standard OAuth 2.0 authorization code flow: 1) User clicks "Sign in with ChainGuard" on your dApp, 2) User authenticates with ChainGuard (email/password = 1FA, QR code scan = 2FA), 3) User grants permission-based data access, 4) ChainGuard 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 ChainGuard - users never connect wallets directly to your dApp.

What are the benefits of using ChainGuard OAuth?

ChainGuard 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 ChainGuard OAuth into my dApp?

Integrate ChainGuard OAuth in four steps: 1) Register your application in ChainGuard developer dashboard to get client ID and client secret, 2) Add "Sign in with ChainGuard" button that redirects to ChainGuard 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 ChainGuard userinfo endpoint and retrieve authorized user data. Full documentation and code examples are available in the developer portal.

What data can I access through ChainGuard 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 ChainGuard OAuth secure?

Yes, ChainGuard 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 ChainGuard OAuth?

No! That's one of the key benefits of ChainGuard OAuth. Users authenticate with ChainGuard using email/password (1FA) and mobile QR code scan (2FA). They never need to connect their wallet directly to your dApp. ChainGuard 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 ChainGuard, not direct wallet connection to your dApp.

Which blockchain networks does ChainGuard OAuth support?

ChainGuard OAuth works across all ChainGuard-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 ChainGuard OAuth?

To get started: 1) Create a ChainGuard 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 ChainGuard OAuth and traditional wallet connections?

Traditional wallet connections require users to connect their wallet (MetaMask, WalletConnect, etc.) directly to each dApp. ChainGuard 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 ChainGuard, not each dApp), and Better UX (familiar email/password login vs. wallet popups). ChainGuard OAuth is designed for dApps that want secure authentication without wallet connection complexity.

Can I use ChainGuard OAuth with existing authentication systems?

Yes! ChainGuard OAuth can be integrated alongside existing authentication systems. You can: Offer ChainGuard OAuth as an additional login option (alongside email/password, social login, etc.), Use ChainGuard OAuth for Web3-specific features while keeping traditional auth for other features, Migrate users gradually by offering both options, or Use ChainGuard 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 ChainGuard OAuth?

ChainGuard 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 ChainGuard 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 ChainGuard 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 ChainGuard OAuth integration?

To test ChainGuard OAuth: 1) Register a test application in developer dashboard, 2) Use test redirect URIs (localhost is supported for development), 3) Create test ChainGuard 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 ChainGuard's test environment for development. Full testing guide and test credentials are available in the developer documentation.

What are the rate limits for ChainGuard OAuth API?

ChainGuard 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 ChainGuard OAuth free to use?

ChainGuard OAuth is included in all ChainGuard 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 ChainGuard membership. For end users: OAuth authentication is free (part of ChainGuard account), Users need a ChainGuard account (free account creation), and Membership includes full access to all ChainGuard services including OAuth. All membership tiers include monthly credits for gasless transactions.

Can I use ChainGuard OAuth for mobile apps?

Yes! ChainGuard 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, ChainGuard 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 ChainGuard OAuth handle user privacy?

ChainGuard 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. ChainGuard never shares user data without explicit consent. Users maintain full control over their data.

What programming languages are supported for ChainGuard OAuth integration?

ChainGuard 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. ChainGuard 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 ChainGuard OAuth for enterprise applications?

Yes! ChainGuard 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 ChainGuard sales for enterprise pricing and custom solutions.

What is ChainGuard OAuth?

ChainGuard OAuth is a user-controlled authentication service for Web3 applications. It enables dApps to authenticate users using their ChainGuard 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 ChainGuard OAuth work?

ChainGuard OAuth follows the standard OAuth 2.0 authorization code flow: 1) User clicks "Sign in with ChainGuard" on your dApp, 2) User authenticates with ChainGuard (email/password = 1FA, QR code scan = 2FA), 3) User grants permission-based data access, 4) ChainGuard 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 ChainGuard - users never connect wallets directly to your dApp.

What are the benefits of using ChainGuard OAuth?

ChainGuard 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 ChainGuard OAuth into my dApp?

Integrate ChainGuard OAuth in four steps: 1) Register your application in ChainGuard developer dashboard to get client ID and client secret, 2) Add "Sign in with ChainGuard" button that redirects to ChainGuard 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 ChainGuard userinfo endpoint and retrieve authorized user data. Full documentation and code examples are available in the developer portal.

What data can I access through ChainGuard 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 ChainGuard OAuth secure?

Yes, ChainGuard 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 ChainGuard OAuth?

No! That's one of the key benefits of ChainGuard OAuth. Users authenticate with ChainGuard using email/password (1FA) and mobile QR code scan (2FA). They never need to connect their wallet directly to your dApp. ChainGuard 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 ChainGuard, not direct wallet connection to your dApp.

Which blockchain networks does ChainGuard OAuth support?

ChainGuard OAuth works across all ChainGuard-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 ChainGuard OAuth?

To get started: 1) Create a ChainGuard 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 ChainGuard OAuth and traditional wallet connections?

Traditional wallet connections require users to connect their wallet (MetaMask, WalletConnect, etc.) directly to each dApp. ChainGuard 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 ChainGuard, not each dApp), and Better UX (familiar email/password login vs. wallet popups). ChainGuard OAuth is designed for dApps that want secure authentication without wallet connection complexity.

Can I use ChainGuard OAuth with existing authentication systems?

Yes! ChainGuard OAuth can be integrated alongside existing authentication systems. You can: Offer ChainGuard OAuth as an additional login option (alongside email/password, social login, etc.), Use ChainGuard OAuth for Web3-specific features while keeping traditional auth for other features, Migrate users gradually by offering both options, or Use ChainGuard 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 ChainGuard OAuth?

ChainGuard 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 ChainGuard 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 ChainGuard 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 ChainGuard OAuth integration?

To test ChainGuard OAuth: 1) Register a test application in developer dashboard, 2) Use test redirect URIs (localhost is supported for development), 3) Create test ChainGuard 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 ChainGuard's test environment for development. Full testing guide and test credentials are available in the developer documentation.

What are the rate limits for ChainGuard OAuth API?

ChainGuard 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 ChainGuard OAuth free to use?

ChainGuard OAuth is included in all ChainGuard 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 ChainGuard membership. For end users: OAuth authentication is free (part of ChainGuard account), Users need a ChainGuard account (free account creation), and Membership includes full access to all ChainGuard services including OAuth. All membership tiers include monthly credits for gasless transactions.

Can I use ChainGuard OAuth for mobile apps?

Yes! ChainGuard 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, ChainGuard 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 ChainGuard OAuth handle user privacy?

ChainGuard 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. ChainGuard never shares user data without explicit consent. Users maintain full control over their data.

What programming languages are supported for ChainGuard OAuth integration?

ChainGuard 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. ChainGuard 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 ChainGuard OAuth for enterprise applications?

Yes! ChainGuard 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 ChainGuard sales for enterprise pricing and custom solutions.

ChainGuard OAuth

Benutzerkontrollierte Web3-Authentifizierung

ChainGuard OAuth ermöglicht nahtlose, sichere Authentifizierung und Aktionsautorisierung für Ihre Web3-Anwendungen. Benutzer authentifizieren sich mit ihrer ChainGuard-Identität (E-Mail/Passwort + mobiles 2FA) und gewähren berechtigungsbasierten Datenpaketzugriff für Ihre dApp oder Unternehmensplattform.

Basierend auf gewährten Berechtigungen kann Ihre Plattform Aktionen anfordern, die mit der Wallet oder dem Vault des Benutzers ausgeführt werden sollen. Kritische Sicherheit: Plattformen können NIEMALS Wallet-Zahlungen direkt aufrufen. Alle Operationen, einschließlich Wallet-Zahlungen, erfordern obligatorisches 2FA - Benutzer müssen zuerst einen QR-Code mit ihrer ChainGuard-Mobil-App signieren, bevor eine Wallet-Operation aufgerufen wird. Erst dann wird die Wallet-Nutzlast zur Signatur gesendet. Vault-Operationen erfordern 3FA (2FA + Guardian-Attestierung für Gas-Zahlung). Diese mehrschichtige Sicherheit ist nur aufgrund von ChainGuards intelligentem abgeschirmtem Umfeld möglich.

Basiert auf OAuth 2.0 Authorization Code Flow mit Unternehmenssicherheit. Ihre Benutzer erhalten eine einheitliche Identität über alle dApps hinweg, während Sie eine einfache Integration erhalten, die über Base, Arbitrum, Optimism, Polygon und Ethereum Mainnet funktioniert.

Integrationsleitfaden anzeigen Mehr erfahren

Marketplace

Featured Collections

AllArtGaming

Cosmic #1234

2.5 ETH

Digital Art #567

1.8 ETH

Pixel Hero #890

3.2 ETH

ChainGuard App

OAuth 2.0

Standardprotokoll

2FA/3FA

Multi-Faktor-Sicherheit

5+ Blockchain-Netzwerke

Datenschutz

Berechtigungsbasiert

Wie ChainGuard OAuth funktioniert

Einfacher, sicherer Authentifizierungsablauf, der die Komplexität der Wallet-Verbindung eliminiert

Benutzer besucht Ihre dApp

Benutzer klickt auf "Mit ChainGuard anmelden" in Ihrer dApp. Ihre App leitet zur ChainGuard-Autorisierungsendpunkt mit Ihrer Client-ID und angeforderten Bereichen um.

Anmeldeanfrage scannen

Benutzer scannt QR-Code mit ChainGuard-Mobil-App, um die Anmeldung zu initiieren. Dies ist der erste Schritt des obligatorischen 2FA - Benutzer müssen sich über die Mobil-App authentifizieren, bevor eine Operation stattfindet.

Berechtigungen für dApp autorisieren

Benutzer überprüft und gewährt berechtigungsbasierten Datenzugriff. Benutzer sieht genau, auf welche Daten Ihre dApp zugreifen wird (Profil, E-Mail, Wallet-Adresse usw.) und kann spezifische Berechtigungen genehmigen oder ablehnen.

Backend validiert Verbindung

Ihr Backend empfängt den Autorisierungscode und validiert die Verbindungsanfrage. Backend tauscht den Code gegen Access Token und Refresh Token mit Ihrem Client-Secret aus. Alle Token-Operationen erfolgen serverseitig für Sicherheit.

Anmeldestatus wird an Frontend gesendet

Nach erfolgreicher Validierung sendet Ihr Backend den Anmeldestatus an Ihr Frontend. Ihre dApp aktualisiert die Benutzeroberfläche, um den authentifizierten Status anzuzeigen (z. B. Marktplatz-Dashboard, Benutzerprofil usw.). Benutzer ist jetzt vollständig angemeldet und kann mit Ihrer Plattform interagieren.

Warum ChainGuard OAuth wählen?

Unternehmenssicherheit für Web3-Anwendungen

Was macht ChainGuard OAuth anders?

Im Gegensatz zur traditionellen Web3-Authentifizierung bietet ChainGuard eine sichere, isolierte Umgebung, die Benutzer schützt und gleichzeitig nahtlose dApp-Integration ermöglicht

Obligatorisches 2FA vor Wallet-Operationen

Im Gegensatz zu MetaMask, WalletConnect oder Web3Auth: Plattformen können NIEMALS Wallet-Zahlungen direkt aufrufen. Alle Operationen erfordern obligatorisches 2FA - Benutzer müssen zuerst einen QR-Code mit ihrer ChainGuard-Mobil-App signieren, bevor eine Wallet-Operation überhaupt initiiert wird. Vault-Operationen erfordern 3FA (2FA + Guardian-Attestierung). Dieser kritische Sicherheitsschritt ist nur aufgrund von ChainGuards intelligentem abgeschirmtem Umfeld möglich.

Transaktionsnachweis & Ausführung

Im Gegensatz zu traditionellem OAuth (Auth0, Okta): ChainGuard authentifiziert nicht nur Benutzer - wir führen Transaktionen aus und bieten nachweisbaren Ausführungsnachweis. Ihre Plattform erhält Transaktions-Hashes, Blocknummern und kryptografischen Beweis, um Ihre Datenbank oder Ihr Frontend mit Vertrauen zu aktualisieren.

Keine Wallet-Verbindung erforderlich

Im Gegensatz zu Magic Link oder Web3Auth: Benutzer authentifizieren sich mit E-Mail/Passwort + mobilem 2FA - keine Browser-Erweiterung oder Wallet-App erforderlich. Dies reduziert die Reibung erheblich und macht Web3 für nicht-krypto-native Benutzer zugänglich, während Unternehmenssicherheit gewährleistet wird.

Aktionsautorisierung, nicht nur Auth

Im Gegensatz zu Standard-OAuth-Anbietern: ChainGuard OAuth ermöglicht Aktionsanfragen basierend auf Berechtigungen. Ihre Plattform kann Zahlungen, Überweisungen oder andere Blockchain-Aktionen anfordern. Benutzer melden sich in ChainGuards vertrauenswürdiger Umgebung an, und Sie erhalten Ausführungsnachweis - alles ohne Wallet-Verbindungen zu handhaben.

Multi-Chain-Nativ

Im Gegensatz zu Single-Chain-Lösungen: ChainGuard OAuth funktioniert nahtlos über Base, Arbitrum, Optimism, Polygon und Ethereum Mainnet. Eine Integration, alle Netzwerke. Benutzer können mit Multi-Chain-dApps interagieren, ohne separate Wallet-Verbindungen pro Netzwerk zu verwalten.

Berechtigungsbasierte Datenpakete

Im Gegensatz zu Alles-oder-Nichts-Zugriff: Benutzer gewähren explizit Berechtigungen für spezifische Datenpakete (Profil, E-Mail, Aktivität, Wallet-Adressen). Basierend auf diesen Berechtigungen kann Ihre Plattform spezifische Aktionen anfordern. Benutzer behalten die volle Kontrolle darüber, welche Daten und Aktionen geteilt werden.

Der ChainGuard-Vorteil

ChainGuard OAuth kombiniert die Sicherheit isolierter Wallet-Operationen mit der Bequemlichkeit von traditionellem OAuth. Im Gegensatz zu Lösungen, die Wallet-Verbindungen erfordern (mit Risiko von Phishing und unbefugtem Zugriff) oder traditionellem OAuth (ohne Blockchain-Transaktionsfähigkeiten), bietet ChainGuard eine vollständige Lösung: sichere Authentifizierung, Aktionsautorisierung und nachweisbare Transaktionsausführung - alles innerhalb einer vertrauenswürdigen, isolierten Umgebung.

🔒 Kritische Sicherheitsinnovation: Plattformen können NIEMALS Wallet-Zahlungen direkt aufrufen. Jede Operation erfordert obligatorisches 2FA (QR-Code-Signatur mit ChainGuard-App), bevor Wallet-Operationen überhaupt initiiert werden. Vault-Operationen erfordern 3FA (2FA + Guardian-Attestierung). Dieser mehrschichtige Schutz ist nur aufgrund von ChainGuards Callback-System möglich - Benutzer signieren immer in ChainGuards Modul-Frontend, niemals in Ihrem Client-Frontend.

🏆 Marktführer: ChainGuard ist der Erste, der dieses komplette Paket auf den Markt bringt. Während Konkurrenten einzelne Funktionen anbieten (Web3Auth hat 2FA, D3fenders hat Vault-Schutz, Auth0 hat OAuth), kombiniert keine andere Lösung OAuth 2.0 + obligatorisches 2FA vor Wallet-Operationen + Callback-System + Transaktionsausführung + 3FA-Vault-Operationen + Multi-Chain-Unterstützung in einer integrierten Plattform. Dies ist die erste produktionsreife Web3-OAuth-Lösung, die direkte Wallet-Verbindungen eliminiert und gleichzeitig Unternehmenssicherheit gewährleistet.

Schneller Integrationsleitfaden

Starten Sie in Minuten mit unserem einfachen Integrationsprozess

Step 1

Ihre Anwendung registrieren

Erstellen Sie ein ChainGuard-Konto und registrieren Sie Ihre dApp im Entwickler-Dashboard. Sie erhalten:

Client-ID (öffentlicher Identifikator)
Client-Secret (sicher aufbewahren, nur Backend)
Redirect-URI-Konfiguration
Bereichsberechtigungs-Setup

Step 2

Autorisierungsbutton hinzufügen

Fügen Sie "Mit ChainGuard anmelden" Button zu Ihrer dApp hinzu. Leiten Sie Benutzer um zu:

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

Callback behandeln

Erstellen Sie einen Callback-Endpunkt, der den Autorisierungscode empfängt:

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

Auf Benutzerdaten zugreifen

Verwenden Sie den Access Token, um Benutzerinformationen abzurufen:

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

Aktionen anfordern (Optional)

Basierend auf gewährten Berechtigungen kann Ihre Plattform Aktionen anfordern, die mit der Wallet oder dem Vault des Benutzers ausgeführt werden sollen:

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

Kritische Sicherheit: Der Benutzer MUSS zuerst einen QR-Code mit seiner ChainGuard-Mobil-App signieren (obligatorisches 2FA), bevor eine Wallet-Operation initiiert wird. Plattformen können NIEMALS Wallet-Zahlungen direkt aufrufen. Nach 2FA wird die Wallet-Nutzlast zur Signatur gesendet. Vault-Operationen erfordern 3FA (2FA + Guardian-Attestierung). Alle Operationen erfolgen ausschließlich innerhalb von ChainGuards intelligentem abgeschirmtem Umfeld - niemals direkt in Ihrer dApp.

Step 6

Transaktionsnachweis erhalten

Nachdem der Benutzer die Aktion in ChainGuards sicherer Umgebung autorisiert hat, führt ChainGuard die Transaktion aus und bietet Nachweis:

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

Ihr Backend kann diesen Transaktionsnachweis verwenden, um Ihre Datenbank oder Ihr Frontend zu aktualisieren und den Aktionsablauf abzuschließen.

Vollständige Dokumentation anzeigen

Sicherheit & Datenschutz

Gebaut mit Sicherheit und Datenschutz als Kernprinzipien

OAuth 2.0 Standard

Branchenüblicher Authorization Code Flow mit PKCE-Unterstützung. Erprobte Sicherheitsprotokolle.

CSRF-Schutz

State-Parameter-Validierung verhindert Cross-Site-Request-Forgery-Angriffe. Alle Umleitungen werden validiert.

Sichere Token-Speicherung

Access Tokens sind kurzlebig. Refresh Tokens werden serverseitig sicher gespeichert. Niemals dem Frontend ausgesetzt.

Datenschutz zuerst

Benutzer kontrollieren, welche Daten geteilt werden. Berechtigungsbasierter Zugriff mit ausdrücklicher Zustimmung. Kein Data Mining.

Verschlüsselte Daten

Alle Benutzerdaten verschlüsselt im Ruhezustand und während der Übertragung. AES-256-GCM-Verschlüsselung für sensible Informationen.

Audit-Protokollierung

Vollständige Audit-Spur aller Authentifizierungsereignisse. Sicherheitsüberwachung und Bedrohungserkennung.

Anwendungsfälle

Perfekt für jede Web3-Anwendung, die sichere Authentifizierung benötigt

Bereit, ChainGuard OAuth zu integrieren?

Beginnen Sie mit dem Aufbau sicherer Web3-Authentifizierung für Ihre dApp. Starten Sie in Minuten mit unserer umfassenden Dokumentation und Entwicklertools.

Loslegen

Dokumentation anzeigen

ChainGuard OAuth

Benutzerkontrollierte Web3-Authentifizierung

Featured Collections

Wie ChainGuard OAuth funktioniert

Benutzer besucht Ihre dApp

Anmeldeanfrage scannen

Berechtigungen für dApp autorisieren

Backend validiert Verbindung

Anmeldestatus wird an Frontend gesendet

Warum ChainGuard OAuth wählen?

Multi-Faktor-Sicherheit

Berechtigungsbasiertes Datenpaket

Einheitliche Identität

Einfache Integration

Obligatorisches 2FA vor Wallet-Operationen

Transaktionsnachweis & Ausführung

Multi-Chain-Unterstützung

Was macht ChainGuard OAuth anders?

Obligatorisches 2FA vor Wallet-Operationen

Transaktionsnachweis & Ausführung

Keine Wallet-Verbindung erforderlich

Aktionsautorisierung, nicht nur Auth

Multi-Chain-Nativ

Berechtigungsbasierte Datenpakete

Der ChainGuard-Vorteil

Schneller Integrationsleitfaden

Ihre Anwendung registrieren

Autorisierungsbutton hinzufügen

Callback behandeln

Auf Benutzerdaten zugreifen

Aktionen anfordern (Optional)

Transaktionsnachweis erhalten

Sicherheit & Datenschutz

OAuth 2.0 Standard

CSRF-Schutz

Sichere Token-Speicherung

Datenschutz zuerst

Verschlüsselte Daten

Audit-Protokollierung

Anwendungsfälle

DeFi-Plattformen

NFT-Marktplätze

Web3-Spiele

DAO-Plattformen

Handelsplattformen

Unternehmens-dApps

Bereit, ChainGuard OAuth zu integrieren?

ChainGuard OAuth - User-Controlled Web3 Authentication

How ChainGuard OAuth Works

Integration Guide

Security Features

Use Cases