{
  "op": [
    "transfer",
    {
      "to": "mamont",
      "from": "howo",
      "memo": "Hi, I have been working for the past two years as a core developer on hive. I worked on a lot of things last year some which went live in hard fork 25 already or will go live soon with hard fork 26. To name a few, RC delegations, recurrent transfers or communities V2. I would love to continue working on hive for a third year on the next hard fork, communities and everything else. I am looking for support on my renewed proposal as the current one will expire soon. Could you review it and maybe vote on it if it's worth your support ? https://peakd.com/me/proposals/214 Thanks a lot !",
      "amount": "0.001 HIVE"
    }
  ],
  "block": 63358442,
  "trx_id": "69457897caf646497f23de63d1fff21c2a2ee5c3",
  "op_in_trx": 0,
  "timestamp": "2022-04-09T09:54:51",
  "virtual_op": false,
  "trx_in_block": 18
}

{
  "op": [
    "curation_reward",
    {
      "author": "daan",
      "reward": "1.975351 VESTS",
      "curator": "mamont",
      "permlink": "instantly-exchange-crypto-at-the-best-market-rates-with-swapy",
      "payout_must_be_claimed": true
    }
  ],
  "block": 37591232,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 70,
  "timestamp": "2019-10-25T11:23:00",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mamont",
      "author": "daan",
      "weight": 339,
      "rshares": 4057809963,
      "permlink": "instantly-exchange-crypto-at-the-best-market-rates-with-swapy",
      "pending_payout": "7.588 HBD",
      "total_vote_weight": 4503625
    }
  ],
  "block": 37517352,
  "trx_id": "b710deeac38d7e04f54ef9a12bc879c4e1bab143",
  "op_in_trx": 1,
  "timestamp": "2019-10-22T21:41:48",
  "virtual_op": true,
  "trx_in_block": 5
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "daan",
      "weight": 10000,
      "permlink": "instantly-exchange-crypto-at-the-best-market-rates-with-swapy"
    }
  ],
  "block": 37517352,
  "trx_id": "b710deeac38d7e04f54ef9a12bc879c4e1bab143",
  "op_in_trx": 0,
  "timestamp": "2019-10-22T21:41:48",
  "virtual_op": false,
  "trx_in_block": 5
}

{
  "op": [
    "comment",
    {
      "body": "Congratulations @mamont! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@mamont/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@mamont) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=mamont)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "title": "",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-mamont-20190711t010841000z",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "mamont",
      "parent_permlink": "remme-technical-white-paper"
    }
  ],
  "block": 34554919,
  "trx_id": "60c52a1ae74297a879db98da077ddb9cbec7de88",
  "op_in_trx": 0,
  "timestamp": "2019-07-11T01:08:45",
  "virtual_op": false,
  "trx_in_block": 5
}

{
  "op": [
    "comment",
    {
      "body": "Congratulations @mamont! You have received a personal award!\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/@mamont/birthday2.png)](http://steemitboard.com/@mamont)  2 Years on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n[SteemitBoard World Cup Contest - Croatia vs England](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-croatia-vs-england)\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "title": "",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-mamont-20180711t012739000z",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "mamont",
      "parent_permlink": "remme-technical-white-paper"
    }
  ],
  "block": 24068823,
  "trx_id": "9d407b616932518e8dad86b6e031e205ddaa4ccc",
  "op_in_trx": 0,
  "timestamp": "2018-07-11T01:27:42",
  "virtual_op": false,
  "trx_in_block": 2
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "freedomcoin",
      "weight": 10000,
      "permlink": "bitcointalks-merit-system-showing-some-love-to-my-recent-favorite-altcoins"
    }
  ],
  "block": 23173031,
  "trx_id": "c64fcc7a277b59995639a98689cef80c59ce4d35",
  "op_in_trx": 0,
  "timestamp": "2018-06-09T14:03:27",
  "virtual_op": false,
  "trx_in_block": 62
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "jamshedalam",
      "weight": 10000,
      "permlink": "kjr3qtqo"
    }
  ],
  "block": 19525503,
  "trx_id": "875764a5059582a126036c19f773d533203d2293",
  "op_in_trx": 0,
  "timestamp": "2018-02-02T19:20:27",
  "virtual_op": false,
  "trx_in_block": 37
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mamont",
      "author": "flodner",
      "weight": 34206,
      "rshares": 4107809962,
      "permlink": "aleks-momot-ceo-remme-pro-ico",
      "pending_payout": "0.070 HBD",
      "total_vote_weight": 77626
    }
  ],
  "block": 18812293,
  "trx_id": "543a06580edb8d28f0b498e0d4016fb0f3e3d841",
  "op_in_trx": 1,
  "timestamp": "2018-01-09T00:34:09",
  "virtual_op": true,
  "trx_in_block": 42
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "flodner",
      "weight": 10000,
      "permlink": "aleks-momot-ceo-remme-pro-ico"
    }
  ],
  "block": 18812293,
  "trx_id": "543a06580edb8d28f0b498e0d4016fb0f3e3d841",
  "op_in_trx": 0,
  "timestamp": "2018-01-09T00:34:09",
  "virtual_op": false,
  "trx_in_block": 42
}

{
  "op": [
    "vote",
    {
      "voter": "gsm",
      "author": "mamont",
      "weight": 10000,
      "permlink": "re-bittrex-richie-a-little-history-of-bittrex-com-how-it-all-started-20160713t192158667z"
    }
  ],
  "block": 17520636,
  "trx_id": "551b2928e2c2d89bea4cb227788aa04f44909b6a",
  "op_in_trx": 0,
  "timestamp": "2017-11-25T03:30:48",
  "virtual_op": false,
  "trx_in_block": 19
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mamont",
      "author": "remme",
      "weight": 59406,
      "rshares": 4107809962,
      "permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "pending_payout": "0.009 HBD",
      "total_vote_weight": 64108
    }
  ],
  "block": 16821623,
  "trx_id": "00ad385017f7c87ef414d5033c011e6da8c22bc1",
  "op_in_trx": 1,
  "timestamp": "2017-10-31T20:43:30",
  "virtual_op": true,
  "trx_in_block": 0
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "remme",
      "weight": 10000,
      "permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks"
    }
  ],
  "block": 16821623,
  "trx_id": "00ad385017f7c87ef414d5033c011e6da8c22bc1",
  "op_in_trx": 0,
  "timestamp": "2017-10-31T20:43:30",
  "virtual_op": false,
  "trx_in_block": 0
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"reblog\",{\"account\":\"mamont\",\"author\":\"remme\",\"permlink\":\"remme-using-blockchain-for-access-management-and-distributed-authentication\"}]",
      "required_auths": [],
      "required_posting_auths": [
        "mamont"
      ]
    }
  ],
  "block": 16762298,
  "trx_id": "7767c141106e70b1cd7434da9ccd086724284b65",
  "op_in_trx": 0,
  "timestamp": "2017-10-29T19:16:57",
  "virtual_op": false,
  "trx_in_block": 6
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"mamont\",\"following\":\"remme\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "mamont"
      ]
    }
  ],
  "block": 16762270,
  "trx_id": "8e70bb56eb8066c7e5eee7616aecd1415a9e6bda",
  "op_in_trx": 0,
  "timestamp": "2017-10-29T19:15:33",
  "virtual_op": false,
  "trx_in_block": 16
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mamont",
      "author": "remme",
      "weight": 41498,
      "rshares": 4107809962,
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "pending_payout": "0.010 HBD",
      "total_vote_weight": 66693
    }
  ],
  "block": 16762248,
  "trx_id": "09531c161b1da2a0ed7df8611946402aafb56c81",
  "op_in_trx": 1,
  "timestamp": "2017-10-29T19:14:27",
  "virtual_op": true,
  "trx_in_block": 25
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "remme",
      "weight": 10000,
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication"
    }
  ],
  "block": 16762248,
  "trx_id": "09531c161b1da2a0ed7df8611946402aafb56c81",
  "op_in_trx": 0,
  "timestamp": "2017-10-29T19:14:27",
  "virtual_op": false,
  "trx_in_block": 25
}

