cmd on Nostr: Fun fact. Nostr and Taproot both use Schnorr for producing signatures. This means ...
Fun fact. Nostr and Taproot both use Schnorr for producing signatures. This means that technically you can sign taproot transactions *and* nostr events with the same pair of keys
The difficulty however, is that taproot transactions use key tweaking, meaning a taproot UTXO on the blockchain is showing you a tweaked pubkey, not the original pubkey.
Even a script-less taproot transaction uses a tweaked pubkey, making cross-verification difficult. Also, Bitcoin Core is not very friendly towards exporting child keys and revealing tweaks.
This script takes the original pubkey and recreates the tweak in order to verify that a taproot pubkey and nostr pubkey are in fact the same key.
The next step is to build a signing extension, so a nostr user can prove they own a particular UTXO (and whatever may be inside of it 😎).
Would you like to know more?
The difficulty however, is that taproot transactions use key tweaking, meaning a taproot UTXO on the blockchain is showing you a tweaked pubkey, not the original pubkey.
Even a script-less taproot transaction uses a tweaked pubkey, making cross-verification difficult. Also, Bitcoin Core is not very friendly towards exporting child keys and revealing tweaks.
This script takes the original pubkey and recreates the tweak in order to verify that a taproot pubkey and nostr pubkey are in fact the same key.
The next step is to build a signing extension, so a nostr user can prove they own a particular UTXO (and whatever may be inside of it 😎).
Would you like to know more?