Atos introduces ZKPass, a private data verification protocol built on multi-party computation and zero-knowledge proofs. He provides an overview of his background and the purpose of the talk.

Introduction to ZKPass

Atos discusses ZKPass's reputation, seed round funding, collaborations, and the increasing importance of private data.

ZKPass Reputation and Traction

Atos explains the significance of private data, its increasing volume, and the competitive landscape of projects working with data.

Importance of Private Data

Atos presents ZKPass as a pioneer in off-chain private data verification and proposes a solution that breaks free from API limitations.

ZKPass Solution and Proposal

Atos elaborates on ZKPass's ability to verify identities from various data sources and explains the data retrieval and verification process from a builder's perspective.

Verification of Identities and Data Retrieval

Atos provides a technical overview of ZKPass SDK, including the define, retrieve, and verify steps, as well as the protocol's abstraction for builders.

Technical Overview of ZKPass SDK

Atos attempts to demonstrate the ZKPass Dev Center, explaining the process of creating a project, adding schemas, and checking the schema.

Live Demo of ZKPass Dev Center

- Atos from ZKPass introduces their private data verification protocol
- They have received funding from prominent VCs and have significant traction
- They focus on private data due to its increasing importance and the abundance of private data generated
- They are pioneers in off-chain private data verification
- Their solution is compatible with all existing infrastructure in Web2
- They work in 3 simple steps: define, retrieve, and verify
- Their SDK abstracts the technicalities of the system for builders
- They provide a live demo of their protocol from the Dev Center

- The video is a demonstration of the Dev Center
- It shows how to connect your wallet and create a project
- Creating a project gives you an app ID (API key) and allows you to add pre-built or custom schemas
- The schemas are used to verify data, such as proving a Binance balance is over a certain amount
- There are technical difficulties during the live demo, but viewers are encouraged to ask developers for help and add the Telegram channel

This is a live demo of how zkPass' SDK can be used in practice. it showcases an example of how a customized schema can be made and how the private data is fetched and parsed into a zkProof using our SDK, and also to answer any questions or receive feedback from builders. 

APPLICATIONS FOR ETHDenver 2024: #YearOfTheSpork ARE OPEN


APPLY NOW
https://ethdenver.com/apply

Hello, my name is Atos and we're from ZKPass.

So, ZKPass is a private data verification protocol that is built upon the foundations of multi-party computation and zero-knowledge proofs.

And that provides the apps with the ability to use private data from off-chain data sources as a dependency for their code.

I'm born, lived, and studied in Australia.

I've done some entrepreneurial stuff back in university.

And fresh off my education, I actually started my career at traditional banking sector.

And then I turned into Tencent, and now in ZKPass.

So the main purpose of this talk really is to just have an in-person explanation of how our SDK works as we've posted our bounty for ETH Denver.

So this workshop would be less thought-provoking compared to other talks here.

So what we'll do is to mainly talk about a few parts.

First of all, it's what CK pass does, and then we get into the technical nitty gritties of the entire product flow from a builder's perspective.

And then finally, if we have time, I'll try to get into a live demo.

But if we don't have time, There are docs that we have and that are still pretty self-explanatory.

And we have a Telegram channel for builders that are interested to build on us, where all the questions can be directly answered.

Feel free to scan it to get into the Telegram channel.

So most of our reputation came from us winning the Binance Launchpad.

So let me give you guys a really quick update of how we're doing.

So we closed our round last year with a 2.5 million seed round.

We were proudly backed by Sequoia, OKEx, Binance, and a few other prominent VCs in the industry.

And we have fairly nice traction, because we launched our pre-alpha at the end of last year and had some pretty significant number of users.

We also collaborated with Linea and Binance Attestation Service for their Proof of Humanity campaign.

But we also have a lot of other big use cases down the line.

For example, Some of the ones are telecom companies from traditional web 2.0 industries.

So you guys might be wondering, why are we focused on private data?

And you can see the overall data sphere is increasing, and the percentage of private data is increasing.

So the reason for this is pretty obvious, as the private data is mostly customer data.

So with the increase of haptic devices that you have, every transaction, every interaction that you have on the internet could mean some sort of private data generated.

So since these sort of data is very easily generated, so there's much more private data than public data.

And the private data sphere projects to be 7 times larger than the public 1 by 2025.

So now let's look at the competitive landscape in terms of projects that are playing with data.

As you can see, there are prominent names in their respective places.

For example, the Chainlink, Super Oracles, Stripe, Fractal ID, Clique ID, Binance Attestation, Ethereum Attestation service, Gitcoin Passport, and all these.

But with off-chain private data, there's only a handful of projects that you might be able to name.

And we're definitely the pioneers in this realm.

So what we propose is a solution that is able to verify any data from any account in any website.

We're compatible with all existing infras in Web2, so we're able to break Oracles free from the limitations of API.

Oracle still relies on APIs to grab and feed information from different applications.

So yeah, so just look at how many projects and how many products that were built using Chainlink and Super Oracles.

Now imagine that what they can do, we can do what they can do permissionlessly.

And that really leaves a lot of room of imagination for applications that can be built with our solutions.

So to better visualize this, let's try to look at the video for the Linear Voyage campaign, where we used Uber as a standard to prove your humanity.

I'll see if this can be So it's not it's not Okay fine So the demo is not available right now, but you can always look into it in YouTube.

But yes, so Uber, as a standard to prove your humanity, is really just the tip of the iceberg.

ZKPass is able to verify identities from a vast amount of data sources, such as government issues IDs, online credentials, health care data, gaming profiles, or online assets.

And so now let's figure out how everything works in a back end.

So in builder's perspective, ZK Pass works in 3 simple steps.

So going from define, you need to define the scope of data that you want from the user.

So what you got to do is first, you've got to register on the Dev Center that we have.

And then there is a schema validator which is sort of acting as like a plugin to validate that the schema does not have bugs.

So it doesn't tamper or look into any of the work you're doing.

And then you can also, after installing it, you would create a customized schema, or you could use schemas that we've already written.

Yeah, and then So when the user comes in and starts the minting process, the user will be redirected to the data source where the user logs in and starts the attestation process.

Then the protocol starts to run and then returns a proof that can be submitted on-chain.

And then so this submitting on-chain process is really just a storage, a way to store this proof.

So it can be also directly used to verify for your own project.

So within this step is what the magic really happens.

So the retrieval of private data and the verification process is conducted between the 3 parties, the ZCapass node, the user, and the data source.

So although the technicalities of our system is going to take a little too long to discuss in this workshop.

Our SDK carefully abstracts them away from the builder.

So if you're interested to know more on how our protocol works from behind the scenes, feel free to read our white paper on our website.

But essentially, what our SDK does is after you've defined the schema for the data you're retrieving, you would provide the schema to the protocol, and it would return a node address, node addresses which contains an allocator node and a validator node, and also hashes of these node addresses and then also a nullifier to prevent redundant duplicates that was generated, and also a task ID that was allocated that is used for the allocator to tell the user which validator that they have to interact with.

Then through the SDK, you can feed the hashes into the SDK verification function, and then it returns the address.

So if the prior and the latter 1 matches, the SVT is valid, or else it's not valid.

And first of all, you have to connect your wallet.

So Creating a project would give you a app ID, which is, you can view it as a API key.

The domain has to be the 1 that you're hosting with.

And then these 2 are just, it could be anything.

You OK, so Let's just assume we've created, because I think there's some issues with the network.

But let's just assume you've created the projects, you've registered a project.

In here, You can select Add Schema for the pre-built schemas.

And then you can also create your own schemas.

And this schema is essentially, so you take the JSON response.

For example, if you want to prove that your Binance balance has over a certain amount of dollars what you do is you would You would log in to your finance account and then And then there would be a There would be a QR code a char code.

And then after logging into it, you would go to the developer console, And then you would look into the network.

So you would see that when it loads, there is a API that feeds the power to this 1.