{
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "mamont",
      "weight": 10000,
      "permlink": "keep-your-information-safe-with-blockchain-technology"
    }
  ],
  "block": 16762044,
  "trx_id": "928fc801e27bfe1488cc910cda1a4d2935966b84",
  "op_in_trx": 0,
  "timestamp": "2017-10-29T19:04:15",
  "virtual_op": false,
  "trx_in_block": 25
}

{
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "mamont",
      "weight": 10000,
      "permlink": "the-hackathon-we-won"
    }
  ],
  "block": 16762041,
  "trx_id": "8c1002af786077b70368af6e97988d04bc5a550c",
  "op_in_trx": 0,
  "timestamp": "2017-10-29T19:04:06",
  "virtual_op": false,
  "trx_in_block": 1
}

{
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "mamont",
      "weight": 10000,
      "permlink": "remme-technical-white-paper"
    }
  ],
  "block": 16762012,
  "trx_id": "66baadccee5177e3e940a934a9d9db78711ad109",
  "op_in_trx": 0,
  "timestamp": "2017-10-29T19:02:39",
  "virtual_op": false,
  "trx_in_block": 15
}

{
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "mamont",
      "weight": 10000,
      "permlink": "hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine"
    }
  ],
  "block": 16761996,
  "trx_id": "9687d25c06cf403d7b56b70c340d24fb1a9cc62d",
  "op_in_trx": 0,
  "timestamp": "2017-10-29T19:01:51",
  "virtual_op": false,
  "trx_in_block": 24
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "crypto.girl",
      "weight": 10000,
      "permlink": "salt-ico-today"
    }
  ],
  "block": 16438633,
  "trx_id": "a804b9edc40eced0d53418bbfb384db8da0e4f3e",
  "op_in_trx": 0,
  "timestamp": "2017-10-18T13:24:33",
  "virtual_op": false,
  "trx_in_block": 19
}

{
  "op": [
    "comment",
    {
      "body": "Interesting post.  I was about to post a similair thread. I'm not sure if coins are that high risk. The quality coins are here to stay and it's like buying in at the S&P 500 50 years ago. Cryptos will fall and rise  at a more rapit phase any investment market has ever seen. Just hold (literaly) and enjoy the ride.  Does anyone know about:  https://www.coincheckup.com This site is really helpful in my coin research. I don't know any other sites with so much indepth analysis.",
      "title": "",
      "author": "kimberlee17",
      "permlink": "re-mamont-remme-technical-white-paper-20170922t124610728z",
      "json_metadata": "{\"tags\":[\"cybersecurity\"],\"links\":[\"https://www.coincheckup.com\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "mamont",
      "parent_permlink": "remme-technical-white-paper"
    }
  ],
  "block": 15689862,
  "trx_id": "0e04bb9901798150f3d44bfdff1bca1cdc8bd7af",
  "op_in_trx": 0,
  "timestamp": "2017-09-22T12:46:12",
  "virtual_op": false,
  "trx_in_block": 1
}

{
  "op": [
    "vote",
    {
      "voter": "naveen.teja",
      "author": "mamont",
      "weight": 10000,
      "permlink": "remme-technical-white-paper"
    }
  ],
  "block": 14831525,
  "trx_id": "eedbf18712f77a2ce1bd934514bd2a6a8939787c",
  "op_in_trx": 0,
  "timestamp": "2017-08-23T17:07:42",
  "virtual_op": false,
  "trx_in_block": 33
}

{
  "op": [
    "vote",
    {
      "voter": "flodner",
      "author": "mamont",
      "weight": 10000,
      "permlink": "the-hackathon-we-won"
    }
  ],
  "block": 14679055,
  "trx_id": "546558cca926ad51400aa4e4ffd789c12fd82676",
  "op_in_trx": 0,
  "timestamp": "2017-08-18T10:02:21",
  "virtual_op": false,
  "trx_in_block": 13
}

{
  "op": [
    "vote",
    {
      "voter": "flodner",
      "author": "mamont",
      "weight": 10000,
      "permlink": "keep-your-information-safe-with-blockchain-technology"
    }
  ],
  "block": 14679047,
  "trx_id": "623ee7608e823adcc47a708b91e28004d2bdd089",
  "op_in_trx": 0,
  "timestamp": "2017-08-18T10:01:57",
  "virtual_op": false,
  "trx_in_block": 4
}

{
  "op": [
    "vote",
    {
      "voter": "flodner",
      "author": "mamont",
      "weight": 10000,
      "permlink": "hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine"
    }
  ],
  "block": 14679033,
  "trx_id": "ba20084beef4e552c807b7165dd3817a4369c758",
  "op_in_trx": 0,
  "timestamp": "2017-08-18T10:01:15",
  "virtual_op": false,
  "trx_in_block": 0
}

{
  "op": [
    "vote",
    {
      "voter": "flodner",
      "author": "mamont",
      "weight": 10000,
      "permlink": "first-blockchain-wedding-in-ukraine"
    }
  ],
  "block": 14679030,
  "trx_id": "bb0ad14568ce8b218407fe1315b85c65fe589354",
  "op_in_trx": 0,
  "timestamp": "2017-08-18T10:01:06",
  "virtual_op": false,
  "trx_in_block": 8
}

{
  "op": [
    "vote",
    {
      "voter": "flodner",
      "author": "mamont",
      "weight": 10000,
      "permlink": "remme-technical-white-paper"
    }
  ],
  "block": 14679023,
  "trx_id": "3aef5a0d69d6db9394db9b5458859f1f05afb70d",
  "op_in_trx": 0,
  "timestamp": "2017-08-18T10:00:45",
  "virtual_op": false,
  "trx_in_block": 13
}

{
  "op": [
    "vote",
    {
      "voter": "voloshyn",
      "author": "mamont",
      "weight": 10000,
      "permlink": "the-hackathon-we-won"
    }
  ],
  "block": 14678997,
  "trx_id": "5143ec031a6e84349cbc2a5ae93e598df46aea2e",
  "op_in_trx": 0,
  "timestamp": "2017-08-18T09:59:27",
  "virtual_op": false,
  "trx_in_block": 2
}

{
  "op": [
    "comment_payout_update",
    {
      "author": "mamont",
      "permlink": "remme-technical-white-paper"
    }
  ],
  "block": 14379515,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 3,
  "timestamp": "2017-08-07T23:35:42",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "pandoraboxchain",
      "author": "mamont",
      "weight": 14885,
      "rshares": 1950958832,
      "permlink": "remme-technical-white-paper",
      "pending_payout": "0.016 HBD",
      "total_vote_weight": 67282
    }
  ],
  "block": 14205739,
  "trx_id": "3c6359fed7ea1a29c1ce8dc98db600136a136426",
  "op_in_trx": 1,
  "timestamp": "2017-08-01T22:31:18",
  "virtual_op": true,
  "trx_in_block": 32
}

