Thread by @svpino

For one second, let's forget the idea of a central database.

Imagine a product that doesn't store your data. Instead, you keep that information. You allow others to use it at your convenience and close it whenever you want to.

Let's talk about one example. ↓

2. Think about those people that have built excellent profiles using @kaggle.

They have participated in many competitions, shared their knowledge, and built impressive curriculums.

What would happen if Kaggle decides to ban them?

3. This is not science fiction.

Every single company out there can ban you if they decide to do so.

Maybe it is justified, maybe it isn't, but that's beyond the point.

What happens then?

4. If Kaggle bans you, your entire profile and reputation disappear.

There's nothing wrong with Kaggle, and the same thing applies to Twitter, Facebook, or YouTube:

We are one decision away from losing everything we have built on top of these platforms.

5. The fundamental problem here is that these platforms own your information and everything you have built on top of them.

That Grandmaster title exists as long as Kaggle wants.

6. But this doesn't make sense:

You earned those certificates, built that audience, and completed that course.

You should be in charge of this data.

What's the alternative?

7. Let's get back to the Kaggle example.

Imagine if you could store the titles you earn instead of relying on a central database.

Imagine if there was a way for Kaggle to "write" a Grandmaster badge on your personal database.

8. Kaggle could go away tomorrow. Or they might decide not to let you compete anymore.

But they don't own the Grandmaster badge: you own it, and you get to keep it.

All of your work doesn't depend anymore on a third-party company!

9. This is a fundamental promise of web3 and one of the features that will redefine the world in the coming decade.

We will shift from "centrally stored" to "fully decentralized" and "personally owned."

Let's talk about some specifics.

10. Here are some of the essential bits:

You have a place in the blockchain where you can store information. Whatever lives in that place is associated with you.

Have you seen people buying NFTs? Those "ownership certificates" end up in this place under their name.

11. Let's call this place our "wallet."

Everything in our wallet we own, and we can easily prove it.

Now, think about any institution that issues certifications: AWS, Kaggle, Microsoft, Coursera, Udemy, universities, anyone.

12. When you complete a course, or get a certification, or win a competition, the issuing authority could give you a "token" that you can store in your wallet.

Just like an ape JPG, but this time, something that certifies that you completed the work.

13. They don't need to store who you are and your achievements in their database anymore.

Instead, you store the badge in your wallet.

This is enough for you to prove you did the work.

14. These badges could even be smart:

They could automatically expire after a few years.

You won't be able to transfer them to another wallet.

They could even act different depending on other badges you already own.

15. These badges be your key to a club or a prerequisite to access another—more advanced—certification.

A collection of these badges will become your resume, impossible to falsify and readily available for whoever needs it.

16. You can push this idea even further and think about companies issuing badges, encoding your years of service, and the skills you used during that time.

Interviews could become a simple check of your collection of badges.

17. The technology to make most of this happen already exists.

Of course, web3 is just getting started, and it will take some time for the world to catch up, but the possibilities are fascinating.

18. This is just one example of how the simple idea of "owning your data" could change the landscape.

I'm experimenting right now with this very idea. It's exciting, new, and it has taken me some time to fully see the entire picture.

I'll report back with my findings.