testbed api is now quite complete
 * problem with reconfigure was a bug in the testbed service
 * only thing left to to is to implement arm for manageService
  * (BUT: I don't get how arm works in conjunction with testbed -- when the arm api can't connect to
    arm it tries to start the arm service *locally*, which is often wrong ...)
  * talked to sriharsha about it

gnunet-java finally has a proper stream tokenizer ...
 * and locking has been removes from Scheduler, Helper is properly implemented

new java API implementation for identity :)
 * why is there no way to import keys?
  * at least API-wise
 * voting should use identity ...

timing information in ballot: we talked about round times,
but shouldn't this be done transparently by consensus?
aren't START_TIME, CLOSING_TIME, QUERY_TIME, END_TIME and maybe CONSENSUS_PARAMS be enough?

certificate authority: is the CAs pubkey different from its peer?
 * it definitely makes sense to have it seperate for other cert methods
  * like sending a cert per email, snail mail, social network ...
 * how do we specify how to reach the cert? one peer? multiple peers?
  * maybe use GADS? (I know very little about GADS right now)
 * does it even make sense to have the CA service at this time?

what now works:
 * authorities check for double vote submission, late / early voting, early result query,
   double registering, vouchers (I don't like to call vouchers receipts because that term has
   a certain meaning in voting literature already)

but: group certs are not checked right now

how to test voting without waiting too long or missing the right time?

any progress on crypto?
 * luckily the private key has the same size, so identity can be used

next:
 * use identity
 * multiple authorities should do consensus on unencrypted votes
 * tests for this with testbed
 * encrypting votes

suggestions?