The primary means of accessing various local and network resources today is via password, a method that has proven itself as a way of identifying and securing users and resources. However, it has one serious drawback: in the event of a password being stolen, the attacker gains access to all of the account-holder’s data. Moreover, because users often deploy the same password for multiple services, the situation is exacerbated, while weak passwords can be a subject to vocabulary attack. Password databases from a variety of resources periodically fall into open access, exposing hundreds of millions of passwords to hackers.
Even where the affected user has the ability to change their password, their account is still vulnerable, since the user's mailboxes are usually protected by a password that is often the same as that used on other resources. Thus, passwords cannot serve as a sufficient instrument for protecting user data and guaranteeing the security of the user session.
REMME solves the following issues:
This allows complete and transparent control and tracking of all issued certificates, no possibility for issuing "hidden" certificates, and eliminated attempts to intercept and redirect connections.
Various parties (including Google) have tried to solve those issues, but without success. Blockchain systems ensure the immutability of data stored within them, providing an effective and practical solution.
- Powered by Blockchain. A distributed database is safe from hack attacks. - No certificate center. - Blockchains and Sidechains. The REMME system can be used with a number of different blockchains and sidechains. It is possible to choose the most convenient combination for company. - Control the identity. - Smooth User Experience. Users can forget about filling out forms, or long sophisticated passwords. From now on, authentication with just one click is as easy, as it is secure. - Instant registration. User personal information will be put on blockchain instantly. - 2FA Based on the app a user already has. REMME uses bots developed for the most popular messenger apps. Instead of traditional text messages and OTP codes, users get an authentication token sent via the messenger app of their choice. - Multiple accounts. One user can register with an unlimited number of accounts, that is have numerous SSL-certificates. Anytime during login, they can choose which account to use.
Idea growth and concept validation
REMME Core public alpha
Releasing DApps on top of REMME Core
Public beta release
Attention. There is a risk that unverified members are not actually members of the team
$19 580 000
$20 048 245
$52 600 000
This offer is based on information provided solely by the offeror and other publicly available information. The token sale or exchange event is entirely unrelated to ICOholder and ICOholder has no involvement in it (including any technical support or promotion). Token sales listed from persons that ICOholder has no relationship with are shown only to help customers keep track of the activity taking place within the overall token sector. This information is not intended to amount to advice on which you should rely. You must obtain professional or specialist advice or carry out your own due diligence before taking, or refraining from, any action on the basis of the content on our site. Any terms and conditions entered into by contributors in respect of the acquisition of Tokens are between them and the issuer of the Token and ICOholder is not the seller of such Tokens. ICOholder has no legal responsibility for any representations made by third parties in respect of any Token sale and any claim for breach of contract must also be made directly against the Token issuing entity listed herein.
If you have any concerns about the nature, propriety or legality of this token sale or the persons involved in it please contact [email protected] with detailed information about your concerns.