Technical Architecture
Nanopublications are published in a decentralized network of services and applications. All components are open source, and the core services run as multiple instances.
How it fits together
- A client, such as Nanodash, a library, or the command-line tool, creates a nanopublication, signs it, and sends it to any Nanopub Registry.
- The registries replicate nanopublications among each other.
- Nanopub Query instances load the nanopublications from a registry into triple stores. They offer SPARQL endpoints over all nanopublications, as well as over subsets such as a single type, a single public key, or the last 30 days. They also offer a REST API whose queries are themselves published as nanopublications.
- Nanodash and other applications read through Nanopub Query and publish through the registries.
Because nanopublications are immutable and identified by hashes, any copy can be checked against its URI, no matter which instance served it.
Core components
Nanopub Registry (instance, code) is the second-generation service for publishing and retrieving nanopublications in a decentralized fashion.
Nanopub Query (instance, code) is the second-generation service to query nanopublications. It allows for decentrally querying the published nanopublications via a number of SPARQL endpoints covering different subsets and aspects of nanopublications.
Nanodash (instance, code) is a general client and user interface for nanopublications. It allows for user-friendly browsing, querying, and publishing of nanopublications, but can also be used as an API and intermediary layer for other services to build upon.
The legacy nanopub-server (instance, code) still holds the old (unsigned) nanopublications, but otherwise no longer has a function in the latest generation of the ecosystem.
Auxiliary components
Nanopub Monitor (instance, code) observes the services that run the core components of the ecosystem.
Vodex (code) is a vocabulary index service, used to provide auto-complete on third-party vocabularies.
nanopub-http (code) provides features of the nanopublication libraries over HTTP, most importantly signing and publishing.
See also
- A Robust Decentralized Infrastructure for Trust-Aware Open Knowledge Sharing (ISWC 2026), the paper that describes this ecosystem and its trust algorithm in detail
- Tools for the libraries and the command-line tool
- Applications for third-party systems that use nanopublications