Ben Rubin

Yeah.

For proof of concept, I would start with just a set of smart contracts that is on an L2, basically on it. layer that is much cheaper on top of Ethereum where you can actually create this protocol, like just exist on Ethereum and without starting a whole new backend infrastructure. And I think you can actually POC it like that. You will have to be somebody who knows how to do an SDK and publish it.

For proof of concept, I would start with just a set of smart contracts that is on an L2, basically on it. layer that is much cheaper on top of Ethereum where you can actually create this protocol, like just exist on Ethereum and without starting a whole new backend infrastructure. And I think you can actually POC it like that. You will have to be somebody who knows how to do an SDK and publish it.

For proof of concept, I would start with just a set of smart contracts that is on an L2, basically on it. layer that is much cheaper on top of Ethereum where you can actually create this protocol, like just exist on Ethereum and without starting a whole new backend infrastructure. And I think you can actually POC it like that. You will have to be somebody who knows how to do an SDK and publish it.

But I think if you can build an SDK from A to Z and publish it, and curiosity around the Web3 space, I would build an SDK that essentially all it does, it helps other developers integrate it to the actions that users are doing on their clients, you know, on their Tinder or any other. And when an action happened verifiably locally, your SDK gets the kind of confirmation that it needs.

But I think if you can build an SDK from A to Z and publish it, and curiosity around the Web3 space, I would build an SDK that essentially all it does, it helps other developers integrate it to the actions that users are doing on their clients, you know, on their Tinder or any other. And when an action happened verifiably locally, your SDK gets the kind of confirmation that it needs.

But I think if you can build an SDK from A to Z and publish it, and curiosity around the Web3 space, I would build an SDK that essentially all it does, it helps other developers integrate it to the actions that users are doing on their clients, you know, on their Tinder or any other. And when an action happened verifiably locally, your SDK gets the kind of confirmation that it needs.

One of the interesting thing is integrating it with pass keys, right? You got pass keys on the phone. You can store locally in the local encrypted drawer of the iPhone that you can only open with your face. You can store there the key that allows for the signature for the local action, right? So you can actually...

One of the interesting thing is integrating it with pass keys, right? You got pass keys on the phone. You can store locally in the local encrypted drawer of the iPhone that you can only open with your face. You can store there the key that allows for the signature for the local action, right? So you can actually...

One of the interesting thing is integrating it with pass keys, right? You got pass keys on the phone. You can store locally in the local encrypted drawer of the iPhone that you can only open with your face. You can store there the key that allows for the signature for the local action, right? So you can actually...

almost verified an action has happened with somebody's face, which is kind of cool. Go and sign that transaction on the backend on that protocol that you created, that is a smart contract. And now all of a sudden,

almost verified an action has happened with somebody's face, which is kind of cool. Go and sign that transaction on the backend on that protocol that you created, that is a smart contract. And now all of a sudden,

almost verified an action has happened with somebody's face, which is kind of cool. Go and sign that transaction on the backend on that protocol that you created, that is a smart contract. And now all of a sudden,

you have this permissionless open set of encrypted users and like hashed users and hash action that maybe on the hash action, only the developers of that implemented have the key to understand what is the action. And for the hash users, only the user have the key to know that this is who they are. And yeah,

you have this permissionless open set of encrypted users and like hashed users and hash action that maybe on the hash action, only the developers of that implemented have the key to understand what is the action. And for the hash users, only the user have the key to know that this is who they are. And yeah,

you have this permissionless open set of encrypted users and like hashed users and hash action that maybe on the hash action, only the developers of that implemented have the key to understand what is the action. And for the hash users, only the user have the key to know that this is who they are. And yeah,

That way you kind of keep everybody shielded, but you also create this great database of action that actually happened locally and the likelihood of the second action to happen. And I think that's great. That's actually something one person can do.

That way you kind of keep everybody shielded, but you also create this great database of action that actually happened locally and the likelihood of the second action to happen. And I think that's great. That's actually something one person can do.

That way you kind of keep everybody shielded, but you also create this great database of action that actually happened locally and the likelihood of the second action to happen. And I think that's great. That's actually something one person can do.

Cause like if somebody is selling ads somewhere and they're like, wait, wait, wait, can we pay? Can we pay to know? Like if somebody saw that ad and we, we take it like, what's the likelihood of them doing something completely random and something else somewhere else. They will pay also for that kind of information. Yeah.