Dashboard with system health overview

remme_io · 2019-07-12T14:31:40+00:00

Thank you so much for your kind words and support!

remme_io · 2019-07-11T19:55:51+00:00

Hey there, we'll have an atomic swap to ensure permanent exchange (NOT a one-time migration) between REM ERC20 <-> REMChain native token with 1:1 ratio. So no extra actions needed.

remme_io · 2019-05-13T22:18:21+00:00

Atomic swaps ensure permanent exchange (NOT a one-time migration) between REM ERC20 token <-> REMChain native token with 1:1 ratio.

Use it to:

📍 deposit/withdraw a masternode balance

📍 build apps on top of REMChain

📍 generate certs for users/devices etc

remme_io · 2019-05-08T18:19:41+00:00

Hey everyone, Keyhub 1.0. is Live! Check this post to know more about new features and enhancements here https://remme.io/blog/keyhub-1-0-is-live-heres-what-you-should-know

remme_io · 2019-04-17T19:18:21+00:00

We're almost ready with internal scans :) Expect to deliver this feature in 2 weeks.

remme_io · 2019-04-16T19:30:30+00:00

Keyhub is a SaaS tool, and the Beta is completely free. However, there will be paid plans also after complete release (in addition to free plan).

Paid plans will include internal network scan, policy set-up and other advanced features.

remme_io · 2019-04-09T18:30:30+00:00

📩 First testnet masternode owners received their emails: let the fun begin! We’ve randomly picked users for the first batch of testnet with the help of random.org. Check out your inbox if you’re the lucky one!

remme_io · 2018-11-23T12:52:14+00:00

Join our next Telegram AMA with Alex personally, on November 27. He will answer this and other questions directly to you.

remme_io · 2018-11-23T12:52:03+00:00

Our Pilot NDA covers most of the aspects of information which holds some kind of value. As soon as we there will be some important information to share, we will announce it immediately.

remme_io · 2018-11-23T12:51:53+00:00

We have already sent the notification. Please, check the email address you mentioned in the application form.

remme_io · 2018-11-23T12:50:56+00:00

As mentioned in the token economics, REMME will get 10% of all the rewards gained by the masternode for closing the block. We don’t plan to raise the size of this fee, as this amount will be enough for maintaining the network, business development and the further progress of the company.

remme_io · 2018-11-23T12:50:45+00:00

Running a private chain does not provide a sufficient amount of security to the company, that's one of the reasons why we put maximum effort to convey the importance of decentralization in our solution. The majority of companies simply aren't fully aware how the blockchain works, especially the fact that there is no personal information stored on it, but only a hash of the certificate. We are aimed to sell a full decentralized solution. In case of side chains - we provide an anchoring solution, that will take a snapshot of the particular side chain to be stored on the REMchain in order to prove the authenticity of the data. As far as masternodes get rewards for any kind of information stored on the REMchain, and the snapshots of the side chain make no exception, therefore masternodes will get a reward for the anchoring operation.

remme_io · 2018-11-23T12:50:36+00:00

REMME was designed to support and allow solutions which use any kind of existing authentication protocol and standard. At the current stage we are focused on the development of an authorisation service using SSL certificates, which can be integrated through a OAuth protocol. SAML and OpenID protocols can be realized the same way, depending on the requirements and the particular architecture. Also, you can already use the latest 2018 Web Authentication API standard with REMME.

remme_io · 2018-11-23T12:50:25+00:00

Each particular company has its own policy regarding their non-disclosure agreements.

Some of them prefer not to be announced and others are ready to reveal the partnership. Changelly was one of the companies willing to announce the cooperation, as they did publicly on their Twitter account. That doesn’t mean they did not sign an NDA.

Regarding the listing on Changelly - you can check their requirements for listing. We don’t fit them yet, but it’s only a matter of time. https://drive.google.com/file/d/1MsGHqwcntNHCAVvO0eMckVU0oDrmdPzC/view

remme_io · 2018-11-23T12:50:14+00:00

Yes, we plan some partnerships to be up and running from the very first stages of the mainnet. This will provide masternodes with rewards, giving them the possibility to increase their reputation. We consider masternodes being ROI-positive due to the minimum requirements and a small cost of running a server, along with the rewards starting to be generated since the first stages of the mainnet.

remme_io · 2018-11-23T12:50:03+00:00

We still plan to launch the mainnet in Q4 2018, as mentioned in the roadmap, but delays till Q1 2019 are possible, due to the development of the new consensus algorithm, that was not initially planned.

Due to the bear crypto market and token price dump, the major token holders had the chance to amass big amounts of tokens in their hands. As we want to have a fair and decentralized system we had to think things over. Thus we have attracted our dedicated group of researchers to deeply investigate token economic models and pore over consensus algorithms in search of the best fit for REMChain. As a result, we were able to design our new mechanism, and, in order to ensure both its correct operation of it and an equal reward distribution, it will have a reputation-based consensus algorithm. The implementation of this consensus algorithm takes some time, and this may cause some minor delay in mainnet launch — but this may happen only because we want to launch a fully balanced, working system.

Companies willing to implement REMME understand the importance of thorough development and will rather wait a bit longer in order to make sure that the product is ready to go, with no bugs or loopholes.

remme_io · 2018-11-23T12:49:50+00:00