{
  "op": [
    "vote",
    {
      "voter": "pandoraboxchain",
      "author": "mamont",
      "weight": 10000,
      "permlink": "remme-technical-white-paper"
    }
  ],
  "block": 14205739,
  "trx_id": "3c6359fed7ea1a29c1ce8dc98db600136a136426",
  "op_in_trx": 0,
  "timestamp": "2017-08-01T22:31:18",
  "virtual_op": false,
  "trx_in_block": 32
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "bicalabs",
      "author": "mamont",
      "weight": 52397,
      "rshares": 2572928208,
      "permlink": "remme-technical-white-paper",
      "pending_payout": "0.009 HBD",
      "total_vote_weight": 52397
    }
  ],
  "block": 14205728,
  "trx_id": "76a6673001f74cda40f26a1e47deb358026733af",
  "op_in_trx": 1,
  "timestamp": "2017-08-01T22:30:45",
  "virtual_op": true,
  "trx_in_block": 13
}

{
  "op": [
    "vote",
    {
      "voter": "bicalabs",
      "author": "mamont",
      "weight": 10000,
      "permlink": "remme-technical-white-paper"
    }
  ],
  "block": 14205728,
  "trx_id": "76a6673001f74cda40f26a1e47deb358026733af",
  "op_in_trx": 0,
  "timestamp": "2017-08-01T22:30:45",
  "virtual_op": false,
  "trx_in_block": 13
}

