Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
What to Build with OPL and Sapphire: Privacy4Web3 Hackathon Workshop
Recorded: Sept. 4, 2023 Duration: 0:52:10Space Recording
Full Transcription
So I'm Harry, I'm a Technical Product Manager at Oasis for Sapphire and OPL, and with us
today we have Nick Hines and Matei Yanez.
So if, Nick, would you like to introduce yourself and then we can move on to Matei.
For sure.
For sure.
Thanks, Harry.
So yeah, as mentioned, I'm Nick, I'm now the ecosystem growth advisor at Oasis and I'm working
in the ecosystem building apps and exploring the uses of the technology for expanding the
platform.
And Matei here, I think you all probably know me, the BD manager here at Oasis, been on a few
spaces in Discord community costs in the past month, so I'm not going to go too long here.
So as you know, we're about 10 days away from the deadline for the Privacy for Web 3 Hackathon, and I would like to give a brief overview of what's on offer here, and hopefully we can get into some details of maybe if you haven't decided what to build yet, or you need some help or some ideas and inspiration, we'll get into that afterwards.
So the Privacy for Web 3 Hackathon is offering up to $40,000 in prizes across four different categories, and I think there's the first, second, and third place in each of the category.
So we're also partnering with a company called Cyberscope to offer free audits for all of the winning projects, and in addition to that, there are $25,000 worth of follow-on grants for winning projects, and also sort of ecosystem support, marketing,
support, business development support, and whatever support we can offer to help incubate these projects.
So the deadline for submission is, as I said, in about 10 days, and we have September the 13th at 11 p.m. UTC, which is 7 p.m. Pacific time, and 6 a.m. Dubai time on the 14th.
And at the moment, there's almost over 800 registrations, which is quite a turnout, so we're going to have to look at which applications come in, and any promising ideas that will go through the judging criteria, and hopefully we'll get some really interesting submissions.
So I'll start off with what to submit.
So really, we're looking for a demo video, which is up to three minutes long, along with a text description explaining the features and functionality of your submission,
and an open-source Git repository with a readme file, and a way to test the project.
So that's a link to the app and testing instructions.
And, of course, you need to submit the submission form by the final deadline.
So, Mate, would you like to go for a bit about the judging criteria, and tell us what we're looking for in these projects that are being submitted?
Yeah, sure, Harry. Thanks.
So the judging criteria, we're pretty objective.
We look at every complete submission, and then we're looking at the uniqueness of how they're implementing Sapphire functionality either natively, or using type of features through OPL.
Then we're also looking at how well the submission is developed, and we gauge a little bit what could be the market interest as well.
So here, I would say we're looking at the complete package.
But, of course, the most emphasis is given on how well the DAP is using the unique features that Sapphire offers.
So to go through the categories, again, we have the best app on Sapphire, and then we have the best app that uses the Oasis privacy layer, which is OPL.
Then the best use of Sapphire for scalability and privacy, and then tutorials and standards.
So one thing I might add with the tutorials and standards categories, there are a lot of differences with confidential EVM and with Sapphire versus the transparent EVM world.
So while we are looking for applications, there's also a lot of ground to break with discovering new patterns, establishing standards for people to work with, or helping people get up to speed with the new technology as well.
So we're looking for applications and tutorials and standards at the same time.
Yeah.
I would just add here that, yes, the tutorials and standards category, I think it's really nice because it enables anybody, you know, that maybe doesn't have, like, a whole team to help them on developing a DAP, you know, that they can still engage in the hackathon, you know, maybe do a tutorial on how something can be done on Sapphire
and gives everybody the opportunity to get involved here and gives everybody the opportunity to get involved here.
I should probably add that if you don't get a full application through for the deadline, it's always possible to turn this into a tutorial.
I mean, to learn about the development process, to maybe cover some tough spots that you ran into or some interesting problems.
And that's definitely worth submitting on its own.
So I think we should move on, Mate, to looking at the projects that won the Pitch Night competition.
And if these projects were to be submitted to the hackathon, so which of the categories would they fit in?
And could we, like, elaborate a bit on the implementation or what could be done in order to obtain a successful application for these?
Yeah, we can go through that, of course.
Yeah, so I think the winners have been announced in the community.
And I think the first place went to the smart wallet for the local markets, where we have, you know, the traders and farmers who are in that unbanked section, you know,
where blockchain can be utilized to facilitate, you know, the ease of transfer of funds.
And, of course, you know, when we're trading amongst each other, you know, the privacy and security of those transactions is always a good thing to have.
And I think this one would be more in the best use, that best app that uses OPL, I think,
because this wouldn't be completely isolated to only Sapphire, but they would be using some form of relaying the messages from and to other blockchains between other blockchains and Sapphire.
So this was an interesting proposal that was maybe slightly more out of the usual scope of, let's say, more DID data storage and the likes that we, the use cases that we see more regularly.
Then the second one was, I think, I think it was, was it DC?
Let me just check something.
Sorry about that.
One second.
I think I have the wrong, I have the wrong scope here of the, of the DC's project.
So if we look at, look at the, the Amino project, where we're acting as a bridge between the sort of decentralized currencies and real world economic activities.
So a lot of the, the main uses for this are still being discovered, but it would be using OPL primarily.
So if, if this were to be submitted to the, the hackathon, it would be definitely in the runnings for the, the Oasis privacy layer best use prize.
Would you agree?
Sorry about that.
I didn't hear well.
Something broke off.
Can you, can you repeat what, what you said for Amino?
Yeah.
Amino.
So if, if we're looking for contenders for the best app uses of the Oasis privacy layer, this would definitely be in the running.
Oh yeah.
Yeah, for sure.
I mean, we are very, very big on, you know, individual privacy, you know, where not everything needs to be seen.
You know, what you, what you purchase from, who you purchase in what amount.
So this, this can definitely fall in the, let's say individual sovereignty of, you know, what, what people are doing when they're trading, trading goods and services amongst each other.
So I think this is, this is for sure a good contender for, for the OPL category.
I would agree completely.
One of the criteria that we are looking for is impact and the kinds of things that can go out into the real world and onboard non-blockchain users seamlessly onto the blockchain, especially Sapphire, are the things that are going to have really high impact.
Yeah, that, that's, that's a spot on, Nick.
Oh yeah.
Found, found the, the DC scope now.
So yeah.
Well, the second, the second winner was a Web3 login solution through SBTs.
And when we, we see that, you know, the demand for a decentralized identity, you know, where the users have control of their data, you know, they decide who they share it with.
Uh, also to gain the reputation, you know, in the Web3 space without necessarily even revealing your identity is one of the, one of the big things happening now in, in, in, in, in, in Web3, you know, because, uh, also we, we need to somehow distinguish, uh, you know, real people from, from bots, you know.
So, uh, so, uh, the ID, SBTs, these are all, uh, topics that, uh, that are very, uh, very in demand now.
And I think, uh, Sapphire and OPL are very, uh, like a perfect match for, for these types of applications, right?
Because, uh, you can deploy, uh, set on, you can deploy, you know, solutions that keep users data private on Sapphire and then use OPL to utilize, uh, that, the, the, those,
the ID solutions across any EVN compatible network, uh, that, uh, that is integrated with, with OPL.
So, uh, this is another, another great example, not sure, uh, where we would put this, uh, because it, it kind of fits in, in both, both, maybe even a best use of Sapphire for scalable privacy.
Uh, Nick, uh, Harry, any, any input on this one?
I'd probably, uh, bring up the account abstraction as well.
So we're, we're moving away from, uh, like externally owned accounts with your key pair and, uh, moving towards, uh, social recovery and, uh, web to log in and, uh, sort of different types of authentication.
So, uh, being able to separate your, your wallet addresses from, uh, your identity and then perhaps have, uh, wallets that are managed by your identity.
That's very, you can log in with multiple different methods.
I think that's a really interesting use case.
So one thing that Sapphire can do, for example, is, uh, it can store, uh, passwords on chain.
So if you want to have like a, a backup password to, uh, gain access back to your, your account, that's, that's definitely possible.
So I think, uh, this is, uh, the kind of thing where it's the best app on Sapphire, where, uh, if you're utilizing Sapphire's confidentiality features and, uh, you can prove your identity to other chains without needing a bridge or even prove it to web two services or create JWT tokens, for example.
Uh, this is something that would stand alone and, and, uh, really demonstrates, uh, sort of Sapphire on its own as, as being its gem.
Uh, Nick, what do you think about account, uh, account abstraction and soulbound NFTs and identity?
I think it's a fantastic use case and it really leverages the unique value that Sapphire has to offer, especially, uh, given that it makes it way easier to use for people who are just getting started with, uh, blockchain.
And it defeats entirely the common or fame that it's like blockchain is too hard to use.
I'm going to lose my wallet.
My tokens are all going to be gone.
And really that just doesn't have to happen anymore.
If you're keeping your account safe on, on Sapphire, using these account abstraction tools, like a login, SBTs, multi-sigs, and, and especially with the new, uh, well here, I might not, I, this might be letting on for too much, but I mean, there's this whole effort in, there's this new effort into secret sharing.
That will allow the key material store on Sapphire to be even more secure against, uh, the kinds of, uh, single point of failure attacks that have been coming up recently against TEE.
So it's really no reason not to use Sapphire for storing your shared secrets for recovery later.
So you're saying that in, in the long run, um, while it may take a bit of time to, to develop these apps and get some use cases, uh, uh, sort of worked out, uh, you're really looking at Sapphire as being able to have custody of, of, uh, to the same degree that you'd expect from, uh, the sort of centralized exchanges, but in a decentralized fashion with a full programmability.
And, uh, uh, that sounds exciting, but it's also, um, interesting as well.
I mean, uh, I'm not sure where this is going to go, but it's, uh, it, it, it makes me wonder what, what's coming up next year or so, but I think we'll have to look at the roadmap for that and, uh, and see what we can do to make this possible.
And, and, and to alleviate some of the concerns that people have to make sure that we can offer, uh, the most secure service.
Should we move on to the next, uh, project here, Matei?
Yeah, yeah.
I think, I think this was covered extensively and I do share your, uh, share your vision that account description will help, help a lot, uh, with bringing more users in, you know, and I, especially, uh, when you mentioned passwords on chain, you know, if somebody creates a password manager for me,
on chain that I can, you know, store there and unlock with my, either now with them, um, and user account or, um, or, uh, some different type of identification, that would be great.
You know, so I have to, uh, keep my files in sync everywhere on all of my devices and making sure that those are, uh, kind of kept updated and, and, and secured.
So I'm really looking forward to this type of, this, these type of applications.
Um, the third one, uh, the third reward for, uh, the pitch night was given to, uh, a pitch about a social media adept, you know, that it would have a customizable privacy settings where you could have like, uh, calling, messaging, uh, stuff like that.
So I think that's, um, it's, um, it's kind of like, you know, building a super DAF on Sapphire, you know, how X is now turning into a similar, similar vision.
And I would very much love to see, see something, something like that built on Sapphire because we have the underlying tooling, right?
Uh, with the privacy aspects, uh, then it's just a matter of how to, how to build on top of that, uh, to enable all these social, social app functionalities.
Uh, maybe on the technical level, you and Nick can, can be more from the commercial side.
I would be very excited about an app like that.
Maybe you can share more on the, on the more technical level, whether there are restraints here and how Sapphire and OPO could be used.
I can take a stab at that.
So one, yeah, one thing, this is really, uh, great because it's at the intersection of account abstraction and, and privacy and just overall usability.
Super high impact because people are really demanding this in this, as we see the decline of existing social media platforms and popularity.
So what we really have is, uh, on OPO and the Sapphire is the ability to, of course, store these secrets and not just store them, but also interact with other chains.
And so one common thing that we've, um, heard is that people want to use like different chains to store like the very fast moving data coming through.
So like Hedera comes up sometimes and then using through OPL Sapphire to store the long-term keys for all of that, uh, social media data.
So you're basically having your social media app wherever you want, where all the users are.
You can have payments going from back and forth, whatever you want, but then you have the keys stored on Sapphire, giving people privacy, selective disclosure, and custody over what they're sharing with whom.
That's great to hear.
That's great to hear.
So technically we don't have many, many obstacles here in terms of theoretics, not in, we'll put, putting this in practice, obviously it takes some work, but theoretically it should be possible.
Something I'm seeing now is, uh, with, uh, like the slow demise of Reddit and the splintering of the different social networks.
And now you've got Mastodon and, uh, a variety of others like Lemmy, for example, uh, we're looking more towards, uh, decentralized identity for federated logins.
And it's, it's quite different now that you have, uh, equivalent of an email address.
So you'll have, uh, Harriet, uh, then my Mastodon server, for example, and being able to have a decentralized identity, perhaps managed, uh, through Sapphire that allows you to connect all of your different social profiles together, uh, and verify your identity across them.
I think that's, uh, an important piece of, uh, infrastructure that's going to be necessary for, uh, more federated, more decentralized social networking.
Um, so I, I think, uh, Nick, it would be a good idea to brainstorm a couple of different ideas for, uh, the use cases that we've gone through so far.
So in terms of like, what, what can be built, what's, what's super high on your priority list at the moment, or, uh, what's the low hanging fruit that, uh, doesn't exist, but could be good, uh, you know, we've got 10 days left with the hackathon.
What, what do you think is realistic to, to get through, uh, in 10 days time?
Yeah, 10 days.
It's still enough time to actually put together something pretty nice with, um, focus.
I'm actually most excited about gaming.
I think gaming is one of those really big areas in Web3 right now, something that people are really excited about.
And Sapphire and OPL have this really unique value proposition in gaming where you can add things like privacy for, like, hidden game state, randomness without having to invoke, like, a slower, expensive Oracle.
And then you still get the ability to, like, interact with what people hold valuable.
So, for instance, tokens.
So, one thing that you can imagine is, like, a, like, a skill-based, uh, card game, for example, where people are, I mean, like, maybe betting on, like, NFTs or something like that on Ethereum or your favorite, uh, layer one.
And then you have the game going on, like, like, the game backend on Sapphire.
And then you use OPL to bridge the final game state, like, essentially, like, a roll-up back to the original network and unlock those funds.
So, like, the concrete step-by-step would be, like, step one.
You get everyone, like, staked on their, on the, like, your preferred layer one.
And then the game happens, like, on, completely on Sapphire, low gas fees, account abstraction, super fast, finality, everything that you want from a, basically, a decentralized game server.
And then once the game is done, you figure out who the winner is.
You compute that privately on Sapphire, send that back through the bridge, and then the tokens get unlocked on the layer one.
So, basically, you get the best of everything you want.
It's really nice for gaming.
So, it applies to, of course, uh, card games with RNGs, um, role-playing games with, like, a smart contract for a DM.
Like, it'd be super cool to see, like, a, like, a mud or something like that.
Also very possible to do in 10 days.
And, yeah, so I think that, like, overall gaming is, like, really exciting for, uh, Sapphire and OPL.
I probably add loot boxes in there as well, although it's a bit of a contentious issue with, uh, uh, can you do loot boxes?
Can you not do loot boxes?
Uh, but an idea I was playing with is, uh, hey, why not, uh, give out real, real cryptocurrency in a loot box?
So, uh, if you have, like, a one spin per day per user, uh, and somebody's gonna win, um, some cryptocurrency in-game.
Uh, and that's the kind of, like, web 2, web 3 gaming integration that I think it's fairly straightforward to do this, uh, but getting it into a game and, uh, making it really streamlined, I think that's where account abstraction comes in, unless you're figuring out how to pay for gas, who pays for gas, and so on and so forth.
But I really like the idea of NFTs working across, uh, these different networks, and, uh, maybe NFTs with private data as well.
So, for example, if you have, uh, uh, like a thumbnail of, uh, of a picture, one thing that, uh, Ethereum and the other transparent EVMs can't really do at the moment without a lot of extra infrastructure, uh, is having, like, a download URL.
So, if you have, uh, an NFT with, uh, after gaining access to it, so if you pay for it, you purchase it, uh, you get a download URL for the full version, and, uh, it could be, like, uh, you know, a gigabyte file hosted on IPFS or an S3.
And because, uh, you can have secrets on Sapphire, you could, uh, generate, like, a download URL so that it's time-limited.
Or, um, I know at least with, with Amazon S3, you can generate secure, uh, download links, and, uh, a number of, a number of other services do that as well.
And, uh, Matej, what do you think about, uh, like, NFTs with private data and, uh, or potentially, like, anonymous owners?
And, um, do you think there's a lot of potential there?
Yeah, I would say that, uh, we, uh, NBD, we like to call them some NFTs, uh, and where they have, uh,
like, certain private data, certain, uh, public metadata, uh, and I think there's a big market for it,
you know, because, uh, you can have, like, the verifiability of an NFT, you know, with the public data,
but then keep certain data private only for the owner to, to see, to reveal.
And I can think of a lot of applications outside of that tree that would, could benefit a lot from this,
but even inside the, um, uh, or crypto space, you know, uh, if we go back to gaming,
you could have, like, you know, where you have these, let's say, PvP battles, you know,
where you have these characters and, uh, you could, uh, give it an extra spin where, uh, there's a certain,
let's say, a certain trait that the character has that is kept private to, to the, to the owner,
right. That only reveals itself within the, within the, within the battle and it gives it a little
bit of an, let's say a nudge, a bit of a surprise effect. So not all these basically known almost in
advance, you know, where you, you know, all the, all the trades and all, you have all the data of,
of the two characters, backlinks, for instance, right. Uh, then with NFTs, you also have,
you know, uh, potential for sealed bid auctions where, you know, you don't have this, the price
force and people coming in last minute out beating somebody, you know, but you have basically a
different price discovery where everybody just, it's how much they think this, this thing is worth,
you know, and then you come to like a real, real price, uh, for that asset, uh, through the sealed bid
auction, uh, once, once it's finalized and revealed, right. So that one for me is also an interesting
aspect when it comes to all these, um, you know, uh, initial sales of NFT collections that happen.
Um, and okay. Anonymous owners, um, are, this is very applicable, applicable where you have, you know,
maybe larger institutions that don't want to reveal, you know, what portfolios they're holding.
And you could, you could, I think do even, uh, you could have accounts on Sapphire in private hold
NFTs on other chains, you know, where the owner remains private and can, can, you know, uh, even maybe
potentially lend out the NFTs without being revealed, you know, without being scrutinized and stuff like
that. So I think, uh, there's a lot of, a lot of different use cases, applications surrounding NFTs and,
and privacy. Uh, one idea I was looking at was, uh, if you have, uh, an NFT that perhaps, uh, provides
you access to a website. Uh, so if you, if you hold the NFT, then, uh, you can generate a code every
day that, uh, gains access to the website. So a lot of, uh, uh, for example, like, uh, friend.tech,
uh, you can trade your, your memberships and swap them around. And if they only swap once a day, then, uh,
you're sort of paying for perpetual access. And, uh, I think there are a lot of interesting ways to, uh,
to start pricing access to websites, but especially with web two integration, because the Sapphire contracts
can generate secrets. That means that, uh, you don't need to have the rest of your infrastructure,
like deeply embedded and hooked into the web three infrastructure. Uh, you just need like the,
the little bits where you do social login and then the market behind the scenes, uh, handles the pricing
and a lot of, a lot of the, uh, ownership and, uh, the identity issues with that. I, uh, what do you
think, Nick? And in terms of like, uh, like, uh, ownership of, of NFTs and, uh, like web two versus
web three, and, uh, are we seeing more traction with, uh, like web two integration or are we going
to move all the way over to web three and, uh, we won't notice the difference?
So although Sapphire has this really unique value proposition for, um, making it easier for web two
users, I think that we'll see that in time, but like right now, web three is like where everything's at,
right? Like, it's really interesting for like web three developers who can like sink their teeth into
the privacy primitives and like the offerings that we, like the, the novel things that you can do
and then really run with those things. So like anonymous owners, we've heard of like coming up
time and again, it's like not something that you would like really go like, for instance, business
to, um, business, sorry, business to customer. It's more about like a business to business thing.
So like you do have sustainable business models around, uh, these kinds of things like, uh, NFTs
and then anonymous ownership, especially when combined with, um, the kind of fraction,
like this all really falls under the umbrella of account abstraction. And like, what can you do
when smart contracts can basically have, uh, identities of their own, they like act on your
behalf. So like these contracts are essentially your, your ambassadors into like the web three world.
So from a foothold of like sustainable revenue sources in web three, you can, we can then see
those same kinds of things extend into web two. So something like this as a hackathon project really
has a lot of potential, both just for the, the hackathon and also for the grants program going forward
and even ecosystem funding.
I know at least with business and it's very difficult to, uh, work with the DeFi space because, uh,
uh, it's not really suited for the way that most businesses do business, but, uh, with a lot of
invoices that are going between different companies, you've got very sensitive information. You've got
the line items, the pricing, uh, but I do see a future where perhaps, uh, uh, uh, you could factor
your invoices and your invoices are an NFT and the, in the NFTs are confidential on Sapphire, right?
Uh, so that would open lots of opportunities for, uh, like invoice factoring. So you're getting a loan
based on the delivery time of, of, uh, your, your item or the shipment or, uh, that kind of thing.
Right. And there are lots of things that are going to happen when we start integrating, uh, NFTs with
DeFi and traditional businesses, but that's not quite ready at the moment because of the privacy
problem. So, I mean, uh, Mate, you're probably more thinking of the business side of things of
how can businesses in the real world use, uh, uh, the Sapphire technology and the Oasis privacy layer,
uh, without, uh, having to, uh, dig into the, the weeds of, of DeFi and, and transparent blockchains.
Yeah. I think here, the use case that you just mentioned, you know, with the invoices, I was
speaking to a company that handles, you know, like fiat on-off ramping and invoicing and all that,
and they are very curious, you know, to, to see how they can utilize the on-chain privacy to have
verifiable data, but at the same time it being private, you know, where you said, as you said,
you have sensitive information. Um, when it comes to, you know, businesses that are not from web,
so this was like the Web3 company, but businesses not coming from Web3 trying to get their, get their
feet wet, right. Uh, in, in DeFi and all that, uh, I think it's going to be, it's going to be interesting
to see, uh, it depends, you know, I think on the scale, there needs, there's going to be some, I think,
intermediate layers, uh, and one, one like that can be Sapphire, you know, where we help on board them
with easy, easy credential storage, easy login. And then, uh, they are, uh, there would be
like, kind of like, uh, a soft landing into, into Web3, at least from this perspective, you know, where
it comes to kind of like DeFi and, and, and trying to, you know, extract some, let's say some yield
from, from those DeFi markets. Uh, those are pretty, you know, let's say pretty similar in nature to, uh,
traditional, uh, finance in certain terms. Uh, so I think here the onboarding is more crucial than they know,
okay, you don't have the, you know, smart contract risk, uh, that you need to take into account. Uh, but of
course that can be, let's say not mitigated, but evaluated through, you know, the project's
reputation, uh, and the amount of auditing that it's, it has been through. But I think the, the first
onboarding will be crucial. I think here Sapphire can play like a very big role, uh, where they can,
they can easily onboard into Web3 and then interact the other dApps, you know, through OPL, but we'll have
to work on, you know, the UX of things and, and trying to make it as simple as possible
or for every, any Web2 user. But you know, Matei, with the, that, that track in the, the hackathon
with tutorials and standards, like that's a really interesting opportunity for people to actually
contribute and actually get something out of contributing these kinds of things. Like,
for example, wouldn't it be cool to have like a starter repo for like these kinds of things,
like, like allowing people to, uh, web on Web2 users to onboard onto Web3. Like, I think Harry's
produced a lot of these, right? So, I mean, someone else could also decide to do something
similar, like a starter repo for confidential NFTs, gaming, uh, decentralized social, and like
DeFi even. I think those would be really strong, uh, hackathon submissions as well.
Yeah, I agree. Good point. Good point. Thanks for pointing it out. I, I don't know why, uh, this,
this category always kind of a little bit eludes me. I think it's because it's, uh, maybe a bit more
unique to this, uh, hackathon where you usually don't see, uh, a special category going for, uh,
tutorials and standards. And, uh, but I think, as, as you said, this can be a really good, uh, good one to,
to help the, with the onboarding as well. Yeah.
I, I, I, there are definitely some tough challenges with new spaces. I'm, I know that Nick was looking at, uh,
some kind of, uh, Sapphire specifics. Uh, so this is a bit of a mouthful, a simple Sapphire
Solidity security scanner, uh, which, uh, we know that, uh, in the, uh, the Ethereum space,
there are a lot of, uh, security problems. Uh, there are lots of audits through a lot of, uh,
automated tools going on. And you also brought up that, uh, if we are going to onboard, uh, businesses
on to, uh, define and smart contracts, uh, you have to make sure that the contracts are correct.
But, uh, with starter repos and the standards, I think, uh, there is opportunity definitely to
get some very simple things, right. And that might need a bit of thought rather than, uh,
going for quantity over quality. So, uh, I, I think, uh, just to think about what Nick was saying with,
uh, uh, like key management and, and decentralized identity. And, um, what other areas are there,
do you think that, that, uh, that we haven't covered yet that are worth going through?
I mean, I guess there's always the, the really low hanging fruit, like, uh,
like just like the standard, uh, DeFi stuff. So, I mean, like, um, some of you might be familiar with
these kinds of solutions that, uh, basically are like rollups, essentially that, uh, where the,
where the rollup contract essentially acts as you on the other chain, uh, kind of like, uh,
I don't know, like, I guess, yeah, it's like kind of like a thing where, so you can do it pretty easy
on, um, Oasis privacy layer where essentially everyone bundles up their transactions into like
one rollup smart contract. Let's say the transaction is something like make a swap on,
on, on Uniswap or trade a, um, an NFT on, on like one of the decentralized NFT trading platforms.
And then it takes all of those impacts them into like one big anonymity set,
shoves it over the bridge and onto the other chain where it is, uh, D can, where the payload is
deconstructed, unpacked, demultiplex, whatever you want to call it. And then it sends the transactions
individually, but the transactions are no longer coming from you. They're coming from a smart
contract. So essentially you are delegating your permissions to a smart contract on, on Sapphire.
Then using OPL, it then sends it to another contract that acts on your behalf. So essentially
you are gaining anonymity because it's no longer you who's doing the transaction. It is the Sapphire
smart contract. So you can do things, well, you get, basically you get anonymity for these kinds
of things where you would, uh, wouldn't otherwise have it. So it's like kind of like adding backwards
compatible privacy to your smart, to your existing Ethereum or other networked apps.
I really liked the idea of backwards compatible privacy. I mean, we're seeing a lot of problems
with privacy systems already where, uh, if you're, you, if you're using say, uh, one of the privacy coins,
then it's, it's automatically a target because it's privacy, right? But if, if nobody knows what
is private or which is a private transaction and which isn't a private transaction, then I think that
offers, uh, some better guarantees for the whole system of, um, not being able to correlate, uh, your
activity with, uh, on-chain activity or, um, I mean, there are a lot of cases where I really want privacy on a
day-to-day basis. For example, if I'm, uh, paying, uh, at a shop, I, I don't want the shopkeeper to be
able to see all of my transactions. So if I could put those, uh, payments through, uh, some kind of
Sapphire wrapper, which would make the payments on my behalf on, on the other network, that, that would
be really neat because it, uh, you know, it prevents me from getting phished. It prevents me from getting
snooped and targeted. And I think there are a lot of use cases, especially for privacy and multi-chain
privacy where there are, uh, like really legitimate use cases for this, but, uh, we have to get over
the, the problem of, uh, maybe privacy has a bad reputation in some places. Uh, so I think, uh,
definitely looking at what can we say that is, this is a really good use case for privacy. Uh, it's
compatible with everything and we don't have to worry about, you know, the funds getting mixed because we
can, uh, uh, selectively disclose, uh, information about our transactions because, uh, with Sapphire,
you have the smart privacy concept, which means that you can, uh, at a point in time very easily say,
uh, this was my transaction, uh, versus, uh, other networks, which are entirely private and more
difficult to prove, uh, the source of funds or which transactions were yours. Uh, but I like the
idea of, uh, gasless wallets and contracts that can pay their own gas and, uh, the anonymity
properties that you can get from that. But, uh, Mate, do you have any, uh, notes on, uh, sort of
confidentiality and privacy or, uh, are we focusing, uh, across the whole spectrum or are there any sort
of specific, uh, aspects to that that you'd have sort of advice on for the, uh, hackathon participants?
Yeah. I would just like to add on, on the previous topic, uh, uh, you know, about having a smart
contract, you know, Sapphire basically be your, uh, outward facing, uh, identity and you, your
real identity being hidden. I really like the, the idea here because, um, the, uh, pliable market is,
is huge, right? You're not locked into Sapphire. You know, you, you don't have to do everything there
in order to keep it private, but you can do it anywhere you want to do it, right? Where the,
the applications are running, you know, the opportunity lies and you still can basically
utilize all the features, privacy features that Sapphire uses via OPL. So I think here, uh, this
is a very, very strong, strong case for, uh, why, why, why to move certain, certain aspects,
you know, of individual operations to Sapphire and then with, uh, through, through that OPL there.
But, um, for me, I would say that, yeah. Okay. Uh, there is also, uh, one thing that we didn't
mention is, you know, using Sapphire for key management on different data, you know, that's
lying around encrypted, or maybe we, we handled that already. Uh, but that's for me, uh, it's, uh,
one of the, one of the bigger ones when you, you were, you basically you're using a smart contract
to store encryption keys and you were just, um, you were approving and, uh, and withdrawing the access,
uh, when, when you, when you basically see fit or where all the smart contracts program to, to work,
right? This, I think helps bring more data, uh, you know, into decentralized storage or even
the centralized storage if it's kept, um, uh, in order to have easier management of the,
of the access to the data, you know, or from, from different users. I think that's going to be
a big, a big thing that, uh, Sapphire and OPL can be utilized for.
Well, I, I think we've covered a lot of different use cases today. I mean, uh, hopefully there will be
some interesting ideas in there. And as I said before, there are, uh, 10 days left. So that's,
uh, the deadline to get the submissions in will be 11 PM UTC on September the 13th.
So there's not a lot of time, but there's enough time to, uh, uh, at least finish off some, some
really interesting concepts or, uh, try to save some projects that didn't quite end how you expected
them or, uh, maybe look at, uh, what are some minimal viable sort of concepts that can be developed.
And, uh, so you should definitely, uh, keep up with our social profiles. So we have, uh, Twitter,
we've got discord, um, they've got the blog on the website. So if you subscribe to our Twitter,
you get notified of, uh, future events and, uh, the different places that we're on. Uh, I also
encourage you to join the discord channel. So on discord, we're available pretty much 24 seven,
any development questions you have, if you want to talk to, uh, the business team or, uh, learn
about staking or getting more information. Uh, discord is a great place for that. Uh, we also have
the, the forum, which I think is a forum.oasis protocol.org and, uh, yeah, reach out if you need
any help and we're there to, uh, help you with ideas as well and bounce anything off that you want.
And, uh, I think to, to wrap up today, uh, we're going to be in DATCON in Berlin for the blockchain,
uh, week next, uh, I think, uh, starting the 11th of September to the 13th of September, but the
blockchain week goes from the 8th to the 17th. And, uh, we'll have a standard DATCON if you want to come
along and say hi to us. And I'll also be running a workshop on confidential EVM and smart privacy
at about midday on the 11th. Um, so if you want to find out or you want to come along, uh, drop us
a message in discord and we'll figure out how to do that. Uh, also be at smart con at the end of the
month for, uh, uh, in Barcelona. So if you're in Barcelona, please come along, say hi to us and, uh,
we'll see what we can do. And, uh, Mate, I think, uh, do you have any closing remarks for this?
Yeah, I would just reiterate it. If anybody's in Berlin or Barcelona, do, uh, do this up. Uh,
we have something special planned for both events, you know, so, uh, it's a little bit of a more
private thing, but, uh, for all, everybody that's going to be in person there, do come by our booth,
you know, or get in touch with us. So we can meet up. We always love to
to, uh, meet our community, you know, or, uh, the developers that are working on Sapphire and OPL
and discuss, you know, how, how we can move this, these things forward. We're always open for input,
you know, any, any use case that people like to solve and maybe need, uh, certain things on the
infrastructure side, you know, we're, we're open for suggestions. Uh, so, uh, as Harry said, you know,
uh, do come by. We also have, uh, interesting swag they're going to be giving out. So,
uh, it's going to be worth your while if you compare, but remind me this.
And Nick, uh, I, I think while you're here as well, uh, could you give us a very,
very quick overview of the, the Intrime projects that you're working on and, uh,
maybe some teasers of what's coming up?
Yeah, I'm happy to. So, uh, basically it is a smart worker runtime where you can extend your smart
contracts with off chain computation and like this, all the scalability, privacy and utility
that comes with that. So you can do things like, uh, build ad hoc bridges. That's what we're doing
right now with the AI Rose project. We're bridging all those NFTs from Emerald over to Sapphire using
secure enclaves running, uh, well, secure JavaScript enclaves running off chain. Uh, other things that
we're, uh, really interested in doing are just basically making overall, uh, serverless. So
take your Cloudflare workers and now we're going to do it on the blockchain. So, uh, oracles are another
thing. And then just essentially making it super convenient to build full stack apps using privacy
and the, all the nice benefits you get from a blockchain like Sapphire.
Yeah, I know it's, uh, a big pain to run your own infrastructure. And one of the benefits is
definitely with, uh, Sapphire, you can do a lot more things because of the, the confidential contracts
and you don't have to run your own services. So if you, uh, deploy an IPFS, do you see like, uh, are we
going to be fully serverless and blockchain enabled and, or will we have to, uh, run our own servers and
um, like, uh, will users pay for it or will we be paying for that? And what kind of thoughts you have
on, on the model going forward? Yeah. So, I mean, one of the things I think is holding back the adoption
of web three is the ability to pay for things. So not just pay for your app, right? Like that stuff is
like in web two, you basically pay for your users. And I think that with the contracts that can self-sign
their own transactions and pay for themselves, like you mentioned, Harry, like all that can solve that
problem, but like actually getting people to pay for like the service they're using,
then that's going to require things like on ramps and stuff. But like, once we have that,
then it's, it just should be super simple, right? Like, let's say you want to store some user data
in a database, then like, why would you go and deploy your database? That's like, so web two,
it's like boring. It's, it's high friction, but instead like you have like this very simple
programmable key value store on the backend, right? Like Sapphire gives you privacy, super nice.
And then for your bulk data storage, like bulk computation to enable things like heavier games,
cross chain protocols, oracles and that kind of thing, then you use these nice serverless workers.
So once we have these on ramps, everyone in like the entire world can conveniently
pay for the services they're using, not the services they're not using, which enables things
like a very robust free tier. And then you get like the really nice convenience of blockchain and like
the developer convenience with the usability convenience of web two. So it's basically
like taking like AWS Lambda and mashing it up with something like Stripe, sprinkling in some really
convenient authentication. So you don't need to use like OAuth and go through like the hours long
process of integrating that. And it's just native, no infrastructure, low costs, and then it just really
fire and forget. Like you can't, you don't need to have, you need to have like, like five nines of
reliability when you're running on this decentralized infrastructure. You just get that for free.
Well, I'm certainly going to be paying attention to this because it sounds really,
really interesting. And one thing at least that I'm looking for is, uh, oracles that I can send,
you know, secrets through. So, uh, you know, my API authentication tokens, for example,
uh, that's, that's something super essential that we're just missing this, this component. And
with the confidential workers being JavaScript, kind of like Lambda, that would be a spot on.
Yep. Sapphire gives that all the Sapphire is what enables that. So, I mean, like,
I would be super happy to see other hackathon submissions along similar lines. Like,
it's just really just a wide field open for open for exploration.
And, uh, on that note, I think we've, we've covered everything that we wanted to cover today,
and there are some really good ideas in there. And, uh, yeah, if you want to have any questions,
uh, follow up on discord afterwards, and, uh, we'll see what we can do for you. So, uh, on that note,
I'll say thank you everybody for listening. And, uh, thank you to, to Nick and Mate for, for,
for speaking with us today. And, uh, I hope to tune in next time. Thank you everybody.
Thank you, Gary. Bye.
Bye, everyone.
Bye, everyone.
Bye, everyone.
