Bitcoin Forum
May 06, 2024, 05:42:24 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Taproot with scriptTree only  (Read 62 times)
acurast (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 6


View Profile
February 16, 2024, 08:10:32 PM
Merited by BlackHatCoiner (4), ABCbits (1)
 #1

Hi there

I'm currently playing around with Taproot and from what I understood a taproot address will always be spendable by either the set internal_pubkey or the script_tree. Now what is the best practice if I don't want it to be spendable by an internal_pubkey? I was thinking of using provably unspendable internal_pubkeys (i.e. "null pubkey"), but thought I ask before going down a wrong path.
1715017344
Hero Member
*
Offline Offline

Posts: 1715017344

View Profile Personal Message (Offline)

Ignore
1715017344
Reply with quote  #2

1715017344
Report to moderator
1715017344
Hero Member
*
Offline Offline

Posts: 1715017344

View Profile Personal Message (Offline)

Ignore
1715017344
Reply with quote  #2

1715017344
Report to moderator
1715017344
Hero Member
*
Offline Offline

Posts: 1715017344

View Profile Personal Message (Offline)

Ignore
1715017344
Reply with quote  #2

1715017344
Report to moderator
Once a transaction has 6 confirmations, it is extremely unlikely that an attacker without at least 50% of the network's computation power would be able to reverse it.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 3388
Merit: 6581


Just writing some code


View Profile WWW
February 16, 2024, 08:53:56 PM
Merited by ABCbits (1)
 #2

BIP 341 recommends using the following provably unspendable pubkey: 50929b74c1a04954b78b4b6035e97a5e078a5a0f28ec96d547bfee9ace803ac0

Otherwise, just pick your own provably unspendable pubkey to use as the internal key.

acurast (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 6


View Profile
February 16, 2024, 09:02:52 PM
Merited by vjudeu (1)
 #3

this is helpful thx! I missed that while going through the docs earlier, was expecting to find something like '0101010101010101010101010101010101010101010101010101010101010101'

vjudeu
Hero Member
*****
Offline Offline

Activity: 678
Merit: 1560



View Profile
February 16, 2024, 09:26:43 PM
Merited by icopress (1)
 #4

Quote
was expecting to find something like '0101010101010101010101010101010101010101010101010101010101010101'
This public key is also valid: 0401010101010101010101010101010101010101010101010101010101010101014D1FD6A5F1A2C BD8536CF702611B753557B0841CA6B327F33C531903CA1A9428. And by hashing it, you will get another valid key, which is 02bab95d0a0de48828c93401baaf87e8fcd777c08bd972051abbe61ab4a49530cb.

However, it is recommended to use N-of-N multisig instead. So, if you have any TapScript, and for example five people put their coins in, then 5-of-5 multisig is better than some unspendable key, because then, there is a small chance, that all of them will be online, and all of them will be honest, so they will join their signatures, to spend those coins in a cheaper way (because spending by key is usually cheaper). And if any of those parties will be offline, then the outcome will be the same, as in case of some unspendable key. However: if the TapScript will turn out to be unspendable for any reason (for example mistake in endianness in the code), then it may be possible to spend it by key, and it may be useful, to experiment with TapScript, without burning coins.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!