API that feeds To this 1 so There's my holdings And then you would use this to create a schema that you would insert in here.

So for the time being, I've already made changes to the schema.

So what this does is It takes the data that was asserted, 6 of them in total, and then calculates if the actual value is over $100.

And then also there's a code that proves that the person is you.

So there's supposed to be a category in here that allows you to choose different categories that your schema belongs to.

And then after you've done this, you would check the schema.

And then the schema would run its for the first time.

There's definitely like some technical difficulties here Maybe we'll try to resolve this after, but the live demo, I think, doesn't work now.

If you guys are building on this, definitely ask our devs on how this is going to be resolved.

But I think this is just this computer's problem.

I don't think it's the problem of the of the Protocol itself, so yeah, so thank you guys.


Speaker 0: Hello, my name is Atos and we're from ZKPass. So, ZKPass is a private data verification protocol that is built upon the foundations of multi-party computation and zero-knowledge proofs. And that provides the apps with the ability to use private data from off-chain data sources as a dependency for their code. So A little introduction about me. My name's Atos.

I'm born, lived, and studied in Australia. I've done some entrepreneurial stuff back in university. And fresh off my education, I actually started my career at traditional banking sector. And then I turned into Tencent, and now in ZKPass. So the main purpose of this talk really is to just have an in-person explanation of how our SDK works as we've posted our bounty for ETH Denver.

So this workshop would be less thought-provoking compared to other talks here. But it's more straightforward. So what we'll do is to mainly talk about a few parts. First of all, it's what CK pass does, and then we get into the technical nitty gritties of the entire product flow from a builder's perspective. And then finally, if we have time, I'll try to get into a live demo.

But if we don't have time, There are docs that we have and that are still pretty self-explanatory. And we have a Telegram channel for builders that are interested to build on us, where all the questions can be directly answered. So there's a QR code here. Feel free to scan it to get into the Telegram channel. So most of our reputation came from us winning the Binance Launchpad.

So let me give you guys a really quick update of how we're doing. So we closed our round last year with a 2.5 million seed round. We were proudly backed by Sequoia, OKEx, Binance, and a few other prominent VCs in the industry. And we have fairly nice traction, because we launched our pre-alpha at the end of last year and had some pretty significant number of users. We also collaborated with Linea and Binance Attestation Service for their Proof of Humanity campaign.

But we also have a lot of other big use cases down the line. For example, Some of the ones are telecom companies from traditional web 2.0 industries. So you guys might be wondering, why are we focused on private data? So let's look at a report from 2018. And you can see the overall data sphere is increasing, and the percentage of private data is increasing.

So the reason for this is pretty obvious, as the private data is mostly customer data. So with the increase of haptic devices that you have, every transaction, every interaction that you have on the internet could mean some sort of private data generated. So since these sort of data is very easily generated, so there's much more private data than public data. And the private data sphere projects to be 7 times larger than the public 1 by 2025. So now let's look at the competitive landscape in terms of projects that are playing with data.

As you can see, there are prominent names in their respective places. For example, the Chainlink, Super Oracles, Stripe, Fractal ID, Clique ID, Binance Attestation, Ethereum Attestation service, Gitcoin Passport, and all these. But with off-chain private data, there's only a handful of projects that you might be able to name. And we're definitely the pioneers in this realm. So what we propose is a solution that is able to verify any data from any account in any website.

We're compatible with all existing infras in Web2, so we're able to break Oracles free from the limitations of API. Oracle still relies on APIs to grab and feed information from different applications. So yeah, so just look at how many projects and how many products that were built using Chainlink and Super Oracles. Now imagine that what they can do, we can do what they can do permissionlessly. And that really leaves a lot of room of imagination for applications that can be built with our solutions.

So to better visualize this, let's try to look at the video for the Linear Voyage campaign, where we used Uber as a standard to prove your humanity. I'll see if this can be So it's not it's not Okay fine So the demo is not available right now, but you can always look into it in YouTube. We have a channel there. But yes, so Uber, as a standard to prove your humanity, is really just the tip of the iceberg. ZKPass is able to verify identities from a vast amount of data sources, such as government issues IDs, online credentials, health care data, gaming profiles, or online assets.

