Crypto Protected Voter Registration Lists :SOVRINTown and IOTA

Well, now more than ever, it's crypto's (public Distributed Ledger  "DL")  time to shine, as 'THE' platform for securing the Vote.

one look at this camera feed is all it takes for anyone in the 'free' world to realize the whole voting system needs an overhaul, fast.

No More 'Crime of The Century' stuff please. :/

Such a proposed public DL and Smart Contract controlled voting system overhaul starts with revamping the way voter registration lists are created and updated in a trustworthy manner, providing both summary data to the public, yet preserving voter privacy.

Ok, how to get a voter Identity, trusted by the voter, private to the voter onto the voter list requires  the solution have a  configurable "line in the sand" , between which fields are private and, which are public/viewed by anyone from their browser over the Internet. (or on a wall of paper printouts

Protecting Voter Privacy on the Public DL  'Blockchain' with Smart Contract controlled Voter Registration Lists

Clearly the following  voter fields need to be private:

Name, Driver's License, address, Proof of age/ID Card Info,  telephone number, signature etc.., so what to show on the public distributed ledger?

<> is a start, which should match that issued on the ballot, and be required for entry at time of vote, either online, via mail voting, or directly at polling day (otherwise you file a provisional vote including proof of new residence, a rental cotract, power bill, and updated driver's license as an example.

Also the voting  <> field  must also be entered from a restricted set of records found in a SC Managed LUT "Look Up Table" containing only valid ward/precinct IDs and their companion description field so the voter know which one to select. Each field may have an information map button so you can search by your address to see which ward you are in, generally the SC will auto populate based on the voter address information and ask you to confirm your entry through the web app allowing the evoter access to the SC controlled Voter Registration List. 

The Unique Voter ID is portable for the State, to facilitate movement  "ward to ward" if you actually do move in state. Between state/province moves would need to have the two public DLs in question facilitate the transfer through  a gateway Oracle with interfaces to both different state/province or  Voter Registration Lists. This would mean part of the Voter ID would need to be mutable with the <>  mutable field short form abbreviation.

Also a  <> field must  accompany  the first two fields : to allow the voter to select from an SC controlled LUT the correct entry from a list  like this: personal information validated; in process; not yet validated, which  needs to be viewed in public along with a <> field to describe the state, where the latter is automatically filled in with values found  in LUTs "Lookup tables" immutably mounted on the public DL and the former , the same, where the validation flag status matches the state/province requirements for voting, where the SC app copies the values from the LUT entry selected and posts that value into the unique voter ID field of the same name.

How many Registered Voters in your Ward/Precinct? A 'snap' for any public DL

A well constructed voting systems on public DL handles this 'dynamic counting' chore easily, via a Smart Contract  "SC" controlled and secured update of the <>, a numeric value which is stored by the SC on the public DK as mutable (changeable) data field at the Smart Contract Address, where the SC is really the Voter Registration List for the <>, meaning the SC has as many fields necessary for the number of wards/precincts in the voting district. 

Handling voter moves: Self Service for the voter getting it right everytime via Smart Contract Apps

As voters comes and go (move in and out of the voting district physically, it is clear the address field needs two fields to support such movement, <> field, which means the address field is mutable(changeable), meaning the SC handles the actual date update of the date change field, which itself is mutable/changeable and only changed after the User has hit the return key, confirmed the entry again by clicking yes I want to update,  where the SC is checking the Internet Distributed network time  clock on the internet (multiple sources) via the same dNTP  Layer 4 ISO protocol which is checked over the Layer 3 ISO Internet Protocol "IP" for the voter changing their ID to get it right every time.

Open Source Voting Systems: Easy to verify the operation and security of the System, by anyone.

Such "Whitebox" systems means the voter/rate payer can expect to have their vorting districts (City or County or some arbitrary, politically legislated voting district geography)  to   pay less to implement such  public DL 'open source' system. Such systems are easily tested and certified "secure and safe" as the software code is open source.

Well that is all for now, as we move forward with #SOVRINTown evoting ideas crafted with #IOTA 's  public DL #TANGLE,  to help solve the mess the "Cracken" is exposing in the US 2020 Election debacle.

Be safe!

TK over and out! 

*****