# What if Web3 was as fast and simple as Google Search?

Source: https://pod.network

## Summary

Pod Network is a Layer-1 blockchain built for open, fair, high-performance markets, and its team says current markets are neither open nor fair. The team describes a system where a few institutions control who can trade and what can be listed, and where proximity to exchange servers determines who profits. Pod Network is designed with an EVM-compatible interface, a streaming architecture with no blocks that peaks at 300k TPS, batch-auction order clearing that is described as MEV-free, and transaction confirmation under 150 ms.

## Article

Pod Network is a purpose-built Layer-1 for fair, high-performance global markets.

compatibility

EVM

An Ethereum-compatible interface, so familiar tooling just works.

primitives

Markets

Order book, matching engine, liquidation, and oracles, fully on-chain.

throughput

300k TPS

A streaming architecture with no blocks, peaking at 300k TPS.

fairness

MEV-free

Orders clear in batches, so the best price wins, not the fastest.

finality

<150 ms

Transaction confirmation in one network round trip, under 150 ms.

A letter from the team

Markets are neither open nor fair.

A handful of exchanges owned by a few institutions decide who can trade, what can be listed, and how fast information travels. Proximity determines who wins. The closer your servers are to the exchange, the more money you make. Everyone else pays a hidden tax in the form of worse prices or missed opportunities.

We are building Pod Network, a Layer-1 for open markets. Orders clear in frequent batch auctions, so the best price wins, not the fastest connection. Anyone can launch a market, its rules enforced by code. Allowing trading from anywhere, 24 hours a day 7 days a week.

Writing

## Comments

**macbudkowski.eth**: You can click on 'how it works' to learn about their architecture. Anyway, found the website and the description pretty sleek, and this quote: 

> Until now, infrastructure limitations have dictated the UX of Web3 products. We're inverting this with UX-driven infrastructure—UX requirements of products govern the updates that go into the infra layer.

sounds inspiring.