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

ユーザー制御のWeb3認証

ChainGuard OAuthは、Web3アプリケーション向けにシームレスで安全な認証とアクション承認を可能にします。ユーザーはChainGuardアイデンティティ（メール/パスワード + モバイル2FA）で認証し、dAppまたはエンタープライズプラットフォームに権限ベースのデータパッケージアクセスを許可します。

付与された権限に基づいて、プラットフォームはユーザーのウォレットまたはボルトで実行されるアクションをリクエストできます。重要なセキュリティ：プラットフォームはウォレット支払いを直接呼び出すことはできません。ウォレット支払いを含むすべての操作には、必須の2FAが必要です - ユーザーはウォレット操作が呼び出される前に、ChainGuardモバイルアプリでQRコードに署名する必要があります。その後、ウォレットペイロードが署名のために送信されます。ボルト操作には3FA（2FA + ガス支払いのガーディアン証明）が必要です。この多層セキュリティは、ChainGuardのスマートシールド環境によってのみ可能です。

エンタープライズグレードのセキュリティを備えたOAuth 2.0認証コードフローに基づいて構築されています。ユーザーはすべてのdAppで統一されたアイデンティティを取得し、Base、Arbitrum、Optimism、Polygon、Ethereumメインネットで動作するシンプルな統合を取得できます。

統合ガイドを表示詳細を見る

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

標準プロトコル

2FA/3FA

多要素セキュリティ

5+ ブロックチェーンネットワーク

プライバシー

権限ベース

ChainGuard OAuthの仕組み

ウォレット接続の複雑さを排除するシンプルで安全な認証フロー

ユーザーがdAppにアクセス

ユーザーがdAppで「ChainGuardでサインイン」をクリックします。アプリはクライアントIDと要求されたスコープでChainGuard認証エンドポイントにリダイレクトします。

ログインリクエストをスキャン

ユーザーがChainGuardモバイルアプリでQRコードをスキャンしてログインを開始します。これは必須2FAの最初のステップです - ユーザーは操作の前にモバイルアプリで認証する必要があります。

dAppの権限を承認

ユーザーが権限ベースのデータアクセスを確認して許可します。ユーザーはdAppがアクセスするデータ（プロファイル、メール、ウォレットアドレスなど）を正確に確認し、特定の権限を承認または拒否できます。

バックエンドが接続を検証

バックエンドが認証コードを受信し、接続リクエストを検証します。バックエンドはクライアントシークレットを使用してコードをアクセストークンとリフレッシュトークンと交換します。すべてのトークン操作はセキュリティのためにサーバー側で行われます。

ログインステータスがフロントエンドに送信

検証が成功した後、バックエンドはログインステータスをフロントエンドに送信します。dAppはユーザーインターフェースを更新して認証済み状態を表示します（例：マーケットプレイスダッシュボード、ユーザープロファイルなど）。ユーザーは完全にログインし、プラットフォームと対話できます。

ChainGuard OAuthを選ぶ理由

Web3アプリケーション向けに設計されたエンタープライズグレードの認証

ChainGuard OAuthの違いは何ですか？

従来のWeb3認証とは異なり、ChainGuardはユーザーを保護しながらシームレスなdApp統合を可能にする安全で分離された環境を提供します

ウォレット操作前の必須2FA

MetaMask、WalletConnect、またはWeb3Authとは異なり：プラットフォームはウォレット支払いを直接呼び出すことはできません。すべての操作には必須の2FAが必要です - ユーザーはウォレット操作が開始される前に、ChainGuardモバイルアプリでQRコードに署名する必要があります。ボルト操作には3FA（2FA + ガーディアン証明）が必要です。この重要なセキュリティステップは、ChainGuardのスマートシールド環境によってのみ可能です。

トランザクション証明と実行

