1 The client enters the desired username. 2 A pair of RSA keys is generated locally on the user's device: one is the private key, and the other is the public key. The private key must be kept secret and must never be shared with others or its contents revealed, while the public key is publicly available and can be shared with other parties. 3 The client is required to save the generated private key on their device. The public key is automatically uploaded to the registration server, which triggers the sending of a registration request. 4 The server generates a temporary code for end-to-end encrypted communication with the client. The temporary code consists of 500 randomly generated digits arranged in 10 series of 50 digits, each series being divided into 9 chunks. The temporary code formed is called a DCCL key. DCCL technology includes logarithmic functions and exponential functions as mutual inverse functions, with different bases, exponents and arguments derived from the corresponding parts of the DCCL key. 5 A DCCL key can be composed of a large number of randomly generated digits (up to 1500 or even more) arranged in as many series as needed (it can be a series of 1, 2, 5, 10 or even 50), while the number of chunks varies from 9 to 17. It all depends on how strong the encryption is supposed to be. The more digits, the more series and chunks, the stronger the protection. On the other hand, the response time increases, which greatly affects the time required to perform encryption and decryption. In some cases, such as online payments, it is unacceptable to wait too long for the transaction to be completed and a compromise solution must be found. The combination 500/10/50/9 has proven to be very successful. This is what it looks like when spoken in the language of mathematics. 6 Each of the 10 strings that make up the DCCL key is encrypted with the client's public key on the server side, notifying the client that the file containing the DCCL key is ready to be downloaded. The DCCL key is temporarily stored in the memory of the application that manages the registration process until the registration is complete and is not stored or logged anywhere else. 7 The client loads the encrypted DCCL key and decrypts it using the corresponding private key located on the client's device. The decrypted set of DCCL keys is temporarily stored in the browser's memory (and is not stored or logged anywhere else) and will be used to encrypt data that the client sends to the server. 8 The entered username is encrypted with the loaded DCCL key. The algorithm involves end-to-end encryption springing from a combination of multiple logarithmic functions, each containing a base and exponent derived from the corresponding part of the DCCL key. 9 A composite file containing the encrypted username, the hash code calculated from the original username, a timestamp, and DCCL-encoded variables associated with artificially generated "fake" logarithmic values is created on the client's device. This is called a data file. 10 A hash code is calculated for the given data file. The generated hash code represents a digital signature attached to the file and verifies the integrity of the file and the authenticity of the client who initiated the registration. 11 The digital signature is encrypted using the loaded DCCL key and inserted into the data file, which is then uploaded in its entirety to the server. 12 The server accepts the digitally signed data file and decrypts the digital signature and DCCL-encrypted variables using the inverse DCCL algorithm and the very same DCCL key that was used for encryption on the client side. 13 The digital signature is validated by recalculating the hash codes and checking whether they match. The availability of the requested username is also confirmed (or not confirmed), and the client is notified of the result. 14 If the digital signature is valid and the username is available, the registration is complete. 15 The application that manages the registration process creates a log file named after the hash code and writes the client's public key and the client's username to the file. Although this is public data, there is no reason not to store the file in a secure location, which would make it inaccessible to cyberattacks. This is called a registration file. 16 If the digital signature is not valid or the username is not available, the registration process must be repeated. 17 Finally, the application that manages the registration process will be closed and the temporary DCCL key will be deleted from the server.

Licensing ChatLiner and the associated products based on Digital Chip Card Locker ("DCCL") technology costs $1200 per year. You can pay $300 quarterly, $600 half-yearly, or $1200 annually.

$300.00 USD / quarterly $600.00 USD / half-yearly $1200.00 USD / annually

Permission is hereby granted, free of charge, to any licensee who obtains a copy of the programming code available at https://soundsofsoftware.com/login.js and associated documentation to use it without restriction, including, without limitation, the rights to use, copy, modify and/or merge portions of the code or the code in its entirety in accordance with the terms of the Licensing Agreement.

By using this software platform (the "Software", or "ChatLiner") owned by VIDYPS 79 d.o.o. (the "Licensor"), you acknowledge and agree that the License Agreement sets out the business relationship between you and the Licensor. Visit this page for more information.