Sparkle Protocol – Changelog
Scope
This changelog tracks substantive changes to the Sparkle Protocol specifications, documentation, and reference implementation.
Version 0.3.8 – December 2025
Mainnet Validation Complete
Major Milestone: Mainnet Transaction Confirmed
Real Bitcoin spent via Taproot script-path on mainnet. Verify on-chain
Real Bitcoin spent via Taproot script-path on mainnet. Verify on-chain
- Mainnet validation: Complete atomic swap cycle confirmed on Bitcoin mainnet
- Transaction proof:
- Contract funding:
7739c731...55b4(15,000 sats locked) - Script-path spend:
1dcbeb24...e994(hashlock claim with preimage)
- Contract funding:
- BIP-371 PSBT fix: TAP_LEAF_SCRIPT corrected to type 0x15 (was 0x16)
- Control block parity: Now derived from output key (Q), not hardcoded
- Dust threshold: Unified to 330 sats everywhere (P2TR standard)
- Test suite: 6 comprehensive BIP compliance tests passing
- Mainnet CLI:
sparkle-mainnet.jsfor production contract creation - Documentation: Complete validation report with verification commands
Verified On-Chain
| Transaction | TXID | Status |
|---|---|---|
| Contract Funding | 7739c731...55b4 | Confirmed |
| Script-Path Spend | 1dcbeb24...e994 | Confirmed (3+ blocks) |
Version 0.3.0 – December 2025
Core Protocol Implementation Complete
Major Milestone: Working Sparkle Swap Implementation
- TypeScript reference implementation complete – Full Taproot atomic swap library
- Taproot script generation:
- Hashlock script:
OP_SHA256 <payment_hash> OP_EQUALVERIFY <buyer_pubkey> OP_CHECKSIG - Timelock script:
<locktime> OP_CHECKLOCKTIMEVERIFY OP_DROP <seller_pubkey> OP_CHECKSIG
- Hashlock script:
- Transaction builders:
- Claim transaction (buyer claims with preimage + signature)
- Refund transaction (seller reclaims after timeout)
- Comprehensive test suite: 10 cryptographic verification tests passing
- Transaction sizes verified: Claim 142 vbytes, Refund 138 vbytes
- Libraries used: @scure/btc-signer, @noble/hashes
- Updated documentation: Status boxes, roadmap, and spec pages
Secure Frontend (sparkle-swap.js)
Security Fix: Removed private key input. All signing via browser extensions.
- NIP-07 wallet integration – Nostr identity via Alby, nos2x (no nsec input)
- Bitcoin wallet support – PSBT signing via Unisat, Xverse
- Unified wallet manager – Single interface for both protocols
- New swap.html – Secure NIP-07 frontend with Taproot atomic swaps
- Browser modules:
nostr-nip07.ts– NIP-07 provider abstractionbitcoin-wallet.ts– Bitcoin wallet detection and signingwallet-manager.ts– Unified state management
- CLI tool –
sparkle-clifor testnet swap execution
Version 0.2.0 – November 2024
Major restructure for clarity and honesty
- Added "Why This Exists (Even If It Never Ships)" section to homepage
- Added three reading paths (Overview, Design, Implementation) for different audiences
- Added "Critical Self-Assessment" documenting weaknesses and limitations
- Created practical guides:
- "How Recursive Inscriptions Actually Work" – working code and real examples
- "Real Alternatives to Sparkle Protocol" – honest comparison of production options
- Added glossary of key terms with neutral definitions
- Added DARKITA case study as illustrative example (not marketing)
- Updated all pages with consistent navigation and status warnings
- Updated to v1.0.0 production status (mainnet validated) throughout documentation
- Removed misleading claims about production readiness
Version 0.1.0 – January 2025 (Original)
Initial publication
- Initial publication of the Sparkle Protocol whitepaper
- Added technical implementation analysis and practical implementation guide
- Added formal security analysis (theoretical; not peer-reviewed)
- Documented conceptual SDK API and coordinator behavior
- Published SIP-3 draft for Lightning-atomic NFT trades
- Created protocol comparison with BRC-20, GBRC-721, Runes, Stamps
- Published vision and roadmap document
Key Changes Summary
Documentation Philosophy Change
Version 0.2.0 represents a fundamental shift from promotional to educational documentation:
- Before: Presented as upcoming protocol with implied production readiness
- After: Clearly documented protocol specification with mainnet validation
Content Additions
| New Content | Purpose |
|---|---|
| Recursive Inscriptions Guide | Practical implementation with working code |
| Alternatives Page | Honest comparison of production options |
| Reading Paths | Structured navigation for different audiences |
| Critical Self-Assessment | Transparent documentation of limitations |
| Glossary | Clear definitions of technical terms |
Clarity Improvements
- Added comprehensive testing documentation
- Documented mainnet validation status
- Distinguished between working techniques (recursive inscriptions) and theoretical proposals (Lightning integration)
- Added "You are here" navigation context on spec pages
Future Considerations
Potential updates that may be added in future versions:
- Interactive cost calculator for inscription planning
- Code repository with working recursive inscription examples
- Video tutorials for practical techniques
- Community contributions section (if community develops)
- Migration guides from theoretical to practical implementations
Note: Sparkle Protocol v1.0.0 has been validated on mainnet. Future development depends on community adoption and contributor interest. The protocol specification is complete and the reference implementation is open source under MIT license.
Version Numbering
This documentation uses semantic versioning:
- Major version (X.0.0): Fundamental changes to protocol design or documentation structure
- Minor version (0.X.0): Significant content additions or reorganization
- Patch version (0.0.X): Minor corrections, typos, clarifications
Current version: 1.0.0 (Mainnet Validated)