従来のOAuth（Auth0、Okta）とは異なり：ChainGuardは単にユーザーを認証するだけでなく、トランザクションを実行し、実行の検証可能な証明を提供します。プラットフォームは、データベースまたはフロントエンドを自信を持って更新するために、トランザクションハッシュ、ブロック番号、暗号化証明を受け取ります。

ウォレット接続は不要

Magic LinkまたはWeb3Authとは異なり：ユーザーはメール/パスワード + モバイル2FAで認証します - ブラウザ拡張機能やウォレットアプリは不要です。これにより摩擦が大幅に減少し、エンタープライズグレードのセキュリティを維持しながら、非暗号ネイティブユーザーがWeb3にアクセスできるようになります。

アクション承認、認証だけでなく

標準のOAuthプロバイダーとは異なり：ChainGuard OAuthは権限に基づくアクションリクエストを可能にします。プラットフォームは支払い、転送、またはその他のブロックチェーンアクションをリクエストできます。ユーザーはChainGuardの信頼できる環境でサインインし、実行証明を受け取ります - すべてウォレット接続を処理することなく。

マルチチェーンネイティブ

シングルチェーンソリューションとは異なり：ChainGuard OAuthはBase、Arbitrum、Optimism、Polygon、Ethereumメインネットでシームレスに動作します。1つの統合で、すべてのネットワークに対応。ユーザーはネットワークごとに個別のウォレット接続を管理することなく、マルチチェーンdAppと対話できます。

権限ベースのデータパッケージ

すべてまたは何もないアクセスとは異なり：ユーザーは特定のデータパッケージ（プロファイル、メール、アクティビティ、ウォレットアドレス）の権限を明示的に付与します。これらの権限に基づいて、プラットフォームは特定のアクションをリクエストできます。ユーザーは共有されるデータとアクションを完全に制御します。

ChainGuardの利点

ChainGuard OAuthは、分離されたウォレット操作のセキュリティと従来のOAuthの利便性を組み合わせます。ウォレット接続が必要なソリューション（フィッシングと不正アクセスのリスク）または従来のOAuth（ブロックチェーントランザクション機能の欠如）とは異なり、ChainGuardは完全なソリューションを提供します：安全な認証、アクション承認、検証可能なトランザクション実行 - すべて信頼できる分離環境内で。

🔒 重要なセキュリティイノベーション：プラットフォームはウォレット支払いを直接呼び出すことはできません。すべての操作には必須の2FA（ChainGuardアプリでQRコード署名）が必要で、ウォレット操作が開始される前に行われます。ボルト操作には3FA（2FA + ガーディアン証明）が必要です。この多層保護は、ChainGuardのコールバックシステムによってのみ可能です - ユーザーは常にChainGuardのモジュールフロントエンドで署名し、クライアントのフロントエンドでは決して署名しません。

🏆 市場初：ChainGuardはこの完全なパッケージを市場に最初に提供します。競合他社が個別の機能を提供する一方で（Web3Authは2FA、D3fendersはボルト保護、Auth0はOAuth）、他のソリューションは1つの統合プラットフォームでOAuth 2.0 + ウォレット操作前の必須2FA + コールバックシステム + トランザクション実行 + 3FAボルト操作 + マルチチェーンサポートを組み合わせていません。これは、エンタープライズグレードのセキュリティを維持しながら直接ウォレット接続を排除する、最初の本番準備が整ったWeb3 OAuthソリューションです。

クイック統合ガイド

シンプルな統合プロセスで数分で開始

Step 1

アプリケーションを登録

ChainGuardアカウントを作成し、開発者ダッシュボードでdAppを登録します。以下を受け取ります：

クライアントID（公開識別子）
クライアントシークレット（安全に保管、バックエンドのみ）
リダイレクトURI設定
スコープ権限設定

Step 2

認証ボタンを追加

dAppに「ChainGuardでサインイン」ボタンを追加します。ユーザーを以下にリダイレクトします：

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

コールバックを処理

