Ignotus Peverell
Ignotus Peverell
I'm not arguing hyper has a lot of eyes on it, but it does have a lot of dependencies. How many eyes on that one? `hyper > tokio > tokio-fs...
Anything showing the current p2p layer is CPU intensive, and the source of that?
Relevant paper: https://crypto.stanford.edu/~dabo/pubs/papers/BLSmultisig.html
I'll need a couple more reads to fully parse this, especially security arguments, but you tickle me pink Gandalf.
Correct me if I'm wrong @gandalfthepink (or anyone else who had a look) but there seems to be an important privacy regression with hanging transactions. Specifically, for the hanging transaction...
@GandalfThePink > To be more specific, all participants that are offline can only receive unblinded. That's what I meant. For hanging transactions to be included in the chain to be...
Sorry for taking so long to follow-up. Can you elaborate on the setup of that shared secret? If both public keys are known, it doesn't seem it can easily be...
To complement, this could have 2 applications: 1. Light clients. 2. Really fast sync, with full headers downloaded in the background afterward.
Marked this for T4 just for the header `previous` change. Actual sync can come later.
The `len()` is a leftover from when we had Borromean sigs based range proofs. Maybe some code to remove...? I'm ok with the approach otherwise.