Thank you for joining us today for our Twitter space with Stellar under Seabridge integration.
I think we just got Wanali up from Stellar, so yeah, we're ready to get started and dive
right into this collaboration.
Yeah, so sorry, I just had some technical difficulties there.
So maybe to start, maybe Wanali and Harry, can you give a brief introduction to yourselves
and what your roles are at your respective organizations?
My name is Wanali and my major responsibilities at Stellar is for partnerships and also debt
relations and really happy to be here and share what Stellar is up to and has been doing and
and also share what we have been working on with the Oasis Sapphire team.
And I'm Harry, so I'm the technical product manager at Oasis for Sapphire and OPL, which is the Oasis privacy layer.
Generally, I'm helping to advance new use cases, look at the future of what Sapphire and OPL can
do and try to make sure that developers have everything they need to develop the next generation
of blockchain applications.
Thank you guys so much for joining us today.
I'm the ecosystem here at Oasis, similar to Wanali, I have partnerships as well as prioritization
of how we can grow our ecosystem.
So I guess a great place to talk about this partnership today is just a brief overview of
the Oasis and Stellar and the Seabridge partnership and what has been the updates on that.
If you want, you can give some context.
So basically, so, well, I want to confirm, are you asking basically to share what we have
been working on with the Oasis team or what Stellar has been up to in general?
I guess like what have been the stages so far and what is like the most recent announcement
So basically, I think most of the audience here probably had heard of the term bridging solutions
So basically, Stellar has been focused on interoperability for quite some time.
And we're like one of the first few bridging solutions that has like issued an arbitrary
And for our collaboration with Oasis, we have also like supported Oasis sci-fi for arbitrary
message passing with Stellar Interchain Messaging Protocol.
And in addition to that, we're also working on bringing assets and liquidity into Oasis Sapphire.
And I think like the current status for our collaboration is for both of the protocols,
Stellar Seabridge, the asset bridge, as well as Stellar Interchain Messaging Framework.
We have launched both on Oasis Sapphire mainnet already.
And we're seeing tremendous growth in terms of like ecosystem project participation in
utilizing these two protocols and building their own features and designs that could
tap into the multi-chain liquidity and also user base from other chains.
So we're in like active exploration with the foundation, as well as the ecosystem to basically
see what are some new use cases that can be built with Stellar Interchain Messaging on Sapphire
that could cater to different use cases like private voting or, for example, dark pool AMMs that
could prevent from running potentially.
So as you mentioned, Wanalee, like in the past, we probably focused a lot on the Teller IM
partnership, and a lot of people are probably familiar with how that powers Opal, the Oasis
But we're really excited today to announce and to begin talking about the Seabridge integration,
which is the token asset bridge.
And I think that basically this rounds out collaboration and it gives us all the tools
that we need to build a vibrant ecosystem.
Maybe Harry, can you just talk a little bit about where you see token asset bridge and how
it benefits Sapphire as well as maybe some Opal?
Sure, so with token asset bridging, it allows you to bring tokens from a variety of different
I know that Stellar supports everything from Ethereum to Binance to ZK Sync, I think, and
And it allows you to bring your tokens over onto Sapphire to perform whatever application
needs to do that needs to be private.
While Juan Lee mentioned dark pools and AMMs, there's a lot of other fairly straightforward
use cases like just private transfers or doing swaps or being able to pay for tickets for events
that you don't want the information to be public on other blockchains.
So with both the messaging bridge and the token bridge together, it really lets you use Sapphire
to the full sub-capabilities that it has.
And as Harry mentioned, Juan Lee, you know, Seller supports many assets as well as many
Maybe you could just give an overview of what assets are supported today and what networks
are supported today using DeepRoot to connect with Oasis Sapphire.
So in general, Seller supports over 40 different blockchains and most of them are EVM
compatibles and some of them are Polkadot or Cosmos.
But for Oasis Sapphire, we have been able to connect, I think, over 10 different blockchains
at least, including Ethereum, BNB chain, Polygon, and many L2s to bring like a list of blue chip
tokens, including Ethereum, USDT, USDC, BTC, BNB, and Matic from external chains to Oasis Sapphire.
Like it's going to be a very straightforward and smooth user experience when people go to
Seabridge and basically you only need to select a source chain, for example, Ethereum and the
token you want to bridge, as well as the destination chain, which in our case will be Oasis Sapphire
for the bridging transaction to happen.
And we're looking, as from the East side, we're looking to create new or work with new partners
and new projects to enable new use cases, which hopefully will bring more assets to the
seller Seabridge token bridge.
I guess as a follow-up question, we should probably get into a bit about how Seabridge works.
Wanoli, how do you see, how does Seabridge work and how do you, how do you see the values
that Seabridge brings to Web3 industry as an interoperability protocol?
So Seabridge has been focused on token bridging for quite some time and we support both
fungible token bridging as well as NFT bridging, although there hasn't been much request for
NFT bridging yet for Sapphire, but it's a like solid use case going forward.
And for token bridging, we have supported like over 150 different tokens for a variety of
different blockchains, like I mentioned.
And that actually is with a goal of like helping users easily onboard to new ecosystems like Sapphire.
And I think like bridging solutions or interoperability solutions like us definitely are kind of the
infrastructure level for any new ecosystem when they try to launch on mainnet and basically introduce the
Quibi and new users to their ecosystem and try out different DApps like DeFi or Gamify, then like
widely accepted or traded tokens like Boovoo chips, USDT, USDC, stablecoins or ETH, BTC are definitely the most
needed for any new ecosystem and that's when bridging solutions can basically help the most.
And like basically with Seller and with Seabridge, we have helped many blockchains build TVLs and also attract
deep enough liquidity for users to enjoy like a smooth trading process and low slippage when they're
onboarding a new chain and for now, up till now, we have helped bridge a total value of over $15 billion worth of value
across different chains for 150 different tokens.
And in terms of like other interoperability aspects that we're also building on and kind of spearheading, I think
interchain messaging is also like a really innovative design that could help developers and DApps to basically tap into a
multi-chain native feature or design when they are trying to launch different launch on different chains.
And for interchain messaging, we are actually the first interoperability protocol that has launched a mainnet ready deployment on multiple different chains.
like we also launched with nine different use cases back in, I think, April 21st, I mean, April 2021.
So pretty early in the game.
And also that also gave us enough time to build use cases and have enough developers be interested in seller interchain messaging.
And so far we're seeing like really attracting use cases for different verticals, including NFT marketplaces, DeFi and Gamify.
For example, for interchain messaging, we have crushing NFT purchasing.
That's already a mainnet ready feature built by Tofu NFT.
And basically what IAM does for NFT marketplaces is that it allows NFT marketplaces to let their users initiate a cross-chain purchase or bid transaction for any NFT listed on other chains.
And when there is some kind of like error, whether the user fails a bit or like the transaction fails, like as long as the fund is locked on the source chain, the user doesn't need to pay for any bridging transactions because like it's not until the user has won the bid or successfully purchased the NFT will their funds be transferred to a destination chain.
And be used to pay for the NFT, which minimizes a lot of costs compared to the user having to manually juggle around different protocols and complete the entire cross-chain NFT purchasing process.
So with IAM, the entire UX is minimized to only like a one step, one click transaction flow.
And other use cases include like cross-chain yield farming with PancakeSwap.
Basically, they could enable users to enter and accept yield farms on different blockchains without having to deal with like reward token bridging, which minimizes the cost in their yielding process.
And for Oasis Sapphire, we're also trying to expand more IAM use cases.
And we're also actively in talk with several like really active developers on the Oasis Sapphire ecosystem.
And some interesting use cases we've heard include private voting and governance and dark pools that could limit front running and some others as well.
And we're generally like very open to new ideas on Oasis Sapphire because it's a brand new ecosystem that's kind of focused on like utilizing Sapphire as a privacy focused chain and with interoperability in mind supporting various other external blockchains.
So if you are a developer and happen to have a lot of ideas, be free to share with either the Sapphire team or us and we can help you expand your ideas or offer you engineering support.
Yeah, that was a lot of information and a lot to break down.
But, you know, I think, you know, on the Oasis side, we're so happy to be partnered with Seller for these use cases, especially like you said, like now we have Seabird available.
Now we have the ability to have like blue chips like ETH, BTC, B&B, Matic, as well as like USDC, USDT to start empowering some of our ecosystem projects.
You know, one that stands out is like CoinCenter, which is a payroll project that's, you know, utilizing Sapphire for some private benefits.
And they had like a strong need for USDC and USDT.
And now with Seabridge, you know, integrated with Sapphire, now they're empowered to start building out that use case.
Additionally, I know you mentioned like some of the NFT interoperability things.
You know, one thing that I've always talked about is like with Sapphire, you can start building more sophisticated NFT auction models, like sealed bid auctions, where you can't see what other people are bidding.
And help prevent some of the frustrations and poor user experiences that have existed in the past, where like you have sort of everyone sort of late waiting for each other at the very last second.
And I'd love to, you know, expand on those use cases with Seller as well.
But maybe we're getting a bit ahead of ourselves.
Maybe we should explain a bit about Oasis and how it enables privacy.
So, Harry, do you think that you can give a brief introduction to smart privacy and how Oasis enables it?
So, I think at the center of it, I'll start with Sapphire, which is the first production-ready confidential EVM.
And because it's programmable with smart contracts, you can decide which information is public and which information is private.
So, that's the basis of smart privacy, which is on an app-by-app basis.
Developers can choose what to disclose, how, when, and who to disclose it to.
So, rather than using complex MPC systems or like fully homomorphic encryption or zero-knowledge cryptography, it's very straightforward to develop for.
So, typically speaking, we're talking about saving months or years of development time to get to market versus some of the more complicated solutions.
So, with smart contracts that are running in a trusted enclave with their own private data, that means the node operators can't see what's happening in the contract.
People observing the blockchain can't see what the contract's doing.
And that forms the basis of, like, a lot of really, really interesting things that you can do with it.
So, with OPL, which is obviously powered by Seller, you can use the features of Sapphire from other chains.
So, as we get more blockchains and they all have different strengths and assets that are spread out across the ecosystem, that means that you can move parts of your application which need privacy or need confidentiality or some of the more unique features of Sapphire onto Sapphire itself and keep the rest of the application where the assets are.
Or, the other way around, you can have a fully private application which can control assets and contracts on other chains through either the IM or through just sending tokens at the right time and the right place.
Additionally, Sapphire has functionality which is really expensive on other blockchains.
And because it's built in, it's quite cheap, it's very straightforward, and it's really essential for a lot of use cases.
So, for example, like encryption, if you want to selectively encrypt information for a specific person, one of the cases is like a regulation, you could allow a regulator to see transactions without letting anybody else see them.
And then with signing and the VRF, which is a verifiable random function built in, it opens up a world of possibilities that just aren't possible or practical without confidentiality.
And, of course, private storage together with easy-to-use smart contracts means it's much, much simpler to do stuff on Sapphire.
That's a great sort of overview of everything that we're doing at Oasis.
So, thank you so much, Harry.
I guess we probably hit on this a little bit in previous questions.
But, Wanalee, I'm wondering if you could maybe expand a bit about why interoperability is crucial for scaling Web3, like why cross-chain bridges are important for building accessible Web3 user experiences, and where we are today compared to maybe five years ago.
So, yeah, that's a really good question.
So, I think, like, based on the, like, number, the sheer number of users of cross-chain bridges, we probably can't understand why, like, I mean, sorry, cross-chain bridging solutions.
We probably can't understand why, like, bridging solutions are important in general because I think first, like, the first and foremost reason for that is we're living in a multi-blockchain space right now.
And there are many, like, parallel or connected blockchains, whether they're, like, L1, L2 construct or whether they're running on parallel, like, Polkadot or Cosmos.
I mean, the two ecosystems themselves are not connected by default.
So, with these different opportunities on different blockchains and with them each focused on certain verticals and have, like, flourishing DApps that is, like, that has been successfully attracting a large user base,
it's very important to remove, like, the segmented space by adding more connections across these ecosystems to allow fluid, I mean, to allow smooth movements of users and assets.
And, like, like, it's very similar to why we're in need of, like, a good asset transfer process for cross-border asset movements.
Like, it's similar in Web3.
People just generally want to explore more opportunities on different places and with different ecosystems.
So, bridging solutions can serve as a really good connection point for the different ecosystems.
And we can easily allow users to basically go from any blockchain of their choice to a list of over 40 different blockchains.
And Sapphire is one of them.
And they can move assets, like, all within 5 to 10 minutes.
And the entire on-chain process is also, like, very minimized for users.
The user will only have to approve one transaction on the source chain for the entire crushing transaction to complete.
And that, to the user level, is very, like, easy and also straightforward.
And also, like, it helps to lower the barrier for people who are not so familiar with Web3 or on-chain logics.
So, we're trying to kind of, like, bring blockchain to mass adoption, which has been our slogan for quite some time at Seller.
And interoperability is, like, a key component to that vision, I would say.
And it does help a lot for users who are, like, less familiar with the technical aspects of blockchain.
And in terms of, like, the status we're at today for interoperability compared to 5 to 10 years ago,
I think 5 to 10 years ago when people were trying to kind of move assets across different ecosystems,
The only possible option I could remember probably was through centralized exchanges.
There, like, is a very tedious process where user will need to manually approve, like, a transaction to move their funds at custody of the centralized exchange.
And then move it on-chain to one blockchain.
Or if they want to move to a different blockchain, they will need to withdraw the assets to their custodial wallet.
And then submit the transaction for the funds to be moved to a different blockchain.
But at least there are, like, two or three transactions that the users will need to deal with.
And there also, like, will need to be a long wait time for the entire bridging experience to be complete.
So compared to, like, 5 to 10 years ago, definitely we have more options right now for bridging.
We can bridge fundable tokens.
We can even bridge arbitrary messages, like what a lot of DApps are trying to build, like, crushing native features.
And on the other hand, like, there are more blockchains that have emerged, all with their unique benefits for people looking for yielding opportunities.
And that landscape allows for the development and growth of interoperability protocols.
So we are seeing more bridging solutions at your choice as well.
And for different use cases, you definitely can go with different bridging solutions.
And it also encourages bridging solutions to advance with your tech stack to be more user-friendly, to be more efficient, and also to be more secure.
So I think, like, we're at a stage right now that there are many solutions for users to choose from.
And we are, like, way a step ahead compared to before in terms of the liquidity efficiency on bridging solutions
and also the overall user experience, that there are still some ways to go to basically make the process more smooth and also more secure.
And that has been, like, the focus of many bridging solutions or the interoperability space for quite some time.
And that's why we have also been kind of, like, starting a new initiative on zero-knowledge proof so that we can offer another security layer for our current bridging solutions.
I, you know, as an avid sort of Web3 user myself, I can't speak enough about how much better that interoperability user experience has been.
In the past, it used to be sort of a nightmare where, like, you did, you were scared.
Every time you clicked a button, you were like, am I, did I do something wrong?
Did I create the right destination chain?
Do I have gas on the other chain?
There's so many different ways that, you know, the experience was pretty miserable.
And so, yeah, it's definitely, I guess, maybe through competition of all these solutions as well as just, you know, innovative ideas that people like Seller have come up with.
You know, the experience has improved tremendously over the last few years.
I guess, you know, we did also talk about this before, but I'd love to discuss, like, what are some of the most pressing industries in Web2 and Web3 that need customizable privacy?
And this is for both Harry and Wannily.
I think I'll start there with one thing that Web3 hasn't really done very well is integrated with the rest of the existing infrastructure that's out there.
So, if there is one thing that Web3 can do, which is to be a bit more compatible with Web2.
Of course, on Web2, you're used to passwords, you're used to centralized databases, and this level of trust with service providers where it doesn't sort of mesh well with Web3,
which is all about, you know, custody, having control of keys and transparency and sort of cryptography that enables that.
So, with having confidential storage, it means that you can have passwords on Web3 now.
You can have, like, the sort of centralized services that you're used to using, but in a decentralized manner,
because you know that the information kept by the contracts can be secret.
So, an example of that would be using Sapphire as, like, an access control system.
So, if you do want to enable people to purchase data, you could generate AWS S3 access tokens from a Sapphire contract, you know,
after receiving payment, which has been bridged over using the SellerBridge.
So, I think we're still in the early days of Web3, which is interesting.
I was thinking about the introduction of bridges, and if you go back to the introduction of telephones and fax machines,
it's the more connections that we have with different systems and the more systems that are connected together,
the more valuable the network as a whole becomes.
And with privacy, it's like the next missing piece of the puzzle that allows us to have so many more use cases.
And one thing I was thinking of was simply custody.
So, with contracts that can have their own key pairs, you can, for example, ask a smart contract from a DAO on Ethereum to sign a Bitcoin transaction,
which is only possible because you have the messaging bridges, and only possible because you have confidentiality.
So, we're still in the early days of finding out what are the really, really interesting things that are going to enable the next exponential level of utility.
And I'm just happy to be exploring this space and trying to find out what sticks and what works.
I think that's sort of, anytime there's a sort of a breakthrough innovative technology, you know,
it's sort of a trial and error period where you're trying to figure out what are the, maybe the simplest use cases
and what are the most beneficial use cases to sort of explore.
I know at least like when Ethereum came out, you know, there was all these sort of ideas of what could be done.
But it took a few different iterations until we, like, you know, for example, in DEXs, you know, came up with the AMM model
and things of this nature and lending as well, like how can we enable lending?
You know, it always takes a bit of time to sort of figure out the best architecture for these things.
Wanalee, do you have any thoughts about, you know, what are some interesting use cases for privacy in Web3?
Yeah, I think what Harry shared was definitely very to the point.
And to my eyes, I think like I would be really interested in seeing something related to decentralized identity.
So DID, if like Sapphire could attract some developers to build privacy reserved DID projects
that could allow users to only kind of review part of their DID for certain activities or campaigns
where DeFi protocols they want to participate in that has gating, that has user gating, both inside of the logics,
then I think it will be a very interesting initiative because I feel like the current gap between Web2 and Web3,
like a lot of the logics, like a lot of the logics derives from the ability to utilize users' existing data,
like their transaction histories or like their other behaviors across different protocols.
So if there is a way for a user to kind of basically use their past transaction identity to participate in some user gating events,
but without revealing all of their information with that identity, I think that would be like a really interesting idea.
Yeah, yeah, absolutely. I love the idea of using DID.
Maybe, you know, I have some thoughts about how messaging can be leveraged for that,
but maybe Wanalee, do you have any ideas about how Acceler can, you know, help enable that use case
to maybe bring DID to the cross-chain world?
Yeah, I think like a lot of the protocols are using NFTs as a way to store like identity data.
And I think that could definitely be part of the interoperability realm,
whether it is like bridging the NFTs directly to Sapphire or from Sapphire to external chains,
or just bridging a message in and out of Sapphire to prove the ownership of a specific NFT
would be something that different protocols can try out.
Yeah, absolutely. I think I have like this idea of creating like, you know, a confidential soulbound token.
So it's the same as like Vitalik's idea of a soulbound token,
but where the data is all like only the owner of the data can access it
and they can sort of grant and revoke permissions and maybe send like Boolean expressions to other chains.
So maybe like you have a, I don't know, a launch pad on Ethereum that, you know, wants to be regulatory compliant.
So they want to make sure that maybe U.S. citizens are not, you know, participating
or that everyone participating is above the age of 18 or something like that.
And that can send a message asking for, you know, a yes or no, whether a certain wallet meets that criteria.
That can send a message to Sapphire.
The sold-on token on Sapphire can basically do the calculation and send over a responding message that says like,
yes, this person meets that criteria or no, it doesn't.
So you don't get like the age of the person or you don't get what country they actually live in,
but you do learn like whether they meet the criteria to participate in like a launch pad or something like that.
That's just like one idea that I've had.
Yeah, I think it's a great idea.
Yeah, and I'd love to see maybe, you know, people in our hackathon that's currently ongoing
or maybe just developers that are interested in this space, you know, leverage Seller and leverage Sapphire
to help start building like some of these solutions.
So I guess, you know, we talked a bit about, you know, Seller, what you guys have done in the past,
what Oasis has done in the past.
Maybe we can start talking a bit about the future.
What's Seller's vision for the future of Web3 both on like a, you know, individual level
as well as like maybe some insights you could provide for the industry as a whole?
I think this is definitely my personal perspective, but also it can be echoed by a lot of people.
We're seeing like the buzzword these days for zero knowledge truths.
And I think this is indeed an area worth like exploring.
And on Seller's end, we have been like contributing, not contributing,
but like devoting a lot of efforts and also resources in our ZK initiative since mid-year last year.
And it has been like around a little bit over one year.
And we have launched Brevis, which is our Web3 coprocessor initiative that utilizes zero knowledge succinct proof
to allow like basically arbitrarily complex data computation on any chain and also across any chain.
So this initiative sounds big, but we do have a testnet version ready for testing.
And you can go to, I think, brevis.network to try out the four or five different use cases we have both.
There is a zero knowledge proof supported ZK bridge.
There is also like a Uniswap proof idea there for user gating purposes.
So we have both a NFT claiming process to allow users who have traded a certain amount of token on Uniswap,
on Ethereum for the past 30 days to be able to claim that token.
So like all of these demo use cases are examples of how Brevis, our zero knowledge supported coprocessor,
can work across different chains.
And the, I wouldn't say magic, but the key value of zero knowledge proof products for Brevis
is that users or projects or smart contracts don't have to like build their trust on a third entity except for like maps
and also the source chain, the consensus layer of the source chain that they're working on.
So I think that's like what attracts most people about zero knowledge proofs.
And we are seeing a lot of use cases utilizing zero knowledge proof.
And for us, we're focused more on interoperability because we started there,
but we have expanded to other use cases as well.
We're now trying to like prove, do computation for single chain use cases without the concept of
like having to make sure use cases always go across different chains.
So we are also kind of like doing some more knowledge sharing on Brevis during our offline events,
like for the Singapore week of token 2049, as well as Singapore, I mean, Singapore.
So if you're interested, feel free to follow us on that.
But I think zero knowledge proof is definitely a very important topic going forward for various verticals
or for like the entire space overall.
It's kind of, like you said, it's kind of like a buzzword.
It seems like everyone's working on our zero knowledge, whether it's scalability or privacy,
or maybe an interoperability space that gives, you know, added security benefits.
There's so much that can be done with this technology.
I know, Harry, though, that you're very excited about Brevis.
So maybe you can share some thoughts about, you know, maybe some use cases that could utilize Brevis for Sapphire or for Opal
or just like in general, what you find interesting about the technology.
Well, one of the problems we have with bridges in the past is it's like another consensus, another point of trust.
And using ZK proofs of the blockchain consensus algorithm itself, which is behind Brevis,
that means that you can take a lot of trust out there and it can be more reliable.
So I'm super excited to see ZK snarks used for interoperability.
And I still think there are some questions around, well, how do we make applications that are suitable for this?
So I know a lot of people are making, just starting to make applications which run across multiple chains using like the messaging bridge.
And Brevis is really like the next generation of after learning one of the problems and we find out what do we want to do next that solves all of them.
But in terms of like applications themselves and how do we use them across multiple chains?
Well, with Brevis, it means that you don't have to have a bridge on every chain connected to every other chain.
You can fairly quickly provide the proofs in the zero knowledge format.
But we're still looking at applications and making them interoperable with each other.
So I know there's a lot of research about intents and sort of compatibility between different blockchain applications.
And I'm excited to see what happens.
But really, for me at the moment, Sapphire, with the upcoming 0.6 release, will have full support for the ZK primitives.
So, of course, we will definitely be looking at using Brevis on Sapphire.
Although you can't do that right now.
In terms of use cases for Sapphire, well, this opens up lots and lots of really interesting things.
So having swaps between multiple different chains where if they're not sort of part of another bridge or if they're anchored to Ethereum one way or another,
that means that you can use bridges without them having to be directly compatible with you.
And you can use them from anywhere at all.
So with privacy and confidentiality, that means you can do swaps across multiple different chains in private,
which is not immediately possible with the current messaging bridges at the moment.
Because you have this linking of on one chain you perform an action and on the other chain you perform another action and they're both linked.
But with Sapphire and some sort of attestation protocol like Brevis, you really get the almost optimal privacy potential.
Yeah, yeah, yeah, yeah, absolutely.
I mean, I think maybe my technical understanding is not as great as yours, Harry,
but it seems like, you know, basically it just accelerates the level of privacy that we can offer as well as, you know,
Seller can offer by combining the two pieces of technology.
I guess one follow-up I had about that is about, I've gotten questions in some of my BD meetings about, you know,
like if we do this sort of confidential governance use case, how do we know that the calculation has been done correctly?
That, you know, everyone's votes was weighed correctly when it was, when the voting period has happened?
Maybe Brevis can offer a better solution for submitting a zero-knowledge proof that says, like here,
that everything was done in a secure and reliable fashion.
Is that the use case for Brevis?
Yeah, I think it's definitely something we can explore.
Sounds like a really good use case.
Harry, do you have any thoughts as well on that?
Well, I'm still looking at Brevis at a fairly abstract level,
which is being able to use other applications without them having to directly integrate with you.
So, for example, proving that an event was emitted from a contract on one chain
and proving that to another chain without the application on the source chain having to know about the other chain
or know about a bridge at all.
So it really makes it more interoperable because you don't have to sort of adjust the contracts
and redeploy them on both chains to support these new use cases.
So in terms of, like, accelerating development,
what Wan Li said about, for example, the Uniswap use case,
where proving that someone has contributed a certain amount of liquidity over the past 30 days,
it's great because it doesn't need support from Uniswap.
So I think the voting example is just sort of the tip of the iceberg,
where really it's more about using contracts and actions on other chains
without having the integration overhead.
Yeah, that's super exciting.
And I can't wait to see, you know, as this sort of collaboration moves forward more,
what sort of use cases we can come up with.
You know, one of the things that I find probably the most exciting is just that
it's a great example of showing how, like, two different privacy-preserving technologies,
ZK and TEs, can be used in combination to, you know,
create something better than either one can do on its own.
So I'm excited to see how this sort of field grows in the future.
I guess there's, like, a, you know, final thoughts.
Are there any upcoming events from the seller side?
Any updates or, you know, hackathons, conferences that you guys are attending to
Yeah, we're going to have several speeches and panels,
keynotes and panels during ETH Singapore as well as Token 2049.
And that's around the week of, from September the 10th to September the 16th.
And we'll post some updates very soon in terms of, like,
the list of events we'll be present at.
And we're happy to meet with developers who are the broader community to explore
bridging or our ZK internship breakfast.
And we're, like, more than happy to directly talk to Sapphire builders to explore how to
utilize IAM for your use cases.
And anyone who's in the audience today, you know, please follow Seller on all of their
I think there's a speaker here, so you can just click that speaker link and keep updated
with everything that they got going on in their network.
Harry, do you have any last closing remarks from the Oasis side of things?
Well, we will be at DatCon in Berlin in the 9th or the 10th through to the 15th, which is
the Berlin Blockchain Week.
I think we'll have a stall there.
We'll also be doing some talks.
And I'm sure if you want to get in contact with us, we can say hi in Berlin.
Likewise with SmartCon in Barcelona, which is towards the end of September and the first
couple of days of October.
If you're in Barcelona or you're going to be coming along, definitely get in touch with us.
And I think Harry, he will be speaking at at least one of those events.
So anyone who wants to hear Harry speak some more about, you know, the power of Sapphire
and privacy, please tune in.
We're also going to have a lot of exciting announcements at East Berlin and SmartCon.
So hope to see you guys all there.
And thank you for joining us for today's space.
We're super excited to have this latest update to our collaboration with Seller.
And yeah, hope you guys all have a great rest of your day.