hodlxxi-bitcoin-identity

What This Skill Does

The hodlxxi-bitcoin-identity skill serves as a robust gateway for integrating HODLXXI as a Bitcoin-native identity provider within your OpenClaw agent ecosystem. It acts as a bridge between traditional OAuth2/OIDC standards and the modern Lightning Network LNURL-Auth protocol. By deploying this skill, your agent gains the ability to manage secure authentication flows, handle client registrations, perform JWT-based identity verification via JWKS, and facilitate seamless Lightning-wallet-based user logins. It provides a standardized framework to authenticate users without relying solely on centralized legacy identity providers, instead leveraging Bitcoin's native cryptographic capabilities.

Installation

To integrate this skill into your agent, execute the following command in your terminal:

clawhub install openclaw/skills/skills/hodlxxi/hodlxxi-bitcoin-identity

Ensure that you have the required helper dependencies for local validation by running: pip install ecdsa pyjwt requests

After installation, configure your environment by setting the BASE_URL to your specific HODLXXI deployment instance. This enables the agent to interact with discovery endpoints and secure token services.

Use Cases

• Decentralized Authentication: Enable login for users using their existing Lightning Network wallets, removing the friction of email-based registration.
• Agent Identity Management: Use the skill to issue and verify identity tokens for other services, ensuring that your agent interacts only with authenticated entities.
• Privacy-Preserving Access: Implement OIDC flows that allow users to authenticate against your agent services while retaining control over their identity data via Bitcoin-native cryptographic proofs.
• Automated Security Auditing: Use the built-in health and metrics endpoints to continuously monitor the security posture of your authentication gateway.

Example Prompts

1. "Initialize the HODLXXI auth flow and provide me with the LNURL to share with the user for Lightning login."
2. "Verify the JWT received from the latest login attempt using the HODLXXI JWKS endpoint."
3. "Check the current status of the authentication server to ensure the identity provider is reachable and healthy."

Tips & Limitations

• Security: Always use PKCE (Proof Key for Code Exchange) when performing OAuth2 authorization code flows to prevent interception attacks.
• Performance: For high-traffic agents, cache the JWKS response locally to reduce latency in JWT verification; ensure your implementation handles key rotation gracefully.
• Reliability: The skill relies on the availability of the HODLXXI deployment. Ensure your BASE_URL points to a highly available node to prevent downtime in authentication flows.