-
Needs to track all information needed to generate a Pour transaction.
**Edit 2015-08-24** We decided that #31 is a duplicate of this ticket.
**Edit 2017-01-24** This ticket means different thing…
-
In the Great Bitcoin Schism, both sides are converging on 2 MB blocks being okay, and the current remaining disagreements are about when to schedule a hard-fork upgrade of Bitcoin from 1 MB blocks to …
-
## what
Take a look at presentations in Scaling Bitcoin conference in 2015 held in HK.
https://scalingbitcoin.org/hongkong2015/#presentations
## why
To learn from other people's suggestions.
## how
…
-
-
We'd like our circuit to be able to detect usage of a bucket commitment produced by a previous circuit which may not be compatible if we were to switch circuits and change the overall scheme in some w…
-
The vast majority of the zk-SNARK circuit's complexity comes from witnessing a coin commitment in the anchored merkle tree. We can split a pour into two operations that can occur at different times: o…
-
-
@amiller just presented a new result that allows converting (any?) PoW puzzle into a non-outsourceable version. Is this practically applicable today? If so, should we make nonoutsourceable a property …
-
@nathan-at-least please add cool labels to this issue
We should reduce the fallout of a potential public parameter failure or crypto vulnerability. If our snark crypto fails in some way, we don't wan…
-
I suggest renaming some of the basic entities in protocol, to more accurately reflect what they really are:
**owner** - the tuple (a_{sk}) and all other keys derived from it
**title** - currently call…