VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.037USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.007SP
├── Own SP
0.635SP
└── Incoming DelegationsDeleg
+4.372SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.635SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.372SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | 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.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1032.712973 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7110.946833 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | mikereams |
| id | 291142 |
| rank | 600,457 |
| reputation | 50530193 |
| created | 2017-08-01T00:58:30 |
| recovery_account | steem |
| proxy | None |
| post_count | 3 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 3 |
| last_post | 2017-08-01T03:12:27 |
| last_root_post | 2017-08-01T03:12:27 |
| last_vote_time | 2017-08-06T14:20:57 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1032.712973 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7110.946833 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-08-01T14:28:30 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM5dA5op67AhiZ692LY5nRavim8VmLqk9gKeNMUwtofGbBj1b3U8",
1
]
],
"weight_threshold": 1
},
"balance": "0.000 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2017-08-01T00:58:30",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779076059
},
"guest_bloggers": [],
"id": 291142,
"json_metadata": "{\"profile\":{\"profile_image\":\"https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg\",\"name\":\"Mike R.\",\"website\":\"http://mikereams.com\",\"location\":\"Atlanta\"}}",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "2017-08-01T14:28:30",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2017-08-01T03:12:27",
"last_root_post": "2017-08-01T03:12:27",
"last_vote_time": "2017-08-06T14:20:57",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4",
"mined": false,
"name": "mikereams",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM54dGxzGkWiNMZx2PHPtMjPsgxBn4jre7Y5U7oWudPQm2fB8EMN",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 3,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6gY7p8ZeurZaup1rUTtui3arqMoEkyJLw8xZJFUPW62nfvvrGf",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg\",\"name\":\"Mike R.\",\"website\":\"http://mikereams.com\",\"location\":\"Atlanta\"}}",
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "7110.946833 VESTS",
"recovery_account": "steem",
"reputation": 50530193,
"reset_account": "null",
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"sbd_balance": "0.000 SBD",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "1032.712973 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779076059
},
"voting_power": 0,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [
"bitcoiner",
"bue",
"good-karma"
],
"witnesses_voted_for": 3,
"rank": 600457
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.372 SP to @mikereams2026/05/18 03:47:39
steemdelegated 4.372 SP to @mikereams
2026/05/18 03:47:39
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 7110.946833 VESTS |
| Transaction Info | Block #106147676/Trx 7f99d1f5555af98f4b0c9e6d55cd23a92bef7124 |
View Raw JSON Data
{
"block": 106147676,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "7110.946833 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-18T03:47:39",
"trx_id": "7f99d1f5555af98f4b0c9e6d55cd23a92bef7124",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 2.704 SP to @mikereams2026/05/12 18:11:09
steemdelegated 2.704 SP to @mikereams
2026/05/12 18:11:09
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 4398.736428 VESTS |
| Transaction Info | Block #105992887/Trx c5c709581eb790808370ae5c03de76bd8818fdf9 |
View Raw JSON Data
{
"block": 105992887,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "4398.736428 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-12T18:11:09",
"trx_id": "c5c709581eb790808370ae5c03de76bd8818fdf9",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 4.380 SP to @mikereams2026/04/26 03:03:00
steemdelegated 4.380 SP to @mikereams
2026/04/26 03:03:00
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 7123.462589 VESTS |
| Transaction Info | Block #105515228/Trx 38c8aeb199c46cfc3f184c9b009659c33ef94dbd |
View Raw JSON Data
{
"block": 105515228,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "7123.462589 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-26T03:03:00",
"trx_id": "38c8aeb199c46cfc3f184c9b009659c33ef94dbd",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 2.730 SP to @mikereams2026/01/23 17:18:03
steemdelegated 2.730 SP to @mikereams
2026/01/23 17:18:03
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 4440.283247 VESTS |
| Transaction Info | Block #102863194/Trx 456e0eb5bf8d5d74265bfac144330e42386f7d75 |
View Raw JSON Data
{
"block": 102863194,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "4440.283247 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-23T17:18:03",
"trx_id": "456e0eb5bf8d5d74265bfac144330e42386f7d75",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 2.831 SP to @mikereams2024/12/17 12:30:54
steemdelegated 2.831 SP to @mikereams
2024/12/17 12:30:54
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 4604.502444 VESTS |
| Transaction Info | Block #91309463/Trx 16e993fcdb49d809b5b40a5d9b7bc4e592845d5b |
View Raw JSON Data
{
"block": 91309463,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "4604.502444 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-17T12:30:54",
"trx_id": "16e993fcdb49d809b5b40a5d9b7bc4e592845d5b",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 2.935 SP to @mikereams2023/11/14 04:12:39
steemdelegated 2.935 SP to @mikereams
2023/11/14 04:12:39
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 4773.635976 VESTS |
| Transaction Info | Block #79863636/Trx e31a201adac7f6b5e2d34998f82f3532a3d5a023 |
View Raw JSON Data
{
"block": 79863636,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "4773.635976 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-14T04:12:39",
"trx_id": "e31a201adac7f6b5e2d34998f82f3532a3d5a023",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 4.741 SP to @mikereams2023/09/22 01:59:39
steemdelegated 4.741 SP to @mikereams
2023/09/22 01:59:39
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 7710.914762 VESTS |
| Transaction Info | Block #78352813/Trx d130d0c79b8a1e1170496708ab6c29a6bc93fb2d |
View Raw JSON Data
{
"block": 78352813,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "7710.914762 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-22T01:59:39",
"trx_id": "d130d0c79b8a1e1170496708ab6c29a6bc93fb2d",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 4.877 SP to @mikereams2022/11/03 15:16:42
steemdelegated 4.877 SP to @mikereams
2022/11/03 15:16:42
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 7932.596200 VESTS |
| Transaction Info | Block #69117530/Trx d98eec504d600da0f1a1a62ebe48bb91017ddeff |
View Raw JSON Data
{
"block": 69117530,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "7932.596200 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T15:16:42",
"trx_id": "d98eec504d600da0f1a1a62ebe48bb91017ddeff",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 5.012 SP to @mikereams2022/01/17 20:43:21
steemdelegated 5.012 SP to @mikereams
2022/01/17 20:43:21
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 8152.703801 VESTS |
| Transaction Info | Block #60821072/Trx 5c5105972ce678260052233c71f151f5fce96b0e |
View Raw JSON Data
{
"block": 60821072,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "8152.703801 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T20:43:21",
"trx_id": "5c5105972ce678260052233c71f151f5fce96b0e",
"trx_in_block": 8,
"virtual_op": 0
}steemdelegated 5.126 SP to @mikereams2021/06/14 04:00:39
steemdelegated 5.126 SP to @mikereams
2021/06/14 04:00:39
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 8336.898089 VESTS |
| Transaction Info | Block #54611535/Trx 13197dbc70677b6553d0738024513c24ef0f9600 |
View Raw JSON Data
{
"block": 54611535,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "8336.898089 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-14T04:00:39",
"trx_id": "13197dbc70677b6553d0738024513c24ef0f9600",
"trx_in_block": 7,
"virtual_op": 0
}steemdelegated 5.241 SP to @mikereams2020/12/11 14:15:24
steemdelegated 5.241 SP to @mikereams
2020/12/11 14:15:24
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 8524.320063 VESTS |
| Transaction Info | Block #49358872/Trx cbca6714f2b1af1841a5d63138cd73cb42ed6845 |
View Raw JSON Data
{
"block": 49358872,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "8524.320063 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T14:15:24",
"trx_id": "cbca6714f2b1af1841a5d63138cd73cb42ed6845",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 1.176 SP to @mikereams2020/12/06 07:51:27
steemdelegated 1.176 SP to @mikereams
2020/12/06 07:51:27
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49210405/Trx a921d42bc14483a9e29c024332e574e1378e65ed |
View Raw JSON Data
{
"block": 49210405,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T07:51:27",
"trx_id": "a921d42bc14483a9e29c024332e574e1378e65ed",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 5.245 SP to @mikereams2020/12/05 17:53:12
steemdelegated 5.245 SP to @mikereams
2020/12/05 17:53:12
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 8530.527917 VESTS |
| Transaction Info | Block #49193958/Trx f6755487a839678dea2eaaa691180bcef0a83cdb |
View Raw JSON Data
{
"block": 49193958,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "8530.527917 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T17:53:12",
"trx_id": "f6755487a839678dea2eaaa691180bcef0a83cdb",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 1.180 SP to @mikereams2020/11/02 22:08:24
steemdelegated 1.180 SP to @mikereams
2020/11/02 22:08:24
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48265459/Trx 7cf5d8f30201972c4aee7690df4afe1189b69101 |
View Raw JSON Data
{
"block": 48265459,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-02T22:08:24",
"trx_id": "7cf5d8f30201972c4aee7690df4afe1189b69101",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 5.369 SP to @mikereams2020/05/09 08:52:24
steemdelegated 5.369 SP to @mikereams
2020/05/09 08:52:24
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 8733.333276 VESTS |
| Transaction Info | Block #43220706/Trx f762d500265a5aeb84cc6e11997d4c3cf4d86fea |
View Raw JSON Data
{
"block": 43220706,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "8733.333276 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T08:52:24",
"trx_id": "f762d500265a5aeb84cc6e11997d4c3cf4d86fea",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 1.201 SP to @mikereams2020/05/08 12:57:06
steemdelegated 1.201 SP to @mikereams
2020/05/08 12:57:06
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43197363/Trx 5041e4809fc91ea712e124e873b6314e750de189 |
View Raw JSON Data
{
"block": 43197363,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T12:57:06",
"trx_id": "5041e4809fc91ea712e124e873b6314e750de189",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 5.377 SP to @mikereams2020/04/16 01:53:30
steemdelegated 5.377 SP to @mikereams
2020/04/16 01:53:30
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 8746.220724 VESTS |
| Transaction Info | Block #42567522/Trx 8f547330e35c3e31f5e563c23d8aa5d47c6482a8 |
View Raw JSON Data
{
"block": 42567522,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "8746.220724 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-04-16T01:53:30",
"trx_id": "8f547330e35c3e31f5e563c23d8aa5d47c6482a8",
"trx_in_block": 20,
"virtual_op": 0
}hasanraza90replied to @mikereams / q0lckk2019/11/07 08:50:45
hasanraza90replied to @mikereams / q0lckk
2019/11/07 08:50:45
| author | hasanraza90 |
| body | Good article, I agree that <a href="https://www.goodcore.co.uk/blog/legacy-systems/">legacy system</a> does not support the modern-day needs, but unfortunately some people have really got accustomed to them and will hardly will ever switch to the latest option. |
| json metadata | {"links":["https://www.goodcore.co.uk/blog/legacy-systems/"],"app":"steemit/0.1"} |
| parent author | mikereams |
| parent permlink | prisoner-of-legacy-systems |
| permlink | q0lckk |
| title | |
| Transaction Info | Block #37961863/Trx ca384f9b501397d0603a53e424ac7e9367c031f9 |
View Raw JSON Data
{
"block": 37961863,
"op": [
"comment",
{
"author": "hasanraza90",
"body": "Good article, I agree that <a href=\"https://www.goodcore.co.uk/blog/legacy-systems/\">legacy system</a> does not support the modern-day needs, but unfortunately some people have really got accustomed to them and will hardly will ever switch to the latest option.",
"json_metadata": "{\"links\":[\"https://www.goodcore.co.uk/blog/legacy-systems/\"],\"app\":\"steemit/0.1\"}",
"parent_author": "mikereams",
"parent_permlink": "prisoner-of-legacy-systems",
"permlink": "q0lckk",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-11-07T08:50:45",
"trx_id": "ca384f9b501397d0603a53e424ac7e9367c031f9",
"trx_in_block": 18,
"virtual_op": 0
}2019/08/01 01:26:36
2019/08/01 01:26:36
| author | steemitboard |
| body | Congratulations @mikereams! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@mikereams/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/@mikereams) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=mikereams)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | mikereams |
| parent permlink | prisoner-of-legacy-systems |
| permlink | steemitboard-notify-mikereams-20190801t012635000z |
| title | |
| Transaction Info | Block #35158951/Trx 9b1121fe5ecc25019afc9fac1979432e412ab491 |
View Raw JSON Data
{
"block": 35158951,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @mikereams! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@mikereams/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/@mikereams) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=mikereams)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "mikereams",
"parent_permlink": "prisoner-of-legacy-systems",
"permlink": "steemitboard-notify-mikereams-20190801t012635000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-01T01:26:36",
"trx_id": "9b1121fe5ecc25019afc9fac1979432e412ab491",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 5.498 SP to @mikereams2019/05/12 18:59:36
steemdelegated 5.498 SP to @mikereams
2019/05/12 18:59:36
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 8941.837537 VESTS |
| Transaction Info | Block #32850393/Trx 2516cbcbaa783b33cd297b9b5300ec711475a591 |
View Raw JSON Data
{
"block": 32850393,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "8941.837537 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-12T18:59:36",
"trx_id": "2516cbcbaa783b33cd297b9b5300ec711475a591",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 5.620 SP to @mikereams2018/05/16 22:59:36
steemdelegated 5.620 SP to @mikereams
2018/05/16 22:59:36
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 9141.448405 VESTS |
| Transaction Info | Block #22493093/Trx 812e788f7f64e092de61cb6729bbccbb18e33347 |
View Raw JSON Data
{
"block": 22493093,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "9141.448405 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-16T22:59:36",
"trx_id": "812e788f7f64e092de61cb6729bbccbb18e33347",
"trx_in_block": 11,
"virtual_op": 0
}steemdelegated 18.256 SP to @mikereams2018/01/09 06:42:39
steemdelegated 18.256 SP to @mikereams
2018/01/09 06:42:39
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 29692.476319 VESTS |
| Transaction Info | Block #18819649/Trx 1222b7db99ef044654c1adee2bb47b5dc10f4c7a |
View Raw JSON Data
{
"block": 18819649,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "29692.476319 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-01-09T06:42:39",
"trx_id": "1222b7db99ef044654c1adee2bb47b5dc10f4c7a",
"trx_in_block": 51,
"virtual_op": 0
}mikereamsupvoted (100.00%) @prakashs / the-truth-of-blockchain-miner-pro2017/12/13 12:40:51
mikereamsupvoted (100.00%) @prakashs / the-truth-of-blockchain-miner-pro
2017/12/13 12:40:51
| author | prakashs |
| permlink | the-truth-of-blockchain-miner-pro |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18049786/Trx 3e89e5ba5fc49175b131ea151f52ae1e8236085f |
View Raw JSON Data
{
"block": 18049786,
"op": [
"vote",
{
"author": "prakashs",
"permlink": "the-truth-of-blockchain-miner-pro",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-12-13T12:40:51",
"trx_id": "3e89e5ba5fc49175b131ea151f52ae1e8236085f",
"trx_in_block": 7,
"virtual_op": 0
}2017/08/08 19:13:27
2017/08/08 19:13:27
| author | lequasaltsmal |
| body | Interesting thoughts |
| json metadata | {"tags":["blockchain"],"app":"steemit/0.1"} |
| parent author | mikereams |
| parent permlink | my-bitcoin-blockchain-analysis |
| permlink | re-mikereams-my-bitcoin-blockchain-analysis-20170808t191357974z |
| title | |
| Transaction Info | Block #14403027/Trx 65aab6c343133a6d12e9541c7c39a733febf34b0 |
View Raw JSON Data
{
"block": 14403027,
"op": [
"comment",
{
"author": "lequasaltsmal",
"body": "Interesting thoughts",
"json_metadata": "{\"tags\":[\"blockchain\"],\"app\":\"steemit/0.1\"}",
"parent_author": "mikereams",
"parent_permlink": "my-bitcoin-blockchain-analysis",
"permlink": "re-mikereams-my-bitcoin-blockchain-analysis-20170808t191357974z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-08-08T19:13:27",
"trx_id": "65aab6c343133a6d12e9541c7c39a733febf34b0",
"trx_in_block": 19,
"virtual_op": 0
}2017/08/06 14:20:57
2017/08/06 14:20:57
| author | bookingteam.com |
| permlink | what-you-need-to-know-in-the-vacation-rental-industry-08-05-2017 |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14339673/Trx 090c2ab2ab0102e2fcbc1a9972dbe995ae7578fc |
View Raw JSON Data
{
"block": 14339673,
"op": [
"vote",
{
"author": "bookingteam.com",
"permlink": "what-you-need-to-know-in-the-vacation-rental-industry-08-05-2017",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-06T14:20:57",
"trx_id": "090c2ab2ab0102e2fcbc1a9972dbe995ae7578fc",
"trx_in_block": 3,
"virtual_op": 0
}2017/08/06 14:20:45
2017/08/06 14:20:45
| author | hardfork-series |
| permlink | announcing-the-world-s-first-crypto-focused-mini-series-powered-by-steemit |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14339669/Trx b13b63bf9f057c8f34099b55bba5098fedc08ef6 |
View Raw JSON Data
{
"block": 14339669,
"op": [
"vote",
{
"author": "hardfork-series",
"permlink": "announcing-the-world-s-first-crypto-focused-mini-series-powered-by-steemit",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-06T14:20:45",
"trx_id": "b13b63bf9f057c8f34099b55bba5098fedc08ef6",
"trx_in_block": 6,
"virtual_op": 0
}steemdelegated 18.410 SP to @mikereams2017/08/04 04:25:45
steemdelegated 18.410 SP to @mikereams
2017/08/04 04:25:45
| delegatee | mikereams |
| delegator | steem |
| vesting shares | 29943.287027 VESTS |
| Transaction Info | Block #14270403/Trx 669bb566cf37823398d7f24f508ad1043d1a08cd |
View Raw JSON Data
{
"block": 14270403,
"op": [
"delegate_vesting_shares",
{
"delegatee": "mikereams",
"delegator": "steem",
"vesting_shares": "29943.287027 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-04T04:25:45",
"trx_id": "669bb566cf37823398d7f24f508ad1043d1a08cd",
"trx_in_block": 3,
"virtual_op": 0
}2017/08/01 21:03:12
2017/08/01 21:03:12
| author | steemitboard |
| body | Congratulations @mikereams! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@mikereams) You made your First Vote [](http://steemitboard.com/@mikereams) You published your First Post [](http://steemitboard.com/@mikereams) You made your First Comment [](http://steemitboard.com/@mikereams) You got a First Vote [](http://steemitboard.com/@mikereams) Award for the number of upvotes 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"]} |
| parent author | mikereams |
| parent permlink | prisoner-of-legacy-systems |
| permlink | steemitboard-notify-mikereams-20170801t210314000z |
| title | |
| Transaction Info | Block #14203979/Trx 609d2fb4c114adc1984dc112c0d8b0c4b2b164e2 |
View Raw JSON Data
{
"block": 14203979,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @mikereams! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@mikereams) You made your First Vote\n[](http://steemitboard.com/@mikereams) You published your First Post\n[](http://steemitboard.com/@mikereams) You made your First Comment\n[](http://steemitboard.com/@mikereams) You got a First Vote\n[](http://steemitboard.com/@mikereams) Award for the number of upvotes\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\"]}",
"parent_author": "mikereams",
"parent_permlink": "prisoner-of-legacy-systems",
"permlink": "steemitboard-notify-mikereams-20170801t210314000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T21:03:12",
"trx_id": "609d2fb4c114adc1984dc112c0d8b0c4b2b164e2",
"trx_in_block": 38,
"virtual_op": 0
}2017/08/01 14:36:30
2017/08/01 14:36:30
| account | mikereams |
| approve | true |
| witness | bue |
| Transaction Info | Block #14196246/Trx 6c34145820e8200449d573bdf868ff3300e9d0de |
View Raw JSON Data
{
"block": 14196246,
"op": [
"account_witness_vote",
{
"account": "mikereams",
"approve": true,
"witness": "bue"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:36:30",
"trx_id": "6c34145820e8200449d573bdf868ff3300e9d0de",
"trx_in_block": 3,
"virtual_op": 0
}mikereamsvoted for witness @bitcoiner2017/08/01 14:36:21
mikereamsvoted for witness @bitcoiner
2017/08/01 14:36:21
| account | mikereams |
| approve | true |
| witness | bitcoiner |
| Transaction Info | Block #14196243/Trx eab0ca72e5585c2502932cb4a9b34aa6d2317920 |
View Raw JSON Data
{
"block": 14196243,
"op": [
"account_witness_vote",
{
"account": "mikereams",
"approve": true,
"witness": "bitcoiner"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:36:21",
"trx_id": "eab0ca72e5585c2502932cb4a9b34aa6d2317920",
"trx_in_block": 10,
"virtual_op": 0
}mikereamsvoted for witness @good-karma2017/08/01 14:35:48
mikereamsvoted for witness @good-karma
2017/08/01 14:35:48
| account | mikereams |
| approve | true |
| witness | good-karma |
| Transaction Info | Block #14196232/Trx 8c8c0f0add9e58094f2329309d3a4c55d187d201 |
View Raw JSON Data
{
"block": 14196232,
"op": [
"account_witness_vote",
{
"account": "mikereams",
"approve": true,
"witness": "good-karma"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:35:48",
"trx_id": "8c8c0f0add9e58094f2329309d3a4c55d187d201",
"trx_in_block": 31,
"virtual_op": 0
}mikereamsupvoted (100.00%) @modprobe / i-looked-into-segwit-and-here-s-what-i-saw2017/08/01 14:34:36
mikereamsupvoted (100.00%) @modprobe / i-looked-into-segwit-and-here-s-what-i-saw
2017/08/01 14:34:36
| author | modprobe |
| permlink | i-looked-into-segwit-and-here-s-what-i-saw |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14196208/Trx 57203097d0ab355cca7e9ced53ed69dc05aac284 |
View Raw JSON Data
{
"block": 14196208,
"op": [
"vote",
{
"author": "modprobe",
"permlink": "i-looked-into-segwit-and-here-s-what-i-saw",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:34:36",
"trx_id": "57203097d0ab355cca7e9ced53ed69dc05aac284",
"trx_in_block": 8,
"virtual_op": 0
}mikereamsupvoted (100.00%) @ghasemkiani / how-did-common-websites-look-10-years-ago2017/08/01 14:34:15
mikereamsupvoted (100.00%) @ghasemkiani / how-did-common-websites-look-10-years-ago
2017/08/01 14:34:15
| author | ghasemkiani |
| permlink | how-did-common-websites-look-10-years-ago |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14196201/Trx a3eb77e82ba593a1d191129eaf89279beef3f6ee |
View Raw JSON Data
{
"block": 14196201,
"op": [
"vote",
{
"author": "ghasemkiani",
"permlink": "how-did-common-websites-look-10-years-ago",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:34:15",
"trx_id": "a3eb77e82ba593a1d191129eaf89279beef3f6ee",
"trx_in_block": 11,
"virtual_op": 0
}2017/08/01 14:30:33
2017/08/01 14:30:33
| author | michiel |
| permlink | re-thecryptofiend-warning-scammers-now-using-bitcoin-bcc-split-to-scam-people-with-fake-wallet-links-20170731t080028110z |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14196127/Trx 2c1310e2aeb006d33ca81c31dfcf59d397d3d690 |
View Raw JSON Data
{
"block": 14196127,
"op": [
"vote",
{
"author": "michiel",
"permlink": "re-thecryptofiend-warning-scammers-now-using-bitcoin-bcc-split-to-scam-people-with-fake-wallet-links-20170731t080028110z",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:30:33",
"trx_id": "2c1310e2aeb006d33ca81c31dfcf59d397d3d690",
"trx_in_block": 15,
"virtual_op": 0
}2017/08/01 14:28:54
2017/08/01 14:28:54
| author | lykencrypto |
| permlink | good-morning-again-steemit-family-short-quote-of-faith-day-6-patience-is-not-determined-by-your-ability-to-wait-but-rather-how |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14196094/Trx c08ff4f4a5d759ca4c6cee9b2d1422a3e3d1d7e6 |
View Raw JSON Data
{
"block": 14196094,
"op": [
"vote",
{
"author": "lykencrypto",
"permlink": "good-morning-again-steemit-family-short-quote-of-faith-day-6-patience-is-not-determined-by-your-ability-to-wait-but-rather-how",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:28:54",
"trx_id": "c08ff4f4a5d759ca4c6cee9b2d1422a3e3d1d7e6",
"trx_in_block": 14,
"virtual_op": 0
}mikereamsupdated their account properties2017/08/01 14:28:30
mikereamsupdated their account properties
2017/08/01 14:28:30
| account | mikereams |
| json metadata | {"profile":{"profile_image":"https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg","name":"Mike R.","website":"http://mikereams.com","location":"Atlanta"}} |
| memo key | STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4 |
| Transaction Info | Block #14196086/Trx 9cfc8f5e3caaed16407fdcdb43905afa092d8a0c |
View Raw JSON Data
{
"block": 14196086,
"op": [
"account_update",
{
"account": "mikereams",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg\",\"name\":\"Mike R.\",\"website\":\"http://mikereams.com\",\"location\":\"Atlanta\"}}",
"memo_key": "STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:28:30",
"trx_id": "9cfc8f5e3caaed16407fdcdb43905afa092d8a0c",
"trx_in_block": 22,
"virtual_op": 0
}2017/08/01 14:27:18
2017/08/01 14:27:18
| author | charlieshrem |
| permlink | tutorial-how-to-display-the-steem-and-bitcoin-price-in-your-macbook-touch-bar |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14196062/Trx 9cc11f1003743ba763b8216b4f214c1428190c0c |
View Raw JSON Data
{
"block": 14196062,
"op": [
"vote",
{
"author": "charlieshrem",
"permlink": "tutorial-how-to-display-the-steem-and-bitcoin-price-in-your-macbook-touch-bar",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:27:18",
"trx_id": "9cc11f1003743ba763b8216b4f214c1428190c0c",
"trx_in_block": 39,
"virtual_op": 0
}2017/08/01 14:27:03
2017/08/01 14:27:03
| author | krystle |
| permlink | i-should-be-writing-about-gaining-1000-followers-instead-i-have-to-address-a-bigger-issue |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14196057/Trx 5a9eedaa160b33507e89fd113078af75a63b3f9e |
View Raw JSON Data
{
"block": 14196057,
"op": [
"vote",
{
"author": "krystle",
"permlink": "i-should-be-writing-about-gaining-1000-followers-instead-i-have-to-address-a-bigger-issue",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:27:03",
"trx_id": "5a9eedaa160b33507e89fd113078af75a63b3f9e",
"trx_in_block": 22,
"virtual_op": 0
}2017/08/01 14:26:39
2017/08/01 14:26:39
| author | kingscrown |
| permlink | watch-out-electron-moves-electrum-files-the-bcc-wallet-for-easy-redeem-of-coins |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14196049/Trx 8d5a865e12b05652cce5452027c581b69dfe8b0b |
View Raw JSON Data
{
"block": 14196049,
"op": [
"vote",
{
"author": "kingscrown",
"permlink": "watch-out-electron-moves-electrum-files-the-bcc-wallet-for-easy-redeem-of-coins",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:26:39",
"trx_id": "8d5a865e12b05652cce5452027c581b69dfe8b0b",
"trx_in_block": 16,
"virtual_op": 0
}2017/08/01 14:26:36
2017/08/01 14:26:36
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"lannocc","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14196048/Trx c14d9a5c41199e11c425c6ea9fae0e314b88ca3e |
View Raw JSON Data
{
"block": 14196048,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"lannocc\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:26:36",
"trx_id": "c14d9a5c41199e11c425c6ea9fae0e314b88ca3e",
"trx_in_block": 0,
"virtual_op": 0
}mikereamsfollowed @joanaltres2017/08/01 14:26:24
mikereamsfollowed @joanaltres
2017/08/01 14:26:24
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"joanaltres","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14196044/Trx 0bc1e633bf434d354cdea7e6d1329d0e7f8825b5 |
View Raw JSON Data
{
"block": 14196044,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"joanaltres\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:26:24",
"trx_id": "0bc1e633bf434d354cdea7e6d1329d0e7f8825b5",
"trx_in_block": 20,
"virtual_op": 0
}mikereamsfollowed @ghasemkiani2017/08/01 14:26:18
mikereamsfollowed @ghasemkiani
2017/08/01 14:26:18
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"ghasemkiani","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14196042/Trx 4787ea8d4788a249b8e59b7a767b8f1abbe357a8 |
View Raw JSON Data
{
"block": 14196042,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"ghasemkiani\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:26:18",
"trx_id": "4787ea8d4788a249b8e59b7a767b8f1abbe357a8",
"trx_in_block": 4,
"virtual_op": 0
}mikereamsfollowed @gamemusic2017/08/01 14:26:06
mikereamsfollowed @gamemusic
2017/08/01 14:26:06
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"gamemusic","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14196038/Trx 32087a4f125d3b6453c44b1362c15ad8bf2dad85 |
View Raw JSON Data
{
"block": 14196038,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"gamemusic\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:26:06",
"trx_id": "32087a4f125d3b6453c44b1362c15ad8bf2dad85",
"trx_in_block": 21,
"virtual_op": 0
}mikereamsfollowed @bilalhaider2017/08/01 14:25:21
mikereamsfollowed @bilalhaider
2017/08/01 14:25:21
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"bilalhaider","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14196023/Trx e83abc9eaa8de2e40a9e8e3fc09498f84ac585e8 |
View Raw JSON Data
{
"block": 14196023,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"bilalhaider\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T14:25:21",
"trx_id": "e83abc9eaa8de2e40a9e8e3fc09498f84ac585e8",
"trx_in_block": 19,
"virtual_op": 0
}2017/08/01 05:04:03
2017/08/01 05:04:03
| author | steemcleaners |
| body | Using irrelevant tags, especially popular tags, makes it hard to find good and relevant content. Please try to use only relevant tags when posting! #steemit Please only use the “steemit” tag for articles distinctly related to Steemit, the website, itself. |
| json metadata | {"tags":["steemit","blockchain"],"app":"steemit/0.1"} |
| parent author | mikereams |
| parent permlink | my-bitcoin-blockchain-analysis |
| permlink | re-mikereams-my-bitcoin-blockchain-analysis-20170801t050401663z |
| title | |
| Transaction Info | Block #14184808/Trx 9ae7a271936037a651aa1ce41ce94e9f26fe0cbd |
View Raw JSON Data
{
"block": 14184808,
"op": [
"comment",
{
"author": "steemcleaners",
"body": "Using irrelevant tags, especially popular tags, makes it hard to find good and relevant content.\nPlease try to use only relevant tags when posting! \n \n#steemit\n \nPlease only use the “steemit” tag for articles distinctly related to Steemit, the website, itself.",
"json_metadata": "{\"tags\":[\"steemit\",\"blockchain\"],\"app\":\"steemit/0.1\"}",
"parent_author": "mikereams",
"parent_permlink": "my-bitcoin-blockchain-analysis",
"permlink": "re-mikereams-my-bitcoin-blockchain-analysis-20170801t050401663z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T05:04:03",
"trx_id": "9ae7a271936037a651aa1ce41ce94e9f26fe0cbd",
"trx_in_block": 7,
"virtual_op": 0
}2017/08/01 03:17:12
2017/08/01 03:17:12
| author | joshsigurdson |
| permlink | the-future-of-bitcoin-and-steem-may-be-limitless-jeff-berwick-talks-cryptocurrencies |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182675/Trx 309ab023abf24ac307dcb1eb17132b6ef2c36779 |
View Raw JSON Data
{
"block": 14182675,
"op": [
"vote",
{
"author": "joshsigurdson",
"permlink": "the-future-of-bitcoin-and-steem-may-be-limitless-jeff-berwick-talks-cryptocurrencies",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:17:12",
"trx_id": "309ab023abf24ac307dcb1eb17132b6ef2c36779",
"trx_in_block": 8,
"virtual_op": 0
}2017/08/01 03:16:54
2017/08/01 03:16:54
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"ocd","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14182669/Trx 2bd657d8337dcef24a2987c3a09eb3b869f13129 |
View Raw JSON Data
{
"block": 14182669,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"ocd\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:16:54",
"trx_id": "2bd657d8337dcef24a2987c3a09eb3b869f13129",
"trx_in_block": 6,
"virtual_op": 0
}mikereamsupvoted (100.00%) @ocd / ocd-daily-issue-262017/08/01 03:16:30
mikereamsupvoted (100.00%) @ocd / ocd-daily-issue-26
2017/08/01 03:16:30
| author | ocd |
| permlink | ocd-daily-issue-26 |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182661/Trx 0b6d78a98061312cec68fad66f67d780c66fa88c |
View Raw JSON Data
{
"block": 14182661,
"op": [
"vote",
{
"author": "ocd",
"permlink": "ocd-daily-issue-26",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:16:30",
"trx_id": "0b6d78a98061312cec68fad66f67d780c66fa88c",
"trx_in_block": 10,
"virtual_op": 0
}unprovokedupvoted (3.00%) @mikereams / prisoner-of-legacy-systems2017/08/01 03:16:24
unprovokedupvoted (3.00%) @mikereams / prisoner-of-legacy-systems
2017/08/01 03:16:24
| author | mikereams |
| permlink | prisoner-of-legacy-systems |
| voter | unprovoked |
| weight | 300 (3.00%) |
| Transaction Info | Block #14182659/Trx d9d19a36fdc6076354c2f934e95fda8d5815e13e |
View Raw JSON Data
{
"block": 14182659,
"op": [
"vote",
{
"author": "mikereams",
"permlink": "prisoner-of-legacy-systems",
"voter": "unprovoked",
"weight": 300
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:16:24",
"trx_id": "d9d19a36fdc6076354c2f934e95fda8d5815e13e",
"trx_in_block": 9,
"virtual_op": 0
}mikereamsupvoted (100.00%) @markwhittam / please-steemit-help-me-save-a-life2017/08/01 03:15:45
mikereamsupvoted (100.00%) @markwhittam / please-steemit-help-me-save-a-life
2017/08/01 03:15:45
| author | markwhittam |
| permlink | please-steemit-help-me-save-a-life |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182646/Trx bca4e1dc31ab4bb81e0af3a06dccf926427d0a30 |
View Raw JSON Data
{
"block": 14182646,
"op": [
"vote",
{
"author": "markwhittam",
"permlink": "please-steemit-help-me-save-a-life",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:15:45",
"trx_id": "bca4e1dc31ab4bb81e0af3a06dccf926427d0a30",
"trx_in_block": 12,
"virtual_op": 0
}mikereamspublished a new post: my-bitcoin-blockchain-analysis2017/08/01 03:14:42
mikereamspublished a new post: my-bitcoin-blockchain-analysis
2017/08/01 03:14:42
| author | mikereams |
| body | ## Analysis ## Blockchain technology derived from the Bitcoin stack promises much in the era of digital business. The Bitcoin blockchain is currently the primary mechanism for implementing a decentralized, distributed ledger of cryptocurrency transactions — although alternatives are have been underway. There is a contradiction between the requirements of a private blockchain and the capabilities of public blockchain, which result from its original purpose of creating a value-exchange system that is resistant to control by a single central authority. This will be an ongoing tension, similar to the dynamic between public and private cloud. Blockchain platforms, also known as distributed ledger technology and termed "metacoin platforms", remain at the peak of the Hype Cycle curve. This means inflated expectations still abound, the result of a lack of knowledge of the technology and what problems it can be applied to. ## The Essence of Blockchain Technology ## Many enterprises are considering blockchain technology but perceive it to be a tool or platform for database management, data integration, application integration, identity management, records management and/or business process management. In its current form, blockchain technology is none of these, although it may evolve to eventually encompass several of these areas. The only blockchain platform that is proven mature, secure and rock solid in production is the Bitcoin blockchain (although, additionally, the Ethereum platform has recently gained credibility). The Bitcoin blockchain is conceptually simple: a flat file, a sequential list of transaction records denominated in bitcoin currency. This record of transactions (distributed ledger) is implemented as direct-to-file-system storage, meaning there is no use of a conventional database management system (DBMS) (except for in a secondary role as a query mechanism for metadata). Instead of relying on a DBMS tool or platform, the Bitcoin ledger is a manually coded data structure that consists of a sequential chain of blocks, in which each block comprises several hundred transaction records appended to the rest of the chain at roughly 10-minute intervals per block. The entire dataset is massively replicated across thousands of nodes in a peer-to-peer network, each one running software that implements the Bitcoin protocol. The system is designed to avoid reliance on any one server, on any one organization or on any one software implementation. Instead, the blockchain represents a trusted record within an untrusted environment — an authoritative record of significant events, where the truth of the record is defined by the majority of nodes in the peer-to-peer network (strictly speaking, by the majority of computational power). Despite this successful track record, the Bitcoin blockchain has known limitations in scalability, flexibility and governance. Due to design decisions made that favor the full scope of the "Byzantine Generals' problem," the system will favor security and data integrity over scalability and flexibility. Regarding throughput, the entire system has a theoretical capacity of only seven transactions per second (tps) maximum (in practice, this number is about three tps). This transaction volume is not for a single application, but for the entire network — the entire world of bitcoin. ## A Crowded Competitive Arena That Continues to Grow ## Over the past two years, there has been a proliferation of blockchain technologies. Some of these are directly competitive with the Bitcoin technology stack, and therefore are designed as public blockchains (similar to Bitcoin, they are integrated with a value token or digital currency). Others are oriented to private blockchain deployments (private networks where the number of participants is stable; all nodes are known; and there is a mechanism that grants permission to participate, which might be a centralized identity management system). Although choosing the eventual winner for this sector is unlikely, given that it may not even be on the market, it is possible to state what that winner will look like. Here are the characteristics of a winning blockchain platform: * Open source — this is necessary to cultivate a rich and diverse ecosystem and accelerate adoption through network effect. * Modular architecture with layers of programmability and customizability — as above, this cultivates an ecosystem and enables market adoption. * Global scale — scalability, performance and efficiency are essential if blockchain is to become the foundation for the "Internet of Money." * Multiple implementations of the core protocol — multiple, independently developed implementations ensure that the protocol is understood, well-defined and adds resistance to possible attacks (as occurred with the Ethereum platform in September 2016). This requires there to be an accurate and precise specification of the core protocol, as opposed to relying on one codebase that is not documented. * Hardened through public blockchain deployment — this is the only way to ensure that the system is secure and "bulletproof," by exposing it to the worst threats on the open internet, as has occurred with both the Bitcoin stack and the Ethereum platform. * Configurable for private blockchain deployment and support for confidentiality of transactions — because most businesses do not want their transactions to be visible by their competitors or by the rest of the world. * Functioning governance — there needs to be a cohesive decision-making structure that can respond in an agile and coherent manner to threats to the system. * Advanced smart contract capability — because the current generation of smart-contract technology relies on traditional languages (similar to Java or C#), which are inadequate for the rigorous requirements of large-value contracts (and are best supported by metadata-driven or mathematically verifiable programming systems). * Adequate tooling for developing, debugging, deploying, monitoring and managing smart-contract-based systems (the importance of which was underscored by the recent denial-of-service attacks on the Ethereum network).  |
| json metadata | {"tags":["blockchain","analysis","steemit","bitcoin","crypto"],"image":["https://steemitimages.com/DQmabMqUzm3SRvyeZN5FM1irJUPd1HNntpGHfqt3vmtv8oj/blockchain.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | blockchain |
| permlink | my-bitcoin-blockchain-analysis |
| title | My Bitcoin Blockchain Analysis |
| Transaction Info | Block #14182625/Trx d740fb8371c0e98ada28a4cdc161e9655dddd912 |
View Raw JSON Data
{
"block": 14182625,
"op": [
"comment",
{
"author": "mikereams",
"body": "## Analysis ##\nBlockchain technology derived from the Bitcoin stack promises much in the era of digital business. The Bitcoin blockchain is currently the primary mechanism for implementing a decentralized, distributed ledger of cryptocurrency transactions — although alternatives are have been underway.\n\nThere is a contradiction between the requirements of a private blockchain and the capabilities of public blockchain, which result from its original purpose of creating a value-exchange system that is resistant to control by a single central authority. This will be an ongoing tension, similar to the dynamic between public and private cloud.\n\nBlockchain platforms, also known as distributed ledger technology and termed \"metacoin platforms\", remain at the peak of the Hype Cycle curve. This means inflated expectations still abound, the result of a lack of knowledge of the technology and what problems it can be applied to.\n\n## The Essence of Blockchain Technology ##\nMany enterprises are considering blockchain technology but perceive it to be a tool or platform for database management, data integration, application integration, identity management, records management and/or business process management. In its current form, blockchain technology is none of these, although it may evolve to eventually encompass several of these areas.\n\n The only blockchain platform that is proven mature, secure and rock solid in production is the Bitcoin blockchain (although, additionally, the Ethereum platform has recently gained credibility).\n\n The Bitcoin blockchain is conceptually simple: a flat file, a sequential list of transaction records denominated in bitcoin currency. This record of transactions (distributed ledger) is implemented as direct-to-file-system storage, meaning there is no use of a conventional database management system (DBMS) (except for in a secondary role as a query mechanism for metadata). \n\nInstead of relying on a DBMS tool or platform, the Bitcoin ledger is a manually coded data structure that consists of a sequential chain of blocks, in which each block comprises several hundred transaction records appended to the rest of the chain at roughly 10-minute intervals per block. The entire dataset is massively replicated across thousands of nodes in a peer-to-peer network, each one running software that implements the Bitcoin protocol. The system is designed to avoid reliance on any one server, on any one organization or on any one software implementation. Instead, the blockchain represents a trusted record within an untrusted environment — an authoritative record of significant events, where the truth of the record is defined by the majority of nodes in the peer-to-peer network (strictly speaking, by the majority of computational power).\n\nDespite this successful track record, the Bitcoin blockchain has known limitations in scalability, flexibility and governance. Due to design decisions made that favor the full scope of the \"Byzantine Generals' problem,\" the system will favor security and data integrity over scalability and flexibility. Regarding throughput, the entire system has a theoretical capacity of only seven transactions per second (tps) maximum (in practice, this number is about three tps). This transaction volume is not for a single application, but for the entire network — the entire world of bitcoin.\n\n## A Crowded Competitive Arena That Continues to Grow ##\nOver the past two years, there has been a proliferation of blockchain technologies. Some of these are directly competitive with the Bitcoin technology stack, and therefore are designed as public blockchains (similar to Bitcoin, they are integrated with a value token or digital currency). Others are oriented to private blockchain deployments (private networks where the number of participants is stable; all nodes are known; and there is a mechanism that grants permission to participate, which might be a centralized identity management system).\n\nAlthough choosing the eventual winner for this sector is unlikely, given that it may not even be on the market, it is possible to state what that winner will look like.\n\n Here are the characteristics of a winning blockchain platform:\n\n* Open source — this is necessary to cultivate a rich and diverse ecosystem and accelerate adoption through network effect.\n \n* Modular architecture with layers of programmability and customizability — as above, this cultivates an ecosystem and enables market adoption.\n \n* Global scale — scalability, performance and efficiency are essential if blockchain is to become the foundation for the \"Internet of Money.\"\n\n* Multiple implementations of the core protocol — multiple, independently developed implementations ensure that the protocol is understood, well-defined and adds resistance to possible attacks (as occurred with the Ethereum platform in September 2016). This requires there to be an accurate and precise specification of the core protocol, as opposed to relying on one codebase that is not documented.\n\n* Hardened through public blockchain deployment — this is the only way to ensure that the system is secure and \"bulletproof,\" by exposing it to the worst threats on the open internet, as has occurred with both the Bitcoin stack and the Ethereum platform.\n\n* Configurable for private blockchain deployment and support for confidentiality of transactions — because most businesses do not want their transactions to be visible by their competitors or by the rest of the world.\n\n* Functioning governance — there needs to be a cohesive decision-making structure that can respond in an agile and coherent manner to threats to the system.\n\n* Advanced smart contract capability — because the current generation of smart-contract technology relies on traditional languages (similar to Java or C#), which are inadequate for the rigorous requirements of large-value contracts (and are best supported by metadata-driven or mathematically verifiable programming systems).\n\n* Adequate tooling for developing, debugging, deploying, monitoring and managing smart-contract-based systems (the importance of which was underscored by the recent denial-of-service attacks on the Ethereum network).\n\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"analysis\",\"steemit\",\"bitcoin\",\"crypto\"],\"image\":[\"https://steemitimages.com/DQmabMqUzm3SRvyeZN5FM1irJUPd1HNntpGHfqt3vmtv8oj/blockchain.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "my-bitcoin-blockchain-analysis",
"title": "My Bitcoin Blockchain Analysis"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:14:42",
"trx_id": "d740fb8371c0e98ada28a4cdc161e9655dddd912",
"trx_in_block": 1,
"virtual_op": 0
}mikereamsupvoted (100.00%) @mikereams / prisoner-of-legacy-systems2017/08/01 03:12:27
mikereamsupvoted (100.00%) @mikereams / prisoner-of-legacy-systems
2017/08/01 03:12:27
| author | mikereams |
| permlink | prisoner-of-legacy-systems |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182580/Trx a3917f6d220ce92dac9f35c36ebff0c67786e91e |
View Raw JSON Data
{
"block": 14182580,
"op": [
"vote",
{
"author": "mikereams",
"permlink": "prisoner-of-legacy-systems",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:12:27",
"trx_id": "a3917f6d220ce92dac9f35c36ebff0c67786e91e",
"trx_in_block": 21,
"virtual_op": 0
}mikereamspublished a new post: prisoner-of-legacy-systems2017/08/01 03:12:27
mikereamspublished a new post: prisoner-of-legacy-systems
2017/08/01 03:12:27
| author | mikereams |
| body | At some point, old software installed, just has to go away. The million dollar question is when. Don’t be a Prisoner of Legacy Systems. After recently experience of having a legacy system for about 8 years too long that prompted me to blog on this topic. I’ve seen the impact first hand with regard to project timelines, business climate changes, and constant tickets to the help desk. Project managers constantly asking, “Why does it take longer every year to do something simple?”. – Really? An online definition, > A legacy system is an old method, technology, computer system or application program that continues to be used, typically because it still functions for the users’ needs, even though newer technology or more efficient methods of performing a task are now available. Those who are making these technology decisions are not typically directly affected by them. They’re looking at out-of-pocket cost versus total cost of ownership. While this takes place, I’m more concerned with all the time involved to resolve the same repeatable problems along with trying to figure out an escape from the legacy prison. So what do I do? Just keep answering those same ridiculous rhetorical questions of “Why does it takes so long and why is it so difficult” with a calm soothing voice, “Because you incurred Technical Debt”. During the course of 8 long years of projects, the project team took shortcuts due to a variety of reasoning, such as lack of technical ability, pressure of meeting project deadlines, or just flat-out lazy. You can imagine over time, these poor decisions accumulate huge backlogs of inefficiencies that keep getting kicked down the road. At some point, Peter may not let you rob him while Paul needs an early payment. While the cost of maintaining an old system may indicate that a change is needed, it is also possible to spend more than necessary on a new solution. We need solutions that help us stay competitive, however wasting money on software upgrades, can be unnecessarily as it increases Technical Debt. When the old systems can’t keep up with the business demands or changes, it’s time to replace. In the absence of due diligence, it is not always clear which option of replacement or upgrade, is best. Most replacement systems at minimum, need to provide marginal benefits over any legacy system being replaced to justify the cost. Poor legacy software replacement decisions happen when technology decisions are not aligned with business requirements and strategy. Have you had lunch with your Enterprise Architect lately? So let’s encourage our product owners to make conscious decisions on if the economics justifies the cost of the incurring technical debt. Not all technical debt needs to be repaid as one can live with issues on a product nearing end of its life. Just like your payment of financial debt, it is good stewardship to first repay the “high interest” technical debt. It is preferable that technical debt be repaid incrementally (like making a monthly mortgage payment) through use of practices such as peer reviews, refactoring, continuous integration, and automated testing. So what’s your strategy for technical debt prioritization on your portfolio prison? A general rule of thumb could be based on comparing the degree of current value of business capabilities against the degree of business value that the system fulfills for future business needs. This may not get you out of an early prison sentence, however maybe, just maybe, feeling liberated removes illusions of being in one. > That which we manifest is before us; we are the creators of our own destiny. Be it through intention or ignorance, our successes and our failures have been brought on by none other than ourselves. ― Garth Stein, The Art of Racing in the Rain  |
| json metadata | {"tags":["technicaldebt","legacy","technology","oldsoftware","ignorance"],"image":["https://steemitimages.com/DQmRAedy2hzfyzGfPmnwM2qXCtNAdsQWgpDXZUAFcjxoVqp/office.jpg"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | technicaldebt |
| permlink | prisoner-of-legacy-systems |
| title | Prisoner of Legacy Systems |
| Transaction Info | Block #14182580/Trx a3917f6d220ce92dac9f35c36ebff0c67786e91e |
View Raw JSON Data
{
"block": 14182580,
"op": [
"comment",
{
"author": "mikereams",
"body": "At some point, old software installed, just has to go away. The million dollar question is when. Don’t be a Prisoner of Legacy Systems.\n\nAfter recently experience of having a legacy system for about 8 years too long that prompted me to blog on this topic. I’ve seen the impact first hand with regard to project timelines, business climate changes, and constant tickets to the help desk. Project managers constantly asking, “Why does it take longer every year to do something simple?”. – Really?\n\nAn online definition,\n\n> A legacy system is an old method, technology, computer system or application program that continues to be used, typically because it still functions for the users’ needs, even though newer technology or more efficient methods of performing a task are now available.\n\nThose who are making these technology decisions are not typically directly affected by them. They’re looking at out-of-pocket cost versus total cost of ownership. While this takes place, I’m more concerned with all the time involved to resolve the same repeatable problems along with trying to figure out an escape from the legacy prison. So what do I do? Just keep answering those same ridiculous rhetorical questions of “Why does it takes so long and why is it so difficult” with a calm soothing voice, “Because you incurred Technical Debt”.\n\nDuring the course of 8 long years of projects, the project team took shortcuts due to a variety of reasoning, such as lack of technical ability, pressure of meeting project deadlines, or just flat-out lazy. You can imagine over time, these poor decisions accumulate huge backlogs of inefficiencies that keep getting kicked down the road. At some point, Peter may not let you rob him while Paul needs an early payment.\n\nWhile the cost of maintaining an old system may indicate that a change is needed, it is also possible to spend more than necessary on a new solution. We need solutions that help us stay competitive, however wasting money on software upgrades, can be unnecessarily as it increases Technical Debt. When the old systems can’t keep up with the business demands or changes, it’s time to replace. In the absence of due diligence, it is not always clear which option of replacement or upgrade, is best.\n\nMost replacement systems at minimum, need to provide marginal benefits over any legacy system being replaced to justify the cost. Poor legacy software replacement decisions happen when technology decisions are not aligned with business requirements and strategy. Have you had lunch with your Enterprise Architect lately?\n\nSo let’s encourage our product owners to make conscious decisions on if the economics justifies the cost of the incurring technical debt. Not all technical debt needs to be repaid as one can live with issues on a product nearing end of its life. Just like your payment of financial debt, it is good stewardship to first repay the “high interest” technical debt. It is preferable that technical debt be repaid incrementally (like making a monthly mortgage payment) through use of practices such as peer reviews, refactoring, continuous integration, and automated testing.\n\nSo what’s your strategy for technical debt prioritization on your portfolio prison? A general rule of thumb could be based on comparing the degree of current value of business capabilities against the degree of business value that the system fulfills for future business needs. This may not get you out of an early prison sentence, however maybe, just maybe, feeling liberated removes illusions of being in one.\n\n> That which we manifest is before us; we are the creators of our own destiny. Be it through intention or ignorance, our successes and our failures have been brought on by none other than ourselves.\n― Garth Stein, The Art of Racing in the Rain\n\n",
"json_metadata": "{\"tags\":[\"technicaldebt\",\"legacy\",\"technology\",\"oldsoftware\",\"ignorance\"],\"image\":[\"https://steemitimages.com/DQmRAedy2hzfyzGfPmnwM2qXCtNAdsQWgpDXZUAFcjxoVqp/office.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "technicaldebt",
"permlink": "prisoner-of-legacy-systems",
"title": "Prisoner of Legacy Systems"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:12:27",
"trx_id": "a3917f6d220ce92dac9f35c36ebff0c67786e91e",
"trx_in_block": 21,
"virtual_op": 0
}2017/08/01 03:07:36
2017/08/01 03:07:36
| author | dollarvigilante |
| permlink | self-ownership-in-the-age-of-authoritarianism-jeff-berwick-on-open-your-mind-radio-ireland |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182484/Trx 4c10fc89d14196b9777c4701f4ed4ea5db95777d |
View Raw JSON Data
{
"block": 14182484,
"op": [
"vote",
{
"author": "dollarvigilante",
"permlink": "self-ownership-in-the-age-of-authoritarianism-jeff-berwick-on-open-your-mind-radio-ireland",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:07:36",
"trx_id": "4c10fc89d14196b9777c4701f4ed4ea5db95777d",
"trx_in_block": 16,
"virtual_op": 0
}mikereamsfollowed @dollarvigilante2017/08/01 03:07:21
mikereamsfollowed @dollarvigilante
2017/08/01 03:07:21
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"dollarvigilante","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14182479/Trx c3b76efebacce92f36eea409d273df191b12b8b4 |
View Raw JSON Data
{
"block": 14182479,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"dollarvigilante\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:07:21",
"trx_id": "c3b76efebacce92f36eea409d273df191b12b8b4",
"trx_in_block": 9,
"virtual_op": 0
}2017/08/01 03:04:06
2017/08/01 03:04:06
| author | mkt |
| permlink | re-stellabelle-how-to-destroy-steemit-in-3-easy-steps-20170730t175646587z |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182414/Trx 0eb785f064b3b4c4e78aad811abed2cac5a1f290 |
View Raw JSON Data
{
"block": 14182414,
"op": [
"vote",
{
"author": "mkt",
"permlink": "re-stellabelle-how-to-destroy-steemit-in-3-easy-steps-20170730t175646587z",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:04:06",
"trx_id": "0eb785f064b3b4c4e78aad811abed2cac5a1f290",
"trx_in_block": 8,
"virtual_op": 0
}2017/08/01 03:04:00
2017/08/01 03:04:00
| author | stellabelle |
| permlink | re-mkt-re-stellabelle-re-mkt-re-stellabelle-how-to-destroy-steemit-in-3-easy-steps-20170730t182706707z |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182412/Trx e03d55dfff6d8727251ed8b9a09da197cfee3969 |
View Raw JSON Data
{
"block": 14182412,
"op": [
"vote",
{
"author": "stellabelle",
"permlink": "re-mkt-re-stellabelle-re-mkt-re-stellabelle-how-to-destroy-steemit-in-3-easy-steps-20170730t182706707z",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:04:00",
"trx_id": "e03d55dfff6d8727251ed8b9a09da197cfee3969",
"trx_in_block": 9,
"virtual_op": 0
}2017/08/01 03:01:33
2017/08/01 03:01:33
| author | mikereams |
| body | Now this was both entertaining and educational! |
| json metadata | {"tags":["abuse"],"app":"steemit/0.1"} |
| parent author | stellabelle |
| parent permlink | how-to-destroy-steemit-in-3-easy-steps |
| permlink | re-stellabelle-how-to-destroy-steemit-in-3-easy-steps-20170801t030135113z |
| title | |
| Transaction Info | Block #14182363/Trx 373a71e3eb1fe4f9bb8548c597ac8c81e1bdc08f |
View Raw JSON Data
{
"block": 14182363,
"op": [
"comment",
{
"author": "mikereams",
"body": "Now this was both entertaining and educational!",
"json_metadata": "{\"tags\":[\"abuse\"],\"app\":\"steemit/0.1\"}",
"parent_author": "stellabelle",
"parent_permlink": "how-to-destroy-steemit-in-3-easy-steps",
"permlink": "re-stellabelle-how-to-destroy-steemit-in-3-easy-steps-20170801t030135113z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:01:33",
"trx_id": "373a71e3eb1fe4f9bb8548c597ac8c81e1bdc08f",
"trx_in_block": 17,
"virtual_op": 0
}mikereamsupvoted (100.00%) @stellabelle / how-to-destroy-steemit-in-3-easy-steps2017/08/01 03:00:45
mikereamsupvoted (100.00%) @stellabelle / how-to-destroy-steemit-in-3-easy-steps
2017/08/01 03:00:45
| author | stellabelle |
| permlink | how-to-destroy-steemit-in-3-easy-steps |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182347/Trx 15198cf8f32d4b5b930e09da2e21fdd64223cb77 |
View Raw JSON Data
{
"block": 14182347,
"op": [
"vote",
{
"author": "stellabelle",
"permlink": "how-to-destroy-steemit-in-3-easy-steps",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T03:00:45",
"trx_id": "15198cf8f32d4b5b930e09da2e21fdd64223cb77",
"trx_in_block": 5,
"virtual_op": 0
}widiaupvoted (100.00%) @mikereams / my-bitcoin-blockchain-analysis2017/08/01 02:59:00
widiaupvoted (100.00%) @mikereams / my-bitcoin-blockchain-analysis
2017/08/01 02:59:00
| author | mikereams |
| permlink | my-bitcoin-blockchain-analysis |
| voter | widia |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182312/Trx ff2640cb6fe213aa38bf148248dca26c30585120 |
View Raw JSON Data
{
"block": 14182312,
"op": [
"vote",
{
"author": "mikereams",
"permlink": "my-bitcoin-blockchain-analysis",
"voter": "widia",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T02:59:00",
"trx_id": "ff2640cb6fe213aa38bf148248dca26c30585120",
"trx_in_block": 11,
"virtual_op": 0
}mikereamspublished a new post: my-bitcoin-blockchain-analysis2017/08/01 02:56:06
mikereamspublished a new post: my-bitcoin-blockchain-analysis
2017/08/01 02:56:06
| author | mikereams |
| body | ## Analysis ## Blockchain technology derived from the Bitcoin stack promises much in the era of digital business. The Bitcoin blockchain is currently the primary mechanism for implementing a decentralized, distributed ledger of cryptocurrency transactions — although alternatives are have been underway. There is a contradiction between the requirements of a private blockchain and the capabilities of public blockchain, which result from its original purpose of creating a value-exchange system that is resistant to control by a single central authority. This will be an ongoing tension, similar to the dynamic between public and private cloud. Blockchain platforms, also known as distributed ledger technology and termed "metacoin platforms", remain at the peak of the Hype Cycle curve. This means inflated expectations still abound, the result of a lack of knowledge of the technology and what problems it can be applied to. ## The Essence of Blockchain Technology ## Many enterprises are considering blockchain technology but perceive it to be a tool or platform for database management, data integration, application integration, identity management, records management and/or business process management. In its current form, blockchain technology is none of these, although it may evolve to eventually encompass several of these areas. The only blockchain platform that is proven mature, secure and rock solid in production is the Bitcoin blockchain (although, additionally, the Ethereum platform has recently gained credibility). The Bitcoin blockchain is conceptually simple: a flat file, a sequential list of transaction records denominated in bitcoin currency. This record of transactions (distributed ledger) is implemented as direct-to-file-system storage, meaning there is no use of a conventional database management system (DBMS) (except for in a secondary role as a query mechanism for metadata). Instead of relying on a DBMS tool or platform, the Bitcoin ledger is a manually coded data structure that consists of a sequential chain of blocks, in which each block comprises several hundred transaction records appended to the rest of the chain at roughly 10-minute intervals per block. The entire dataset is massively replicated across thousands of nodes in a peer-to-peer network, each one running software that implements the Bitcoin protocol. The system is designed to avoid reliance on any one server, on any one organization or on any one software implementation. Instead, the blockchain represents a trusted record within an untrusted environment — an authoritative record of significant events, where the truth of the record is defined by the majority of nodes in the peer-to-peer network (strictly speaking, by the majority of computational power). Despite this successful track record, the Bitcoin blockchain has known limitations in scalability, flexibility and governance. Due to design decisions made that favor the full scope of the "Byzantine Generals' problem," the system will favor security and data integrity over scalability and flexibility. Regarding throughput, the entire system has a theoretical capacity of only seven transactions per second (tps) maximum (in practice, this number is about three tps). This transaction volume is not for a single application, but for the entire network — the entire world of bitcoin. ## A Crowded Competitive Arena That Continues to Grow ## Over the past two years, there has been a proliferation of blockchain technologies. Some of these are directly competitive with the Bitcoin technology stack, and therefore are designed as public blockchains (similar to Bitcoin, they are integrated with a value token or digital currency). Others are oriented to private blockchain deployments (private networks where the number of participants is stable; all nodes are known; and there is a mechanism that grants permission to participate, which might be a centralized identity management system). Although choosing the eventual winner for this sector is unlikely, given that it may not even be on the market, it is possible to state what that winner will look like. Here are the characteristics of a winning blockchain platform: * Open source — this is necessary to cultivate a rich and diverse ecosystem and accelerate adoption through network effect. * Modular architecture with layers of programmability and customizability — as above, this cultivates an ecosystem and enables market adoption. * Global scale — scalability, performance and efficiency are essential if blockchain is to become the foundation for the "Internet of Money." * Multiple implementations of the core protocol — multiple, independently developed implementations ensure that the protocol is understood, well-defined and adds resistance to possible attacks (as occurred with the Ethereum platform in September 2016). This requires there to be an accurate and precise specification of the core protocol, as opposed to relying on one codebase that is not documented. * Hardened through public blockchain deployment — this is the only way to ensure that the system is secure and "bulletproof," by exposing it to the worst threats on the open internet, as has occurred with both the Bitcoin stack and the Ethereum platform. * Configurable for private blockchain deployment and support for confidentiality of transactions — because most businesses do not want their transactions to be visible by their competitors or by the rest of the world. * Functioning governance — there needs to be a cohesive decision-making structure that can respond in an agile and coherent manner to threats to the system. * Advanced smart contract capability — because the current generation of smart-contract technology relies on traditional languages (similar to Java or C#), which are inadequate for the rigorous requirements of large-value contracts (and are best supported by metadata-driven or mathematically verifiable programming systems). * Adequate tooling for developing, debugging, deploying, monitoring and managing smart-contract-based systems (the importance of which was underscored by the recent denial-of-service attacks on the Ethereum network).  |
| json metadata | {"tags":["blockchain","platforms","analysis","steemit","bitcoin"],"image":["https://steemitimages.com/DQmabMqUzm3SRvyeZN5FM1irJUPd1HNntpGHfqt3vmtv8oj/blockchain.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | blockchain |
| permlink | my-bitcoin-blockchain-analysis |
| title | My Bitcoin Blockchain Analysis |
| Transaction Info | Block #14182254/Trx 611a59ea8b0ebf6c17a753581958b1f2dedab596 |
View Raw JSON Data
{
"block": 14182254,
"op": [
"comment",
{
"author": "mikereams",
"body": "## Analysis ##\nBlockchain technology derived from the Bitcoin stack promises much in the era of digital business. The Bitcoin blockchain is currently the primary mechanism for implementing a decentralized, distributed ledger of cryptocurrency transactions — although alternatives are have been underway.\n\nThere is a contradiction between the requirements of a private blockchain and the capabilities of public blockchain, which result from its original purpose of creating a value-exchange system that is resistant to control by a single central authority. This will be an ongoing tension, similar to the dynamic between public and private cloud.\n\nBlockchain platforms, also known as distributed ledger technology and termed \"metacoin platforms\", remain at the peak of the Hype Cycle curve. This means inflated expectations still abound, the result of a lack of knowledge of the technology and what problems it can be applied to.\n\n## The Essence of Blockchain Technology ##\nMany enterprises are considering blockchain technology but perceive it to be a tool or platform for database management, data integration, application integration, identity management, records management and/or business process management. In its current form, blockchain technology is none of these, although it may evolve to eventually encompass several of these areas.\n\n The only blockchain platform that is proven mature, secure and rock solid in production is the Bitcoin blockchain (although, additionally, the Ethereum platform has recently gained credibility).\n\n The Bitcoin blockchain is conceptually simple: a flat file, a sequential list of transaction records denominated in bitcoin currency. This record of transactions (distributed ledger) is implemented as direct-to-file-system storage, meaning there is no use of a conventional database management system (DBMS) (except for in a secondary role as a query mechanism for metadata). \n\nInstead of relying on a DBMS tool or platform, the Bitcoin ledger is a manually coded data structure that consists of a sequential chain of blocks, in which each block comprises several hundred transaction records appended to the rest of the chain at roughly 10-minute intervals per block. The entire dataset is massively replicated across thousands of nodes in a peer-to-peer network, each one running software that implements the Bitcoin protocol. The system is designed to avoid reliance on any one server, on any one organization or on any one software implementation. Instead, the blockchain represents a trusted record within an untrusted environment — an authoritative record of significant events, where the truth of the record is defined by the majority of nodes in the peer-to-peer network (strictly speaking, by the majority of computational power).\n\nDespite this successful track record, the Bitcoin blockchain has known limitations in scalability, flexibility and governance. Due to design decisions made that favor the full scope of the \"Byzantine Generals' problem,\" the system will favor security and data integrity over scalability and flexibility. Regarding throughput, the entire system has a theoretical capacity of only seven transactions per second (tps) maximum (in practice, this number is about three tps). This transaction volume is not for a single application, but for the entire network — the entire world of bitcoin.\n\n## A Crowded Competitive Arena That Continues to Grow ##\nOver the past two years, there has been a proliferation of blockchain technologies. Some of these are directly competitive with the Bitcoin technology stack, and therefore are designed as public blockchains (similar to Bitcoin, they are integrated with a value token or digital currency). Others are oriented to private blockchain deployments (private networks where the number of participants is stable; all nodes are known; and there is a mechanism that grants permission to participate, which might be a centralized identity management system).\n\nAlthough choosing the eventual winner for this sector is unlikely, given that it may not even be on the market, it is possible to state what that winner will look like.\n\n Here are the characteristics of a winning blockchain platform:\n\n* Open source — this is necessary to cultivate a rich and diverse ecosystem and accelerate adoption through network effect.\n \n* Modular architecture with layers of programmability and customizability — as above, this cultivates an ecosystem and enables market adoption.\n \n* Global scale — scalability, performance and efficiency are essential if blockchain is to become the foundation for the \"Internet of Money.\"\n\n* Multiple implementations of the core protocol — multiple, independently developed implementations ensure that the protocol is understood, well-defined and adds resistance to possible attacks (as occurred with the Ethereum platform in September 2016). This requires there to be an accurate and precise specification of the core protocol, as opposed to relying on one codebase that is not documented.\n\n* Hardened through public blockchain deployment — this is the only way to ensure that the system is secure and \"bulletproof,\" by exposing it to the worst threats on the open internet, as has occurred with both the Bitcoin stack and the Ethereum platform.\n\n* Configurable for private blockchain deployment and support for confidentiality of transactions — because most businesses do not want their transactions to be visible by their competitors or by the rest of the world.\n\n* Functioning governance — there needs to be a cohesive decision-making structure that can respond in an agile and coherent manner to threats to the system.\n\n* Advanced smart contract capability — because the current generation of smart-contract technology relies on traditional languages (similar to Java or C#), which are inadequate for the rigorous requirements of large-value contracts (and are best supported by metadata-driven or mathematically verifiable programming systems).\n\n* Adequate tooling for developing, debugging, deploying, monitoring and managing smart-contract-based systems (the importance of which was underscored by the recent denial-of-service attacks on the Ethereum network).\n\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"platforms\",\"analysis\",\"steemit\",\"bitcoin\"],\"image\":[\"https://steemitimages.com/DQmabMqUzm3SRvyeZN5FM1irJUPd1HNntpGHfqt3vmtv8oj/blockchain.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "my-bitcoin-blockchain-analysis",
"title": "My Bitcoin Blockchain Analysis"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T02:56:06",
"trx_id": "611a59ea8b0ebf6c17a753581958b1f2dedab596",
"trx_in_block": 11,
"virtual_op": 0
}mikereamscustom json: follow2017/08/01 02:55:21
mikereamscustom json: follow
2017/08/01 02:55:21
| id | follow |
| json | ["reblog",{"account":"mikereams","author":"vominhquoc","permlink":"steemit-tricks-tag-using-strategy-secret-of-ridiculous-post-payout"}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14182239/Trx a86a5ceb034b9f594a42edb1f9dfc66186fb4663 |
View Raw JSON Data
{
"block": 14182239,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"reblog\",{\"account\":\"mikereams\",\"author\":\"vominhquoc\",\"permlink\":\"steemit-tricks-tag-using-strategy-secret-of-ridiculous-post-payout\"}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T02:55:21",
"trx_id": "a86a5ceb034b9f594a42edb1f9dfc66186fb4663",
"trx_in_block": 19,
"virtual_op": 0
}unprovokedupvoted (3.00%) @mikereams / my-bitcoin-blockchain-analysis2017/08/01 02:55:15
unprovokedupvoted (3.00%) @mikereams / my-bitcoin-blockchain-analysis
2017/08/01 02:55:15
| author | mikereams |
| permlink | my-bitcoin-blockchain-analysis |
| voter | unprovoked |
| weight | 300 (3.00%) |
| Transaction Info | Block #14182237/Trx 271fedc98f1fc0370826327b193a68eceec62cc0 |
View Raw JSON Data
{
"block": 14182237,
"op": [
"vote",
{
"author": "mikereams",
"permlink": "my-bitcoin-blockchain-analysis",
"voter": "unprovoked",
"weight": 300
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T02:55:15",
"trx_id": "271fedc98f1fc0370826327b193a68eceec62cc0",
"trx_in_block": 11,
"virtual_op": 0
}2017/08/01 02:55:09
2017/08/01 02:55:09
| author | vominhquoc |
| permlink | steemit-tricks-tag-using-strategy-secret-of-ridiculous-post-payout |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182235/Trx 628c830979d0452e934c06a66861ead96ab15769 |
View Raw JSON Data
{
"block": 14182235,
"op": [
"vote",
{
"author": "vominhquoc",
"permlink": "steemit-tricks-tag-using-strategy-secret-of-ridiculous-post-payout",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T02:55:09",
"trx_id": "628c830979d0452e934c06a66861ead96ab15769",
"trx_in_block": 6,
"virtual_op": 0
}mikereamsupvoted (100.00%) @mikereams / my-bitcoin-blockchain-analysis2017/08/01 02:52:21
mikereamsupvoted (100.00%) @mikereams / my-bitcoin-blockchain-analysis
2017/08/01 02:52:21
| author | mikereams |
| permlink | my-bitcoin-blockchain-analysis |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14182179/Trx a64a6a6d862122fbf7708e751facd3bf3638d26b |
View Raw JSON Data
{
"block": 14182179,
"op": [
"vote",
{
"author": "mikereams",
"permlink": "my-bitcoin-blockchain-analysis",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T02:52:21",
"trx_id": "a64a6a6d862122fbf7708e751facd3bf3638d26b",
"trx_in_block": 3,
"virtual_op": 0
}mikereamspublished a new post: my-bitcoin-blockchain-analysis2017/08/01 02:52:21
mikereamspublished a new post: my-bitcoin-blockchain-analysis
2017/08/01 02:52:21
| author | mikereams |
| body | ## Analysis ## Blockchain technology derived from the Bitcoin stack promises much in the era of digital business. The Bitcoin blockchain is currently the primary mechanism for implementing a decentralized, distributed ledger of cryptocurrency transactions — although alternatives are have been underway. There is a contradiction between the requirements of a private blockchain and the capabilities of public blockchain, which result from its original purpose of creating a value-exchange system that is resistant to control by a single central authority. This will be an ongoing tension, similar to the dynamic between public and private cloud. Blockchain platforms, also known as distributed ledger technology and termed "metacoin platforms", remain at the peak of the Hype Cycle curve. This means inflated expectations still abound, the result of a lack of knowledge of the technology and what problems it can be applied to. ## The Essence of Blockchain Technology ## Many enterprises are considering blockchain technology but perceive it to be a tool or platform for database management, data integration, application integration, identity management, records management and/or business process management. In its current form, blockchain technology is none of these, although it may evolve to eventually encompass several of these areas. The only blockchain platform that is proven mature, secure and rock solid in production is the Bitcoin blockchain (although, additionally, the Ethereum platform has recently gained credibility). The Bitcoin blockchain is conceptually simple: a flat file, a sequential list of transaction records denominated in bitcoin currency. This record of transactions (distributed ledger) is implemented as direct-to-file-system storage, meaning there is no use of a conventional database management system (DBMS) (except for in a secondary role as a query mechanism for metadata). Instead of relying on a DBMS tool or platform, the Bitcoin ledger is a manually coded data structure that consists of a sequential chain of blocks, in which each block comprises several hundred transaction records appended to the rest of the chain at roughly 10-minute intervals per block. The entire dataset is massively replicated across thousands of nodes in a peer-to-peer network, each one running software that implements the Bitcoin protocol. The system is designed to avoid reliance on any one server, on any one organization or on any one software implementation. Instead, the blockchain represents a trusted record within an untrusted environment — an authoritative record of significant events, where the truth of the record is defined by the majority of nodes in the peer-to-peer network (strictly speaking, by the majority of computational power). Despite this successful track record, the Bitcoin blockchain has known limitations in scalability, flexibility and governance. Due to design decisions made that favor the full scope of the "Byzantine Generals' problem," the system will favor security and data integrity over scalability and flexibility. Regarding throughput, the entire system has a theoretical capacity of only seven transactions per second (tps) maximum (in practice, this number is about three tps). This transaction volume is not for a single application, but for the entire network — the entire world of bitcoin. ## A Crowded Competitive Arena That Continues to Grow ## Over the past two years, there has been a proliferation of blockchain technologies. Some of these are directly competitive with the Bitcoin technology stack, and therefore are designed as public blockchains (similar to Bitcoin, they are integrated with a value token or digital currency). Others are oriented to private blockchain deployments (private networks where the number of participants is stable; all nodes are known; and there is a mechanism that grants permission to participate, which might be a centralized identity management system). Although choosing the eventual winner for this sector is unlikely, given that it may not even be on the market, it is possible to state what that winner will look like. Here are the characteristics of a winning blockchain platform: * Open source — this is necessary to cultivate a rich and diverse ecosystem and accelerate adoption through network effect. * Modular architecture with layers of programmability and customizability — as above, this cultivates an ecosystem and enables market adoption. * Global scale — scalability, performance and efficiency are essential if blockchain is to become the foundation for the "Internet of Money." * Multiple implementations of the core protocol — multiple, independently developed implementations ensure that the protocol is understood, well-defined and adds resistance to possible attacks (as occurred with the Ethereum platform in September 2016). This requires there to be an accurate and precise specification of the core protocol, as opposed to relying on one codebase that is not documented. * Hardened through public blockchain deployment — this is the only way to ensure that the system is secure and "bulletproof," by exposing it to the worst threats on the open internet, as has occurred with both the Bitcoin stack and the Ethereum platform. * Configurable for private blockchain deployment and support for confidentiality of transactions — because most businesses do not want their transactions to be visible by their competitors or by the rest of the world. * Functioning governance — there needs to be a cohesive decision-making structure that can respond in an agile and coherent manner to threats to the system. * Advanced smart contract capability — because the current generation of smart-contract technology relies on traditional languages (similar to Java or C#), which are inadequate for the rigorous requirements of large-value contracts (and are best supported by metadata-driven or mathematically verifiable programming systems). * Adequate tooling for developing, debugging, deploying, monitoring and managing smart-contract-based systems (the importance of which was underscored by the recent denial-of-service attacks on the Ethereum network).  |
| json metadata | {"tags":["blockchain","platforms","analysis"],"image":["https://steemitimages.com/DQmabMqUzm3SRvyeZN5FM1irJUPd1HNntpGHfqt3vmtv8oj/blockchain.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | blockchain |
| permlink | my-bitcoin-blockchain-analysis |
| title | My Bitcoin Blockchain Analysis |
| Transaction Info | Block #14182179/Trx a64a6a6d862122fbf7708e751facd3bf3638d26b |
View Raw JSON Data
{
"block": 14182179,
"op": [
"comment",
{
"author": "mikereams",
"body": "## Analysis ##\nBlockchain technology derived from the Bitcoin stack promises much in the era of digital business. The Bitcoin blockchain is currently the primary mechanism for implementing a decentralized, distributed ledger of cryptocurrency transactions — although alternatives are have been underway.\n\nThere is a contradiction between the requirements of a private blockchain and the capabilities of public blockchain, which result from its original purpose of creating a value-exchange system that is resistant to control by a single central authority. This will be an ongoing tension, similar to the dynamic between public and private cloud.\n\nBlockchain platforms, also known as distributed ledger technology and termed \"metacoin platforms\", remain at the peak of the Hype Cycle curve. This means inflated expectations still abound, the result of a lack of knowledge of the technology and what problems it can be applied to.\n\n## The Essence of Blockchain Technology ##\nMany enterprises are considering blockchain technology but perceive it to be a tool or platform for database management, data integration, application integration, identity management, records management and/or business process management. In its current form, blockchain technology is none of these, although it may evolve to eventually encompass several of these areas.\n\n The only blockchain platform that is proven mature, secure and rock solid in production is the Bitcoin blockchain (although, additionally, the Ethereum platform has recently gained credibility).\n\n The Bitcoin blockchain is conceptually simple: a flat file, a sequential list of transaction records denominated in bitcoin currency. This record of transactions (distributed ledger) is implemented as direct-to-file-system storage, meaning there is no use of a conventional database management system (DBMS) (except for in a secondary role as a query mechanism for metadata). \n\nInstead of relying on a DBMS tool or platform, the Bitcoin ledger is a manually coded data structure that consists of a sequential chain of blocks, in which each block comprises several hundred transaction records appended to the rest of the chain at roughly 10-minute intervals per block. The entire dataset is massively replicated across thousands of nodes in a peer-to-peer network, each one running software that implements the Bitcoin protocol. The system is designed to avoid reliance on any one server, on any one organization or on any one software implementation. Instead, the blockchain represents a trusted record within an untrusted environment — an authoritative record of significant events, where the truth of the record is defined by the majority of nodes in the peer-to-peer network (strictly speaking, by the majority of computational power).\n\nDespite this successful track record, the Bitcoin blockchain has known limitations in scalability, flexibility and governance. Due to design decisions made that favor the full scope of the \"Byzantine Generals' problem,\" the system will favor security and data integrity over scalability and flexibility. Regarding throughput, the entire system has a theoretical capacity of only seven transactions per second (tps) maximum (in practice, this number is about three tps). This transaction volume is not for a single application, but for the entire network — the entire world of bitcoin.\n\n## A Crowded Competitive Arena That Continues to Grow ##\nOver the past two years, there has been a proliferation of blockchain technologies. Some of these are directly competitive with the Bitcoin technology stack, and therefore are designed as public blockchains (similar to Bitcoin, they are integrated with a value token or digital currency). Others are oriented to private blockchain deployments (private networks where the number of participants is stable; all nodes are known; and there is a mechanism that grants permission to participate, which might be a centralized identity management system).\n\nAlthough choosing the eventual winner for this sector is unlikely, given that it may not even be on the market, it is possible to state what that winner will look like.\n\n Here are the characteristics of a winning blockchain platform:\n\n* Open source — this is necessary to cultivate a rich and diverse ecosystem and accelerate adoption through network effect.\n \n* Modular architecture with layers of programmability and customizability — as above, this cultivates an ecosystem and enables market adoption.\n \n* Global scale — scalability, performance and efficiency are essential if blockchain is to become the foundation for the \"Internet of Money.\"\n\n* Multiple implementations of the core protocol — multiple, independently developed implementations ensure that the protocol is understood, well-defined and adds resistance to possible attacks (as occurred with the Ethereum platform in September 2016). This requires there to be an accurate and precise specification of the core protocol, as opposed to relying on one codebase that is not documented.\n\n* Hardened through public blockchain deployment — this is the only way to ensure that the system is secure and \"bulletproof,\" by exposing it to the worst threats on the open internet, as has occurred with both the Bitcoin stack and the Ethereum platform.\n\n* Configurable for private blockchain deployment and support for confidentiality of transactions — because most businesses do not want their transactions to be visible by their competitors or by the rest of the world.\n\n* Functioning governance — there needs to be a cohesive decision-making structure that can respond in an agile and coherent manner to threats to the system.\n\n* Advanced smart contract capability — because the current generation of smart-contract technology relies on traditional languages (similar to Java or C#), which are inadequate for the rigorous requirements of large-value contracts (and are best supported by metadata-driven or mathematically verifiable programming systems).\n\n* Adequate tooling for developing, debugging, deploying, monitoring and managing smart-contract-based systems (the importance of which was underscored by the recent denial-of-service attacks on the Ethereum network).\n\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"platforms\",\"analysis\"],\"image\":[\"https://steemitimages.com/DQmabMqUzm3SRvyeZN5FM1irJUPd1HNntpGHfqt3vmtv8oj/blockchain.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "my-bitcoin-blockchain-analysis",
"title": "My Bitcoin Blockchain Analysis"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T02:52:21",
"trx_id": "a64a6a6d862122fbf7708e751facd3bf3638d26b",
"trx_in_block": 3,
"virtual_op": 0
}2017/08/01 01:54:54
2017/08/01 01:54:54
| author | venuspcs |
| permlink | re-dan-eos-development-sneak-peek-for-very-early-developers-20170728t114552730z |
| voter | mikereams |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14181032/Trx f7880e4a6a15903999925a46cdb4c7f8ed7994f4 |
View Raw JSON Data
{
"block": 14181032,
"op": [
"vote",
{
"author": "venuspcs",
"permlink": "re-dan-eos-development-sneak-peek-for-very-early-developers-20170728t114552730z",
"voter": "mikereams",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T01:54:54",
"trx_id": "f7880e4a6a15903999925a46cdb4c7f8ed7994f4",
"trx_in_block": 0,
"virtual_op": 0
}2017/08/01 01:06:06
2017/08/01 01:06:06
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"dan","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14180059/Trx 48469e3141c4bf48924dafbf5ab528f2bfad4a95 |
View Raw JSON Data
{
"block": 14180059,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"dan\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T01:06:06",
"trx_id": "48469e3141c4bf48924dafbf5ab528f2bfad4a95",
"trx_in_block": 15,
"virtual_op": 0
}2017/08/01 01:05:21
2017/08/01 01:05:21
| id | follow |
| json | ["follow",{"follower":"mikereams","following":"modprobe","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["mikereams"] |
| Transaction Info | Block #14180044/Trx d70ec6608477e4e3089f96149b1623161426d473 |
View Raw JSON Data
{
"block": 14180044,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mikereams\",\"following\":\"modprobe\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"mikereams"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T01:05:21",
"trx_id": "d70ec6608477e4e3089f96149b1623161426d473",
"trx_in_block": 17,
"virtual_op": 0
}mikereamsupdated their account properties2017/08/01 01:04:39
mikereamsupdated their account properties
2017/08/01 01:04:39
| account | mikereams |
| json metadata | {"profile":{"profile_image":"https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg","name":"Mike R.","website":"http://mikereams.com"}} |
| memo key | STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4 |
| Transaction Info | Block #14180030/Trx 8ea043604d6279ad061fcb93a7ead3de2cd203e4 |
View Raw JSON Data
{
"block": 14180030,
"op": [
"account_update",
{
"account": "mikereams",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg\",\"name\":\"Mike R.\",\"website\":\"http://mikereams.com\"}}",
"memo_key": "STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T01:04:39",
"trx_id": "8ea043604d6279ad061fcb93a7ead3de2cd203e4",
"trx_in_block": 22,
"virtual_op": 0
}steemcreated a new account: @mikereams2017/08/01 00:58:30
steemcreated a new account: @mikereams
2017/08/01 00:58:30
| active | {"account_auths":[],"key_auths":[["STM5dA5op67AhiZ692LY5nRavim8VmLqk9gKeNMUwtofGbBj1b3U8",1]],"weight_threshold":1} |
| creator | steem |
| delegation | 57000.000000 VESTS |
| extensions | [] |
| fee | 0.500 STEEM |
| json metadata | |
| memo key | STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4 |
| new account name | mikereams |
| owner | {"account_auths":[],"key_auths":[["STM54dGxzGkWiNMZx2PHPtMjPsgxBn4jre7Y5U7oWudPQm2fB8EMN",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM6gY7p8ZeurZaup1rUTtui3arqMoEkyJLw8xZJFUPW62nfvvrGf",1]],"weight_threshold":1} |
| Transaction Info | Block #14179907/Trx 04cf74fec02cd1ff3b2623230695ed12591b9724 |
View Raw JSON Data
{
"block": 14179907,
"op": [
"account_create_with_delegation",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM5dA5op67AhiZ692LY5nRavim8VmLqk9gKeNMUwtofGbBj1b3U8",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"delegation": "57000.000000 VESTS",
"extensions": [],
"fee": "0.500 STEEM",
"json_metadata": "",
"memo_key": "STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4",
"new_account_name": "mikereams",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM54dGxzGkWiNMZx2PHPtMjPsgxBn4jre7Y5U7oWudPQm2fB8EMN",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6gY7p8ZeurZaup1rUTtui3arqMoEkyJLw8xZJFUPW62nfvvrGf",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T00:58:30",
"trx_id": "04cf74fec02cd1ff3b2623230695ed12591b9724",
"trx_in_block": 12,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779076059
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779076059
},
"rc_account": {
"account": "mikereams",
"max_rc": "10164408779",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779076059
}
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg","name":"Mike R.","website":"http://mikereams.com","location":"Atlanta"} |
| JSON METADATA | |
| profile | {"profile_image":"https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg","name":"Mike R.","website":"http://mikereams.com","location":"Atlanta"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg",
"name": "Mike R.",
"website": "http://mikereams.com",
"location": "Atlanta"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAAAAAVAAAAAJGZiZGNjNTM1LTY3YjEtNDE2NC1iNzU2LTlkMjlmNmRjNDhmNA.jpg",
"name": "Mike R.",
"website": "http://mikereams.com",
"location": "Atlanta"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM54dGxzGkWiNMZx2PHPtMjPsgxBn4jre7Y5U7oWudPQm2fB8EMN1/1
Active
Single Signature
Public Keys
STM5dA5op67AhiZ692LY5nRavim8VmLqk9gKeNMUwtofGbBj1b3U81/1
Posting
Single Signature
Public Keys
STM6gY7p8ZeurZaup1rUTtui3arqMoEkyJLw8xZJFUPW62nfvvrGf1/1
Memo
STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM54dGxzGkWiNMZx2PHPtMjPsgxBn4jre7Y5U7oWudPQm2fB8EMN",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM5dA5op67AhiZ692LY5nRavim8VmLqk9gKeNMUwtofGbBj1b3U8",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6gY7p8ZeurZaup1rUTtui3arqMoEkyJLw8xZJFUPW62nfvvrGf",
1
]
],
"weight_threshold": 1
},
"memo": "STM4trv49nWEaEcsFbs19F2pptNxPXiL3GyPPzFgnspQ4ssMcYwB4"
}Witness Votes
3 / 30
01.bitcoiner |
02.bue |
03.good-karma |
[ "bitcoiner", "bue", "good-karma" ]