{
  "op": [
    "comment",
    {
      "body": "We are pleased to announce our current technical white paper.\n\nWe welcome everyone to provide feedback and improve document.\n\nLet`s start discussion and make it better together.\n\n\n# White paper\n**(v.0.1)**\n **July 30, 2017** \n\n\n## Contents\n\n\n**Background**\t\n**REMME’s Edge**  \t\n**How REMME works** \t\n**Use of multi-factor authentication**  \t\n**Conclusion** \t\n**Links** \t\n \n\n**Background**\n\nThe goal of the REMME high-end secure system is to build a distributed Public Key Infrastructure (“PKI”) management on top of the x.509 standard [1] that will help big infrastructure companies, government authorities, financial and blockchain companies address the problem of security failings. \n \nA look at the classical variant of certificate management used in most current systems shows that it is usually built in a hierarchical structure. This enables the certificates to be managed based on the certificate authority (CA) entity which stores, issues and signs the digital certificates.  \n \nThe Certificate Authority uses a hierarchical tree system to build trust on the network all through to the root certificate. However, since the center of the system is always a point of attack, a compromise of the root certificate will expose the entire system to any form of vulnerability.  \n \nREMME will use the blockchain technology as a vehicle of transportation and a source of consensus to offer a solution to this problem: decentralization.  \n\n\n\n**REMME’s Edge**  \n\nThough not the first to build a distributed system using the blockchain technology to manage certificates, REMME comes with a difference from what DNS SSL by Namecoin developers [2] and EMCSSL [3] built on the Emercoin technology have to offer as the first to use the blockchain and SSL.  \n \nWhile the DNS SSL system allows the binding of DNS to the certificate hash, the EMCSSL built on the Emercoin decentralized solution for storing the key-value bundle enables the serial number of the certificate to be the key and the certificate hash as the value. The key is unique and the hash value can be changed. By this way, certificate management is implemented. \n\nREMME differs from these two systems as it does not save the certificate’s data on the blockchain at the initial point. A revocation of the certificate has to be carried out by publishing a secret revocation message, which is signed by a private key of the network blockchain address. The scheme, which is used to connect blockchain address with a certificate, is very similar to the proxy certificate mechanism described in RFC3820 (X.509 Proxy Certificate Profile). [4]\n \n \n \n**How REMME works** \n\nIn our case, the message is a normal blockchain transaction. The mechanism is very similar to that of classic certificate management systems, in which certificate revocation lists are used to manage CRLs. This comes in a data format that publishes a list of revoked certificates and signed by a Certificate Authority. There is an OCSP extension, which allows the central server to manage the status of certificates.  \n \nREMME also provides a self-managed certification center for the owner of the private key to the network’s block address as a unique opportunity for the decentralized management of certificates by the user. The same address is also an account on systems that use REMME authentication. \n \nThe system can be used with a number of different blockchains (Bitcoin, Emercoin, Ethereum, etc.) and sidechains  (Rootstock, Exonum, etc.) by customer's choice. This document covers technology solution based on the Bitcoin network. \n\nThe four basic types of REMME certificates are determined according to the signature of the publisher: \n1.\tSelf-signed certificates; \n2.\tCertificates signed by the organization; \n3.\tCertificates signed by the certifying center REMME; \n4.\tCertificates signed by an official certifying center \n\nThe first 3 types of certificate differ only in the subscription method, while the changes in the fourth type are related to the limitations of the certification centers and its use of the imperfection of the existing mechanism to issue certificates. \n \nThis document does not consider x.509 in details. To understand this document, it is advisable to get acquainted with RFC5280 [5] and a general idea of how the blockchain works. In short, the blockchain system is a data storage technology in a sequential chain based on a set of rules that allows users to add new data. All participants can use the consensus mechanism to add data at the same time, however data from the blockchain cannot be deleted. The unique identifier in the block system is the hash of the public part of the key (let it be the address in the future) while the private part of this key signs the data added to the blockchain. \n \nBitcoin addresses are identifiers that are used to send bitcoins from one person to another. \n \nThe REMME technology provides: \n\n-\tthe ability to associate a bitcoin address with a certificate;\n-\tthe ability to organize a decentralized system for revocation of certificates.\n  \nThe address is linked by signing key certificate data such as the public key's hash, the hash of the revocation transaction etc using the private key. The certificate can be revoked by using the \"warrant canary\" mechanism [6]. A common bitcoin transaction is created - one of the outputs of which will be the activity marker of the certificate. As soon as the output is spent, the certificate is considered withdrawn. In RFC 6960 [7], it is described that in OCSP the answer can add CRLReason (the cause of revocation of the certificate) but this is not used in the basic version of REMME. \n \n    CertStatus ::= CHOICE {\n           good        [0]     IMPLICIT NULL,\n           revoked     [1]     IMPLICIT RevokedInfo,\n           unknown     [2]     IMPLICIT UnknownInfo }\n    RevokedInfo ::= SEQUENCE {\n           revocationTime              GeneralizedTime,\n           revocationReason    [0]     EXPLICIT CRLReason OPTIONAL }\n\nIn the certificate, it is necessary to save: \n●\tSignature by private address key \n●\tHash of revoke transaction {txOutHash} \n●\tExit number of the revocation transaction {txOutNumber} \n \n1.\tThe first type is a self-signed certificate in which accessLocation [8] from OCSP [9] has a special format. \n \n    AccessDescription  ::=  SEQUENCE {\n               accessMethod          OBJECT IDENTIFIER,\n               accessLocation        GeneralName  }\n \n    http://ocsp.REMME.io/{$txOutHash}/{$txOutNumber}/ \n \nThis allows the server client to query the OCSP server about the status of the certificate even if the client does not know about the existence of the REMME add-on. But then, the service becomes centralized hence using this method is not recommended. The signature of the private address key is written to the extension x509 nsComment. \n \n2.\tFor the second type of certificate for the structure of additional data, REMME repeats the first type, but the certificate itself is signed by the private key of the organization that issued the certificate. \n\n3.\tThe third type of certificate is the same as the second type except that REMME acts instead of an organization and the certificate data is checked by the REMME certificate authority. \n\n4.\tThe fourth type of certificate is needed to enable the use of decentralized REMME technology in conjunction with the CA, which has no idea of the existence of REMME. In other words, there is no way to change the fields that the CA fills on its own, but the mechanism allows the use of traditional certification centers.\n\nThough signed by third parties, the second and third types of certificate allow users to revoke the certificate using their own signature as well as the signature of the CA.\n  \nThe standard X.509 certificate consists of several fields. The \"Name of the subject\" field is one of the most important fields. This field specifies the unique name (Dname) of the certificate owner. Dname is a unique name that points to an X.500 directory object. It consists of several attribute-value pairs (RDNS). Some of the most common RDN names are: \n \nCN: CommonName \nOU: OrganizationalUnit \nO: Organization \nL: Locality \nS: StateOrProvinceName \nC: CountryName \n \nExample of subject: \nCN=Sample Cert, OU=R&D, O=Company Ltd., L=Dublin 4, S=Dublin,C=IE \n \nIn the case of the fourth type of certificate, fields will be filled with special values: \n \n    O=Bitcoin \n    UID=12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX (Bitcoin address)\t \n    OU=0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd51298 (A transaction hash that marks a revoke of \n    certificate)\n    ST=0 (transaction output number) \n    L=Hy15Vc5HFHisgkB5sUiithUC6i0uPETcVBVYHHpMQePbTK6ZNwOombXS+I/PnouqYrkmV7H4Wl6egIyQuJc70Xs=(Signature \n    by private address key)\n \nAll other values are set according to the needs of the CA. \n\nThe signature for all types of the certificate is formed by signing a special format message with a private address key. \n \nSign (\"http://REMME.io/certificate/\" + Certificate serial number + \"/\" + Public key hash + \"/\" + Revocation transaction hash + \"/\" + Revocation transaction number) \n \nThe certificate can be revoked using the \"warrant canary\" mechanism. A common bitcoin transaction is created - one of whose outputs will be the activity token of the certificate. As soon as the output is spent, the certificate is considered withdrawn: \n \n    gettxout 0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098 0 \n    { \n    \"bestblock\" : \"000000000000000000ff4c920d339f7211125f01957ac6d42a876162025764f9\", \"confirmations\" : 462282, \n    \"value\" : 50.00000000, \"scriptPubKey\" : { \"asm\" : \n    \"0496b538e853519c726a2c91e61ec11600ae1390813a627c66fb8be7947be63c52da7589379515d4e\n    0a604f8141781e62294721166bf621e73a82cbf2342c858ee OP_CHECKSIG\", \n    \"hex\" : \n    \"410496b538e853519c726a2c91e61ec11600ae1390813a627c66fb8be7947be63c52da7589379515d\n    4e0a604f8141781e62294721166bf621e73a82cbf2342c858eeac\", \n    \"reqSigs\" : 1, \n    \"type\" : \"pubkey\", \n    \"addresses\" : [ \n    \"12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX\" \n    ] \n    }, \n    \"version\" : 1, \n    \"coinbase\" : true \n    } \n \nIn Bitcoin node, this mechanism is used as any full Bitcoin node keeps an indexed list of all UTXO (unspent transaction output) in its memory and replies to such requests are very fast and efficient. \n\nScenario for client authentication: \n1.\tCheck certificate.\n2.\tCheck signature of the certificate.\n3.\tCheck that the certificate data is signed with the private key of blockchain account.\n4.\tFind  UTXO (unspent transaction output) with number N of the hash transaction with hash X. If this output is unspent, then the certificate is still active. \n\n\n**Use of multi-factor authentication**  \n\nThe two-factor authentication is an additional layer of security ensuring that only the owner of the account can access it, even if the private SSL certificate key has been compromised. Multifactor authentication is a cryptographic system that allows access only in the case of a mathematically conditioned conjunction of several keys [10]. Commonly, the first key is generated according to one factor and is then used to decrypt the second one. \n \nE.g., ATM systems around the world utilize a relatively successful two-factor authentication implementation. For more than 30 years, banks' clients obtain secure access to their accounts and withdraw cash using a PIN code and a bank card. This technological approach was remarkably successful due to its notable ease of use and, nonetheless, cryptographically solid authentication method. The ATM network does not store any credentials exchanged between the server and the client. No information regarding tokens, contacts or passwords is ever transmitted over the wires between the ATM and the bank. If any part of the system is compromised, it does not permit access to any other part. \n \nThe choice of technology for the second factor depends on the characteristics of the system, which is protected by REMME technology. However, when choosing technology, it should be taken into account that the more reliable the authentication solution is, the more complicated and expensive it is to use. Therefore, it is vital to choose the optimal balance between reliability and complexity. \n \nFor example, if a system requires a physical presence of an authorized person, then the best option for the second factor would be to use biometric data, such as a fingerprint scan or an eye retina scan. This data can be used to validate the certificate. [11] \n\nIf the system uses some local sensor, then the second factor would be the physical connection to the local network check. \nIf the system is remote, it is optimal to use a secondary device (a phone or another PC). The probability of simultaneous malware infection of two devices is lower than of one. It would also help to protect the account with a compromised certificate. \n \nOne of the simplest variations of two-step authorization is to use two separate certificates on two different devices. In this case, the use of one certificate should be confirmed with the second one. Additionally, an instant messenger can be installed on the second device to receive secret keys via messages from a protected system. In this case, the reliability of the second factor will be equal to the reliability of the messenger account. For example, it is possible to use Telegram (or other messengers), email, or email + PGP key. \n \nSpecial consideration should be given to the standard TOTP (time-based one-time password) method, which generates one-time codes within certain time intervals (e.g., every thirty seconds). Such a scheme is implemented, for example, in the Google Authenticator application. [12] You can also use an entirely-hardware solution for generating access tokens, for instance with the help of YubiKey [13], Yubico or Trezor [14].\n\n\n\n**Conclusion** \n\nThe goal of the REMME high-end secure system is to help organizations like infrastructure companies, IoT, medtech, financial and blockchain companies protect sensitive data. It is a distributed Public Key Infrastructure (“PKI”) management technology built on top of the X.509 certificate standard that uses SSL to protect the entire channel from an attack.\n\nREMME does not save the certificate’s data on the blockchain at the initial point. A revocation of the certificate has to be carried out by publishing a secret revocation message, which is signed by a private key of the network blockchain address. According to this approach, user do not need to wait for few confirmation, the certificate will be valid immediately after creating transaction. The system can be used with a number of different blockchains (Bitcoin, Emercoin, Ethereum, etc.) and sidechains  (Rootstock, Exonum, etc.) by customer's choice.\n\nThe two-factor authentication is an additional layer of security ensuring that only the owner of the account can access it, even if the private SSL certificate key has been compromised. The choice of technology for the second factor depends on the characteristics of the system, which is protected by REMME technology.\n\nDuring the development of the REMME system, a number of standard and well-known components that are time-tested and proven effective by numerous audits were used. \n\n\n**Links** \n \n1.\thttps://www.rfc-editor.org/rfc/rfc5912.txt \n2.\thttps://namecoin.org/ \n3.\thttp://emercoin.com/EMCSSL\n4.\thttps://www.ietf.org/rfc/rfc3820.txt \n5.\thttps://tools.ietf.org/html/rfc5280 \n6.\thttps://en.wikipedia.org/wiki/Warrant_canary\n7.\thttps://tools.ietf.org/html/rfc6960\n8.\thttps://tools.ietf.org/html/rfc5280#section-4.2.2.1\n9.\thttps://tools.ietf.org/html/rfc6960\n10.\thttps://www.miracl.com/miracl-labs/m-pin-a-multi-factor-zero-knowledge-authentication-protocol\n11.\thttp://www.cse.lehigh.edu/prr/Biometrics/Archive/Papers/Uludag05.pdf  \n12.\thttps://www.google.com/intl/ru/landing/2step/features.html  \n13.\thttps://www.yubico.com/products/yubikey-hardware/  \n14.\thttps://trezor.io/",
      "title": "REMME Technical White Paper",
      "author": "mamont",
      "permlink": "remme-technical-white-paper",
      "json_metadata": "{\"tags\":[\"cybersecurity\",\"authentication\",\"blockchain\",\"remme\",\"whitepaper\"],\"links\":[\"http://ocsp.REMME.io/{$txOutHash}/{$txOutNumber}/\",\"http://REMME.io/certificate/\",\"https://www.rfc-editor.org/rfc/rfc5912.txt\",\"https://namecoin.org/\",\"http://emercoin.com/EMCSSL\",\"https://www.ietf.org/rfc/rfc3820.txt\",\"https://tools.ietf.org/html/rfc5280\",\"https://en.wikipedia.org/wiki/Warrant_canary\",\"https://tools.ietf.org/html/rfc6960\",\"https://tools.ietf.org/html/rfc5280#section-4.2.2.1\",\"https://www.miracl.com/miracl-labs/m-pin-a-multi-factor-zero-knowledge-authentication-protocol\",\"http://www.cse.lehigh.edu/prr/Biometrics/Archive/Papers/Uludag05.pdf\",\"https://www.google.com/intl/ru/landing/2step/features.html\",\"https://www.yubico.com/products/yubikey-hardware/\",\"https://trezor.io/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "cybersecurity"
    }
  ],
  "block": 14178255,
  "trx_id": "fe22ccee517308b1a1e2b40f5e6e634b3379fdc3",
  "op_in_trx": 0,
  "timestamp": "2017-07-31T23:35:45",
  "virtual_op": false,
  "trx_in_block": 8
}

