Finally, I released a console tools for working with files service. In a server (service node) the file are stored in generated shadownames. The shadownames are generated on client, and they look like this: zxce.12 .Directories and real filenames are stored on client in separate config files (~/.privateness/keys/files.json and directories.json)…

Thinking about Proof Of Time conception a came to a conclusion, that we need a simplified solution. That means, less storage, less resources and less code. In the first place I combined token and payment into one solid token. The token is generated and shown to user, it is stored…

Working with file service I realized, that we need not only alternative ID but also user shadowname. URL: http://[IP]/files/pub/AlternativeID-Shadowname-FileHash AlternativeID = sign(user_private_key, “node.url-node.nonce-username-user.nonce-alternative-123”) Used to verify the user FileHash = MD5(filename) Filehash is needed to determine which file to download not showing real file name for security reasons

A little changes on registration process … URL join/username-or-userhash/auth-id returns {address: privateness-address-to-send-coin-hours} or ERROR URL joined/username-or-userhash/auth-id returns {joined: true-or-false} or ERROR The user is “joined” (registered) if there are at least one transaction on user’s address “privateness-address-to-send-coin-hours”. Userhash is also more secure than username.

Problem All coins in hands of small amount of crooks Most amount of BITCOINS and other CRYPTO are in the hands of small amount of crooks and that means they can manipulate course and accumulate even more CRYPTO. KYC It’s not an easy task to buy some bitcoins or other CRYPTO if you…

The next step is a file service. This type of service can be used both for “private user storage” and CDN type services … This service requires 3 additional features: 1. Open user slots (how many users the node can hold and how many open places (slots) we have). 2. User quota…

The first version of microservices platform based on blockchain is ready. It uses Emercoin blockchain Privateness coin-hours Counter-Random payment Ness node — the main platform Ness node tester — the tools for testing and generating keys It has only one service — random number generator (PRNG) Now it need’s to be tested … Telegram group: PrivateNess Network | Noderunners

I was thinking about my previous conception https://ness-main-dev.medium.com/random-payment-e438874f458b and realized, that it does not suit our needs. 1. It’s unfair (the user can be payed twice a month) 2. It’s not understandable to user. So I invented another conception CRP — counter random payment Each user has a counter. The Counter…

The problem: Skycoin/Privateness network at every transaction takes 10% fee of all Coin-Hours on input address. This makes small transactions impossible. The solution: Make a random payment every hour. The user will pay for a whole month in 1/720 probability in every hour (month has 720 hours). The user is valid if he has > 720 Coin-Hours on his account (user-address). Emercoin has a similar technology https://emercoin.com/en/news/randpay