-
[Research Summary by Tina](https://docs.google.com/document/d/1nfh4An1g49jzV6wEaCrNDwc80nCQj1WQkJpSUQy17uQ/edit)
-
Looking over the current `protocol.pdf`, we are using the following nonstandard primitives. We should prove all of them secure using reasonable assumptions about SHA256.
- The four PRFs.
- The fixed-d…
-
We stopped using magenta to indicate changes from Zerocash.
daira updated
3 years ago
-
Bonsai is based on [Coda](https://codaprotocol.com/static/coda-whitepaper-05-10-2018-0.pdf)'s technique of verifying state transitions between trees of mutable accounts. In Coda, this requires you to …
daira updated
3 years ago
-
I hear bitcoin-core plans to remove OpenSSL as a dependency (at least in the consensus path) as it migrates to libsecp256k1. I _think_ it may be using the latter today for signatures and openssl for …
-
**Inspiration**
*IETF specifications*
- [RFC 791 - Internet Protocol](https://tools.ietf.org/html/rfc791)
- [RFC 2818 - HTTP over TLS](https://tools.ietf.org/html/rfc2818)
- [RFC 5246 - The Tr…
-
Our commitment scheme follows ZeroCash's and truncates the outer commitment to 128 bits.
ZCash considers this as a vulnerability however as an adversary would need to perform only 2^64 operations t…
-
If we follow #2171 and the general approach of the Sapling design that Ian/Matt/I are working on, it will be more than feasible to "mint" (as in Zerocash) in the coinbase transaction, allowing us to e…
-
The attack below seems to be a vulnerability:
User U broadcasts a transaction to which calls \mix to withdrawn funds from the mixer. A malicious Ethereum node A notices the transaction in the mempo…
-
This issue describes the planned protocol features that need to be activated by consensus for the next major release (planned to be 1.21)
## Summary
With the next major release, we plan to propo…