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

Gebruikersgecontroleerde Web3-authenticatie

ChainGuard OAuth maakt naadloze, veilige authenticatie en actie-autorisatie mogelijk voor Web3-applicaties. Gebruikers authenticeren met hun ChainGuard-identiteit (e-mail/wachtwoord + mobiele 2FA) en verlenen op rechten gebaseerde data-pakket toegang aan dApps of enterprise platforms.

Op basis van verleende rechten kunnen platforms acties aanvragen die worden uitgevoerd met de portemonnee of kluis van de gebruiker. Belangrijke beveiliging: platforms kunnen NOOIT portemonnee-betalingen direct aanroepen. Alle operaties, inclusief portemonnee-betalingen, vereisen verplichte 2FA - gebruikers moeten een QR-code ondertekenen met hun ChainGuard mobiele app voordat een portemonnee-operatie wordt aangeroepen. Daarna wordt de portemonnee-payload verzonden voor ondertekening. Kluisoperaties vereisen 3FA (2FA + bewijs van bewaker voor gasbetaling). Deze gelaagde beveiliging is alleen mogelijk door ChainGuard's slimme afgeschermde omgeving.

Gebouwd op OAuth 2.0 authenticatiecode flow met enterprise-grade beveiliging. Gebruikers krijgen een geünificeerde identiteit voor alle dApps en een eenvoudige integratie die werkt op Base, Arbitrum, Optimism, Polygon en Ethereum mainnet.

Integratiehandleiding bekijken Meer informatie

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

Standaard protocol

2FA/3FA

Multi-factor beveiliging

5+ blockchain netwerken

Privacy

Op rechten gebaseerd

Hoe ChainGuard OAuth werkt

Eenvoudige, veilige authenticatiestroom die de complexiteit van portemonnee-verbindingen elimineert

Gebruiker heeft toegang tot dApp

Gebruiker klikt op "Inloggen met ChainGuard" in de dApp. De app leidt gebruikers door naar het ChainGuard authenticatie-eindpunt met client-ID en aangevraagde scopes.

Scan loginverzoek

Gebruiker scant QR-code in ChainGuard mobiele app om login te starten. Dit is de eerste stap van verplichte 2FA - gebruikers moeten authenticeren in de mobiele app voordat operaties.

Autoriseer dApp-rechten

Gebruiker bekijkt en verleent op rechten gebaseerde data-access. Gebruikers kunnen precies zien welke data de dApp toegang heeft (profiel, e-mail, portemonnee-adressen, etc.) en specifieke rechten goedkeuren of weigeren.

Backend valideert verbinding

Backend ontvangt autorisatiecode en valideert verbindingsverzoek. Backend wisselt code in voor toegangstoken en vernieuwingstoken met behulp van clientgeheim. Alle tokenoperaties vinden plaats op de server voor beveiliging.

Loginstatus verzonden naar frontend

Na succesvolle validatie verzendt backend loginstatus naar frontend. dApp werkt gebruikersinterface bij om geauthenticeerde status weer te geven (bijv. marktplaats dashboard, gebruikersprofiel, etc.). Gebruiker is nu volledig ingelogd en kan interacteren met het platform.

Waarom ChainGuard OAuth kiezen?

Enterprise-grade authenticatie ontworpen voor Web3-applicaties

Wat maakt ChainGuard OAuth anders?

In tegenstelling tot traditionele Web3-authenticatie biedt ChainGuard een veilige, geïsoleerde omgeving die gebruikers beschermt terwijl naadloze dApp-integratie wordt mogelijk gemaakt

Verplichte 2FA vóór portemonnee-operaties

In tegenstelling tot MetaMask, WalletConnect of Web3Auth: Platforms kunnen NOOIT portemonnee-betalingen direct aanroepen. Alle operaties vereisen verplichte 2FA - gebruikers moeten eerst een QR-code ondertekenen met hun ChainGuard mobiele app voordat een portemonnee-operatie zelfs wordt gestart. Kluisoperaties vereisen 3FA (2FA + bewijs van bewaker). Deze cruciale beveiligingsstap is alleen mogelijk door ChainGuard's slimme afgeschermde omgeving.

Transactiebewijs & uitvoering

In tegenstelling tot traditionele OAuth (Auth0, Okta): ChainGuard authenticeert niet alleen gebruikers - we voeren transacties uit en bieden verifieerbaar bewijs van uitvoering. Uw platform ontvangt transactie-hashes, bloknummers en cryptografisch bewijs om uw database of frontend met vertrouwen bij te werken.

Geen portemonnee-verbinding vereist

In tegenstelling tot Magic Link of Web3Auth: Gebruikers authenticeren met e-mail/wachtwoord + mobiele 2FA - geen browserextensie of portemonnee-app vereist. Dit vermindert wrijving aanzienlijk en maakt Web3 toegankelijk voor niet-crypto-native gebruikers terwijl enterprise-grade beveiliging wordt behouden.

Actie-autorisatie, niet alleen auth

In tegenstelling tot standaard OAuth-providers: ChainGuard OAuth maakt actieverzoeken mogelijk op basis van rechten. Uw platform kan betalingen, overdrachten of andere blockchain-acties aanvragen. Gebruikers ondertekenen in ChainGuard's vertrouwde omgeving en u ontvangt bewijs van uitvoering - allemaal zonder portemonnee-verbindingen te behandelen.

Multi-chain native

In tegenstelling tot single-chain oplossingen: ChainGuard OAuth werkt naadloos op Base, Arbitrum, Optimism, Polygon en Ethereum mainnet. Eén integratie, alle netwerken. Gebruikers kunnen interacteren met multi-chain dApps zonder aparte portemonnee-verbindingen per netwerk te beheren.

Op rechten gebaseerde datapakketten

In tegenstelling tot alles-of-niets toegang: Gebruikers verlenen expliciet rechten voor specifieke datapakketten (profiel, e-mail, activiteit, portemonnee-adressen). Op basis van deze rechten kan uw platform specifieke acties aanvragen. Gebruikers behouden volledige controle over welke data en acties worden gedeeld.

Het ChainGuard-voordeel

ChainGuard OAuth combineert de beveiliging van geïsoleerde portemonnee-operaties met het gemak van traditionele OAuth. In tegenstelling tot oplossingen die portemonnee-verbindingen vereisen (risico op phishing en onbevoegde toegang) of traditionele OAuth (gebrek aan blockchain-transactiecapaciteiten), biedt ChainGuard een complete oplossing: veilige authenticatie, actie-autorisatie en verifieerbare transactie-uitvoering - allemaal binnen een vertrouwde, geïsoleerde omgeving.

🔒 Kritieke beveiligingsinnovatie: Platforms kunnen NOOIT portemonnee-betalingen direct aanroepen. Elke operatie vereist verplichte 2FA (QR-code-ondertekening met ChainGuard-app) voordat portemonnee-operaties zelfs worden gestart. Kluisoperaties vereisen 3FA (2FA + bewijs van bewaker). Deze gelaagde bescherming is alleen mogelijk door ChainGuard's callback-systeem - gebruikers ondertekenen altijd in ChainGuard's module frontend, nooit in de frontend van uw client.

🏆 Markt eerst: ChainGuard is de eerste die dit complete pakket op de markt brengt. Terwijl concurrenten individuele functies aanbieden (Web3Auth heeft 2FA, D3fenders heeft kluisbescherming, Auth0 heeft OAuth), combineert geen andere oplossing OAuth 2.0 + verplichte 2FA vóór portemonnee-operaties + callback-systeem + transactie-uitvoering + 3FA kluisoperaties + multi-chain ondersteuning in één geïntegreerd platform. Dit is de eerste productieklare Web3 OAuth-oplossing die directe portemonnee-verbindingen elimineert terwijl enterprise-grade beveiliging wordt behouden.

Snelle integratiehandleiding

Begin in minuten met ons eenvoudige integratieproces

Step 1

Registreer uw applicatie

Maak een ChainGuard-account en registreer uw dApp in het ontwikkelaarsdashboard. U ontvangt:

Client-ID (publieke identifier)
Client Secret (veilig bewaren, alleen backend)
Redirect URI-configuratie
Scope-rechten instelling

Step 2

Voeg autorisatieknop toe

Voeg "Inloggen met ChainGuard"-knop toe aan uw dApp. Leid gebruikers door naar:

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

Behandel callback

Maak een callback-eindpunt dat de autorisatiecode ontvangt:

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

