Governments provide many services and collect a lot of information to provide those services. At least, that's how it works in theory. Some of this information should be made public in the name of transparency and to assist others in deciding where taxpayer money is spent, but others information must be kept private. Companies devising blockchain solutions for governments should work closely with governments to explore how blockchain works and match needs with functionality.
Dr. Wright opened Session 6 of Day 2 of Bitcoin Masterclass #7 by a foreign fraudster (probably by randomly selecting someone in the UK) who ran 15,000 companies in his name at his home address. We begin with an anecdote about a British national who was forced to register. . The government began pursuing victims for unpaid registration fees without attempting to confirm whether the registration was correct or even intended. Dr. Wright has personal experience with items delivered to his home (a piano) being flagged as suspicious, but sneakers delivered to a third party's address being flagged as suspicious. He added that there is.
“This is our problem now,” he says. Users need to control the keys that can be used to perform actions in their name, and these keys need to be notified when they are used.
If you move your tax returns, your licenses, all of that (to blockchain), your life will be much easier. Rather than having arcane cypherpunk-style debates about the nature of government itself, the industry strives to make things simple for ordinary people. And you have to convince everyone that this isn't just going to make their lives and business a little better, it's going to be 10x, 100x better.
Checking data and data to check
Validating or cross-checking records using a hash of the data may not be enough. There are unconventional names and situations, misspellings and variations, and random additional data (as discussed in the previous session).
Also, you should always use a challenge when submitting information. Otherwise, third parties will be able to match it with publicly available data. If you know how the data hashed, you can also perform a match on the data hash. You must ensure that sensitive data and changes to that data can be verified by one party to the transaction, but not by other parties.
Dr. Wright provides several examples of data that needs to be anonymized (if not completely necessary), database fields that should be considered, and government services that could work better depending on how data is collected and compared. I'll take it up. Be private. Remember, blockchain has a lot of information that can be authenticated without making the information itself public.
You also need to think about time. After a few years, being associated with an individual becomes less important and can be anonymized for statistical purposes. You might want to look at his tax receipts over time, but no one cares whether 50 years after his death he personally paid all the taxes he owed in a year.
There are many details that need to be discussed and decided before you start moving government records to the blockchain. Many of them may sound boring, at least on the surface. There is no single system that meets the needs of all governments in all countries. The advantage is that there are many niches that you can explore and specialize in. This means there are plenty of opportunities to generate potentially valuable ideas.
Recordings of all past seasons of The Bitcoin Masterclass are available on the CoinGeek YouTube channel.
Watch Bitcoin Masterclass #5: EDI Logistics and Goods Tracking
New to blockchain? Check out CoinGeek's Blockchain for Beginners section. This is the ultimate resource guide to learn more about blockchain technology.
