+ 4NK PITCH V0.2 by Elie Sader +
+
+ 4NK
+ 
+ Plus Sûr, Plus Simple, Souverain
+Les utilisateurs paient toujours plus cher pour collaborer, gérer leurs identités et accéder à leurs propres données, tout en restant vulnérables aux piratages, rançongiciels et espionnage...
Et s'il existait une solution, juste à portée de main ?
+
4NK construit un cloud où vous restez propriétaire de vos données, alliant souveraineté et simplicité. Nous faisons de la souveraineté numérique une réalité technique, pas une simple promesse.
L'OS Cloud Auto-Souverain 4NK fonctionne comme une application sur votre équipement souvent sous-utilisé.
Nous restaurons l'autonomie des utilisateurs sur Internet en utilisant les clés privées comme fondement pour ancrer la propriété et les flux de travail de confiance. Notre approche est pragmatique, axée sur la confidentialité et alignée sur Bitcoin.
+
Pas de blockchain, pas de jeton : simplement une infrastructure côté client qui étend les propriétés de Bitcoin pour une utilisation quotidienne et des flux de travail collaboratifs.
+
+ Les utilisateurs possèdent et gèrent leurs propres clés en toutes circonstances.
L'infrastructure est construite autour de vous.
Contrôlez ce que vous partagez, avec qui et comment.
+ Utilisez du matériel existant ou sous-utilisé (ordinateur portable, serveurs...) pour exécuter l'application. Les nouveaux investissements CAPEX sont optionnels. Invitez d'autres à utiliser votre infrastructure (juste d'un navigateur).
+
+ Vos données, vos règles. Chiffrement par défaut, partage selon vos conditions. Stockage entièrement chiffré. Local ou distribué. Toutes les communications sont chiffrées et ne fuient pas de métadonnées grâce à la fonctionnalité de silentpayment de Bitcoin.
+
+ Collaborez et réseautez comme bon vous semble. La couche réseau est composée de nœuds qui peuvent être locaux ou distribués. De nombreux réseaux peuvent être construits à partir de nœuds ouverts ou en îlots fermés.
+
La proposition de valeur du Cloud Auto-Souverain est de vous permettre de créer n'importe quel flux de travail collaboratif dans le cloud.
+
Voici quelques exemples des services que vous pouvez déployer.
+
+ Stockage sécurisé pour vos documents. Partage sécurisé. Choisissez de stocker localement ou dans le cloud. Toujours entièrement chiffré par votre clé privée.
+
+ Exécutez un LLM uniquement sur le contenu que vous possédez et souhaitez garder privé. 100% local.
Sans aucune fuite de données
+ Créez des flux de travail documentaires sécurisés. Avec stockage et partage de données chiffrés. Gestion d'identités ultra-simple : créez, partagez, invitez des utilisateurs (ils n'ont pas besoin d'exécuter de nœud, juste d'un navigateur).
+
+ Vos Règles : gérez entièrement les règles, rôles, politiques d'accès et accès aux données pour n'importe quel flux de travail. Toujours avec des identités vérifiables. Piste d'audit avec preuves horodatées à chaque interaction.
+
Dernières actualités et projets du réseau 4NK.
+Notre équipe et comité consultatif sont composés de professionnels expérimentés et de passionnés de Bitcoin, dont un développeur principal. Notre mission est d'étendre les propriétés de Bitcoin, comme l'auto-custode, la confidentialité et l'autonomisation, à la vie numérique quotidienne.
+
+ 
+ 
+ 
+ Intéressé par des solutions cloud auto-souveraines ?
+ + Contactez-nous + +
+ 4NK
+ 
- - A revolutionary infrastructure redefining security and decentralization. - Our cutting-edge technology removes intermediaries and puts control in your hands. -
- - -Secure infrastructure with no single point of failure
-Distributed and cryptographically secured storage solutions
-Eliminating intermediaries for full control
-- 4NK represents a new era of technology infrastructure. - Our self-custodial cloud infrastructure approach revolutionizes how we think about - security, decentralization, and data control. -
-- With our cutting-edge technology, we eliminate traditional points of failure - and create a resilient, transparent ecosystem entirely under your control. -
-
- Ready to revolutionize your infrastructure? Contact us to discover how 4NK can transform your approach to security and decentralization.
-With the rise of online tools, we all—at work and at home—sit on underused resources. Think for a moment about your computer, your smartphone. Each day, these machines spend most of their time idle, waiting for your next action. Yet they hold immense computing, storage, and security capabilities. It's as if we left our cars idling in the garage, never really using the engine.
+ +Meanwhile, what do we do? We rent, at a high price, server power owned by a handful of American players. We hand over our documents, our conversations, our digital identities, our payments. Every time we log in, every time we click "accept," we reinforce our dependence:
+Centralized infrastructures are showing their cracks:
+We refuse a future where Internet balkanization and creeping dystopia become a reality, where trust erodes and simplicity is purchased at the price of sovereignty. Dystopias are no longer fiction—they're taking shape in our daily habits.
+ +What if the solution isn't "elsewhere," but already in our hands? What if digital sovereignty, security, and simplicity came not from ever more data centers, but from what we already possess—underused—on our own devices?
+ +This is a client-side serverless cloud—a model where:
+Every exchange becomes a verifiable contract, every use a proof, every device a building block of the infrastructure.
+ +With 4NK, this vision is already taking shape through:
+We choose to build this shift progressively and credibly. Over the next two to three years, we will lay the first stones with these services—serving regulated professions, SMEs, and critical sectors first—to prove that simplicity of use, strong security, and stakeholder sovereignty (for organizations and individuals) can coexist.
+ +In 2–3 years, 4NK will be the virtualized low-level implementation—a revolution of operating systems into active, sovereign nodes of the Internet. These are the first stones of an Internet where sovereignty is a technical property, not a political promise.
+ +We believe we must retake control of its digital infrastructure—not by imitating centralized models, but by inventing a new model: a trustworthy Internet, distributed by design, where sovereignty is engineered, not merely declared.
+ +Do we want to keep relying on fragile, costly, centralized infrastructures? Or do we want to build a digital sphere where freedom, trust, and simplicity are non-negotiable?
+ +We call on those who reject dependence, insecurity, and fragmentation to join this movement. The future of European digital life will not be forged by surviving a balkanized network, but by creating a shared, sovereign, simple, and verifiable space.
+4NK & Bitcoin: the custodian-killer infrastructure
+ +For fifteen years, Bitcoin has proven that a decentralized network can secure value without any trusted intermediary. Every block, every signature, every verification is performed by the users themselves. No need for a centralized custodian: everyone can verify, everyone can hold.
+But outside of payments, the digital world still relies everywhere on trusted third parties:
+These custodians capture data, impose costs, and create points of failure. They are the equivalent of banks before Bitcoin: convenient, but vulnerable and intrusive.
+ +4NK is a client-side infrastructure layer that extends Bitcoin's native properties to everyday digital uses:
+Everything is operated client-side (Client-Side Validation). No custodian.
+ +Just as Bitcoin killed the need for a central bank to hold and transfer value, 4NK kills the need for digital custodians to identify, exchange, store, and contract.
+This is not a new blockchain. This is not a token. It is the natural extension of Bitcoin:
+Every time, the model is the same: replace a custodian with Bitcoin + client-side.
+ +Making Bitcoin not only the currency of trust, but also the universal infrastructure layer of the digital world:
+To make Bitcoin not only the currency of trust, but also the universal infrastructure layer of the internet:
+An internet where the user is sovereign, verification is local, and custodians belong permanently to the past.
+4NK: the self-custodial cloud infrastructure.
+ ++ Looking for more context? Read the full Manifest. +
+Every time, the model is the same: replace a custodian with Bitcoin + client-side.
-Making Bitcoin not only the currency of trust, but also the universal infrastructure layer of the digital world:
Version: 1.0
+ Date: October 1, 2025
+ Source: Complete analysis of sdk_client, sdk_common, sdk_relay, sdk_storage, ihm_client, rust-silentPayments components
4NK is a decentralized system for collaborative process management based on the Bitcoin blockchain, using Silent Payments (BIP352) for identity and encryption. The system enables multiple parties to collaborate on processes with verifiable states, defined roles, and cryptographic validation rules.
+ +| Component | +Role | +Technology | +
|---|---|---|
| sdk_common | +Shared types and structures | +Rust (WASM-ready) | +
| sdk_client | +WASM client library | +Rust → WebAssembly | +
| sdk_relay | +Message relay and synchronization | +Rust + WebSocket | +
| sdk_storage | +Distributed key-value storage | +Rust + HTTP | +
| ihm_client | +Web user interface | +TypeScript + Web Components | +
| rust-silentPayments | +Silent Payments implementation | +Rust (dependency) | +
Device
+ ├─ SpClient (Silent Payment Client)
+ │ ├─ Scan Key (private)
+ │ ├─ Spend Key (private)
+ │ └─ Silent Payment Address (public)
+ ├─ SpWallet (UTXO outputs)
+ ├─ Pairing Process (OutPoint)
+ └─ Member (list of paired addresses)A Device represents a single physical device with its own cryptographic keys:
Main operations:
+A Member represents a set of devices belonging to the same entity:
Pairing is the mechanism for associating multiple devices to a single logical identity (member).
+ +Pairing steps:
+A Process is a state machine with defined roles, validation rules, and Bitcoin commitments. Each state transition creates a new Bitcoin UTXO.
+ +Key characteristics:
+| Field | +Description | +Type | +
|---|---|---|
| commitment | +Current Bitcoin commitment (OutPoint) | +OutPoint | +
| state | +Current state (data + metadata) | +ProcessState | +
| roles | +Role definitions and permissions | +Roles | +
| previous | +Previous state (for history) | +Option<ProcessState> | +
Each process defines roles with specific permissions. A role contains:
+Special role "apophis":
+A ValidationRule defines who can modify which fields:
Example: A rule with quorum=0.67 and min_sig_member=0.5 requires:
+CommitMessageValidationTokenA ValidationToken is a cryptographic signature proving a member's approval:
The system supports complex multi-signature schemes:
+Example scenario:
+The sdk_relay component provides real-time communication via WebSocket. All messages are JSON-encoded.
Message types:
+Client A → Relay: CommitMessage (new state proposal)
+Relay → All participants: Broadcast CommitMessage
+Client B → Relay: ValidationToken (signature)
+Client C → Relay: ValidationToken (signature)
+Relay → Client A: Forward ValidationTokens
+Client A: Aggregates signatures, creates Bitcoin tx
+Client A → Relay: CommitMessage (with on-chain proof)
+Relay → All: Broadcast committed stateThe system uses a distributed key-value storage (sdk_storage) for:
| Level | +Description | +Example | +
|---|---|---|
| Private (PCD) | +Encrypted data, only commitment on-chain | +Sensitive documents | +
| Public | +Readable by all network participants | +Paired addresses list | +
| On-chain | +Only state_id (32 bytes) in OP_RETURN | +State commitments | +
Private fields use AES-256-GCM encryption:
+create_process(roles, initial_state)CommitMessageCommitMessage with new stateobliterate(process_id)Protected against:
+Residual risks:
+For developers:
+For users:
+get_fields_to_validate_for_member()The 4NK identity and process system is built on an innovative decentralized architecture combining:
+This architecture enables various use cases:
+Strengths:
+Areas for improvement:
+
+ Document generated on October 1, 2025
+ Based on 4NK source code analysis (sdk_client, sdk_common, sdk_relay, sdk_storage, ihm_client)
+ View original specification (French)
+