Bitcoin Forum
May 05, 2024, 11:37:26 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: libsecp256k1 schnorr sigs - how to determine the number of signers  (Read 803 times)
jl777 (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1132


View Profile WWW
June 06, 2016, 10:40:19 AM
 #1

I have been experimenting with the schnorr combined signatures and I cant figure out how to directly determine the number of signers.

From what I am seeing, the combined pubkey will say any combined pubkey with any subset of signers is valid.

I dont see a clean way to get a specific threshold validation. Is the process to iterate through all the pubkeys from each signer to see which ones validate against the combined signature? Otherwise it seems that some sort of combinatorial explosion of combined pubkey needs to be made to find the exact set of signers.

but I only need the number of signers, not the exact ones, so I am hoping there is a simple way

James

http://www.digitalcatallaxy.com/report2015.html
100+ page annual report for SuperNET
1714952246
Hero Member
*
Offline Offline

Posts: 1714952246

View Profile Personal Message (Offline)

Ignore
1714952246
Reply with quote  #2

1714952246
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
tonytumble
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
June 08, 2016, 10:46:07 PM
 #2

I have been experimenting with the schnorr combined signatures and I cant figure out how to directly determine the number of signers.

From what I am seeing, the combined pubkey will say any combined pubkey with any subset of signers is valid.

I dont see a clean way to get a specific threshold validation. Is the process to iterate through all the pubkeys from each signer to see which ones validate against the combined signature? Otherwise it seems that some sort of combinatorial explosion of combined pubkey needs to be made to find the exact set of signers.

but I only need the number of signers, not the exact ones, so I am hoping there is a simple way

James

i would determine it by iterating through every users pubkey and validating them against the sig. I don"t think there is a easier way as its not known how many users combined their sigs into the merged "unified signature" which from my understanding does not reveal who nor how many people signed. but with their pubkeys you could validate their participation incrementaly.
jl777 (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1132


View Profile WWW
June 10, 2016, 03:17:01 AM
 #3

I have been experimenting with the schnorr combined signatures and I cant figure out how to directly determine the number of signers.

From what I am seeing, the combined pubkey will say any combined pubkey with any subset of signers is valid.

I dont see a clean way to get a specific threshold validation. Is the process to iterate through all the pubkeys from each signer to see which ones validate against the combined signature? Otherwise it seems that some sort of combinatorial explosion of combined pubkey needs to be made to find the exact set of signers.

but I only need the number of signers, not the exact ones, so I am hoping there is a simple way

James

i would determine it by iterating through every users pubkey and validating them against the sig. I don"t think there is a easier way as its not known how many users combined their sigs into the merged "unified signature" which from my understanding does not reveal who nor how many people signed. but with their pubkeys you could validate their participation incrementaly.
thanks, I guess this requires every node sharing the pubkeys globally... But if that is the case then how would this save space on the blockchain as these are temporary keypairs each multisig would need all the pubkeys, which is essentially the same as now.

Not exactly the behaviour I was expecting.

I had thought using schnorr partial sigs allowed for space efficient threshold sigs, ie MofN
If iterating through the pubkeys is required, that seems to not allow any space savings

http://www.digitalcatallaxy.com/report2015.html
100+ page annual report for SuperNET
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!