Union: Interoperability Accelerated | Karel
Episode publishedPodcast: 0xResearch0xResearch
Transcript preview
Preview only
I do think that we're going into this era soon also where kind of apps will almost be like like Polkadot's original vision of, like, having on demand roll ups with, parachains, and para threads. I think that's something really cool that we could move into in the module space right now that's very much underexplored at the moment. Nothing
set on Xerox Research is a recommendation to buy or sell securities or tokens. This podcast is for informational purposes only, and any views expressed by anyone on the show are solely our opinions, not financial advice. But, Kachio, Ryan, and our guests may hold positions in the company's funds or projects discussed. What's up, guys? Welcome back to another episode of Xerox Research. As a disclaimer, today's episode is sponsored by Union. I'm joined by Karel, the founder and a core contributor at Union. Thanks for coming on, Karel. Yeah.
Thanks so much for having me. Before
we get started, do you mind running over what Union is and what you guys are building?
Yeah. Of course. So Union is, an interoperability and settlement layer. So for kind of the regular user, what this means is, again, a project that connects different blockchains. What we focused on is, a, being really fast in doing this. So, messages and transfers get sent really quickly between blockchains, but as well as being extremely secure and decentralized. So we don't rely on, like, oracles or some service that we are running that could potentially be hacked by any group, and that's especially important if you're doing bridging.
That makes sense. And what's the motivation behind it? What apart from not being reliant on other protocols, what are the problems you guys are trying to solve?
Yeah. So, a, obviously, everyone's kinda building, like, app chains, app specific roll ups. They're following in hyperliquids footsteps of if you have, like, your own environment, you can build a really cool product. So this idea that, like, the l two centric roadmap of Ethereum is kind of what everyone is doing in crypto is very real. With that, you get a majorly complex, like, architecture for how these blockchains need to interact and communicate with each other. Extremely annoying for users. Like, you'll really wanna do bridging, but also actually really annoying for developers because you
That makes sense. And how does it achieve or aim to achieve these objectives? What does the back end architecture look like?
So, basically, in designing this, the first thing, like, if you're not gonna use like a multisig or Oracle or something means that you need different like security mechanism to verify that a transfer occurred. In our case, we use live clients for that. Live clients are kind of like the the best that you can do at the moment. Basically, what it means is, like, we generate these certain mathematical proofs about, like, validator sets or the consensus algorithms of the different chains that we connect to. So in the case of Ethereum, that is tracking the same committee. In the case of Bitcoin, tha
Keep exploring with a free account.
A free account preserves the short preview. Upgrade to Pro for the full transcript and episode chat.