<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aleksej Sokolov on Medium]]></title>
        <description><![CDATA[Stories by Aleksej Sokolov on Medium]]></description>
        <link>https://medium.com/@ness-main-dev?source=rss-e0d5794ff45d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Mv_5RPOJco-OYAVI9hqs8g.jpeg</url>
            <title>Stories by Aleksej Sokolov on Medium</title>
            <link>https://medium.com/@ness-main-dev?source=rss-e0d5794ff45d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:18:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ness-main-dev/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Services and Tokens]]></title>
            <link>https://ness-main-dev.medium.com/services-and-tokens-5a009df2e2bc?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a009df2e2bc</guid>
            <category><![CDATA[public-key-cryptography]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[email]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 23:19:11 GMT</pubDate>
            <atom:updated>2026-11-21T23:19:11.609Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vXdaASL2HsjV-IeJN9OV6g.jpeg" /></figure><h3>Main concept</h3><p>Main concept for all services is “Blind Service Smart Client”. Blind service, means that service is doing it’s work and it doesn’t know everything about client and what client is doing. The Client doesn’t serve the server anymore, now Client is free and Server serves the Client. Only simple actions are made by services. The file-service is for storing files (touch, upload, download, delete). The mail service is for sending and reading messages (send, read). All logic is stored on the client and works on the client (encryption, decryption, search, rendering … ). This two services are enough to make almost everything on the web …</p><h3>Tokens</h3><p>The are two major types of tokens, time token and payment token.</p><p>Time token is used for registration and in this case timestamp is a date and time of registration. The address is payment for registration, it also can be used for payment for subscription. You can always determine the time of subscription (timestamp — token.timestamp) and you can always determine the sum of incoming transactions (NCH coin hours) to token.address.</p><p>The formula is simple:</p><pre>if (sum &gt; ((timestamp - token.timestamp) / seconds_in_day) * price_of_day) then<br>  subscription_is_valid = true;</pre><p>Where <strong>sum</strong> is sum of incoming transactions to token.address.</p><p>Payment token is used for various kinds of payment. This can be payment for product, payment for traffic or payment for any kind of service … Payment token concept goes beyond services and can be used other payment applications.</p><h3>Terms</h3><p><strong>Token<br></strong>A string including a NESS address, data, random data, timestamp and a signature of all previous items.</p><p><strong>Slot<br></strong>A signature part of a token, can be used as part of URL address.</p><p><strong>Container<br></strong>A storage for storing files, messages and other data. The container is accessable by slot.</p><h3>File Service</h3><p>File service needs only one type of token — time token. The user pays for subscription time. The user has access to files container and can perform simple actions with files: touch, upload, download, delete. Each file is shared and can be downloaded by a anyone who has a link. File system structure is stored on a client side.</p><h3>Mail Service</h3><p>Mail service needs two types of tokens: time token for slot registration and payment token to pay for messages to be sent. Payment token creates a good spam protection, if you pay for each message you want to send then spamming is pointless.</p><p>Mail service has one or many message containers, they are accessable through registration slot (slot part of registration token). Users who has registration slot can read messages from a message container. To write a message to a message container user need both registration slot and payment slot.</p><p>The message can be both personal and anonymous. If you have payment token for 10 messages you send this messages anonymously or you can sign each message with you keypair and address each message to any user registered in blockchain.</p><p>All logic is stored inside client and messages, for example, you can create a bots similar to a telegram bots.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a009df2e2bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node and Client Communication]]></title>
            <link>https://ness-main-dev.medium.com/node-and-client-communication-1a1b1acb5b53?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a1b1acb5b53</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[public-key-cryptography]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:58:52 GMT</pubDate>
            <atom:updated>2026-11-17T14:58:52.575Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AtOWutEOZP4FWvpxjyqDOg.jpeg" /><figcaption>Communication scheme</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5gpjjq4zchuLMETnmFIZAw.png" /><figcaption>Mind Map</figcaption></figure><p>The problem with communication between Client and Service Node is already solved twice, first time with public key cryptography and public key placement in blockchain for both Client and Service Node, second time using <a href="https://medium.com/@ness-main-dev/token-authentication-final-cut-22f6217cfaad">tokens</a>.</p><p>The second and also very important problem is safe communication between Client and Personal Node.</p><p>Why do they need to communicate ?</p><p>There are many reasons:</p><ol><li>The client must have place, where to store it’s keypair, ciphers, tokens and other important and vulnerable data.</li><li>The client must have access to blockchain, to Emercoin blockchain for storing and reading the NVS values, and to NESS blockchain for payment operations.</li></ol><p>How to solve this problem ?</p><ol><li>SSH communication between Client and Personal Node — safe but not convenient.</li><li>Web interface on Personal Node with manual copy and paste operations — not safe and not convenient.</li><li>Move user interface on client (web interface will be the most simple). Use HTTP and public key cryptography to encrypt and sign every request and every response. This choice is both safe and convenient.</li></ol><h3>Initialization</h3><ol><li>The Client generates the keypair for communication with Personal Node.</li><li>The user copies Public Key from Client.</li><li>The user enters Personal Node using standard SSH gateway.</li><li>The user executes <strong>generate_keypair.sh</strong> script on Personal Node.</li><li>The user executes <strong>add_pubkey.sh &lt;client pubkey&gt; </strong>script on Personal Node, where <strong>&lt;client pubkey&gt;</strong> is public key from client user has previously copied.</li></ol><h3>Workflow</h3><ol><li>The client reads Public Key from Personal Node and stores it in memory.</li><li>The client encrypts the message using Personal Node Public Key and signs everything with it’s Public Key and stores everything in JSON format.</li><li>The Client send message to Personal Node.</li><li>The Personal node checks the signature (using Clients Public Key) and if signature is correct, decrypts the message using it’s Private Key.</li><li>The Personal Node sends response to Client in same JSON format. The response data gets encrypted with Clients Public Key and signed with Personal Nodes Private Key.</li><li>The Client receives response from Personal Node, checks the signature using Personal Nodes Public Key and is signature is correct, decrypts response contents using it’s Private Key.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a1b1acb5b53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Token authentication final cut.]]></title>
            <link>https://ness-main-dev.medium.com/token-authentication-final-cut-22f6217cfaad?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/22f6217cfaad</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[authentication]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Sun, 18 Oct 2026 07:06:58 GMT</pubDate>
            <atom:updated>2026-11-19T19:19:55.909Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hgAnTnLqJI1jXORxLHALXg.jpeg" /></figure><p>This article is finalization of two previous pieces <a href="https://ness-main-dev.medium.com/token-authentication-complete-3ae633c9a75e">one</a> and <a href="https://ness-main-dev.medium.com/token-authentication-5683eecc7b30">two</a>. Token authentication is realization of “Pay for registration” concept. This concept has several benefits: no CAPTCHA which collects your data, no stupid and over-complicated OAUTH, no other stupid things like TWO-FACTOR authentication.</p><p>Our conception is base on generated tokens. Each token are generated by user request and there can be infinite number of tokens because generated token is not stored, it doesn’t need a storage because it can be always checked using electronic signature. Each token is burnable token, that means, if it’s not payed in BURN_TIME (5 minutes will be fine) it will be burned.</p><p>Each token contains cryptocurrency address, unix timestamp (time of creation), random data and signature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*ADyqH63FmIh2S2tmY54bxw.png" /></figure><p>SLOT is equal to signature of address timestamp and random data. SLOT is user for registered user access after token is payed and payment is checked.</p><p>The addresses are pre-generated (as more as better, BURN_TIME * 2 will be fine). Pre-generated addresses stored in cryptocurrency wallet and in JSON file. There can be infinite number of tokens but we have limited number of addresses, that’s why the addresses are stored. They are stored with the associated token’s timestamp to determine which addresses are used inside unburned tokens and which addresses and which addresses were used inside burned tokens and which addresses were never used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*biAh34SyIiHTbT7LMhzZGw.png" /></figure><p>The newly generated token uses unused address (not used in other unburned tokens).</p><p>If this newly generated token is not payed in BURN_TIME seconds, it becomes burned token and the associated address if free to use (it’s older than BURN_TIME), but before the toked is burned it’s address is used (it’s younger than BURN_TIME).</p><p>If the token is shown to user, the appropriate addresses timestamp is renewed to now().</p><p>If the token is payed and after payment the token is checked, the appropriate address is deleted from the addresses list. After the check() action the user’s SLOT is created. The SLOT is part of the token (SLOT is equal to signature of address timestamp and random data) and is used for user’a access to his account.</p><p>What if User pays but not checks the token ?</p><p>In this case user will pay someone else’s token.</p><p>What if no free addresses are left ?</p><p>If we have enough addresses this probability is very low, but if it happened that mean’s someone is making a brute-force attack.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22f6217cfaad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blockchain and it’s role]]></title>
            <link>https://ness-main-dev.medium.com/blockchain-and-its-role-4c79ee5f1801?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c79ee5f1801</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Sun, 23 Aug 2026 12:11:18 GMT</pubDate>
            <atom:updated>2026-08-23T12:11:18.705Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*pJxLh7nleo9BpD5fRY2hrQ.png" /></figure><p>The main role of the blockchain is to connect all the data from the internet and beyond … Blockchain is a glue which connects different types of data, a container of links to different parts of global data.</p><p>How to connect different types of data using blockchain ?</p><h3>WORM</h3><p>WORM is Wold Object MaRcup language or in other words, HTML for data.</p><p>Worm is a collection of objects. The object can be a real world object (human, location, product …) or a cyber world object (user, server, encrypted data …).</p><p>Entity entity is a special type of object. Entity has a keypair and using this keypair entity can do two important things:</p><ol><li>It can own other object and entities using electronic signature.</li><li>It can send encrypted messages to other entities using public key encryption.</li></ol><p>Small WORM fileas are stored in a blockchain (Emercoin) and big WORM files are stored in torrent network (IPFS is best suited for this role).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c79ee5f1801" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Memorandum of free internet]]></title>
            <link>https://ness-main-dev.medium.com/memorandum-of-free-internet-0b0328e5f72b?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b0328e5f72b</guid>
            <category><![CDATA[liberty]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[memorandum]]></category>
            <category><![CDATA[freedom]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Sun, 12 Jul 2026 23:34:09 GMT</pubDate>
            <atom:updated>2026-07-15T07:11:17.137Z</atom:updated>
            <content:encoded><![CDATA[<ol><li>We support publicity.</li><li>We support privacy.</li><li>We support peoples freedom of creative and productive collaboration.</li></ol><h3>Meaning of Privacy and Publicity</h3><p>Publicity and Privacy are basic rights of the internet.</p><p>Privacy is a right to be anonymous for entity or a group of entities.<br>Privacy is a right for private communication between two or more entities.<br>Entity can be human, cyborg, any kind of device connected to internet, any software or neural network capable of independent communication.<br>Privacy is not possible without encryption, that means privacy includes a right for any kind of encryption.</p><p>Publicity is more complicated concept …</p><ol><li>Publicity is a right to be heard for any conscious being.</li><li>Publicity is freedom of any kind of knowledge (scientific or humanitarian).</li><li>Publicity is transparency in legislation, lawmaking, and all types of contracts.</li></ol><h3>Balance between Privacy and Publicity</h3><p>Everyone has a need to be public and private simultaneously, but it’s important to find a balance between privacy and publicity. One part of your personality is public (for example your C.V.) and other part is private (usually your personal life).</p><h3>Need of this rights</h3><p>Without Publicity and Privacy internet will become an instrument of totalitarian control.</p><h3>Communication</h3><p>What is communication ?</p><p>Internet is communication network and everything what happens in internet can be described as communication.</p><p>Without basic rights (publicity and privacy) any kind of communication will be controlled.</p><h3>Decentralization and it’s role</h3><p>What are decentralized cervices ?</p><p>Decentralized cervices are services with no central authority and no intermediaries. Examples of decentralized services are cryptocurrency, blockchain, torrent network.</p><p>Decentralized services is BASEMENT for freedom of communication.</p><p>Centralized communication will always be controlled.</p><p>Centralized means belonging to state or one organization.</p><h3>Collaboration</h3><p>Collaboration is important type of communication.</p><p>There are two kinds of collaboration, creative and productive.</p><p>Creative collaboration is when conscious beings collaborate to create something (fizical or intelectual). The initial aim of the internet (ARPANET) was creative collaboration.</p><p>Productive collaboration is when all members of collaboration get any kind of profit (trade, labor, any kind of financial operations). Any kind of fraud is not productive collaboration.</p><p>The main activity of INTERNET is collaboration between conscious beings, all other activity is no more than a white noise. The freedom of INTERNET can be described as freedom of creative and productive collaboration.</p><h3>What is open source ?</h3><p>Open source includes a publicity principle and creative collaboration.</p><h3>What is cryptocurrency ?</h3><p>Cryptocurrency is a form of decentralized productive collaboration.</p><h3>HOW IT WORKS ?</h3><p>This works for you if you place this memorandum text in a public place together with your name.</p><h3>Future additions</h3><p>This memorandum is collaborative creativity and is free to future additions.<br>The conditions for modification of this memorandum:</p><ol><li>All later versions of this memorandum must contain in self the first version. The first version of memorandum can not be modified with changes in it’s mean and internal logic.</li><li>The author of addition or additions must name himself.</li><li>The new version of memorandum must have readable and meaningful name and if new version is big enough, it also must contain readable and meaningful description.</li><li>The new version works for those, who agree with it by placing the text of new version in public place together with his name.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b0328e5f72b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Emersite]]></title>
            <link>https://ness-main-dev.medium.com/emersite-68d443a909f2?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/68d443a909f2</guid>
            <category><![CDATA[website]]></category>
            <category><![CDATA[ipfs]]></category>
            <category><![CDATA[emercoin]]></category>
            <category><![CDATA[sitemap]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Fri, 12 Jun 2026 13:16:56 GMT</pubDate>
            <atom:updated>2026-06-12T13:16:56.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gjnSkxhKtmTwCme8YdxHQ.jpeg" /></figure><p>The idea is simple: website inside IPFS network with a SITEMAP inside Emercoin NVS.</p><h3>IPFS</h3><p>All pages, images, etc will be placed inside IPFS files.<br>All links inside pages (HTML) will have the following format <strong>ipfs://v8q3hq3fhq3fh3q489fh</strong></p><h3>NVS</h3><p>name: worm.emersite.sitename<br>value: SITEMAP in &lt;WORM&gt; format</p><h3>Link</h3><p>URL format: <br>Link to a site nsite://sitename<br>Link to a resource (page or other resource): nsite://emersite/h389457ty38th</p><h3>SITEMAP</h3><pre>&lt;worm&gt;<br>&lt;site&gt;<br> &lt;title&gt;Emersite&lt;/title&gt;<br> &lt;description&gt;Hello world from emersite !&lt;/description&gt;<br> &lt;keywords&gt;Hello,world&lt;/description&gt;<br> &lt;sitemeap&gt;<br>  &lt;page url=&quot;ipfs://eheghgeh3q489fh&quot; description=&quot;Main page&quot; keywords=&quot;Main,page&quot;&gt;Main page&lt;/page&gt;<br>  &lt;folder name=&quot;Folder 1&quot;&gt;&lt;/folder&gt;<br>   &lt;folder name=&quot;Sub folder&quot;&gt;<br>    &lt;page url=&quot;ipfs://he5hghfghrehfgh&quot; description=&quot;Page inside folder&quot; keywords=&quot;one,two&quot;&gt;Page inside folder&lt;/page&gt;<br>   &lt;/folder&gt;<br>  &lt;/folder&gt;<br> &lt;/sitemap&gt;<br>&lt;/site&gt;<br>&lt;/worm&gt;</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68d443a909f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dockerization]]></title>
            <link>https://ness-main-dev.medium.com/dockerization-ea101b6705d0?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea101b6705d0</guid>
            <category><![CDATA[privateness]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Fri, 12 Jun 2026 08:10:49 GMT</pubDate>
            <atom:updated>2026-06-12T08:10:49.317Z</atom:updated>
            <content:encoded><![CDATA[<h3>Decision</h3><p>There are two kinds of Privateness users:</p><ol><li>Service provider — the owner of ness services.</li><li>Client — the user of ness services.</li></ol><p>From client’s perspective you need at least one device — personal node. But the device itself has several limitations …</p><ol><li>You need buy the device.</li><li>You need to connect this device to a network and this is not always possible. For example this can be a non-friendly environment, where you can connect only one main device (PC or Smartphone) to network.</li></ol><h3>Advantages</h3><ol><li>You don’t need to buy separate device.</li><li>The Docker environment can be installed on any operating system and almost any device.</li></ol><h3>Disadvantages</h3><p>It’s more safe to store encryption keys outside your main device. In this case external device has huge advantage.</p><h3>Different systems</h3><p>Linux is the default docker environment</p><p><a href="https://docs.docker.com/desktop/setup/install/windows-install/">Windows</a></p><p><a href="https://docs.docker.com/desktop/setup/install/mac-install/">Mac</a></p><p>Android: <a href="https://medium.com/@kumargaurav.pandey/docker-on-mobile-that-too-without-root-how-7b0848833c42">Docker on Mobile, that too without root, How?</a> <a href="https://www.geeksforgeeks.org/devops/setting-up-docker-for-android-development/">Setting Up Docker for Android Development</a> <a href="https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27">Docker on Android</a> <a href="https://play.google.com/store/apps/details?id=com.pavit.docker">Docker Manager</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea101b6705d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Addition to nodes]]></title>
            <link>https://ness-main-dev.medium.com/addition-to-nodes-b550bc820e18?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b550bc820e18</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[ipfs]]></category>
            <category><![CDATA[public-key-cryptography]]></category>
            <category><![CDATA[torrent]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Mon, 27 Apr 2026 03:44:55 GMT</pubDate>
            <atom:updated>2026-04-27T03:44:55.673Z</atom:updated>
            <content:encoded><![CDATA[<p>This is an addition to <a href="https://ness-main-dev.medium.com/nodes-b1391ad5e607">previous article about nodes</a>.</p><p>I decided to separate the nodes to 3 types:</p><ol><li>Crypto-device</li><li>Personal node</li><li>Service node</li></ol><h3>Crypto-device</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_MiVXy750TsNQWVKHRW9xQ.png" /></figure><p>What it is ?</p><p>Basicaly, it’a a <a href="https://www.gnupg.org/">GPG</a> on a device or, it also can be compared to a <a href="https://trezor.io/?srsltid=AfmBOop_XOf6UK3HDoKt_64wqPEiXvo8Jm8WoRXrJpE6nyYN5iCAMCt6">Trezor</a> like device. It has no connection to a internet and it’s done for safety reasons. It also has one big advantage, you can always take this device with you.</p><p>How it will work ?</p><p>The device is used for cryptographic key generation, storage and signing data with that keys (my article about Privateness <a href="https://ness-main-dev.medium.com/public-key-infrastructure-da78a9ab58ed?source=user_profile_page---------19-------------e0d5794ff45d----------------------">PKI</a> subsystem). In addition, this device can store other vulnerable data. The keypair after generation must be registered in Emercoin Wallet.</p><p>How it will connect ?</p><p>It will connect by <a href="https://www.raspberrypi.com/news/usb-gadget-mode-in-raspberry-pi-os-ssh-over-usb/">USB cable</a> or <a href="https://neonexxa.medium.com/how-to-serve-localhost-in-rapsbery-pi-thru-bluetooth-8e2e0d74da74">Bluetooth</a> interface and it will have a WEB interface accessible by a browser. Bluetooth can be used to connect this device to a smartphone.</p><p>What is Inside ?<br><a href="https://github.com/NESS-Network/PrivatenessTools">Privateness Tools</a> with a WEB interface.</p><h3>Personal node</h3><p>Also known as Private Node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*29_OdYoUQ3jXJqsV6aF7_A.png" /></figure><p>What it is ?</p><p>This is your personal device for different applications:</p><ol><li>Privateness Wallet — for payments</li><li>Emercoin Wallet — for storage</li><li>File sharing application.</li><li>Websites inside <a href="https://ipfs.tech/">IPFS</a> network.</li><li><a href="https://github.com/Alex014/PrivateBlog">Private Blog</a></li><li>Other 3rd party applications …</li></ol><p>This device will be located in your constant living place and it will be always on. For safety reasons this device will have no access from outside LAN. Only Blockchain (NESS, Emercoin) and torrent network (IPFS) will have access to internet. This device will be accessible to you from LAN by WEB interface.<br>Important addition:<br>This device will store only public part of a keypair.</p><p>How it will work ?</p><p>The device is used as a platform for personal applications with WEB interface (listed above).</p><p>How it will connect ?</p><p>It will connect to your LAN network by RJ45 cable or WIFI.</p><p>What is Inside ?</p><p>Apart from application a <a href="https://github.com/Alex014/Service-Controller">service controller </a>(connected to systemd) and <a href="https://github.com/Alex014/PrivateNode-WebFace">WEB face</a>.</p><h3>Service node</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*hlHU3N-Bc9Evb2EHu7BNgg.png" /></figure><p>What it is ?</p><p>It’s a node for different types of <a href="https://ness-main-dev.medium.com/microservices-d56eb8021112">microservices</a>.<br>I wrote a lot about service nodes in my previous articles …</p><p>How it will work ?</p><p>Basically it will sell different microservices to a clients.</p><p>How it will connect ?</p><p>It will connect to internet or DPN (Tor, I2p, Ygg, …) directly.</p><p>What is Inside ?</p><p><a href="https://github.com/NESS-Network/NessNode">Files Service</a> is under construction.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b550bc820e18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Privateness Manifest]]></title>
            <link>https://ness-main-dev.medium.com/privateness-manifest-aea1d377d36c?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/aea1d377d36c</guid>
            <category><![CDATA[manifest]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[privateness]]></category>
            <category><![CDATA[liberty]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 20:20:49 GMT</pubDate>
            <atom:updated>2026-04-22T20:21:42.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*6lsr_nRK07rkfTWqNzixjA.jpeg" /></figure><ol><li>Privateness is OPEN SOURCE INITIATIVE O.S.I.<br>The open source can have any license (MIT, GNU, etc) and the term “open source” also spreads to hardware.</li><li>Our aim is to build free and private internet for the people.</li><li>Privateness is leaderless.<br>- No central authority.<br>- You choose your role.<br>- You take the initiative.</li><li>Strength through unity.<br>- Every initiative member must know each other (at least nickname and skills).<br>- Every initiative member must share his skills and his skills must be a public info among initiative members.</li><li>Freedom through decentralization.<br>- Blockchain is the matrix of whole structure. Blockchain is more reliable than network of servers, it can serve infinite amount of users and it’s perfectly suits to the role of matrix or base-structure.<br>- Microservices: One service — one device. Services instead of servers. Services are more flexible than servers. You can build your own system based on services. You can use both your own services and out-source services.</li><li>You control your privacy and Publicity.<br>- You control your hardware.<br>- You control your software.<br>- You control your data.<br>- You control your communication.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aea1d377d36c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nodes]]></title>
            <link>https://ness-main-dev.medium.com/nodes-b1391ad5e607?source=rss-e0d5794ff45d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1391ad5e607</guid>
            <category><![CDATA[rpi4]]></category>
            <category><![CDATA[file-sharing]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[arm]]></category>
            <dc:creator><![CDATA[Aleksej Sokolov]]></dc:creator>
            <pubDate>Thu, 15 Jan 2026 00:24:20 GMT</pubDate>
            <atom:updated>2026-01-15T00:24:20.719Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hardware</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*VoV4p7UjKnUy9uOgi6wAbg.jpeg" /></figure><p>I have chosen ARM, the cheapest and most common architecture. The first version of the nodes are tested on <a href="https://www.raspberrypi.com/products/raspberry-pi-4-model-b/">RPI4</a> device, but the are many cheaper analogs …<br>I came to conclusion that it is easier to install everything on a separate small ARM device and access the infrastructure through WEB interface. This approach has many advantages in comparison with docker containers (you own the OS and that means you own the device). Also, small ARM device has low power consumption and can be turned on 24/7 (this is very ucesful when sharing IPFS data).</p><h3>Personal Node</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SxHx1uVsUDs1QkOV8Zru-w.png" /></figure><p><strong>Purpose</strong><br>The primary purpose of personal node is <strong>user key generation and storage</strong>. Secondary purpose is to operate different tools based on user keys and blockchain.</p><p><strong>Blockchain<br></strong>There are two blockchains:<br>1.Emercoin used for public key storage and for storage long-term data and for storage data which links to other data (magnet links, IPFS links, etc).<br>2.NESS blockchain for fast transactions and payments between users and service providers.</p><p><strong>Internal Services</strong><br>IPFS — torrent network for file sharing<br>Yggdrasil — DPN for communication (can be changed to TOR, I2P, Skywire, …)</p><p><strong>Entities<br></strong><a href="https://ness-main-dev.medium.com/entities-concept-809ec2815eb6">Article about entities</a>.<br>&lt;human&gt; — <a href="https://ness-main-dev.medium.com/human-and-user-1eb3def476bb">Article about &lt;human&gt;</a></p><pre>&lt;human name=&quot;&quot; tags=&quot;&quot;&gt;<br>  &lt;description&gt;&lt;/description&gt;<br>&lt;/human&gt;<br>&lt;!--<br>tags - coma,separated,keywords<br>description - optional<br>--&gt;</pre><p>&lt;share&gt; — Used for file sharing, stored in blockchain.</p><pre>&lt;share filename=&quot;&quot; mime=&quot;&quot; type=&quot;ipfs&quot; tags=&quot;&quot;&gt; &lt;description&gt;&lt;/description&gt;&lt;/share&gt;<br>&lt;!--<br>mime - file mime type<br>type - ipfs or magnet<br>tags - coma,separated,keywords<br>description - optional<br>--&gt;</pre><p>&lt;message&gt; — Used for communication between humans, sent through network, stored in internal database.</p><pre>&lt;message from=&quot;&quot; to=&quot;&quot; subject=&quot;&quot; reply=&quot;&quot; mime=&quot;&quot; unite=&quot;&quot; time=&quot;&quot; sig=&quot;&quot;&gt; <br>  &lt;body&gt;&lt;/body&gt;<br>&lt;/message&gt;<br>&lt;!--<br>mime - mime type of body (than base64 encoded if binary)<br>reply - reply to message (signature of that message)<br>unite - a part of some other massage, a file or some other data sent separately (signature of that message)<br>time - unixtime of message creation (UTC)<br>sig - signature of body<br>--&gt;</pre><p><strong>Tools<br></strong>Messages — application for sending messages with WEB interface<br>Share — application for sharing files with WEB interface</p><h3>Service Node</h3><p><strong>Services<br></strong>More detailed described <a href="https://ness-main-dev.medium.com/microservices-d56eb8021112">here</a>.</p><p><strong>Authentication<br></strong>Authentication will be based on tokens <a href="https://ness-main-dev.medium.com/token-authentication-complete-3ae633c9a75e">described here</a>.</p><h3>Clients</h3><p><strong>Console client<br></strong>The client will use <a href="https://ness-main-dev.medium.com/token-authentication-complete-3ae633c9a75e">token authentication</a> and <a href="https://ness-main-dev.medium.com/session-dadb05c02379">session algorithm</a> for key storage.</p><p><strong>WEB Client<br></strong>Web inteface will be build on a top of existing console client.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1391ad5e607" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>