What is the standard format for a bitcoin-auth token?

A bitcoin-auth token is a pipe-delimited string following the format: pubkey|scheme|timestamp|requestPath|signature.

How does this skill help with Sigma Auth?

It provides specific diagnostic workflows to validate tokens used by Sigma Auth endpoints, helping identify if the error lies in the request body encoding, the path formatting, or the cryptographic signature itself.

Why does my bitcoin-auth signature verification fail?

Failures are typically caused by request path mismatches (including query parameter order), body hash discrepancies, or the token's timestamp exceeding the allowed timePad (usually 5 minutes).

What is the difference between BSM and BRC77 schemes?

BSM (Bitcoin Signed Message) is a legacy signature format used for basic compatibility, whereas BRC77 is the modern, recommended standard for peer-to-peer authentication in the BSV ecosystem.

Bitcoin Auth Diagnostics

Name: Bitcoin Auth Diagnostics
Author: Microck

byMicrock

•

Security & Testing

Diagnoses and troubleshoots authentication failures, signature verification errors, and token generation issues within the bitcoin-auth ecosystem.

About

This skill provides a specialized diagnostic framework for developers working with the bitcoin-auth library, which is a standard for authenticated communication in Bitcoin SV applications and Sigma Auth integrations. It enables Claude to perform systematic validation of five-part pipe-delimited tokens, checking for component validity, signature correctness across BSM and BRC77 schemes, and common integration pitfalls like timestamp skew or request path mismatches. Whether you are debugging a client-side wallet connection or a server-side API guard, this skill streamlines the identification of cryptographic and structural authentication errors.

Key Features

Troubleshoots body hash discrepancies and encoding issues
Detects request path and query parameter mismatches
Diagnoses signature verification failures for BSM and BRC77 schemes
81 GitHub stars
Validates five-part pipe-delimited token structures
Identifies time skew and ISO8601 timestamp format errors

Use Cases

Resolving authentication failures caused by server-client clock drift
Debugging 'invalid signature' errors in Sigma Auth API integrations
Verifying client-side token generation logic against server requirements

About

Key Features

Troubleshoots body hash discrepancies and encoding issues
Detects request path and query parameter mismatches
Diagnoses signature verification failures for BSM and BRC77 schemes
81 GitHub stars
Validates five-part pipe-delimited token structures
Identifies time skew and ISO8601 timestamp format errors

Use Cases

Resolving authentication failures caused by server-client clock drift
Debugging 'invalid signature' errors in Sigma Auth API integrations
Verifying client-side token generation logic against server requirements