Sorry for the tech issue and we can now ongoing.
Should we just give it a couple minutes and see if we can recover some of those last listeners?
Maybe I'll just give it a minute and then we'll head back into the panel discussion.
All right, let's just pick things up where we left off. Dogue from Mystico was telling us a little bit about their solutions with privacy. So you want to take it as way to do it.
Oh, hi. So just pick up what I left. So, oh, yeah. So in general, in our particular, so, QUNC is organized into a local tree. Where a local tree is like you can easily to verify a membership of a member.
And also each coin is, I mean, have some public key of the user. So the user, if a user wants to spend a coin, the user has to prove that he knows the private key and also the membership of the coin in the whole
Marko tree which is with the journal to prove so that no one else will know which coins he wants to spend and also I mean how he spends that coin in this way no one can recover the transaction link between any two Sunday and the receive transactions and this is basically what we
do with the prior transaction and to make it auditable, we use a little trick which is called secret sharing. Secret sharing is like you have some message or see you have some data and you share it with different parties. Only a
say over half or two third of the parties join together and agree to recover the original secret so they can recover the secret or if licensed that threshold no one can recover the secret so what we are doing is we
asks the user when he spends the coin. He also needs to generate a secret sharing and share the secret to different parties for the government or for the court. In this way, if the agency wants to audit
the whole transaction link. They can join together and recover the user's transaction link. But this is just about the history of the transaction. This deal cannot spend users' core. So this is what we do with Auditable and also the private transaction.
It's really interesting. I know that Mr. Co, it's implementing its snarks across different platforms to create a bridged layer, I suppose, across them. Does this introduce any issues into the auditability process?
process for you where you're relying on the security of these vastly different L ones and some of them may not have the same security assurances as some of the others. How does that impact the way that the auditing process works for you?
Okay, so I think at first we use Quartz branch as a information bridge. So it's just transferred information from a center, so it's a source channel to a destination channel. And even the underlying
but the coin in Oracle Ducco is locked in a shadow pool, so it's still security for the user. The only concern here is like if the user themselves lost their set of plan coin is due to
to the base blockchain, we can do nothing. But this is as secure as our original channel, we hope to call just idea one more layer of security. We will not don't go into the whole security.
Cool, thanks for showing your insights. Let's move on to Rick from Opside again, who can maybe tell us a little bit about their user-facing tools with their own ZK bridge.
and also their more developer-facing tools with their general purpose and app-specific roll-ups. Hey guys, I think