{
  "op": [
    "curation_reward",
    {
      "author": "hipster",
      "reward": "12.395957 VESTS",
      "curator": "mamont",
      "permlink": "updates-satoshi-pie-ethereum-multisig-has-been-hacked",
      "payout_must_be_claimed": true
    }
  ],
  "block": 14031067,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 23,
  "timestamp": "2017-07-26T20:52:03",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mamont",
      "author": "hipster",
      "weight": 1959,
      "rshares": 4107809962,
      "permlink": "updates-satoshi-pie-ethereum-multisig-has-been-hacked",
      "pending_payout": "2.315 HBD",
      "total_vote_weight": 816180
    }
  ],
  "block": 13830702,
  "trx_id": "0b0ce876003b1c1bab3ea7b7b64cfc477e7b6056",
  "op_in_trx": 1,
  "timestamp": "2017-07-19T21:44:15",
  "virtual_op": true,
  "trx_in_block": 0
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "hipster",
      "weight": 10000,
      "permlink": "updates-satoshi-pie-ethereum-multisig-has-been-hacked"
    }
  ],
  "block": 13830702,
  "trx_id": "0b0ce876003b1c1bab3ea7b7b64cfc477e7b6056",
  "op_in_trx": 0,
  "timestamp": "2017-07-19T21:44:15",
  "virtual_op": false,
  "trx_in_block": 0
}

{
  "op": [
    "comment",
    {
      "body": "Congratulations @mamont! You have received a personal award!\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/@mamont/birthday1.png)](http://steemitboard.com/@mamont) Happy Birthday - 1 Year\nClick on the badge to view your own Board of Honor on SteemitBoard.\n\nFor more information about this award, click [here](https://steemit.com/steemitboard/@steemitboard/steemitboard-update-8-happy-birthday)\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
      "title": "",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-mamont-20170711t002056000z",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}",
      "parent_author": "mamont",
      "parent_permlink": "the-hackathon-we-won"
    }
  ],
  "block": 13574838,
  "trx_id": "5a0d5750ad329618959cf72e0fc8d5aa474bd0c0",
  "op_in_trx": 0,
  "timestamp": "2017-07-11T00:20:57",
  "virtual_op": false,
  "trx_in_block": 17
}

{
  "op": [
    "comment_payout_update",
    {
      "author": "mamont",
      "permlink": "the-hackathon-we-won"
    }
  ],
  "block": 13418443,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 6,
  "timestamp": "2017-07-05T13:30:15",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "comment_reward",
    {
      "author": "mamont",
      "payout": "0.372 HBD",
      "permlink": "the-hackathon-we-won",
      "author_rewards": 227,
      "total_payout_value": "0.372 HBD",
      "curator_payout_value": "0.000 HBD",
      "beneficiary_payout_value": "0.000 HBD"
    }
  ],
  "block": 13418443,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 5,
  "timestamp": "2017-07-05T13:30:15",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "author_reward",
    {
      "author": "mamont",
      "permlink": "the-hackathon-we-won",
      "hbd_payout": "0.185 HBD",
      "hive_payout": "0.000 HIVE",
      "vesting_payout": "235.790684 VESTS",
      "payout_must_be_claimed": true,
      "curators_vesting_payout": "0.000000 VESTS"
    }
  ],
  "block": 13418443,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 4,
  "timestamp": "2017-07-05T13:30:15",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "curation_reward",
    {
      "author": "nebi",
      "reward": "10.342639 VESTS",
      "curator": "mamont",
      "permlink": "re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z",
      "payout_must_be_claimed": true
    }
  ],
  "block": 13369497,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 5,
  "timestamp": "2017-07-03T20:40:51",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "comment_payout_update",
    {
      "author": "mamont",
      "permlink": "keep-your-information-safe-with-blockchain-technology"
    }
  ],
  "block": 13369235,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 4,
  "timestamp": "2017-07-03T20:27:45",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "comment_reward",
    {
      "author": "mamont",
      "payout": "0.043 HBD",
      "permlink": "keep-your-information-safe-with-blockchain-technology",
      "author_rewards": 27,
      "total_payout_value": "0.043 HBD",
      "curator_payout_value": "0.000 HBD",
      "beneficiary_payout_value": "0.000 HBD"
    }
  ],
  "block": 13369235,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 3,
  "timestamp": "2017-07-03T20:27:45",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "author_reward",
    {
      "author": "mamont",
      "permlink": "keep-your-information-safe-with-blockchain-technology",
      "hbd_payout": "0.021 HBD",
      "hive_payout": "0.000 HIVE",
      "vesting_payout": "28.959403 VESTS",
      "payout_must_be_claimed": true,
      "curators_vesting_payout": "0.000000 VESTS"
    }
  ],
  "block": 13369235,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 2,
  "timestamp": "2017-07-03T20:27:45",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "kumaranvpl",
      "author": "mamont",
      "weight": 351,
      "rshares": 232138524,
      "permlink": "the-hackathon-we-won",
      "pending_payout": "0.604 HBD",
      "total_vote_weight": 213519
    }
  ],
  "block": 13217495,
  "trx_id": "2a2112bb9f7201e19efa012619710d21cf82ffdf",
  "op_in_trx": 1,
  "timestamp": "2017-06-28T13:54:06",
  "virtual_op": true,
  "trx_in_block": 11
}

{
  "op": [
    "vote",
    {
      "voter": "kumaranvpl",
      "author": "mamont",
      "weight": 10000,
      "permlink": "the-hackathon-we-won"
    }
  ],
  "block": 13217495,
  "trx_id": "2a2112bb9f7201e19efa012619710d21cf82ffdf",
  "op_in_trx": 0,
  "timestamp": "2017-06-28T13:54:06",
  "virtual_op": false,
  "trx_in_block": 11
}

{
  "op": [
    "comment",
    {
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://medium.com/remme/the-hackathon-we-won-5e9fe6a67189",
      "title": "",
      "author": "cheetah",
      "permlink": "cheetah-re-mamontthe-hackathon-we-won",
      "json_metadata": "",
      "parent_author": "mamont",
      "parent_permlink": "the-hackathon-we-won"
    }
  ],
  "block": 13217075,
  "trx_id": "6ac43fe45bd8b95bb09816521da118d2ccd1dd95",
  "op_in_trx": 0,
  "timestamp": "2017-06-28T13:31:51",
  "virtual_op": false,
  "trx_in_block": 6
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cheetah",
      "author": "mamont",
      "weight": 46,
      "rshares": 506440232,
      "permlink": "the-hackathon-we-won",
      "pending_payout": "0.601 HBD",
      "total_vote_weight": 213076
    }
  ],
  "block": 13217073,
  "trx_id": "34401a26ce6ccf8b3d66777816109e022dd372dd",
  "op_in_trx": 1,
  "timestamp": "2017-06-28T13:31:45",
  "virtual_op": true,
  "trx_in_block": 6
}

