Omer Shlomovits [ARCHIVE]

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2018-11-27 to 2020-12-16
💬 Posted a total of 3 messages
📚 Participated in the following categories: bitcoin-dev
🔇 Please do not DM this user as it's used for archive purposes only.

Public Key

npub1c9a5u7zmrdhczzudz4nuh3t7hmag6gx9ntdz7hguj5magyj35mksegxtzx

Profile Code

nprofile1qqsvz76w0pd3kmuppwx32e7tc4lta75dyrze4k30t5wf2d75zfg6dmgr80ymg

Author Public Key

npub1c9a5u7zmrdhczzudz4nuh3t7hmag6gx9ntdz7hguj5magyj35mksegxtzx

Show more details

Last Notes

2023-06-07 18:15:22

- reply

📅 Original date posted:2018-11-27
📝 Original message:Hello all,
I am working for the past few months with collaborators (in cc) on
providing Rust reference implementations to existing multi party schemes
for Schnorr signatures [1]. This includes aggregated signatures,
accountable signatures (which for n out of n are multi-signatures) and
threshold signatures (wip).
The project can be found here:
https://github.com/KZen-networks/multi-party-schnorr .
We aim that if the protocol is run in a configuration of a single party it
will be bip-schnorr [2] compliant.
Hope you'll find it useful :)
Questions, suggestions and pull requests are welcome!
[1] https://github.com/KZen-networks/multi-party-schnorr/tree/master/papers
[2] https://github.com/sipa/bips/blob/bip-schnorr/bip-schnorr.mediawiki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20181127/4f353499/attachment.html>