How it works(technical)
Frontend ↔ Logic, Bindings code ↔ Backend.
The HTML, CSS and Javascript that form the Gui. It is good if the javascript just works if you put the id= in the right places.(i.e. you dont need to write javascript to change the looks)
The bindings read from the backend, for instance with PoC javascript bindings.
Round that there might be some logic to make it more 'general purpose' and reusable.
The backend consists of three separate parts:
- Ethereum entities users create as votable items.
- Bitvote.
- The one person per ID.
These use Bitvote to show how many votes they have. They could be as simple to keep a little counter, or they may automatically do some stuff based on votes. It might have its own page or entire website aswel.
Bitvote itself, it keeps track on how much vote-time people have and how much votable items have, it will allow other contracts to show that they got some amount of votes. It uses the one-per-ID system to establish voting-accounts.
It will have some self-improvement/fixing features. For instance, it will have a voting mechanism to change the one-per-ID system entirely. Of course changing something that important should be very difficult.
Keeps track of identities so that to sufficient certainty each person has one, next to scalability, this is not entirely solved at this point. To large extent it will be its own thing next to bitvote.