So we're able to work with RWAs as well. And so now let's figure out how everything works in a back end. So in builder's perspective, ZK Pass works in 3 simple steps. So it's define, retrieve, and verify. So going from define, you need to define the scope of data that you want from the user.

So what you got to do is first, you've got to register on the Dev Center that we have. And then there is a schema validator which is sort of acting as like a plugin to validate that the schema does not have bugs. So it doesn't tamper or look into any of the work you're doing. But yeah. And then you can also, after installing it, you would create a customized schema, or you could use schemas that we've already written.

Yeah, and then So when the user comes in and starts the minting process, the user will be redirected to the data source where the user logs in and starts the attestation process. Then the protocol starts to run and then returns a proof that can be submitted on-chain. And then so this submitting on-chain process is really just a storage, a way to store this proof. So it can be also directly used to verify for your own project. So within this step is what the magic really happens.

So the retrieval of private data and the verification process is conducted between the 3 parties, the ZCapass node, the user, and the data source. So although the technicalities of our system is going to take a little too long to discuss in this workshop. Our SDK carefully abstracts them away from the builder. So if you're interested to know more on how our protocol works from behind the scenes, feel free to read our white paper on our website. But essentially, what our SDK does is after you've defined the schema for the data you're retrieving, you would provide the schema to the protocol, and it would return a node address, node addresses which contains an allocator node and a validator node, and also hashes of these node addresses and then also a nullifier to prevent redundant duplicates that was generated, and also a task ID that was allocated that is used for the allocator to tell the user which validator that they have to interact with.

Then through the SDK, you can feed the hashes into the SDK verification function, and then it returns the address. So if the prior and the latter 1 matches, the SVT is valid, or else it's not valid. So yeah, that's how you prove it. So we do have time. I'm Going to put up a live demo.

So starting from a Dev Center. 1 second. Lagging a little bit. All right. So this is our Dev Center.

All right. This is our Dev Center. And first of all, you have to connect your wallet. And then you can create a project here. So Creating a project would give you a app ID, which is, you can view it as a API key.

And that. So you input the name and the domain. The domain has to be the 1 that you're hosting with. For example, let's put demo here. And then We're locally hosting it.

And then these 2 are just, it could be anything. So I'll just leave it. You OK, so Let's just assume we've created, because I think there's some issues with the network. But let's just assume you've created the projects, you've registered a project. In here, You can select Add Schema for the pre-built schemas.

And then you can also create your own schemas. And this schema is essentially, so you take the JSON response. For example, if you want to prove that your Binance balance has over a certain amount of dollars what you do is you would You would log in to your finance account and then And then there would be a There would be a QR code a char code. And then after logging into it, you would go to the developer console, And then you would look into the network. So you would see that when it loads, there is a API that feeds the power to this 1.

API that feeds To this 1 so There's my holdings And then you would use this to create a schema that you would insert in here. So for the time being, I've already made changes to the schema. Changes to the schema. So what this does is It takes the data that was asserted, 6 of them in total, and then calculates if the actual value is over $100. And then also there's a code that proves that the person is you.

Name, Finance balance. So there's supposed to be a category in here that allows you to choose different categories that your schema belongs to. And then after you've done this, you would check the schema. And then the schema would run its for the first time. I don't know why.

Yeah. Yeah. So after you've checked the loads. The loads Yeah, I'm sorry guys. There's definitely like some technical difficulties here Maybe we'll try to resolve this after, but the live demo, I think, doesn't work now.

Yeah. So add the Telegram channel and try it. If you guys are building on this, definitely ask our devs on how this is going to be resolved. But I think this is just this computer's problem. I don't think it's the problem of the of the Protocol itself, so yeah, so thank you guys.

Thank you for your time.

See all ETHDenver transcripts on Youtube

Fetching Offchain Private Data Using zkPass | Aetos Huo - zkPass