VIA Labs Interview
In this interview, Cletus, CEO of VIA Labs, shares how his background in electrical engineering led him into blockchain interoperability and the challenges of connecting different networks. He explains how VIA Labs connects Cardano with more than 150 blockchain networks through a cross-chain messaging protocol designed with security and developer flexibility in mind.
The conversation covers several fundamental concepts in Web3, explained in accessible language without getting lost in technical detail. Cletus walks us through how cross-chain messaging works, why traditional bridges have faced security challenges, and how VIA approaches interoperability differently by giving projects greater control over their assets and transactions. We also look at the technical side of bringing VIA to Cardano, the role of private oracles, and potential applications in stablecoins, tokenized assets, institutional finance, and multi-chain governance.
For some additional context, you can also watch the previous Cardano Seminar session, where the VIA Labs team walked through the technology behind cross-chain interoperability.
To kick things off, could you please introduce yourself, share a bit about your background, and tell us how you came to found VIA Labs?
Hello everyone! I’m Cletus, CEO of VIA Labs. My background is in electrical engineering. Previously, I took part in building electrical infrastructure for utility-scale solar plants throughout the United States, specializing in selecting the electrical components to ensure that these facilities were up to par with existing regulations and electrical code. It was my responsibility to ensure that the design was sufficient where the cables that carried electricity from the plant to the substation didn’t overheat or cause problems for each of our clients.
I’d say there are many parallels between utility infrastructure and blockchain infrastructure. Primarily, a power plant can connect to the grid only if it meets a common standard, and the right protection systems are in place to limit electrical faults from cascading. Cross-chain messaging, which is what we do at VIA Labs, takes this same idea into the digital realm. Messaging needs the same two things – it requires one standard that every chain can connect to, and controls that stop one bad message from spreading.
I started building cross-chain infrastructure in 2021. As some of us in the space may remember, this was the year of “DeFi summer.” I joined the space because I saw opportunity in blockchain technology and, frankly, didn’t know what I was getting myself into at the time. I was what they called a “retail investor.”
Everyone remembers their first bridging experience. It’s terrible. I was attempting to bridge funds between Ethereum and Polygon. The process took several hours, my funds got lost, and I had to beg in a Discord for someone to “kick my transaction” to process. This is where I saw the problem. This wasn’t the future of finance that we were all promised. And I made it a mission of mine to improve the space.
Through much trial and error, I learned how the blockchain space operates. I learned at the time, that about $2 billion was stolen from bridges in 2022 (roughly half of all crypto stolen that year). And I learned that given my background, I could make a positive change by introducing a means by which people could send data and value securely between networks.
By happenstance, I found a team that aligned with these values and spent the next couple of years building generic cross-chain products. And in 2024, VIA Labs was born.
From then onwards, our team has honed its skills in developing a cross-chain standard that puts both security and the developer experience first. And ironically, while the space has evolved in those few years, we face many of the same problems that were here in 2021. While there have been significant improvements in generic infrastructure (Circle’s CCTP to name one), much of the space, particularly non-EVMs, is still made up of isolated islands without connection to the outside world. At VIA Labs, we aim to bring everything under one roof, where builders can connect to one omnichain network and not have to worry about what blockchain their funds are operating under.
For community members who are new to the concept of blockchain interoperability, could you explain in plain terms what it actually means for two blockchains to "talk to each other," and why that has historically been so difficult to achieve?
Each blockchain keeps its own ledger and follows its own rules. It can read only its own ledger. For example, Ethereum can’t see what happens on Cardano.
When two chains “talk to each other” an event on one chain causes an action on another. In practice, what this means is that a user locks a token on Cardano, and a contract on Ethereum releases the same value. For that to work, a system must carry the message between the chains, and the destination must be able to verify that the message is real.
Verification is the hard part. A chain can’t check another chain’s ledger by itself, so it depends on an outside party to confirm (validate) that message.
This is one of the primary attack vectors we see today. Most large bridge hacks came from stolen keys or broken verification. Chains also differ in block times, programming languages, address formats, and fee tokens, and an interoperability protocol must handle each difference for every chain it adds.
Most people in the crypto space have heard the word "bridge" and many have also heard horror stories about bridges being hacked. How is what VIA Labs does different from a traditional bridge, and why does that distinction matter?
VIA is a cross-chain messaging network. A bridge is one type of application that developers can build on it.
A traditional bridge is a product. It usually locks tokens in its own vault on one chain and mints its own copy on another. The bridge owns the copy, sets the security model, and controls the vault, so the token issuer has little control. If the bridge is hacked, holders are left with copies backed by nothing.
VIA is not a bridge. Instead, our protocol works on a lower level. It carries messages between smart contracts, and a message can contain many things – a token transfer, a price, a vote, or a function call. Each project deploys and owns its contracts on every chain it uses.
Projects can also choose who signs their messages. Signers run by VIA Labs sign every message, and a project can also require signatures from its own team, or any desired outside party. If a project requires its own signers, no message reaches the project’s contract without the project’s signature. Many interoperability setups offer one fixed security model. With VIA, a small project can dictate its own security model. They can choose to start with VIA’s own signers, or, they can choose to set their own security standards and set up a custom signer and relayer network, all of which is able to natively communicate with other blockchains using the VIA Network.
When a token moves across chains today using a traditional bridge, something called "wrapped" tokens are often created, copies of the original that live on the destination chain. Could you explain what wrapping is, why it causes liquidity fragmentation, and how VIA Labs approaches the problem differently?
Wrapping means locking a token on its home chain and minting a copy on another chain. The copy has value only while the original stays locked.
Fragmentation happens when several bridges wrap the same token. Each bridge mints its own version on the same destination chain. The versions aren’t interchangeable, so liquidity (which lives on DEXs) isn’t interchangeable. Instead, it must live in its own smaller pool, and each version carries the risk of the specific bridge that brought the token to the chain in question.
There are three common ways to move a token between chains:
- Burn and mint: burn the token on the source chain and mint the same amount on the destination.
- Lock and mint: lock the original on its home chain and mint a one-to-one version on the destination.
- Lock and release: lock the token on one chain and release existing tokens from a pool on the other.
Most bridges use lock and mint and own the copies they mint. For a token to be canonical, meaning the official version, the issuer must own the contract on every chain. With VIA, the issuer owns its contracts and chooses its desired bridging pattern. For example, Moneta, the stablecoin issuer behind Cardano’s USDM, uses VIA as USDM’s canonical cross-chain provider.
VIA uses a three-layer security model to validate cross-chain messages. Could you walk us through what those three layers are, why each one exists, and how the system ensures that a message arriving on the destination chain is genuinely the one that was sent, and not something tampered with along the way?
The VIA Network operates using three layers of signers to decentralize security. The only difference between each layer is who runs them:
- The “VIA Layer” is run by VIA Labs. It's on by default, so every message gets a baseline minimum security floor.
- The “Chain Layer” is run by the chain's own operators. It gives a chain a direct say in the messages its network accepts.
- The “Project Layer” is run by the integrating team. It gives the project its own approval on messages to its contracts.
On EVM chains and on Cardano, the destination gateway verifies the signatures on-chain. Each layer has a configurable minimum number of signatures, and if any active layer disagrees with the others (spots a fraudulent message), the gateway will reject the message – ensuring all funds are safe.
Security increases as more layers are added. For example, with the Project Layer turned on, VIA's signers alone can't individually send a message into the project's contract.
Additional security protections can also be added by the implementing parties. For routes that need extra protection (stablecoins / large liquidity transfers), our signers also enforce limits, such as a maximum amount per message and a minimum number of confirmations.
In the VIA Labs architecture there is an important distinction between signers and relayers, two roles that are easy to confuse. Could you walk us through what each one does, why they are kept separate, and what that separation means for keeping a cross-chain transaction safe from the moment it is sent to the moment it arrives?
VIA's node software watches every chain, including the destination. It waits for the required confirmations and checks the transaction again. The nodes also share each message with each other over a peer-to-peer network. If the message on-chain exactly matches what was shared, a signer hashes the message data and signs the hash. Signing and delivering are separate jobs. A relayer takes the signed message to the destination chain and pays the gas to submit it to a message receiver contract called a “gateway.” The gateway checks the message and then delivers it to its intended destination contract.
We keep the roles separate to give the implementing builder customization to their own security. A relayer can't change a message, because any change invalidates the signatures. And as long as the signer and relayer addresses are different, a signer cannot relay / forward a message on-chain. Both must work in tandem.
By default, for projects that prefer a simple onboarding experience, VIA Labs can operate both the signers and relayers. However, it is fully customizable (and can change later depending on the project’s preferences).
Every cross-chain message has to wait for something called "block finality" on the source chain before it can be safely delivered. Could you explain what finality means, why it matters, and how VIA Labs gives developers control over how much confirmation they want before a message is considered safe to act on?
Blockchain finality is the point at which a blockchain’s transaction can't be rolled back. For a short time after a block is added, the network can still replace it. Each new block on top makes a rollback less likely, until the block is final. VIA lets the developer choose how long to wait. Each message sets the number of confirmations on the source chain, and every signer waits for that number before it signs.
Not all messages are equal. Some may not need to wait. For example, for use cases involving sensor data, a blockchain rollback doesn’t matter much. On the other hand, liquidity transfers may want to wait longer. If a stablecoin issuer mints on the destination before the burn on the source is final, a rollback can leave unbacked tokens.
Chains reach finality at different speeds. Avalanche finalizes a block in about one second. Cardano produces a block about every 20 seconds, and doesn’t officially finalize for 2,160 blocks (or about 12 hours). With VIA’s infrastructure, teams can select a confirmation time that matches their risk tolerance depending on their use case and chain.
Cardano’s Peras upgrade will reduce this wait time from ~12 hours down to ~2 minutes. Something we’re very excited about (and you should be too).
The protocol supports over 150 networks, covering both EVM and non-EVM chains. For those unfamiliar with that terminology, could you explain what EVM means, what makes non-EVM chains fundamentally different to integrate, and why supporting both is technically significant?
EVM stands for Ethereum Virtual Machine, the execution environment for smart contracts on Ethereum. Many chains use it, including Base, Arbitrum, Avalanche, BNB Chain, and Polygon. EVM chains share the same contract language, wallets, and tools. Essentially, most EVM chains are the same when it comes to deploying smart contracts because it’s the same coding language.
Non-EVM chains use their own execution environments. Cardano uses the eUTxO model, with contracts written in Aiken or Haskell, compiled down to run on Plutus, Cardano's smart contract platform. Midnight uses Compact and zero-knowledge proofs. Stellar uses Soroban contracts written in Rust. These chains differ in language, state model, signature schemes, address formats, and fees. A good analogy is spoken language. Someone who only knows English can’t understand someone who only speaks Spanish. Besides the words themselves being different, the sentence structure isn’t the same, there are different conjugations, tone differences, body language, etc. The VIA Network strives to support all chains, EVM and non-EVM.
VIA Labs supports what you call "private oracles", the ability to connect proprietary or encrypted off-chain data feeds directly to smart contracts. Most people in the Cardano space are familiar with public oracles like Charli3, but the concept of a private oracle is less discussed. Could you explain what it is, who needs one, and why controlling your own data pipeline changes what you can build?
A public oracle is a shared data feed. A provider such as Charli3 or Pyth publishes data, such as the ADA price, and any contract can read it.
A private oracle is a feed that you own. The data comes from a source you control, such as your API, database, sensors, or internal systems. You decide what to send and when, and VIA delivers it to your contract on any connected chain. The data is recorded on a public chain, so sensitive data must be encrypted before it's sent.
Private oracles suit organizations whose data is proprietary or regulated. Examples include a fund that publishes the value of its tokenized shares, an insurer that pays claims when a flight is delayed, and a company that reports shipment and payment events from its existing systems. You don't have to wait for a public oracle to carry your data. Once delivered, your data lives on the blockchain more or less permanently, and you can query it and decode it locally whenever you need to.
For more privacy, zero-knowledge (ZK) proofs let a contract prove a fact about data without revealing the data itself. Any chain that supports ZK proofs can do this, and some, like Midnight, are built around them. VIA can then carry the result to other chains.
So with all of that context in place, what exactly is VIA Labs at its core, and how would you describe it to a developer who has never encountered a cross-chain messaging protocol before?
VIA is a cross-chain messaging protocol. It connects EVM and non-EVM blockchains natively and carries data between smart contracts on different chains. Developers decide what to build on top, such as bridges, DEXs, marketplaces, or oracle feeds.
You deploy a contract on each chain. One contract sends a message, such as "mint 100 tokens to this address" or "record this price." VIA verifies the message and delivers it to your contract on the other chain, which acts on it. You can move tokens, NFTs, data, and contract calls between chains, or broadcast one call to many chains at once.
When a developer integrates VIA Labs, the actual flow involves calling a send function on the source chain and implementing a process function on the destination. How much of the complexity is genuinely hidden, and what does a developer still need to understand about cross-chain behaviour to build something production-ready?
Most of the complexity is abstracted. On EVM, the developer's contract inherits from one base contract, ViaIntegrationV1. To send a message, the contract calls messageSend and specifies the destination chain, the payload, and the number of confirmations.
To receive a message, the developer overrides a function called messageProcess. Our Hello World guide does this in under 30 lines of Solidity. VIA inherently handles much of the complexity: message numbering, fees, signers, relayers, signature checks, and replay protection.
Cardano is a different environment, mainly because of the eUTxO model, so different requirements apply, including a standardized / approved message format. For all chains, we recommend testing on testnets, tracing each message on our cross-chain scan site, and working with our team before mainnet.
Your use case documentation covers some quite specific regulated verticals, tokenized equities, cross-border payment settlement, and KYC attestations propagated across chains. These are not typical DeFi use cases. Who is the audience you are really building for, and how does cross-chain messaging make these use cases viable in a way that was not possible before?
Our audience is institutions and the teams that build for them: stablecoin issuers, RWA issuers, payment companies, the chains they launch on, and the developers who serve them.
These use cases need three things:
- Control: a regulated issuer can't hand its token to a bridge operator. With VIA, the issuer owns its contract on every chain, keeps its compliance controls, and can require its own signers on every message.
- Data: a payment needs its invoice reference, and a tokenized stock needs its corporate actions, such as dividends. VIA carries value and data in the same message.
- Reach: institutions use many chains. For example, a company could issue tokenized shares on one chain and offer them to investors on other chains, while keeping control of the token and its compliance rules everywhere it trades.
Stablecoin issuers freeze addresses one chain at a time. With VIA, an issuer could send one compliance update to every chain it uses in a single action.
Cross-chain identity is one of the use cases you highlight, specifically propagating KYC and AML attestations across chains without requiring a user to re-verify on each network. Could you explain why that matters and what it would take to make that a real production flow?
Repeating KYC on every chain costs users time and creates risk. Each check leaves another copy of a user's documents with another company.
The better model is to verify once and reuse the result. A trusted provider checks a person one time and issues a digital credential. After that, an app on any chain can ask a simple question, such as "has this person passed KYC?", and get a yes or no without seeing the person's documents. Zero-knowledge proofs make this possible, and privacy-focused chains like Midnight are built around them.
VIA's role is to carry that answer to whichever chain needs it, so users verify once instead of on every network. To make it work in production, regulators need to trust the credential issuers, and credentials need to be revocable. The Cardano Foundation's work on Veridian is a good example of that credential layer taking shape.
You list multi-chain governance as a use case, the ability to execute DAO proposals and votes across all chains where token holders reside in a single action. For Cardano community members who are deeply engaged in on-chain governance, could you explain what that would look like in practice and why it is technically non-trivial to achieve?
Consider a project whose token exists on Cardano, Ethereum, Base, and Midnight. Today, holders usually move their tokens to one chain to vote. That costs fees and reduces participation.
With VIA, the project runs a ballot on each chain, and holders vote on the chain where they hold their tokens. When voting closes, each ballot sends its tally to a home chain. The home chain adds the tallies and broadcasts the result, so the decision executes on every chain in one action. Several problems make this difficult:
- Tokens can move between chains during a vote, so each chain needs a snapshot or a lock to prevent double voting.
- Chains finalize at different speeds, so each tally must wait for enough confirmations.
- The same holder may have a different address on each chain.
Voting power can come from assets staked on other chains, such as ETH on Ethereum or NIGHT on Midnight. Midnight can run private ballots that publish only the tally. The broadcast that executes a proposal can also pause every deployment in an emergency.
VIA Labs went live on Cardano mainnet on August 13, 2026, connecting it to 150+ other networks. What drew you specifically to Cardano, and what has the technical journey of integrating a non-EVM chain looked like?
We were drawn to Cardano because it’s an active chain without any way to broadly communicate with the outside world. It’s like a paradise island without an airport.
In cross-chain terms, the airport is the gateway contract. A gateway serves as one entry and exit point where generic cross-chain messages can be routed. Cardano had bridges, but each was a separate product run by a third party. VIA's cross-chain messaging gateway gives Cardano projects one entry point to 150+ chains, and each project keeps ownership of its contracts.
Frankly, the integration was difficult. Cardano works very differently from EVM, and we had to redesign our architecture for it. Anastasia Labs was a major part of this work. Phil DiSarro and the Anastasia team audited our Cardano contracts and worked closely with our CTO, Druuu, on the design. Phil's expertise made this possible.
Cardano's eUTxO model is quite distinct from the EVM environment where most cross-chain tooling was originally built. What were the most unexpected technical challenges you ran into during the Cardano integration, and how did you solve them?
The biggest difference is how state works. On EVM, our gateway is one contract. It stores its own data and handles sending, delivery, signature checks, and replay protection. Cardano has no contract storage. State lives in UTxOs, and a validator is a script that approves or rejects any transaction that spends a UTxO.
Our core Cardano system has eight validators: the gateway settings, a one-time token that identifies the gateway, a counter that assigns message IDs, a pair for outgoing messages, a registry of integrations, and a pair for incoming deliveries that includes the replay-protection list. Client templates sit on top. In total, 15 scripts went through audit.
Only one transaction can spend a UTxO, so a single shared state would force every user to wait in line. Instead, each message gets its own UTxO, and we process them in batches. Replay protection, which is one mapping on EVM, is a sorted linked list of UTxOs on Cardano.
The message format was the other main challenge. We use a fixed byte layout called VILR. The client rebuilds each message byte for byte and checks it before it mints, burns, locks, or releases tokens.
Integrations on Cardano are permissioned today. Once a token is set up, anyone can transfer it, but a new integration needs our team, because our nodes must know how to deliver to the new contract. We have templates for common patterns (token bridging), and we build custom integrations with partners.
Cardano is deeply focused on real-world utility, and cross-chain interoperability is often cited as one of the missing pieces for broader DeFi and institutional adoption. In your view, what does Cardano's integration with VIA Labs unlock that was not possible before?
The main change is reach. Before, a Cardano project that wanted to reach another chain needed a bridge run by a third party, usually with a wrapped copy of its token. Now VIA connects Cardano to 150+ chains, and the integrating project owns the contracts on both sides. This lets Cardano teams issue their tokens on EVM chains and keep control of them while also letting EVM projects expand to Cardano. Additionally, off-chain data can be brought from an API into Cardano contracts. In other words, oracles (another highly desired use case on Cardano) can be built with VIA infrastructure.
VIA Labs is also building AnyToAny. AnyToAny is an all-in-one bridge, swap, and aggregator that connects EVM chains and centralized exchanges directly to Cardano. A user can start with a token on an EVM chain, or USDC on an exchange, and receive the Cardano token they want, then move back the same way. It's one of 12 projects, from 117 applications, selected for the Catalyst Pilot 2026.
The multi-chain landscape is only going to grow more complex over time. How do you think about the long-term vision for VIA Labs, are you building infrastructure for the next few years, or is this something you see as foundational for the next decade of Web3?
We're building for the next decade. The final frontier of web3 is web2. I expect Treasuries, funds, stocks, and payments to move on-chain next. Forecasts for tokenized assets in 2030 range from about $2 to $5 trillion.
Financial companies are also launching their own chains, alongside new chains built for stablecoins. VIA is live on several of them, including Circle's Arc, Robinhood Chain, Stripe's Tempo, Plasma, and Stable.
These institutions won't all use the same chain. A tokenized stock needs to reach traders, lenders, and payment apps on other chains. That's the work for the next ten years: connecting chains to each other and to real-world systems. VIA is built for this. It carries data as well as tokens, and institutions can run their own signers.
Beyond the tech, what do you enjoy outside of the world of blockchain and infrastructure building? What keeps you grounded?
Golf and my two black Labs, Jaeger and Goose. They're my boys. I got them during COVID and trained them close to hunting-dog level: they know many tricks, such as sit, stay, place, fetch, and bite!
For golf, I play my home course and local courses in Michigan. I try to keep a list of every course I've played. My goals are to play St. Andrews and to evolve into a scratch golfer. I still have a long way to go. If anyone wants to play golf at one of these blockchain events, hit me up! 😉
If you could go back to the very beginning of the VIA Labs journey, knowing what you know now, what is the one piece of advice you would give yourself?
Stick with what you're good at, and focus on where people are having trouble. In this industry, it's easy to chase whatever is popular. The work that paid off for us came from finding where teams were stuck and fixing it. That meant new chains that couldn't get connected, non-EVM chains that others skipped, and issuers who needed their tokens on more chains without giving up control. I would have done more of that, sooner.
Thank you so much for sharing your story with the Cardano community. To wrap up, where can people follow VIA Labs, explore the documentation, or get in touch if they want to build with you?
Thanks for having us! For starters, head to our website at https://vialabs.tech/ to learn more. Developers can go straight to https://developer.vialabs.tech/ for our integration docs, the Cardano guides, and the audit reports.
All cross-chain messages sent through the VIA Network are displayed on our scan site at https://scan.vialabs.tech/. For the latest news, check us out on X @VIA_Labs!
To build with us, email hello@vialabs.tech or fill out the onboarding form on our website. We reply within one business day. Most blockchains on the VIA Network are permissionless, so you can start building without even speaking to us. It’s all up to personal preference!
Thank you for sharing your story. To wrap up, can you tell us a bit about your team? Who’s behind VIA Labs, and where can readers follow your progress or get involved?
We're a nimble team and easy to reach:
- Cletus Pilat (CEO - @Cletus_VIA - GitHub: cletus-VIA - in charge of strategy, partnerships, and the builder experience)
- Druuu (CTO - GitHub: DruuuCLT - in charge of protocol architecture, integrations, and the live build)
- Jake Salthouse (Chief Business Officer - @JakeSalthouse97 - in charge of business development and strategic partnerships)
- Brad Simon (Full-stack engineer - GitHub: brad-za - in charge of our apps, wallet integrations, and developer experience)
Follow @VIA_Labs on X and developer.vialabs.tech for updates, or email hello@vialabs.tech to get involved.
Cardano Seminar
To explore VIA Labs' solution further, watch their presentation at the Cardano Seminar, where key leaders dive deep into cross-chain architecture, security models, and live technical demos. Hear directly from the VIA Labs team, including Robert Pilot (Cletus), Founder and COO, and Andre Vanyi (Drew), CTO and Chief System Architect, as they discuss building secure, scalable interoperability for Cardano.
Watch now
