Contract SDKs
Ledger contract interfaces, examples, and reproducible execution tooling, beginning with the Go SDK direction.
QKITE PROTOCOL THE BRAIN
RESEARCH / ENGINEERING / REVIEWBetter questions.
Stronger foundations.
Research for the quantum era.
From post-quantum cryptography to deterministic execution, QKite Protocol is the research home for the private Ledger and public Mainnet.
Explore the research agenda ↓POST-QUANTUM CRYPTOGRAPHYEXECUTIONVERIFICATIONNETWORK SYSTEMS
ONE RESEARCH HOME. TWO DEPLOYMENT CONTEXTS.
Shared questions.
Different constraints.
Select a research lens to explore where the work applies. Public participation and enterprise confidentiality demand explicit assumptions of their own.
R / 01RESEARCH AGENDA
COMMON FOUNDATIONS
Make the trust assumptions explicit.
Cryptographic choices, key lifecycles, reproducible execution, and verifiable history connect both deployment modes. Each needs documented assumptions and evidence from testing.
- Standardized post-quantum primitives and migration planning
- Deterministic execution, bounded resources, and reproducibility
- Security review, failure models, and measurable performance
QUESTION → PROTOTYPE → REVIEW → VALIDATION
POST-QUANTUM DIRECTION
Standard primitives.
Careful engineering.
The Ledger design names ML-DSA for signatures and ML-KEM for establishing shared keys. Protocol research examines how primitives are composed, implemented, and maintained—not just which algorithms are selected.
Standards are a foundation. Secure implementations also depend on parameter choices, key handling, testing, and review.
FROM THE ENGINEERING NOTEBOOK
Understand the thinking.
Short explainers grounded in the Ledger architecture and the new public-network research agenda.
NOTE 01 / PRIVATE NETWORKSA shared record does not require shared payloads.
+
In the Ledger design, collection members receive and execute a private payload. They sign the result. Validators then check matching attestations against the policy committed for that action. This separates verification of agreement from access to the business record.
Membership remains declared. Privacy therefore needs a clear threat model: who sees payloads, who sees metadata, and what a fingerprint can reveal.
Read the architecture →NOTE 02 / EXECUTIONWhy deterministic contracts matter.
+
Organizations must be able to reproduce the same result from the same inputs. The Ledger direction uses bounded WebAssembly execution, with Go as the first SDK direction, and excludes uncontrolled clocks, randomness, network calls, and file access from contract execution.
Reproducibility is a design requirement to validate, not a substitute for reviewing business logic or resource limits.
NOTE 03 / PUBLIC NETWORKSParticipation is part of the protocol.
+
A public chain needs explicit answers about node participation, consensus, transaction admission, resource costs, and upgrades. Those choices shape who can use the network and how it behaves under adversarial conditions.
Mainnet’s research track will need its own published model. Enterprise organization membership rules should not be assumed to describe public participation.
Explore public-network readiness →OPEN-SOURCE DIRECTION
Research becomes useful
when others can build on it.
Planned library and publication tracks. Release links, licenses, and compatibility information will be published with the work.
Verification tools
Policy inspection, attestation verification, test vectors, and tools that help reviewers reproduce results.
Research publications
Threat models, post-quantum cryptography engineering papers, measured evaluations, and public testnet reports.
A PROPOSED PATH FOR CHANGE
From an idea
to a network upgrade.
Major changes need a visible record of motivation, tradeoffs, evaluation, and adoption. This proposed process informs future public and private release practices.
- 01
Propose
Describe the problem, affected deployments, compatibility, and security assumptions.
- 02
Review
Invite technical scrutiny and document alternatives and unresolved concerns.
- 03
Validate
Exercise implementations in test environments and publish the evidence.
- 04
Coordinate
Define release criteria, adoption authority, migration, and rollback procedures.
DEVELOPMENT ROADMAP
From research
to reviewed releases.
Proposed development priorities. Timing and launch dates have not been announced; these milestones do not indicate completed releases.
01
Specify the assumptions
Document cryptographic composition, key lifecycles, threat models, and differences between deployment modes.
Cryptography & architecture02
Build reproducible foundations
Develop contract SDKs, test vectors, policy inspection, and verification tools with clear versioning.
SDKs & open-source libraries03
Evaluate and publish
Review implementations, measure behavior, and publish technical papers and test-environment reports.
Research notes · Whitepapers · Testnet reports04
Propose and coordinate upgrades
Document compatibility and migration; review major proposals and define release criteria before network adoption.
Ledger & Mainnet upgrade proposalsRESEARCH THAT REACHES THE REAL WORLD