Hangout preparation

NOTE: edit this agressively?! Just prepend/append if you dont know how to incorporate. Feel like i am writing some of this a bit too definitely to encourage discussion/interaction.

Topics?

• Core architecture
• Use cases.
• Additional tools. Interpreting Bitvote state. Some provided, independent ones encouraged)
  • I.e. interfaces to it, buttons.(html+js) (Careful! Phishing)
  • Analysing behaviors/potential attacks/OnePerID performance.
  • The users information is largely their concern. I.e. journalism, organizing, discussion, etcetera. However, we should probably discuss it if it comes up.

Subtopics

• Scalability issues

  • Been assured they're working it in Ethereum itself.

  • Hanging blocks.('auditable blocks') Has data availability issue, but because Bitvote is about voting, votes might be amenable way for the contract to know whether data is available.

    Also has advantage that you could do things more gas-expensively, and use binaries especially for it.

• Anonymity? Probably ring signatures.

  Ring signatures largely prevent people from figuring out statistics like the size of single contributors!

  Anonymity can help make sale of vote-time difficult.

• OneperID: by far most difficult bit.

  • Will likely not stay the same in use! Has mechanism to change!

  • 'Bioauthentication': to be honest, how do measurements about someones persons known to the contract?

  • Synchronized pulsed computer-hard actions: do stuff computers have difficulty doing, and a lot of it at a time.

    How do you measure the activity?

  • Reputation systems: vouching that other people not-yet have an account to give them an account. Or vouching about a mistake/attack where someone got multiple accounts.

  • Old-world stuff, i.e. pubkeys on passports.