{
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "mamont",
      "weight": 100,
      "permlink": "the-hackathon-we-won"
    }
  ],
  "block": 13217073,
  "trx_id": "34401a26ce6ccf8b3d66777816109e022dd372dd",
  "op_in_trx": 0,
  "timestamp": "2017-06-28T13:31:45",
  "virtual_op": false,
  "trx_in_block": 6
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "sveokla",
      "author": "mamont",
      "weight": 3453,
      "rshares": 38379882573,
      "permlink": "the-hackathon-we-won",
      "pending_payout": "0.594 HBD",
      "total_vote_weight": 212110
    }
  ],
  "block": 13217059,
  "trx_id": "f56c516ace2a44cd14eeb10825c5ededfcff960e",
  "op_in_trx": 1,
  "timestamp": "2017-06-28T13:31:03",
  "virtual_op": true,
  "trx_in_block": 49
}

{
  "op": [
    "vote",
    {
      "voter": "sveokla",
      "author": "mamont",
      "weight": 10000,
      "permlink": "the-hackathon-we-won"
    }
  ],
  "block": 13217059,
  "trx_id": "f56c516ace2a44cd14eeb10825c5ededfcff960e",
  "op_in_trx": 0,
  "timestamp": "2017-06-28T13:31:03",
  "virtual_op": false,
  "trx_in_block": 49
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mamont",
      "author": "mamont",
      "weight": 0,
      "rshares": 4107809962,
      "permlink": "the-hackathon-we-won",
      "pending_payout": "0.057 HBD",
      "total_vote_weight": 64108
    }
  ],
  "block": 13217046,
  "trx_id": "807002114f2fda662870a95fa85700ca079fc1e6",
  "op_in_trx": 2,
  "timestamp": "2017-06-28T13:30:18",
  "virtual_op": true,
  "trx_in_block": 16
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "mamont",
      "weight": 10000,
      "permlink": "the-hackathon-we-won"
    }
  ],
  "block": 13217046,
  "trx_id": "807002114f2fda662870a95fa85700ca079fc1e6",
  "op_in_trx": 1,
  "timestamp": "2017-06-28T13:30:18",
  "virtual_op": false,
  "trx_in_block": 16
}

{
  "op": [
    "comment",
    {
      "body": "https://steemitimages.com/DQmbmC9KxLhLWQgpvLvbmj3XjnBVACajujNCSmt2BPJiS15/1-LPBwbl08mHBq-sbP9GyiDw.jpeg\n\nJust two weeks ago we returned from the Microsoft Blockchain Intensive, and we brought back some good news!\n\nFirst of all, what is the Microsoft Blockchain Intensive? It’s a large, 3-day event in Kyiv, held by Microsoft Ukraine and focused on solving real-life challenges with Blockchain technology. On June 9–11th, 2017, the event gathered over 500 visitors, and received praise and support from PwC, Deloitte, EY, Infopulse, Distributed Lab, IDF Reforms Lab, and other local and international companies. It was a smorgasbord of awesome — such a massive gathering of amazing projects and ideas!\n\nOn the second and third day of the Intensive, 18 teams competed in a Blockchain-themed hackathon. The primary task was to create a solution, which would be fully compliant with the core ideas of Blockchain: transparency, decentralization, and security. The participants were free to either select an open topic or embrace a challenge suggested by real clients such as Raiffeisen Bank Aval and The Ukrainian Sea Ports Authority.\n\nFor the hackathon, REMME teamed up with Infopulse, an international vendor of services in the areas of Software R&D, Application Management, IT Operations, and Information Security. This proved to be a successful partnership, as together we won first place in the Microsoft Blockchain Intensive with our traffic collision awareness and reporting system, which is based on the core REMME authentication technology, IPFS protocol and Ethereum Blockchain.\n\nhttps://steemitimages.com/DQmRZZMfqh19EFgAjPA6np9oNCpqzujQU89c1biQ6CvvEW2/1-jGDfNIyHYB3kQHVdxlmVBw.jpeg\n\nWe also made off with some amazing prizes! To the first place winners, Ernst & Young Global Limited offers business, legal and marketing consulting; help in gaining access to investors and global companies; as well as participation in one of their educational programs. Aside from that, they awarded us with invitations to VivaTechnology in Paris, one of the world’s biggest and most important startup conferences. Airalab has awarded us with a $10,000 grant to fulfill our project. Some exciting times are ahead!\n\nThe Solution\n\nWe presented our own solution for the automotive industry to make the roads safer. According to the statistics, the total cost of traffic accidents in 2016 was $249,271,731,355 and 16,842,685 people were victims of car accidents . We started thinking about how blockchain can help decrease traffic accident rates, and make the life of both drivers and pedestrians safer in a world with 1.2 billion vehicles on the road?\n\nFor the presentation, we used one of the most widespread use cases: two cars collide at a crossroad. Each driver claims to be driving on a green light. How do we find out who is right and who is wrong? Is it possible that the traffic lights were broken, and both drivers were deceived by a traffic light malfunction? The situation could potentially be worse, if one car was driven by an autopilot, or there were no cameras at that crossroad to show which light was actually on.\n\nhttps://steemitimages.com/DQmfVk7mu1pdTRvg3PaEVE11CnJ5KiiSXj6us6UDqcyv9Fx/1-V6Z9Ewygg4vCsA_-08Hj5w.jpeg\nOur joint REMME-Infopulse team consisted of Alex Momot (CEO REMME), Taras Emelianenko (CTO REMME), Jan Keil (Vice President of Marketing at Infopulse), Yaroslav Pishta (Scala Engineer), Anatolii Padenko (Smart Contract Engineer), and Alex Brezhnev (Back-End Developer).\n\nTechnology\n\nhttps://steemitimages.com/DQmZVBxYZ6oizTQ6Wm5oG3ZiwrgQMsGFBHbmZJX7QkNecXp/1-MRvLYcpchlDD4OLfSr3_oA.png\n\nThe solution is based on the Ethereum blockchain, and utilizes car sensors, telemetry, and distributed technologies to record traffic incidents and settle them before trial. If an accident happens, our system allows one to safely extract and analyze the telemetry data from the car, record it via Smart Contract and Microsoft Azure. The sensors necessary for this process can be located in the car, as well as in other cars, on traffic lights, etc. They record data instantly and send it to Blockchain, which makes forging, stealing or changing it nearly impossible.\n\nThe system also implements Blockchain-secured authentication, protection from cyber attacks, and allows gathering vehicle data for further infrastructure and car safety improvements. To make it more graphic, we presented an interactive visualization based on a sample from a sensor and confirmed data plausibility via Blockchain in Azure Cloud.\n\nWho can make use of it?\n\nAside from municipal and state authorities, this solution is useful for:\nInsurance companies:\nAccess to a car’s reliable telemetry data at the time of the accident and shortly before.\nFind out who is guilty based on this data.\nInstantly pay the insurance money to the victim (including in cryptocurrency)\nCar manufacturers:\nObjective vehicle data, including the one to analyse and improve its safety\nAnalysis of the autopilot, its functions and malfunctions\nWe don’t stop at what we’ve achieved. Currently, we’re continuing our collaboration with Infopulse, reviewing strategic opportunities and researching multiple applications of Blockchain in the automotive industry.\n\nSign-up on REMME news: https://www.remme.io\n\nREMME intro video: https://www.youtube.com/watch?v=9APHeHRmrGw![1-V6Z9Ewygg4vCsA_-08Hj5w.jpeg](![",
      "title": "The Hackathon — We Won!",
      "author": "mamont",
      "permlink": "the-hackathon-we-won",
      "json_metadata": "{\"tags\":[\"blockchain\",\"remme\",\"smartcity\",\"ethereum\",\"iot\"],\"image\":[\"https://steemitimages.com/DQmbmC9KxLhLWQgpvLvbmj3XjnBVACajujNCSmt2BPJiS15/1-LPBwbl08mHBq-sbP9GyiDw.jpeg\",\"https://steemitimages.com/DQmRZZMfqh19EFgAjPA6np9oNCpqzujQU89c1biQ6CvvEW2/1-jGDfNIyHYB3kQHVdxlmVBw.jpeg\",\"https://steemitimages.com/DQmfVk7mu1pdTRvg3PaEVE11CnJ5KiiSXj6us6UDqcyv9Fx/1-V6Z9Ewygg4vCsA_-08Hj5w.jpeg\",\"https://steemitimages.com/DQmZVBxYZ6oizTQ6Wm5oG3ZiwrgQMsGFBHbmZJX7QkNecXp/1-MRvLYcpchlDD4OLfSr3_oA.png\",\"https://img.youtube.com/vi/9APHeHRmrGw/0.jpg\"],\"links\":[\"https://www.remme.io\",\"https://www.youtube.com/watch?v=9APHeHRmrGw!\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "blockchain"
    }
  ],
  "block": 13217046,
  "trx_id": "807002114f2fda662870a95fa85700ca079fc1e6",
  "op_in_trx": 0,
  "timestamp": "2017-06-28T13:30:18",
  "virtual_op": false,
  "trx_in_block": 16
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mamont",
      "author": "nebi",
      "weight": 63794,
      "rshares": 4066731863,
      "permlink": "re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z",
      "pending_payout": "0.076 HBD",
      "total_vote_weight": 63794
    }
  ],
  "block": 13169071,
  "trx_id": "56ce7b04d88771329f727722256a5a21a3e4dcaa",
  "op_in_trx": 1,
  "timestamp": "2017-06-26T21:19:57",
  "virtual_op": true,
  "trx_in_block": 21
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "nebi",
      "weight": 10000,
      "permlink": "re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z"
    }
  ],
  "block": 13169071,
  "trx_id": "56ce7b04d88771329f727722256a5a21a3e4dcaa",
  "op_in_trx": 0,
  "timestamp": "2017-06-26T21:19:57",
  "virtual_op": false,
  "trx_in_block": 21
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "nebi",
      "author": "mamont",
      "weight": 1745,
      "rshares": 521925600,
      "permlink": "keep-your-information-safe-with-blockchain-technology",
      "pending_payout": "0.090 HBD",
      "total_vote_weight": 69462
    }
  ],
  "block": 13168292,
  "trx_id": "d0211f502178169672c2fc39b2117acf27140300",
  "op_in_trx": 1,
  "timestamp": "2017-06-26T20:40:57",
  "virtual_op": true,
  "trx_in_block": 22
}

