skills.rest
aibtcdev
aibtcdevOFFICIAL
Explore all skills by this author →
Website𝕏@aibtcdevGitHub

signing

Generate and verify multi-protocol cryptographic signatures via a single CLI.

9|43|Updated Feb 19, 2026
Search Tags:#cryptography#nostr#stacks#signing#bitcoin#schnorr#sip-018
One-click install
npx skills add https://github.com/aibtcdev/skills --skill signing-aibtcdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signing
Source: https://github.com/aibtcdev/skills/tree/main/signing
Command: npx skills add https://github.com/aibtcdev/skills --skill signing-aibtcdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @stacks/transactions, @stacks/encryption, @stacks/common, @noble/curves/secp256k1.js, @scure/base, @scure/btc-signer.

What problem does it solve?

Signing across multiple ecosystems (Stacks, Bitcoin, and Nostr) is complex and requires juggling different tools. This skill consolidates cryptographic signing into a single CLI, enabling quick ownership proofs and authenticated messages.

Core Features & Use Cases

  • SIP-018 structured data signing for on-chain verification and governance flows.
  • Stacks plain-text message signing (SIWS-compatible) for wallet authentication.
  • Bitcoin message signing (BIP-137 legacy/wrapped-SegWit and BIP-322 native) for cross-chain proofs.
  • Schnorr signing for Taproot multisig and script-path spending.
  • Nostr event signing using NIP-06 derivation for identity proof.
  • Use cases include onboarding, verifications, cross-chain authenticators, and multi-signature workflows.

Quick Start

Invoke bun run signing/signing.ts sip018-sign to generate 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 messages across Bitcoin, Stacks, and Nostr using a single CLI?▼

This CLI generates and verifies multi-protocol cryptographic signatures for Stacks, Bitcoin, and Nostr. It supports Stacks SIWS, Bitcoin BIP-137/BIP-322, Schnorr for Taproot, and Nostr events from a single interface.

How do I generate a SIP-018 structured data signature for on-chain verification?▼

Run the sip018-sign command to generate a verifiable SIP-018 structured data signature. This requires an unlocked wallet and domain binding to ensure compatibility with on-chain verification processes.

Can I use Schnorr signing for Bitcoin Taproot script-path spending?▼

Yes, the CLI supports Schnorr signing specifically for Taproot multisig and script-path spending. It generates the necessary cryptographic proofs for authenticating Taproot transactions.

Does cross-chain signing require an unlocked wallet for verification?▼

An unlocked wallet is required for signing operations across Stacks, Bitcoin, and Nostr. However, the verify command can validate signatures independently without needing wallet access.

What is the difference between BIP-137 and BIP-322 Bitcoin message signing?▼

BIP-137 handles legacy and wrapped-SegWit Bitcoin message signing, while BIP-322 supports native SegWit message proofs. The CLI executes both formats for cross-chain ownership proofs.

How does Nostr event signing work for identity proof?▼

Nostr event signing uses NIP-06 derivation to generate cryptographic identity proofs. The CLI signs Nostr events directly for authentication and verifiable off-chain identity workflows.

Related Skills

Explore More Software Engineering Skills→
accolveraccolver
4

nostr-crypto-guide

Implement Nostr cryptography workflows for NIP-06, NIP-44, NIP-46, NIP-49, and NIP-59 in TypeScript.

Community
Advanced
Jay0xxJay0xx

signing

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

Community
Advanced
dnzengoudnzengou

symbiosis

Execute cross-chain token swaps and bridging via the Symbiosis protocol.

Community
Advanced
phantomphantom
7

sign-message

Sign messages on Solana and EVM chains using Phantom Connect SDK.

Official
Intermediate