Nathan and I have been full time since July 11th so not on the coding side. My last day here is 23rd September then I'm 50-100% on voting software from there depending on work and things.
Structural update though: have realised that something I designed in 2014 solves an architectural issue:
Previously there was an issue with object permanence, IE once you submit a vote how do you guarantee it persists. You could embed it directly in the Bitcoin blockchain but then you're limited to Bitcoin's throughput which is not high enough. You could just submit a digest (hash) though and link to votes stored off chain, but then you have to store them someone. If we store them there's a centralisation issue, and if you use a DHT there's a permanence issue.
We solve this by using a block-dag to allow anyone being able to submit 'boxes' (1) of votes, where the block headers are the digest stored on the bitcoin blockchain.
I'll be doing some preliminary coding in the next few weeks then will hit it pretty hard.
Aiming for a live stress test in December that ppl at home can follow along with. Ideally we'll aim for half a billion votes in 24 hrs, probably livestreamed too. We need the underlying architecture first before the app can be written (and be trustless). We can also use a near-identical trustfull system (IE running on servers like a normal web app) to rapidly test and develop things.
Not having working software is a big setback atm (and a strong criticism). If I could go back to early 2016 I think we'd not contest the federal election heavily and focus on writing the software.
1: Basically a 'block' - IE list of transactions/votes - but called a box to differentiate because it's a layer over Bitcoin and there are also more blocks.