{
  "op": [
    "vote",
    {
      "voter": "nebi",
      "author": "mamont",
      "weight": 10000,
      "permlink": "keep-your-information-safe-with-blockchain-technology"
    }
  ],
  "block": 13168292,
  "trx_id": "d0211f502178169672c2fc39b2117acf27140300",
  "op_in_trx": 0,
  "timestamp": "2017-06-26T20:40:57",
  "virtual_op": false,
  "trx_in_block": 22
}

{
  "op": [
    "comment",
    {
      "body": "Interesting concept and proposal. Thanks for sharing.",
      "title": "",
      "author": "nebi",
      "permlink": "re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z",
      "json_metadata": "{\"tags\":[\"cybersecurity\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "mamont",
      "parent_permlink": "keep-your-information-safe-with-blockchain-technology"
    }
  ],
  "block": 13168291,
  "trx_id": "45c1bd5a1b0cabc7f647716c4897c334c22da75e",
  "op_in_trx": 0,
  "timestamp": "2017-06-26T20:40:54",
  "virtual_op": false,
  "trx_in_block": 8
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mohammedfelahi",
      "author": "mamont",
      "weight": 150,
      "rshares": 179908305,
      "permlink": "keep-your-information-safe-with-blockchain-technology",
      "pending_payout": "0.080 HBD",
      "total_vote_weight": 65480
    }
  ],
  "block": 13168096,
  "trx_id": "c0f9321207db2fd52f82e7166d12e00f0b056081",
  "op_in_trx": 1,
  "timestamp": "2017-06-26T20:31:06",
  "virtual_op": true,
  "trx_in_block": 7
}

{
  "op": [
    "vote",
    {
      "voter": "mohammedfelahi",
      "author": "mamont",
      "weight": 10000,
      "permlink": "keep-your-information-safe-with-blockchain-technology"
    }
  ],
  "block": 13168096,
  "trx_id": "c0f9321207db2fd52f82e7166d12e00f0b056081",
  "op_in_trx": 0,
  "timestamp": "2017-06-26T20:31:06",
  "virtual_op": false,
  "trx_in_block": 7
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "mamont",
      "author": "mamont",
      "weight": 0,
      "rshares": 4107809962,
      "permlink": "keep-your-information-safe-with-blockchain-technology",
      "pending_payout": "0.077 HBD",
      "total_vote_weight": 64108
    }
  ],
  "block": 13168030,
  "trx_id": "f9bb7dd7ad0416aafe641bf093f965c2fc4abed5",
  "op_in_trx": 2,
  "timestamp": "2017-06-26T20:27:48",
  "virtual_op": true,
  "trx_in_block": 3
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "mamont",
      "weight": 10000,
      "permlink": "keep-your-information-safe-with-blockchain-technology"
    }
  ],
  "block": 13168030,
  "trx_id": "f9bb7dd7ad0416aafe641bf093f965c2fc4abed5",
  "op_in_trx": 1,
  "timestamp": "2017-06-26T20:27:48",
  "virtual_op": false,
  "trx_in_block": 3
}

