Securing access of digital identities

REMME is the Distributed Public Key Infrastructure protocol with a set of DApps for Access Management. 65% of confirmed data breaches involve weak, default, or stolen passwords and cybercrime costs the global economy around $400 billion annually. REMME is building the distributed Public Key Infrastructure (PKI) solution, which prevents phishing, server and password breach, and utilize SSL/TLS protocol to protect the entire channel from attack. The REM token powers all operations within the ecosystem including certificate generation, revocation, and rewarding of nodes which safeguard the network.

Business services Internet Platform Software

by expert rating and reviews

Token REM
Platform Ethereum
Raised $20,000,000
Country British Virgin Islands
ICO Start Date 13 Feb 2018
ICO End Date 22 Feb 2018


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:

  1. Trusting the centralized certification authority (CA)
  2. CA keys being compromised
  3. Fake certificate issuance
  4. Issuance of "hidden" certificates, trying to intercept and redirect connections

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.


Alex Momot member of REMME ICO
Alex Momot
Founder & CEO
Kate Pospelova member of REMME ICO
Kate Pospelova
CMO & Co-founder
Roman Kravchenko member of REMME ICO
Roman Kravchenko
Jan Keil member of REMME ICO
Jan Keil
Eugene Babichenko member of REMME ICO
Eugene Babichenko
DApp Architect
Taras Emelyanenko member of REMME ICO
Taras Emelyanenko
System Architect
Anatolii Padenko member of REMME ICO
Anatolii Padenko
Smart Contract Engineer
Iryna Slobodianiuk member of REMME ICO
Iryna Slobodianiuk
Zoya Danilina member of REMME ICO
Zoya Danilina
Social Media Specialist
Nick Bilogorskiy member of REMME ICO
Nick Bilogorskiy
Security Advisor
Gordon Einstein member of REMME ICO
Gordon Einstein
Legal Advisor
Vitaliy Bulychov member of REMME ICO
Vitaliy Bulychov
Investments Advisor
Roman Oliynykov member of REMME ICO
Roman Oliynykov
Cryptography Advisor
Stepan Gershuni member of REMME ICO
Stepan Gershuni
Technical Advisor
Artem Afian member of REMME ICO
Artem Afian
Legal Advisor
Nestor Dubnevych member of REMME ICO
Nestor Dubnevych
Legal Advisor


  • 1

    Q4, 2015

    - Idea growth and concept validation

  • 2


    - REMME Core MVP V 0.1 with 2FA on Telegram based on Emercoin blockchain.
    - 5 pilot projects.

  • 3

    Q2 2017

    - Blockchain Intensive Hackathon by Microsoft – winner.
    - Memorandum of Understanding with Ukrinmash.
    - Strategic partnership with Infopulse.

  • 4

    Q3 2017

    - REMME Core MVP V 0.2 - CRL infrastructure on Bitcoin blockchain, certificate generation in browser.
    - White paper 1.0 release.
    - REMME’s 2018 Pilot program announced.

  • 5

    Q4 2017

    - December 4, 2017: Pre-sale for the REMME community whitelist.
    - White paper 2.0 release.
    - Public GitHub release.

  • 6

    Q1, 2018

    - REMME Core public alpha.
    - Product security audits and pen-tests.
    - Extending team of software engineers.
    - REMME’s 2018 Pilot program launch.
    - Public sale phase.
    - Legal structure.

  • 7

    Q2, 2018

    - At this stage private blockchains for integration with enterprise systems will be implemented. The planned functionality is:
    a) Blockchain-based certificate data storage.
    b) Integration for different client systems.
    c) Bitcoin anchoring for higher auditability.
    - Open source integration libraries for websites and web applications.
    - Additional 2FA options such as Signal, Status, WeChat, Trezor.
    - Product security audits and pen-tests.
    - 20+ integrations.

  • 8

    Q3, 2018

    - Public testing. At this stage a user can nominate themselves to become a holder of a master node, which will be processed by the existing master nodes and, if the user is eligible by all criteria, they will be included in the list of approved nodes. At this stage, thanks to further development of PoA, master nodes from the list of approved nodes will be added periodically by REMME maintainers. Prices will be updated in a centralized manner (see “Pricing policy”) from a REMME maintainer’s trusted node. New prices will take their place after 10 confirmation of the block they were introduced in. By this stage, the system will also have cross-blockchain token transfers so that everyone who purchased REMME
    tokens will be able to take full advantage of the service.
    - REMME Core integration with Active Directory and SCADA systems.
    - Extending of decentralized ecosystem of nodes.
    - Product security audits and pen-tests.
    - Opening sales office in London: hiring dedicated sales responsible for EU, extending existing marketing team and hiring support team.
    - 50+ integrations.

  • 9

    Q4, 2018

    - At this stage the release of the public system is planned, so the process of master node management on the public service will be fully automatic without involving REMME maintainers.
    - The consensus algorithm update is also planned. Master nodes are ranked according to their performance and stability of operation (or uptime) every n seconds. When a new block appears (every m seconds), the pseudorandom algorithm selects one of the nodes in proportion to its rank (the higher the rank the higher the possibility for the node to be selected), and the system waits for the block signed by this node to appear. If the selected node does not produce a new block for more than k seconds, the algorithm automatically proceeds to the next node. In this way, the system ensures maximum adherence to the specified parameters and motivates the master nodes to remain in the system.
    - Building DApps for IoT on top of REMME Core (with a focus on automotive and smart cities).
    - Product security audits and pen-tests.
    - Opening sales office in New York: hiring dedicated sales team responsible for US, extending existing marketing team and hiring support team.
    - 100+ integrations.

  • 10

    Q1, 2019

    - Opening sales offices in Tokyo and Singapore: hiring dedicated sales teams responsible for Asian market, extending existing marketing team and hiring support team for the region.
    - Holding special cybersecurity events once every 3 months.
    - Special cybersecurity lessons and classes in Ukraine for training specialists to contribute to the REMME ecosystem.


Token Sale Info
Token REM
Token Type ERC-20
Platform Ethereum
Tokens for Sale 500000000
Investment info
Distributed in ICO 50%
Soft cap 480,000 USD (pre-sale)
Hard cap 20,000,000 USD (including $3M pre-sale)
Raised $20,000,000

Others in "ENDED ICO"