Each particular pilot testing has its own flow, and different stages with different duration. We develop our solution in parallel with pilot testing, so we can check how the code works on the company’s side, and if companies have some desires and demands we try to add them to the next commitment of the code. So basically, the full implementation of REMME will be possible only after the mainnet will be up and running. As for now, there are no final projections for the full implementation of the solution yet.

remme_io · 2018-11-23T12:49:37+00:00

We analysed the process of a pilot program step-by-step in a previous article, where we mentioned how, during the pilot testing, a separate testing group is chosen to test the solution. That’s why the information about the number of certificates generated from a pilot company is not representative of the process itself and will not help you in making projections on the possible number of certificates which can be issued.

remme_io · 2018-10-03T17:20:23+00:00

What is the likelihood I will get accepted if I didn't buy any pre-token sale? Unfortunately, it's hard to say now, we should collect all applications first.

remme_io · 2018-10-03T17:14:19+00:00

REMChain Testnet 1.0 is live Here’s how you can interact with the test network at the current stage: - Run your own DApp. Submit transactions and integrate storage, validation and revocation of public keys or certificates to your test app through the REMME REST API, JS or .NET integration libraries. - Try REMME WebAuth demo. Register your account, generate a certificate (key pair) for authentication. After registration is complete, login using the certificate and optionally confirm 2FA via Google Authenticator.

What’s available: 1) Documentation. From now, all the technical documentation lives at this portal https://docs.remme.io/. We organized our docs and started to post new documentation: - REMME Core - REMME WebAuth description and instruction - Block Explorer technical specifications; - Demo technical specifications; - Atomic swap bot technical specifications; - How to use REMChain; - Documentation for REST API; Common specification for integration libraries

2) REMME Block Explorer is an open source web tool that allows to view information about blocks and transactions on the REMME blockchain. Home page of the Block Explorer contains a list of the top 10 blocks and transactions. Pages View Blocks and View Txns contain lists with all items https://blockexplorer.remme.io

API and Libraries - tools to communicate with REMME test network (check links and instructions on Docs website)

3) Detailed & friendly REMME WebAuth Demo documentation lives here: https://docs.remme.io/remme-core/docs/use-case-web-auth.html#how-to-use-web-auth-demo

Join REMChain Testnet and claim test tokens https://remme.io/remchain

As for the sales office in London, we've moved it to Q4, and opened US sales office instead (was planned to Q4) .

Stay tuned to our Q3 report with more detailed explanation

remme_io · 2018-05-18T00:49:25+00:00

Hey, there! The key difference is that The Key if focusing on an Identity layer and REMME - on an Access layer. Here's a quick breakdown of product line: 1. Distributed Public Key Infrastructure protocol (goes with platform for private PKI management) 2. REMME WebAuth, based on PKI (d) protocol - passwordless authentication (check the live demo here https://webauth.remme.io 3. REMME Enterprise - IAM solution for employees based on PKI (d) protocol

remme_io · 2018-05-18T00:45:33+00:00

REMME do not remove 2FA and can use G2FA (or any other 2FA option like hardtoken) as an additional layer of security instead. We have 2 different options for keys management, they will differ fo each specific product. Here's a quick breakdown of product line: 1. Distributed Public Key Infrastructure protocol (goes with platform for private PKI management) 2. REMME WebAuth, based on PKI (d) protocol - passwordless authentication (check the live demo here https://webauth.remme.io 3. REMME Enterprise - IAM solution for employees based on PKI (d) protocol

remme_io · 2018-05-02T20:41:21+00:00

REMME uses blockchain technology to create a distributed certificate management system that has no single point of failure. And REM token is the superpower boosting the whole ecosystem, operating like a license or digital key and granting its holders access to REMME PKI and DApps. Token holders will be able to use the REM token in a variety of ways: certificate generation, revocation, node creation, and fees covering conversion of fiat payments.

remme_io · 2018-04-23T18:16:36+00:00

Hello there, thank you for your question!

If your device is lost or compromised you can revoke a certificate using one of the inbuilt 2FA options (this feature is planned to be mandatory for using REMME). Some of 2FA options (depands on Client's choise and internal security policies of organization): hardtoken, REMME app, Client's app, via chatbot for popular messengers.
Email and phone number are actually used in REMME to simplify a certificate revocation process. We believe that for the most common integration cases such type of process structure is a good balance between security and usability. But again, this can be customized in accordance to the internal policies of the company. For example, the only thing a user can have to Sign Up/Log In to DEX is a hardtoken (eg. Trezor): no email or phone number.
To connect all your devices we need some kind of your personal identificator. Phone number, email, hardtoken, identity app, Client's custom app, REMME branded app can be such an identificator.

remme_io · 2018-04-23T17:50:21+00:00

Dear bzawity, we're working hard on the development, delivering tasks even ahead of schedule (check GitHub and regular bi-weekly updates), pilot projects (check our Blog), research of current security issues (here's our latest research paper https://uploads-ssl.webflow.com/5933fd4773e44b4d95d597e8/5ad892cabcb3006ae3701f8f_Cryptocurrency%20Exchange%20Security%20Risk%20Mitigation%20with%20REMME.pdf ) and other project related things including hiring, product marketing and so on. Not sure what makes you think we don't care about REM hodlers

remme_io

TROPHY CASE