{
  "op": [
    "comment",
    {
      "body": "![1-j3iIpKepFTzq6QBSdDG0-Q.png](https://steemitimages.com/DQmaUHmYTrE4UzSoKyLVaz1pu4HHgTY8wBuyWFxB3mrCJdg/1-j3iIpKepFTzq6QBSdDG0-Q.png)\n\nPasswords are supposed to secure our information, but even the most trustworthy of companies don’t always stand against the forces of evil in the online world. For example, did you know that the latest hack attack on LinkedIn caused credentials of 117 million users of the professional networking site to be put up for sale online? REMME has found a way to prevent attacks like this from ever happening and stop attackers from obtaining private information by using blockchain.\n\nBlockchain: The Introduction\n\nWhat exactly is a blockchain? A blockchain is a secure technology that uses a distributed database instead of locating, storing, and maintaining data in a single location. It’s decentralized database capability allows for addressing security concerns raised by numerous password confirmation tools available today. If a hardware failure occurs on a centralized database, it may cause all the data to be lost. This doesn’t happen to a distributed database, which makes it a very secure way to store sensitive information.\n\nBy design, blockchains are resistant to data modification. Once the data is recorded, it cannot be altered. This makes them an efficient tool for recording transactions between two parties in a verifiable and permanent way.\nBlockchain features guarantee users secure passwords and take into account the important role of human nature in creating passwords. However, only a few companies use its potential to tackle the subject of password-related issues.\n\nCyber Crime Trend\n\nIn 2016, the attack on Yahoo! lead to around one billion Yahoo user accounts being compromised. Cybercriminals were able to obtain names, passwords and other personal details, such as telephone numbers and answers to security questions. Sadly, this wasn’t the first hacker attack on Yahoo! Afterward, loads of DIY-guides on how to hack a Yahoo!-account were posted and are still online.\n\nThe findings of security companies only confirm this unfortunate trend. In 2016, Verizon reported that 65% of confirmed data breaches involve weak, default or stolen passwords. It’s much less then compared to the 95% in 2015, but still, the company states that the real problem, which accounts for 90% of all security incidents, are people. Numerous users fall for phishing attacks, attempts to obtain sensitive information such as usernames, passwords, and credit card details disguised as credible requests. According to Verizon, 23% of people open phishing emails, half of them even open attachments.\n\nAt this time, global level of cyber attacks is far greater than the number of tools to fight them effectively. Reports show that cyber crime is a growth industry that costs the global economy about $400 billion annually. Over 70% of organizations have increased their spending on cyber security in 2017, as opposed to just 58% the previous year.\n\nPassword Problems\n\nAnnually, billions of dollars are spent on cyber security, as even the slightest breach can have disastrous consequences. The number of services that are supposed to minimize the danger of being hacked grows, including browsers remembering password or password managers like 1Password and LastPass. However, they only delivered minor improvements without changing the nature of the problem.\n\nA larger problem, is the centralized architecture of the database storing logins and passwords on a server. Which means, if it’s been hacked, all data can be accessed at once. Unfortunately, even Two Factor Authentication (2FA) has been proven to be penetrable through social engineering. This is especially true with data delivered via SMS, as hackers can access user data through a user’s login phone number, that can then be provided by the phone company.\n\nREMME’s Proposal\n\nThe goal of the REMME high-end secure system is to build a distributed Public Key Infrastructure (“PKI”) management on top of the x.509 standard using Blockchain that will help IoT, financial, infrastructure, medtech and blockchain companies address the problem of security failings.\n\nA PKI is a set of roles, policies, and procedures that are necessary to create and manage digital certificates and public-key encryption. It’s being used to secure the electronic transfer of information in e-commerce, online banking, and confidential correspondence. This way, passwords and human error are eliminated to provide a high-end secure system, that is easy to use without compromising security.\n\nREMME solves the problem of central servers that can be hacked, as well as preventing attacks, such as phishing, server and password breach, and password reuse attacks.\n\nWe believe that blockchain will help build a safer future and offers a solution that potentially can prevent terrorist attacks or stop hackers from overriding election software in one candidate’s favor.\n\nhttps://www.youtube.com/watch?v=9APHeHRmrGw\n\nHow Does It Work\n\nThe REMME technology has TLS/SSL certificates that protect the channel from an attack such as the “man in the middle”, where the attacker secretly alters the communication between two parties without them noticing. The technology allows to validate certificate without the certification authority creating trusted p2p TLS connection. Certification authority is replaced by Blockchain.\n\nREMME allows companies to issue and revoke their own self signed certificates. The certificate is releasing with the email address and phone number of a user. Then server checks the certificate’s signature and generates a random number. Company generates certificate locally and then installs it to a certificate store on a local machine, where it stores encrypted with some secret phrase. The certificate uses api from certificate store on a local machine to interact with private keys, which adds an additional layer of security in comparison with other account protection technologies.\n\nIn addition, REMME provides 2FA based on the app a user already has. Instead of traditional text messages and OTP codes, users get an authentication token sent via the messenger apps (like Telegram, Facebook Messanger, WeChat) of their choice.\n\nWhy Is It Important?\n\nWith all that said, is there a way to fix the problems companies like LinkedIn or Yahoo! have been plagued with? We can only learn from the mistakes of the others to make the world a better place. We depend on technology to prevent hacker attacks and misuse of information. Which is why REMME has developed a technology that helps us make the first step towards protecting our personal data; keeping private and business conversations, payments, financial and medical records safe.",
      "title": "Keep your information safe with Blockchain technology",
      "author": "mamont",
      "permlink": "keep-your-information-safe-with-blockchain-technology",
      "json_metadata": "{\"tags\":[\"cybersecurity\",\"blockchain\",\"remme\",\"identity\",\"passwords\"],\"image\":[\"https://steemitimages.com/DQmaUHmYTrE4UzSoKyLVaz1pu4HHgTY8wBuyWFxB3mrCJdg/1-j3iIpKepFTzq6QBSdDG0-Q.png\",\"https://img.youtube.com/vi/9APHeHRmrGw/0.jpg\"],\"links\":[\"https://www.youtube.com/watch?v=9APHeHRmrGw\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "cybersecurity"
    }
  ],
  "block": 13168030,
  "trx_id": "f9bb7dd7ad0416aafe641bf093f965c2fc4abed5",
  "op_in_trx": 0,
  "timestamp": "2017-06-26T20:27:48",
  "virtual_op": false,
  "trx_in_block": 3
}

{
  "op": [
    "vote",
    {
      "voter": "seoirse",
      "author": "mamont",
      "weight": 10000,
      "permlink": "besparolnaya-avtorizaciya-cherez-blokchein"
    }
  ],
  "block": 12977753,
  "trx_id": "d1b676a06dabfb4efe7105da7bcaa8d197ae55bb",
  "op_in_trx": 0,
  "timestamp": "2017-06-20T05:38:24",
  "virtual_op": false,
  "trx_in_block": 7
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"mamont\",\"following\":\"trogdor\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "mamont"
      ]
    }
  ],
  "block": 12521657,
  "trx_id": "343c9b51556611d1e8dae4d9654ec6a779fe8c23",
  "op_in_trx": 0,
  "timestamp": "2017-06-04T09:15:27",
  "virtual_op": false,
  "trx_in_block": 2
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "trogdor",
      "weight": 10000,
      "permlink": "introduction-to-eos-the-epic-blockchain-operating-system"
    }
  ],
  "block": 12521645,
  "trx_id": "77102f3afd2038db38bfcf4fb44973c87279dc1e",
  "op_in_trx": 0,
  "timestamp": "2017-06-04T09:14:51",
  "virtual_op": false,
  "trx_in_block": 5
}

{
  "op": [
    "comment_payout_update",
    {
      "author": "mamont",
      "permlink": "re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z"
    }
  ],
  "block": 6466973,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 5,
  "timestamp": "2016-11-05T20:19:00",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "lehard",
      "weight": 10000,
      "permlink": "moi-30-dnevnyi-stimit-eksperiment-otchyot-spustya-12-dnei-cel-vypolnena-na-44"
    }
  ],
  "block": 6426696,
  "trx_id": "8133ad8fa8e7bb2fca5e5033e6b539b6651f482f",
  "op_in_trx": 0,
  "timestamp": "2016-11-04T10:44:30",
  "virtual_op": false,
  "trx_in_block": 0
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"mamont\",\"following\":\"lehard\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "mamont"
      ]
    }
  ],
  "block": 6426590,
  "trx_id": "0d750b88f78df5f6fc4970bf20dd100fe130e295",
  "op_in_trx": 0,
  "timestamp": "2016-11-04T10:39:12",
  "virtual_op": false,
  "trx_in_block": 0
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "infinity108",
      "author": "mamont",
      "weight": 0,
      "rshares": -129344327,
      "permlink": "re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z",
      "pending_payout": "0.000 HBD",
      "total_vote_weight": 0
    }
  ],
  "block": 5626680,
  "trx_id": "6e966f6342a65068d0c062d93169b56583c3c80d",
  "op_in_trx": 1,
  "timestamp": "2016-10-07T15:26:21",
  "virtual_op": true,
  "trx_in_block": 5
}