Toegang tot gebruikersdata

Gebruik het toegangstoken om gebruikersinformatie op te halen:

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

Vraag acties aan (optioneel)

Op basis van verleende rechten kan uw platform acties aanvragen die worden uitgevoerd met de portemonnee of kluis van de gebruiker:

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

Kritieke beveiliging: De gebruiker MOET eerst een QR-code ondertekenen met hun ChainGuard mobiele app (verplichte 2FA) voordat een portemonnee-operatie wordt gestart. Platforms kunnen NOOIT portemonnee-betalingen direct aanroepen. Na 2FA wordt de portemonnee-payload verzonden voor ondertekening. Kluisoperaties vereisen 3FA (2FA + bewijs van bewaker). Alle operaties vinden uitsluitend plaats binnen ChainGuard's slimme afgeschermde omgeving - nooit direct in uw dApp.

Step 6

Ontvang transactiebewijs

Nadat de gebruiker de actie heeft geautoriseerd in ChainGuard's veilige omgeving, voert ChainGuard de transactie uit en biedt bewijs:

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

Uw backend kan dit transactiebewijs gebruiken om uw database of frontend bij te werken, waardoor de actiestroom wordt voltooid.

Bekijk volledige documentatie

Beveiliging & privacy

Gebouwd met beveiliging en privacy als kernprincipes

OAuth 2.0 standaard

Industriestandaard autorisatiecode flow met PKCE-ondersteuning. Beproefde beveiligingsprotocollen.

CSRF-bescherming

Statusparameter-validatie voorkomt cross-site request forgery-aanvallen. Alle redirects worden gevalideerd.

Veilige tokenopslag

Toegangstokens zijn kortlevend. Vernieuwingstokens worden veilig opgeslagen server-side. Nooit blootgesteld aan frontend.

Privacy-first

Gebruikers bepalen welke data wordt gedeeld. Op rechten gebaseerde toegang met expliciete toestemming. Geen datamining.

Versleutelde data

Alle gebruikersdata versleuteld in rust en onderweg. AES-256-GCM versleuteling voor gevoelige informatie.

Audit logging

Volledig audittrail van alle authenticatiegebeurtenissen. Beveiligingsmonitoring en bedreigingsdetectie.

Gebruikssituaties

Perfect voor elke Web3-applicatie die veilige authenticatie nodig heeft

Klaar om ChainGuard OAuth te integreren?

Begin met het bouwen van veilige Web3-authenticatie voor uw dApp. Begin in minuten met onze uitgebreide documentatie en ontwikkelaarstools.

Aan de slag

Bekijk documentatie

ChainGuard OAuth

Gebruikersgecontroleerde Web3-authenticatie

Featured Collections

Hoe ChainGuard OAuth werkt

Gebruiker heeft toegang tot dApp

Scan loginverzoek

Autoriseer dApp-rechten

Backend valideert verbinding

Loginstatus verzonden naar frontend

Waarom ChainGuard OAuth kiezen?

Multi-factor beveiliging

Op rechten gebaseerd datapakket

Geünificeerde identiteit

Eenvoudige integratie

Verplichte 2FA vóór portemonnee-operaties

Transactiebewijs & uitvoering

Multi-chain ondersteuning

Wat maakt ChainGuard OAuth anders?

Verplichte 2FA vóór portemonnee-operaties

Transactiebewijs & uitvoering

Geen portemonnee-verbinding vereist

Actie-autorisatie, niet alleen auth

Multi-chain native

Op rechten gebaseerde datapakketten

Het ChainGuard-voordeel

Snelle integratiehandleiding

Registreer uw applicatie

Voeg autorisatieknop toe

Behandel callback

Toegang tot gebruikersdata

Vraag acties aan (optioneel)

Ontvang transactiebewijs

Beveiliging & privacy

OAuth 2.0 standaard

CSRF-bescherming

Veilige tokenopslag

Privacy-first

Versleutelde data

Audit logging

Gebruikssituaties

DeFi-platforms

NFT-marktplaatsen

Web3-games

DAO-platforms

Handelsplatforms

Enterprise dApps

Klaar om ChainGuard OAuth te integreren?

ChainGuard OAuth - User-Controlled Web3 Authentication

How ChainGuard OAuth Works

Integration Guide

Security Features

Use Cases