The Blockchain Built for What’s Coming
A Layer 1 bringing post-quantum cryptography, MEV-free execution, sub-second finality, and externally verifiable proofs to the foundation of the blockchain stack.
The Protocol
Four Commitments. No Exceptions.
Pyde doesn’t patch problems after launch. These four properties are baked into the architecture
Post-Quantum from Genesis
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.
MEV-Resistant by Construction
Transactions can be encrypted in the mempool with threshold-derived keys. The committee commits to an order at the DAG anchor before decryption shares are released. Front-running and sandwich attacks aren’t discouraged — they’re inexpressible in the protocol.
Built for Real Throughput
Consensus and execution run in a single binary, single process. A Mysticeti-style DAG advances rounds in roughly 150 ms and produces wave commits about every 500 ms. Realistic v1 targets are 10–30K plaintext TPS on commodity hardware, validated by the performance harness.
Decentralized by Default
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.
The Chain
Built for the Next Era of Blockchains.
Pyde is a Layer 1 designed from the ground up for a world where quantum computers exist, MEV is a solved problem, and any chain can verify any other — without asking permission.
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 DAG 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.
- on the roadmap
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.
- on the roadmap
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.