then you got some speaker invites now
give us just a few minutes while we get announcements out on all of our platforms and get our speakers up on stage
speakers if you're not seeing an invite
go ahead and request a join as a speaker
not sure if you're seeing my invitation right now
I think everybody's on stage now can we do a mic check with you guys?
Hello. Hello, Alex testing.
All right, we'll get started in just a minute.
Welcome to Secret Spaces, everybody.
Thanks for joining. This is a weekly Twitter space featuring news from around the Secret ecosystem.
And this is a part two episode. Last week we had part one of our grant recipients.
And this week we have the final two grant recipients. We recently rebooted the Secret Labs grant program.
And I just posted the announcement or pinned the announcement in this space so you can check that out if you're not familiar with it.
But on January 19, we posted the winners. And today we're going to be speaking with a couple of the teams and hearing about what they're building on Secret.
So thanks for being with us. Let's do some introductions.
If you want to just do like a one minute introduction to your team and then we'll go over to the Reclaim protocol team.
Yeah, of course. Thank you. Thanks for inviting me. Hi, everyone. My name is Yesha.
I am a associate at AART. That's the ANTHA Association Research and Technology.
So AART is a collection or collective of some experienced people in different areas.
So that's software engineering, finance, tech, you name it.
So what brings us all together is we tend to work on projects, especially in cutting edge or bleeding edge technology.
And two years ago, I think in either September or November, I was looking into Web 3 and that got me into the secret network.
And I was very interested in privacy on the blockchain. Around November 2022, I was the team lead for a project named called Blackjack.
Blackjack is a card game on the secret network. So it's a blockchain card game.
It was quite successful, I believe, and we had quite a good community.
And we really learned some insights on building not just games, but building contracts that employ privacy.
And since that time, we've entertained the idea of building a platform where people can can play with with the benefit of having privacy and a really good area that is in high demand is in the casino area.
So what we are building at AART is a industry first decasino.
So decasino is just a decentralized casino, but what really gives power to this idea is the application of privacy.
With privacy, not only does it mean you can be secure, you can have privacy in your earnings when you win a game, but with a secret VRF, you can also have a trustless way of being certain about the randomness and the fairness of your games.
And that's sort of what we're going to talk about today, at least myself with AART. Thank you. That's me.
Not sure if it was me or if it was everybody.
Yeah, I was experiencing something strange as well.
I think everyone's invited back up now. Sorry about that.
Hey, can you hear me now?
Hey, now I can hear you. Yeah, sorry about that.
All right, let's jump back in. Reclaim Protocol, I want to do an introduction.
Great. Again, let me start from the beginning. I am Subarsh, one of the co-founders of Reclaim Protocol.
What we have built is ZK browser infrastructure.
You have all heard of Oracle's that bring all the publicly available data using APIs into Web3.
The infrastructure that we have built enables users to attest to their own data on the web and seamlessly port it to any application on Web3 or Web2
in a privacy-preserving manner.
So what we do is we make the user data, like I said, privacy-preserving.
The proofs are generated by the user on their own local machines,
and we enable differential privacy by using zero-knowledge proofs,
so users can reveal only the data that they want to reveal
and not everything that they see on their webpage.
So what we pride in is that we are able to create zero-knowledge proof infrastructure
which runs on user devices like mobile devices
and be able to generate these proofs with a Web2 kind of a user experience in less than and also 5 to 7 seconds.
So we have an SDK that integrates with the third-party applications,
and at this point of time, we are deploying the smart contracts on secret.
As of today, we have those smart contracts deployed on Testnet doing some testing before we can make any further announcements.
I'll go into more technical details and use cases during this call.
Yeah, sounds good. That was a great introduction. Thanks.
All right, so that's a brief intro to both of these projects.
Let's talk to the AR team now in more detail about what exactly they're building as part of this grant.
So you mentioned you've already built something called Blackjack on secret,
and I think most of the secret community has probably tried that out at some point.
That's still up and running, and that's a card game that uses secret VRF.
It's not like the traditional Blackjack that probably most people think of when they hear Blackjack,
but it is a card game, and as part of this new grant proposal,
I think maybe you're also including the classic Blackjack as well,
but feel free to just dive in however you want to tell us what's in this grant.
What all are you building as part of this casino?
Yeah, absolutely. So from a user's side, we're building three things.
We're building a decasino, which is a platform that will allow you to play multiple games,
and the decasino itself, we hope it will integrate good KYC, good AML that is still privacy preserving,
but basically allows people to play these games with the safety and the knowledge that it's all above board,
and that makes the games much more available to everyone.
The two games that we're going to pilot with is video poker,
which is quite similar to poker.
So we've got an MVP for that already, and we are hoping to start a beta testing program for people to try out in the near future.
And indeed, the second game that we're going to release for this grant is a Blackjack or 21,
so the classic Blackjack that most people know from casinos.
What's exciting for us is in the frame of a backend team or a dev team,
what we're excited to build as well as this is key infrastructure that allows for seamless and quite user-friendly experience.
So we want for someone to be able to connect to our decasino and not have to worry too much about the backend stuff,
the stuff that's quite difficult to get into when you get into Web3 or into blockchain,
things with wallets and things with viewing keys.
We want to integrate it in a way that it's very user-friendly.
And some of the technologies that we're developing specifically for this project, for the decasino,
we're sort of using it as a test subject.
The two primary ones are a fee grant faucet and an alias or like a dummy account.
So the fee grant faucet gives a fee grant allowance for people who are connecting to our smart contracts
and utilizing our smart contracts or playing our games.
What that means is when you interact with our smart contracts, we will cover the gas fees
so that you don't have to worry or really know about gas fees if you're someone from outside of Web3.
If you interact with our smart contracts, we'll deal with that for you on the backend.
And it'll be as though you are interacting with any other Web2 application.
And that sort of abstracts away that information, that flow from the user.
The second thing that we're really keen to try out is an alias.
So our smart contracts are made to be quite flexible and robust with which wallet you connect to.
So our smart contracts, they're compatible with MetaMask.
They're compatible with FINA, which is a big one.
They're quite compatible with Kepler, all the major ones.
But what this means is it sort of creates a delta of, well, the common thing is that every time you want to interact with a smart contract,
there's a bit of tedium where you have to often double, not double sign, but double confirm just to do a basic task.
Like, for example, in Blackjack, we were actually trialing this concept where you have an alias.
So every time you want to play your turn, instead of having to confirm with your wallet that,
yes, I want to play my turn and start the next player's turn, you can create an alias.
And that alias is completely removed from your wallet.
So we don't even need to actually interact with your wallet that has your tokens or your information.
And we can give that dummy a fee grant.
And then that alias is associated with your wallet.
So when you interact with our smart contracts, our smart contracts are able to know that this alias is associated with your wallet.
And that's how we know when you win a game, for example, to send the funds to your wallet.
The things like signing are still done through your wallet.
So there's still that security and that safety.
But it's something that we're really excited to prototype and integrate into this decasino.
That's interesting. So the idea of these aliases is just to...
Sorry, I've actually just lost you there.
I can no longer hear you.
So I can address a question while Patrick gets his issue.
So someone has asked, how do you plan to compete with other casinos in the space?
I think I know of three others just in secret, not even mentioned the plethora of ones outside of secret like Gelato.
Just so I know I'm not speaking.
Hey, I can hear you. Go ahead.
Okay. Yeah, to answer that question, we're a small team.
There's no doubt about that.
And our focus is on building the infrastructure that makes this stuff seamless.
While we are a small team, I very much have confidence in our ability to develop a product that is not only unique, but is competitive.
When it comes to scalability, we do have experience when it comes in that area.
And competition is always good.
This is a space that needs different people trying the same thing but differently.
And we're not really in the mindset that we're competing.
We're in the mindset that we're foraying into a new area rather than an era.
And what makes the decasino quite unique is the use of secret VRF and privacy in ways that haven't been done before and can scale in ways that what we're creating is basically a template.
So our actual goal is not to, at the end of this, be the only ones making the decasino.
But what we're creating is a template for other people to build their own decasinos and perhaps even implement their own changes and their own styles to it.
But I hope that answers your question.
Sorry, guys, I dropped again, apparently. Was it Alex that asked a question after I dropped?
Yeah, there were questions. There is one more. Are there any plans like capping that supply? I'm not sure I quite understand.
Okay, I see you're answering questions in the chat now. Gotcha.
I asked the question as well. I'm not sure if you heard me about the aliases, but just the idea of those aliases is to improve the overall UX, make it so that people playing the game don't have to sign transactions as often in between turns.
Yeah, that's exactly right. So it's about improving the UX.
And the way that we want to implement it is you don't have to do this per contract when you're when you're using an arts contract.
It's shared. The alias is shared across contracts. That's just adding an extra layer of the UX, the UI.
Interesting. Is that something that other secret gaming apps could potentially use as well?
Yeah, absolutely. So at the moment, we're testing it out on our smart contracts, but we're planning to roll it out as a general service that other smart contracts can sort of take advantage of because there are a lot of areas where you want the UX to be no different from web 2.
You know, the biggest thing, the hardest thing to get people from web 2 to web 3 who aren't really technically aligned with how web 3 works is getting them to familiarize with that kind of stuff, you know, with the wallets and signing and understanding what they're signing.
So if we can abstract that way in a way that's still safe for the users, that's going to help a lot of smart contracts.
So yeah, that's definitely something other contracts can use. And we hope to roll it out as a service once it's tested.
That's awesome. The fewer the clicks, the better.
And you also mentioned metamask compatibility. Do you currently have plans to have this completely compatible with metamask so that, for example, if someone has never used secret before,
let's say they just have a metamask wallet with some Ethereum in it, is the goal to be able to onboard them directly?
They could just connect their metamask wallet and maybe swap their Ethereum and start playing?
Yeah, exactly. That's already something that we were working on with Blackjack.
So actually, metamask users can use Blackjack. So we'll be able to integrate that into our DeCasino.
And yeah, indeed, the flow is that a metamask user connects to secret and they would need to get some secret tokens for gas.
And then they could play just as if they had a FINA or a Kepler account.
That's awesome. That's great to hear. I think that's a trend we're going to be seeing over the next year.
Any new secret apps that come along, we'll probably try to make sure they're keeping that in mind and making it as easy as possible to onboard people from EVM ecosystems. So that's great.
All right. That's a great overview of what you guys are building for this grant. Let's go over to the Reclaim Protocol team.
So what are you guys building specifically as part of your integration with secret?
We kind of already talked about what Reclaim Protocol is and your project has been around for a while now operating on other chains, I believe.
But this grant will allow you to integrate with secret and I think that will involve some customizations that aren't present on the Reclaim Protocol right now.
But yeah, just tell us what are you doing as part of this grant?
Yeah, Patrick, if you will, so I will take like a minute or two just to explain how Reclaim works and then jump into the secret.
So like I mentioned earlier, what we're building is ZK browser infrastructure.
What happens is typically when a user tries to access any particular website,
we have the ZK browser on which they do that activity. So let's just say now there is a DeFi app which is trying to enable under collateralized lending.
And now it comes to and Patrick is interested in applying for a loan. He goes on that application and starts filling out details.
Then at every point of time. So think of this like a typical bank loan application. So where they will ask for Patrick's identity.
Where does he work? And also things like so what is the monthly average balance for the last three months?
For each of these questions, instead of submitting a paper trail, which is impossible to do in the web3 world
and increasingly getting so difficult to do in the even the web2 world.
So there will be a nudge where.
When when when they click on proof to submit the proof, it opens up the ZK browser in which let's just say like we have to pull bank account details.
So it will open up your Bank of America webpage. You log in into the webpage in the ZK browser.
The attester reclaim attester. The infrastructure that we build is so access a proxy through which the traffic data traffic is going.
Mind you, the traffic is all encrypted and it's all this activity is happening on your own local device.
The one thing that happens is the attester edits to the fact that a legit request to Bank Bank of America has been made and the response that is coming first hits the proxy before it hits the actual front end.
So both the response the request in the response are attested to be legit and then the particular page where the account balance has to be revealed.
And also that particular page the attester shares it with the zero noise proof circum circuit where the user Patrick and also shares the session case of the data so that the encrypted data can be revealed in this circum circuit.
We do a regular expression match of only the fields that matter, which is the statement balance and not any other detail. So that is how in a so ZK zero noise proofs enable differential privacy.
So this selective reveal of data plus the attestations that all this happened in an environment which is legit combined together forms a proof of the ownership of the proof of prominence of the data.
That's kind of a ELI five or a slightly more complex explanation of how reclaim works. Now specifically, you know, so this doesn't require anything to do with blockchain per se, like it has so the TLS network layer level intervention and zero noise proofs for selective reveal.
But, you know, for a third party app on secret, you know, let's just say like blackjack now they want to do age verification or ZKKYC.
So they are a secret network, you know, so for them to communicate and do a verification to prove the proof generation happened locally, but the verification has to happen on chain and the data has to be accessed.
So this is this is where the integration comes into picture where we would deploy easy DSA or an equal and signature schema and then we deploy the smart contracts on on secret network and also for any of the application to seamlessly interact with the user and access the data and put it on chain.
So that's the integration that we are working on. And of course, so we are a enabler of use cases, right? And also like I explained, so blackjack and so they can use reclaim to enable age verification and ZKKYC.
You can do an entire KYC that somebody holds a Coinbase account and that's that's as good as a KYC technically.
So and then there are applications like bushy they're into eSports and also if you want users to port the steam ID their gaming activity across different games and also that's again enabler.
I talked about NASA DeFi applications of ZKKYC proof of personhood a whole bunch of social logins a whole bunch of new use cases that are not previously possible can be enabled with reclaim integrating with secret.
So that is that is the whole intent here. So we want to enable a whole bunch of new use cases that were not thought about in this space that can tap into identity reputation reputation or using users that to social data.
So I'll stop at this point of time and see if there are any questions.
Yeah, that's awesome. That's so we kind of saw a similar theme last week with the grant projects we spoke to where the technologies they were building.
They are already seeing use cases that they could they would fit together and they could like use each other's technologies and that's something that I didn't realize hosting this space today, but blackjack could potentially use reclaim protocol for their KYC solution.
Have you have you guys considered that yet blackjack team? I mean the AR team.
Yeah, yeah, we have actually talked with reclaim and we think we think that there's potential to be a good fit.
And yeah, we think that CK.
CK KYC is is actually exactly what we're looking for when it comes to privacy preserving KYC.
So it's definitely something that we want to explore.
Yeah, yeah, we already have a few examples that I can share with you guys.
Yeah, and happy to go more into tapping into some of these use cases.
I have a quick question. This is Alex and I think I asked it to chill before, but for everyone's benefit. So ZK proofs are kind of confidential by themselves, right?
So maybe you can elaborate a little like how do you use the secret networks privacy in this context? Like what is the actual benefit of using specifically secret for your for your technology as compared to, you know, a non confidential blockchain network?
So honestly, like I'm I'll try to attempt to answering this question is so I was not following those conversations, so I come unprepared for this. But let me see. The thing is.
When the data goes on chain like so till the part that the user generates the proof and.
Ports it to the web three applications, you know, it's all privacy preserving. So that part is is what reclaim is enabling. But once the data goes on chain.
Now the user has given the consent to share the data and the third party application is using the data. And how do the third party application uses the data? And that is where the the privacy preserving.
Dynamics of of the data comes into picture and that's where so I believe in also applications are specifically deploying on on secret network and still keep this differential privacy.
Continue the continue managing this differential privacy like so in the example that I mentioned previously, not so yes enough. We have revealed that Patrick Patrick has so identity is so and so or they have a coinbase account which is the KYC and they have a bank balance of more than $10,000 something like that. Now once this data is on chain.
It's only a blockchain like also the enabler like secret and also that keeps it to privacy preserving.
That's that's a that's a kind of a generic answer like so I may be able to probably put a blog and share on specifically in us or how reclaim can and secret can enable this.
The privacy of user data for a longer period of time.
Yeah, well, thank you. Thank you. I think a blog, you know, will be great and I agree as far as I understand is I understood it from, you know, initial conversations that exactly as I said, you know, I can prove I'm over 21.
But on a on a regular blockchain, like everyone would see that everyone would be able to see that I have a certain proof attached to my wallet and I'm over 21 or that I have well, I mean being over 21 is probably not a very private piece of information.
But, you know, holding over a certain amount of of of assets is and I think it's it's super important.
Even though those are zero knowledge proofs and they don't disclose how much, you know, funds I've got.
But just the fact that I have, you know, I have funds and I have proof that I have found, you know, even that my it's not desirable for anyone in the world to know that.
But I have funds in a certain bank over a certain amount or even my age or any other, you know, anything else. So I think it's kind of I think it's really improving the offering in the sense that whatever I want to prove to the world.
I still control the information. I don't just shout it out to anyone, but I only show this proof to the, you know, people or apps that need that information that I consent to give that information to.
Yeah, definitely. So at a very high level, you know, so we can have some kind of a mixer.
So that's one thing. But yeah, it still says like this or the pool of data or the pool of wallets that are there in the mixers. So all of them are above the age of 21.
I think it also we'll go deep into it as we explore it further.
Yeah, honestly, at this point of time, so I don't have a great answer for this.
But we'll we'll we'll try to also put together something and share pretty soon with this group.
Awesome. Thank you. Yeah.
So could this technology potentially be used to allow people to authenticate with their like the Twitter handle or their Discord handle telegram handles, something like that.
Maybe verify that they are who they say they are on this platforms and then use that to log in or like authenticate with a Web3 application on secret.
Absolutely. Absolutely. So this this comes kind of in the arena of the login user. So using a social login to kind of authenticate or access a few things. So that's absolutely possible. In fact, I think, you know, so Madhavan
My co-founder also has written a blog on how this can be enabled.
It is it is one of the strong use cases for this in the web space.
Yeah. In fact, like one of the one of my favorites is proof of personhood.
proving that somebody has taken 25 Uber and Uber is quite popular for most people access most of the people moving that somebody taken 10 right in the last year.
So that's that way of proving to somebody is it's difficult to replicate it.
So that's that's an interesting way of enabling proof of personhood.
So so that's that's one of my favorite use cases.
That one of the first things is first ones that we came across when we started building this
Nice. Well, let's hear a little bit about the progress that's being made so far. So let's go back to the team.
What are you guys working on right now as part of this grant? And I guess what is your overall timeline for this project?
Yeah, definitely. So where we are at the moment is our MVP for video poker has been buffed up a little bit proceed.
We're still running testing on it. And very soon we will want to make that testing public.
So it will be on on Pulsar 3 the testnet and people will be able to play around and we'll be making a post probably in in Twitter and on our Discord to get people to sign on to our beta testing program.
And the benefit of that program is that you'll be able to have a say and have your input on what sort of what sort of improvements can be made or what features do you want to see that makes sense or that that enhance the user experience.
And that would be quite good as well. That's how we that's how we generally like to do our testing.
We like to get the community involved. It was very successful when we did that with Blackjack. Some of the some of the OG testers will will be able to attest to how how great the end product was compared to when it started out because of because of user input.
So we really value that in terms of time frame. We're looking to get the beta testing open hopefully by the end of next week.
And the main the main focus for ourselves right now is actually the DC no platform. And that's less to do with the with the games themselves.
But with the onboarding and the and the user experience that what we were talking about with the FGF the big run to force it and the alias a way to sort of to handle that across across different smart contracts because each one of these games is a separate smart contract.
Right. So we need like a seamless way to for the user to connect to just one thing which is the D casino. And then because they've connected to the D casino it means that they don't have to do a repeat signing on when they connect to the wallet.
Sorry to the to video poker or to Blackjack or to or to roulette or to to crash when we add later games down the line.
So yeah our roadmap looks like in the next by the end of next week we'll be asking people to to beta test. And I think there are some questions if you'd like me to answer them.
I'm just not sure that they're showing up but I can see a notification.
Yeah. Feel free to go ahead and reply to those if you see some.
I can't actually see. Yeah I've seen five in the number but I don't see any new one since the original three a while ago.
But let's that's that's a good point. Let's go ahead and ask for any questions in the audience.
If anybody has any questions feel free to put your hand up. We'll bring you up or just type it in the chat if you want to just type in the comments of the space.
And let's go over to reclaim protocol. So what are you guys working on right now and what's the time frame for this?
Great. So the good good thing is we are working on reclaim smart contract deployments and we have finished that on we completed deploying on secret test net as of this morning.
PSD and we are looking at sharing a demo video of how it works with the team in the next 12 to 24 hours.
Awesome. So post that and also of course also we will be sharing some documentation to on how to integrate reclaim SDKs and also onto any of the decentralized applications.
So and then we'll be doing like a few announcements and community calls and also where we can go over with some of the developers on how reclaim can be leveraged.
So that's that's something that we are looking forward to do in the next couple of weeks again.
Ruchil and I will be working on reaching out to the likes of Blackjack and a whole bunch of applications where we feel there they can potentially be a new use case that can come up and see like which of the applications that are active on secret can leverage reclaim.
So that so that's the effort that we're going to put in in the next 2 to 4 weeks while this deployment is tested and taken live on secret mainnet.
Yeah, if I just want to ask. So if you're already ready on on testnet I'd be interested if possible if we could I'd be interested in coordinating so that we could even try try your your your AP your API's.
So your SDK on our testnet. Yeah, that would be that would be something I'd be interested in doing after call because I think a collaboration might be good and we've already discussed it.
Awesome. Sounds like good progress is being made. Definitely looking forward to seeing more from those updates over the next couple of weeks.
I did want to mention that the Q2 grants cohort will be opening up in March. So if anyone is currently thinking about applying to the secret labs grants program, definitely start looking into it and ring up on the requirements and what we're looking for.
It's not too early to go ahead and start putting together your proposal because March will be here in no time. So definitely check that out. And if you have any questions, feel free to reach out to us. We're happy to answer any questions you might have about the grants program.
I don't see any questions from the audience. So I think we can probably go ahead and wrap this up. Alex, did you have any other questions that you wanted to ask the teams?
No, I don't have any questions. I just wanted to say that, you know, we are excited with both projects. You know, the first two projects we discussed last week were more about privacy and service.
Those two projects are, you know, very different in a way and are using secret network in different ways, both for randomness and for privacy, very different applications. You know, gaming is something that has existed gaming gambling for a very long time.
But it was always hard on the blockchain and art is attacking that. And we see there is a huge potential reclaim in my way has a very innovative model and idea that opens up for, you know, some use cases that are clear now.
But I think the potential is, you know, big for use cases that we don't even or cannot even think about right now, like what kind of things people can really prove on web to that can can be used a web tree.
So, I think this these are great opportunities, you know, we're happy to have both projects as part of the grant program and you know we'll be providing support and help.
And thank you for for being here.
Absolutely. Yeah, and the team is, you know, the team is very pleased to be to be included in the first grant program.
So we're very excited to continue building. And yeah, we're quite grateful. So, thank you.
I'm guessing it looks like Patrick is. Okay, yeah, you did drop Yeah, by the way, Twitter spaces is having issues like, I mean, I think people should start thinking about an alternative because it's sometimes you're not heard or things cut out.
It's it's been terrible lately so I don't know.
Anyway, I guess we're we're wrapping up right.
Yeah, wrapping up sorry about that. That was like the fourth time my personal account dropped off for some reason but the secret account stayed on, which is good because it was the one hosting, so we're going to wrap it up from here.
Thanks for being here everybody. We'll see you next week at our usual time Tuesday at 5pm UTC for another episode of secret spaces.
Until then, we'll see you in the secret network community. Have a good week.