-
Notifications
You must be signed in to change notification settings - Fork 993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Study support of vaults in grin/mimblewimble #71
Comments
No panic on response, but what's the intended mechanism for time-locked transactions? Edit, never mind, I need to look at the other time-related issues more closely. |
You're in for some reading :-) It's mostly on the mailing-list, mixed up with more sophisticated contract explorations. I'd look over the following threads, check some of the replies as well: https://lists.launchpad.net/mimblewimble/msg00022.html |
Heh... at some stage I'll have a look through that lot and try to summarise here, for easier future reference. |
Multisig we effectively get for free right? It can be handled entirely in the wallet impl? http://diyhpl.us/~bryan/papers2/bitcoin/mimblewimble-andytoshi-INCOMPLETE-DRAFT-2016-10-06-001.pdf
|
Andrew assumes Schnorr sigs in his paper, however those aren't ready yet (although getting close from what I can see at bitcoin-core/secp256k1#461). So yes, once we have Schnorr, they'll basically come for free. For now, as we temporarily do ECDSA, we don't have multisig. |
Ahh makes sense - thanks! |
In September, Schnorr sigs were not ready yet. Does |
grin uses Schnorr since a couple months, and this issue talks about time locked transactions which we presumably already have. So with both pieces, what's left to research or implement in this issue? |
Grin should already support in the near future:
Using these primitives, figure out how to implement vaults [1] [2].
[1] http://hackingdistributed.com/2016/02/26/how-to-implement-secure-bitcoin-vaults/
[2] http://fc16.ifca.ai/bitcoin/papers/MES16.pdf
The text was updated successfully, but these errors were encountered: