The blockchain, finally.
Pyde is the Layer 1 where your assets stay secure, your trades stay fair, and anyone can run a node. Not as promises you have to trust — as properties the protocol enforces from the first block.
Built for
Who builds on Pyde
The businesses that can't afford their value stolen, front-run, or broken — and the teams that want their own chain without asking permission.
Payments & remittance
Move money across borders without the fees, delays, or reordering. Sub-second settlement on hardware anyone can run — value arrives fast, and arrives whole.
Exchanges & trading
Give your users execution that can't be front-run or sandwiched. Fair ordering is the protocol's default, so best price isn't a promise you have to police.
Tokenization & real-world assets
Issue bonds, deeds, funds, or IP meant to last decades. Post-quantum cryptography means the signatures protecting them won't expire under your assets.
DeFi protocols
Build lending, perps, and AMMs where traders keep the price they signed — no MEV tax skimming every swap, no relayer to trust.
Your own chain
As Pyde grows, launch an app-specific parachain — a game world, a confidential enterprise ledger, an oracle network — with no slot auction. Inherit Pyde's security and finality; set your own fees.
Built for the people who'll actually use it.
Pyde is technically dense underneath — but what it gives you depends on who you are. Three short reads, one for each audience.
The Protocol
Four Commitments. No Exceptions.
Pyde doesn’t patch problems after launch. These four properties are baked into the architecture
Safe through the quantum era
FALCON-512 signatures. Kyber-768 key exchange. Poseidon2 hashing. Every primitive in the protocol is post-quantum from the first block — no migration window, no per-app upgrade. For businesses, long-tail contracts signed today stay valid into the quantum era; for users, funds remain secure as quantum computing matures.
The price you sign is the price you get
Transactions can be encrypted in the mempool with threshold-derived keys. The committee commits to an order at the anchor before decryption shares are released. Front-running and sandwich attacks can’t be executed — no one can read a transaction before its order is locked. Users keep the price they signed; businesses don’t owe customers a trust assumption they can’t independently verify.
Fast enough for real apps
Consensus and execution run in a single binary, single process. Mysticeti consensus advances rounds in roughly 150 ms and produces wave commits about every 500 ms. Throughput scales with the consensus parallelism on commodity hardware — and we publish numbers only after a multi-region harness measures them, never lab extrapolations.
A network anyone can run
Validators run on modest hardware. Each committee seat carries one vote, regardless of stake size. The parachain layer that handles cross-chain calls and oracles is permissionless — anyone meeting the spec can operate. Enterprises can verify the chain on a normal machine; developer teams can launch their own parachain without a slot auction.
The Chain
Built to hold value through whatever comes next.
Designed from the ground up for a world where quantum computers exist, front-running has no edge, and any chain can verify any other — without asking permission. For the businesses that need it to settle, the developers that need it to extend, and the users that need it to hold value through whatever the next decade brings.
Build on Pyde
A Foundation You Don’t Have to Trust.
Pyde gives developers a base layer that handles the hard guarantees — so you build the application, not the security model.
Honest Ordering. Transactions execute in the order the protocol commits to before decryption. Your users keep what they meant to spend.
Quantum-Safe by Default. Every app on Pyde inherits post-quantum cryptography at the protocol level.
Trustless Interoperability. Pyde’s finality certificates are portable proofs — any chain that can verify FALCON signatures can run a light client and prove a Pyde block was finalized. Cross-chain calls go through the parachain layer with the same gas fee as a local transaction.
Predictable Performance. Roughly 150 ms rounds and sub-second wave-commit finality, sustained.
Maximum Security
Lose a Key, Not Your Account.
Account security on Pyde is a protocol mode, not a contract you deploy yourself. The architecture is built so a leaked private key is an inconvenience, not a catastrophe.
- available at mainnet
Native Multisig
Require any M-of-N signatures to authorize a transaction. Built into the protocol itself — no third-party contract to deploy, no per-app integration. If one of your keys leaks, the holder can’t move anything on their own.
- planned
Programmable Accounts
Attach a sandboxed policy to your account that runs on every transaction: spend limits, time locks, allow-listed recipients, social recovery, tiered authorization. Opt-in by design — simple accounts stay simple.
- planned
Native Session Keys
Issue scoped keys that can act on your behalf for one app, with hard caps on spend and a deadline. Games, AI agents, and consumer apps stop needing to wake up your wallet for every action. Revoke any time.
Mainnet ships with native multisig today. Programmable accounts and session keys are post-mainnet work — the protocol is designed to grow into them without breaking accounts that prefer to stay simple.
Build with Pyde
Everything you need to build on Pyde — architecture specs, RPC references, and integration guides.