Technology

Full decentralisation

The protocol has no central server. Every participant (master block) is an isolated, self-governing block node. Data exchange happens via agreed channels that are manually created and cryptographically signed.

LMBI: block management model

• Each block = data unit + meta info + hash links
• Maximum size — 512 KB (optimised for weak networks)
• Blocks are chained together (similar to blockchain, but lighter)
• Blocks are immutable: new data is added as new versions
• No tables or SQL — only block structure with explicit links

Access and channel management

Connections can be revoked at any time. When a channel is broken, data stops flowing and the very fact of the channel is removed from the public structure.

• Data access is only possible with an active communication channel
• Each channel is a cryptographically signed agreement between two parties
• One-way and two-way connections are supported
• Even with a channel, data is available only if the key or decryption rights are present

Encryption and security

Even with physical access to the disk, nobody can decrypt blocks without the phrases and keys.

• All data is encrypted (AES-CBC)
• No session keys — only block access keys
• Each block is an independent encrypted entity
• Access keys never traverse the system and are not stored centrally
• Each block can have its own unique key or access scheme

WebSocket + Zero Sync

The platform uses WebSocket for real-time block operations. This delivers:

• Instant confirmations and data delivery
• Lower network and CPU load
• Offline scenarios (updates when a connection appears)

Updates between users happen without REST requests or APIs — only via WebSocket + hash control + event subscriptions.

Tokenisation and access

The new protocol token (NPT) unlocks compute access, enables delegated permissions and connects external services without compromising security.

• The protocol uses blind tokens — one-way, untraceable access keys
• Supports zk-coupons (Zero-Knowledge — prove without revealing)
• Confirmation mechanisms via nonce_id and channel signatures

Post-quantum protection

The architecture already supports migrating to quantum-resistant algorithms. We experiment with Kyber/Dilithium and can adopt them as NIST finalises the standards.

Even today, key lengths, agreement schemes and the lack of session keys create a high barrier for attacks, even with breakthroughs in computing power.

Event execution format

Every action is executed on a client event trigger. There are no server-side CRON jobs.

• There are encrypted rule blocks readable only by trusted executors
• Events are initiated on the client when the data is opened
• Scenarios execute directly in the client upon receiving and decrypting blocks

This allows launching complex processes (e.g. reporting, data collection, mailing) without a central server and with full control.

Summary: reliability, sovereignty, control

Novij Protocol is an engineering platform-protocol built on the principle of sovereign control: every owner fully governs their data, channels, security and architecture.

This is not a cloud service. It is a cryptographic system where you control everything: structure, links, access and execution. Even physical access to the server is useless without keys.

Roadmap

These milestones turn the technology into a profitable product: token-based payments → linear revenue growth, referral programme → exponential network effect without marketing spend.

• MVP Multi-Access — multiple administrators inside blocks.
• MVP Event Triggers — scheduled tasks.
• MVP Paid Access — tokenised payments for reading/writing data.
• MVP Referral DAO — referral programme with automatic reward distribution.
• MVP Template-ERP — ready-made business scenarios (restaurant, e-commerce, service).