aboutsummaryrefslogtreecommitdiff
path: root/ISSUES
blob: 3da6f9310d22da9192e200f0f367ef112a8f777d (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
mesh service regularly segfaults when running secretsharing

how do the *_QUOTA_* options of ats work?

thesis / voting:
coercion-freeness (there is no way for me to prove you that I voted for party X)
 * current implementation is not coercion-free (nonce for encryption is the proof)
 * most of the literature published on coercion/receipt-freeness turned out
   to be faulty
 * basic problem: the r in (g^r,m*h^r) can be used as proof of what we voted (m)
 * the sako+hirt construction posts one list of vote choices per voter (!!!) on the bulletin board,
   voters only give number of choice
 * there are some ideas based on re-encryption and designated verifier proofs of re-encryption
  * I think the main reason they do not work for the approach we implement is that we need (in
    contrast to mix-based voting) zero knowledge proofs of valitity
 * I believe we could have a system that is resistant against vote-buying under
   the assumption that none of the authorities cooperates with a vote-buyer.
  * the voter would ask an authority to re-randomize the vote
  * the voter again must re-randomize the vote so that the authority can't associate the vote
    with the voter
  * if the authority is compromized, the coercer could force the voter to leave out the 
    re-randomization

How extensive should the discussion be of completely different (mixnets / blind signatures) voting
systems? 

------------------------------------------------

regarding digital currencies:
have you heard about ripple?
They have:
 * a public ledger
 * a group of validators (peers)
 * a set of transactions
 * a consensus on transaction set to apply to the ledger
   (done repeatedly)
Does that sound vaguely familiar? ;-)

However, they do nothing about byzantine consensus ... 
how are they not susceptible to "transaction stuffing", fragmenting the ledger?
Why does nobody mention this?

Quote (wikipedia):
"For its creation and development of the ripple protocol (RTXP) and the Ripple
payment/exchange network, the Massachusetts Institute of Technology (MIT)
recognized Ripple Labs as one of 2014’s 50 Smartest Companies in the February
2014 edition of MIT Technology Review. "