What is REMME?
REMME is a distributed authentication, designed to replace passwords with digital certificates. 65% of confirmed data breaches involve weak, default or stolen passwords and cybercrime costs the global economy around $400 billion annually. REMME's next-gen Access Management solution eliminates the risk of user credentials being leaked and does away with weak means of protection.
These are the two core components of the solution:
1. REMME PKI (d) protocol: this uses a custom blockchain with bitcoin anchoring. Nodes are employed to confirm the stability of the system. The open source REMME Protocol enables anyone to build their own DApps with the aid of REMME SDK.
2. REMME DApps: REMME WebAuth, REMME Enterprise and REMME for IoT are a series of DApps that will be developed during the first stage of the project. REMME mail and REMME sign will also be introduced further down the line.
Advantages for service providers:
1. REMME can be described as a next-gen data protection solution because it removes friction and enhances the user experience. All of the security aspects that REMME tackles, it does whilst providing high value: - It frees businesses from a reliance on centralized storage and virtually eliminates the risk of user credentials being leaked. - It also does away with weak means of protection: REMME isn’t simply another password-based system – it’s a solution which eliminates the need for passwords altogether. - In 80% of cases, REMME actually makes passwords and PINs obsolete.
2. It minimizes the single biggest point of failure in organizations – humans, who are susceptible to things such as phishing and social engineering. With no password to acquire, there’s a limit to what cyber criminals can steal. Advantages for end-users: When building REMME, one of our key considerations was that it must be simple for end users to log in. For any technology to achieve widespread adoption, it needs to have a user-friendly interface, and the concept needs to be understandable even to less technically-minded individuals. We believe that REMME attains a balance between security and convenience.
We certainly have no desire to compromise on network security in our quest to create a clean interface. Compared to other access management solutions, we see REMME holding four key advantages: Other exciting info to share about the project: At the start of 2016, we introduced pilot projects with five companies from different sectors, ranging from a hardware manufacturer to an online healthcare portal.
Then, on October 17th, 2017, we opened applications to our 2018 Pilot Program, and have already had more than 50 great applicants contact us, which is really exciting. We're especially proud to have signed the memorandum on pilot project implementation with Ukraine’s state-owned company Ukrinmash. Information security is a critical matter for this organization more than most, and tightly restricting access to its data is paramount.
It’s a matter of both corporate as well as state secrets protection. It would be no exaggeration to say that the security of Ukrainian sovereignty may depend on the company’s internal data remaining impervious to external threats. Another pilot project memorandum, one of a very different nature, was signed recently with the New-York based Depositphotos, a creative content marketplace that allows users to buy and sell high-quality stock photos, vector images, and videos. Then there’s Gladius, a blockchain startup that builds product for DDoS protection. We’re reviewing options to integrate REMME PKI (d) with their solution to build a fully decentralized product that can successfully compete with Cloudflare. Other partnerships will be announced soon, as we are currently finalizing our agreements.
ICO Dates - Pre-sale is over (finished on December 25th) -
Start date: February 13, 20:00 UTC End date: March 13, 20:00 UTC Cost per token along with bonus structure during ICO - Basic price per 1 REM - $0.04 - Bonus 10%: days 1-3 - Bonus 5% - days 4-7 - Minimal contribution - 0,01 ETH. - Hard cap: $20M (including pre-sale amount)
Telegram and other channel links Twitter: https://twitter.com/remme_io
Team member names, social media links:
Alex Momot (https://www.linkedin.com/in/alex-momot-93596b32/) Founder and CEO.
Kate Pospelova (https://www.linkedin.com/in/kate-pospelova-6153a536/) - CMO and co-founder.
Roman Kravchenko (https://www.linkedin.com/in/romankrav4/) — CTO
Jan Keil (https://www.linkedin.com/in/jan-keil-2011a61/) — CBDO
Oleksii Baranovskyi, PhD (https://www.linkedin.com/in/oleksiibaranovskyi/) - Chief Cybersecurity Scientis
Eugene Babichenko (https://www.linkedin.com/in/eugenebabichenko/) DApp Architect
Taras Emelyanenko (https://www.linkedin.com/in/taras-emelyanenko-97055047/) System Architect
Anatolii Padenko (https://www.linkedin.com/in/anatolii-padenko-60322b83/) Smart Contract Engineer
Iryna Slobodianiuk (https://www.linkedin.com/in/iryna-slobodianiuk-75542689/) Legal
Yevhenii Turanov - Legal
Zoya Danilina (https://www.linkedin.com/in/zoya-danilina-b40bbb85/) Social Media Specialist
Sergii Androsiuk - Community Support
Nick Bilogorskiy (https://www.linkedin.com/in/bilogorskiy/) Security Advisor
Prof. Roman Oliynykov (https://www.linkedin.com/in/oliynykov/) - Cryptography Advisor
Andrey Zamovskiy Advisor, Ethereum Guru
Vitaliy Bulychov (https://www.linkedin.com/in/vitaliy-bulychov-839aa543/)
Stepan Gershuni (https://www.linkedin.com/in/sgershuni/) Technical Advisor
Gordon Einstein (https://www.linkedin.com/in/gordoneinstein/) Legal Advisor
Artem Afian (https://www.linkedin.com/in/afian/) Legal Advisor
Nestor Dubnevych (https://www.linkedin.com/in/nestor-dubnevych/) - Legal Advisor
- Compact and highly skilled team with a lot of experience in startups, fintech and payment systems.
- Funds allocation seems great and well thought out in general
- Roadmap seems well thought out for the team and it’s size. Team is also planning to expand the team size by 60%.
- The logos shown on the website eg. Visa and Mastercard could be interpreted as partners, but can’t be verified. Possibility of exaggeration
- Information is not presented clearly either on the website or white paper. Most of the contributor-relevant information is scattered
- Low hard cap considering the expenditures associated with required licenses and institutional statuses