About the Project

Novij Protocol is a distributed network layer for applications and data. The SDK encrypts application payloads and signs entries on the user’s device; Relay validates signatures, operations, and billing, while Storage keeps and serves binary blocks without decrypting their content.

Novij Protocol — distributed network layer for secure applications

Our Mission

We are building a common protocol layer in which owners keep their keys and control access, while applications use the same verifiable storage, exchange, and settlement rules.

  • Append-only blocks and entries with a verifiable hash chain.
  • One post-quantum profile, ntp-pq-v1: ML-DSA-65 and ML-KEM-768.
  • Group access through per-recipient ML-KEM envelopes without sending keys to nodes.
  • A public Network System Chain for settings, node registries, and governance.
  • SDKs, APIs, and a module system for application integrations.

Architecture in Brief

Roles are separated: Relay registers wallets, binds blocks, validates signatures, nonces, transfers, DSR, ZK, and billing; Storage provides append/read/batch operations and stores Protocol v3 binary blocks.

Personal and project meta-blocks form append-only chains with a stable root. When a chain fills up, verified checkpoints and publish-last rollover extend it without rewriting history.

Who Benefits

Novij Protocol helps teams that need autonomy, privacy, and auditability. A few reference scenarios:

  • Business applications: ERP, CRM, documents, and workflows with project meta-blocks, roles, and an audit trail.
  • Files and backups: local encryption, Storage blocks, and paid ZK coverage.
  • Financial flows: NPT transfers and constrained delegated spending through DSR.
  • Modules and services: signed manifests, registry/code chains, and isolated application runtime.

NPT Token Utility

New Protocol Token (NPT) is used for protocol operations, storage, and economic rules resolved from active System Settings.

  • Storage is paid through a ZK prepaid storage lease priced per block-day.
  • Relay and Storage nodes pay a join fee, while storage-lease revenue is split between their pools according to availability.
  • Proposal deposits, penalties, and join fees move to DevFund/penalty wallets selected by System Settings — tokens are not burned.
  • Total supply can increase only through a TOKEN_MINT governance proposal; there is no fixed hard cap.

Current Profile

The active runtime profile is Protocol v3 / ntp-pq-v1. The specification, SDK, Relay, and Storage evolve together; applications obtain the operational topology from a verified Network Registry instead of a fixed server list.

Team and Contact

For partnerships, integrations, or research inquiries, message us on Telegram @novijceo.