The blockchain, finally.
Fair by default · anyone can run it · built to last
Pyde is a quiet attempt at what a blockchain could have been from the start. Not a faster copy of what already exists, but a base layer built around a handful of properties that should already be standard, and that no production chain combines today.
Trades that can't be front-run. On most chains, bots quietly tax ordinary users by reordering their trades. On Pyde, a transaction's place in line is locked before anyone, including the network itself, can see what it contains. There is no committee key to trust and no relayer to opt into, so front-running has nothing to act on. Users keep the price they signed.
One network, not another island. Every new chain splits liquidity and users a little further, and the bridges meant to reconnect them keep getting drained. Pyde is built to reach the rest of the world through its own security, not a bridge you have to trust. A Pyde transaction is verifiable by anyone today, and the parachain layer that connects it to other chains and to real-world data is the chapter we are building next.
A network anyone can run. A validator runs on an ordinary laptop, not a data center rig, and every seat on the committee carries one vote regardless of stake. No quiet centralization.
Fast, and built to last. Your transaction is final when the chain says it is, and it says so in about half a second. The cryptography protecting it is chosen to stay valid for decades, long after today's computers can no longer keep it safe.
Contracts run on WebAssembly, so teams build in languages they already know (Rust, Go, C, and AssemblyScript) and ship with a single tool, otigen. The work is deliberate, and documented end to end before it ships.
We would rather be plain about status than polished about it. Pyde is pre-mainnet. The architecture is designed, and the hard parts are built: the execution engine runs, the state layer is wired end to end, the developer toolchain and a one-command local devnet are shipped, and the native token standard works from start to finish. Consensus is live and being hardened under sustained, adversarial conditions.
What remains is the careful part. Proving the network holds up under real load, completing external security audits, and standing up the public infrastructure that lets anyone join. Mainnet ships when the work is complete, audited, and validated by an incentivized testnet. There is no public schedule, and we publish performance numbers only after a real multi-region harness has measured them, never lab estimates.
- The Pyde Book is the full story and the complete technical reference, from how the chain works to how it launches. Source lives at
pyde-book. - Pyde Improvement Proposals are where the protocol grows, one proposal at a time.
Open source today: the book, the improvement proposals, the cryptography (pyde-crypto and its browser build), the contract interface (pyde-host), the Rust and TypeScript SDKs, the contract templates, and the signed toolchain releases.
The engine, the otigen toolchain, the in-browser playground, the explorer, the faucet, and the website stay private during pre-mainnet engineering, and open as each stabilizes and security review allows. Access on request at info@pyde.network.
- Contributing, how to propose changes, the PIP process, and engineering standards.
- Security policy, vulnerability disclosure, scope, and safe harbor.
- Code of Conduct, our community standards (Contributor Covenant 2.1).
These apply across the org. Substantive protocol changes go through a Pyde Improvement Proposal in the pips repo.
- Website: https://pyde.network
- Book: https://book.pyde.network
- Email:
info@pyde.network - X:
@pydenet - Telegram:
t.me/pydenet - Security disclosures:
security@pyde.network
Code is licensed under Apache-2.0 (per-repo LICENSE files). The book is licensed under CC BY-SA 4.0.