Bitcoin Forum
January 19, 2025, 05:37:16 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Trying to understand the benefits of multisig tapscripts...  (Read 76 times)
Jodmapht (OP)
Member
**
Offline Offline

Activity: 74
Merit: 21


View Profile
August 22, 2024, 12:14:40 AM
 #1

Hi,

Trying to educate myself about tapscripts, Schnorr signatures and taproot in general. My understanding is that taproot Merkle trees have the advantage of being able to reveal only the used path of the tree when signing a transaction. I am trying to understand if this can be leveraged at all for a k of n threshold scheme (putting aside the future possibility of using FROST when it is ready). For example, I would have expected that for a 2 of 3 with keys A, B and C, we would want to use 3 script paths:

- A and B
- B and C
- A and C

However, from what I have seen it seems that this is not how it is done, and even that using the same key more than once is not allowed, which would not even make it possible to do.

Am I understanding this properly? If so, why would a single script path be preferable for a threshold scheme? Finally, why isn't it allowed to reuse the same key within multiple script paths?

Thanks!
Jodmapht (OP)
Member
**
Offline Offline

Activity: 74
Merit: 21


View Profile
August 29, 2024, 06:46:23 PM
 #2

Anyone knows about this? If my question does not make sense, please let me know!
Ambatman
Sr. Member
****
Offline Offline

Activity: 518
Merit: 461


Playbet.io - Crypto Casino and Sportsbook


View Profile WWW
September 04, 2024, 04:55:52 AM
 #3

The essence of Taproot is to improve privacy and efficiency and it's most efficient when you are using script path or non. Though using what you mentioned above is correct in a traditional of K of n scheme, But not quite the most efficient in Taproot.
In taproot rather than using all the combination as seperate script path, multisig( a schnorr based signature that allows multiple keys to produce a single aggregated public key and signature) is quite more efficient.


Yes you have it right. Now the reason for using a single script and not using same key more than once is for security purposes.
Using a single script is more efficient(reduces the size of the transaction since only one public key is needed) ,secured( improves privacy since specific private keys used is not shown) and not to mention simpler (since you using an aggregated script rather than multiple script).


Anyone knows about this? If my question does not make sense, please let me know!
It does.

█████████████████████████
████████▀▀████▀▀█▀▀██████
█████▀████▄▄▄▄████▀████
███▀███▄████████▄████▀███
██▀███████████████████▀██
█████████████████████████
█████████████████████████
█████████████████████████
██▄███████████████▀▀▄▄███
███▄███▀████████▀███▄████
█████▄████▀▀▀▀████▄██████
████████▄▄████▄▄█████████
█████████████████████████
 
 BitList 
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
REAL-TIME DATA TRACKING
CURATED BY THE COMMUNITY

.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
 
  List #kycfree Websites   
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!