HOW DOES IT WORK?
No centralized company servers!
- All data exchange is based on devices that allocate their disk space to the Artery Node.
- They form a decentralized pool in the form of the Artery Storage product.
- Messages and their contents are not handled by the company's centralized servers, but by a network of thousands of connected devices from around the world.
What's cool (about)
Translates on the fly
WHY DO WE NEED IT?
Internet starts with security!
Since Artery Network only deals with decentralized solutions, the DEM product is purely a reputational development.
There has been a lot of talk about decentralized data exchange in messengers, but no one has brought it to a popular end product before!
We decided to bring this to a head, especially with the network we created of several thousand devices allocating their disk space and Internet connection to their respective decentralized pools, forming the Artery Storage and Artery VPN products.
Wallet for storing, sending and delegating ARTR - the basic Artery Blockchain coin.
Decentralized cloud storage.
The section in which devices allocate their memory and Internet connection, thereby providing resources for the Artery VPN and Artery Storage products. Yes, according to our concept, the same user can be both the user of the products and the one who provides the resources for those products and is paid for doing so. This is the essence of decentralization.
A section where you can see your invited users, for whom you received rewards, if they paid the rate or delegated ARTR coins. Classic MLM, which for full transparency has been placed in a blockchain to avoid the accusation of signs of a pyramid. In our case the payout occurs when paying for specific products as affiliate rewards and from a limited number of tiers (10).
Events for the project's endorsers
The Central Bank of Russia added us to its blacklist with signs of a financial pyramid, and the Russian media proclaimed us to be the largest cryptocurrency financial pyramid in Russia, which of course is a complete lie. Roskomnadzor has blocked more than 35 of our sites. We would spend time proving that this is not true, but even bitcoin.org is blocked in RF. Until there is healthy market regulation, all crypto-projects in RF will be pyramids, time has proven.
Along with DEM, we sent a new Artery Wallet app to the AppStore, from which we removed the Team and Status sections, since our first Artery Network app was removed from the AppStore for being an MLM app (against Apple policy). Nevertheless, we added a free VPN to the Artery Wallet so that our Russian users can easily open any of our blocked sites.
With our resources today, we will only go further despite the challenges of the old formations, but we don't want to contradict the established. We just want to give security and a new understanding of the Internet and making money in it. And whether it's much or little is for you to judge!
HOW TO START
If you already have a wallet in Artery Blockchain
HOW IS THE DATA EXCHANGED?
Join the Artery community now and accelerate the progress of society!
All information on this site is provided from open and accessible sources. The company only promotes the project and is not a beneficiary of any product in the Artery ecosystem, including DEM. Many of the developments implemented today were made or suggested by community members. Anyone can take the initiative within the Artery Network ecosystem by suggesting or adding something for consideration by developers of existing applications or implement their own. Everyone is equal before blockchain. This is the strength of the DAO we are creating. At every stage of releasing something new for the Artery infrastructure, developers increasingly increase the openness and universality of the ecosystem for all, lowering the entry threshold.
Sincerely, your Artery.
FAQ. Messaging in DEMTo exchange messages, the DeM application must first establish a connection with the Artery Storage nodes, since all data exchange goes through them. To do this, initially in the application code is written several ip addresses of control nodes (they are described in the description of Artery Storage) and also a centralized API company address, from which the application can get such a list (if the address is not available, the embedded addresses are used).
After launching the application and getting the addresses of the control node, a request is sent to that node to get the addresses of the control nodes responsible for servicing a particular account (which the user specified when he logged in). After installing such nodes, further exchange of service information is carried out with them (service information includes - the list of nodes storing user correspondence, list of user contacts (in encrypted form), space limits for data storage, blockchain node addresses, information about blockchain accounts by their address and nickname, application settings).
This is necessary to ensure that the application works.
Once the address search is finished ("initialization phase"), the application goes "online", i.e. directly communicates with the Artery Storage nodes, namely: first it updates the timestamp with information about the last online presence of the application, and secondly it contacts the nodes storing the correspondence and downloads new messages into the local (on the phone) storage.
The application also establishes a persistent connection to one of the nodes storing the user's correspondence and reacts to the recording of new messages (downloads them and adds to the local storage).
When exchanging messages, the application sends requests to the nodes allocated for the storage of correspondence (received during the initialization phase).
There are 2 types of messages: outgoing and incoming.
Inbox - when someone records a message for a user, and their app downloads those messages and saves them to local storage.
Outgoing - the application gets the user's (message recipient's) public key from the blockchain, encrypts the message with it, and writes it to the public section of the message recipient. Also, a copy of the message encrypted with the sender's public key is written to the sender's public section.
All operations are signed with the user's key and checked for authenticity (immutability and belonging to a particular user).
When sending a file, it is first split into blocks, each of which is encrypted, then uploaded to different Artery Storage nodes, and then the hashes of these blocks are attached to the block storing the user's message. The list of blocks attached to the message is stored in an open form, it will not allow you to restore the data, but allows you to delete the information from the repository completely when the limit for recording is reached (if the deletion of old messages is enabled).
List of blocks attached to the message. Some of the non-critical for messenger messaging functions have been implemented (and new ones will be implemented) centrally. If the company's servers are unavailable, such functions will not work. Namely:
1. The "what the user does" function (meaning prints a message, selects a photo, etc.) - this uses centralized company servers, through which the corresponding events are passed between the active applications.
2. Search by partial nickname match (due to the fact that such a search is not possible in the blockchain).
3. Sending PUSH notifications (this requires tokens and services that are only available to companies) - to do this, the company's server receives information about who sent the message and to whom (the device PUSH token is associated with the recipient's address, this information is only stored by the company and is not shared with third parties).
4. New implementation of the "last time online" function on a centralized basis, to improve display accuracy and reduce the load on control nodes (т.к. данная (since this function is not critical for messaging).
User data is protected using xChaCha20 encryption and asymmetric encryption using the secp256k1 elliptic curve.
Ciphering is used to protect user data. Information in the block is encrypted with a one-time key for xChaChat20 using random nonce and salt (random data), then the key itself, salt and nonce are encrypted by asymmetric algorithm and all this information is stored in the block. Cryptographically secure (CPRNG) pseudorandom number generator provided by the operating system (iOS, Android) is used to create the key, nonce and salt (поверьте правильное ли слово указали).
Each message block stores information about the sender, the recipient, the message itself and information about the attachment. (hashes of data blocks included in the message, if it occupies more than 1mb).
All requests from an app are signed separately with the app's private key, so that nodes can verify that the app is trusted. If third-party developers want to release their own app, they can get the key for it by contacting the voting board. This is to protect users from SPAM.