認証コードを受信するコールバックエンドポイントを作成します：

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

ユーザーデータにアクセス

アクセストークンを使用してユーザー情報を取得します：

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

アクションをリクエスト（オプション）

付与された権限に基づいて、プラットフォームはユーザーのウォレットまたはボルトで実行されるアクションをリクエストできます：

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

重要なセキュリティ：ユーザーはウォレット操作が開始される前に、ChainGuardモバイルアプリでQRコードに署名する必要があります（必須2FA）。プラットフォームはウォレット支払いを直接呼び出すことはできません。2FA後、ウォレットペイロードが署名のために送信されます。ボルト操作には3FA（2FA + ガーディアン証明）が必要です。すべての操作は、ChainGuardのスマートシールド環境内でのみ排他的に発生します - dAppで直接発生することはありません。

Step 6

トランザクション証明を受信

ユーザーがChainGuardの安全な環境でアクションを承認した後、ChainGuardはトランザクションを実行し、証明を提供します：

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

バックエンドはこのトランザクション証明を使用してデータベースまたはフロントエンドを更新し、アクションフローを完了できます。

完全なドキュメントを表示

セキュリティとプライバシー

セキュリティとプライバシーを核心原則として構築

OAuth 2.0標準

PKCEサポート付きの業界標準認証コードフロー。実戦でテストされたセキュリティプロトコル。

CSRF保護

状態パラメータの検証により、クロスサイトリクエストフォージェリ攻撃を防止します。すべてのリダイレクトが検証されます。

安全なトークンストレージ

アクセストークンは短期間です。リフレッシュトークンはサーバー側で安全に保存されます。フロントエンドに公開されることはありません。

プライバシー優先

ユーザーが共有するデータを制御します。明示的な同意を伴う権限ベースのアクセス。データマイニングなし。

暗号化データ

すべてのユーザーデータが保存時と転送時に暗号化されます。機密情報にはAES-256-GCM暗号化を使用。

監査ログ

すべての認証イベントの完全な監査証跡。セキュリティ監視と脅威検出。

ユースケース

安全な認証が必要なWeb3アプリケーションに最適

ChainGuard OAuthを統合する準備はできましたか？

dApp向けの安全なWeb3認証の構築を開始します。包括的なドキュメントと開発者ツールで数分で開始できます。

始める

ドキュメントを表示

ChainGuard OAuth

ユーザー制御のWeb3認証

Featured Collections

ChainGuard OAuthの仕組み

ユーザーがdAppにアクセス

ログインリクエストをスキャン

dAppの権限を承認

バックエンドが接続を検証

ログインステータスがフロントエンドに送信

ChainGuard OAuthを選ぶ理由

多要素セキュリティ

権限ベースのデータパッケージ

統一されたアイデンティティ

シンプルな統合

ウォレット操作前の必須2FA

トランザクション証明と実行

マルチチェーンサポート

ChainGuard OAuthの違いは何ですか？

ウォレット操作前の必須2FA

トランザクション証明と実行

ウォレット接続は不要

アクション承認、認証だけでなく

マルチチェーンネイティブ

権限ベースのデータパッケージ

ChainGuardの利点

クイック統合ガイド

アプリケーションを登録

認証ボタンを追加

コールバックを処理

ユーザーデータにアクセス

アクションをリクエスト（オプション）

トランザクション証明を受信

セキュリティとプライバシー

OAuth 2.0標準

CSRF保護

安全なトークンストレージ

プライバシー優先

暗号化データ

監査ログ

ユースケース

DeFiプラットフォーム

NFTマーケットプレイス

Web3ゲーム

DAOプラットフォーム

取引プラットフォーム

エンタープライズdApp

ChainGuard OAuthを統合する準備はできましたか？

ChainGuard OAuth - User-Controlled Web3 Authentication

How ChainGuard OAuth Works

Integration Guide

Security Features

Use Cases