Build an application.
Explore public digital assets, community applications, and open financial primitives. Contract interfaces, examples, and network access will be release milestones.
Builder readiness →QKITE MAINNET THE ENGINE
PUBLIC NETWORK · IN DEVELOPMENTOpen by design.
Built for participation.
A public Layer 1 direction for open participation, informed by post-quantum research.
TRANSACTION JOURNEYINTERACTIVE CONCEPT · NO LIVE NETWORK DATA
01 / AUTHORIZE AN ACTION
It starts with a signature.
A user reviews an action and signs it with their key. A good wallet makes the network, recipient, and requested action clear before submission.
AN OPEN NETWORK TAKES PEOPLE
Not one kind of user.
A whole community.
Mainnet is the public side of QKite. Its development priorities center on accessible participation, inspectable rules, and applications that can share a common network.
Operate a node.
Help validate and reproduce the network’s history. Node requirements, participation rules, upgrade procedures, and operator guides must be defined and tested.
Operator readiness →Use the ecosystem.
Follow the wallet, explorer, and DEX development tracks. Their release depends on network readiness, security review, and usable signing flows.
Explore the tools →THE INNOVATION LAYER
A shared canvas.
An open-ended future.
Build on shared state.
Public applications can coordinate around a common record, with explicit rules for how that record changes.
Make participation visible.
Public proposals, review, and network information form the direction for community participation and governance.
Explore open markets.
Exchange and other DeFi concepts belong to the public ecosystem roadmap. They remain planned, with no live market or financial return implied.
Let people inspect.
Explorer access, reproducible node operation, and clear protocol documentation are proposed foundations for an inspectable network.
DEVELOPER & OPERATOR RESOURCES
Know what comes next.
Public endpoints and release links will follow validated releases. The resource plan below shows what each audience will need.
01Technical documentation & whitepaperPlanned
Architecture, transaction format, contract interfaces, network assumptions, and a clear account of the public consensus and participation model.
Explore the research agenda →02GitHub & developer librariesPlanned
Versioned repositories, licensing, SDK examples, compatibility notes, and a contribution process. No public repository URL has been announced here.
See the library roadmap →03Node operatorsPlanned
Hardware sizing, reproducible installation, network configuration, monitoring, upgrade coordination, and recovery procedures. Participation and validator eligibility need published specifications.
04Testnet & faucetPlanned
A separated testing environment, connection details, reset policies, and test-only funds for exercising transactions. There is no live faucet or announced chain ID on this site.
05Public governanceProposed
A documented route from discussion to proposal, testing, review, and network adoption. Eligibility, voting rules, and upgrade authority are research questions, not established token mechanics.
Review the proposed upgrade process →DEVELOPMENT ROADMAP
A path to a public network.
Proposed development priorities. Timing and launch dates have not been announced; these milestones do not indicate completed releases.
01
Public-network foundations
Document participation, transaction rules, consensus assumptions, and governance questions.
Specifications & threat model02
Developer test environments
Develop node software, contract interfaces, SDK examples, operator guides, and test-only network access.
Nodes · Docs · Testnet · Faucet03
Review & network validation
Evaluate adversarial behavior, recovery, interoperability, and performance under stated test conditions.
Security & performance evidence04
Release & ecosystem readiness
Publish release criteria and operational guidance; coordinate wallet, explorer, and application readiness before announcing availability.
Mainnet · Vault · Explorer · DEXOPEN NETWORK. SHARED RESPONSIBILITY.
Good infrastructure
starts with good questions.
Follow the technical work behind Mainnet: post-quantum cryptography, network behavior, and release criteria.
Explore QKite Protocol ↗