⋮⋮⋮ GRIDNET OS was designed with the end-user in mind. It aims to allow for user experience resembling the one known from DOS, LINUX, Windows and Mac OS X centralized operating systems. We took inspiration from these all. Both commands - many of which come with comprehensive built-in MAN pages - and UI.

Yes, ⋮⋮⋮ GRIDNET OS boasts a Graphical User Interface. Which is also 100% decentralized.

How can a UI be decentralized? Once a user connects to a node, it would deliver what we call a Bootloader, which encapsulates IP addresses of other nodes discovered through Kademlia. The Bootloader would then keep fetching assets (code, images, JavaScript modules, whatever) from possibly multiple peers at once, even for a single UI session, while verifying integrity of these.

It gets way more abstract than that. Imagine the very first successful implementation of the concept of Decentralized Processing Threads (DPTs). Each UI dApp can spawn many DPTs each of which executess byte-code of GridScript language. The byte-code may result in either textual output (when executed from Terminal - SSH or WebGL rendered Terminal UI dApp), or code execution may result in Basic Encoding Rules (BER) encoded meta data - when DPT is spawned by a front-end component of an UI dApp. All UI dApps are hosted on-chain. BER encoded results of GridScript execution are onion-routed (custom ECC encryption everywhere), at the final stage through a Web-Socket, to finally arrive at a web-browser where the front-end sub-system of GRIDNET OS routes (the now decoded) meta-data to particular instances of front-end components of UI dApps. As far as UI dApps can tell everything is ECMA6 events' driven.

Execution of each and every GridScript instruction in a DPT is crypto-incentivized (off-the-chain).

The computer-vision enabled mobile app (GRIDNET Token) plays a crucial role in this architecture. Whenever any kind of incentivization / payment / authentication is needed user simply scans a QR code.

The following peer-reviewed Research paper does justice in explaining the overall architecture: here.

Our Community has massive plans. Decentralized applications of any kind one can imagine. Decentralized Web, decentralized social media (X / Facebook)-like UI dApps, games, business applications, decentralized AI, everything.

The system, especially the UI is in alpha stage, even still - it already boards quite a few useful UI dApps (decentralized applications). It already allow for anonymous web-browsing, file sharing, drag&drop file uploads from native OS, communication, collaboration, end-to-end encrypted group audio / video streaming, multi-party conferencing where you share you screen(s) or particular window(s) from your native operating system, value transfers (both on-the-chain and off-the-chain) and gaming (feeling like looking for some Gold? Launch GridCraft, grab a metal detector and be on your way! It's a game but under the hood it employs some cutting-edge achievements in cryptography to allow for rewards for such minuscule activities as finding stuff within a game).. or you might want to play Snake (also multiplayer!) through the decentralized SSH Terminal Services.. yes.. each node operating the decentralized state-machine is capable of spawning a Shell for you.

Most commands are compatible with Unix/Linux and to some extent, with DOS. Decentralized File System supporting Access Control Lists (ACLs) through and commands? Sure! Many in-terminal commands come with built-in MAN-pages just run or .

The onboard Firewall? It comes with kernel-mode integration with Micorosft Windows for maxmium efficiency.

Maybe you are feeling like deploying a decentralized web-site of your own? Editing it straight within the UI? Be our guest! Maybe you would like to deploy a NFT, by dragging and dropping a file from you computer and setting ownership through ? It's all possible.


As for communication note that we were the first to come up with a data-exchange protocol provably Sybil-proof in any kind of computer networks.

All of the communication sub-systems employ these research findings. If you use collaboration, communication UI dApps on ⋮⋮⋮ GRIDNET OS, data does not flow through any server. No server is involved even during the WebRTC connection establishment phase. It's all decentralized. Definitely feel invited to check out some of our research papers. The only trusted thing from your perspective is your mobile device.

Once you install the mobile app (available for both iOS and Android), Hexi (our in-system AI) would guide you through setting up your public/private key pairs. Then, whenever your consent is needed, you would simply scan QR code displayed on screen (it can be rendered in UI session rendered through WebGL, but also in terminal session over SSH through UNICODE 1.1. half-blocks for maximum in-terminal data-density). Remember, it's an alpha stage. We've been implementing it on YouTube LIVE almost each and every day since the early 2017. The entire system is backed by GNC cryptocurrency which is live and tradable.

To find yourself in the center of the Action, feel invited to join our Discord community in particular. While YouTube LIVE streams are for accountability and code quality assessment, the #Live-Development Discord channel contains lots of hourly Live commentary. See https://mag.gridnet.org for in-depth articles, documentation. New releases and additional materials including comprehensive Release Notes are always made available at https://talk.gridnet.org