/**
 * Message Signing Tools
 *
 * These tools provide message signing capabilities for agent identity and authentication:
 *
 * SIP-018 (Structured Data Signing):
 * - sip018_sign: Sign structured Clarity data (SIP-018 standard)
 * - sip018_verify: Verify SIP-018 signature and recover signer
 * - sip018_hash: Compute SIP-018 message hash without signing
 *
 * Stacks Message Signing (SIWS-Compatible):
 * - stacks_sign_message: Sign plain text messages with Stacks prefix
 * - stacks_verify_message: Verify message signature and recover signer
 *
 * Bitcoin Message Signing (BIP-137 / BIP-322):
 * - btc_sign_message: Sign messages with Bitcoin private key (BIP-137 for legacy, BIP-322 for bc1q/bc1p)
 * - btc_verify_message: Verify Bitcoin message signatures (auto-detects BIP-137 vs BIP-322)
 *
 * Nostr Event Signing (NIP-01):
 * - nostr_sign_event: Sign a Nostr event with BIP-340 Schnorr using the NIP-06 derived key (default) or a custom keySource
 *
 * SIP-018 signatures can be verified both off-chain and on-chain by smart contracts.
 * Stacks message signatures are SIWS-compatible for web authentication flows.
 * Bitcoin signatures use BIP-137 format compatible with most Bitcoin wallets.
 * Nostr events are signed with BIP-340 Schnorr and can be published to Nostr relays.
 */
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
export declare function registerSigningTools(server: McpServer): void;
//# sourceMappingURL=signing.tools.d.ts.map