VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.058USD
STEEM
0.001STEEM
SBD
0.044SBD
Effective Power
5.001SP
├── Own SP
0.680SP
└── Incoming DelegationsDeleg
+4.321SP
Detailed Balance
| STEEM | ||
| balance | 0.001STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.680SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.321SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.044SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1106.522652 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7037.137154 VESTS",
"sbd_balance": "0.044 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | sacen |
| id | 366664 |
| rank | 1,424,270 |
| reputation | 756505281 |
| created | 2017-09-12T23:02:21 |
| recovery_account | steem |
| proxy | None |
| post_count | 17 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2017-11-05T20:38:57 |
| last_root_post | 2017-11-05T20:38:57 |
| last_vote_time | 2017-11-05T20:38:57 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.001 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.044 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1106.522652 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7037.137154 VESTS |
| reward_vesting_balance | 0.000000 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 | 2017-11-06T01:48:06 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 366664,
"name": "sacen",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5cQnbwTkh6nhkxW8Mx7uYHZ7ogAXx3EQVDFwwRWUwNgqPx6BTX",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7F9UfC1g9Arb8ANaGhmzhAe8tCPpJfx4qGVbmzmXU12rosBs1X",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM57PhNhqo6rG6CGqwyz6PfGcBrUN9m3gv9YTmkFRZvRoYcaf6sm",
1
]
]
},
"memo_key": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/54NpKqK.png\",\"cover_image\":\"https://i.imgur.com/1hKiWNY.png\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/54NpKqK.png\",\"cover_image\":\"https://i.imgur.com/1hKiWNY.png\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-11-06T01:48:06",
"created": "2017-09-12T23:02:21",
"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": 17,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779084036
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779084036
},
"voting_power": 0,
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.044 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2018-07-25T04:46:51",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"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.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "1106.522652 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7037.137154 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": 0,
"posting_rewards": 74,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2017-11-05T20:38:57",
"last_root_post": "2017-11-05T20:38:57",
"last_vote_time": "2017-11-05T20:38:57",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 756505281,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 1424270
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 06:00:36
2026/05/18 06:00:36
| delegator | steem |
| delegatee | sacen |
| vesting shares | 7037.137154 VESTS |
| Transaction Info | Block #106150326/Trx 02e161a1643ee81aa4cf390f9baf6e933d7290f7 |
View Raw JSON Data
{
"trx_id": "02e161a1643ee81aa4cf390f9baf6e933d7290f7",
"block": 106150326,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T06:00:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "7037.137154 VESTS"
}
]
}2026/05/13 03:13:42
2026/05/13 03:13:42
| delegator | steem |
| delegatee | sacen |
| vesting shares | 4324.926749 VESTS |
| Transaction Info | Block #106003711/Trx 9d232163efadbd66040f9036c16e81bfd97ef0c2 |
View Raw JSON Data
{
"trx_id": "9d232163efadbd66040f9036c16e81bfd97ef0c2",
"block": 106003711,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-13T03:13:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "4324.926749 VESTS"
}
]
}2026/04/26 05:12:42
2026/04/26 05:12:42
| delegator | steem |
| delegatee | sacen |
| vesting shares | 7049.652910 VESTS |
| Transaction Info | Block #105517817/Trx 6bde877e4da26c05c5828fa6c94d18ba726fcc86 |
View Raw JSON Data
{
"trx_id": "6bde877e4da26c05c5828fa6c94d18ba726fcc86",
"block": 105517817,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-26T05:12:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "7049.652910 VESTS"
}
]
}2026/01/23 23:16:51
2026/01/23 23:16:51
| delegator | steem |
| delegatee | sacen |
| vesting shares | 4366.473568 VESTS |
| Transaction Info | Block #102870355/Trx 9ec7a0c7649c6b324ef76edb5d876787604eb0ec |
View Raw JSON Data
{
"trx_id": "9ec7a0c7649c6b324ef76edb5d876787604eb0ec",
"block": 102870355,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T23:16:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "4366.473568 VESTS"
}
]
}2024/12/17 18:27:15
2024/12/17 18:27:15
| delegator | steem |
| delegatee | sacen |
| vesting shares | 4530.692765 VESTS |
| Transaction Info | Block #91316575/Trx 29802e6b5bccc07ff98f1ffa72960eb18dd63eb3 |
View Raw JSON Data
{
"trx_id": "29802e6b5bccc07ff98f1ffa72960eb18dd63eb3",
"block": 91316575,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T18:27:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "4530.692765 VESTS"
}
]
}2023/11/14 10:08:33
2023/11/14 10:08:33
| delegator | steem |
| delegatee | sacen |
| vesting shares | 4699.826297 VESTS |
| Transaction Info | Block #79870729/Trx 6b4b5dd8ef8a82dd3ea53d38267f56dda48dbfc2 |
View Raw JSON Data
{
"trx_id": "6b4b5dd8ef8a82dd3ea53d38267f56dda48dbfc2",
"block": 79870729,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-14T10:08:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "4699.826297 VESTS"
}
]
}2023/09/22 10:03:45
2023/09/22 10:03:45
| delegator | steem |
| delegatee | sacen |
| vesting shares | 7636.735083 VESTS |
| Transaction Info | Block #78362471/Trx c0b5066a8fc86d5dd89f626c9a1ae9984511c909 |
View Raw JSON Data
{
"trx_id": "c0b5066a8fc86d5dd89f626c9a1ae9984511c909",
"block": 78362471,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-22T10:03:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "7636.735083 VESTS"
}
]
}2022/11/03 17:33:54
2022/11/03 17:33:54
| delegator | steem |
| delegatee | sacen |
| vesting shares | 7858.786521 VESTS |
| Transaction Info | Block #69120262/Trx 6295c051dae5e76e92a19a6fc00d8b7949a2336d |
View Raw JSON Data
{
"trx_id": "6295c051dae5e76e92a19a6fc00d8b7949a2336d",
"block": 69120262,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T17:33:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "7858.786521 VESTS"
}
]
}2022/01/17 22:47:33
2022/01/17 22:47:33
| delegator | steem |
| delegatee | sacen |
| vesting shares | 8078.894122 VESTS |
| Transaction Info | Block #60823544/Trx 9e4a62095bb895f3be1fc7e327c6550b39262a0e |
View Raw JSON Data
{
"trx_id": "9e4a62095bb895f3be1fc7e327c6550b39262a0e",
"block": 60823544,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T22:47:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "8078.894122 VESTS"
}
]
}2021/06/14 05:59:12
2021/06/14 05:59:12
| delegator | steem |
| delegatee | sacen |
| vesting shares | 8263.088410 VESTS |
| Transaction Info | Block #54613887/Trx 2ce5059d95113639e46cf732dcbb2042a1bf0c72 |
View Raw JSON Data
{
"trx_id": "2ce5059d95113639e46cf732dcbb2042a1bf0c72",
"block": 54613887,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T05:59:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "8263.088410 VESTS"
}
]
}2020/12/11 16:11:54
2020/12/11 16:11:54
| delegator | steem |
| delegatee | sacen |
| vesting shares | 8450.510384 VESTS |
| Transaction Info | Block #49361160/Trx c2c241171144d0b094a6abac292fac965f45c35c |
View Raw JSON Data
{
"trx_id": "c2c241171144d0b094a6abac292fac965f45c35c",
"block": 49361160,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T16:11:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "8450.510384 VESTS"
}
]
}2020/12/06 09:47:39
2020/12/06 09:47:39
| delegator | steem |
| delegatee | sacen |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49212686/Trx 833f22f74c344da8f7740fb35021d1f32405edbf |
View Raw JSON Data
{
"trx_id": "833f22f74c344da8f7740fb35021d1f32405edbf",
"block": 49212686,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T09:47:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "1912.543513 VESTS"
}
]
}2020/12/05 19:49:39
2020/12/05 19:49:39
| delegator | steem |
| delegatee | sacen |
| vesting shares | 8456.718238 VESTS |
| Transaction Info | Block #49196243/Trx 3a9f205363ea423d2f0e115d15cd81d50914dfec |
View Raw JSON Data
{
"trx_id": "3a9f205363ea423d2f0e115d15cd81d50914dfec",
"block": 49196243,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T19:49:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "8456.718238 VESTS"
}
]
}2020/11/03 02:11:18
2020/11/03 02:11:18
| delegator | steem |
| delegatee | sacen |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48270223/Trx b89d740182051194b95c103156dbf0cf4911e4a6 |
View Raw JSON Data
{
"trx_id": "b89d740182051194b95c103156dbf0cf4911e4a6",
"block": 48270223,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-03T02:11:18",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "1920.017158 VESTS"
}
]
}2020/05/09 10:50:30
2020/05/09 10:50:30
| delegator | steem |
| delegatee | sacen |
| vesting shares | 8659.523597 VESTS |
| Transaction Info | Block #43223008/Trx 03deec0591e145a84d6c6ca01c781621ef8ad03e |
View Raw JSON Data
{
"trx_id": "03deec0591e145a84d6c6ca01c781621ef8ad03e",
"block": 43223008,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T10:50:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "8659.523597 VESTS"
}
]
}2020/05/08 15:12:30
2020/05/08 15:12:30
| delegator | steem |
| delegatee | sacen |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43200009/Trx 435fd915d636c0c891612bc46a9aa32670981b5f |
View Raw JSON Data
{
"trx_id": "435fd915d636c0c891612bc46a9aa32670981b5f",
"block": 43200009,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T15:12:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "1953.311140 VESTS"
}
]
}2019/10/02 03:17:33
2019/10/02 03:17:33
| delegator | steem |
| delegatee | sacen |
| vesting shares | 8783.788857 VESTS |
| Transaction Info | Block #36920486/Trx ec0d2ae1977b4121c09f941272bc83217faa1e04 |
View Raw JSON Data
{
"trx_id": "ec0d2ae1977b4121c09f941272bc83217faa1e04",
"block": 36920486,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-02T03:17:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "8783.788857 VESTS"
}
]
}2019/09/13 00:04:24
2019/09/13 00:04:24
| parent author | sacen |
| parent permlink | two-of-the-biggest-challenges-blockchain-developers |
| author | steemitboard |
| permlink | steemitboard-notify-sacen-20190913t000424000z |
| title | |
| body | Congratulations @sacen! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@sacen/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@sacen) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=sacen)_</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"]} |
| Transaction Info | Block #36370593/Trx 40a41dbc1519a7473cb658da05171eacbe80da0e |
View Raw JSON Data
{
"trx_id": "40a41dbc1519a7473cb658da05171eacbe80da0e",
"block": 36370593,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-13T00:04:24",
"op": [
"comment",
{
"parent_author": "sacen",
"parent_permlink": "two-of-the-biggest-challenges-blockchain-developers",
"author": "steemitboard",
"permlink": "steemitboard-notify-sacen-20190913t000424000z",
"title": "",
"body": "Congratulations @sacen! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@sacen/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@sacen) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=sacen)_</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\"]}"
}
]
}2018/10/24 07:12:54
2018/10/24 07:12:54
| delegator | steem |
| delegatee | sacen |
| vesting shares | 8981.651569 VESTS |
| Transaction Info | Block #27081851/Trx 5947e72c270c7b04d34c4b04d5651033026d7847 |
View Raw JSON Data
{
"trx_id": "5947e72c270c7b04d34c4b04d5651033026d7847",
"block": 27081851,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-10-24T07:12:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "8981.651569 VESTS"
}
]
}2018/09/13 01:37:12
2018/09/13 01:37:12
| parent author | sacen |
| parent permlink | two-of-the-biggest-challenges-blockchain-developers |
| author | steemitboard |
| permlink | steemitboard-notify-sacen-20180913t013712000z |
| title | |
| body | Congratulations @sacen! You have received a personal award! [](http://steemitboard.com/@sacen) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-09-07"><img src="https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-09-07">SteemitBoard - Witness Update</a></td></tr></table> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[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"]} |
| Transaction Info | Block #25910881/Trx c31210de87562baa23ce3ee46fbf54890c67b6bf |
View Raw JSON Data
{
"trx_id": "c31210de87562baa23ce3ee46fbf54890c67b6bf",
"block": 25910881,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-13T01:37:12",
"op": [
"comment",
{
"parent_author": "sacen",
"parent_permlink": "two-of-the-biggest-challenges-blockchain-developers",
"author": "steemitboard",
"permlink": "steemitboard-notify-sacen-20180913t013712000z",
"title": "",
"body": "Congratulations @sacen! You have received a personal award!\n\n[](http://steemitboard.com/@sacen) 1 Year 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<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-09-07\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-09-07\">SteemitBoard - Witness Update</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[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\"]}"
}
]
}2018/07/25 06:11:51
2018/07/25 06:11:51
| delegator | steem |
| delegatee | sacen |
| vesting shares | 29305.402079 VESTS |
| Transaction Info | Block #24477463/Trx 2c5137d4705285f03f7a18ce668db285ba4745fd |
View Raw JSON Data
{
"trx_id": "2c5137d4705285f03f7a18ce668db285ba4745fd",
"block": 24477463,
"trx_in_block": 38,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-25T06:11:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "29305.402079 VESTS"
}
]
}sacenclaimed reward balance: 0.044 SBD, 0.047 SP2018/07/25 04:46:51
sacenclaimed reward balance: 0.044 SBD, 0.047 SP
2018/07/25 04:46:51
| account | sacen |
| reward steem | 0.000 STEEM |
| reward sbd | 0.044 SBD |
| reward vests | 76.148322 VESTS |
| Transaction Info | Block #24475764/Trx de4a906edb29e86733dc35e59c73e36530e11448 |
View Raw JSON Data
{
"trx_id": "de4a906edb29e86733dc35e59c73e36530e11448",
"block": 24475764,
"trx_in_block": 47,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-25T04:46:51",
"op": [
"claim_reward_balance",
{
"account": "sacen",
"reward_steem": "0.000 STEEM",
"reward_sbd": "0.044 SBD",
"reward_vests": "76.148322 VESTS"
}
]
}2018/05/17 02:33:27
2018/05/17 02:33:27
| delegator | steem |
| delegatee | sacen |
| vesting shares | 9143.691272 VESTS |
| Transaction Info | Block #22497369/Trx 4d5b58836ffd0c81fc4836d0da0db9b1e4d0f2fd |
View Raw JSON Data
{
"trx_id": "4d5b58836ffd0c81fc4836d0da0db9b1e4d0f2fd",
"block": 22497369,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-17T02:33:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "9143.691272 VESTS"
}
]
}2018/02/22 12:29:03
2018/02/22 12:29:03
| delegator | steem |
| delegatee | sacen |
| vesting shares | 29625.749579 VESTS |
| Transaction Info | Block #20092609/Trx 3ce53229e5dcf823224a0da737bc940e3f7b16ab |
View Raw JSON Data
{
"trx_id": "3ce53229e5dcf823224a0da737bc940e3f7b16ab",
"block": 20092609,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-22T12:29:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "29625.749579 VESTS"
}
]
}money-dreamersent 0.001 STEEM to @sacen- "Gift!"2018/01/25 04:33:57
money-dreamersent 0.001 STEEM to @sacen- "Gift!"
2018/01/25 04:33:57
| from | money-dreamer |
| to | sacen |
| amount | 0.001 STEEM |
| memo | Gift! |
| Transaction Info | Block #19277603/Trx 9fa3c6bd5758fc5084499b266b3bc4d319e3d87c |
View Raw JSON Data
{
"trx_id": "9fa3c6bd5758fc5084499b266b3bc4d319e3d87c",
"block": 19277603,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-25T04:33:57",
"op": [
"transfer",
{
"from": "money-dreamer",
"to": "sacen",
"amount": "0.001 STEEM",
"memo": "Gift!"
}
]
}2018/01/23 20:44:21
2018/01/23 20:44:21
| voter | kostika |
| author | sacen |
| permlink | re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19239423/Trx f50c3a8bb84625316d8140481af693a4b34922b9 |
View Raw JSON Data
{
"trx_id": "f50c3a8bb84625316d8140481af693a4b34922b9",
"block": 19239423,
"trx_in_block": 50,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-23T20:44:21",
"op": [
"vote",
{
"voter": "kostika",
"author": "sacen",
"permlink": "re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z",
"weight": 10000
}
]
}2018/01/08 15:43:18
2018/01/08 15:43:18
| parent author | sacen |
| parent permlink | re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z |
| author | ryuzaki |
| permlink | re-sacen-re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20180108t154321616z |
| title | |
| body | i'm in the same, the worst is i'm almost sure ( 99.5% ) i saw it once : 0.6 QTUM and then, i tried again to watch it after my dinner, like 1 hour afer and they disapear. I'm exactly in the same case, with another "accountname" plus de default one. Thanks if you can return about this |
| json metadata | {"tags":["qtum"],"app":"steemit/0.1"} |
| Transaction Info | Block #18801695/Trx 821d4c0f1e8e165b0c8933e4f0b4a3fbe85fd5d8 |
View Raw JSON Data
{
"trx_id": "821d4c0f1e8e165b0c8933e4f0b4a3fbe85fd5d8",
"block": 18801695,
"trx_in_block": 51,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-08T15:43:18",
"op": [
"comment",
{
"parent_author": "sacen",
"parent_permlink": "re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z",
"author": "ryuzaki",
"permlink": "re-sacen-re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20180108t154321616z",
"title": "",
"body": "i'm in the same, the worst is i'm almost sure ( 99.5% ) i saw it once : 0.6 QTUM and then, i tried again to watch it after my dinner, like 1 hour afer and they disapear. I'm exactly in the same case, with another \"accountname\" plus de default one. \n\nThanks if you can return about this",
"json_metadata": "{\"tags\":[\"qtum\"],\"app\":\"steemit/0.1\"}"
}
]
}2017/12/18 07:17:18
2017/12/18 07:17:18
| parent author | sacen |
| parent permlink | tron-and-why-it-s-price-looking-bullish |
| author | tripledoubleyo |
| permlink | re-sacen-tron-and-why-it-s-price-looking-bullish-20171218t071716607z |
| title | |
| body | TRX goal doesn't seem to be different from steemit. |
| json metadata | {"tags":["cryptocurrency"],"app":"steemit/0.1"} |
| Transaction Info | Block #18187288/Trx 7b511b2d9171734deae68718bfb14f2c848d73f6 |
View Raw JSON Data
{
"trx_id": "7b511b2d9171734deae68718bfb14f2c848d73f6",
"block": 18187288,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-18T07:17:18",
"op": [
"comment",
{
"parent_author": "sacen",
"parent_permlink": "tron-and-why-it-s-price-looking-bullish",
"author": "tripledoubleyo",
"permlink": "re-sacen-tron-and-why-it-s-price-looking-bullish-20171218t071716607z",
"title": "",
"body": "TRX goal doesn't seem to be different from steemit.",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
}
]
}tripledoubleyoupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish2017/12/18 07:15:00
tripledoubleyoupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish
2017/12/18 07:15:00
| voter | tripledoubleyo |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18187242/Trx a3b3ebb89919fbefd250882daf12a4d81ec2fdcc |
View Raw JSON Data
{
"trx_id": "a3b3ebb89919fbefd250882daf12a4d81ec2fdcc",
"block": 18187242,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-18T07:15:00",
"op": [
"vote",
{
"voter": "tripledoubleyo",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"weight": 10000
}
]
}alex13200upvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish2017/12/16 03:02:18
alex13200upvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish
2017/12/16 03:02:18
| voter | alex13200 |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18124596/Trx be0ac5d4b4258f00e5839aff4708efbf5de1f759 |
View Raw JSON Data
{
"trx_id": "be0ac5d4b4258f00e5839aff4708efbf5de1f759",
"block": 18124596,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-16T03:02:18",
"op": [
"vote",
{
"voter": "alex13200",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"weight": 10000
}
]
}katyclarkupvoted (100.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers2017/11/09 10:20:15
katyclarkupvoted (100.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers
2017/11/09 10:20:15
| voter | katyclark |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17068190/Trx 8573967f4030e5316310b823c8886e26f8ba979e |
View Raw JSON Data
{
"trx_id": "8573967f4030e5316310b823c8886e26f8ba979e",
"block": 17068190,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-09T10:20:15",
"op": [
"vote",
{
"voter": "katyclark",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"weight": 10000
}
]
}smartonelegalupvoted (1.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers2017/11/06 03:57:45
smartonelegalupvoted (1.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers
2017/11/06 03:57:45
| voter | smartonelegal |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| weight | 100 (1.00%) |
| Transaction Info | Block #16974258/Trx e27da199bb8f6ea2353a64bcf8e61811944e8751 |
View Raw JSON Data
{
"trx_id": "e27da199bb8f6ea2353a64bcf8e61811944e8751",
"block": 16974258,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T03:57:45",
"op": [
"vote",
{
"voter": "smartonelegal",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"weight": 100
}
]
}sacenupdated their account properties2017/11/06 01:48:06
sacenupdated their account properties
2017/11/06 01:48:06
| account | sacen |
| memo key | STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/54NpKqK.png","cover_image":"https://i.imgur.com/1hKiWNY.png"}} |
| Transaction Info | Block #16971665/Trx 30d758f1978fd66e8cf339b394ed897460486167 |
View Raw JSON Data
{
"trx_id": "30d758f1978fd66e8cf339b394ed897460486167",
"block": 16971665,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:48:06",
"op": [
"account_update",
{
"account": "sacen",
"memo_key": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/54NpKqK.png\",\"cover_image\":\"https://i.imgur.com/1hKiWNY.png\"}}"
}
]
}sacenupdated their account properties2017/11/06 01:43:54
sacenupdated their account properties
2017/11/06 01:43:54
| account | sacen |
| memo key | STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/54NpKqK.png","cover_image":"https://i.imgur.com/ZLPTEK2.jpg"}} |
| Transaction Info | Block #16971581/Trx 21bacfca3fdb5f16167ec608117e32734db4d6fa |
View Raw JSON Data
{
"trx_id": "21bacfca3fdb5f16167ec608117e32734db4d6fa",
"block": 16971581,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:43:54",
"op": [
"account_update",
{
"account": "sacen",
"memo_key": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/54NpKqK.png\",\"cover_image\":\"https://i.imgur.com/ZLPTEK2.jpg\"}}"
}
]
}sacenupdated their account properties2017/11/06 01:41:09
sacenupdated their account properties
2017/11/06 01:41:09
| account | sacen |
| memo key | STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/54NpKqK.png","cover_image":"https://i.imgur.com/8UOOlQK.png"}} |
| Transaction Info | Block #16971526/Trx 7935a60d92d367679d592b6e2448bc424dc58f98 |
View Raw JSON Data
{
"trx_id": "7935a60d92d367679d592b6e2448bc424dc58f98",
"block": 16971526,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:41:09",
"op": [
"account_update",
{
"account": "sacen",
"memo_key": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/54NpKqK.png\",\"cover_image\":\"https://i.imgur.com/8UOOlQK.png\"}}"
}
]
}sacenupdated their account properties2017/11/06 01:39:36
sacenupdated their account properties
2017/11/06 01:39:36
| account | sacen |
| memo key | STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/54NpKqK.png","cover_image":"https://i.imgur.com/k4jtXdN.png"}} |
| Transaction Info | Block #16971495/Trx 806715934f749fcb9675664e8165346b8cccff94 |
View Raw JSON Data
{
"trx_id": "806715934f749fcb9675664e8165346b8cccff94",
"block": 16971495,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:39:36",
"op": [
"account_update",
{
"account": "sacen",
"memo_key": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/54NpKqK.png\",\"cover_image\":\"https://i.imgur.com/k4jtXdN.png\"}}"
}
]
}sacenupdated their account properties2017/11/06 01:35:09
sacenupdated their account properties
2017/11/06 01:35:09
| account | sacen |
| memo key | STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/54NpKqK.png"}} |
| Transaction Info | Block #16971406/Trx a523123f80f41d6073534d9472b8feff9d4b3597 |
View Raw JSON Data
{
"trx_id": "a523123f80f41d6073534d9472b8feff9d4b3597",
"block": 16971406,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:35:09",
"op": [
"account_update",
{
"account": "sacen",
"memo_key": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/54NpKqK.png\"}}"
}
]
}sacenupdated their account properties2017/11/06 01:32:54
sacenupdated their account properties
2017/11/06 01:32:54
| account | sacen |
| memo key | STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/qMwLOhP.jpg"}} |
| Transaction Info | Block #16971361/Trx 09808b66f7cbabf834e54f1e1e614be8acb36cfc |
View Raw JSON Data
{
"trx_id": "09808b66f7cbabf834e54f1e1e614be8acb36cfc",
"block": 16971361,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:32:54",
"op": [
"account_update",
{
"account": "sacen",
"memo_key": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/qMwLOhP.jpg\"}}"
}
]
}sacenupdated their account properties2017/11/06 01:27:09
sacenupdated their account properties
2017/11/06 01:27:09
| account | sacen |
| memo key | STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ |
| json metadata | {"profile":{"profile_image":"https://ibb.co/kuODYG"}} |
| Transaction Info | Block #16971246/Trx 1298b2eb0deab45ca038c62a4c21143f7bee4843 |
View Raw JSON Data
{
"trx_id": "1298b2eb0deab45ca038c62a4c21143f7bee4843",
"block": 16971246,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:27:09",
"op": [
"account_update",
{
"account": "sacen",
"memo_key": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://ibb.co/kuODYG\"}}"
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/06 01:19:03
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/06 01:19:03
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers face |
| body | @@ -5881,16 +5881,17 @@ real wor +l d throug |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16971084/Trx 1f743711605b686d086b4537738237b8e7ae6261 |
View Raw JSON Data
{
"trx_id": "1f743711605b686d086b4537738237b8e7ae6261",
"block": 16971084,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:19:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers face",
"body": "@@ -5881,16 +5881,17 @@\n real wor\n+l\n d throug\n",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/06 01:15:06
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/06 01:15:06
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers face |
| body | @@ -1,88 +1,88 @@ # K -NOW YOUR CUSTOMER (KYC) AND SCALABILITY CHALLENGES FACED BY BLOCKCHAIN DEVELOPERS +now your customer(KYC) and Scalability Challenges Faced by Blockchain Developers. %0A%0A!%5B |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16971005/Trx ba9763f46dc30d6b078962550dad0b3acd75bc8c |
View Raw JSON Data
{
"trx_id": "ba9763f46dc30d6b078962550dad0b3acd75bc8c",
"block": 16971005,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-06T01:15:06",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers face",
"body": "@@ -1,88 +1,88 @@\n # K\n-NOW YOUR CUSTOMER (KYC) AND SCALABILITY CHALLENGES FACED BY BLOCKCHAIN DEVELOPERS\n+now your customer(KYC) and Scalability Challenges Faced by Blockchain Developers.\n %0A%0A!%5B\n",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}skurkovaupvoted (100.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers2017/11/05 23:25:27
skurkovaupvoted (100.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers
2017/11/05 23:25:27
| voter | skurkova |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16968814/Trx 3cb91f33f2305ac324a3961b13834fd5260819d1 |
View Raw JSON Data
{
"trx_id": "3cb91f33f2305ac324a3961b13834fd5260819d1",
"block": 16968814,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T23:25:27",
"op": [
"vote",
{
"voter": "skurkova",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"weight": 10000
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/05 22:29:57
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/05 22:29:57
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers face |
| body | @@ -2618,16 +2618,17 @@ nd why.%0A +%0A He also |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16967705/Trx d875c1b4422f57564db64cfb94fbe5f8aba40ab5 |
View Raw JSON Data
{
"trx_id": "d875c1b4422f57564db64cfb94fbe5f8aba40ab5",
"block": 16967705,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T22:29:57",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers face",
"body": "@@ -2618,16 +2618,17 @@\n nd why.%0A\n+%0A\n He also \n",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/05 22:27:57
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/05 22:27:57
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers face |
| body | @@ -1851,16 +1851,17 @@ scale.%0A +%0A Also, sc |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16967665/Trx 535a9162299613bd05181f2a7dc8396705a46e45 |
View Raw JSON Data
{
"trx_id": "535a9162299613bd05181f2a7dc8396705a46e45",
"block": 16967665,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T22:27:57",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers face",
"body": "@@ -1851,16 +1851,17 @@\n scale.%0A\n+%0A\n Also, sc\n",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/05 22:26:36
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/05 22:26:36
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers face |
| body | @@ -1487,17 +1487,17 @@ etc.%0A%0ATh -e +a n we hav |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16967638/Trx 74dfb8a566e2759399eb778d00e09d4cead5e34d |
View Raw JSON Data
{
"trx_id": "74dfb8a566e2759399eb778d00e09d4cead5e34d",
"block": 16967638,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T22:26:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers face",
"body": "@@ -1487,17 +1487,17 @@\n etc.%0A%0ATh\n-e\n+a\n n we hav\n",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/05 22:24:27
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/05 22:24:27
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers face |
| body | @@ -1046,16 +1046,18 @@ peated. +%0A%0A One solu |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16967595/Trx c782bb0b3fad21f12d87eb244d56668f49547058 |
View Raw JSON Data
{
"trx_id": "c782bb0b3fad21f12d87eb244d56668f49547058",
"block": 16967595,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T22:24:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers face",
"body": "@@ -1046,16 +1046,18 @@\n peated. \n+%0A%0A\n One solu\n",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/05 22:24:00
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/05 22:24:00
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers face |
| body | @@ -367,16 +367,17 @@ omer). %0A +%0A In secur |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16967586/Trx b3297cf66345e7f605c1cec6a0a4f36fe37bfe56 |
View Raw JSON Data
{
"trx_id": "b3297cf66345e7f605c1cec6a0a4f36fe37bfe56",
"block": 16967586,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T22:24:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers face",
"body": "@@ -367,16 +367,17 @@\n omer). %0A\n+%0A\n In secur\n",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}lawyerupupvoted (1.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers2017/11/05 21:30:27
lawyerupupvoted (1.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers
2017/11/05 21:30:27
| voter | lawyerup |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| weight | 100 (1.00%) |
| Transaction Info | Block #16966517/Trx 3c22be1474cc36a5d0b241cb5bcdbe955711fd82 |
View Raw JSON Data
{
"trx_id": "3c22be1474cc36a5d0b241cb5bcdbe955711fd82",
"block": 16966517,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T21:30:27",
"op": [
"vote",
{
"voter": "lawyerup",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"weight": 100
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/05 21:29:09
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/05 21:29:09
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers face |
| body | # KNOW YOUR CUSTOMER (KYC) AND SCALABILITY CHALLENGES FACED BY BLOCKCHAIN DEVELOPERS  # Introduction Two of the biggest challenges blockchain developers faces are Scalability and KYC (Know your customer). In security-sensitive businesses, there is a need to have a means of knowing who your customers are. The “know your customer” process better known as KYC helps institutions verify the identity of their clients. KYC is a regulatory and legal requirement that has to be fulfilled by the banks for both new and existing clients. Typical KYC includes acquiring personal information, related proofs, background checks, ongoing changes and store client details. Current systems require each institution do their own KYC which translates to a higher cost of customer acquisition for the banks. Also, should the customer wish to engage with a different bank, the process gets repeated. One solution is to have a central entity do the KYC process on behalf of the entire industry. A central database provides universal accessibility and lower cost of client acquisition. However, having a single source of information makes it more vulnerable to hacking attacks. This is where the distributed ledger technology becomes a game changer. Documents necessary for KYC often includes Driving license, Passport, utility bill etc. Then we have scalability, a network protocol is said to be scalable if it is suitably efficient and practical when applied to large situations, for example, a large input data set; a large number of outputs or user; in the case of a distributed system, a large number of participating nodes. If a system or design fails when a quantity increases, it does not scale. Also, scalability is defined by B. Clifford Neuman as: “A system is said to be scalable if it can handle the addition of users and resources without suffering a noticeable loss of performance or increase in administrative complexity.” # What the community are talking about and their solutions to these two issues? In a meet up with Pavel Kravchenko (PhD), he talks about cryptocurrency exchanges like Kraken, having a huge form with many pages for customers. These contain all the information of all their customers, leading to a situation where whitelisted customer information. As soon as these whitelisted addresses get leaked to the internet, then anonymity is completely destroyed. Everybody will then be able to see who transacted with whom, when and why. He also discussed a group based system for solving the KYC problem, by assigning private keys to each member of the group, and a unique public key that ties them to the group. In an event where an individual in a group has his identity stolen or lost his/ her phone, this can be easily revoked as soon as it is reported to the group head, and a new one can be re-issued via a recovery key. The best-proposed solution again was a community-based manager, whereby if some member of a group did something wrong, the group could vote to reveal the person’s identity. Pavel further mentioned data mining, which makes it possible to analyze transaction patterns, hence leading to an understanding of the individuals or entity behind the transactions. Cryptocurrencies are no different from credit card information, considering that the blockchain (database) is public. With whitelisted addresses, at some point anonymity will be zero. # Why Scalability and KYC (Know your customer) are so hard to solve? The first generation cryptocurrency “Bitcoin” was about building a decentralized money, i.e. sending the value to people that is actually worth something. The second generation “Ethereum” looked at the transactions having stories, which came in the form of smart contracts. Both first and second generation blockchain systems faced a challenge of scalability because of the way their architecture. This makes it difficult to make a change or upgrade without it leading to a hard fork, i.e. a complete divergence of the network. Know your customer (KYC) is equally challenging because these systems were also designed as completely anonymous. This anonymity makes it very attractive to a lot of users who believe in having control over their identity and privacy. Making any form of changes to this is hard without it leading to a hard fork of the network. # Which crypto blockchain might be able to solve the problem: Cardano, Ethereum, Neo, Qtum, or Civic? From a research of the above-listed blockchain/cryptocurrency solution, no single one proffers a perfect solution to both scalability and KYC challenges. However Cardano, Civic, and Qtum are closest to coming up with solution towards scalability and KYC. Following an interview with Charles Hoskinson the CEO of Input-Output Hong Kong (IOHK), currently working on the Cardano (ADA) project. Charles talked about one of the major challenges with cryptocurrencies when it came to adding new features or making upgrades, hence scalability issues. Even making small changes were complicated. He further discussed Bitcoin being the first generation blockchain, Ethereum being second generation blockchain, and Cardano being the third generation blockchain, with a vision to solve the ever-growing scalability and KYC challenges in the blockchain/cryptocurrency space. Cardano has series of layers which allows for scalability and gives users more flexibility to decide if their layers will be regulated or not. With Cardano, a user has a KYC profile which helps with issues of lost login details and so on. Civic focuses more on KYC related solution, giving the user control of their KYC information. Qtum in their white paper also mentioned working on a KYC solution, and ability to connect real word through off-chain data sources. Ethereum is currently working on tackling scalability through the use of “Plasma” as a scalable autonomous smart contract, but not more information on KYC. Unfortunately we all have to wait and see. |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16966491/Trx a940431352c6c6f6ee4c48b36fa655dc499934bc |
View Raw JSON Data
{
"trx_id": "a940431352c6c6f6ee4c48b36fa655dc499934bc",
"block": 16966491,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T21:29:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers face",
"body": "# KNOW YOUR CUSTOMER (KYC) AND SCALABILITY CHALLENGES FACED BY BLOCKCHAIN DEVELOPERS\n\n\n\n# Introduction\n\nTwo of the biggest challenges blockchain developers faces are Scalability and KYC (Know your customer). \nIn security-sensitive businesses, there is a need to have a means of knowing who your customers are. The “know your customer” process better known as KYC helps institutions verify the identity of their clients. KYC is a regulatory and legal requirement that has to be fulfilled by the banks for both new and existing clients. Typical KYC includes acquiring personal information, related proofs, background checks, ongoing changes and store client details. Current systems require each institution do their own KYC which translates to a higher cost of customer acquisition for the banks. Also, should the customer wish to engage with a different bank, the process gets repeated. One solution is to have a central entity do the KYC process on behalf of the entire industry. A central database provides universal accessibility and lower cost of client acquisition. However, having a single source of information makes it more vulnerable to hacking attacks. This is where the distributed ledger technology becomes a game changer. Documents necessary for KYC often includes Driving license, Passport, utility bill etc.\n\nThen we have scalability, a network protocol is said to be scalable if it is suitably efficient and practical when applied to large situations, for example, a large input data set; a large number of outputs or user; in the case of a distributed system, a large number of participating nodes. If a system or design fails when a quantity increases, it does not scale.\nAlso, scalability is defined by B. Clifford Neuman as:\n“A system is said to be scalable if it can handle the addition of users and resources without suffering a noticeable loss of performance or increase in administrative complexity.”\n\n# What the community are talking about and their solutions to these two issues? \n\nIn a meet up with Pavel Kravchenko (PhD), he talks about cryptocurrency exchanges like Kraken, having a huge form with many pages for customers. These contain all the information of all their customers, leading to a situation where whitelisted customer information. As soon as these whitelisted addresses get leaked to the internet, then anonymity is completely destroyed. Everybody will then be able to see who transacted with whom, when and why.\nHe also discussed a group based system for solving the KYC problem, by assigning private keys to each member of the group, and a unique public key that ties them to the group. In an event where an individual in a group has his identity stolen or lost his/ her phone, this can be easily revoked as soon as it is reported to the group head, and a new one can be re-issued via a recovery key.\n\nThe best-proposed solution again was a community-based manager, whereby if some member of a group did something wrong, the group could vote to reveal the person’s identity.\nPavel further mentioned data mining, which makes it possible to analyze transaction patterns, hence leading to an understanding of the individuals or entity behind the transactions. Cryptocurrencies are no different from credit card information, considering that the blockchain (database) is public. With whitelisted addresses, at some point anonymity will be zero.\n\n# Why Scalability and KYC (Know your customer) are so hard to solve?\n\nThe first generation cryptocurrency “Bitcoin” was about building a decentralized money, i.e. sending the value to people that is actually worth something. The second generation “Ethereum” looked at the transactions having stories, which came in the form of smart contracts. Both first and second generation blockchain systems faced a challenge of scalability because of the way their architecture. This makes it difficult to make a change or upgrade without it leading to a hard fork, i.e. a complete divergence of the network.\n\nKnow your customer (KYC) is equally challenging because these systems were also designed as completely anonymous. This anonymity makes it very attractive to a lot of users who believe in having control over their identity and privacy. Making any form of changes to this is hard without it leading to a hard fork of the network.\n\n# Which crypto blockchain might be able to solve the problem: Cardano, Ethereum, Neo, Qtum, or Civic? \n\nFrom a research of the above-listed blockchain/cryptocurrency solution, no single one proffers a perfect solution to both scalability and KYC challenges. However Cardano, Civic, and Qtum are closest to coming up with solution towards scalability and KYC. \n\nFollowing an interview with Charles Hoskinson the CEO of Input-Output Hong Kong (IOHK), currently working on the Cardano (ADA) project. Charles talked about one of the major challenges with cryptocurrencies when it came to adding new features or making upgrades, hence scalability issues. Even making small changes were complicated. He further discussed Bitcoin being the first generation blockchain, Ethereum being second generation blockchain, and Cardano being the third generation blockchain, with a vision to solve the ever-growing scalability and KYC challenges in the blockchain/cryptocurrency space. Cardano has series of layers which allows for scalability and gives users more flexibility to decide if their layers will be regulated or not. With Cardano, a user has a KYC profile which helps with issues of lost login details and so on.\n\nCivic focuses more on KYC related solution, giving the user control of their KYC information. Qtum in their white paper also mentioned working on a KYC solution, and ability to connect real word through off-chain data sources. Ethereum is currently working on tackling scalability through the use of “Plasma” as a scalable autonomous smart contract, but not more information on KYC. Unfortunately we all have to wait and see.",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}irbotupvoted (50.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers2017/11/05 21:11:15
irbotupvoted (50.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers
2017/11/05 21:11:15
| voter | irbot |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| weight | 5000 (50.00%) |
| Transaction Info | Block #16966133/Trx d6553bf05b40ca5cba51a3594bd71e8f4f724d71 |
View Raw JSON Data
{
"trx_id": "d6553bf05b40ca5cba51a3594bd71e8f4f724d71",
"block": 16966133,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T21:11:15",
"op": [
"vote",
{
"voter": "irbot",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"weight": 5000
}
]
}bitcoinparadiseupvoted (0.02%) @sacen / two-of-the-biggest-challenges-blockchain-developers2017/11/05 21:06:57
bitcoinparadiseupvoted (0.02%) @sacen / two-of-the-biggest-challenges-blockchain-developers
2017/11/05 21:06:57
| voter | bitcoinparadise |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| weight | 2 (0.02%) |
| Transaction Info | Block #16966047/Trx 020103357d4db2a08bf6e910b3bdbebc01fbe819 |
View Raw JSON Data
{
"trx_id": "020103357d4db2a08bf6e910b3bdbebc01fbe819",
"block": 16966047,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T21:06:57",
"op": [
"vote",
{
"voter": "bitcoinparadise",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"weight": 2
}
]
}sacenupvoted (100.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers2017/11/05 20:38:57
sacenupvoted (100.00%) @sacen / two-of-the-biggest-challenges-blockchain-developers
2017/11/05 20:38:57
| voter | sacen |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16965487/Trx 23d0a521d8151b074c820487a59c1dd139bcf5ae |
View Raw JSON Data
{
"trx_id": "23d0a521d8151b074c820487a59c1dd139bcf5ae",
"block": 16965487,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T20:38:57",
"op": [
"vote",
{
"voter": "sacen",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"weight": 10000
}
]
}sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers2017/11/05 20:38:57
sacenpublished a new post: two-of-the-biggest-challenges-blockchain-developers
2017/11/05 20:38:57
| parent author | |
| parent permlink | cardano |
| author | sacen |
| permlink | two-of-the-biggest-challenges-blockchain-developers |
| title | Two of the biggest challenges blockchain developers |
| body | # KNOW YOUR CUSTOMER (KYC) AND SCALABILITY CHALLENGES FACED BY BLOCKCHAIN DEVELOPERS  # Introduction Two of the biggest challenges blockchain developers faces are Scalability and KYC (Know your customer). In security-sensitive businesses, there is a need to have a means of knowing who your customers are. The “know your customer” process better known as KYC helps institutions verify the identity of their clients. KYC is a regulatory and legal requirement that has to be fulfilled by the banks for both new and existing clients. Typical KYC includes acquiring personal information, related proofs, background checks, ongoing changes and store client details. Current systems require each institution do their own KYC which translates to a higher cost of customer acquisition for the banks. Also, should the customer wish to engage with a different bank, the process gets repeated. One solution is to have a central entity do the KYC process on behalf of the entire industry. A central database provides universal accessibility and lower cost of client acquisition. However, having a single source of information makes it more vulnerable to hacking attacks. This is where the distributed ledger technology becomes a game changer. Documents necessary for KYC often includes Driving license, Passport, utility bill etc. Then we have scalability, a network protocol is said to be scalable if it is suitably efficient and practical when applied to large situations, for example, a large input data set; a large number of outputs or user; in the case of a distributed system, a large number of participating nodes. If a system or design fails when a quantity increases, it does not scale. Also, scalability is defined by B. Clifford Neuman as: “A system is said to be scalable if it can handle the addition of users and resources without suffering a noticeable loss of performance or increase in administrative complexity.” # What the community are talking about and their solutions to these two issues? In a meet up with Pavel Kravchenko (PhD), he talks about cryptocurrency exchanges like Kraken, having a huge form with many pages for customers. These contain all the information of all their customers, leading to a situation where whitelisted customer information. As soon as these whitelisted addresses get leaked to the internet, then anonymity is completely destroyed. Everybody will then be able to see who transacted with whom, when and why. He also discussed a group based system for solving the KYC problem, by assigning private keys to each member of the group, and a unique public key that ties them to the group. In an event where an individual in a group has his identity stolen or lost his/ her phone, this can be easily revoked as soon as it is reported to the group head, and a new one can be re-issued via a recovery key. The best-proposed solution again was a community-based manager, whereby if some member of a group did something wrong, the group could vote to reveal the person’s identity. Pavel further mentioned data mining, which makes it possible to analyze transaction patterns, hence leading to an understanding of the individuals or entity behind the transactions. Cryptocurrencies are no different from credit card information, considering that the blockchain (database) is public. With whitelisted addresses, at some point anonymity will be zero. # Why Scalability and KYC (Know your customer) are so hard to solve? The first generation cryptocurrency “Bitcoin” was about building a decentralized money, i.e. sending the value to people that is actually worth something. The second generation “Ethereum” looked at the transactions having stories, which came in the form of smart contracts. Both first and second generation blockchain systems faced a challenge of scalability because of the way their architecture. This makes it difficult to make a change or upgrade without it leading to a hard fork, i.e. a complete divergence of the network. Know your customer (KYC) is equally challenging because these systems were also designed as completely anonymous. This anonymity makes it very attractive to a lot of users who believe in having control over their identity and privacy. Making any form of changes to this is hard without it leading to a hard fork of the network. # Which crypto blockchain might be able to solve the problem: Cardano, Ethereum, Neo, Qtum, or Civic? From a research of the above-listed blockchain/cryptocurrency solution, no single one proffers a perfect solution to both scalability and KYC challenges. However Cardano, Civic, and Qtum are closest to coming up with solution towards scalability and KYC. Following an interview with Charles Hoskinson the CEO of Input-Output Hong Kong (IOHK), currently working on the Cardano (ADA) project. Charles talked about one of the major challenges with cryptocurrencies when it came to adding new features or making upgrades, hence scalability issues. Even making small changes were complicated. He further discussed Bitcoin being the first generation blockchain, Ethereum being second generation blockchain, and Cardano being the third generation blockchain, with a vision to solve the ever-growing scalability and KYC challenges in the blockchain/cryptocurrency space. Cardano has series of layers which allows for scalability and gives users more flexibility to decide if their layers will be regulated or not. With Cardano, a user has a KYC profile which helps with issues of lost login details and so on. Civic focuses more on KYC related solution, giving the user control of their KYC information. Qtum in their white paper also mentioned working on a KYC solution, and ability to connect real word through off-chain data sources. Ethereum is currently working on tackling scalability through the use of “Plasma” as a scalable autonomous smart contract, but not more information on KYC. Unfortunately we all have to wait and see. |
| json metadata | {"tags":["cardano","ethereum","neo","qtum","civic"],"image":["https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16965487/Trx 23d0a521d8151b074c820487a59c1dd139bcf5ae |
View Raw JSON Data
{
"trx_id": "23d0a521d8151b074c820487a59c1dd139bcf5ae",
"block": 16965487,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-05T20:38:57",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cardano",
"author": "sacen",
"permlink": "two-of-the-biggest-challenges-blockchain-developers",
"title": "Two of the biggest challenges blockchain developers",
"body": "# KNOW YOUR CUSTOMER (KYC) AND SCALABILITY CHALLENGES FACED BY BLOCKCHAIN DEVELOPERS\n\n\n\n# Introduction\n\nTwo of the biggest challenges blockchain developers faces are Scalability and KYC (Know your customer). \nIn security-sensitive businesses, there is a need to have a means of knowing who your customers are. The “know your customer” process better known as KYC helps institutions verify the identity of their clients. KYC is a regulatory and legal requirement that has to be fulfilled by the banks for both new and existing clients. Typical KYC includes acquiring personal information, related proofs, background checks, ongoing changes and store client details. Current systems require each institution do their own KYC which translates to a higher cost of customer acquisition for the banks. Also, should the customer wish to engage with a different bank, the process gets repeated. One solution is to have a central entity do the KYC process on behalf of the entire industry. A central database provides universal accessibility and lower cost of client acquisition. However, having a single source of information makes it more vulnerable to hacking attacks. This is where the distributed ledger technology becomes a game changer. Documents necessary for KYC often includes Driving license, Passport, utility bill etc.\n\nThen we have scalability, a network protocol is said to be scalable if it is suitably efficient and practical when applied to large situations, for example, a large input data set; a large number of outputs or user; in the case of a distributed system, a large number of participating nodes. If a system or design fails when a quantity increases, it does not scale.\nAlso, scalability is defined by B. Clifford Neuman as:\n“A system is said to be scalable if it can handle the addition of users and resources without suffering a noticeable loss of performance or increase in administrative complexity.”\n\n# What the community are talking about and their solutions to these two issues? \n\nIn a meet up with Pavel Kravchenko (PhD), he talks about cryptocurrency exchanges like Kraken, having a huge form with many pages for customers. These contain all the information of all their customers, leading to a situation where whitelisted customer information. As soon as these whitelisted addresses get leaked to the internet, then anonymity is completely destroyed. Everybody will then be able to see who transacted with whom, when and why.\nHe also discussed a group based system for solving the KYC problem, by assigning private keys to each member of the group, and a unique public key that ties them to the group. In an event where an individual in a group has his identity stolen or lost his/ her phone, this can be easily revoked as soon as it is reported to the group head, and a new one can be re-issued via a recovery key.\n\nThe best-proposed solution again was a community-based manager, whereby if some member of a group did something wrong, the group could vote to reveal the person’s identity.\nPavel further mentioned data mining, which makes it possible to analyze transaction patterns, hence leading to an understanding of the individuals or entity behind the transactions. Cryptocurrencies are no different from credit card information, considering that the blockchain (database) is public. With whitelisted addresses, at some point anonymity will be zero.\n\n# Why Scalability and KYC (Know your customer) are so hard to solve?\n\nThe first generation cryptocurrency “Bitcoin” was about building a decentralized money, i.e. sending the value to people that is actually worth something. The second generation “Ethereum” looked at the transactions having stories, which came in the form of smart contracts. Both first and second generation blockchain systems faced a challenge of scalability because of the way their architecture. This makes it difficult to make a change or upgrade without it leading to a hard fork, i.e. a complete divergence of the network.\n\nKnow your customer (KYC) is equally challenging because these systems were also designed as completely anonymous. This anonymity makes it very attractive to a lot of users who believe in having control over their identity and privacy. Making any form of changes to this is hard without it leading to a hard fork of the network.\n\n# Which crypto blockchain might be able to solve the problem: Cardano, Ethereum, Neo, Qtum, or Civic? \n\nFrom a research of the above-listed blockchain/cryptocurrency solution, no single one proffers a perfect solution to both scalability and KYC challenges. However Cardano, Civic, and Qtum are closest to coming up with solution towards scalability and KYC. \n\nFollowing an interview with Charles Hoskinson the CEO of Input-Output Hong Kong (IOHK), currently working on the Cardano (ADA) project. Charles talked about one of the major challenges with cryptocurrencies when it came to adding new features or making upgrades, hence scalability issues. Even making small changes were complicated. He further discussed Bitcoin being the first generation blockchain, Ethereum being second generation blockchain, and Cardano being the third generation blockchain, with a vision to solve the ever-growing scalability and KYC challenges in the blockchain/cryptocurrency space. Cardano has series of layers which allows for scalability and gives users more flexibility to decide if their layers will be regulated or not. With Cardano, a user has a KYC profile which helps with issues of lost login details and so on.\n\nCivic focuses more on KYC related solution, giving the user control of their KYC information. Qtum in their white paper also mentioned working on a KYC solution, and ability to connect real word through off-chain data sources. Ethereum is currently working on tackling scalability through the use of “Plasma” as a scalable autonomous smart contract, but not more information on KYC. Unfortunately we all have to wait and see.",
"json_metadata": "{\"tags\":[\"cardano\",\"ethereum\",\"neo\",\"qtum\",\"civic\"],\"image\":[\"https://steemitimages.com/DQmUBL2gZBi8pQNy1qm8j4xe5M7ctcVwsmJRPpbNPp4vET2/The-challenges-of-scaling-microservices.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/10/31 03:28:21
2017/10/31 03:28:21
| parent author | sacen |
| parent permlink | cryptocurrency-review-and-insights-for-q4-2017 |
| author | sacen |
| permlink | re-sacen-cryptocurrency-review-and-insights-for-q4-2017-20171031t032821157z |
| title | |
| body | Looks like Bitcoin to hit $7,000 by the end of the year is possible. Another fork in December will push it close to $7K |
| json metadata | {"tags":["cryptocurrency"],"app":"steemit/0.1"} |
| Transaction Info | Block #16800923/Trx 125a74669bb09551de9b5bb58611f25b58f82f71 |
View Raw JSON Data
{
"trx_id": "125a74669bb09551de9b5bb58611f25b58f82f71",
"block": 16800923,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-31T03:28:21",
"op": [
"comment",
{
"parent_author": "sacen",
"parent_permlink": "cryptocurrency-review-and-insights-for-q4-2017",
"author": "sacen",
"permlink": "re-sacen-cryptocurrency-review-and-insights-for-q4-2017-20171031t032821157z",
"title": "",
"body": "Looks like Bitcoin to hit $7,000 by the end of the year is possible. Another fork in December will push it close to $7K",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
}
]
}teovmyupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish2017/10/27 21:25:39
teovmyupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish
2017/10/27 21:25:39
| voter | teovmy |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16707345/Trx d041dec578e0f14973170a10e113da01acffb3f1 |
View Raw JSON Data
{
"trx_id": "d041dec578e0f14973170a10e113da01acffb3f1",
"block": 16707345,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-27T21:25:39",
"op": [
"vote",
{
"voter": "teovmy",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"weight": 10000
}
]
}2017/10/27 03:58:06
2017/10/27 03:58:06
| parent author | hilarski |
| parent permlink | is-it-better-to-hodl-or-trade-in-crypto |
| author | sacen |
| permlink | re-hilarski-is-it-better-to-hodl-or-trade-in-crypto-20171027t035807054z |
| title | |
| body | Do both. |
| json metadata | {"tags":["bitcoin"],"app":"steemit/0.1"} |
| Transaction Info | Block #16686394/Trx 73d805da882af42062b694f5d1efc54ed6cf2596 |
View Raw JSON Data
{
"trx_id": "73d805da882af42062b694f5d1efc54ed6cf2596",
"block": 16686394,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-27T03:58:06",
"op": [
"comment",
{
"parent_author": "hilarski",
"parent_permlink": "is-it-better-to-hodl-or-trade-in-crypto",
"author": "sacen",
"permlink": "re-hilarski-is-it-better-to-hodl-or-trade-in-crypto-20171027t035807054z",
"title": "",
"body": "Do both.",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}"
}
]
}sacenupvoted (100.00%) @hilarski / is-it-better-to-hodl-or-trade-in-crypto2017/10/27 03:57:54
sacenupvoted (100.00%) @hilarski / is-it-better-to-hodl-or-trade-in-crypto
2017/10/27 03:57:54
| voter | sacen |
| author | hilarski |
| permlink | is-it-better-to-hodl-or-trade-in-crypto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16686390/Trx a5667b2475bb015cb832a3648f16be5fb481276f |
View Raw JSON Data
{
"trx_id": "a5667b2475bb015cb832a3648f16be5fb481276f",
"block": 16686390,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-27T03:57:54",
"op": [
"vote",
{
"voter": "sacen",
"author": "hilarski",
"permlink": "is-it-better-to-hodl-or-trade-in-crypto",
"weight": 10000
}
]
}sacenupvoted (100.00%) @sacen / proof-of-work-vs-proof-of-stake-in-blockchain-bitcoin-vs-qtum2017/10/27 03:52:27
sacenupvoted (100.00%) @sacen / proof-of-work-vs-proof-of-stake-in-blockchain-bitcoin-vs-qtum
2017/10/27 03:52:27
| voter | sacen |
| author | sacen |
| permlink | proof-of-work-vs-proof-of-stake-in-blockchain-bitcoin-vs-qtum |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16686281/Trx d2a62b8f88cb881bd66cdd9f321ebfbb8bc23675 |
View Raw JSON Data
{
"trx_id": "d2a62b8f88cb881bd66cdd9f321ebfbb8bc23675",
"block": 16686281,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-27T03:52:27",
"op": [
"vote",
{
"voter": "sacen",
"author": "sacen",
"permlink": "proof-of-work-vs-proof-of-stake-in-blockchain-bitcoin-vs-qtum",
"weight": 10000
}
]
}sacenupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish2017/10/27 03:52:21
sacenupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish
2017/10/27 03:52:21
| voter | sacen |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16686279/Trx 0979ab48ce3c2960ce7e4f9bc292b96d79fee1b1 |
View Raw JSON Data
{
"trx_id": "0979ab48ce3c2960ce7e4f9bc292b96d79fee1b1",
"block": 16686279,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-27T03:52:21",
"op": [
"vote",
{
"voter": "sacen",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"weight": 10000
}
]
}sacenpublished a new post: proof-of-work-vs-proof-of-stake-in-blockchain-bitcoin-vs-qtum2017/10/16 09:02:36
sacenpublished a new post: proof-of-work-vs-proof-of-stake-in-blockchain-bitcoin-vs-qtum
2017/10/16 09:02:36
| parent author | |
| parent permlink | cryptocurrency |
| author | sacen |
| permlink | proof-of-work-vs-proof-of-stake-in-blockchain-bitcoin-vs-qtum |
| title | Proof-of-Work vs. Proof-of-Stake in Blockchain: Bitcoin vs. Qtum |
| body | # INTRODUCTION The innovation of the blockchain is really a process to figure out how to update a ledger that is shared on decentralized servers with a new block of transactions, hence reaching a consensus. The idea of proof-of-work and proof-of-stake, are both ways through which consensus is reached in a decentralized or distributed system. This consensus or agreement on what is true or false between nodes on a blockchain is what makes blockchain based cryptocurrencies work.  # BITCOIN: PROOF-OF-WORK Proof-of-work consensus algorithm is a means by which someone can prove to others on a distributed network that they have carried out a significant amount of computational effort. It allows a participant on the blockchain display a forge proof number which can be used to determine how many Joules of electricity that was consumed to create that number. That number is in itself an artifact, a monument of immutability, a proof that you have done the work. Imagine the possibility of presenting a number to a system that has never seen the history of the blockchain, and the node knows the amount of work it took to generate that number. Bitcoin is a monument of immutability, built block by block that cannot be changed or forged without the other person knowing that it has been changed, and without expending the same amount of work/energy it took to create it. • Mining in Bitcoin In Bitcoin, consensus is reached through a process called mining. This is carried out by special nodes on the blockchain known as miners, who earn the right to validate and add the next block of transactions by solving an energy intensive cryptographic puzzle, hence “Proof-of-work”. This puzzle is difficult to compute but easy to verify. Similar to the lottery, the more tickets you buy the greater your chance of winning, the more processing power each computer puts in the greater their chance of winning.  The correctly generated hash is added into the next field as previous hash, putting the blocks in a chain. # Qtum: Proof-of-Stake The Quantum blockchain (Qtum) as stated in their white paper “is a combination of Bitcoin Core, Proof-of-Stake, and the Ethereum Virtual Machine (EVM)”. Its Qtum Core allows for the execution of Smart contracts on a proof-of-stake model. The major difference between proof-of-stake and proof-of-work is that proof-of-stake mainly uses the underlying native assets to stake into the consensus algorithm. A participant stakes a particular amount of his currency in validating a block, with the risk of losing the staked asset (money) if he fails. On the other hand if the validation process is correct, a small fee is gained. In the proof-of-stake consensus algorithm, block validators are selected based on a simulated combination of random selection. Here the group or entity with the highest stake has a higher probability of winning. This consensus algorithm unlike proof-of-work does not come with the creation of new currencies/tokens. Only transaction fees are gained. • HASH FUNCTIONS, MERKLE TREE, AND MINING The idea “Proof-of-work” is linked to other blockchain concepts such as hash functions, Merkle tree, and mining. A brief introduction into these concepts will shed more light into better understanding of the concept. The Bitcoin ledger is based on a Merkle tree data structure that is continuously growing. Its inner workings are built upon what is known as a cryptographic hash. A hash is a one way function that has multiple uses in blockchain and distributed/decentralized systems. It takes any digital media and runs an algorithm on it to produce a unique fixed length digital output known as a hash. This is normally much smaller than the original input. The hash function can equally be likened to a Smoothie Machine. The fruits or veggies are the digital media. Once they are blended together, we cannot get back the digital media. However the taste of the output smoothie is its digital signature. • A SIMPLE EXAMPLE OF HASHING BITCOIN TRANSACTIONS Hashes in combination of peers produce what is called a Merkle tree, which is an essential part of a blockchain for data integrity. Proof-of-work in Bitcoin requires guessing a number known as a [Nonce] which can generate a hash (Alphanumeric character) that begins with four Zeros (0000). The [Mine] button in the figure below runs a function on the following: Block Number, Nonce, Transactions, and Previous Hash, to create the valid new hash. If the generated hash does not begin with four zeros, then it means that the transactions have been altered, or the nonce is incorrect. This in security means tamper evidence. The guessed Nonce is now the proof that the particular block of transactions has been solved. # Here is how it works under the hood: • First step is to add a coinbase transaction, along with a mostly hard coded staking transaction. • Second is the process of preparing blocks which includes transactions from the network. • The third step is to compute a Proof-of-Stake (PoS) “kernel”. • Forth is a computation of “Staking difficulty” • A comparison of the kernel’s hash against the staking difficulty • Continue to a valid Proof-of-stake block if the hash meets the difficulty, else go back to step 1 • Finally, the block header is signed as a confirmation that you own the staking transaction. The Proof-of-stake kernel is a very significant part of the solution, in the sense that its content cannot be easily changed in the block. Another important feature is the staking difficulty, which is taken from Bitcoins’ standard difficulty. If a single coin is staked the standard difficulty is maintained, however staking 2, or 4 coins imply that the difficulty will be halved or quarter respectively. Some restriction mechanisms are put in place for ensuring that the network is not being controlled by a single entity. This is done by putting a limit to the amount of staking coins, consequently a benchmark which the difficulty can be reduced. # CONCLUSION In conclusion, proof-of-work and proof-of-stake algorithms can both coexist. This is because there would be applications that would require a more robust level of immutability, while another may not require that amount of immutability. |
| json metadata | {"tags":["cryptocurrency","bitcoin","qtum","ethereum"],"image":["https://steemitimages.com/DQmToLb4UJ6RJGMQBqbR21LsuWKB9m8c7rZsXg7u1Q9vPNC/DigitalBrain-20150812091648187.jpg","https://steemitimages.com/DQmcdJs3F89QZkNNXvKXL3c3UAgzDvkfmhnsKfJeWJgErAK/tx.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16375809/Trx a7bbd1a7fd4114913892a1d46371740915182e75 |
View Raw JSON Data
{
"trx_id": "a7bbd1a7fd4114913892a1d46371740915182e75",
"block": 16375809,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-16T09:02:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrency",
"author": "sacen",
"permlink": "proof-of-work-vs-proof-of-stake-in-blockchain-bitcoin-vs-qtum",
"title": "Proof-of-Work vs. Proof-of-Stake in Blockchain: Bitcoin vs. Qtum",
"body": "# INTRODUCTION\nThe innovation of the blockchain is really a process to figure out how to update a ledger that is shared on decentralized servers with a new block of transactions, hence reaching a consensus. \n\nThe idea of proof-of-work and proof-of-stake, are both ways through which consensus is reached in a decentralized or distributed system. This consensus or agreement on what is true or false between nodes on a blockchain is what makes blockchain based cryptocurrencies work. \n\n\n\n# BITCOIN: PROOF-OF-WORK\nProof-of-work consensus algorithm is a means by which someone can prove to others on a distributed network that they have carried out a significant amount of computational effort. It allows a participant on the blockchain display a forge proof number which can be used to determine how many Joules of electricity that was consumed to create that number. That number is in itself an artifact, a monument of immutability, a proof that you have done the work. Imagine the possibility of presenting a number to a system that has never seen the history of the blockchain, and the node knows the amount of work it took to generate that number. Bitcoin is a monument of immutability, built block by block that cannot be changed or forged without the other person knowing that it has been changed, and without expending the same amount of work/energy it took to create it.\n\n•\tMining in Bitcoin\nIn Bitcoin, consensus is reached through a process called mining. This is carried out by special nodes on the blockchain known as miners, who earn the right to validate and add the next block of transactions by solving an energy intensive cryptographic puzzle, hence “Proof-of-work”. This puzzle is difficult to compute but easy to verify. Similar to the lottery, the more tickets you buy the greater your chance of winning, the more processing power each computer puts in the greater their chance of winning. \n\n\n\nThe correctly generated hash is added into the next field as previous hash, putting the blocks in a chain.\n\n# Qtum: Proof-of-Stake\nThe Quantum blockchain (Qtum) as stated in their white paper “is a combination of Bitcoin Core, Proof-of-Stake, and the Ethereum Virtual Machine (EVM)”. Its Qtum Core allows for the execution of Smart contracts on a proof-of-stake model. The major difference between proof-of-stake and proof-of-work is that proof-of-stake mainly uses the underlying native assets to stake into the consensus algorithm. \n\nA participant stakes a particular amount of his currency in validating a block, with the risk of losing the staked asset (money) if he fails. On the other hand if the validation process is correct, a small fee is gained. \n\nIn the proof-of-stake consensus algorithm, block validators are selected based on a simulated combination of random selection. Here the group or entity with the highest stake has a higher probability of winning. This consensus algorithm unlike proof-of-work does not come with the creation of new currencies/tokens. Only transaction fees are gained.\n\n•\tHASH FUNCTIONS, MERKLE TREE, AND MINING\nThe idea “Proof-of-work” is linked to other blockchain concepts such as hash functions, Merkle tree, and mining. A brief introduction into these concepts will shed more light into better understanding of the concept.\nThe Bitcoin ledger is based on a Merkle tree data structure that is continuously growing. Its inner workings are built upon what is known as a cryptographic hash. \n\nA hash is a one way function that has multiple uses in blockchain and distributed/decentralized systems. It takes any digital media and runs an algorithm on it to produce a unique fixed length digital output known as a hash. This is normally much smaller than the original input. The hash function can equally be likened to a Smoothie Machine. The fruits or veggies are the digital media. Once they are blended together, we cannot get back the digital media. However the taste of the output smoothie is its digital signature. \n\n•\tA SIMPLE EXAMPLE OF HASHING BITCOIN TRANSACTIONS\nHashes in combination of peers produce what is called a Merkle tree, which is an essential part of a blockchain for data integrity.\n\nProof-of-work in Bitcoin requires guessing a number known as a [Nonce] which can generate a hash (Alphanumeric character) that begins with four Zeros (0000). The [Mine] button in the figure below runs a function on the following: Block Number, Nonce, Transactions, and Previous Hash, to create the valid new hash. If the generated hash does not begin with four zeros, then it means that the transactions have been altered, or the nonce is incorrect. This in security means tamper evidence. The guessed Nonce is now the proof that the particular block of transactions has been solved.\n\n# Here is how it works under the hood:\n•\tFirst step is to add a coinbase transaction, along with a mostly hard coded staking transaction.\n•\tSecond is the process of preparing blocks which includes transactions from the network.\n•\tThe third step is to compute a Proof-of-Stake (PoS) “kernel”.\n•\tForth is a computation of “Staking difficulty”\n•\tA comparison of the kernel’s hash against the staking difficulty\n•\tContinue to a valid Proof-of-stake block if the hash meets the difficulty, else go back to step 1 \n•\tFinally, the block header is signed as a confirmation that you own the staking transaction.\n\nThe Proof-of-stake kernel is a very significant part of the solution, in the sense that its content cannot be easily changed in the block. Another important feature is the staking difficulty, which is taken from Bitcoins’ standard difficulty. If a single coin is staked the standard difficulty is maintained, however staking 2, or 4 coins imply that the difficulty will be halved or quarter respectively. Some restriction mechanisms are put in place for ensuring that the network is not being controlled by a single entity. This is done by putting a limit to the amount of staking coins, consequently a benchmark which the difficulty can be reduced.\n\n# CONCLUSION \nIn conclusion, proof-of-work and proof-of-stake algorithms can both coexist. This is because there would be applications that would require a more robust level of immutability, while another may not require that amount of immutability.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"bitcoin\",\"qtum\",\"ethereum\"],\"image\":[\"https://steemitimages.com/DQmToLb4UJ6RJGMQBqbR21LsuWKB9m8c7rZsXg7u1Q9vPNC/DigitalBrain-20150812091648187.jpg\",\"https://steemitimages.com/DQmcdJs3F89QZkNNXvKXL3c3UAgzDvkfmhnsKfJeWJgErAK/tx.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/10/15 09:20:12
2017/10/15 09:20:12
| parent author | solaris234 |
| parent permlink | re-sacen-re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171014t143838035z |
| author | sacen |
| permlink | re-solaris234-re-sacen-re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171015t092011181z |
| title | |
| body | In my last installation I had error with the passphrase step. So I format the SD card and re-burn Raspbian and did the above steps again. It worked some how. GL |
| json metadata | {"tags":["qtum"],"app":"steemit/0.1"} |
| Transaction Info | Block #16347378/Trx 6687f90d6e601e090303d4c7df824f7a667d9e52 |
View Raw JSON Data
{
"trx_id": "6687f90d6e601e090303d4c7df824f7a667d9e52",
"block": 16347378,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-15T09:20:12",
"op": [
"comment",
{
"parent_author": "solaris234",
"parent_permlink": "re-sacen-re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171014t143838035z",
"author": "sacen",
"permlink": "re-solaris234-re-sacen-re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171015t092011181z",
"title": "",
"body": "In my last installation I had error with the passphrase step. So I format the SD card and re-burn Raspbian and did the above steps again. It worked some how. GL",
"json_metadata": "{\"tags\":[\"qtum\"],\"app\":\"steemit/0.1\"}"
}
]
}2017/10/14 14:38:39
2017/10/14 14:38:39
| parent author | sacen |
| parent permlink | re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z |
| author | solaris234 |
| permlink | re-sacen-re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171014t143838035z |
| title | |
| body | I have exactly the same issue now. Did you manage to make it work? :) |
| json metadata | {"tags":["qtum"],"app":"steemit/0.1"} |
| Transaction Info | Block #16325348/Trx 0517ee34910e5b5c6202d3c860eaeb8af683d5ba |
View Raw JSON Data
{
"trx_id": "0517ee34910e5b5c6202d3c860eaeb8af683d5ba",
"block": 16325348,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-14T14:38:39",
"op": [
"comment",
{
"parent_author": "sacen",
"parent_permlink": "re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z",
"author": "solaris234",
"permlink": "re-sacen-re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171014t143838035z",
"title": "",
"body": "I have exactly the same issue now. Did you manage to make it work? :)",
"json_metadata": "{\"tags\":[\"qtum\"],\"app\":\"steemit/0.1\"}"
}
]
}2017/10/13 16:05:30
2017/10/13 16:05:30
| delegator | steem |
| delegatee | sacen |
| vesting shares | 29830.625670 VESTS |
| Transaction Info | Block #16298294/Trx 25e520bba8eec93443781cd232d48ce7f897303e |
View Raw JSON Data
{
"trx_id": "25e520bba8eec93443781cd232d48ce7f897303e",
"block": 16298294,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T16:05:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sacen",
"vesting_shares": "29830.625670 VESTS"
}
]
}ashish.sharmaupvoted (100.00%) @sacen / bitcoin-gold-another-hard-fork-on-the-bitcoin-blockchain2017/10/13 11:24:57
ashish.sharmaupvoted (100.00%) @sacen / bitcoin-gold-another-hard-fork-on-the-bitcoin-blockchain
2017/10/13 11:24:57
| voter | ashish.sharma |
| author | sacen |
| permlink | bitcoin-gold-another-hard-fork-on-the-bitcoin-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16292691/Trx 8765289efb7389775852c3e01e8413b00b2b64cc |
View Raw JSON Data
{
"trx_id": "8765289efb7389775852c3e01e8413b00b2b64cc",
"block": 16292691,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T11:24:57",
"op": [
"vote",
{
"voter": "ashish.sharma",
"author": "sacen",
"permlink": "bitcoin-gold-another-hard-fork-on-the-bitcoin-blockchain",
"weight": 10000
}
]
}2017/10/13 03:23:21
2017/10/13 03:23:21
| parent author | cryptominder |
| parent permlink | qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3 |
| author | sacen |
| permlink | re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z |
| title | |
| body | @@ -68,116 +68,21 @@ wed -the +your steps -here. https://steemit.com/qtum/@cryptominder/qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3 +. %0A%0AGo |
| json metadata | {"tags":["qtum"],"app":"steemit/0.1"} |
| Transaction Info | Block #16283068/Trx 916864a66fe5c103ad9a60963e4972c51b6dfa69 |
View Raw JSON Data
{
"trx_id": "916864a66fe5c103ad9a60963e4972c51b6dfa69",
"block": 16283068,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T03:23:21",
"op": [
"comment",
{
"parent_author": "cryptominder",
"parent_permlink": "qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3",
"author": "sacen",
"permlink": "re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z",
"title": "",
"body": "@@ -68,116 +68,21 @@\n wed \n-the\n+your\n steps \n-here. https://steemit.com/qtum/@cryptominder/qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3\n+. \n %0A%0AGo\n",
"json_metadata": "{\"tags\":[\"qtum\"],\"app\":\"steemit/0.1\"}"
}
]
}2017/10/13 03:22:30
2017/10/13 03:22:30
| parent author | cryptominder |
| parent permlink | qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3 |
| author | sacen |
| permlink | re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z |
| title | |
| body | I'm having an issue with transferring Qtum into the Wallet, I followed the steps here. https://steemit.com/qtum/@cryptominder/qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3 Got everything running - On Step 10 - Encrypting and Unlocking Your Wallet. $ ~/qtum-wallet/bin/qtum-cli -stdin encryptwallet I can see "unlocked_until": 0, and I set that to 99999999 I created a new account with $ ~/qtum-wallet/bin/qtum-cli getaccountaddress "accountname" Account info show default account "" and "accountname" Does "getaccountaddress" create a new account and key? I assume It does because it shows up on listaccounts. I transferred 1 Qtum from Binance to "accountname" public key. Binance confirm transfer completed. But when I check with $ ~/qtum-wallet/bin/qtum-cli getwalletinfo My balance is 0.0000000 What might I have missed or done wrong? Do I need to select which account to get info on? If so how I select the account I want to display the info? Thanks in advance. |
| json metadata | {"tags":["qtum"],"links":["https://steemit.com/qtum/@cryptominder/qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3"],"app":"steemit/0.1"} |
| Transaction Info | Block #16283051/Trx 8cf26f15d2bba979ec0457ef87173443cdbbde1c |
View Raw JSON Data
{
"trx_id": "8cf26f15d2bba979ec0457ef87173443cdbbde1c",
"block": 16283051,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T03:22:30",
"op": [
"comment",
{
"parent_author": "cryptominder",
"parent_permlink": "qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3",
"author": "sacen",
"permlink": "re-cryptominder-qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3-20171013t032229377z",
"title": "",
"body": "I'm having an issue with transferring Qtum into the Wallet, I followed the steps here. https://steemit.com/qtum/@cryptominder/qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3\n\nGot everything running - On Step 10 - Encrypting and Unlocking Your Wallet. $ ~/qtum-wallet/bin/qtum-cli -stdin encryptwallet\n\nI can see \"unlocked_until\": 0, and I set that to 99999999\n\nI created a new account with $ ~/qtum-wallet/bin/qtum-cli getaccountaddress \"accountname\"\nAccount info show default account \"\" and \"accountname\"\n\nDoes \"getaccountaddress\" create a new account and key? I assume It does because it shows up on listaccounts.\n\nI transferred 1 Qtum from Binance to \"accountname\" public key. Binance confirm transfer completed.\n\nBut when I check with $ ~/qtum-wallet/bin/qtum-cli getwalletinfo\nMy balance is 0.0000000\n\nWhat might I have missed or done wrong?\n\nDo I need to select which account to get info on?\n\nIf so how I select the account I want to display the info?\n\nThanks in advance.",
"json_metadata": "{\"tags\":[\"qtum\"],\"links\":[\"https://steemit.com/qtum/@cryptominder/qtum-staking-tutorial-using-qtumd-on-a-raspberry-pi-3\"],\"app\":\"steemit/0.1\"}"
}
]
}sacenfollowed @mdsaimonuddin2017/10/10 22:01:18
sacenfollowed @mdsaimonuddin
2017/10/10 22:01:18
| required auths | [] |
| required posting auths | ["sacen"] |
| id | follow |
| json | ["follow",{"follower":"sacen","following":"mdsaimonuddin","what":["blog"]}] |
| Transaction Info | Block #16219051/Trx bfa8cf99b3f2c72fce63116368eac920e1f0ac92 |
View Raw JSON Data
{
"trx_id": "bfa8cf99b3f2c72fce63116368eac920e1f0ac92",
"block": 16219051,
"trx_in_block": 33,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-10T22:01:18",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sacen"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sacen\",\"following\":\"mdsaimonuddin\",\"what\":[\"blog\"]}]"
}
]
}2017/10/08 09:19:12
2017/10/08 09:19:12
| parent author | sacen |
| parent permlink | tron-and-why-it-s-price-looking-bullish |
| author | steemitboard |
| permlink | steemitboard-notify-sacen-20171008t091914000z |
| title | |
| body | Congratulations @sacen! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@sacen) Award for the number of upvotes received Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > 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"]} |
| Transaction Info | Block #16146262/Trx bb2940306a84a154fe00b7044cd7354475dcfb96 |
View Raw JSON Data
{
"trx_id": "bb2940306a84a154fe00b7044cd7354475dcfb96",
"block": 16146262,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-08T09:19:12",
"op": [
"comment",
{
"parent_author": "sacen",
"parent_permlink": "tron-and-why-it-s-price-looking-bullish",
"author": "steemitboard",
"permlink": "steemitboard-notify-sacen-20171008t091914000z",
"title": "",
"body": "Congratulations @sacen! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@sacen) Award for the number of upvotes received\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\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\"]}"
}
]
}sacenpublished a new post: bitcoin-gold-another-hard-fork-on-the-bitcoin-blockchain2017/10/08 06:30:18
sacenpublished a new post: bitcoin-gold-another-hard-fork-on-the-bitcoin-blockchain
2017/10/08 06:30:18
| parent author | |
| parent permlink | cryptocurrency |
| author | sacen |
| permlink | bitcoin-gold-another-hard-fork-on-the-bitcoin-blockchain |
| title | BITCOIN GOLD, ANOTHER HARD FORK ON THE BITCOIN BLOCKCHAIN |
| body | @@ -1,8 +1,128 @@ +* Do not make investment decisions based on this article. All contents are personal opinion and not financial advice. %0A%0A !%5Blogo.p |
| json metadata | {"tags":["cryptocurrency","bitcoin","gold","fork","conclusion"],"image":["https://steemitimages.com/DQmNg7gETJmEeXcfKfHZJQ9CmLMKpYas1t4dezauKFpo2Kh/logo.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16142884/Trx accb069f7e5252b1807997c516d2e70dbcf49431 |
View Raw JSON Data
{
"trx_id": "accb069f7e5252b1807997c516d2e70dbcf49431",
"block": 16142884,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-08T06:30:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrency",
"author": "sacen",
"permlink": "bitcoin-gold-another-hard-fork-on-the-bitcoin-blockchain",
"title": "BITCOIN GOLD, ANOTHER HARD FORK ON THE BITCOIN BLOCKCHAIN",
"body": "@@ -1,8 +1,128 @@\n+* Do not make investment decisions based on this article. All contents are personal opinion and not financial advice. %0A%0A\n !%5Blogo.p\n",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"bitcoin\",\"gold\",\"fork\",\"conclusion\"],\"image\":[\"https://steemitimages.com/DQmNg7gETJmEeXcfKfHZJQ9CmLMKpYas1t4dezauKFpo2Kh/logo.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sacenpublished a new post: tron-and-why-it-s-price-looking-bullish2017/10/08 06:29:45
sacenpublished a new post: tron-and-why-it-s-price-looking-bullish
2017/10/08 06:29:45
| parent author | |
| parent permlink | cryptocurrency |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| title | TRON AND WHY IT'S PRICE LOOKING BULLISH |
| body | @@ -1,8 +1,128 @@ +* Do not make investment decisions based on this article. All contents are personal opinion and not financial advice. %0A%0A # ABOUT |
| json metadata | {"tags":["cryptocurrency","trx","tron","peiwo"],"image":["https://steemitimages.com/DQmaJpDkDfdLsBSp2V2eFNQLkbjtpujPdRp17fhsyVUSAdQ/tr.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16142873/Trx 8e943849800d76bacaf30742ab7ecf04b20f40f0 |
View Raw JSON Data
{
"trx_id": "8e943849800d76bacaf30742ab7ecf04b20f40f0",
"block": 16142873,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-08T06:29:45",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrency",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"title": "TRON AND WHY IT'S PRICE LOOKING BULLISH",
"body": "@@ -1,8 +1,128 @@\n+* Do not make investment decisions based on this article. All contents are personal opinion and not financial advice. %0A%0A\n # ABOUT \n",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"trx\",\"tron\",\"peiwo\"],\"image\":[\"https://steemitimages.com/DQmaJpDkDfdLsBSp2V2eFNQLkbjtpujPdRp17fhsyVUSAdQ/tr.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}chandan.maddannaupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish2017/10/08 01:32:21
chandan.maddannaupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish
2017/10/08 01:32:21
| voter | chandan.maddanna |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16136925/Trx 63276a963a69eaacb3bfc9d994454eb429bcc199 |
View Raw JSON Data
{
"trx_id": "63276a963a69eaacb3bfc9d994454eb429bcc199",
"block": 16136925,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-08T01:32:21",
"op": [
"vote",
{
"voter": "chandan.maddanna",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"weight": 10000
}
]
}tomzdupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish2017/10/07 23:43:03
tomzdupvoted (100.00%) @sacen / tron-and-why-it-s-price-looking-bullish
2017/10/07 23:43:03
| voter | tomzd |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16134739/Trx a7482d94d1e6ef2918b5aae20ab56d5d7ef03432 |
View Raw JSON Data
{
"trx_id": "a7482d94d1e6ef2918b5aae20ab56d5d7ef03432",
"block": 16134739,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-07T23:43:03",
"op": [
"vote",
{
"voter": "tomzd",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"weight": 10000
}
]
}sacenreceived 0.044 SBD, 0.047 SP author reward for @sacen / neo-gas-red-pulse-ico-a-comprehensive-guide2017/10/07 23:14:42
sacenreceived 0.044 SBD, 0.047 SP author reward for @sacen / neo-gas-red-pulse-ico-a-comprehensive-guide
2017/10/07 23:14:42
| author | sacen |
| permlink | neo-gas-red-pulse-ico-a-comprehensive-guide |
| sbd payout | 0.044 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 76.148322 VESTS |
| Transaction Info | Block #16134171/Virtual Operation #4 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 16134171,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 4,
"timestamp": "2017-10-07T23:14:42",
"op": [
"author_reward",
{
"author": "sacen",
"permlink": "neo-gas-red-pulse-ico-a-comprehensive-guide",
"sbd_payout": "0.044 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "76.148322 VESTS"
}
]
}ubgupvoted (1.00%) @sacen / tron-and-why-it-s-price-looking-bullish2017/10/07 21:51:24
ubgupvoted (1.00%) @sacen / tron-and-why-it-s-price-looking-bullish
2017/10/07 21:51:24
| voter | ubg |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| weight | 100 (1.00%) |
| Transaction Info | Block #16132506/Trx a122099d433172bff8fae17550e24bb685f7bf42 |
View Raw JSON Data
{
"trx_id": "a122099d433172bff8fae17550e24bb685f7bf42",
"block": 16132506,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-07T21:51:24",
"op": [
"vote",
{
"voter": "ubg",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"weight": 100
}
]
}primetimesportsupvoted (0.02%) @sacen / tron-and-why-it-s-price-looking-bullish2017/10/07 21:46:42
primetimesportsupvoted (0.02%) @sacen / tron-and-why-it-s-price-looking-bullish
2017/10/07 21:46:42
| voter | primetimesports |
| author | sacen |
| permlink | tron-and-why-it-s-price-looking-bullish |
| weight | 2 (0.02%) |
| Transaction Info | Block #16132412/Trx a02f87b02e46170bc010871d4d93833338410c10 |
View Raw JSON Data
{
"trx_id": "a02f87b02e46170bc010871d4d93833338410c10",
"block": 16132412,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-07T21:46:42",
"op": [
"vote",
{
"voter": "primetimesports",
"author": "sacen",
"permlink": "tron-and-why-it-s-price-looking-bullish",
"weight": 2
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779084036
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779084036
},
"rc_account": {
"account": "sacen",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779084036
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://i.imgur.com/54NpKqK.png","cover_image":"https://i.imgur.com/1hKiWNY.png"} |
| JSON METADATA | |
| profile | {"profile_image":"https://i.imgur.com/54NpKqK.png","cover_image":"https://i.imgur.com/1hKiWNY.png"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://i.imgur.com/54NpKqK.png",
"cover_image": "https://i.imgur.com/1hKiWNY.png"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://i.imgur.com/54NpKqK.png",
"cover_image": "https://i.imgur.com/1hKiWNY.png"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM5cQnbwTkh6nhkxW8Mx7uYHZ7ogAXx3EQVDFwwRWUwNgqPx6BTX1/1
Active
Single Signature
Public Keys
STM7F9UfC1g9Arb8ANaGhmzhAe8tCPpJfx4qGVbmzmXU12rosBs1X1/1
Posting
Single Signature
Public Keys
STM57PhNhqo6rG6CGqwyz6PfGcBrUN9m3gv9YTmkFRZvRoYcaf6sm1/1
Memo
STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5cQnbwTkh6nhkxW8Mx7uYHZ7ogAXx3EQVDFwwRWUwNgqPx6BTX",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7F9UfC1g9Arb8ANaGhmzhAe8tCPpJfx4qGVbmzmXU12rosBs1X",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM57PhNhqo6rG6CGqwyz6PfGcBrUN9m3gv9YTmkFRZvRoYcaf6sm",
1
]
]
},
"memo": "STM5Z4VEkNFyhnpwH2TyVv2mUax79Bz6vkr7nG58z6v4NtnP2uJtZ"
}Witness Votes
0 / 30
No active witness votes.
[]