SIP-2: BTNFT - Bitcoin Token Non-Fungible Extension for Spark #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ation and security analysis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This SIP proposes BTNFT (Bitcoin Token Non-Fungible), an extension to the existing BTKN protocol that enables native NFT functionality on the Spark Bitcoin Layer 2 network. BTNFT extends the proven TTXO (Token Transaction Output) model and existing BTKN infrastructure to support NFT collections, individual token minting, and instant transfers while maintaining full compatibility with Spark's statechain and FROST signing mechanisms. By building on Spark's battle-tested infrastructure rather than creating a separate protocol, BTNFT provides Lightning-compatible NFTs with sub-second transfers, near-zero fees, and Bitcoin's security guarantees while preserving self-custody principles.