signing

Automate cryptographic signing and verification across SIP-018, Stacks, Bitcoin, Schnorr, and Nostr.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Jay0xx/forge0btc-news-agent --skill signing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signing
Source: https://github.com/Jay0xx/forge0btc-news-agent/tree/main/aibtcdev-skills/signing
Command: npx skills add https://github.com/Jay0xx/forge0btc-news-agent --skill signing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates cryptographic signing and verification across SIP-018, Stacks SIWS, Bitcoin (BIP-137/BIP-322), Schnorr, and Nostr, enabling verifiable signatures from a single interface.

Core Features & Use Cases

  • SIP-018 structured data signing and verification for on-chain and off-chain scenarios.
  • Stacks SIWS plain-text signing for wallet authentication and ownership proof.
  • Bitcoin messages signing (BIP-137/BIP-322) for legacy and native addresses, plus Taproot.
  • Schnorr (BIP-340) signing for Taproot multisig and script-path spending.
  • Nostr event signing via NIP-06 key derivation.

Quick Start

Sign a sample structured Clarity payload using sip018-sign to produce a verifiable SIP-018 signature.

Frequently Asked Questions about signing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sign and verify crypto messages across multiple blockchains like Stacks and Bitcoin?

Automated cryptographic signing and verification across SIP-018, Stacks SIWS, Bitcoin BIP-137/BIP-322, Schnorr, and Nostr enables verifiable multi-chain signatures from a single interface for wallet identity proofs and on-chain workflows.

What is SIP-018 structured data signing and when do I need it for Stacks?

SIP-018 structured data signing standardizes cryptographic verification for Stacks on-chain and off-chain scenarios. You need it to produce verifiable proofs for Clarity payloads, wallet authentication, and multi-chain ownership workflows.

How do I sign a Bitcoin message for Taproot and legacy addresses?

You can sign Bitcoin messages for legacy, native, and Taproot addresses using BIP-137 and BIP-322 standards. This supports Schnorr BIP-340 signing required for Taproot multisig and script-path spending scenarios.

Can I sign Nostr events using BIP-340 Schnorr signatures?

Yes, Nostr event signing is supported via NIP-06 key derivation alongside Schnorr BIP-340 digest signing. This allows you to generate verifiable signatures for Nostr events and Taproot script-path spending from one interface.

Does this signing tool support Stacks SIWS plain-text wallet authentication?

Yes, Stacks SIWS plain-text signing is supported for wallet authentication and ownership proof. It operates alongside SIP-018, Bitcoin, Schnorr, and Nostr signing through command-driven operations with domain binding.

What are the limitations of multi-chain signing across Bitcoin and Nostr protocols?

Multi-chain signing across Bitcoin, Stacks, and Nostr requires domain binding and wallet unlocking for command-driven operations. Limitations include protocol-specific constraints like BIP-340 Schnorr for Taproot and NIP-06 key derivation for Nostr events.