July 24, 2023
Future of Social Cryptocurrency in Web 3 with Pi Network's Co-Founders, Dr. Nicolas Kokkalis and Dr. Chengdiao Fan
Host Alex Kehaya welcomes Pi Network's Cofounders, Dr. Nicolas Kokkalis and Dr. Chengdiao Fan this week. Tune in to learn more about the open-source technology powering Pi Network's unique consensus algorithm and how it makes crypto mining accessible and eco-friendly. They discuss how they utilize AI to verify identities worldwide by balancing automated and manual processes to ensure network safety and security. Get ready to explore the future of social cryptocurrency in Web3.
Host - Alex Kehaya
Producer - Shawn Nova
Chapters
00:04 - Exploring Pi Network's Mobile Mining Concept
13:38 - Pi Network's Mainnet Innovation and Utility
18:40 - KYC Solution and Applications on Pi Network
29:58 - PyOS License's Impact on Collaboration
Transcript
WEBVTT
00:00:04.427 --> 00:00:08.013
Welcome to the Index Podcast hosted by Alex Kahaya.
00:00:08.013 --> 00:00:13.529
Plug in as we explore new frontiers with Web 3 and the decentralized future.
00:00:19.129 --> 00:00:25.888
Hey everyone and welcome to the Index brought to you by the Graph, where we talk with the entrepreneurs building the next wave of the internet.
00:00:25.888 --> 00:00:27.405
I'm your host, alex Kahaya.
00:00:27.405 --> 00:00:38.131
In today's episode of the Index, I'm thrilled to welcome Nicholas Cacolus and Cheng Zhao, the co-founders of Pi Network, the first digital currency that can be mined on your phone.
00:00:38.131 --> 00:00:45.003
We will learn all about how Pi differs from other crypto projects, their approach and the utility that they're building.
00:00:45.003 --> 00:00:45.905
Welcome to the show.
00:00:45.905 --> 00:00:46.545
Thanks for being here.
00:00:47.067 --> 00:00:48.470
Thank you for having us, alex.
00:00:48.470 --> 00:00:49.212
Thanks Alex.
00:00:49.619 --> 00:00:52.209
So I would just first love to learn more about you guys.
00:00:52.209 --> 00:00:53.603
How did you meet?
00:00:53.603 --> 00:00:55.284
How did you get the idea for Pi?
00:00:55.284 --> 00:00:58.307
What is the genesis story in your backgrounds?
00:00:59.179 --> 00:01:03.692
Pi Network is a combination of our academic and also personal interests.
00:01:04.340 --> 00:01:20.730
Nicholas and I got to know each other a long time before we built Pi, so he is always a hardcore computer scientist, from hardware to theory or distributed system, which is a precursor to blockchain and later human computer interaction.
00:01:20.730 --> 00:01:23.123
I am a social scientist.
00:01:23.123 --> 00:01:43.805
During my second half of my PhD at Stanford, I also got interested into human computer interaction, so that's where Nicholas and I collaborated many years on multiple projects in social computing, crowdsourcing, building large scale systems, design systems for scaling, human communication and productivity.
00:01:43.805 --> 00:01:49.871
We wrote a few papers together and then we both are interested in entrepreneurship.
00:01:49.871 --> 00:01:52.507
So we combine all this interest together.
00:01:52.507 --> 00:02:06.771
Pi combines all this interest I mentioned above and to solve human interaction, facilitate large scale participation and collaboration to create something larger than just the people combined collectively.
00:02:06.771 --> 00:02:15.687
And then we think blockchain is a very powerful technology to facilitate that and we look into the solution in that space.
00:02:15.687 --> 00:02:27.790
And actually Nicholas was even teaching a class on decentralized applications, on blockchain, and through that experience we discover certain issues of the industry at the time.
00:02:28.939 --> 00:02:35.469
Especially through that experience, we were very frustrated with the current limitations and implementations of the crypto industry at the moment.
00:02:35.469 --> 00:02:41.693
We initially tried fixing the user experience problems that some other platforms had.
00:02:41.693 --> 00:02:51.532
Soon, we realized that without actually building our own platform, we would not be able to create a truly decentralized and truly accessible cryptocurrency for people to use.
00:02:51.532 --> 00:02:59.485
So that's because, fundamentally, people would not have been able to mine it themselves without upfront financial costs.
00:02:59.485 --> 00:03:16.524
We ended up designing Pi to address all these issues and we aimed to have it have accessibility and wide distribution on a large social network that recognizes Pi and, this way, allows true utility to emerge.
00:03:17.086 --> 00:03:18.969
Really interesting and it's all done on the phone.
00:03:18.969 --> 00:03:27.150
One of the things you guys are trying to accomplish is just lowering the barrier and to make it more accessible, and I think that's been the holy grail of crypto for a while.
00:03:27.150 --> 00:03:33.586
I remember I got back in the space in 2016, and that was the narrative then and it's still the narrative now.
00:03:33.586 --> 00:03:35.224
It's still a work in progress.
00:03:35.224 --> 00:03:42.931
There's a lot to be done, but I'm just genuinely curious to learn more about your approach to solving that problem.
00:03:42.931 --> 00:03:53.131
Let's go a layer deeper and talk through what it actually looks like, what Pi does and how it brings that user experience problem and accessibility problem fixes that.
00:03:54.282 --> 00:03:57.069
Yeah, accessibility has multiple aspects.
00:03:57.069 --> 00:04:06.231
There is the financial barrier, there is knowledge barrier, there is also the easy to use or the technical, logistic barriers.
00:04:06.231 --> 00:04:24.829
So in order to achieve true accessibility, you need to solve all these barriers in order to break down all the barriers and have a free flow of user experience, and that's what Pi is trying to address those issues so, specifically, have a phone that is accessible.
00:04:24.829 --> 00:04:26.786
Almost these days, everyone can have a phone.
00:04:26.786 --> 00:04:29.668
And also, accessibility is about equal opportunity.
00:04:29.668 --> 00:04:52.096
So it's free, everyone can just go to the app store and download and then easy to understand, meaning that people don't have to have a CS degree in order to know how to run a node to mine, but they can use a phone and an app and building the user experience easy enough for them to follow the education of the whole process of what is mining, how you can mine.
00:04:52.096 --> 00:04:53.442
This is also important.
00:04:54.225 --> 00:04:58.990
I would love to dig deeper into the consensus or just how that works From a mining perspective.
00:04:58.990 --> 00:05:06.836
That is definitely one of the biggest things, especially for early adopters, that you miss out on If you're not highly skilled DevOps engineer.
00:05:06.836 --> 00:05:10.410
In most cases you cannot participate at that level in the earliest days.
00:05:10.410 --> 00:05:20.935
A lot of that has to do with the software, the validator software, and how complex the algorithms are or whatever to validate and to set up that validator.
00:05:20.935 --> 00:05:22.449
How does it work in your system?
00:05:22.449 --> 00:05:24.839
It sounds like you get set up really easily, but under the hood.
00:05:24.839 --> 00:05:26.428
I'm curious to learn more about that.
00:05:26.904 --> 00:05:31.627
The essence is a different type of consensus algorithm In terms of how it works.
00:05:31.627 --> 00:05:35.036
If you compare it to Bitcoin, everyone knows Bitcoin uses proof of work.
00:05:35.036 --> 00:05:37.485
Let's compare it to Bitcoin.
00:05:37.485 --> 00:05:41.475
Like Bitcoin, Pi is also running on its own blockchain, so it's a later one solution.
00:05:41.475 --> 00:05:43.730
We are not running on other people's blockchain.
00:05:43.730 --> 00:05:46.874
Unlike Bitcoin, we use different types of consensus algorithms.
00:05:46.874 --> 00:05:48.230
Bitcoin uses proof of work.
00:05:48.230 --> 00:05:54.918
The requirement for that consensus to run is contributors or miners contributing energy and electricity.
00:05:54.918 --> 00:05:57.100
In return, they receive Bitcoin rewards.
00:05:57.100 --> 00:06:00.374
In Pi's case, we use federated bisanding agreements.
00:06:01.125 --> 00:06:04.214
In Pi's specific blockchain, it actually relies on a trust graph.
00:06:04.214 --> 00:06:09.697
A trust graph is an essential component feed into the blockchain for it to reach consensus.
00:06:09.697 --> 00:06:17.192
The mobile miners are actually contributing to this trust graph that the blockchain will use in order to secure the ledger.
00:06:17.192 --> 00:06:27.136
Each miner, each mobile miner, actually are contributing by their trust circles we call it security circles, which is they appointing three to five people they trust.
00:06:27.136 --> 00:06:45.315
In aggregate, millions of people's trust circles forms this trust graph that will be used by the blockchain and to scale the mining in analogy is Pi's consensus algorithm requires the trust graph and contributors or miners contributing to the trust graph in return receive Pi rewards.
00:06:45.315 --> 00:06:52.812
This is the fundamental reason why Pi mining doesn't consume the level of energy required by traditional mining of cryptocurrency.
00:06:52.812 --> 00:07:04.817
At the same time, it's also allowing mobile miners to contribute to the blockchain without getting with obstruction also from the complications of the technical aspect of blockchain.
00:07:05.545 --> 00:07:12.930
So I have five friends and I onboard them to the Pi network as part of my trust graph, to like, send them a link to the app.
00:07:12.930 --> 00:07:17.836
They download the app and they hit the button to run to contribute resources.
00:07:17.836 --> 00:07:21.213
How is the trust verified?
00:07:21.213 --> 00:07:25.254
I guess another way asks is like how would you game the system and how do you prevent that?
00:07:25.254 --> 00:07:29.913
So what is trust actually mean and how do you, at a scale?
00:07:29.913 --> 00:07:40.295
I kind of see it already If everyone's trust circles 30 people, that's still not big enough to be like the billions of people they can't possibly collude to corrupt the chain.
00:07:40.295 --> 00:07:43.752
I'm trying to wrap my head around, like what are the risks and tradeoffs?
00:07:43.752 --> 00:07:45.136
And like how does it actually work?
00:07:45.136 --> 00:07:46.550
How does the trust actually work?
00:07:47.305 --> 00:07:49.673
Yeah, I can try to explain intuitively how this works.
00:07:49.673 --> 00:08:01.050
First of all, I want to clarify that the blockchain consensus algorithm is running on computer nodes and we'll have tens of thousands of these computer nodes already, even just on our testnet.
00:08:01.050 --> 00:08:07.057
So comparing the testnet of Pi with other mainets is a few or maybe orders of magnitude even bigger.
00:08:07.057 --> 00:08:10.149
Now the mobile miners.
00:08:10.149 --> 00:08:14.038
What they are contributing is those connections that you mentioned, the trust.
00:08:14.038 --> 00:08:21.096
So intuitively this helps isolate any potential.
00:08:21.096 --> 00:08:23.038
It's called Sibyl attackers.
00:08:23.384 --> 00:08:29.329
Sibyl attackers when someone is creating fake accounts to pretend he's more than one people on the network.
00:08:30.105 --> 00:08:47.073
So think of it intuitively if me, you and Cendiao are the only people on Pi network and no one else yet and we point at each other because we pulled out on the phone each other and selected them and we say that these are the people we trust.
00:08:47.605 --> 00:08:56.355
Now if a fourth person comes along and creates, even if they create a thousand fake accounts, the best they can do is they can have those accounts pointing at each other.
00:08:56.355 --> 00:09:11.080
But in order for us, for the three of us right now, to trust that, those fake accounts, we would need to be convinced to change the trust pointers that we have from each other to those fake accounts, and why would we do that?
00:09:11.080 --> 00:09:15.033
So now imagine take this idea to millions of people.
00:09:15.033 --> 00:09:16.615
You will understand how it works.
00:09:16.615 --> 00:09:35.591
In its essence, it's similar to the original Google page rank algorithm, where you have web pages on the internet and the true web page of MIT is pointing to the true web page of Stanford and it doesn't really matter in the end of the day, it's the authority that's built from backlinks is kind of the idea.
00:09:35.991 --> 00:09:36.754
Yes, exactly.
00:09:36.933 --> 00:09:37.716
Exactly, exactly.
00:09:37.716 --> 00:09:42.554
So you could have fake blogs pretending to be Stanford, but no one cares.
00:09:43.424 --> 00:09:44.770
So let's use the web page example.
00:09:44.770 --> 00:09:49.897
Let's say I'm like a web page that's rank one on like a high traffic search.
00:09:49.897 --> 00:09:52.716
I have a lot of weight because I have a lot of trust.
00:09:52.716 --> 00:09:56.693
Like I have a thousand people pointing to me and you know those people are not fake accounts.
00:09:56.693 --> 00:10:01.113
Does that mean I'm mind more of the currency because I have more?
00:10:01.113 --> 00:10:03.664
Is it like proof of stake, kind of like that, or how does that work?
00:10:04.307 --> 00:10:11.508
No, we didn't want to make it on the plutocratic side, so the mining rate is standard across everyone.
00:10:11.508 --> 00:10:15.085
There are certain bonuses depending on different contributions.
00:10:16.269 --> 00:10:36.674
Basically the transparv give rise to the better formation of the corons, of the nodes, and the corons are basically a subset of the whole node network within which the nodes are messaging each other in terms of voting whether a transaction is true or not, and each time the corons are dynamically formed, so it's not just always that set of nodes.
00:10:36.674 --> 00:10:54.465
That's why it's to some extent more decentralized in a way, because it's a dynamic, corons is formed independently and within the forum, nodes message each other and reach consensus and the algorithm basically can ensure a finality to this transaction and get recorded on the ledger.
00:10:55.126 --> 00:10:59.100
And so you mentioned that you have 10,000 of these nodes.
00:10:59.100 --> 00:11:00.866
Is that 10,000 people with their phones?
00:11:00.866 --> 00:11:03.720
That was my understanding, but is it different than that?
00:11:03.720 --> 00:11:04.865
Are they actual computers?
00:11:04.865 --> 00:11:06.672
They're phones in the sense that you're a computer.
00:11:07.647 --> 00:11:19.187
Yeah, if you're referring to the blockchain running, to the devices that are running the consensus algorithm to produce blocks, these devices are only computers at the moment, not phones.
00:11:19.187 --> 00:11:26.471
We don't think that it would make sense for phones to be doing this kind of job and in fact, I mentioned that there are tens of thousands.
00:11:26.471 --> 00:11:37.721
I need to look a little more into giving you a more authoritative answer of how many of those we have, but some unofficial survey we did recently gave us more than 90,000 nodes on the network.
00:11:37.721 --> 00:11:39.046
These are the computer nodes.
00:11:39.245 --> 00:11:42.215
Yeah, and that's just like laptops, like anybody's laptop could.
00:11:42.946 --> 00:11:54.017
Yes, yes, so that essentially, if you look at this large number, even on just on the test net, it makes pi network one of the largest distributed systems on the planet.
00:11:54.017 --> 00:11:59.466
Not just a blockchain distributed system, any system that doesn't have a essentially centralized server.
00:11:59.466 --> 00:12:03.817
There's a lot of different kinds like file sharing, including distributed system.
00:12:04.206 --> 00:12:05.231
And so you have a test net.
00:12:05.231 --> 00:12:06.418
You haven't launched mainnet yet.
00:12:06.418 --> 00:12:09.892
What's sort of the status of where you are in building, building all this out?
00:12:10.664 --> 00:12:11.827
Our mainnet is live.
00:12:11.827 --> 00:12:13.150
We launched the mainnet.
00:12:13.150 --> 00:12:18.410
This goes to also your just now, your question about what we are different from other blockchains.
00:12:18.410 --> 00:12:21.076
We are taking very non consensus type of approach.
00:12:21.076 --> 00:12:27.905
Our mainnet is live and we actually created a special period is called enclose the network period.
00:12:28.366 --> 00:12:38.474
This is a special phase inside our mainnet where the mainnet is live but it artificially put a firewall against any external connectivity.
00:12:38.955 --> 00:12:48.429
This is to ensure that we can focus on building utilities within our ecosystem and we believe their utilities can be built in the enclosed environment.
00:12:48.429 --> 00:13:05.871
Of course, recognizing there are certain utility requires external connectivity, but we want to focus on building utilities within this enclosed phase in order to get the utility based ecosystem more mature before we open up to a open network where the firewall will be removed.
00:13:05.871 --> 00:13:12.297
In addition, during this phase, as you know, our network is not just a few thousand people or participants.
00:13:12.297 --> 00:13:14.566
We have millions of pioneers all over the world.
00:13:14.566 --> 00:13:26.628
So in order to onboard them, these millions, all into the network, it makes sense and more fair for majority of the network migrate to the mainnet in the enclosed environment before opening up.
00:13:26.628 --> 00:13:37.971
This is also another goal of the enclosed network, in addition to creating utility within the enclosed system, and this is also, you know, the answer to your question how is it so different from other crypto projects?
00:13:37.971 --> 00:13:40.817
I think this is an innovative phase we created.
00:13:41.125 --> 00:13:42.312
Yeah, it's just kind of gated.
00:13:42.312 --> 00:13:47.032
I mean you let a bunch of people sign up and then you sort of gate the mainnet access.
00:13:47.032 --> 00:13:54.106
It's permissioned right now, but you will be an open, permissionless chain once you feel like you've kind of made it out of this period and you have enough utility.
00:13:54.668 --> 00:14:01.754
Yeah, during this period, as we mentioned earlier, there is more than 45 million engaged members on Pi network.
00:14:01.754 --> 00:14:02.275
Right now.
00:14:02.275 --> 00:14:03.445
We call them miners.
00:14:03.445 --> 00:14:09.410
We are in the phase of completing, accomplishing KYC for them and transitioning them to the mainnet.
00:14:09.410 --> 00:14:11.923
The mainnet you see on the Block Explorer is the real mainnet.
00:14:11.923 --> 00:14:14.211
That will will continue when it's open.
00:14:14.211 --> 00:14:20.190
Right now, with KYC over 5 million people, and that's one of the goals to to make the migration.
00:14:20.490 --> 00:14:25.634
Yeah, this choice of this strategy is also based on price philosophy of inclusivity, right.
00:14:25.634 --> 00:14:33.797
Our requirement of KYC is also making sure that all corners of the world regions are able to KYC and get on to our mainnet.
00:14:33.797 --> 00:14:36.253
This period supports this process.
00:14:36.916 --> 00:14:37.961
I have so many questions.
00:14:37.961 --> 00:14:41.143
Just to take a step back, the utility you're building.
00:14:41.143 --> 00:14:49.559
Can you give me examples of what things you're building on top of Pi network and the examples plus the impact?
00:14:49.559 --> 00:14:58.039
You've obviously prioritized some things that are gating the launch of the permissionless network and so I'm kind of curious like what are things and what is the impact?
00:14:58.039 --> 00:15:02.003
You know, once you have these things, why do you need them to wait to be permissionless?
00:15:02.664 --> 00:15:08.398
Yeah, so utility is decentralized efforts from the whole community, not just the core team.
00:15:08.398 --> 00:15:19.378
Of course, we play a big role inside that by providing the infrastructure that facilitates the decentralized efforts, such as providing the platform, the SDK and developer tools.
00:15:19.378 --> 00:15:33.047
However, the actual building and the holding on the real, true utility for human to solve human needs is a completely a collective effort from the community builders and also community users of those apps.
00:15:33.047 --> 00:15:38.225
We have ourselves built some apps, for example, just now I already mentioned the KYC app.
00:15:38.225 --> 00:16:01.153
The KYC app because, also following accessibility, we did an outsource to a third party, which usually charged at least $1 for doing a check right, so that actually we developed a native solution that not only solved the scalability and also wide distribution of the geographic locations, but also it doesn't require people to pay out of pocket cost.
00:16:01.875 --> 00:16:17.538
Actually, people, pioneers, actually pay high cryptocurrency for the labor or the work down by the crowdsourced human validators within the community to perfecting the validation process where the AI or machine automation lacks.
00:16:17.538 --> 00:16:28.195
Ai advance a lot, of course, but for identity verification there are cases that still needs human touch and that human touch was provided by the community itself.
00:16:28.195 --> 00:16:36.337
So actually, pioneers are working as validators, actually making pie from the pioneers who want to verify their identity.
00:16:36.337 --> 00:16:50.929
So this is a true utility using pie meaning that the pie is used to facilitate transaction between the labor of the validator, work of the validator and the result in actual substance, which is whether someone is verified or not.
00:16:51.171 --> 00:16:53.416
So you guys built a custom KYC solution.
00:16:53.996 --> 00:16:55.147
Yes, yes, we did.
00:16:55.147 --> 00:17:04.353
We have to, because even the market providers don't necessarily provide KYC in, for example, regions that are really small or have a smaller market.
00:17:04.353 --> 00:17:14.233
Because most of the KYC providers are profit driven, building the infrastructure for a specific small region really cost a lot for those businesses.
00:17:14.233 --> 00:17:22.154
But for pie, in order to really achieve inclusivity, we have to provide KYC solution to all regions where our pioneers exist.
00:17:22.154 --> 00:17:33.250
So we created a design innovatively, this design that's scalable to cover all geolocations while at the same time, not costing out of pocket.
00:17:34.294 --> 00:17:44.116
So this is super interesting to me because and just for people listening KYC stands for Know your Customer and it's a really common thing you have to do in this space like anytime, just for like a lot of regulatory reasons.
00:17:44.116 --> 00:17:55.637
It's the best practice to KYC folks for things like grants, programs and kind of anytime you're dealing with tokens you're probably KYC'ing somebody, especially if it's a permission chain, like this is right now.
00:17:55.637 --> 00:18:00.330
So I see why you're having to do it, but building a totally custom one.
00:18:00.330 --> 00:18:08.678
That's a huge effort I've actually built, like integrated with providers multiple times to automate KYC for things like grant programs.
00:18:08.678 --> 00:18:14.285
They're checking OFAC databases, they're checking a whole bunch of different things to make sure that.
00:18:15.086 --> 00:18:22.776
I mean, it depends on the level of KYC you're trying to do, but making sure you're not on a list of countries where you're just not allowed to do business, like North Korea and stuff.
00:18:22.776 --> 00:18:31.291
What is the process under the hood, again, and what is running there in the app and how do people verify identity, especially this manual process?
00:18:31.291 --> 00:18:33.537
It sounds like with pioneers who are doing the work.
00:18:33.537 --> 00:18:34.628
How does it work?
00:18:34.628 --> 00:18:35.654
What are they looking into?
00:18:35.654 --> 00:18:37.525
What's automated, what's not?
00:18:37.525 --> 00:18:39.971
I'm just very curious to hear more about that.
00:18:40.733 --> 00:18:45.547
Well, it starts as a typical KYC solution, what you would expect.
00:18:45.547 --> 00:18:57.759
So you pull your phone, you have to show liveness, turn your head, respond to certain prompts, you have to show your ID, and the ID is captured and then AI is reading it.
00:18:57.759 --> 00:19:03.766
You have to fill out certain information, which is pretty standard stuff that all the KYC solutions do.
00:19:03.766 --> 00:19:11.347
We have a back end layer which is processing all those things automatically, as much as it can and as expected.
00:19:11.347 --> 00:19:20.018
There are some cases where they in certain questions that the AI has or is uncertain about, and those questions need to be answered.
00:19:20.018 --> 00:19:22.385
Every KYC solution has to answer them with humans.
00:19:22.385 --> 00:19:36.258
So what we're doing at Pi is that we reward existing, selected, trustworthy KYC already KYC members of the Pi network to answer those questions.
00:19:36.759 --> 00:19:45.934
We also had to add an additional layer of security on this so that what they see is not the raw data of what someone updated.
00:19:46.095 --> 00:20:06.942
So, for example, if someone were to see, to want to verify the face of someone on an ID versus whatever we got from a selfie picture that they get, then our software is cutting out only the picture from the ID, is cutting out the picture from the selfie, putting the two together and asking a validator to say are these two pictures the same person?
00:20:07.797 --> 00:20:10.998
Another use case, and there's multiple of them, but it will be.
00:20:10.998 --> 00:20:17.656
The last example I give is that if you need to ask certain question about an ID to a human, we are.
00:20:17.656 --> 00:20:29.862
The software is covering with black reduction boxes all the information on the ID, that all the text that is not supposed to be seen, and it's also cutting out the picture.
00:20:29.862 --> 00:20:35.661
So when you're showing an ID, it's pretty much fully anonymized, having, like, the picture is missing.
00:20:35.661 --> 00:20:36.964
The data is covered.
00:20:36.964 --> 00:20:39.642
It says California driving license.
00:20:39.642 --> 00:20:47.467
That is not covered and then possibly the question is is this, does this look like a real California driving license, for example?
00:20:47.467 --> 00:20:54.785
And then the specific question that a human needed to answer can be answered while trying to preserve privacy and security.
00:20:54.785 --> 00:21:02.994
Then, after this whole process completes, we have to do all the compliance requirements, like you mentioned, ofac and other things.
00:21:03.858 --> 00:21:09.394
Yeah, it's packed into this one app that basically follows the guidelines of law and regulations.
00:21:09.394 --> 00:21:13.469
This is not just the work that we do just for Pi Network.
00:21:13.469 --> 00:21:19.394
The whole community actually have this produced this large scale KYC to social network.
00:21:19.394 --> 00:21:38.760
It's actually a contribution from Pi Network from all of us, including pioneers to the world because, as the industry towards getting more and more into the compliance, having a large enough social network that is KYC make the world ready to plug in true Web3 tools or services more easily.
00:21:38.760 --> 00:21:50.674
It also facilitated more easier onboarding of future other chains or other blockchain or financial services or Web3 type of applications that has a financial aspect or element inside.
00:21:51.820 --> 00:22:03.394
This is something that why we need to actually build in-house kind of solution, because it's important for our philosophy of accessibility, but also it actually create a great contribution.
00:22:03.394 --> 00:22:15.075
I mean there was in Web2, facebook's innovation was using real identity, real name in the social network and that break through the last few decades, the fame and the boom of Facebook.
00:22:15.075 --> 00:22:20.047
The next phase for Web3, web3 means ownership right People are being able to own.
00:22:20.047 --> 00:22:22.954
When it touches ownership, there is the need of KYC.
00:22:22.954 --> 00:22:32.263
That's why we're building this huge network, not just large but actually actually more compliant and, towards the future, that easy to plug in for even other services.
00:22:33.615 --> 00:22:35.742
That makes a ton of sense to me and I agree with you.
00:22:35.742 --> 00:22:50.983
Like, if you guys succeed in getting a high quality KYC done, that other people trust other networks, other people who might want to use the like, interact with that network of people, then you've created something pretty valuable for sure.
00:22:50.983 --> 00:22:56.843
What other kinds of applications are going to run or are already running on PyNetwork?
00:22:56.843 --> 00:22:59.755
Some chains are purpose-built or better for other things.
00:22:59.755 --> 00:23:04.362
Then they have unique things that they might be good at, whereas they might not be good at other things.
00:23:04.362 --> 00:23:13.785
Is it a general purpose, l1, or do you think there are some applications that are more appealing to be built on top of the network than, say, something other applications that might be a better fit somewhere else?
00:23:14.576 --> 00:23:21.943
Any type of blockchain application that you know from other networks can also run on Py.
00:23:21.943 --> 00:23:24.663
There's no restrictions there.
00:23:24.663 --> 00:23:43.506
We focus also on applications that traditionally have not been popular on blockchains, and I'm talking about applications that are very popular even in Web 2, the way that the world has been working until now.
00:23:43.506 --> 00:24:03.282
We had a few, a couple of hackathons, and we have some programs inside Py for people to collaborate and create apps, and we've had a few thousand developers engage, producing hundreds of apps and tens of thousands of pioneers giving them feedback on these ideas.
00:24:03.282 --> 00:24:12.923
So through these they have started building applications of various kinds like, for example, one vertical is remote labor.
00:24:12.923 --> 00:24:35.905
One example is the KYC app that we build, but another example is apps that are similar to Fiverr or Upwork, where a pioneer can provide some work and in exchange, get paid in Py from someone else, and that work could be from something simple as creating a piece of art to something more complex than this.
00:24:36.635 --> 00:24:45.954
Another vertical of applications that we see we actually have several marketplaces on Py and these marketplaces each one has a slightly different angle.
00:24:45.954 --> 00:24:51.220
Some marketplaces are focusing on user-to-user good exchanges, like eBay.
00:24:51.220 --> 00:25:04.161
Others are focusing on rallying up and connecting merchants around the world, and some are either even creating a decentralized network of logistics.
00:25:04.161 --> 00:25:16.561
So, because Py is in enclosed domain at period right now and you can't use Py to use FedEx or something like this, people have created this network of individuals who can help with delivery of goods.
00:25:16.561 --> 00:25:19.584
Other vertical is crowdsourcing tools.
00:25:19.584 --> 00:25:35.659
So, for example, there is an app for creating polls and someone who wants to get some feedback from community and they don't have a community, they can post a poll there and reward people in Py for answering those questions that they may have.
00:25:35.659 --> 00:25:41.483
There is other apps such as quote production, funny quotes, good quotes, quality quotes.
00:25:41.483 --> 00:25:44.634
And there's, of course, games that are using Pi.
00:25:44.634 --> 00:25:47.354
For example, when you lose, you spend some Pi to continue.
00:25:47.354 --> 00:25:53.852
Or we use Pi to buy virtual goods, cats and fertilizer or whatever the game has with Pi.
00:25:54.724 --> 00:26:20.073
Yeah, so basically overall, the application, in addition to the traditional like blockchain-based kind of application, like DeFi related, which Pi is capable of providing, especially after the open mainnet, we are also emphasizing utility or apps that facilitate access to true goods and services type of apps, and in addition to that utility includes also entertainment or social life, like specifically on the social side applications.
00:26:20.204 --> 00:26:35.309
There are a bunch also coming from the community developers, but at the same time we also are innovators of social applications and we believe that the true Web3 social apps are not just moving from the Web2 and putting things on chain and then become Web3.
00:26:35.424 --> 00:27:01.288
Of course that's one aspect, like the ownership aspect, like store things on chain, but we see far beyond that in the sense that we really want to build Web3 applications that actually make improvement of the flaws of Web2, for example, authenticity, the fake news, misinformation, disinformation, for example, information silo, information overload how do you find high signal information from a crowd of noises Like these type of things?
00:27:01.328 --> 00:27:24.691
We think, with the tool of cryptocurrency and token economics, designing the token economics of using cryptocurrency are able to facilitate the incentive and disincentive inside the social applications to regulate or moderate the behavior online and ultimately achieving better content better curated content and better signal content At the same time, make people more accountable in their behavior.
00:27:24.691 --> 00:27:28.030
And actually this is not something that we just the only idea.
00:27:28.030 --> 00:27:38.593
This idea has been with Pi since the last three or four years, but actually recently because our ecosystem reached the point that we're actually about to launch some of our applications.
00:27:38.593 --> 00:27:44.049
That is an instantiation of such ideas I just described, so we're actually excited.
00:27:44.049 --> 00:27:48.734
Very soon, some of these apps of ours will actually be released.
00:27:49.325 --> 00:27:56.175
And I want to mention that one of the things we can actually do that at Pi is because of the large number of people on the network.
00:27:56.175 --> 00:28:12.112
So if certain social networking apps, or certain apps that we are describing just now, they only start making sense when you have a large number of people and the utility is much lower when you haven't reached the critical mass.
00:28:12.345 --> 00:28:13.872
Yeah, I was going to point that same thing out.
00:28:13.872 --> 00:28:22.453
You can't have a Fiverr clone on chain without a couple million people, because then you just don't have diversity enough to get the tasks.
00:28:22.453 --> 00:28:23.609
It's the chicken and egg problem.
00:00:04.427 --> 00:00:08.013
00:00:08.013 --> 00:00:13.529
00:00:19.129 --> 00:00:25.888
00:00:25.888 --> 00:00:27.405
00:00:27.405 --> 00:00:38.131
00:00:38.131 --> 00:00:45.003
00:00:45.003 --> 00:00:45.905
00:00:45.905 --> 00:00:46.545
00:00:47.067 --> 00:00:48.470
00:00:48.470 --> 00:00:49.212
00:00:49.619 --> 00:00:52.209
00:00:52.209 --> 00:00:53.603
00:00:53.603 --> 00:00:55.284
00:00:55.284 --> 00:00:58.307
00:00:59.179 --> 00:01:03.692
00:01:04.340 --> 00:01:20.730
00:01:20.730 --> 00:01:23.123
00:01:23.123 --> 00:01:43.805
00:01:43.805 --> 00:01:49.871
00:01:49.871 --> 00:01:52.507
00:01:52.507 --> 00:02:06.771
00:02:06.771 --> 00:02:15.687
00:02:15.687 --> 00:02:27.790
00:02:28.939 --> 00:02:35.469
00:02:35.469 --> 00:02:41.693
00:02:41.693 --> 00:02:51.532
00:02:51.532 --> 00:02:59.485
00:02:59.485 --> 00:03:16.524
00:03:17.086 --> 00:03:18.969
00:03:18.969 --> 00:03:27.150
00:03:27.150 --> 00:03:33.586
00:03:33.586 --> 00:03:35.224
00:03:35.224 --> 00:03:42.931
00:03:42.931 --> 00:03:53.131
00:03:54.282 --> 00:03:57.069
00:03:57.069 --> 00:04:06.231
00:04:06.231 --> 00:04:24.829
00:04:24.829 --> 00:04:26.786
00:04:26.786 --> 00:04:29.668
00:04:29.668 --> 00:04:52.096
00:04:52.096 --> 00:04:53.442
00:04:54.225 --> 00:04:58.990
00:04:58.990 --> 00:05:06.836
00:05:06.836 --> 00:05:10.410
00:05:10.410 --> 00:05:20.935
00:05:20.935 --> 00:05:22.449
00:05:22.449 --> 00:05:24.839
00:05:24.839 --> 00:05:26.428
00:05:26.904 --> 00:05:31.627
00:05:31.627 --> 00:05:35.036
00:05:35.036 --> 00:05:37.485
00:05:37.485 --> 00:05:41.475
00:05:41.475 --> 00:05:43.730
00:05:43.730 --> 00:05:46.874
00:05:46.874 --> 00:05:48.230
00:05:48.230 --> 00:05:54.918
00:05:54.918 --> 00:05:57.100
00:05:57.100 --> 00:06:00.374
00:06:01.125 --> 00:06:04.214
00:06:04.214 --> 00:06:09.697
00:06:09.697 --> 00:06:17.192
00:06:17.192 --> 00:06:27.136
00:06:27.136 --> 00:06:45.315
00:06:45.315 --> 00:06:52.812
00:06:52.812 --> 00:07:04.817
00:07:05.545 --> 00:07:12.930
00:07:12.930 --> 00:07:17.836
00:07:17.836 --> 00:07:21.213
00:07:21.213 --> 00:07:25.254
00:07:25.254 --> 00:07:29.913
00:07:29.913 --> 00:07:40.295
00:07:40.295 --> 00:07:43.752
00:07:43.752 --> 00:07:45.136
00:07:45.136 --> 00:07:46.550
00:07:47.305 --> 00:07:49.673
00:07:49.673 --> 00:08:01.050
00:08:01.050 --> 00:08:07.057
00:08:07.057 --> 00:08:10.149
00:08:10.149 --> 00:08:14.038
00:08:14.038 --> 00:08:21.096
00:08:21.096 --> 00:08:23.038
00:08:23.384 --> 00:08:29.329
00:08:30.105 --> 00:08:47.073
00:08:47.605 --> 00:08:56.355
00:08:56.355 --> 00:09:11.080
00:09:11.080 --> 00:09:15.033
00:09:15.033 --> 00:09:16.615
00:09:16.615 --> 00:09:35.591
00:09:35.991 --> 00:09:36.754
00:09:36.933 --> 00:09:37.716
00:09:37.716 --> 00:09:42.554
00:09:43.424 --> 00:09:44.770
00:09:44.770 --> 00:09:49.897
00:09:49.897 --> 00:09:52.716
00:09:52.716 --> 00:09:56.693
00:09:56.693 --> 00:10:01.113
00:10:01.113 --> 00:10:03.664
00:10:04.307 --> 00:10:11.508
00:10:11.508 --> 00:10:15.085
00:10:16.269 --> 00:10:36.674
00:10:36.674 --> 00:10:54.465
00:10:55.126 --> 00:10:59.100
00:10:59.100 --> 00:11:00.866
00:11:00.866 --> 00:11:03.720
00:11:03.720 --> 00:11:04.865
00:11:04.865 --> 00:11:06.672
00:11:07.647 --> 00:11:19.187
00:11:19.187 --> 00:11:26.471
00:11:26.471 --> 00:11:37.721
00:11:37.721 --> 00:11:39.046
00:11:39.245 --> 00:11:42.215
00:11:42.946 --> 00:11:54.017
00:11:54.017 --> 00:11:59.466
00:11:59.466 --> 00:12:03.817
00:12:04.206 --> 00:12:05.231
00:12:05.231 --> 00:12:06.418
00:12:06.418 --> 00:12:09.892
00:12:10.664 --> 00:12:11.827
00:12:11.827 --> 00:12:13.150
00:12:13.150 --> 00:12:18.410
00:12:18.410 --> 00:12:21.076
00:12:21.076 --> 00:12:27.905
00:12:28.366 --> 00:12:38.474
00:12:38.955 --> 00:12:48.429
00:12:48.429 --> 00:13:05.871
00:13:05.871 --> 00:13:12.297
00:13:12.297 --> 00:13:14.566
00:13:14.566 --> 00:13:26.628
00:13:26.628 --> 00:13:37.971
00:13:37.971 --> 00:13:40.817
00:13:41.125 --> 00:13:42.312
00:13:42.312 --> 00:13:47.032
00:13:47.032 --> 00:13:54.106
00:13:54.668 --> 00:14:01.754
00:14:01.754 --> 00:14:02.275
00:14:02.275 --> 00:14:03.445
00:14:03.445 --> 00:14:09.410
00:14:09.410 --> 00:14:11.923
00:14:11.923 --> 00:14:14.211
00:14:14.211 --> 00:14:20.190
00:14:20.490 --> 00:14:25.634
00:14:25.634 --> 00:14:33.797
00:14:33.797 --> 00:14:36.253
00:14:36.916 --> 00:14:37.961
00:14:37.961 --> 00:14:41.143
00:14:41.143 --> 00:14:49.559
00:14:49.559 --> 00:14:58.039
00:14:58.039 --> 00:15:02.003
00:15:02.664 --> 00:15:08.398
00:15:08.398 --> 00:15:19.378
00:15:19.378 --> 00:15:33.047
00:15:33.047 --> 00:15:38.225
00:15:38.225 --> 00:16:01.153
00:16:01.875 --> 00:16:17.538
00:16:17.538 --> 00:16:28.195
00:16:28.195 --> 00:16:36.337
00:16:36.337 --> 00:16:50.929
00:16:51.171 --> 00:16:53.416
00:16:53.996 --> 00:16:55.147
00:16:55.147 --> 00:17:04.353
00:17:04.353 --> 00:17:14.233
00:17:14.233 --> 00:17:22.154
00:17:22.154 --> 00:17:33.250
00:17:34.294 --> 00:17:44.116
00:17:44.116 --> 00:17:55.637
00:17:55.637 --> 00:18:00.330
00:18:00.330 --> 00:18:08.678
00:18:08.678 --> 00:18:14.285
00:18:15.086 --> 00:18:22.776
00:18:22.776 --> 00:18:31.291
00:18:31.291 --> 00:18:33.537
00:18:33.537 --> 00:18:34.628
00:18:34.628 --> 00:18:35.654
00:18:35.654 --> 00:18:37.525
00:18:37.525 --> 00:18:39.971
00:18:40.733 --> 00:18:45.547
00:18:45.547 --> 00:18:57.759
00:18:57.759 --> 00:19:03.766
00:19:03.766 --> 00:19:11.347
00:19:11.347 --> 00:19:20.018
00:19:20.018 --> 00:19:22.385
00:19:22.385 --> 00:19:36.258
00:19:36.759 --> 00:19:45.934
00:19:46.095 --> 00:20:06.942
00:20:07.797 --> 00:20:10.998
00:20:10.998 --> 00:20:17.656
00:20:17.656 --> 00:20:29.862
00:20:29.862 --> 00:20:35.661
00:20:35.661 --> 00:20:36.964
00:20:36.964 --> 00:20:39.642
00:20:39.642 --> 00:20:47.467
00:20:47.467 --> 00:20:54.785
00:20:54.785 --> 00:21:02.994
00:21:03.858 --> 00:21:09.394
00:21:09.394 --> 00:21:13.469
00:21:13.469 --> 00:21:19.394
00:21:19.394 --> 00:21:38.760
00:21:38.760 --> 00:21:50.674
00:21:51.820 --> 00:22:03.394
00:22:03.394 --> 00:22:15.075
00:22:15.075 --> 00:22:20.047
00:22:20.047 --> 00:22:22.954
00:22:22.954 --> 00:22:32.263
00:22:33.615 --> 00:22:35.742
00:22:35.742 --> 00:22:50.983
00:22:50.983 --> 00:22:56.843
00:22:56.843 --> 00:22:59.755
00:22:59.755 --> 00:23:04.362
00:23:04.362 --> 00:23:13.785
00:23:14.576 --> 00:23:21.943
00:23:21.943 --> 00:23:24.663
00:23:24.663 --> 00:23:43.506
00:23:43.506 --> 00:24:03.282
00:24:03.282 --> 00:24:12.923
00:24:12.923 --> 00:24:35.905
00:24:36.635 --> 00:24:45.954
00:24:45.954 --> 00:24:51.220
00:24:51.220 --> 00:25:04.161
00:25:04.161 --> 00:25:16.561
00:25:16.561 --> 00:25:19.584
00:25:19.584 --> 00:25:35.659
00:25:35.659 --> 00:25:41.483
00:25:41.483 --> 00:25:44.634
00:25:44.634 --> 00:25:47.354
00:25:47.354 --> 00:25:53.852
00:25:54.724 --> 00:26:20.073
00:26:20.204 --> 00:26:35.309
00:26:35.424 --> 00:27:01.288
00:27:01.328 --> 00:27:24.691
00:27:24.691 --> 00:27:28.030
00:27:28.030 --> 00:27:38.593
00:27:38.593 --> 00:27:44.049
00:27:44.049 --> 00:27:48.734
00:27:49.325 --> 00:27:56.175
00:27:56.175 --> 00:28:12.112
00:28:12.345 --> 00:28:13.872
00:28:13.872 --> 00:28:22.453
00:28:22.453 --> 00:28:23.609