Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Breaking Barriers in Blockchain with ZetaChain
Recorded: April 29, 2025 Duration: 1:04:10Space Recording
Short Summary
Zeta Chain is making waves in the blockchain space with its innovative omni-chain platform aimed at enhancing interoperability and user experience. The project is set to redefine how developers interact with multiple blockchains, offering a seamless environment for token launches and cross-chain applications. With a focus on security, growth, and strategic partnerships, Zeta Chain is positioned to lead the charge in the evolving crypto landscape.
Full Transcription
Thank you. Thank you. Thank you. Thank you. Thank you. you Another edition of our wonderful spaces here on Satoshi Club.
It's always a pleasure to have you on board.
And as always, I'm excited to be your host today.
Today we have our guest from Zeta Chain.
So Zeta Chain is one project that really excites me.
It's a pioneering omni-chain platform,
revolutionizing blockchain interoperability
by enabling seamless blockchain DApps
and unifying fragmented ecosystems.
ZetaChain is building a connected Web3 future.
So let's dive in to what their vision is
as we explore this space today. Let's go. So let's dive into what their vision is as we explore
this space today. Let's go. So our guest today is already on board. Hello, can you unmute your mic
and introduce yourself briefly? Hey, thanks so much for having me. My name is Dennis. Hope you
can hear me. And yeah, I am a core contributor to Zeta Chain. I focus on developer experience, which means building tutorials, tools, documentation,
all the things necessary for developers to be successful building on Zeta Chain.
All right, all right, Dennis.
Welcome aboard.
I'm so happy to have you on the space today
with Satoshi Club. We're excited to have you with us, man.
Awesome. Let's do it.
All right. All right. So can you tell us a little about yourself and your journey in
your journey in Web3 up until the point that led you to Zeta Chain?
Web3 up until the point I led you to Zeta Chain?
Yeah, absolutely.
So I've been in crypto since 2019.
I started my journey in the Cosmos ecosystem,
basically building websites, web applications for Cosmos
websites, web applications for Cosmos and kind of gradually transitioned into building
developer tools back in 2020.
And me and my team built the CLI for building blockchains using Cosmos SDK, which has been
used by a bunch of projects to build their blockchains.
It was pretty cool. And at some point, I believe more than two years ago actually,
I joined Zeta Chain because I believed in the vision and it's it's tech and that's that's basically how i ended up here and
yeah
splendid splendid um thank you for that introduction so um now moving on to a couple of
questions which i'll be asking in the course of our discussion. What inspired the creation of Zeta Chain and how does its vision of connecting fragmented
blockchains into a seamless ecosystem address the current challenges in the crypto space?
So basically in the past we had just a few blockchains, right?
With Bitcoin, Ethereum, some other blockchains.
But as an industry, as we kind of evolve and as more people start using blockchains for different purposes,
we kind of quickly realized that one blockchain that fits all purposes is not really
the way to go. It's just impossible to build such a blockchain the same way as it's really
impossible to build an application that has absolutely everything, right? You can build a
very general purpose application that has many features and
it might seem like it has almost everything, but it simply cannot have all
the functionality one would expect from a whole ecosystem of applications.
And the same thing is in blockchain, right?
We don't have a single application. We have a bunch of apps and some
applications require.
Uh, PI throughput, right?
Maybe it's a game.
Maybe it's a high frequency application
that needs very.
Very quick blocks block time, right?
Like, uh, uh, I don't know 10 millisecond block time or something
some applications need more privacy right and some applications need more liquidity and like all of
this cannot possibly fit onto a single blockchain and that's how we started to see proliferation
of chains being built that solve a specific problem, right?
They're built for a specific application,
call them app chains,
or just chains that are different.
They're still general purpose chains,
but they focus on different things, on privacy,
on being fast, on being super developer friendly or very secure and so on.
So we're seeing now hundreds and thousands of blockchains all popping up and all kind
of hosting different apps.
And it's great, but the problem with, not a problem, but like the challenge of all of
this is fragmentation of user experience and fragmentation of everything, right?
Of developer experience, of liquidity, of kind of general understanding of how it all
works together and there are different approaches
to solving this fragmentation problem you have different protocols you have different
bridges right and some of them offer just token transfers,
which is fine, right?
You wanna transfer tokens between blockchains,
but some offer message passing,
which is also pretty cool because you have applications
on different blockchains that want to talk to each other
and you need to pass data and value between them and their message passing
protocols and um there are other systems in place but at the end of the day it does seem like this
is still a fragmented experience with just some connectivity built on on top of it, right? So it doesn't look like a solution that really ties together everything in a platform that
is really kind of connecting everything very tightly.
It doesn't seem this way. So kind of slowly going back to what Zeta Chain
is all about, the vision is that Zeta Chain provides
this platform that connects everything
and lets you build anything you want,
but we provide all the primitives for your application
to be cross-chain by default.
We call these applications universal
because on Zeta chain, when you build an app,
it's automatically connected to all the chains
connected to Zeta chain.
And that's the main idea, right?
Provide a platform for developers
to build these applications that are augmented with this interoperability baked in.
So you don't have to worry about bridges, about establishing message passing systems.
You just build one contract and it works with all the chains.
So to me, this vision,
it resonates quite strongly with me personally
because I think interoperability
is a big and hard problem to solve.
And it's especially difficult to provide experience
which makes
building these cross chain applications easier, right?
Instead of just kind of doing it in ad hoc kind of way.
Ideally, as a developer, you don't really think about all of this infrastructure.
You kind of focus on business logic and everything else is provided for you.
So that's what Zeta Chain is doing.
All right, all right.
That sounds very awesome.
It seems like Zeta Chain has the community at heart
and I'm thinking of building something
that makes enhancing blockchain and universality of all the different chains all in one space and reducing the bulk or the bulk of the work for developers.
I think that's quite commendable. So I commend your team for that. And what you're building seems like something that's going to have a broad use case. So thank you for that insight, Dennis. So moving on to a different question now.
So could you quickly explain how Zeta Chain's Omni Chain smart contract works and what makes
that a game changer for developers building the apps? Specifically, like broadening on what you
just talked about. So how do developers benefit and how do they need to interact with the
multiple, how do they get to be able to interact with the multiple blockchains available?
Yeah, I'll try to explain this on a high level, but it's going to get technical anyways, because
you kind of need to go in the technical details to understand how it really works. But on a high level, there are systems like message passing
where you have two blockchains and you deploy applications in both of them.
And you use one of the message passing providers
to send data between your applications on different chains.
And when you add more chains into the mix,
you have to deploy more apps, more connections,
and it quickly becomes very hard to manage.
And what Zeta Chain is building, is providing,
is an alternative to these sort of systems
where you have this complexity that inevitably creeps in.
With Zeta Chain, the architecture is very different. Instead of deploying
your application on different blockchains, you just deploy it once on Zeta Chain.
So Zeta Chain is EVM compatible, so it means that you can take an existing Solidity contract, deploy it on Zeta Chain, it's just going to work.
And the core idea is that you deploy this app and this app on Zeta Chain, this contract is capable of accessing calls and data and value from users and contracts on connected chains like Ethereum, Base, Polygon,
Solana, Sui, Ton, Bitcoin. All of these chains are connected to Zeta chain and users can kind
of remotely call your application. Let me give you an example. So let's say you have an application that swaps tokens, right? And you have a user on Bitcoin and they only have BTC, right? They're Bitcoin maxi.
someone some used DC tokens right maybe they owe someone uh used to see right they want to make this
transaction but they don't want to leave bitcoin right they don't want to use a bridge to bridge
their bdc they don't want to worry about like what how much they're going to spend on gas on ethereum
that sort of thing right so ideally they don't have to think about it and with the zeta chain they actually don't they don't have to think about it because your application abstracts away all of
this complexity from the user so what a user does on bitcoin is they use a web application that you've
built right like a web app they uh use the their favorite wallet maybe it's Unisad or Xverse or OKEx, whichever
wallet they're using for Bitcoin, and they just press a button to send someone some USDC.
And what happens under the hood is a user's wallet broadcasts a Bitcoin transaction with the amount of BTC that will eventually be converted into USDC.
So this Bitcoin is sent to a Zeta chain address on Bitcoin called Gateway address.
This address is controlled by Zeta chain validators in a decentralized way through TSS signing, right? So
the private key of this address is split into fragments and distributed between validators
of Zeta chain. So this BTC goes into this address with a message that instructs which universal app to call and some other data, right?
So in our case, that would be your swap contract
and the instruction would be just to swap incoming token
and to use DC and send it to a specific address.
What Zeta Chain does automatically
is it monitors incoming transactions and calls on Bitcoin. And if it sees
BTC coming in with a memo, with the message, it relays this call to your universal swap contract.
And it represents BTC as something we call ZRC20BTC, which basically just a token that is meant to represent Bitcoin.
For the user, it's completely invisible.
They don't have to know about it, think about it.
Your Universal Lab just gets BTC in the ZRC20 form.
It executes the logic of the contract, which is swapping for USDC, and then it transfers this USDC token to the recipient on Ethereum.
So all of this happens automatically
and completely invisible to the user.
So you, as a Bitcoin user,
you only have to sign one Bitcoin transaction and that's it.
And after these transactions are processed, you only have to sign one Bitcoin transaction and that's it.
And after these transactions are processed,
recipients on Ethereum will get a USDC amount.
So this is probably the best experience possible because we only ask the user to do the bare minimum
for this process to actually succeed, which is
send some tokens. And the rest is happening completely automatically. Your universal app
is triggered and a withdrawal of USDC happens, of course, also automatically. From a developer point of view, it's also very easy to build such a thing.
In fact, one of our examples is a cross-chain swap application.
It's a very, very small app considering how much functionality is built in.
So from a developer point of view, what you do is you just build a Solidity contract, just one contract, which has a function that gets called whenever a user from a connected chain interacts with your contract has access to the ZRC 20 representation of the assets that are being transferred
and it also can trigger withdrawals.
So in this example, it will get ZRC 20 BTC
as an incoming token,
then it will process the swapping logic
and in the end it will withdraw USDC to a target chain,
to a target recipient, which is Ethereum.
So it's really easy to build because you just handle incoming calls from connected chains and possibly generate outgoing transactions to other blockchains. And you're not limited to just one output.
One incoming call from Bitcoin can trigger more than one outgoing transaction. Maybe you want to
send one token and distribute it to users on different blockchains. But maybe you don't even need to make an outgoing call at all.
So for example, another example of this is NFT, right?
You might want to build an app that mints NFTs
and it can do so in response to a call from Bitcoin
or any other chain.
So an NFT is minted on Zeta chain,
and then maybe users can transfer it to other blockchains.
So it's very flexible.
And what we provide as a platform are these mechanisms
that abstract away all the complexities of cross-chain interactions.
So instead of you having to kind of worry about which bridge to use,
which I was going to like work with other connectivity solutions,
because like you're using one bridge for Bitcoin and you're using another bridge for Sui.
And then what's with Tan
is probably going to have something else.
With ZA chain, all of these interactions
happen through a single interface.
So from a developer point of view,
it's very easy because it's just one function
that gets called.
You get chain ID, you get tokens, you get a a message and then you figure out what to do from there so from
from DevEx point of view couldn't couldn't really be easier and I mean I
can talk about this on and on but there are many advantages to this architecture
sorry yeah yeah no no no I was just um buttressing what you said i mean it seems like
broadly um um planned architecture and it seems like a whole lot of work has been put in to making
this possible because i mean having to transition from one blockchain to another automatically from
the user point of view that's um that's something that takes a lot of work.
So that's a lot.
Kudos for that.
So, well, I think we're going to dive into all of that more as we go on.
I'm just going to move on to a different question now
because we have quite a number of them before we move on to the community questions.
Are you ready for my next question, Dennis?
Absolutely.
All right, splendid. So could you tell me about Zeta Chain's proof of stake consensus
and how it relies on validators, observers, and signers? So how do these roles ensure security
and scalability, and what opportunities exist for community members to participate in securing the network.
So ZetaChain is a, as you said, is a delegated proof of stake
BFT consensus under the hood. So it uses Comet BFT,
which at the end of the day means that you have a network of validators run by people, by different entities,
and users stake zeta to these validators or delegate zeta to these validators and validators. Propose blocks. At random or not at random,
but it's deterministic,
but based on voting power,
a validator.
Is is chosen to propose a block
and they get rewards for producing blocks.
So Zeta chain has two types of validators.
One is core validator,
which is purely commit BFT proof of stake.
Validator, they process all the transactions
and they get rewards.
And Zeta Chain also has observer signer validators where they, instead of only participating in the consensus, they do more things.
Basically, they observe connected chains and they also sign transactions on behalf of the network.
So these two types of validators are both required for the data chain to work.
And observer signers deal with interoperability and core validators deal with consensus like they do on most other proof of state blockchains.
So observer signers are incredibly important
because they keep their fragments of the private key.
So whenever a transaction comes in from a connected chain, what they do, they, well, they, first of all, they run nodes of all the connected chains so that they can observe events on these chains, incoming transactions, incoming token transfers, let's say from Bitcoin to Zeta chain, from Ethereum to Zeta chain and so on. So they observe these events and they vote on them
on Zeta chain if majority of validators agree
that this event actually happened,
then it gets processed.
And for outgoing transactions, for example,
in the scenario that I described earlier
with Bitcoin and USDC, validators would first observe Bitcoin and see that the BTC is coming in.
They would vote on this transaction and a universal app is executed.
And at the end, USDC, they observe an outgoing transaction from Zeta Chain to Ethereum.
And they go through this process of signing an outgoing transaction on Ethereum on behalf of the protocol to actually transfer USDC from the custody of validators to the receiver.
from the custody of validators to the receiver.
So every transaction that is going from Zeta Chain
goes to this decentralized signing process.
All right, all right.
That sounds awesome.
That sounds very awesome.
So quick one.
Could you tell us how the Zeta Hub works?
How does it serve as the entry point for users interested in leveraging the inter-chain operability feature?
And what steps is Zeta Chain taking to make it accessible to both crypto newcomers and seasoned users?
So I think the main kind of way that ZA chain makes crypto accessible is by adapting to the way users are already engaging with crypto.
What I mean is instead of us telling users we built a whole new system and the only thing you need to do is install this wallet
and import your private key.
Like that's just too much of a barrier to entry.
You don't wanna tell users to install yet another application
or trust yet another system.
What you wanna do instead is adapt to the apps
that users are already
using on a daily basis and the wallets especially the wallets that users are are using because a
wallet is an important part of the of the journey right it's the it's the app that you interact with
that you interact with blockchains
and you have some trust in this wallet.
And what data chain offers is this ability to interact
with any application on any chain using the wallet
that you're already using.
So it might be a Bitcoin wallet,
it might be if you're a Sui user,
you have your Sui wallet of choice.
And we just adapt and allow developers
to build these universal apps
that can be triggered essentially from any wallet.
And I think that's the main user experience uh advantage is that
most users will not even know necessarily that they're uh they're using zeta chain under the hood
and and that's great because that means that we've successfully abstracted away the complexity
That's great because that means that we've successfully abstracted away the complexity without users even kind of being aware that what's going on under the hood.
Of course, it doesn't mean that users will not use Zeta Chain directly.
Of course, many applications will be used on Zeta Chain directly because it's an EDM chain.
directly because it's an EDM chain.
So you already have a wallet probably available
like MetaMask, Coinbase, Rabi, whatever, right?
It's just gonna work with the data chain.
So if you wanna do that, you can.
And there are many good reasons to do this
because if you make calls from Zeta chain
to a connected chain is just faster,
but many users are not gonna do that.
Just gonna use the chains that they're already on,
such as the Ethereum base, Bitcoin, whatever.
And they'll just move value and call applications remotely
from these wallets that they have.
So in addition to this, just one more thing is that
through this network of validators, ZetaShame provides custody for tokens.
So when you transfer assets, you actually get native assets in the end. and send USDC to someone on Ethereum. What I mean is this USDC is going to be like the native,
the real deal, right?
The native USDC, not some Zeta chain wrapped version of it.
And I think that's really powerful because that's what users want at the end of the day, right?
They don't want to get another wrapped asset.
They just want to interact with applications
and other users
in native tokens of the chains that they're on.
So, yeah, broadly speaking,
I think these are two main advantages in terms of UX,
both relevant to new users of crypto
as well as to those who've been around for a while.
All right.
That sounds very interesting.
So now we are actually going to move on to the questions from our community members.
We have an amazing community here on Satoshi Club.
And of course, we have tons of questions so if I were to keep asking
my questions we would have maybe a hundred because I'm quite curious about
Zeta Chain but let's move on to the first question from our community members
now this is from Chuck he's asking how does the Zeta Chain Universal app model
redefine the role of liquidity across chains can we eventually see a single
liquidity layer for the entire crypto ecosystem?
And is Zeta Chain building towards that?
That's a really good question,
because one of the things that Zeta Chain provides
is this mechanism of universal liquidity.
What this means is that instead of necessarily relying
on liquidity pools on connected chains,
universal applications can tap into the liquidity pools on the Zeta chain. So when you're swapping
tokens, you can kind of tap into these pools that have all representations of all the tokens of the connected, not all the tokens,
but of the supported tokens of the connected blockchains on Zeta chain. So this means that
instead of fragmenting liquidity and having a bunch of smaller pools, you can pool all the
liquidity on Zeta chain and all applications essentially reuse the same
pools. These pools are with representations of tokens from connected chains, but for the end
user, it doesn't matter because when they're withdrawing tokens, at the end of the day, they're getting native assets, right?
Transferred from custody to the user.
So this ability to essentially pool all the liquidity on Zeta chain
is what makes building universal apps much easier
because you can kind of reuse the same liquidity pools,
but not all tokens are going to be in this pools
right um of course some chains have like some meme coins that you probably not going to find
a pool for them on data chain but this still can be uh used from your universal apps where you can
make a call to that chain so let's say there's some meme coin on base and your universal apps where you can make a call to that chain. So let's say there's some meme coin on base
and your universal app needs to swap into that token.
You're making an outgoing call from your universal app to Zeta chain
with an instruction to swap an asset into this meme coin.
an asset into this meme coin.
So you can still do that.
So you can still do that.
And you can use the unified liquidity pools
on the data chain for supported assets
and you making outgoing calls
and tapping into liquidity on connected chains
for tokens that are probably like smaller,
lesser known or just new.
So both approaches work fine.
All right. All right. All right. Thank you for that answer. I hope that answers your question,
Chuck. So the next question is from Cleverland. The Universal EVM aims to provide a consistent
execution environment across different chains. How does it handle the differences in data structures, gas models,
and execution environments between various blockchains,
especially non-EVM chains like Bitcoin?
So Zeta chain is EVM, and the way we handle calls from different connect chains and outgoing calls is this way. So basically,
when a user is making a call from Bitcoin, what they do is they supply a message in the memo of
a transaction and relay this message to your universal contract. The same happens actually from any other connected chain.
When a user on Ethereum interacts with your app,
they're interacting with what we call a gateway on Ethereum,
which is a contract,
and you're passing a message to this gateway
and it gets propagated, relayed to your universal app.
So from universal apps point of view,
interactions from connected chains is exactly the same.
You're just getting a message.
You're getting some bytes from a connected chain,
and that's it, and you can do whatever you want
with these bytes.
When you're making an outgoing call,
it's a bit different because for every chain, like the interaction could
be different. But what we're doing is we're just using ABI encoding to kind of standardize
interactions and the translation layer happens on the Zeta chain side. So you don't need to
worry about that all that much.
So for Solana, for example,
when you're making a call to Solana,
you would be providing all the assets
that you're gonna be interacting with.
You're providing the program name
if you wanna call a program on Solana from Zeta chain.
Same with SUI.
So you would be passing all the objects
that you're going to be interacting with.
And on the SUI side, you will handle this call
and relay it to an appropriate contract.
With EVM chains, it's also very easy.
Arguably, it's a bit easier to understand
because Zeta Chain is EVM.
And if a connected chain is also EVM, you just pass a contract address
that you want to call and the message, and the gateway will call that contract
on your behalf with the tokens that you provided or without tokens.
the tokens that you provided or without tokens and in addition to this zh chain offers robust
reverting mechanisms which are often kind of um uh they're not talked about as much but they
should be because it's a very important part when you're building an application you just
you don't want to build just for the happy path,
right? You want to handle all the possible nuances and situations that might occur.
So with Zeta Chain, we're providing all the mechanisms for you to ensure that the assets
that you're transferring are never lost or locked, even if the call fails. Let's say you're transferring are never lost or locked,
even if the call fails.
Let's say you're making a call from Zeta Chain's universal app to contract on Ethereum to swap some tokens,
but there are no liquidity for that operation.
The transaction can revert back to Zeta Chain
so that you can handle these tokens
and send it to user or do anything you want with it,
making sure that no assets are kind of locked.
Yes, it's really important
that these mechanisms are in place.
But yeah, at the end of the day, Zeta chain kind of abstracts away
differences between blockchains by standardizing on kind of a single format
of a message, which is just bytes coming in.
And then you can make outgoing calls using abi encoding you can't make
outgoing calls to bitcoin because you can't really have proper smart contracts in bitcoin but you can
accept calls from bitcoin and you can withdraw btc to the bitcoin, which is already very powerful.
Wow, that's actually a very robust network you got there.
Well, thank you for that splendid explanation.
I must commend you, Dennis.
You're doing a wonderful job at breaking down all these complex concepts.
Thank you so much, Dennis.
So we'll be moving on to question three
from our community now, and this is from Carl. He's asking, there's always competition in
blockchain technology. How does Zeta Chain plan to be at the forefront of its innovative features?
And what if in the next few years, the entire market crashes? That's funny.
Due to little demand and strict regulations,
how will Zeta Chain ecosystem survive?
So the way we survive,
no, not survive,
but like the way we plan on kind of growing and expanding essentially
is by not competing with other blockchains really, right?
So our goal is to not build a blockchain
that everyone will migrate to,
but rather build a platform
that is a great place to build, of course,
but is also connecting other networks.
So it's a perfectly fine use of Zeta chain where you maybe you already have
an application on Avalanche, for example, and you want to keep using it, right? You built this
application, it's working great, but the only thing that's missing is connectivity to the Tom
network, right? So that's something you wanted to add to your application,
but there are no good bridges between these two networks.
So you can use ZetaChain as a mechanism to connect to networks
that you weren't able to be connected to.
And maybe you're not leveraging all the features that Zeta
Chain offers, but you can still use it in this way, right? Maybe you're
building an NFT collection and you don't want limit your users to just
like one blockchain, right? Like base is popular right now, but what if
there is like a more popular EVM chain?
You want to let your users move these NFTs to that chain. So you can build that very easily
on Zetaship. In fact, you can already use an existing solution for this called universal NFT.
You just mint it on any number of connected EVM chains and users are free to move these nfts or maybe you
just want connectivity to bitcoin right you want to build a new application with very good
interoperability with bitcoin to allow um btc holders to engage in in in and defy in a novel way, right? You can do that as well,
just build a universal app on Zeta Chain.
So I think the way Zeta Chain
is going to continue growing
is by being very flexible
in what we offer
and not forcing anyone to kind of,
yeah, you have to drop your project
and like build a new one on Zeta Chain.
That's not the approach.
We want to provide as many tools as possible
and connect as many ecosystems as possible
to essentially create this environment
where users don't have to think about moving assets
or differences between blockchains.
They're just using an app and kind of data and
value just freely flows between networks. And that's what we're building.
All right. All right. Splendid answer, Dennis. Thank you so much. So this question is from Yamiko.
What are the security considerations of Zeta chain
and potential vulnerabilities introduced by native cross-chain technology
and how are they mitigated?
So there are many answers to this question,
but from the source code point of view, of course, all the sources
is public. We are building everything in the open. We're hosting protocol development calls every
two weeks. So we really value transparency and we want everyone to be able to kind of
peek under the hood and see how it all works and suggest
improvements. And if there are even any kind of hints of a possible vulnerability, we want to
know about it as early as possible. That's why everything is out in the open. It's actually very
good. These protocol calls are a very good place to learn about all the new things that are coming because you can hear about new stuff long before we announce them.
So that's from the source code point of view.
And of course, every change that we're making, every release goes to an audit.
So code is fully audited by a bunch of different entities.
So code is fully audited by a bunch of different entities.
We have a list of audits that we've completed over the past year or so.
On the operations point of view, there's no single bottleneck.
There's no single place where many L2s have a
sequencer and it's just basically like one server that's
doing this work, right? So it's not very decentralized. With
Zeta Chain, it's always a network of entities validating,
be it's consensus of the protocol validating transactions
and producing blocks or observing cross-chain calls.
So it's always the vote mechanism,
which ensures that there's no single entity
making these calls.
And aside from this,
we are kind of growing responsibly or sustainably, I'd say, because
we want to make sure that the security of the network is proportional to the amount
of value that it holds, it secures, right?
So we don't want to be in a situation where the network is not capable of securing the assets.
So that's why we have things like liquidity caps
where there is a limit on how much liquidity
can be transferred to Zeta chain.
And this is not because we want to prevent people
from providing more liquidity,
but we want to make sure that the network is secure enough
to handle the incoming value.
And since we use these kind of unified liquidity pools,
that's actually more efficient
because we get the liquidity from different chains.
All apps use the same pools.
They don't have to rely on other chains' liquidity if they don't need to.
And so, yeah, I'm sure there are many other aspects of security,
but that's what comes to mind.
All right. All right. security but that's what comes to mind yeah all right all right um it's um commendable that um security is a top-notch um consideration and um that's an amazing question from your yamiko thank
you so much for that question it's i mean it's expected that community would be concerned about security
and they want to be sure that when they get in on zeta chain their assets are secure and i must
comment that thought from zeta chain as well from your team for considering um that you do not want
to overwhelm the system with so much liquidity that wouldn't be able to be secured so i think
that's actually very commendable yeah so um I'll be moving over to question number five
from our community now, and this is from Fefi.
Fefi is asking, how does Zeta blockchain
achieve consistent five-second finality
while maintaining cross-chain consensus,
particularly with chains like Ethereum or Bitcoin
that have longer finality times
and probabilistic finality models?
Yeah, I think that's a very good technical question.
So the way it works is these transactions between blockchains,
let's say it's from Bitcoin to Zeta Chain to Ethereum,
they're not atomic.
So they don't happen in a single block, right?
So we're not in the business of synchronizing block times
between blockchains.
That would be maybe possible to do with blockchains
that have similar consensus characteristics
where the finality is instant,
like with Cosmos chains, that would be much easier.
But many blockchains have probabilistic finality.
And the way we handle this is basically every transaction,
transaction, every incoming transaction from a connected chain, let's say Bitcoin, the
every incoming transaction from a connected chain, let's say Bitcoin,
observer signer validators network has a number of confirmations that they wait before considering
this transaction to be finalized.
And every chain has a different number of confirmations. So essentially observer signers wait
for a certain number of blocks
before considering this transaction to be finalized.
And the reason why we do this
is we wanna avoid reorganizations as much as possible.
So as long as we waited
for a certain amount of blocks,
the transaction goes through, then it's processed on zeta chain.
Right now we're actually in the process of reducing the block time on zeta chain
even lower than five seconds to make it faster and more efficient.
It's processed on Zeta chain,
and then we're making an outgoing call.
And observer signers also wait
for a certain number of confirmations on that chain.
And these numbers are going to change,
and we're going to iterate on the mechanism
of observation and signing to ensure
that there's a good balance between security where we
actually avoid reorgs and do everything very securely and reliably. But at the same time,
we don't wait for too long and we don't waste any user's time on this. So there has to be a good balance.
And we have systems being built right now where you can
actually reduce the waiting time for simple deposits.
So there's going to be more and more tools available for developers to
actually make their transactions much faster, more and more tools available for developers to actually
make their transactions much faster be processed much faster um so very excited to see where this is going but yeah right now or for for security reasons we're waiting for a certain number of
of confirmations on each chain.
confirmations on each chain and and that's how we do an operability
And that's how we do in our ability.
All right.
All right.
All right.
That's quite understandable.
Speaking of the future, I mean, you can give us some insight, at least some sneak peeks,
if I would call it that.
So I'm going to ask what you have installed.
With Mainnet launch behind us, that's happened.
What are the next major milestones for Zeta Chain in 2025?
And how do you plan to expand partnerships with other blockchains
and other Web3 projects looking forward?
Yeah, so we've added quite a few chains,
non-EDM chains recently, like Sui and Tom.
Not many interoperability solutions actually integrate with those chains, especially Tom.
So that's really cool.
And support for both of these chains is coming.
It's already on test sets.
Of course, you can already build on it as a developer,
and it's going to become available on mainnet very soon.
As I said, we have some interesting mechanisms coming soon,
which will allow transactions to be processed much faster.
We're also looking into other non-smart contract chains to be connected because Bitcoin has been one of the main chains at launch, one of the four chains that were connected at launch.
connected at launch and it's it was very important for us to connect connect bitcoin because we
wanted to provide this uh connectivity to bitcoin users so they wouldn't have to like rely on
bridges and all that right and but there's still other non-smart contract chains to be connected
so we're looking into that and And of course, looking into the mechanism
that actually allows validators
to sign transactions
on behalf of the protocol,
the more improvements
we can make on that front,
the easier it's going to be
for end users
to interact with apps
the less time
they're going to have to wait.
So, but yeah, I'm really excited about these new non-EVM chains connected to Zeta chain.
I think there's going to be a lot of interesting use cases where you would be able to, like from your Telegram app,
you would be able to interact with any application on any
any blockchain uh through tom so i'm very excited about that
all right sounds sounds good sounds good so speaking specifically about Bitcoin now, so for all Bitcoin transactions,
are there any restrictions on the particular wallets or it's a sort of universal thing,
like no restrictions, every single Bitcoin wallet, be it Xverse or whichever Bitcoin wallet,
it's going to work seamlessly with ZTE Chain. Yeah, every wallet should be compatible.
So we don't necessarily require anything from wallets aside from being able,
for your wallet to be compatible with Zeta Chain,
it has to be able to send transactions with a memo encoded as bytes in OP return,
which is standard for your encoding memos
in Bitcoin transactions.
And all major wallets support this functionality.
And Xverse, Unisats, OKX are just a few that come to mind.
They all work very well with zeta chain
but any wallet should be compatible we actually now support two mechanisms of interacting
with universal apps from bitcoin one is op return the traditional uh very kind of low maintenance
uh way of of of uh sending data on the Bitcoin network,
but it also supports inscriptions, which is a new, arguably more flexible,
well, objectively more flexible mechanism because it allows you to send much more data in a single transaction.
So we also support inscriptionscriptions and many wallets now support
inscriptions as well. So very easy to interact with with universal apps from Bitcoin. It
doesn't really matter how much data your application requires. If it's less than 80 bytes, actually
60, less than 60 bytes, you can use op return.
If you need more data, just use the inscription.
You broadcast the commit transaction,
reveal transaction and witness data contains
the message that will be passed to universal app.
And it also supports revert address so if your universal
app reverts for some reason maybe you didn't format the data correctly or something else happens
the bitcoin amount will be returned to the address that you specified which is very convenient
which is very convenient.
Well, that's actually an amazing feature.
So providing the avenue to have reverse transactions
in cases of errors, I mean, that's top notch.
Well, thank you so much, Dennis.
This has been an amazing eye-opening conversation
I've had with you today.
It's been fun talking to you
it's been educative and it's been um it's been most of all really really really really cool
talking to you dennis so thank you so much for your answers we sadly have to draw the
curtains at this point um there are so many other questions of course, we have all your socials. We have your Twitter. We have Telegram.
And I'm sure if anyone still has a couple of questions which were not answered,
it would be nice to hop in your TG, your Discord,
and pop them so your mods can do justice to them, right?
Thank you so much for having me.
It was a pleasure.
Yeah, thank you. So do you happen to have any added information that we possibly did not touch in the course of our conversation? Anything you want to
add? Anything we should look forward to that you could just quickly tell us about? I think we
covered quite a bit, but I just wanted to highlight that there's really no better place, better time to start building because we've connected so many blockchains already.
Like if you're looking, if you're a builder, if you want to create an app for Bitcoin users, especially Zeta Chain provides all the infrastructure, all the tools for you to build the next big app.
All right, splendid, splendid. Thank you.
Thank you so much for that, Dennis.
So you guys follow up on their socials,
hop in their Discord or your Telegram if you have
any further questions for Zeta Chain. It's been an amazing conversation. I'm glad I was able to be your host today.
I'm glad I was able to talk to Dennis. It will be wonderful to have you again sometime
soon. We look forward to having you here on Satoshi Club, Dennis.
Awesome. Thank you so much and have a great day.
All right. Have a good one, Dennis.
Have a good one, guys.
