Alice isn’t thinking about chains. She’s got ETH sitting on Appchain 1, and she wants USDC on Appchain 2. Maybe she thinks of providing liquidity, maybe just to park it. Normally, that’s where her pain points start: bridges, wrappers, delays, and hoping nothing gets stuck halfway.
But on Pelagos, it doesn’t work like that.
She opens her wallet, selects “Swap ETH to USDC,” hits “confirm”, and in less than a second, her ETH on Appchain 1 is gone, and her USDC appears on Appchain 2. No bridges. No solver. No waiting for a confirmation. Just done.
The moment Alice hit “confirm”, her ETH was locked inside the Appchain 1 Treasury, a contract backed by real ETH on Ethereum. At that same instant, every Pelagos validator saw that lock event. There’s no leader collecting blocks as all of them move in sync, inside a universal DAG sequencer.
Within a single round, about 400 milliseconds, the event is finalized, and ETH appears in Alice’s account on Appchain 1. She’s still in the same wallet, but she’s already in a different universe.
Now the DAG picks up her swap order. An Uniswap-style pool (running on another Pelagos appchain, let’s call it App-Uniswap) sees the incoming trade. The system simulates it across chains, checks if there’s enough liquidity, and only then commits. If it clears, USDC lands in her account on Appchain 2. If something fails, a slippage check, a pool limit, whatever, the entire thing rolls back, and her xETH unlocks instantly. That’s the atomicity promise: either everything happens, or nothing does.
To Alice, it felt like one click. To the network, it was a dozen coordinated acts, which were observed, agreed, and executed everywhere at once.
Suppose Alice wanted to go back to Ethereum instead. It still feels the same. She locks her ETH on Appchain 1, and Pelagos orchestrates the rest: validators finalize the event, trigger a TSS signature on Ethereum, unlock her ETH, and even handle gas through account abstraction. The ETH moves. The Uniswap swap happens on Ethereum. The result leads to USDC in her address.
Because Pelagos doesn’t treat chains as different worlds. Every validator runs the same leaderless DAG, watching all appchains at once. A lock on Appchain 1 and a swap on Appchain 2 don’t live on different timelines, as they’re part of the same block-free event flow.
This DAG layer gives Pelagos what bridges never could:
Instant finality (no waiting, no reorg risk)
Native composition (cross-chain actions in one round)
Scalability through sharding (each appchain can run as a microservice)
And under that DAG sits the Multichain Layer, a live feed of finalized blocks from Ethereum, Solana, and others. It reads events directly from those networks, validates receipts, and ensures external actions happen exactly once.
Reactive contracts listen to those receipts. As soon as one lands, they wake up automatically — no extra transactions, no manual claiming.
Tokens like ETH and USDC stay 1-for-1 backed on their source chains. Unlocking them takes one threshold-signature transaction. No bridges. No custodians. Just liquidity that can move anywhere.
The swap can match against an intent on Solana, or use an Appchain treasury that spans both ecosystems. Pelagos simply runs the external leg. From Alice’s view, nothing changes. From the system’s view, it’s just another plan, one that spans Ethereum and Solana and still settles atomically.
Pelagos makes the multichain world feel like one chain. There’s no “wait for bridge confirmation.” No wrapped assets. No retry buttons. It’s one DAG, one set of validators, one atomic commit across everything, Ethereum, Solana, L2s, and Pelagos appchains.
For Alice, it’s a button that just works. For everyone else, it’s the end of fragmented liquidity.
One signature. One plan. Native everywhere, or nothing moves.
If you're a developer interested in building on Pelagos or a potential validator, we'd love to hear from you.
Visit our Website
Join our Discord
Follow us on X
Email: contact@pelagos.network
Subscribe to Pelagos
Alice isn’t thinking about chains. She’s got ETH sitting on Appchain 1, and she wants USDC on Appchain 2. Maybe she thinks of providing liquidity, maybe just to park it. Normally, that’s where her pain points start: bridges, wrappers, delays, and hoping nothing gets stuck halfway.
But on Pelagos, it doesn’t work like that.
She opens her wallet, selects “Swap ETH to USDC,” hits “confirm”, and in less than a second, her ETH on Appchain 1 is gone, and her USDC appears on Appchain 2. No bridges. No solver. No waiting for a confirmation. Just done.
The moment Alice hit “confirm”, her ETH was locked inside the Appchain 1 Treasury, a contract backed by real ETH on Ethereum. At that same instant, every Pelagos validator saw that lock event. There’s no leader collecting blocks as all of them move in sync, inside a universal DAG sequencer.
Within a single round, about 400 milliseconds, the event is finalized, and ETH appears in Alice’s account on Appchain 1. She’s still in the same wallet, but she’s already in a different universe.
Now the DAG picks up her swap order. An Uniswap-style pool (running on another Pelagos appchain, let’s call it App-Uniswap) sees the incoming trade. The system simulates it across chains, checks if there’s enough liquidity, and only then commits. If it clears, USDC lands in her account on Appchain 2. If something fails, a slippage check, a pool limit, whatever, the entire thing rolls back, and her xETH unlocks instantly. That’s the atomicity promise: either everything happens, or nothing does.
To Alice, it felt like one click. To the network, it was a dozen coordinated acts, which were observed, agreed, and executed everywhere at once.
Suppose Alice wanted to go back to Ethereum instead. It still feels the same. She locks her ETH on Appchain 1, and Pelagos orchestrates the rest: validators finalize the event, trigger a TSS signature on Ethereum, unlock her ETH, and even handle gas through account abstraction. The ETH moves. The Uniswap swap happens on Ethereum. The result leads to USDC in her address.
Because Pelagos doesn’t treat chains as different worlds. Every validator runs the same leaderless DAG, watching all appchains at once. A lock on Appchain 1 and a swap on Appchain 2 don’t live on different timelines, as they’re part of the same block-free event flow.
This DAG layer gives Pelagos what bridges never could:
Instant finality (no waiting, no reorg risk)
Native composition (cross-chain actions in one round)
Scalability through sharding (each appchain can run as a microservice)
And under that DAG sits the Multichain Layer, a live feed of finalized blocks from Ethereum, Solana, and others. It reads events directly from those networks, validates receipts, and ensures external actions happen exactly once.
Reactive contracts listen to those receipts. As soon as one lands, they wake up automatically — no extra transactions, no manual claiming.
Tokens like ETH and USDC stay 1-for-1 backed on their source chains. Unlocking them takes one threshold-signature transaction. No bridges. No custodians. Just liquidity that can move anywhere.
The swap can match against an intent on Solana, or use an Appchain treasury that spans both ecosystems. Pelagos simply runs the external leg. From Alice’s view, nothing changes. From the system’s view, it’s just another plan, one that spans Ethereum and Solana and still settles atomically.
Pelagos makes the multichain world feel like one chain. There’s no “wait for bridge confirmation.” No wrapped assets. No retry buttons. It’s one DAG, one set of validators, one atomic commit across everything, Ethereum, Solana, L2s, and Pelagos appchains.
For Alice, it’s a button that just works. For everyone else, it’s the end of fragmented liquidity.
One signature. One plan. Native everywhere, or nothing moves.
If you're a developer interested in building on Pelagos or a potential validator, we'd love to hear from you.
Visit our Website
Join our Discord
Follow us on X
Email: contact@pelagos.network
Subscribe to Pelagos
<100 subscribers
<100 subscribers
Share Dialog
Share Dialog
No comments yet