Pennsylvania Voter Registration Databases.
Now How Would You Explain This?
As we looked at the lists of elderly and very young voters, we noticed something rather extraordinary. A few of these voters were listed twice, with identical information, including identical voter IDs.
In Pennsylvania, each voter record has a “base ID” of nine digits, then a hyphen, then a two-digit code indicating the county. For instance the voter ID 00123467-01 indicates that the voter lives in county 01, or Adams County.
If that voter moved to Allegheny county, his or her new “full ID” would be 00123467-02. That voter’s “root ID” is 00123467, and that id should identify the voter as long as he or she is a voter in Pennsylvania.
Duplicate Voter IDs
As stated in Pennsylvania’s Title 25, each voter should have exactly one ID. This means that when the voter moves to a new county, the previous ID must be deleted. Given this fact, we made lists of all the “full ids” and “root ids” in each data set, and checked for duplicates.
We found nearly 13,000 exact duplicate records (same root ID and same county) and over 2000 “two county” duplicates (same root ID, different counties) in our November 7th and November 28th data sets.
This is particularly surprising because very simple database maintenance should have detected these duplicates and deleted them, perhaps after mailing requests for address verification in the case of “two-county” duplicates.
That is right. Over 2,000 duplicate voters that suddenly showed up in multiple counties.
All of the one-county duplicates and most of the two-county duplicates suddenly disappeared before the next data set. In other words, these duplicates showed up right before the election and went missing right after the election.
We then took a closer look at the complete records for the voters with two, identical IDs; and we found something truly bizarre and extraordinary.
The two records were identical, except for the fields showing voting history for the past 40 elections. In all cases, there is no commonality in the data between the voting patterns of the duplicate voter and the legitimate voter.
We internally consider the Voting Record field the DNA equivalent of the voter. It is probably the best identifier of a voter. People share names and even birthdays; but when you throw in the last 40 elections, they really should look quite different.
So how were these changes made? How would a coincidental—almost opposite—voting record get attached to these duplicate voters? Why didn’t the system pick this up?
The “duplicate count” for our November data set and for the two earlier and two later data sets is here.
The Importance of Voter Registration Databases
The point here is simple. Voter Registration Databases are the foundation of a safe election. They should be secured and maintained. They should have no known erroneous data or anything like we are seeing. It is an invitation to trouble.
> When we see data that looks like it isn’t a function of a database (as above), we worry.
> When we see duplicate voters with fields changed to opposite data, we worry.
> When we see voters being duplicated and showing up in multiple counties at the time of the election, we worry.
> When we see all of this show up right before the election and disappear right after, we really worry.
We still haven’t found the bottom of this Rabbit Hole. Let’s go deeper.
Read the rest of the Pennsylvania Rabbit Hole Series:
- Pennsylvania Rabbit Hole Part I
- Pennsylvania Rabbit Hole Part II
- Pennsylvania Rabbit Hole Part III
- Pennsylvania Rabbit Hole Part IV
- Pennsylvania Rabbit Hole Part V
- Pennsylvania Rabbit Hole Part VI
- Pennsylvania Rabbit Hole Part VII (Current article)
- Pennsylvania Rabbit Hole Part VIII
- Pennsylvania Rabbit Hole Part IX
- Pennsylvania Rabbit Hole Part X
Written by Unhackthevote