🔑REMME
The REMME project works in the field of information security, Identity and Access Management. For this purpose, it is proposed to use the widely distributed X.509 certificates, which are independently released by network nodes (master codes), information about which is recorded in blockchain. The revoking of certificates is implemented by adding a predefined transaction to the blockchain of the owner of the certificate. This allows users of the REMME protocol to verify their certificates through the blockchain system, and the attacker will have to restrict the client's access to all the nodes of the blockchain to carry out the certificate substitution, which is technically difficult. In the traditional architecture of PKI (Public Key Infrastructure), there are CAs and other nodes that store information about the status of issued certificates. CA certifies the identity of the resource owners and issues certificates that are accepted by the users to authenticate the resource and establish a secure connection with the certificate holder. It is not possible to exclude certifying authorities as an element that certifies the identity of network nodes, but this approach is not applicable to end-user authentication. Services with certificates from CA register their users themselves and authentication takes place using the usual access attributes in the form of login and password. For ordinary users, storing a lot of logins and passwords is simply inconvenient and using REMME certificates would allow using the same certificate for authentication on a variety of resources, as CA certificate owners do to their users.
The REMME project is staging the ICO with the aim of attracting funds for the development of technology and brand. The project partners provide it with technical and legal support.
The project has reached the Hard Cap on the first day of Public Sale, which indicates possible investment from large players or funds in the project.
📈Milestones📉
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.
Q2, 2018
Private blockchains for integration with enterprise systems.
Open source integration libraries for websites and web applications.
Additional 2FA options such as Signal, Status, WeChat, Trezor.
20+ integrations.
Q3, 2018
- Public testing.
- Master nodes with Proof-of-Stake consensus.
REMME Core integration with Active Directory and SCADA systems.
Opening sales office in London.
50+ integrations.
Q4, 2018
- Public release.
- Consensus algorithm update (Proof-of-Authority).
- Building DApps for IoT on top of REMME.
- Opening sales office in New York.
- 100+ integrations.
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.
🗳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
🍴Token distribution:
50% - for sale
20% - partners and advisor
20% - team and founders
10% - reserve fund
Bountyhive username: infocoins
The REMME project works in the field of information security, Identity and Access Management. For this purpose, it is proposed to use the widely distributed X.509 certificates, which are independently released by network nodes (master codes), information about which is recorded in blockchain. The revoking of certificates is implemented by adding a predefined transaction to the blockchain of the owner of the certificate. This allows users of the REMME protocol to verify their certificates through the blockchain system, and the attacker will have to restrict the client's access to all the nodes of the blockchain to carry out the certificate substitution, which is technically difficult. In the traditional architecture of PKI (Public Key Infrastructure), there are CAs and other nodes that store information about the status of issued certificates. CA certifies the identity of the resource owners and issues certificates that are accepted by the users to authenticate the resource and establish a secure connection with the certificate holder. It is not possible to exclude certifying authorities as an element that certifies the identity of network nodes, but this approach is not applicable to end-user authentication. Services with certificates from CA register their users themselves and authentication takes place using the usual access attributes in the form of login and password. For ordinary users, storing a lot of logins and passwords is simply inconvenient and using REMME certificates would allow using the same certificate for authentication on a variety of resources, as CA certificate owners do to their users.
The REMME project is staging the ICO with the aim of attracting funds for the development of technology and brand. The project partners provide it with technical and legal support.
The project has reached the Hard Cap on the first day of Public Sale, which indicates possible investment from large players or funds in the project.
📈Milestones📉
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.
Q2, 2018
Private blockchains for integration with enterprise systems.
Open source integration libraries for websites and web applications.
Additional 2FA options such as Signal, Status, WeChat, Trezor.
20+ integrations.
Q3, 2018
- Public testing.
- Master nodes with Proof-of-Stake consensus.
REMME Core integration with Active Directory and SCADA systems.
Opening sales office in London.
50+ integrations.
Q4, 2018
- Public release.
- Consensus algorithm update (Proof-of-Authority).
- Building DApps for IoT on top of REMME.
- Opening sales office in New York.
- 100+ integrations.
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.
🗳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
🍴Token distribution:
50% - for sale
20% - partners and advisor
20% - team and founders
10% - reserve fund
Bountyhive username: infocoins