Diagnose and troubleshoot bitcoin-auth token generation and verification issues. This skill should be used when users encounter authentication failures, signature verification errors, or integration problems with the bitcoin-auth library.
npx skills add https://github.com/Microck/ordinary-claude-skills --skill bitcoin-auth-diagnostics
This skill enables comprehensive diagnosis of bitcoin-auth authentication issues across client and server implementations. Use this skill when encountering token generation failures, signature verification errors, or integration problems with the bitcoin-auth library.
Use this skill when:
All bitcoin-auth tokens follow this pipe-delimited format:
pubkey|scheme|timestamp|requestPath|signature
Components:
pubkey: Hex-encoded public key (66 characters)scheme: Either bsm (legacy) or brc77 (recommended)timestamp: ISO8601 format (e.g., 2025-01-15T14:30:00.000Z)requestPath: Full path including query parameters (e.g., /api/endpoint?param=value)signature: Base64-encoded signatureExample valid token:
02a1b2c3d4e5f6...|brc77|2025-01-15T14:30:00.123Z|/api/status|dGVzdHNpZ25hdHVyZQ==
First, validate the token structure before checking cryptographic validity:
import { parseAuthToken } from 'bitcoin-auth';
const token = "..."; // The failing token
const parsed = parseAuthToken(token);
if (!parsed) {
console.error("FAILED: Token structure is invalid");
// Check: Does token have exactly 5 pipe-delimited parts?
const parts = token.split('|');
console.log(`Token has ${parts.length} parts (expected 5)`);
console.log("Parts:", parts);
// Common issues:
// - Missing parts (incomplete token)
// - Extra pipes in requestPath or other fields
// - Invalid scheme (not 'bsm' or 'brc77')
} else {
console.log("✅ Token structure is valid");
console.log("Parsed token:", parsed);
}
Validate each component individually:
const { pubkey, scheme, timestamp, requestPath, signature } = parsed;
// Validate public key
console.log("Public key length:", pubkey.length); // Should be 66 chars
console.log("Public key starts with 02/03:", pubkey.startsWith('02') || pubkey.startsWith('03'));
// Validate scheme
console.log("Scheme:", scheme); // Must be 'bsm' or 'brc77'
// Validate timestamp
const tokenTime = new Date(timestamp);
console.log("Token timestamp:", tokenTime.toISOString());
console.log("Current time:", new Date().toISOString());
console.log("Age (minutes):", (Date.now() - tokenTime.getTime()) / 60000);
// Default timePad is 5 minutes - token older than 5 minutes will fail
// Validate request path
console.log("Request path:", requestPath);
// Must match EXACTLY including query parameters and their order
// Validate signature
console.log("Signature (base64):", signature);
console.log("Signature length:", signature.length);
If structure is valid, diagnose verification failures:
import { verifyAuthToken } from 'bitcoin-auth';
import type { AuthPayload } from 'bitcoin-auth';
const authPayload: AuthPayload = {
requestPath: "/api/endpoint?param=value", // Must match token exactly
timestamp: new Date().toISOString(), // Server's current time
body: requestBody // Optional, must match if token was signed with body
};
const isValid = verifyAuthToken(
token,
authPayload,
5, // timePad in minutes (default 5)
'utf8' // bodyEncoding: 'utf8', 'hex', or 'base64'
);
if (!isValid) {
console.error("FAILED: Signature verification failed");
// Diagnose specific failures:
// 1. Request path mismatch
if (parsed.requestPath !== authPayload.requestPath) {
console.error("❌ Request path mismatch:");
console.error(" Token path:", parsed.requestPath);
console.error(" Verify path:", authPayload.requestPath);
// Common issue: Query parameter order differs
}
// 2. Timestamp issues
const tokenTimestamp = new Date(parsed.timestamp);
const targetTime = new Date(authPayload.timestamp);
targetTime.setMinutes(targetTime.getMinutes() + 5); // Add timePad
if (tokenTimestamp > targetTime) {
console.error("❌ Token timestamp too far in future");
console.error(" Token time:", tokenTimestamp.toISOString());
console.error(" Target time:", targetTime.toISOString());
}
// 3. Body hash mismatch
if (authPayload.body) {
console.log("Verifying with body present");
console.log(" Body encoding:", 'utf8'); // Check encoding matches
console.log(" Body length:", authPayload.body.length);
// Try different encodings if utf8 fails
}
// 4. Scheme-specific issues
if (parsed.scheme === 'bsm') {
console.log("Using legacy BSM signature scheme");
// BSM uses different signature format than BRC77
} else {
console.log("Using BRC77 signature scheme (recommended)");
}
}
Check for common integration mistakes:
Server-side (verification):
// ❌ WRONG: Using token's timestamp (defeats the purpose)
const authPayload = {
requestPath,
timestamp: parsedToken.timestamp, // DON'T DO THIS
body
};
// ✅ CORRECT: Use server's current time
const serverTime = new Date().toISOString();
const authPayload = {
requestPath,
timestamp: serverTime,
body
};
Client-side (generation):
// ✅ Token generation
import { getAuthToken } from 'bitcoin-auth';
const token = getAuthToken({
privateKeyWif,
requestPath: '/api/endpoint?param=value', // Include full path with query
body: JSON.stringify(requestBody), // If POST/PUT with body
scheme: 'brc77', // Default, recommended
bodyEncoding: 'utf8' // Default
});
// Include in request headers
fetch(url + requestPath, {
method: 'POST',
headers: {
'X-Auth-Token': token,
'Content-Type': 'application/json'
},
body: JSON.stringify(requestBody)
});
Cause: Token doesn't have exactly 5 pipe-delimited parts
Solutions:
Cause: Signature doesn't match the payload
Solutions:
Cause: Token timestamp too far from server time
Solutions:
Cause: Token requestPath doesn't match verification path
Solutions:
Cause: Body used for signing doesn't match verification body
Solutions:
When working with Sigma Auth (auth.sigmaidentity.com), common patterns:
Token verification endpoint:
// POST /api/auth/token-for-endpoint
// Body: { authToken: "...", requestBody: "..." }
// Server parses and verifies:
const parsed = parseAuthToken(authToken);
const authPayload = {
requestPath: "/api/auth/token-for-endpoint",
timestamp: new Date().toISOString(),
body: requestBody
};
const isValid = verifyAuthToken(authToken, authPayload);
Wallet connect flow:
// Uses BSM scheme for compatibility
const token = getAuthToken({
privateKeyWif,
requestPath: "/wallet/connect",
scheme: 'bsm'
});
For detailed API documentation and implementation examples, see:
references/bitcoin-auth-api.md - Complete API referencereferences/common-issues.md - Detailed troubleshooting guide@bsv/sdk peer dependencybun add bitcoin-authNever log private keys or WIF strings - Only log public keys, tokens, and diagnostic information.
When diagnosing authentication issues:
You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
Implement authentication and authorization with Better Auth - a framework-agnostic TypeScript authentication framework. Features include email/password authentication with verification, OAuth providers (Google, GitHub, Discord, etc.), two-factor authentication (TOTP, SMS), passkeys/WebAuthn support, session management, role-based access control (RBAC), rate limiting, and database adapters. Use when adding authentication to applications, implementing OAuth flows, setting up 2FA/MFA, managing user sessions, configuring authorization rules, or building secure authentication systems for web applications.
Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.
You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.
Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs.
Perform language and framework specific security best-practice reviews and suggest improvements. Use when the user explicitly requests security best practices guidance, a security review or report, or secure-by-default coding help. Supports Python, JavaScript/TypeScript, and Go. Do NOT use for general code review, debugging, threat modeling (use security-threat-model), or non-security tasks.
Configures API gateways for routing, authentication, rate limiting, and request transformation in microservice architectures. Use when setting up Kong, Nginx, AWS API Gateway, or Traefik for centralized API management.
Take microck/bitcoin-auth-diagnostics from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.