Nokto
Composable, privacy-preserving receiving accounts on Midnight.
Alpha — do not use this for anything real. This is early, unaudited, in-progress work, published so it can be read and discussed. The
@nokto-protocol/*packages are not published to npm; every code sample on this site shows the intended shape of the interfaces, and the only way to run any of it today is to build from source. Proof generation and transaction submission are unproven against a real network. Nothing here is audited. Do not put value, personal data, or production keys anywhere near it.
Income arrives across accounts that do not compose. A rideshare platform, a marketplace, a payment processor, a subscription biller, and increasingly an agent earning on someone's behalf — each knows one fragment, none know the whole, and so none of it counts toward credit. The person is, on paper, poorer and less creditworthy than they are in fact.
Nokto makes the fragments composable and provable without making them public. A lender learns one number's relation to a threshold, and how far that number can be trusted. It does not learn how many accounts contributed, which they were, or what any of them paid.
Nokto is an open protocol, Apache-2.0. This site documents the protocol: the contracts, the circuits, and the packages anyone can build against. Nokto Platform maintains it, and builds a commercial product on it — on the same terms as anyone else. When these packages publish, its product will install them from the registry exactly as you would, and will never reach past them by path or private hook. See SCOPE for the boundary between the protocol and anything built above it.
Where to go
- Start here — build the repository from source and verify your first disclosure.
- Concepts — accounts, composition, assurance tiers, and disclosure and consent: the vocabulary the rest of the site assumes.
- Guides — write a verifier or an issuer
adapter against
@nokto-protocol/plugin-kit. - Reference — the five operations, the predicate registry, the signed message layout, and the ten invariants (eight enforced in-circuit, two by process).
- Releases — what is true of the protocol at the current version, the toolchain it was verified against, and what is not yet demonstrated.
- Governance — what is part of the protocol and what is built above it, and how changes to the consensus surface are proposed.