VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS77.81%
Net Worth
7.605USD
STEEM
3.136STEEM
SBD
0.207SBD
Own SP
126.280SP
Detailed Balance
| STEEM | ||
| balance | 3.136STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 126.280SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 126.280SP | SP |
| Reward SP (pending) | 0.140SP | SP |
| SBD | ||
| sbd_balance | 0.001SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.206SBD | SBD |
{
"balance": "3.136 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "205390.498149 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.001 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.206 SBD",
"conversions": []
}Account Info
| name | mamont |
| id | 16458 |
| rank | 15,186 |
| reputation | 94482084485 |
| created | 2016-07-10T23:38:09 |
| recovery_account | steem |
| proxy | None |
| post_count | 12 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2017-07-31T23:35:42 |
| last_root_post | 2017-07-31T23:35:42 |
| last_vote_time | 2019-10-22T21:41:45 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,799 |
| delayed_votes | 0 |
| balance | 3.136 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.001 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 205390.498149 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 0.000000 VESTS |
| reward_vesting_balance | 289.464034 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 4,750,258,143 |
| sbd_last_interest_payment | 2016-07-18T23:58:54 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 16458,
"name": "mamont",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM77wBJPpuro3z56qbnMqtzJ5xjN23zusebGoK6yQr6bJBYeC43V",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6MyRjswpSDkpcrbTmEebuLRpdfhoS2yooxiGVSaQUZahDKQvsp",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6W4GcqazvfQmWUUNrFLamTexGe2LLAxAVcjQYcR8FkEK2AyUGu",
1
]
]
},
"memo_key": "STM8EcDjDWYNxUdBn4X2ozyUd2wRHExFvbp48TFSnwKff4tmFFeo6",
"json_metadata": "",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2016-07-10T23:38:09",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 12,
"can_vote": true,
"voting_manabar": {
"current_mana": "201282688186",
"last_update_time": 1571780505
},
"downvote_manabar": {
"current_mana": "51347624537",
"last_update_time": 1571780505
},
"voting_power": 9799,
"balance": "3.136 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.001 SBD",
"sbd_seconds": "4750258143",
"sbd_seconds_last_update": "2016-08-11T10:53:42",
"sbd_last_interest_payment": "2016-07-18T23:58:54",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.206 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "289.464034 VESTS",
"reward_vesting_steem": "0.140 STEEM",
"vesting_shares": "205390.498149 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 14,
"posting_rewards": 7370,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2017-07-31T23:35:42",
"last_root_post": "2017-07-31T23:35:42",
"last_vote_time": "2019-10-22T21:41:45",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": "94482084485",
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 15186
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
mamontreceived 0.001 SP curation reward for @daan / instantly-exchange-crypto-at-the-best-market-rates-with-swapy2019/10/25 11:23:00
mamontreceived 0.001 SP curation reward for @daan / instantly-exchange-crypto-at-the-best-market-rates-with-swapy
2019/10/25 11:23:00
| comment author | daan |
| comment permlink | instantly-exchange-crypto-at-the-best-market-rates-with-swapy |
| curator | mamont |
| reward | 1.975351 VESTS |
| Transaction Info | Block #37591232/Virtual Operation #70 |
View Raw JSON Data
{
"block": 37591232,
"op": [
"curation_reward",
{
"comment_author": "daan",
"comment_permlink": "instantly-exchange-crypto-at-the-best-market-rates-with-swapy",
"curator": "mamont",
"reward": "1.975351 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-10-25T11:23:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 70
}mamontupvoted (100.00%) @daan / instantly-exchange-crypto-at-the-best-market-rates-with-swapy2019/10/22 21:41:45
mamontupvoted (100.00%) @daan / instantly-exchange-crypto-at-the-best-market-rates-with-swapy
2019/10/22 21:41:45
| author | daan |
| permlink | instantly-exchange-crypto-at-the-best-market-rates-with-swapy |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #37517352/Trx b710deeac38d7e04f54ef9a12bc879c4e1bab143 |
View Raw JSON Data
{
"block": 37517352,
"op": [
"vote",
{
"author": "daan",
"permlink": "instantly-exchange-crypto-at-the-best-market-rates-with-swapy",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-10-22T21:41:45",
"trx_id": "b710deeac38d7e04f54ef9a12bc879c4e1bab143",
"trx_in_block": 5,
"virtual_op": 0
}2019/07/11 01:08:42
2019/07/11 01:08:42
| author | steemitboard |
| body | Congratulations @mamont! You received a personal award! <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> <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> ###### [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! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | mamont |
| parent permlink | remme-technical-white-paper |
| permlink | steemitboard-notify-mamont-20190711t010841000z |
| title | |
| Transaction Info | Block #34554919/Trx 60c52a1ae74297a879db98da077ddb9cbec7de88 |
View Raw JSON Data
{
"block": 34554919,
"op": [
"comment",
{
"author": "steemitboard",
"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!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "mamont",
"parent_permlink": "remme-technical-white-paper",
"permlink": "steemitboard-notify-mamont-20190711t010841000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-07-11T01:08:42",
"trx_id": "60c52a1ae74297a879db98da077ddb9cbec7de88",
"trx_in_block": 5,
"virtual_op": 0
}2018/07/11 01:27:39
2018/07/11 01:27:39
| author | steemitboard |
| body | Congratulations @mamont! You have received a personal award! [](http://steemitboard.com/@mamont) 2 Years on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** [SteemitBoard World Cup Contest - Croatia vs England](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-croatia-vs-england) --- **Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!** Collect World Cup badges and win free SBD Support 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) --- > 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**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | mamont |
| parent permlink | remme-technical-white-paper |
| permlink | steemitboard-notify-mamont-20180711t012739000z |
| title | |
| Transaction Info | Block #24068823/Trx 9d407b616932518e8dad86b6e031e205ddaa4ccc |
View Raw JSON Data
{
"block": 24068823,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @mamont! You have received a personal award!\n\n[](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**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "mamont",
"parent_permlink": "remme-technical-white-paper",
"permlink": "steemitboard-notify-mamont-20180711t012739000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-07-11T01:27:39",
"trx_id": "9d407b616932518e8dad86b6e031e205ddaa4ccc",
"trx_in_block": 2,
"virtual_op": 0
}2018/06/09 14:03:24
2018/06/09 14:03:24
| author | freedomcoin |
| permlink | bitcointalks-merit-system-showing-some-love-to-my-recent-favorite-altcoins |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23173031/Trx c64fcc7a277b59995639a98689cef80c59ce4d35 |
View Raw JSON Data
{
"block": 23173031,
"op": [
"vote",
{
"author": "freedomcoin",
"permlink": "bitcointalks-merit-system-showing-some-love-to-my-recent-favorite-altcoins",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-06-09T14:03:24",
"trx_id": "c64fcc7a277b59995639a98689cef80c59ce4d35",
"trx_in_block": 62,
"virtual_op": 0
}mamontupvoted (100.00%) @jamshedalam / kjr3qtqo2018/02/02 19:20:24
mamontupvoted (100.00%) @jamshedalam / kjr3qtqo
2018/02/02 19:20:24
| author | jamshedalam |
| permlink | kjr3qtqo |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19525503/Trx 875764a5059582a126036c19f773d533203d2293 |
View Raw JSON Data
{
"block": 19525503,
"op": [
"vote",
{
"author": "jamshedalam",
"permlink": "kjr3qtqo",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-02-02T19:20:24",
"trx_id": "875764a5059582a126036c19f773d533203d2293",
"trx_in_block": 37,
"virtual_op": 0
}mamontupvoted (100.00%) @flodner / aleks-momot-ceo-remme-pro-ico2018/01/09 00:34:06
mamontupvoted (100.00%) @flodner / aleks-momot-ceo-remme-pro-ico
2018/01/09 00:34:06
| author | flodner |
| permlink | aleks-momot-ceo-remme-pro-ico |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18812293/Trx 543a06580edb8d28f0b498e0d4016fb0f3e3d841 |
View Raw JSON Data
{
"block": 18812293,
"op": [
"vote",
{
"author": "flodner",
"permlink": "aleks-momot-ceo-remme-pro-ico",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-01-09T00:34:06",
"trx_id": "543a06580edb8d28f0b498e0d4016fb0f3e3d841",
"trx_in_block": 42,
"virtual_op": 0
}2017/11/25 03:30:45
2017/11/25 03:30:45
| author | mamont |
| permlink | re-bittrex-richie-a-little-history-of-bittrex-com-how-it-all-started-20160713t192158667z |
| voter | gsm |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17520636/Trx 551b2928e2c2d89bea4cb227788aa04f44909b6a |
View Raw JSON Data
{
"block": 17520636,
"op": [
"vote",
{
"author": "mamont",
"permlink": "re-bittrex-richie-a-little-history-of-bittrex-com-how-it-all-started-20160713t192158667z",
"voter": "gsm",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-25T03:30:45",
"trx_id": "551b2928e2c2d89bea4cb227788aa04f44909b6a",
"trx_in_block": 19,
"virtual_op": 0
}2017/10/31 20:43:27
2017/10/31 20:43:27
| author | remme |
| permlink | how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16821623/Trx 00ad385017f7c87ef414d5033c011e6da8c22bc1 |
View Raw JSON Data
{
"block": 16821623,
"op": [
"vote",
{
"author": "remme",
"permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-31T20:43:27",
"trx_id": "00ad385017f7c87ef414d5033c011e6da8c22bc1",
"trx_in_block": 0,
"virtual_op": 0
}mamontcustom json: follow2017/10/29 19:16:54
mamontcustom json: follow
2017/10/29 19:16:54
| id | follow |
| json | ["reblog",{"account":"mamont","author":"remme","permlink":"remme-using-blockchain-for-access-management-and-distributed-authentication"}] |
| required auths | [] |
| required posting auths | ["mamont"] |
| Transaction Info | Block #16762298/Trx 7767c141106e70b1cd7434da9ccd086724284b65 |
View Raw JSON Data
{
"block": 16762298,
"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"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T19:16:54",
"trx_id": "7767c141106e70b1cd7434da9ccd086724284b65",
"trx_in_block": 6,
"virtual_op": 0
}2017/10/29 19:15:30
2017/10/29 19:15:30
| id | follow |
| json | ["follow",{"follower":"mamont","following":"remme","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mamont"] |
| Transaction Info | Block #16762270/Trx 8e70bb56eb8066c7e5eee7616aecd1415a9e6bda |
View Raw JSON Data
{
"block": 16762270,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mamont\",\"following\":\"remme\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mamont"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T19:15:30",
"trx_id": "8e70bb56eb8066c7e5eee7616aecd1415a9e6bda",
"trx_in_block": 16,
"virtual_op": 0
}2017/10/29 19:14:24
2017/10/29 19:14:24
| author | remme |
| permlink | remme-using-blockchain-for-access-management-and-distributed-authentication |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16762248/Trx 09531c161b1da2a0ed7df8611946402aafb56c81 |
View Raw JSON Data
{
"block": 16762248,
"op": [
"vote",
{
"author": "remme",
"permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T19:14:24",
"trx_id": "09531c161b1da2a0ed7df8611946402aafb56c81",
"trx_in_block": 25,
"virtual_op": 0
}remmeupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology2017/10/29 19:04:12
remmeupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology
2017/10/29 19:04:12
| author | mamont |
| permlink | keep-your-information-safe-with-blockchain-technology |
| voter | remme |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16762044/Trx 928fc801e27bfe1488cc910cda1a4d2935966b84 |
View Raw JSON Data
{
"block": 16762044,
"op": [
"vote",
{
"author": "mamont",
"permlink": "keep-your-information-safe-with-blockchain-technology",
"voter": "remme",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T19:04:12",
"trx_id": "928fc801e27bfe1488cc910cda1a4d2935966b84",
"trx_in_block": 25,
"virtual_op": 0
}remmeupvoted (100.00%) @mamont / the-hackathon-we-won2017/10/29 19:04:03
remmeupvoted (100.00%) @mamont / the-hackathon-we-won
2017/10/29 19:04:03
| author | mamont |
| permlink | the-hackathon-we-won |
| voter | remme |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16762041/Trx 8c1002af786077b70368af6e97988d04bc5a550c |
View Raw JSON Data
{
"block": 16762041,
"op": [
"vote",
{
"author": "mamont",
"permlink": "the-hackathon-we-won",
"voter": "remme",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T19:04:03",
"trx_id": "8c1002af786077b70368af6e97988d04bc5a550c",
"trx_in_block": 1,
"virtual_op": 0
}remmeupvoted (100.00%) @mamont / remme-technical-white-paper2017/10/29 19:02:36
remmeupvoted (100.00%) @mamont / remme-technical-white-paper
2017/10/29 19:02:36
| author | mamont |
| permlink | remme-technical-white-paper |
| voter | remme |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16762012/Trx 66baadccee5177e3e940a934a9d9db78711ad109 |
View Raw JSON Data
{
"block": 16762012,
"op": [
"vote",
{
"author": "mamont",
"permlink": "remme-technical-white-paper",
"voter": "remme",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T19:02:36",
"trx_id": "66baadccee5177e3e940a934a9d9db78711ad109",
"trx_in_block": 15,
"virtual_op": 0
}remmeupvoted (100.00%) @mamont / hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine2017/10/29 19:01:48
remmeupvoted (100.00%) @mamont / hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine
2017/10/29 19:01:48
| author | mamont |
| permlink | hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine |
| voter | remme |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16761996/Trx 9687d25c06cf403d7b56b70c340d24fb1a9cc62d |
View Raw JSON Data
{
"block": 16761996,
"op": [
"vote",
{
"author": "mamont",
"permlink": "hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine",
"voter": "remme",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T19:01:48",
"trx_id": "9687d25c06cf403d7b56b70c340d24fb1a9cc62d",
"trx_in_block": 24,
"virtual_op": 0
}mamontupvoted (100.00%) @crypto.girl / salt-ico-today2017/10/18 13:24:30
mamontupvoted (100.00%) @crypto.girl / salt-ico-today
2017/10/18 13:24:30
| author | crypto.girl |
| permlink | salt-ico-today |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16438633/Trx a804b9edc40eced0d53418bbfb384db8da0e4f3e |
View Raw JSON Data
{
"block": 16438633,
"op": [
"vote",
{
"author": "crypto.girl",
"permlink": "salt-ico-today",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-18T13:24:30",
"trx_id": "a804b9edc40eced0d53418bbfb384db8da0e4f3e",
"trx_in_block": 19,
"virtual_op": 0
}2017/09/22 12:46:09
2017/09/22 12:46:09
| author | kimberlee17 |
| 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. |
| json metadata | {"tags":["cybersecurity"],"links":["https://www.coincheckup.com"],"app":"steemit/0.1"} |
| parent author | mamont |
| parent permlink | remme-technical-white-paper |
| permlink | re-mamont-remme-technical-white-paper-20170922t124610728z |
| title | |
| Transaction Info | Block #15689862/Trx 0e04bb9901798150f3d44bfdff1bca1cdc8bd7af |
View Raw JSON Data
{
"block": 15689862,
"op": [
"comment",
{
"author": "kimberlee17",
"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.",
"json_metadata": "{\"tags\":[\"cybersecurity\"],\"links\":[\"https://www.coincheckup.com\"],\"app\":\"steemit/0.1\"}",
"parent_author": "mamont",
"parent_permlink": "remme-technical-white-paper",
"permlink": "re-mamont-remme-technical-white-paper-20170922t124610728z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-09-22T12:46:09",
"trx_id": "0e04bb9901798150f3d44bfdff1bca1cdc8bd7af",
"trx_in_block": 1,
"virtual_op": 0
}naveen.tejaupvoted (100.00%) @mamont / remme-technical-white-paper2017/08/23 17:07:39
naveen.tejaupvoted (100.00%) @mamont / remme-technical-white-paper
2017/08/23 17:07:39
| author | mamont |
| permlink | remme-technical-white-paper |
| voter | naveen.teja |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14831525/Trx eedbf18712f77a2ce1bd934514bd2a6a8939787c |
View Raw JSON Data
{
"block": 14831525,
"op": [
"vote",
{
"author": "mamont",
"permlink": "remme-technical-white-paper",
"voter": "naveen.teja",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-23T17:07:39",
"trx_id": "eedbf18712f77a2ce1bd934514bd2a6a8939787c",
"trx_in_block": 33,
"virtual_op": 0
}flodnerupvoted (100.00%) @mamont / the-hackathon-we-won2017/08/18 10:02:18
flodnerupvoted (100.00%) @mamont / the-hackathon-we-won
2017/08/18 10:02:18
| author | mamont |
| permlink | the-hackathon-we-won |
| voter | flodner |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14679055/Trx 546558cca926ad51400aa4e4ffd789c12fd82676 |
View Raw JSON Data
{
"block": 14679055,
"op": [
"vote",
{
"author": "mamont",
"permlink": "the-hackathon-we-won",
"voter": "flodner",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-18T10:02:18",
"trx_id": "546558cca926ad51400aa4e4ffd789c12fd82676",
"trx_in_block": 13,
"virtual_op": 0
}flodnerupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology2017/08/18 10:01:54
flodnerupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology
2017/08/18 10:01:54
| author | mamont |
| permlink | keep-your-information-safe-with-blockchain-technology |
| voter | flodner |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14679047/Trx 623ee7608e823adcc47a708b91e28004d2bdd089 |
View Raw JSON Data
{
"block": 14679047,
"op": [
"vote",
{
"author": "mamont",
"permlink": "keep-your-information-safe-with-blockchain-technology",
"voter": "flodner",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-18T10:01:54",
"trx_id": "623ee7608e823adcc47a708b91e28004d2bdd089",
"trx_in_block": 4,
"virtual_op": 0
}flodnerupvoted (100.00%) @mamont / hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine2017/08/18 10:01:12
flodnerupvoted (100.00%) @mamont / hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine
2017/08/18 10:01:12
| author | mamont |
| permlink | hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine |
| voter | flodner |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14679033/Trx ba20084beef4e552c807b7165dd3817a4369c758 |
View Raw JSON Data
{
"block": 14679033,
"op": [
"vote",
{
"author": "mamont",
"permlink": "hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine",
"voter": "flodner",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-18T10:01:12",
"trx_id": "ba20084beef4e552c807b7165dd3817a4369c758",
"trx_in_block": 0,
"virtual_op": 0
}flodnerupvoted (100.00%) @mamont / first-blockchain-wedding-in-ukraine2017/08/18 10:01:03
flodnerupvoted (100.00%) @mamont / first-blockchain-wedding-in-ukraine
2017/08/18 10:01:03
| author | mamont |
| permlink | first-blockchain-wedding-in-ukraine |
| voter | flodner |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14679030/Trx bb0ad14568ce8b218407fe1315b85c65fe589354 |
View Raw JSON Data
{
"block": 14679030,
"op": [
"vote",
{
"author": "mamont",
"permlink": "first-blockchain-wedding-in-ukraine",
"voter": "flodner",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-18T10:01:03",
"trx_id": "bb0ad14568ce8b218407fe1315b85c65fe589354",
"trx_in_block": 8,
"virtual_op": 0
}flodnerupvoted (100.00%) @mamont / remme-technical-white-paper2017/08/18 10:00:42
flodnerupvoted (100.00%) @mamont / remme-technical-white-paper
2017/08/18 10:00:42
| author | mamont |
| permlink | remme-technical-white-paper |
| voter | flodner |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14679023/Trx 3aef5a0d69d6db9394db9b5458859f1f05afb70d |
View Raw JSON Data
{
"block": 14679023,
"op": [
"vote",
{
"author": "mamont",
"permlink": "remme-technical-white-paper",
"voter": "flodner",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-18T10:00:42",
"trx_id": "3aef5a0d69d6db9394db9b5458859f1f05afb70d",
"trx_in_block": 13,
"virtual_op": 0
}voloshynupvoted (100.00%) @mamont / the-hackathon-we-won2017/08/18 09:59:24
voloshynupvoted (100.00%) @mamont / the-hackathon-we-won
2017/08/18 09:59:24
| author | mamont |
| permlink | the-hackathon-we-won |
| voter | voloshyn |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14678997/Trx 5143ec031a6e84349cbc2a5ae93e598df46aea2e |
View Raw JSON Data
{
"block": 14678997,
"op": [
"vote",
{
"author": "mamont",
"permlink": "the-hackathon-we-won",
"voter": "voloshyn",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-18T09:59:24",
"trx_id": "5143ec031a6e84349cbc2a5ae93e598df46aea2e",
"trx_in_block": 2,
"virtual_op": 0
}pandoraboxchainupvoted (100.00%) @mamont / remme-technical-white-paper2017/08/01 22:31:15
pandoraboxchainupvoted (100.00%) @mamont / remme-technical-white-paper
2017/08/01 22:31:15
| author | mamont |
| permlink | remme-technical-white-paper |
| voter | pandoraboxchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14205739/Trx 3c6359fed7ea1a29c1ce8dc98db600136a136426 |
View Raw JSON Data
{
"block": 14205739,
"op": [
"vote",
{
"author": "mamont",
"permlink": "remme-technical-white-paper",
"voter": "pandoraboxchain",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T22:31:15",
"trx_id": "3c6359fed7ea1a29c1ce8dc98db600136a136426",
"trx_in_block": 32,
"virtual_op": 0
}bicalabsupvoted (100.00%) @mamont / remme-technical-white-paper2017/08/01 22:30:42
bicalabsupvoted (100.00%) @mamont / remme-technical-white-paper
2017/08/01 22:30:42
| author | mamont |
| permlink | remme-technical-white-paper |
| voter | bicalabs |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14205728/Trx 76a6673001f74cda40f26a1e47deb358026733af |
View Raw JSON Data
{
"block": 14205728,
"op": [
"vote",
{
"author": "mamont",
"permlink": "remme-technical-white-paper",
"voter": "bicalabs",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T22:30:42",
"trx_id": "76a6673001f74cda40f26a1e47deb358026733af",
"trx_in_block": 13,
"virtual_op": 0
}mamontpublished a new post: remme-technical-white-paper2017/07/31 23:35:42
mamontpublished a new post: remme-technical-white-paper
2017/07/31 23:35:42
| author | mamont |
| body | We are pleased to announce our current technical white paper. We welcome everyone to provide feedback and improve document. Let`s start discussion and make it better together. # White paper **(v.0.1)** **July 30, 2017** ## Contents **Background** **REMME’s Edge** **How REMME works** **Use of multi-factor authentication** **Conclusion** **Links** **Background** The 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. A 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. The 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. REMME will use the blockchain technology as a vehicle of transportation and a source of consensus to offer a solution to this problem: decentralization. **REMME’s Edge** Though 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. While 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. REMME 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] **How REMME works** In 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. REMME 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. The 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. The four basic types of REMME certificates are determined according to the signature of the publisher: 1. Self-signed certificates; 2. Certificates signed by the organization; 3. Certificates signed by the certifying center REMME; 4. Certificates signed by an official certifying center The 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. This 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. Bitcoin addresses are identifiers that are used to send bitcoins from one person to another. The REMME technology provides: - the ability to associate a bitcoin address with a certificate; - the ability to organize a decentralized system for revocation of certificates. The 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. CertStatus ::= CHOICE { good [0] IMPLICIT NULL, revoked [1] IMPLICIT RevokedInfo, unknown [2] IMPLICIT UnknownInfo } RevokedInfo ::= SEQUENCE { revocationTime GeneralizedTime, revocationReason [0] EXPLICIT CRLReason OPTIONAL } In the certificate, it is necessary to save: ● Signature by private address key ● Hash of revoke transaction {txOutHash} ● Exit number of the revocation transaction {txOutNumber} 1. The first type is a self-signed certificate in which accessLocation [8] from OCSP [9] has a special format. AccessDescription ::= SEQUENCE { accessMethod OBJECT IDENTIFIER, accessLocation GeneralName } http://ocsp.REMME.io/{$txOutHash}/{$txOutNumber}/ This 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. 2. For 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. 3. The 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. 4. The 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. Though 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. The 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: CN: CommonName OU: OrganizationalUnit O: Organization L: Locality S: StateOrProvinceName C: CountryName Example of subject: CN=Sample Cert, OU=R&D, O=Company Ltd., L=Dublin 4, S=Dublin,C=IE In the case of the fourth type of certificate, fields will be filled with special values: O=Bitcoin UID=12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX (Bitcoin address) OU=0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd51298 (A transaction hash that marks a revoke of certificate) ST=0 (transaction output number) L=Hy15Vc5HFHisgkB5sUiithUC6i0uPETcVBVYHHpMQePbTK6ZNwOombXS+I/PnouqYrkmV7H4Wl6egIyQuJc70Xs=(Signature by private address key) All other values are set according to the needs of the CA. The signature for all types of the certificate is formed by signing a special format message with a private address key. Sign ("http://REMME.io/certificate/" + Certificate serial number + "/" + Public key hash + "/" + Revocation transaction hash + "/" + Revocation transaction number) The 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: gettxout 0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098 0 { "bestblock" : "000000000000000000ff4c920d339f7211125f01957ac6d42a876162025764f9", "confirmations" : 462282, "value" : 50.00000000, "scriptPubKey" : { "asm" : "0496b538e853519c726a2c91e61ec11600ae1390813a627c66fb8be7947be63c52da7589379515d4e 0a604f8141781e62294721166bf621e73a82cbf2342c858ee OP_CHECKSIG", "hex" : "410496b538e853519c726a2c91e61ec11600ae1390813a627c66fb8be7947be63c52da7589379515d 4e0a604f8141781e62294721166bf621e73a82cbf2342c858eeac", "reqSigs" : 1, "type" : "pubkey", "addresses" : [ "12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX" ] }, "version" : 1, "coinbase" : true } In 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. Scenario for client authentication: 1. Check certificate. 2. Check signature of the certificate. 3. Check that the certificate data is signed with the private key of blockchain account. 4. Find 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. **Use of multi-factor authentication** The 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. E.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. The 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. For 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] If the system uses some local sensor, then the second factor would be the physical connection to the local network check. If 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. One 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. Special 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]. **Conclusion** The 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. REMME 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. The 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. During 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. **Links** 1. https://www.rfc-editor.org/rfc/rfc5912.txt 2. https://namecoin.org/ 3. http://emercoin.com/EMCSSL 4. https://www.ietf.org/rfc/rfc3820.txt 5. https://tools.ietf.org/html/rfc5280 6. https://en.wikipedia.org/wiki/Warrant_canary 7. https://tools.ietf.org/html/rfc6960 8. https://tools.ietf.org/html/rfc5280#section-4.2.2.1 9. https://tools.ietf.org/html/rfc6960 10. https://www.miracl.com/miracl-labs/m-pin-a-multi-factor-zero-knowledge-authentication-protocol 11. http://www.cse.lehigh.edu/prr/Biometrics/Archive/Papers/Uludag05.pdf 12. https://www.google.com/intl/ru/landing/2step/features.html 13. https://www.yubico.com/products/yubikey-hardware/ 14. https://trezor.io/ |
| 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 |
| permlink | remme-technical-white-paper |
| title | REMME Technical White Paper |
| Transaction Info | Block #14178255/Trx fe22ccee517308b1a1e2b40f5e6e634b3379fdc3 |
View Raw JSON Data
{
"block": 14178255,
"op": [
"comment",
{
"author": "mamont",
"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/",
"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",
"permlink": "remme-technical-white-paper",
"title": "REMME Technical White Paper"
}
],
"op_in_trx": 0,
"timestamp": "2017-07-31T23:35:42",
"trx_id": "fe22ccee517308b1a1e2b40f5e6e634b3379fdc3",
"trx_in_block": 8,
"virtual_op": 0
}mamontreceived 0.008 SP curation reward for @hipster / updates-satoshi-pie-ethereum-multisig-has-been-hacked2017/07/26 20:52:03
mamontreceived 0.008 SP curation reward for @hipster / updates-satoshi-pie-ethereum-multisig-has-been-hacked
2017/07/26 20:52:03
| comment author | hipster |
| comment permlink | updates-satoshi-pie-ethereum-multisig-has-been-hacked |
| curator | mamont |
| reward | 12.395957 VESTS |
| Transaction Info | Block #14031067/Virtual Operation #23 |
View Raw JSON Data
{
"block": 14031067,
"op": [
"curation_reward",
{
"comment_author": "hipster",
"comment_permlink": "updates-satoshi-pie-ethereum-multisig-has-been-hacked",
"curator": "mamont",
"reward": "12.395957 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-07-26T20:52:03",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 23
}mamontupvoted (100.00%) @hipster / updates-satoshi-pie-ethereum-multisig-has-been-hacked2017/07/19 21:44:12
mamontupvoted (100.00%) @hipster / updates-satoshi-pie-ethereum-multisig-has-been-hacked
2017/07/19 21:44:12
| author | hipster |
| permlink | updates-satoshi-pie-ethereum-multisig-has-been-hacked |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13830702/Trx 0b0ce876003b1c1bab3ea7b7b64cfc477e7b6056 |
View Raw JSON Data
{
"block": 13830702,
"op": [
"vote",
{
"author": "hipster",
"permlink": "updates-satoshi-pie-ethereum-multisig-has-been-hacked",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-07-19T21:44:12",
"trx_id": "0b0ce876003b1c1bab3ea7b7b64cfc477e7b6056",
"trx_in_block": 0,
"virtual_op": 0
}2017/07/11 00:20:54
2017/07/11 00:20:54
| author | steemitboard |
| body | Congratulations @mamont! You have received a personal award! [](http://steemitboard.com/@mamont) Happy Birthday - 1 Year Click on the badge to view your own Board of Honor on SteemitBoard. For more information about this award, click [here](https://steemit.com/steemitboard/@steemitboard/steemitboard-update-8-happy-birthday) > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| parent author | mamont |
| parent permlink | the-hackathon-we-won |
| permlink | steemitboard-notify-mamont-20170711t002056000z |
| title | |
| Transaction Info | Block #13574838/Trx 5a0d5750ad329618959cf72e0fc8d5aa474bd0c0 |
View Raw JSON Data
{
"block": 13574838,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @mamont! You have received a personal award!\n\n[](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)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}",
"parent_author": "mamont",
"parent_permlink": "the-hackathon-we-won",
"permlink": "steemitboard-notify-mamont-20170711t002056000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-07-11T00:20:54",
"trx_id": "5a0d5750ad329618959cf72e0fc8d5aa474bd0c0",
"trx_in_block": 17,
"virtual_op": 0
}mamontreceived 0.185 SBD, 0.145 SP author reward for @mamont / the-hackathon-we-won2017/07/05 13:30:15
mamontreceived 0.185 SBD, 0.145 SP author reward for @mamont / the-hackathon-we-won
2017/07/05 13:30:15
| author | mamont |
| permlink | the-hackathon-we-won |
| sbd payout | 0.185 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 235.790684 VESTS |
| Transaction Info | Block #13418443/Virtual Operation #4 |
View Raw JSON Data
{
"block": 13418443,
"op": [
"author_reward",
{
"author": "mamont",
"permlink": "the-hackathon-we-won",
"sbd_payout": "0.185 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "235.790684 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-07-05T13:30:15",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}mamontreceived 0.006 SP curation reward for @nebi / re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z2017/07/03 20:40:51
mamontreceived 0.006 SP curation reward for @nebi / re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z
2017/07/03 20:40:51
| comment author | nebi |
| comment permlink | re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z |
| curator | mamont |
| reward | 10.342639 VESTS |
| Transaction Info | Block #13369497/Virtual Operation #5 |
View Raw JSON Data
{
"block": 13369497,
"op": [
"curation_reward",
{
"comment_author": "nebi",
"comment_permlink": "re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z",
"curator": "mamont",
"reward": "10.342639 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-07-03T20:40:51",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 5
}mamontreceived 0.021 SBD, 0.018 SP author reward for @mamont / keep-your-information-safe-with-blockchain-technology2017/07/03 20:27:45
mamontreceived 0.021 SBD, 0.018 SP author reward for @mamont / keep-your-information-safe-with-blockchain-technology
2017/07/03 20:27:45
| author | mamont |
| permlink | keep-your-information-safe-with-blockchain-technology |
| sbd payout | 0.021 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 28.959403 VESTS |
| Transaction Info | Block #13369235/Virtual Operation #2 |
View Raw JSON Data
{
"block": 13369235,
"op": [
"author_reward",
{
"author": "mamont",
"permlink": "keep-your-information-safe-with-blockchain-technology",
"sbd_payout": "0.021 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "28.959403 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-07-03T20:27:45",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 2
}kumaranvplupvoted (100.00%) @mamont / the-hackathon-we-won2017/06/28 13:54:03
kumaranvplupvoted (100.00%) @mamont / the-hackathon-we-won
2017/06/28 13:54:03
| author | mamont |
| permlink | the-hackathon-we-won |
| voter | kumaranvpl |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13217495/Trx 2a2112bb9f7201e19efa012619710d21cf82ffdf |
View Raw JSON Data
{
"block": 13217495,
"op": [
"vote",
{
"author": "mamont",
"permlink": "the-hackathon-we-won",
"voter": "kumaranvpl",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-28T13:54:03",
"trx_id": "2a2112bb9f7201e19efa012619710d21cf82ffdf",
"trx_in_block": 11,
"virtual_op": 0
}cheetahreplied to @mamont / cheetah-re-mamontthe-hackathon-we-won2017/06/28 13:31:48
cheetahreplied to @mamont / cheetah-re-mamontthe-hackathon-we-won
2017/06/28 13:31:48
| author | cheetah |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://medium.com/remme/the-hackathon-we-won-5e9fe6a67189 |
| json metadata | |
| parent author | mamont |
| parent permlink | the-hackathon-we-won |
| permlink | cheetah-re-mamontthe-hackathon-we-won |
| title | |
| Transaction Info | Block #13217075/Trx 6ac43fe45bd8b95bb09816521da118d2ccd1dd95 |
View Raw JSON Data
{
"block": 13217075,
"op": [
"comment",
{
"author": "cheetah",
"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",
"json_metadata": "",
"parent_author": "mamont",
"parent_permlink": "the-hackathon-we-won",
"permlink": "cheetah-re-mamontthe-hackathon-we-won",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-06-28T13:31:48",
"trx_id": "6ac43fe45bd8b95bb09816521da118d2ccd1dd95",
"trx_in_block": 6,
"virtual_op": 0
}cheetahupvoted (1.00%) @mamont / the-hackathon-we-won2017/06/28 13:31:42
cheetahupvoted (1.00%) @mamont / the-hackathon-we-won
2017/06/28 13:31:42
| author | mamont |
| permlink | the-hackathon-we-won |
| voter | cheetah |
| weight | 100 (1.00%) |
| Transaction Info | Block #13217073/Trx 34401a26ce6ccf8b3d66777816109e022dd372dd |
View Raw JSON Data
{
"block": 13217073,
"op": [
"vote",
{
"author": "mamont",
"permlink": "the-hackathon-we-won",
"voter": "cheetah",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-06-28T13:31:42",
"trx_id": "34401a26ce6ccf8b3d66777816109e022dd372dd",
"trx_in_block": 6,
"virtual_op": 0
}sveoklaupvoted (100.00%) @mamont / the-hackathon-we-won2017/06/28 13:30:57
sveoklaupvoted (100.00%) @mamont / the-hackathon-we-won
2017/06/28 13:30:57
| author | mamont |
| permlink | the-hackathon-we-won |
| voter | sveokla |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13217059/Trx f56c516ace2a44cd14eeb10825c5ededfcff960e |
View Raw JSON Data
{
"block": 13217059,
"op": [
"vote",
{
"author": "mamont",
"permlink": "the-hackathon-we-won",
"voter": "sveokla",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-28T13:30:57",
"trx_id": "f56c516ace2a44cd14eeb10825c5ededfcff960e",
"trx_in_block": 49,
"virtual_op": 0
}mamontupvoted (100.00%) @mamont / the-hackathon-we-won2017/06/28 13:30:15
mamontupvoted (100.00%) @mamont / the-hackathon-we-won
2017/06/28 13:30:15
| author | mamont |
| permlink | the-hackathon-we-won |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13217046/Trx 807002114f2fda662870a95fa85700ca079fc1e6 |
View Raw JSON Data
{
"block": 13217046,
"op": [
"vote",
{
"author": "mamont",
"permlink": "the-hackathon-we-won",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-28T13:30:15",
"trx_id": "807002114f2fda662870a95fa85700ca079fc1e6",
"trx_in_block": 16,
"virtual_op": 0
}mamontpublished a new post: the-hackathon-we-won2017/06/28 13:30:15
mamontpublished a new post: the-hackathon-we-won
2017/06/28 13:30:15
| author | mamont |
| body | https://steemitimages.com/DQmbmC9KxLhLWQgpvLvbmj3XjnBVACajujNCSmt2BPJiS15/1-LPBwbl08mHBq-sbP9GyiDw.jpeg Just two weeks ago we returned from the Microsoft Blockchain Intensive, and we brought back some good news! First 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! On 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. For 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. https://steemitimages.com/DQmRZZMfqh19EFgAjPA6np9oNCpqzujQU89c1biQ6CvvEW2/1-jGDfNIyHYB3kQHVdxlmVBw.jpeg We 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! The Solution We 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? For 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. https://steemitimages.com/DQmfVk7mu1pdTRvg3PaEVE11CnJ5KiiSXj6us6UDqcyv9Fx/1-V6Z9Ewygg4vCsA_-08Hj5w.jpeg Our 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). Technology https://steemitimages.com/DQmZVBxYZ6oizTQ6Wm5oG3ZiwrgQMsGFBHbmZJX7QkNecXp/1-MRvLYcpchlDD4OLfSr3_oA.png The 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. The 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. Who can make use of it? Aside from municipal and state authorities, this solution is useful for: Insurance companies: Access to a car’s reliable telemetry data at the time of the accident and shortly before. Find out who is guilty based on this data. Instantly pay the insurance money to the victim (including in cryptocurrency) Car manufacturers: Objective vehicle data, including the one to analyse and improve its safety Analysis of the autopilot, its functions and malfunctions We 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. Sign-up on REMME news: https://www.remme.io REMME intro video: https://www.youtube.com/watch?v=9APHeHRmrGw, 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 |
| Transaction Info | Block #13169071/Trx 56ce7b04d88771329f727722256a5a21a3e4dcaa |
View Raw JSON Data
{
"block": 13169071,
"op": [
"vote",
{
"author": "nebi",
"permlink": "re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-26T21:19:54",
"trx_id": "56ce7b04d88771329f727722256a5a21a3e4dcaa",
"trx_in_block": 21,
"virtual_op": 0
}nebiupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology2017/06/26 20:40:54
nebiupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology
2017/06/26 20:40:54
| author | mamont |
| permlink | keep-your-information-safe-with-blockchain-technology |
| voter | nebi |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13168292/Trx d0211f502178169672c2fc39b2117acf27140300 |
View Raw JSON Data
{
"block": 13168292,
"op": [
"vote",
{
"author": "mamont",
"permlink": "keep-your-information-safe-with-blockchain-technology",
"voter": "nebi",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-26T20:40:54",
"trx_id": "d0211f502178169672c2fc39b2117acf27140300",
"trx_in_block": 22,
"virtual_op": 0
}2017/06/26 20:40:51
2017/06/26 20:40:51
| author | nebi |
| body | Interesting concept and proposal. Thanks for sharing. |
| json metadata | {"tags":["cybersecurity"],"app":"steemit/0.1"} |
| parent author | mamont |
| parent permlink | keep-your-information-safe-with-blockchain-technology |
| permlink | re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z |
| title | |
| Transaction Info | Block #13168291/Trx 45c1bd5a1b0cabc7f647716c4897c334c22da75e |
View Raw JSON Data
{
"block": 13168291,
"op": [
"comment",
{
"author": "nebi",
"body": "Interesting concept and proposal. Thanks for sharing.",
"json_metadata": "{\"tags\":[\"cybersecurity\"],\"app\":\"steemit/0.1\"}",
"parent_author": "mamont",
"parent_permlink": "keep-your-information-safe-with-blockchain-technology",
"permlink": "re-mamont-keep-your-information-safe-with-blockchain-technology-20170626t204050511z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-06-26T20:40:51",
"trx_id": "45c1bd5a1b0cabc7f647716c4897c334c22da75e",
"trx_in_block": 8,
"virtual_op": 0
}mohammedfelahiupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology2017/06/26 20:31:03
mohammedfelahiupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology
2017/06/26 20:31:03
| author | mamont |
| permlink | keep-your-information-safe-with-blockchain-technology |
| voter | mohammedfelahi |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13168096/Trx c0f9321207db2fd52f82e7166d12e00f0b056081 |
View Raw JSON Data
{
"block": 13168096,
"op": [
"vote",
{
"author": "mamont",
"permlink": "keep-your-information-safe-with-blockchain-technology",
"voter": "mohammedfelahi",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-26T20:31:03",
"trx_id": "c0f9321207db2fd52f82e7166d12e00f0b056081",
"trx_in_block": 7,
"virtual_op": 0
}mamontupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology2017/06/26 20:27:45
mamontupvoted (100.00%) @mamont / keep-your-information-safe-with-blockchain-technology
2017/06/26 20:27:45
| author | mamont |
| permlink | keep-your-information-safe-with-blockchain-technology |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13168030/Trx f9bb7dd7ad0416aafe641bf093f965c2fc4abed5 |
View Raw JSON Data
{
"block": 13168030,
"op": [
"vote",
{
"author": "mamont",
"permlink": "keep-your-information-safe-with-blockchain-technology",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-26T20:27:45",
"trx_id": "f9bb7dd7ad0416aafe641bf093f965c2fc4abed5",
"trx_in_block": 3,
"virtual_op": 0
}mamontpublished a new post: keep-your-information-safe-with-blockchain-technology2017/06/26 20:27:45
mamontpublished a new post: keep-your-information-safe-with-blockchain-technology
2017/06/26 20:27:45
| author | mamont |
| body |  Passwords 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. Blockchain: The Introduction What 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. By 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. Blockchain 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. Cyber Crime Trend In 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. The 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. At 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. Password Problems Annually, 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. A 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. REMME’s Proposal The 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. A 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. REMME 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. We 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. https://www.youtube.com/watch?v=9APHeHRmrGw How Does It Work The 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. REMME 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. In 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. Why Is It Important? With 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. |
| 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 |
| permlink | keep-your-information-safe-with-blockchain-technology |
| title | Keep your information safe with Blockchain technology |
| Transaction Info | Block #13168030/Trx f9bb7dd7ad0416aafe641bf093f965c2fc4abed5 |
View Raw JSON Data
{
"block": 13168030,
"op": [
"comment",
{
"author": "mamont",
"body": "\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.",
"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",
"permlink": "keep-your-information-safe-with-blockchain-technology",
"title": "Keep your information safe with Blockchain technology"
}
],
"op_in_trx": 0,
"timestamp": "2017-06-26T20:27:45",
"trx_id": "f9bb7dd7ad0416aafe641bf093f965c2fc4abed5",
"trx_in_block": 3,
"virtual_op": 0
}seoirseupvoted (100.00%) @mamont / besparolnaya-avtorizaciya-cherez-blokchein2017/06/20 05:38:21
seoirseupvoted (100.00%) @mamont / besparolnaya-avtorizaciya-cherez-blokchein
2017/06/20 05:38:21
| author | mamont |
| permlink | besparolnaya-avtorizaciya-cherez-blokchein |
| voter | seoirse |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12977753/Trx d1b676a06dabfb4efe7105da7bcaa8d197ae55bb |
View Raw JSON Data
{
"block": 12977753,
"op": [
"vote",
{
"author": "mamont",
"permlink": "besparolnaya-avtorizaciya-cherez-blokchein",
"voter": "seoirse",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-20T05:38:21",
"trx_id": "d1b676a06dabfb4efe7105da7bcaa8d197ae55bb",
"trx_in_block": 7,
"virtual_op": 0
}2017/06/04 09:15:24
2017/06/04 09:15:24
| id | follow |
| json | ["follow",{"follower":"mamont","following":"trogdor","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mamont"] |
| Transaction Info | Block #12521657/Trx 343c9b51556611d1e8dae4d9654ec6a779fe8c23 |
View Raw JSON Data
{
"block": 12521657,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mamont\",\"following\":\"trogdor\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mamont"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-06-04T09:15:24",
"trx_id": "343c9b51556611d1e8dae4d9654ec6a779fe8c23",
"trx_in_block": 2,
"virtual_op": 0
}mamontupvoted (100.00%) @trogdor / introduction-to-eos-the-epic-blockchain-operating-system2017/06/04 09:14:48
mamontupvoted (100.00%) @trogdor / introduction-to-eos-the-epic-blockchain-operating-system
2017/06/04 09:14:48
| author | trogdor |
| permlink | introduction-to-eos-the-epic-blockchain-operating-system |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12521645/Trx 77102f3afd2038db38bfcf4fb44973c87279dc1e |
View Raw JSON Data
{
"block": 12521645,
"op": [
"vote",
{
"author": "trogdor",
"permlink": "introduction-to-eos-the-epic-blockchain-operating-system",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-04T09:14:48",
"trx_id": "77102f3afd2038db38bfcf4fb44973c87279dc1e",
"trx_in_block": 5,
"virtual_op": 0
}| author | lehard |
| permlink | moi-30-dnevnyi-stimit-eksperiment-otchyot-spustya-12-dnei-cel-vypolnena-na-44 |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #6426696/Trx 8133ad8fa8e7bb2fca5e5033e6b539b6651f482f |
View Raw JSON Data
{
"block": 6426696,
"op": [
"vote",
{
"author": "lehard",
"permlink": "moi-30-dnevnyi-stimit-eksperiment-otchyot-spustya-12-dnei-cel-vypolnena-na-44",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-11-04T10:44:27",
"trx_id": "8133ad8fa8e7bb2fca5e5033e6b539b6651f482f",
"trx_in_block": 0,
"virtual_op": 0
}| id | follow |
| json | ["follow",{"follower":"mamont","following":"lehard","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mamont"] |
| Transaction Info | Block #6426590/Trx 0d750b88f78df5f6fc4970bf20dd100fe130e295 |
View Raw JSON Data
{
"block": 6426590,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mamont\",\"following\":\"lehard\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mamont"
]
}
],
"op_in_trx": 0,
"timestamp": "2016-11-04T10:39:09",
"trx_id": "0d750b88f78df5f6fc4970bf20dd100fe130e295",
"trx_in_block": 0,
"virtual_op": 0
}infinity108flagged (-100.00%) @mamont / re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z
infinity108flagged (-100.00%) @mamont / re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z
| author | mamont |
| permlink | re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z |
| voter | infinity108 |
| weight | -10000 (-100.00%) |
| Transaction Info | Block #5626680/Trx 6e966f6342a65068d0c062d93169b56583c3c80d |
View Raw JSON Data
{
"block": 5626680,
"op": [
"vote",
{
"author": "mamont",
"permlink": "re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z",
"voter": "infinity108",
"weight": -10000
}
],
"op_in_trx": 0,
"timestamp": "2016-10-07T15:26:18",
"trx_id": "6e966f6342a65068d0c062d93169b56583c3c80d",
"trx_in_block": 5,
"virtual_op": 0
}nikolay-babenkoupvoted (100.00%) @mamont / re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z
nikolay-babenkoupvoted (100.00%) @mamont / re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z
| author | mamont |
| permlink | re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z |
| voter | nikolay-babenko |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5592881/Trx 1080bb6a8e9e338a491b6c7509df12d327145c30 |
View Raw JSON Data
{
"block": 5592881,
"op": [
"vote",
{
"author": "mamont",
"permlink": "re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z",
"voter": "nikolay-babenko",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-10-06T11:15:42",
"trx_id": "1080bb6a8e9e338a491b6c7509df12d327145c30",
"trx_in_block": 3,
"virtual_op": 0
}azzot88upvoted (100.00%) @mamont / re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z
azzot88upvoted (100.00%) @mamont / re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z
| author | mamont |
| permlink | re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z |
| voter | azzot88 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5591687/Trx f1ec66e44b7cf0480fb0ba38ce266c87ec7dbb16 |
View Raw JSON Data
{
"block": 5591687,
"op": [
"vote",
{
"author": "mamont",
"permlink": "re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z",
"voter": "azzot88",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-10-06T10:16:00",
"trx_id": "f1ec66e44b7cf0480fb0ba38ce266c87ec7dbb16",
"trx_in_block": 0,
"virtual_op": 0
}| author | mamont |
| body | Спасибо за материал. Если есть возможность делать такой анализ по другим скам-проектам, был бы благодарен. Надоело объяснять каждый раз новичкам одно и то же ) |
| json metadata | {"tags":["ponzi"]} |
| parent author | azzot88 |
| parent permlink | chto-ne-tak-s-kibo |
| permlink | re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z |
| title | |
| Transaction Info | Block #5572297/Trx e555daa37b8d9cb9c24a3eaffd03c7c426ce9ed1 |
View Raw JSON Data
{
"block": 5572297,
"op": [
"comment",
{
"author": "mamont",
"body": "Спасибо за материал. Если есть возможность делать такой анализ по другим скам-проектам, был бы благодарен. Надоело объяснять каждый раз новичкам одно и то же )",
"json_metadata": "{\"tags\":[\"ponzi\"]}",
"parent_author": "azzot88",
"parent_permlink": "chto-ne-tak-s-kibo",
"permlink": "re-azzot88-chto-ne-tak-s-kibo-20161005t180620255z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-10-05T18:06:27",
"trx_id": "e555daa37b8d9cb9c24a3eaffd03c7c426ce9ed1",
"trx_in_block": 1,
"virtual_op": 0
}mamontupvoted (100.00%) @azzot88 / chto-ne-tak-s-kibo
mamontupvoted (100.00%) @azzot88 / chto-ne-tak-s-kibo
| author | azzot88 |
| permlink | chto-ne-tak-s-kibo |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5572248/Trx 912ce50386374e2c618283f22a596554d47f871c |
View Raw JSON Data
{
"block": 5572248,
"op": [
"vote",
{
"author": "azzot88",
"permlink": "chto-ne-tak-s-kibo",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-10-05T18:04:00",
"trx_id": "912ce50386374e2c618283f22a596554d47f871c",
"trx_in_block": 2,
"virtual_op": 0
}migechupvoted (100.00%) @mamont / first-blockchain-wedding-in-ukraine
migechupvoted (100.00%) @mamont / first-blockchain-wedding-in-ukraine
| author | mamont |
| permlink | first-blockchain-wedding-in-ukraine |
| voter | migech |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5536565/Trx e4ddfd81e2abe59f6c90533869c9c4c28402d75f |
View Raw JSON Data
{
"block": 5536565,
"op": [
"vote",
{
"author": "mamont",
"permlink": "first-blockchain-wedding-in-ukraine",
"voter": "migech",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-10-04T12:18:39",
"trx_id": "e4ddfd81e2abe59f6c90533869c9c4c28402d75f",
"trx_in_block": 0,
"virtual_op": 0
}mamontupvoted (100.00%) @hipster / u-golosa-budet-krutaya-viki
mamontupvoted (100.00%) @hipster / u-golosa-budet-krutaya-viki
| author | hipster |
| permlink | u-golosa-budet-krutaya-viki |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5534821/Trx 8d582da923548966fa38ebc7c0c414c8dd1384e3 |
View Raw JSON Data
{
"block": 5534821,
"op": [
"vote",
{
"author": "hipster",
"permlink": "u-golosa-budet-krutaya-viki",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-10-04T10:51:15",
"trx_id": "8d582da923548966fa38ebc7c0c414c8dd1384e3",
"trx_in_block": 2,
"virtual_op": 0
}| author | hipster |
| permlink | cyber-fund-is-to-launch-a-russian-steem-based-social-media-platform-golos-under-license-from-steemit-inc |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5290769/Trx 364c0ed6ee4524dff952593c76a557efb6db2ae9 |
View Raw JSON Data
{
"block": 5290769,
"op": [
"vote",
{
"author": "hipster",
"permlink": "cyber-fund-is-to-launch-a-russian-steem-based-social-media-platform-golos-under-license-from-steemit-inc",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-25T23:17:54",
"trx_id": "364c0ed6ee4524dff952593c76a557efb6db2ae9",
"trx_in_block": 0,
"virtual_op": 0
}mamontupvoted (100.00%) @aleco / golos-kiber-fond-tolko-prosheptal-a-vokrug-uzhe-podnimayut-golos
mamontupvoted (100.00%) @aleco / golos-kiber-fond-tolko-prosheptal-a-vokrug-uzhe-podnimayut-golos
| author | aleco |
| permlink | golos-kiber-fond-tolko-prosheptal-a-vokrug-uzhe-podnimayut-golos |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5290640/Trx 012e4f357ff645e2f19a4371b65d493d6da50f78 |
View Raw JSON Data
{
"block": 5290640,
"op": [
"vote",
{
"author": "aleco",
"permlink": "golos-kiber-fond-tolko-prosheptal-a-vokrug-uzhe-podnimayut-golos",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-25T23:11:27",
"trx_id": "012e4f357ff645e2f19a4371b65d493d6da50f78",
"trx_in_block": 0,
"virtual_op": 0
}mamontupvoted (100.00%) @hipster / cyber-nomics-in-august-2016
mamontupvoted (100.00%) @hipster / cyber-nomics-in-august-2016
| author | hipster |
| permlink | cyber-nomics-in-august-2016 |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5101908/Trx 863f2c7a566d27f31d898ae565eaa44514fef5a1 |
View Raw JSON Data
{
"block": 5101908,
"op": [
"vote",
{
"author": "hipster",
"permlink": "cyber-nomics-in-august-2016",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-19T09:13:09",
"trx_id": "863f2c7a566d27f31d898ae565eaa44514fef5a1",
"trx_in_block": 0,
"virtual_op": 0
}mamontupvoted (100.00%) @hipster / obzor-kiber-ekonomiki-za-avgust
mamontupvoted (100.00%) @hipster / obzor-kiber-ekonomiki-za-avgust
| author | hipster |
| permlink | obzor-kiber-ekonomiki-za-avgust |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5086290/Trx d12b1a24f9422f90a4f28117eb8d42e7c84d621f |
View Raw JSON Data
{
"block": 5086290,
"op": [
"vote",
{
"author": "hipster",
"permlink": "obzor-kiber-ekonomiki-za-avgust",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-18T20:10:48",
"trx_id": "d12b1a24f9422f90a4f28117eb8d42e7c84d621f",
"trx_in_block": 0,
"virtual_op": 0
}mamontfollowed @vitaly-lvov
mamontfollowed @vitaly-lvov
| id | follow |
| json | ["follow",{"follower":"mamont","following":"vitaly-lvov","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mamont"] |
| Transaction Info | Block #5086149/Trx 6ac721bd674fbd7b1dc1903536d838c1fad8e288 |
View Raw JSON Data
{
"block": 5086149,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mamont\",\"following\":\"vitaly-lvov\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mamont"
]
}
],
"op_in_trx": 0,
"timestamp": "2016-09-18T20:03:42",
"trx_id": "6ac721bd674fbd7b1dc1903536d838c1fad8e288",
"trx_in_block": 0,
"virtual_op": 0
}mamontfollowed @davidapple
mamontfollowed @davidapple
| id | follow |
| json | ["follow",{"follower":"mamont","following":"davidapple","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mamont"] |
| Transaction Info | Block #4903048/Trx 3299a878d19b966c2fe484a51f8227f4325183d3 |
View Raw JSON Data
{
"block": 4903048,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mamont\",\"following\":\"davidapple\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mamont"
]
}
],
"op_in_trx": 0,
"timestamp": "2016-09-12T10:32:36",
"trx_id": "3299a878d19b966c2fe484a51f8227f4325183d3",
"trx_in_block": 1,
"virtual_op": 0
}mamontupvoted (100.00%) @webosfritos / a-list-of-all-current-and-ongoing-crypto-icos-and-crowdsales
mamontupvoted (100.00%) @webosfritos / a-list-of-all-current-and-ongoing-crypto-icos-and-crowdsales
| author | webosfritos |
| permlink | a-list-of-all-current-and-ongoing-crypto-icos-and-crowdsales |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4804251/Trx 04543f72fa5dd0bf70bb96a0bbaf9227544c0b6d |
View Raw JSON Data
{
"block": 4804251,
"op": [
"vote",
{
"author": "webosfritos",
"permlink": "a-list-of-all-current-and-ongoing-crypto-icos-and-crowdsales",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-08T23:48:09",
"trx_id": "04543f72fa5dd0bf70bb96a0bbaf9227544c0b6d",
"trx_in_block": 1,
"virtual_op": 0
}| author | ekitcho |
| permlink | hacked-full-list-of-soros-ngos-manipulating-elections-in-all-eu-member-states |
| voter | mamont |
| weight | -10000 (-100.00%) |
| Transaction Info | Block #4101593/Trx 372acd8c0256a8224705f322934d761a05ef613a |
View Raw JSON Data
{
"block": 4101593,
"op": [
"vote",
{
"author": "ekitcho",
"permlink": "hacked-full-list-of-soros-ngos-manipulating-elections-in-all-eu-member-states",
"voter": "mamont",
"weight": -10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-15T11:01:27",
"trx_id": "372acd8c0256a8224705f322934d761a05ef613a",
"trx_in_block": 0,
"virtual_op": 0
}| amount | 0.001 SBD |
| from | vdoh |
| memo | I believe in Steemit, I believe in You! Good afternoon, I want to invite you to support my post dedicated to my dream and development and good advertizing of community of Steemit! I want to make the balloon on which I am going to visit many large cities and to place the logo and the slogan Steemit on it. Support me and I will support you! URL : https://steemit.com/steem/@vdoh/rise-steemit |
| to | mamont |
| Transaction Info | Block #3986827/Trx c79c2fd6c8f43396a232972dfaa0a5cc5e70abde |
View Raw JSON Data
{
"block": 3986827,
"op": [
"transfer",
{
"amount": "0.001 SBD",
"from": "vdoh",
"memo": "I believe in Steemit, I believe in You! Good afternoon, I want to invite you to support my post dedicated to my dream and development and good advertizing of community of Steemit! I want to make the balloon on which I am going to visit many large cities and to place the logo and the slogan Steemit on it. Support me and I will support you! URL : https://steemit.com/steem/@vdoh/rise-steemit",
"to": "mamont"
}
],
"op_in_trx": 0,
"timestamp": "2016-08-11T10:53:42",
"trx_id": "c79c2fd6c8f43396a232972dfaa0a5cc5e70abde",
"trx_in_block": 2,
"virtual_op": 0
}mamontconversion request filled: received 3.136 STEEM in exchange of 7.841 SBD
mamontconversion request filled: received 3.136 STEEM in exchange of 7.841 SBD
| amount in | 7.841 SBD |
| amount out | 3.136 STEEM |
| owner | mamont |
| requestid | 1469492152 |
| Transaction Info | Block #3716262/Virtual Operation #2 |
View Raw JSON Data
{
"block": 3716262,
"op": [
"fill_convert_request",
{
"amount_in": "7.841 SBD",
"amount_out": "3.136 STEEM",
"owner": "mamont",
"requestid": 1469492152
}
],
"op_in_trx": 0,
"timestamp": "2016-08-02T00:15:57",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 2
}mamontupvoted (100.00%) @coar / kak-rabotaet-steemit-ru-dlya-russkogovoryashikh
mamontupvoted (100.00%) @coar / kak-rabotaet-steemit-ru-dlya-russkogovoryashikh
| author | coar |
| permlink | kak-rabotaet-steemit-ru-dlya-russkogovoryashikh |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3714569/Trx 629bdbeca853e24878e1714aabe98a5beac38704 |
View Raw JSON Data
{
"block": 3714569,
"op": [
"vote",
{
"author": "coar",
"permlink": "kak-rabotaet-steemit-ru-dlya-russkogovoryashikh",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-01T22:51:03",
"trx_id": "629bdbeca853e24878e1714aabe98a5beac38704",
"trx_in_block": 0,
"virtual_op": 0
}| author | onceuponatime |
| permlink | re-blockchaingirl-the-blockchain-girl-has-joined-steemit-20160730t215150124z |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3657115/Trx a0187fe1deca9ddba5609f9c59941c754a4d2d71 |
View Raw JSON Data
{
"block": 3657115,
"op": [
"vote",
{
"author": "onceuponatime",
"permlink": "re-blockchaingirl-the-blockchain-girl-has-joined-steemit-20160730t215150124z",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-30T22:44:09",
"trx_id": "a0187fe1deca9ddba5609f9c59941c754a4d2d71",
"trx_in_block": 4,
"virtual_op": 0
}mamontupvoted (100.00%) @blockchaingirl / the-blockchain-girl-has-joined-steemit
mamontupvoted (100.00%) @blockchaingirl / the-blockchain-girl-has-joined-steemit
| author | blockchaingirl |
| permlink | the-blockchain-girl-has-joined-steemit |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3657114/Trx 005453d2287ace33834bebd0029cfe68f9a23b2d |
View Raw JSON Data
{
"block": 3657114,
"op": [
"vote",
{
"author": "blockchaingirl",
"permlink": "the-blockchain-girl-has-joined-steemit",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-30T22:44:06",
"trx_id": "005453d2287ace33834bebd0029cfe68f9a23b2d",
"trx_in_block": 0,
"virtual_op": 0
}olesukrupvoted (100.00%) @mamont / besparolnaya-avtorizaciya-cherez-blokchein
olesukrupvoted (100.00%) @mamont / besparolnaya-avtorizaciya-cherez-blokchein
| author | mamont |
| permlink | besparolnaya-avtorizaciya-cherez-blokchein |
| voter | olesukr |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3585432/Trx 9adfef5b935760211b38a3d59381dc4706e0c107 |
View Raw JSON Data
{
"block": 3585432,
"op": [
"vote",
{
"author": "mamont",
"permlink": "besparolnaya-avtorizaciya-cherez-blokchein",
"voter": "olesukr",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-28T10:37:15",
"trx_id": "9adfef5b935760211b38a3d59381dc4706e0c107",
"trx_in_block": 3,
"virtual_op": 0
}olesukrupvoted (100.00%) @mamont / first-blockchain-wedding-in-ukraine
olesukrupvoted (100.00%) @mamont / first-blockchain-wedding-in-ukraine
| author | mamont |
| permlink | first-blockchain-wedding-in-ukraine |
| voter | olesukr |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3585428/Trx 2defc60a7aa21c88ed7901649bb79fe35f8e3440 |
View Raw JSON Data
{
"block": 3585428,
"op": [
"vote",
{
"author": "mamont",
"permlink": "first-blockchain-wedding-in-ukraine",
"voter": "olesukr",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-28T10:37:03",
"trx_id": "2defc60a7aa21c88ed7901649bb79fe35f8e3440",
"trx_in_block": 2,
"virtual_op": 0
}olesukrupvoted (100.00%) @mamont / hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine
olesukrupvoted (100.00%) @mamont / hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine
| author | mamont |
| permlink | hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine |
| voter | olesukr |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3585415/Trx 812e9faa613b777875ce0069ab6a55c8dcf9cbfd |
View Raw JSON Data
{
"block": 3585415,
"op": [
"vote",
{
"author": "mamont",
"permlink": "hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine",
"voter": "olesukr",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-28T10:36:24",
"trx_id": "812e9faa613b777875ce0069ab6a55c8dcf9cbfd",
"trx_in_block": 1,
"virtual_op": 0
}mamontupvoted (100.00%) @stealthtrader / is-ethereum-classic-replacing-ethereum
mamontupvoted (100.00%) @stealthtrader / is-ethereum-classic-replacing-ethereum
| author | stealthtrader |
| permlink | is-ethereum-classic-replacing-ethereum |
| voter | mamont |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3560594/Trx 06cd20e726d688d806b3e6494c99b2e594e49c9f |
View Raw JSON Data
{
"block": 3560594,
"op": [
"vote",
{
"author": "stealthtrader",
"permlink": "is-ethereum-classic-replacing-ethereum",
"voter": "mamont",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-27T13:39:54",
"trx_id": "06cd20e726d688d806b3e6494c99b2e594e49c9f",
"trx_in_block": 0,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress77.81%
{
"voting_manabar": {
"current_mana": "201282688186",
"last_update_time": 1571780505
},
"downvote_manabar": {
"current_mana": "51347624537",
"last_update_time": 1571780505
},
"rc_account": {
"account": "mamont",
"rc_manabar": {
"current_mana": "207411247122",
"last_update_time": 1572002580
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "207411247122"
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM77wBJPpuro3z56qbnMqtzJ5xjN23zusebGoK6yQr6bJBYeC43V1/1
Active
Single Signature
Public Keys
STM6MyRjswpSDkpcrbTmEebuLRpdfhoS2yooxiGVSaQUZahDKQvsp1/1
Posting
Single Signature
Public Keys
STM6W4GcqazvfQmWUUNrFLamTexGe2LLAxAVcjQYcR8FkEK2AyUGu1/1
Memo
STM8EcDjDWYNxUdBn4X2ozyUd2wRHExFvbp48TFSnwKff4tmFFeo6
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM77wBJPpuro3z56qbnMqtzJ5xjN23zusebGoK6yQr6bJBYeC43V",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6MyRjswpSDkpcrbTmEebuLRpdfhoS2yooxiGVSaQUZahDKQvsp",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6W4GcqazvfQmWUUNrFLamTexGe2LLAxAVcjQYcR8FkEK2AyUGu",
1
]
]
},
"memo": "STM8EcDjDWYNxUdBn4X2ozyUd2wRHExFvbp48TFSnwKff4tmFFeo6"
}Witness Votes
0 / 30
No active witness votes.
[]