VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS73.72%
Net Worth
1.377USD
STEEM
0.000STEEM
SBD
0.000SBD
Own SP
23.747SP
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 | 23.747SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 23.747SP | 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": "38616.568692 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | gmikeska07 |
| id | 23338 |
| rank | 70,735 |
| reputation | 72391553208 |
| created | 2016-07-14T21:53:33 |
| recovery_account | steem |
| proxy | None |
| post_count | 15 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2016-07-26T23:09:18 |
| last_root_post | 2016-07-26T23:09:18 |
| last_vote_time | 2016-07-26T23:09:18 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,938 |
| 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 | 38616.568692 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 0.000000 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 | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 10,874,760 |
| sbd_last_interest_payment | 2016-07-18T03:22:54 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 23338,
"name": "gmikeska07",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7ekzkzmxfzLBhs18xdExG58TU8328TkYdzc11rpTNB8SGSCRXo",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM54Zfa2UnbvPU2za248PVxrk3s1gyCa3Kdnj4ogVQ3pv4upY6ga",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5rL6WMiUvnJXedsTqB4VmA8i95eYyYxmcMhqscYhaHArTniSzX",
1
]
]
},
"memo_key": "STM6qzmXaDZJLoKjh9EgYzmzQ2PTbrtR5TndqV9HDPqfd4YxPkTrY",
"json_metadata": "",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2016-07-14T21:53:33",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 15,
"can_vote": true,
"voting_manabar": {
"current_mana": 9938,
"last_update_time": 1469574558
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1468533213
},
"voting_power": 9938,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "10874760",
"sbd_seconds_last_update": "2016-07-18T19:39:00",
"sbd_last_interest_payment": "2016-07-18T03:22:54",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "38616.568692 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 3789,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2016-07-26T23:09:18",
"last_root_post": "2016-07-26T23:09:18",
"last_vote_time": "2016-07-26T23:09:18",
"post_bandwidth": 10000,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": "72391553208",
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 70735
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2019/07/14 23:06:12
2019/07/14 23:06:12
| parent author | gmikeska07 |
| parent permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| author | steemitboard |
| permlink | steemitboard-notify-gmikeska07-20190714t230611000z |
| title | |
| body | Congratulations @gmikeska07! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@gmikeska07/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@gmikeska07) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=gmikeska07)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #34667550/Trx 36cd82e03eb71e2f330c580e31b899853eafd836 |
View Raw JSON Data
{
"trx_id": "36cd82e03eb71e2f330c580e31b899853eafd836",
"block": 34667550,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-07-14T23:06:12",
"op": [
"comment",
{
"parent_author": "gmikeska07",
"parent_permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"author": "steemitboard",
"permlink": "steemitboard-notify-gmikeska07-20190714t230611000z",
"title": "",
"body": "Congratulations @gmikeska07! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@gmikeska07/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@gmikeska07) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=gmikeska07)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2018/07/14 23:55:03
2018/07/14 23:55:03
| parent author | gmikeska07 |
| parent permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| author | steemitboard |
| permlink | steemitboard-notify-gmikeska07-20180714t235505000z |
| title | |
| body | Congratulations @gmikeska07! You have received a personal award! [](http://steemitboard.com/@gmikeska07) 2 Years on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** [SteemitBoard World Cup Contest - Play-off for third result](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-play-off-for-third-result) --- **Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!** Collect World Cup badges and win free SBD Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1) --- > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #24182131/Trx e17bea03340645b3454e901deeaac3a3fdf697c1 |
View Raw JSON Data
{
"trx_id": "e17bea03340645b3454e901deeaac3a3fdf697c1",
"block": 24182131,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-14T23:55:03",
"op": [
"comment",
{
"parent_author": "gmikeska07",
"parent_permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"author": "steemitboard",
"permlink": "steemitboard-notify-gmikeska07-20180714t235505000z",
"title": "",
"body": "Congratulations @gmikeska07! You have received a personal award!\n\n[](http://steemitboard.com/@gmikeska07) 2 Years on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n[SteemitBoard World Cup Contest - Play-off for third result](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-play-off-for-third-result)\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2017/12/13 18:11:39
2017/12/13 18:11:39
| voter | cryptocamel |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18056396/Trx 0ad917dbc389d260e581144dbc90c2aee3d55efa |
View Raw JSON Data
{
"trx_id": "0ad917dbc389d260e581144dbc90c2aee3d55efa",
"block": 18056396,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-13T18:11:39",
"op": [
"vote",
{
"voter": "cryptocamel",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"weight": 10000
}
]
}2017/07/14 22:25:12
2017/07/14 22:25:12
| parent author | gmikeska07 |
| parent permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| author | steemitboard |
| permlink | steemitboard-notify-gmikeska07-20170714t222514000z |
| title | |
| body | Congratulations @gmikeska07! You have received a personal award! [](http://steemitboard.com/@gmikeska07) Happy Birthday - 1 Year Click on the badge to view your own Board of Honor on SteemitBoard. For more information about this award, click [here](https://steemit.com/steemitboard/@steemitboard/steemitboard-update-8-happy-birthday) > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #13687604/Trx a47f7c7d966ea5a77edce789fcbbbed4ef119c80 |
View Raw JSON Data
{
"trx_id": "a47f7c7d966ea5a77edce789fcbbbed4ef119c80",
"block": 13687604,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-14T22:25:12",
"op": [
"comment",
{
"parent_author": "gmikeska07",
"parent_permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"author": "steemitboard",
"permlink": "steemitboard-notify-gmikeska07-20170714t222514000z",
"title": "",
"body": "Congratulations @gmikeska07! You have received a personal award!\n\n[](http://steemitboard.com/@gmikeska07) Happy Birthday - 1 Year\nClick on the badge to view your own Board of Honor on SteemitBoard.\n\nFor more information about this award, click [here](https://steemit.com/steemitboard/@steemitboard/steemitboard-update-8-happy-birthday)\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}2017/05/31 22:29:57
2017/05/31 22:29:57
| voter | mrstaf |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12422444/Trx 68520c7267e327b0c24492984c3859dfad010f75 |
View Raw JSON Data
{
"trx_id": "68520c7267e327b0c24492984c3859dfad010f75",
"block": 12422444,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-05-31T22:29:57",
"op": [
"vote",
{
"voter": "mrstaf",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"weight": 10000
}
]
}| voter | aaseb |
| author | gmikeska07 |
| permlink | re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220422757z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3543903/Trx f50e4ffd7d2bbc564c2b3dcb8512be463aba5d37 |
View Raw JSON Data
{
"trx_id": "f50e4ffd7d2bbc564c2b3dcb8512be463aba5d37",
"block": 3543903,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T23:42:18",
"op": [
"vote",
{
"voter": "aaseb",
"author": "gmikeska07",
"permlink": "re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220422757z",
"weight": 10000
}
]
}| parent author | gmikeska07 |
| parent permlink | re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220422757z |
| author | aaseb |
| permlink | re-gmikeska07-re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t234140133z |
| title | |
| body | that's what I seem to remember the white hat attack... So the devs have control of the funds from the non-forked DAO. I think they should find a way to give it back no? |
| json metadata | {"tags":["ether"]} |
| Transaction Info | Block #3543898/Trx 5801192191706194f76bed490ae3e144dba62b80 |
View Raw JSON Data
{
"trx_id": "5801192191706194f76bed490ae3e144dba62b80",
"block": 3543898,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T23:42:03",
"op": [
"comment",
{
"parent_author": "gmikeska07",
"parent_permlink": "re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220422757z",
"author": "aaseb",
"permlink": "re-gmikeska07-re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t234140133z",
"title": "",
"body": "that's what I seem to remember the white hat attack... So the devs have control of the funds from the non-forked DAO. I think they should find a way to give it back no?",
"json_metadata": "{\"tags\":[\"ether\"]}"
}
]
}religionupvoted (100.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
religionupvoted (100.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
| voter | religion |
| author | gmikeska07 |
| permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3543854/Trx fbae702ac67b92e98fd8f62bdb659440d5812caa |
View Raw JSON Data
{
"trx_id": "fbae702ac67b92e98fd8f62bdb659440d5812caa",
"block": 3543854,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T23:39:51",
"op": [
"vote",
{
"voter": "religion",
"author": "gmikeska07",
"permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"weight": 10000
}
]
}biitoremoved vote from (0.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
biitoremoved vote from (0.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
| voter | biito |
| author | gmikeska07 |
| permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| weight | 0 (0.00%) |
| Transaction Info | Block #3543461/Trx 60597916f66d1d1801ece491a2d84f67663477d3 |
View Raw JSON Data
{
"trx_id": "60597916f66d1d1801ece491a2d84f67663477d3",
"block": 3543461,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T23:20:09",
"op": [
"vote",
{
"voter": "biito",
"author": "gmikeska07",
"permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"weight": 0
}
]
}biitoupvoted (100.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
biitoupvoted (100.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
| voter | biito |
| author | gmikeska07 |
| permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3543458/Trx eb5eb1e37f2a595e6b981d3c2f4a751e6acaf31c |
View Raw JSON Data
{
"trx_id": "eb5eb1e37f2a595e6b981d3c2f4a751e6acaf31c",
"block": 3543458,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T23:20:00",
"op": [
"vote",
{
"voter": "biito",
"author": "gmikeska07",
"permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"weight": 10000
}
]
}chakra74upvoted (100.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
chakra74upvoted (100.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
| voter | chakra74 |
| author | gmikeska07 |
| permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3543249/Trx 305fca989dd3de4120e5a2653dcfed889d6467fb |
View Raw JSON Data
{
"trx_id": "305fca989dd3de4120e5a2653dcfed889d6467fb",
"block": 3543249,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T23:09:30",
"op": [
"vote",
{
"voter": "chakra74",
"author": "gmikeska07",
"permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"weight": 10000
}
]
}gmikeska07upvoted (100.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
gmikeska07upvoted (100.00%) @gmikeska07 / a-look-ahead-more-hard-forks-in-ethereum-s-future
| voter | gmikeska07 |
| author | gmikeska07 |
| permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3543245/Trx 20d9658392938e168dc793bd495885024239f518 |
View Raw JSON Data
{
"trx_id": "20d9658392938e168dc793bd495885024239f518",
"block": 3543245,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T23:09:18",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "gmikeska07",
"permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"weight": 10000
}
]
}gmikeska07published a new post: a-look-ahead-more-hard-forks-in-ethereum-s-future
gmikeska07published a new post: a-look-ahead-more-hard-forks-in-ethereum-s-future
| parent author | |
| parent permlink | ethereum |
| author | gmikeska07 |
| permlink | a-look-ahead-more-hard-forks-in-ethereum-s-future |
| title | A look ahead -- More Hard-Forks in Ethereum's Future? |
| body | https://www.cryptocoinsnews.com/wp-content/uploads/2016/07/Fork-and-straight-384x253.jpg I have been following Ethereum with interest since its announcement. I started learning solidity recently and have mocked up a DAO framework or two. However, Today I Learned™ that Ethereum's POW phase is scheduled to kick-in soon-ish: [a helpful stackExchange article](https://ethereum.stackexchange.com/questions/3779/when-will-the-difficulty-bomb-make-mining-impossible/3800) estimates: >**Blocktime over one day in July 2017** Difficulty on 2017-08-02 is 219.9 P and average blocktime is 26.06 hours. Difficulty on 2017-09-05 is 879.6 P and average blocktime is 4.342 days. **Blocktime over one week in September 2017** Difficulty on 2017-10-02 is 2.639 E and average blocktime is 13.02 days. **Blocktime over one month in October 2017** Difficulty on 2017-11-05 is 10.55 E and average blocktime is 7.443 weeks. Difficulty on 2017-12-01 is 28.14 E and average blocktime is 4.962 month. Difficulty on 2018-01-05 is 112.5 E and average blocktime is 19.84 month. I heard that the so called "Ice Age" is going to be delayed. I have seen [sources](https://forum.ethereum.org/discussion/5668/vb-end-of-pow-will-be-delayed) that say a HF is necessary for such a change. Is that true? It would be interesting to see the dynamics of a currency that proceeds ahead with POS in lieu of such a hardfork. Discuss.... :-) |
| json metadata | {"tags":["ethereum","blockchain","ethereum-classic","money","fiat",""],"image":["https://www.cryptocoinsnews.com/wp-content/uploads/2016/07/Fork-and-straight-384x253.jpg"]} |
| Transaction Info | Block #3543245/Trx 20d9658392938e168dc793bd495885024239f518 |
View Raw JSON Data
{
"trx_id": "20d9658392938e168dc793bd495885024239f518",
"block": 3543245,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T23:09:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ethereum",
"author": "gmikeska07",
"permlink": "a-look-ahead-more-hard-forks-in-ethereum-s-future",
"title": "A look ahead -- More Hard-Forks in Ethereum's Future?",
"body": "https://www.cryptocoinsnews.com/wp-content/uploads/2016/07/Fork-and-straight-384x253.jpg\nI have been following Ethereum with interest since its announcement. I started learning solidity recently and have mocked up a DAO framework or two. However, Today I Learned™ that Ethereum's POW phase is scheduled to kick-in soon-ish: [a helpful stackExchange article](https://ethereum.stackexchange.com/questions/3779/when-will-the-difficulty-bomb-make-mining-impossible/3800) estimates:\n>**Blocktime over one day in July 2017**\nDifficulty on 2017-08-02 is 219.9 P and average blocktime is 26.06 hours.\nDifficulty on 2017-09-05 is 879.6 P and average blocktime is 4.342 days.\n**Blocktime over one week in September 2017**\nDifficulty on 2017-10-02 is 2.639 E and average blocktime is 13.02 days.\n**Blocktime over one month in October 2017**\nDifficulty on 2017-11-05 is 10.55 E and average blocktime is 7.443 weeks.\nDifficulty on 2017-12-01 is 28.14 E and average blocktime is 4.962 month.\nDifficulty on 2018-01-05 is 112.5 E and average blocktime is 19.84 month.\n\nI heard that the so called \"Ice Age\" is going to be delayed.\n\nI have seen [sources](https://forum.ethereum.org/discussion/5668/vb-end-of-pow-will-be-delayed) that say a HF is necessary for such a change. Is that true?\nIt would be interesting to see the dynamics of a currency that proceeds ahead with POS in lieu of such a hardfork.\n\nDiscuss.... :-)",
"json_metadata": "{\"tags\":[\"ethereum\",\"blockchain\",\"ethereum-classic\",\"money\",\"fiat\",\"\"],\"image\":[\"https://www.cryptocoinsnews.com/wp-content/uploads/2016/07/Fork-and-straight-384x253.jpg\"]}"
}
]
}| parent author | gmikeska07 |
| parent permlink | re-madhatting-re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220619512z |
| author | madhatting |
| permlink | re-gmikeska07-re-madhatting-re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t221749696z |
| title | |
| body | OMG, I cant breath... Why do you say that. :-(.. I put everything into this. |
| json metadata | {"tags":["ether"]} |
| Transaction Info | Block #3542200/Trx 9371461463330b1488d5f78c63cc1c606d04bcc2 |
View Raw JSON Data
{
"trx_id": "9371461463330b1488d5f78c63cc1c606d04bcc2",
"block": 3542200,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T22:16:48",
"op": [
"comment",
{
"parent_author": "gmikeska07",
"parent_permlink": "re-madhatting-re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220619512z",
"author": "madhatting",
"permlink": "re-gmikeska07-re-madhatting-re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t221749696z",
"title": "",
"body": "OMG, I cant breath... Why do you say that. :-(.. I put everything into this.",
"json_metadata": "{\"tags\":[\"ether\"]}"
}
]
}| voter | gmikeska07 |
| author | madhatting |
| permlink | re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t215655528z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3541994/Trx b61acf4e0218eec0cb81c17691e7b2dd2f301697 |
View Raw JSON Data
{
"trx_id": "b61acf4e0218eec0cb81c17691e7b2dd2f301697",
"block": 3541994,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T22:06:24",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "madhatting",
"permlink": "re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t215655528z",
"weight": 10000
}
]
}| parent author | madhatting |
| parent permlink | re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t215655528z |
| author | gmikeska07 |
| permlink | re-madhatting-re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220619512z |
| title | |
| body | I think Bernie needs a bailout now too, @madhatting..... |
| json metadata | {"tags":["ether"]} |
| Transaction Info | Block #3541993/Trx 7350979706b634d3653afb999f05ed5049d25be5 |
View Raw JSON Data
{
"trx_id": "7350979706b634d3653afb999f05ed5049d25be5",
"block": 3541993,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T22:06:21",
"op": [
"comment",
{
"parent_author": "madhatting",
"parent_permlink": "re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t215655528z",
"author": "gmikeska07",
"permlink": "re-madhatting-re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220619512z",
"title": "",
"body": "I think Bernie needs a bailout now too, @madhatting.....",
"json_metadata": "{\"tags\":[\"ether\"]}"
}
]
}| voter | gmikeska07 |
| author | aaseb |
| permlink | shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3541958/Trx 80f804485fa3261635cf206148605cb2c97a861b |
View Raw JSON Data
{
"trx_id": "80f804485fa3261635cf206148605cb2c97a861b",
"block": 3541958,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T22:04:30",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "aaseb",
"permlink": "shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain",
"weight": 10000
}
]
}| parent author | aaseb |
| parent permlink | shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain |
| author | gmikeska07 |
| permlink | re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220422757z |
| title | |
| body | They (the #Forked #ETH devs) were discussing dumping the #ETC from the DAO to depress the price. Not sure that attack vector would be economically viable given the volume we're now seeing on #Poloniex. Further I think that the ETH folks are realizing that they *can't* do anything about the fork, so there's less political viability as well. It will be interesting to see how this plays out. I wish there was a remindme bot for steemit! |
| json metadata | {"tags":["ether"]} |
| Transaction Info | Block #3541956/Trx 3500ad88d8ef6979e56fabddab75201517b47bcd |
View Raw JSON Data
{
"trx_id": "3500ad88d8ef6979e56fabddab75201517b47bcd",
"block": 3541956,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T22:04:24",
"op": [
"comment",
{
"parent_author": "aaseb",
"parent_permlink": "shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain",
"author": "gmikeska07",
"permlink": "re-aaseb-shouldn-t-we-be-able-to-get-etc-back-from-dao-on-the-non-forked-chain-20160726t220422757z",
"title": "",
"body": "They (the #Forked #ETH devs) were discussing dumping the #ETC from the DAO to depress the price. Not sure that attack vector would be economically viable given the volume we're now seeing on #Poloniex. Further I think that the ETH folks are realizing that they *can't* do anything about the fork, so there's less political viability as well. It will be interesting to see how this plays out. \n\nI wish there was a remindme bot for steemit!",
"json_metadata": "{\"tags\":[\"ether\"]}"
}
]
}gmikeska07powered up 1.711 STEEM to @gmikeska07
gmikeska07powered up 1.711 STEEM to @gmikeska07
| from | gmikeska07 |
| to | gmikeska07 |
| amount | 1.711 STEEM |
| Transaction Info | Block #3517735/Trx 8745614291ff6be5a1b6508f828c05916616ac6c |
View Raw JSON Data
{
"trx_id": "8745614291ff6be5a1b6508f828c05916616ac6c",
"block": 3517735,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-26T01:41:00",
"op": [
"transfer_to_vesting",
{
"from": "gmikeska07",
"to": "gmikeska07",
"amount": "1.711 STEEM"
}
]
}gmikeska07conversion request filled: received 1.711 STEEM in exchange of 6.218 SBD
gmikeska07conversion request filled: received 1.711 STEEM in exchange of 6.218 SBD
| owner | gmikeska07 |
| requestid | 1468870733 |
| amount in | 6.218 SBD |
| amount out | 1.711 STEEM |
| Transaction Info | Block #3510572/Virtual Operation #2 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 3510572,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 2,
"timestamp": "2016-07-25T19:39:00",
"op": [
"fill_convert_request",
{
"owner": "gmikeska07",
"requestid": 1468870733,
"amount_in": "6.218 SBD",
"amount_out": "1.711 STEEM"
}
]
}| voter | bitkoyin |
| author | gmikeska07 |
| permlink | helicopter-seen-shooting-state-broadcaster-s-hq-in-ankara-explosions-heard-rt-com |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3388853/Trx cdfb667538de5a824b2cb4bdda1be38371ae0952 |
View Raw JSON Data
{
"trx_id": "cdfb667538de5a824b2cb4bdda1be38371ae0952",
"block": 3388853,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-21T13:03:00",
"op": [
"vote",
{
"voter": "bitkoyin",
"author": "gmikeska07",
"permlink": "helicopter-seen-shooting-state-broadcaster-s-hq-in-ankara-explosions-heard-rt-com",
"weight": 10000
}
]
}gmikeska07upvoted (100.00%) @ozmaster / today-s-smoke
gmikeska07upvoted (100.00%) @ozmaster / today-s-smoke
| voter | gmikeska07 |
| author | ozmaster |
| permlink | today-s-smoke |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3359809/Trx 97f3c7217a2fe277073689bc196f53c5a1ea2cb3 |
View Raw JSON Data
{
"trx_id": "97f3c7217a2fe277073689bc196f53c5a1ea2cb3",
"block": 3359809,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-20T12:36:03",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "ozmaster",
"permlink": "today-s-smoke",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | kingjohal |
| permlink | re-gmikeska07-re-kingjohal-steemstarter-campaign-steem-android-wallet-nfc-tap-and-pay-integration-20160717t041049223z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3348503/Trx 8ea0f7f14b692d6ea51dfd02fc9e8ecff3a156c9 |
View Raw JSON Data
{
"trx_id": "8ea0f7f14b692d6ea51dfd02fc9e8ecff3a156c9",
"block": 3348503,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-20T03:04:36",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "kingjohal",
"permlink": "re-gmikeska07-re-kingjohal-steemstarter-campaign-steem-android-wallet-nfc-tap-and-pay-integration-20160717t041049223z",
"weight": 10000
}
]
}| parent author | kingjohal |
| parent permlink | re-gmikeska07-re-kingjohal-steemstarter-campaign-steem-android-wallet-nfc-tap-and-pay-integration-20160717t041049223z |
| author | gmikeska07 |
| permlink | re-kingjohal-re-gmikeska07-re-kingjohal-steemstarter-campaign-steem-android-wallet-nfc-tap-and-pay-integration-20160720t030414785z |
| title | |
| body | 19vCeH21gSD41MxC2LGiZBru18ifN3XQ8b thanks! |
| json metadata | {"tags":["proposals"]} |
| Transaction Info | Block #3348498/Trx e209d58a94c0086ff4b806416c88064c7b4878e6 |
View Raw JSON Data
{
"trx_id": "e209d58a94c0086ff4b806416c88064c7b4878e6",
"block": 3348498,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-20T03:04:21",
"op": [
"comment",
{
"parent_author": "kingjohal",
"parent_permlink": "re-gmikeska07-re-kingjohal-steemstarter-campaign-steem-android-wallet-nfc-tap-and-pay-integration-20160717t041049223z",
"author": "gmikeska07",
"permlink": "re-kingjohal-re-gmikeska07-re-kingjohal-steemstarter-campaign-steem-android-wallet-nfc-tap-and-pay-integration-20160720t030414785z",
"title": "",
"body": "19vCeH21gSD41MxC2LGiZBru18ifN3XQ8b thanks!",
"json_metadata": "{\"tags\":[\"proposals\"]}"
}
]
}gmikeska07custom json: follow
gmikeska07custom json: follow
| required auths | [] |
| required posting auths | ["gmikeska07"] |
| id | follow |
| json | {"follower":"gmikeska07","following":"bryan-kho","what":["blog"]} |
| Transaction Info | Block #3347697/Trx bc00b9e48d6e213b8eec481f34cd6f28971e3f57 |
View Raw JSON Data
{
"trx_id": "bc00b9e48d6e213b8eec481f34cd6f28971e3f57",
"block": 3347697,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-20T02:23:54",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"gmikeska07"
],
"id": "follow",
"json": "{\"follower\":\"gmikeska07\",\"following\":\"bryan-kho\",\"what\":[\"blog\"]}"
}
]
}gmikeska07upvoted (100.00%) @bryan-kho / hi-from-melbourne-australia
gmikeska07upvoted (100.00%) @bryan-kho / hi-from-melbourne-australia
| voter | gmikeska07 |
| author | bryan-kho |
| permlink | hi-from-melbourne-australia |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3347690/Trx d4316f4ea66040aee3de403c4a3d2c193f5289c2 |
View Raw JSON Data
{
"trx_id": "d4316f4ea66040aee3de403c4a3d2c193f5289c2",
"block": 3347690,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-20T02:23:33",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "bryan-kho",
"permlink": "hi-from-melbourne-australia",
"weight": 10000
}
]
}| parent author | gridcoinman |
| parent permlink | wallsteetjournal-the-central-bankers-bold-new-idea-greater-than-print-bitcoins |
| author | gmikeska07 |
| permlink | re-gridcoinman-wallsteetjournal-the-central-bankers-bold-new-idea-greater-than-print-bitcoins-20160720t021940234z |
| title | |
| body | One dynamic that many companies and governments are realizing is that having a permissioned ledger is meaningless unless you tie to Bitcoin at some point as a trust anchor. I think that with a FedCoin we'd see their block hashes printed on the Bitcoin blockchain. This would, in turn, increase Bitcoin's value long-term. |
| json metadata | {"tags":["bitcoin"]} |
| Transaction Info | Block #3347614/Trx d5a4f714600ecf11b1537447da293e6c2aa13b18 |
View Raw JSON Data
{
"trx_id": "d5a4f714600ecf11b1537447da293e6c2aa13b18",
"block": 3347614,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-20T02:19:45",
"op": [
"comment",
{
"parent_author": "gridcoinman",
"parent_permlink": "wallsteetjournal-the-central-bankers-bold-new-idea-greater-than-print-bitcoins",
"author": "gmikeska07",
"permlink": "re-gridcoinman-wallsteetjournal-the-central-bankers-bold-new-idea-greater-than-print-bitcoins-20160720t021940234z",
"title": "",
"body": "One dynamic that many companies and governments are realizing is that having a permissioned ledger is meaningless unless you tie to Bitcoin at some point as a trust anchor. I think that with a FedCoin we'd see their block hashes printed on the Bitcoin blockchain. This would, in turn, increase Bitcoin's value long-term.",
"json_metadata": "{\"tags\":[\"bitcoin\"]}"
}
]
}| voter | gmikeska07 |
| author | decryptson |
| permlink | why-steemit-has-a-good-chance-to-become-the-worlds-next-revolutionary-social-media-platform |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3347531/Trx c368f61c1438bea436fd5f7efa6d66b257935e1d |
View Raw JSON Data
{
"trx_id": "c368f61c1438bea436fd5f7efa6d66b257935e1d",
"block": 3347531,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-20T02:15:36",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "decryptson",
"permlink": "why-steemit-has-a-good-chance-to-become-the-worlds-next-revolutionary-social-media-platform",
"weight": 10000
}
]
}gmikeska07upvoted (100.00%) @bansky / robot
gmikeska07upvoted (100.00%) @bansky / robot
| voter | gmikeska07 |
| author | bansky |
| permlink | robot |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3347501/Trx 13732113c2ac6340d6fb9873f2ff1c8a8287af73 |
View Raw JSON Data
{
"trx_id": "13732113c2ac6340d6fb9873f2ff1c8a8287af73",
"block": 3347501,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-20T02:14:06",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "bansky",
"permlink": "robot",
"weight": 10000
}
]
}| voter | madhatting |
| author | gmikeska07 |
| permlink | re-kingjohal-steemstarter-campaign-steem-android-wallet-nfc-tap-and-pay-integration-20160717t033728873z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3320967/Trx 710fa2e635e99a3de0a5577ea4f6f962385c11dc |
View Raw JSON Data
{
"trx_id": "710fa2e635e99a3de0a5577ea4f6f962385c11dc",
"block": 3320967,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T03:57:42",
"op": [
"vote",
{
"voter": "madhatting",
"author": "gmikeska07",
"permlink": "re-kingjohal-steemstarter-campaign-steem-android-wallet-nfc-tap-and-pay-integration-20160717t033728873z",
"weight": 10000
}
]
}gmikeska07upvoted (100.00%) @pharesim / pevo-funding-cut-off
gmikeska07upvoted (100.00%) @pharesim / pevo-funding-cut-off
| voter | gmikeska07 |
| author | pharesim |
| permlink | pevo-funding-cut-off |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3316801/Trx 88b125429d870923ae6e51691aea4b47c2eeb2c7 |
View Raw JSON Data
{
"trx_id": "88b125429d870923ae6e51691aea4b47c2eeb2c7",
"block": 3316801,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:28:03",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "pharesim",
"permlink": "pevo-funding-cut-off",
"weight": 10000
}
]
}gmikeska07upvoted (100.00%) @bola / developers-programmers-will-flock-steemit
gmikeska07upvoted (100.00%) @bola / developers-programmers-will-flock-steemit
| voter | gmikeska07 |
| author | bola |
| permlink | developers-programmers-will-flock-steemit |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3316698/Trx 63a1afbd57c6408c373b16ee545f1324f9780a6b |
View Raw JSON Data
{
"trx_id": "63a1afbd57c6408c373b16ee545f1324f9780a6b",
"block": 3316698,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:22:54",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "bola",
"permlink": "developers-programmers-will-flock-steemit",
"weight": 10000
}
]
}gmikeska07published a new post: securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock
gmikeska07published a new post: securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock
| parent author | |
| parent permlink | bitcoin |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| title | A Solution to the Centralization of Mining Power - Securization of Miner Ownership |
| body | @@ -143,16 +143,17 @@ 237.png%0A +%0A A Brief |
| json metadata | {"tags":["bitcoin","bitcoin-mining","cryptocurrency","money","decentralize","d10e","ethereum","mining"],"users":["gmikeska07"],"image":["http://bitcoinchaser.com/wp-content/uploads/2015/10/miner-300x237.png"]} |
| Transaction Info | Block #3316687/Trx 23c47378df7794a548475fe39a2adcbe56e46682 |
View Raw JSON Data
{
"trx_id": "23c47378df7794a548475fe39a2adcbe56e46682",
"block": 3316687,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:22:21",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"title": "A Solution to the Centralization of Mining Power - Securization of Miner Ownership",
"body": "@@ -143,16 +143,17 @@\n 237.png%0A\n+%0A\n A Brief \n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"bitcoin-mining\",\"cryptocurrency\",\"money\",\"decentralize\",\"d10e\",\"ethereum\",\"mining\"],\"users\":[\"gmikeska07\"],\"image\":[\"http://bitcoinchaser.com/wp-content/uploads/2015/10/miner-300x237.png\"]}"
}
]
}| parent author | gmikeska07 |
| parent permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| author | gmikeska07 |
| permlink | re-gmikeska07-securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock-20160719t001724704z |
| title | |
| body | @@ -186,16 +186,24 @@ ckchain +related company |
| json metadata | {"tags":["bitcoin"]} |
| Transaction Info | Block #3316639/Trx 404c4cc7bc9f64f6b0b3397d4e7262a8bb026908 |
View Raw JSON Data
{
"trx_id": "404c4cc7bc9f64f6b0b3397d4e7262a8bb026908",
"block": 3316639,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:19:57",
"op": [
"comment",
{
"parent_author": "gmikeska07",
"parent_permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"author": "gmikeska07",
"permlink": "re-gmikeska07-securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock-20160719t001724704z",
"title": "",
"body": "@@ -186,16 +186,24 @@\n ckchain \n+related \n company \n",
"json_metadata": "{\"tags\":[\"bitcoin\"]}"
}
]
}gmikeska07published a new post: securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock
gmikeska07published a new post: securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock
| parent author | |
| parent permlink | bitcoin |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| title | A Solution to the Centralization of Mining Power - Securization of Miner Ownership |
| body | @@ -73,16 +73,86 @@ otstock%0A +http://bitcoinchaser.com/wp-content/uploads/2015/10/miner-300x237.png%0A A Brief |
| json metadata | {"tags":["bitcoin","bitcoin-mining","cryptocurrency","money","decentralize","d10e","ethereum","mining"],"users":["gmikeska07"],"image":["http://bitcoinchaser.com/wp-content/uploads/2015/10/miner-300x237.png"]} |
| Transaction Info | Block #3316614/Trx 0081e39e815a82c28c8df4618684b7db5325d0e5 |
View Raw JSON Data
{
"trx_id": "0081e39e815a82c28c8df4618684b7db5325d0e5",
"block": 3316614,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:18:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"title": "A Solution to the Centralization of Mining Power - Securization of Miner Ownership",
"body": "@@ -73,16 +73,86 @@\n otstock%0A\n+http://bitcoinchaser.com/wp-content/uploads/2015/10/miner-300x237.png%0A\n A Brief \n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"bitcoin-mining\",\"cryptocurrency\",\"money\",\"decentralize\",\"d10e\",\"ethereum\",\"mining\"],\"users\":[\"gmikeska07\"],\"image\":[\"http://bitcoinchaser.com/wp-content/uploads/2015/10/miner-300x237.png\"]}"
}
]
}| parent author | gmikeska07 |
| parent permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| author | gmikeska07 |
| permlink | re-gmikeska07-securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock-20160719t001724704z |
| title | |
| body | I thought I'd add a note here about myself. I am a developer hoping to be discovered by someone in the Bitcoin sector. I'm contracting to survive while sending applications to every blockchain company I can get in touch with. I hope to help implement technologies to further the cryptocurrency industry! Thanks for reading my idea! Feedback is welcome! |
| json metadata | {"tags":["bitcoin"]} |
| Transaction Info | Block #3316589/Trx b35624c3d03a29e93ba9114ba38aee4cc36436d4 |
View Raw JSON Data
{
"trx_id": "b35624c3d03a29e93ba9114ba38aee4cc36436d4",
"block": 3316589,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:17:27",
"op": [
"comment",
{
"parent_author": "gmikeska07",
"parent_permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"author": "gmikeska07",
"permlink": "re-gmikeska07-securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock-20160719t001724704z",
"title": "",
"body": "I thought I'd add a note here about myself. I am a developer hoping to be discovered by someone in the Bitcoin sector. I'm contracting to survive while sending applications to every blockchain company I can get in touch with. I hope to help implement technologies to further the cryptocurrency industry!\nThanks for reading my idea! Feedback is welcome!",
"json_metadata": "{\"tags\":[\"bitcoin\"]}"
}
]
}gmikeska07published a new post: securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock
gmikeska07published a new post: securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock
| parent author | |
| parent permlink | bitcoin |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| title | A Solution to the Centralization of Mining Power - Securization of Miner Ownership |
| body | # Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock A Brief White Paper by @gmikeska07 # Introduction Mining is a crucial function in the Bitcoin ecosystem. Concerns abound over potential centralization of mining power into the hands of mining cartels which may or may not be benevolent oligarchs. Attempts at innovation in the mining space, though well-intentioned and, often, well executed have fallen short of incentivizing a trend toward decentralization of mining power. Mining “contracts” and “bonds” were the first instruments used to allow investment in mining projects. Companies offering such investment opportunities set up warehouses of GPU and FPGA miners, and offered contracts at a flat rate based on hashrate offered and contract duration. Often, companies offering mining contracts would allow the investor to specify a pool toward which the mining power would be directed. Unfortunately, the hashrate avalanche that resulted from the flood of investment during this period caused many ingenuous offerings to lose production capability quickly because of Bitcoin’s rapidly increasing difficulty during this period. As the first ASIC machines came online, the community was excited to see the advent of “cloud mining” services which make investment in cryptocurrency mining trivial for anyone who has interacted with a modern trading interface. Many entries in this space failed to perform as expected, again, due to the difficulty increases from rapid innovation occurring at this point. Still other companies claiming to offer cloud mining services disappeared seemingly overnight, taking investor funds with them. Further, most cloud mining operations don’t allow the investor to specify a mining pool in which they would like their hashrate to participate. This incentivizes a trend toward centralization, with specific cases in mind of cloud providers approaching 51% of network mining power. Along with contracts and cloud mining, some companies offer miner hosting. With miner hosting, an investor retains ownership of the hardware and control over pool participation. The investor pays maintenance fees to the hosting provider, who is responsible for securing, powering, and maintaining the hardware. Investors can usually take delivery of their mining hardware at any time, and may then sell the miner, operate it locally, or find another hosting company for the miner. This approach, though properly incentivized, drastically reduces the liquidity of the miner as a resource, as the owner must take ownership of the hardware if he wishes to switch hosting companies or market the hardware to another investor. The approach described in this document uses smart contracts on the Rootstock (RSK) network to commoditize ownership of mining hardware and facilitate issue of derivative instruments, based upon the hashing power of the hardware in question, as tokens. I want this document to be read as a recommendation, or an “Invitation to discussion” if you will. Many details of implementation will require some modicum of community consensus before an approach like this can succeed. # Vocabulary Mining Hardware - Any device or group of devices that emit shares which can be directed toward a mining pool. Miner Hosting Provider - An individual or organization which take custody of mining hardware and operate it on behalf of an investor, collecting maintenance fees in return. Provider Contract - A contract which performs blockchain-data management functions on behalf of a specific hosting provider. Such a contract should be considered implementation of a protocol to facilitate interoperability with other provider contracts. Implementation should begin only after adequate community discussion. Hardware Contract - A contract issued by a provider when new mining hardware is brought online. The provider is responsible for configuring the contract to reflect ownership by an address specified by the initial investor. Again, care should be taken in implementing these contracts to maximize interoperability with related systems. Initial Investor - An individual or organization that puts down initial investment on mining hardware. # The Provider Contract The provider, to bootstrap his endeavor, issues a contract that holds all metadata about the operation. Contact information, number of hardware spots available (perhaps the community can come to an agreement on standard sizing of hardware) and maintenance fee information can all be enumerated in the contract, with “owner-only” accessor methods to provide update capabilities. Contracts representing hardware housed by a given provider will contain a reference to this contract so that the intrinsic “reputation” of the provider can substantiate the condition scores and other metrics the provider is responsible for maintaining. (More on these later). The establishment of a contract as the basis for reference to a hosting provider allows ownership to be passed on to other organizations (distributed or otherwise) in the future. # Equipment Purchase/Assay Process Initial investors may either purchase equipment and have it shipped to a hosting facility, or may order hardware through the hosting provider. The provider must then assay the hardware, (much like the process for admitting large-ingot gold bars to the financial system) checking for physical as well as performance issues. During assay, the provider rates the overall condition of the hardware (new, good, poor, etc), and may test the miner’s hashrate (Though as a sign of goodwill to the investor, I recommend that any assay related mining be conducted on testnet, or that revenue be identified and perhaps loaded into the investor’s account to cover initial maintenance fees). The provider then issues a contract, sets the variable for “owner” in the contract to the address specified by their investor at time of purchase or onboarding. # Mining Pools and Protocol Enhancements Mining pools stand to greatly benefit if a contract-focused securitization of mining power succeeds. That being said, these benefits will require some changes to the protocols that pools use to communicate to worker nodes, and APIs will need to be constructed to allow owner specification of mining pool preference. Another pool API should be architected to allow hardware owners to pay maintenance fees to their hosting provider out of pool revenue if they so choose. I also think that it might be worthwhile to investigate the idea of mining pools issuing a share-count statement whenever they discover a block. The statement would certify the percentages of work that each worker contributed to block discovery, referring to each worker by the address of its associated contract. Such certification could provide an indelible record of the performance of a piece of hardware, and enforce accountability for pool operators, hosting providers and investors alike. # Ownership Transfer An investor may decide to sell his hardware at any time. The recent explosion of interest in DAOs have driven many centralized exchanges to support trading of tokens. Support for trading of contracts that represent mining hardware should be well within reach. Just as one must transfer tokens to an address corresponding to his account on an exchange, an investor looking to market his mining hardware need only call the ‘changeOwner’ function on the contract. Exchanges could use the metadata in the hardware contract to build a description of the equipment. Further, just as exchanges have accommodated users in execution of DAO functions through their tokens, a proxy for update/maintenance of miner information could be provided. # Tokenization of Equipment Ownership The investor may decide to maintain some stake in the hardware when seeking to defer costs. This can be undertaken simply by creating a DAO contract and passing ownership of the hardware contract to the DAO. Details on how DAO members can then vote on changes to the miner’s pool status, request a provider transfer, or acommodate distribution of mining revenue to tokenholders are discussed at length in the DAO white paper (https://download.slock.it/public/DAO/WhitePaper.pdf) and are beyond the scope of this document. # Provider Transfer Keeping the market for miner hosting both open and flexible is crucial to the securitization of mining power. Protocols for issuing requests for hardware transfer from one hosting provider to another will need to be designed, but these tasks can be handled through the provider and hardware contract implementations. Requests can be initiated by the owner of a piece of hardware, perhaps via a function call to the new provider. The function call could carry fees to cover shipping along with initial maintenance fees and assay service Then, the “New Provider” would send a notification of transfer to the provider in custody of the hardware in question. This method call could reference the payment they received to vouch that the transaction came from the address listed as the owner of the hardware. # A note on Interoperability vs. Competition While it is crucial that the community develop contract interfaces which are interoperable, I see no problem at all with healthy competition between individual contract stacks. That is to say, though we may delineate standard function names and data fields, differences in the way these protocols are implemented will foster healthy growth for contract stacks across the board. ```` -----BEGIN SIGNATURE BLOCK TEXT----- Document: Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock Date: July 9th, 2016 Author: Gregory J. Mikeska Signatory Address:1KDPgyR4kvbazDMYNFzcyr8HrCaNPmSjLZ -----END SIGNATURE BLOCK TEXT----- -----BEGIN SIGNATURE BLOCK----- IPTVp5ZWZe3QAH8ZC26Ytte68T//8fYgEz6bLaWwD1VjJpDek31XaMF4CJQ+FEQ2wQfwXv1C3C0DDMs5Ds7kt3E= -----END SIGNATURE BLOCK-----```` |
| json metadata | {"tags":["bitcoin","bitcoin-mining","cryptocurrency","money","decentralize","d10e","ethereum","mining"],"users":["gmikeska07"],"links":["https://download.slock.it/public/DAO/WhitePaper.pdf"]} |
| Transaction Info | Block #3316523/Trx cb8ba99f6d9451f8254eab53b98f9d8ace3ae5e6 |
View Raw JSON Data
{
"trx_id": "cb8ba99f6d9451f8254eab53b98f9d8ace3ae5e6",
"block": 3316523,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:14:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"title": "A Solution to the Centralization of Mining Power - Securization of Miner Ownership",
"body": "# Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock\nA Brief White Paper by @gmikeska07\n# Introduction\nMining is a crucial function in the Bitcoin ecosystem. Concerns abound over potential centralization of mining power into the hands of mining cartels which may or may not be benevolent oligarchs. Attempts at innovation in the mining space, though well-intentioned and, often, well executed have fallen short of incentivizing a trend toward decentralization of mining power.\n\nMining “contracts” and “bonds” were the first instruments used to allow investment in mining projects. Companies offering such investment opportunities set up warehouses of GPU and FPGA miners, and offered contracts at a flat rate based on hashrate offered and contract duration. Often, companies offering mining contracts would allow the investor to specify a pool toward which the mining power would be directed. Unfortunately, the hashrate avalanche that resulted from the flood of investment during this period caused many ingenuous offerings to lose production capability quickly because of Bitcoin’s rapidly increasing difficulty during this period.\n\tAs the first ASIC machines came online, the community was excited to see the advent of “cloud mining” services which make investment in cryptocurrency mining trivial for anyone who has interacted with a modern trading interface. Many entries in this space failed to perform as expected, again, due to the difficulty increases from rapid innovation occurring at this point. Still other companies claiming to offer cloud mining services disappeared seemingly overnight, taking investor funds with them. Further, most cloud mining operations don’t allow the investor to specify a mining pool in which they would like their hashrate to participate. This incentivizes a trend toward centralization, with specific cases in mind of cloud providers approaching 51% of network mining power.\nAlong with contracts and cloud mining, some companies offer miner hosting. With miner hosting, an investor retains ownership of the hardware and control over pool participation. The investor pays maintenance fees to the hosting provider, who is responsible for securing, powering, and maintaining the hardware. Investors can usually take delivery of their mining hardware at any time, and may then sell the miner, operate it locally, or find another hosting company for the miner. This approach, though properly incentivized, drastically reduces the liquidity of the miner as a resource, as the owner must take ownership of the hardware if he wishes to switch hosting companies or market the hardware to another investor.\nThe approach described in this document uses smart contracts on the Rootstock (RSK) network to commoditize ownership of mining hardware and facilitate issue of derivative instruments, based upon the hashing power of the hardware in question, as tokens.\nI want this document to be read as a recommendation, or an “Invitation to discussion” if you will. Many details of implementation will require some modicum of community consensus before an approach like this can succeed.\n# Vocabulary\nMining Hardware - Any device or group of devices that emit shares which can be directed toward a mining pool.\n\nMiner Hosting Provider - An individual or organization which take custody of mining hardware and operate it on behalf of an investor, collecting maintenance fees in return.\n\nProvider Contract - A contract which performs blockchain-data management functions on behalf of a specific hosting provider. Such a contract should be considered implementation of a protocol to facilitate interoperability with other provider contracts. Implementation should begin only after adequate community discussion.\n\nHardware Contract - A contract issued by a provider when new mining hardware is brought online. The provider is responsible for configuring the contract to reflect ownership by an address specified by the initial investor. Again, care should be taken in implementing these contracts to maximize interoperability with related systems.\n\t\nInitial Investor - An individual or organization that puts down initial investment on mining hardware.\n\n# The Provider Contract\nThe provider, to bootstrap his endeavor, issues a contract that holds all metadata about the operation. Contact information, number of hardware spots available (perhaps the community can come to an agreement on standard sizing of hardware) and maintenance fee information can all be enumerated in the contract, with “owner-only” accessor methods to provide update capabilities. Contracts representing hardware housed by a given provider will contain a reference to this contract so that the intrinsic “reputation” of the provider can substantiate the condition scores and other metrics the provider is responsible for maintaining. (More on these later). The establishment of a contract as the basis for reference to a hosting provider allows ownership to be passed on to other organizations (distributed or otherwise) in the future.\n# Equipment Purchase/Assay Process\nInitial investors may either purchase equipment and have it shipped to a hosting facility, or may order hardware through the hosting provider. The provider must then assay the hardware, (much like the process for admitting large-ingot gold bars to the financial system) checking for physical as well as performance issues. During assay, the provider rates the overall condition of the hardware (new, good, poor, etc), and may test the miner’s hashrate (Though as a sign of goodwill to the investor, I recommend that any assay related mining be conducted on testnet, or that revenue be identified and perhaps loaded into the investor’s account to cover initial maintenance fees). The provider then issues a contract, sets the variable for “owner” in the contract to the address specified by their investor at time of purchase or onboarding.\n\n# Mining Pools and Protocol Enhancements\nMining pools stand to greatly benefit if a contract-focused securitization of mining power succeeds. That being said, these benefits will require some changes to the protocols that pools use to communicate to worker nodes, and APIs will need to be constructed to allow owner specification of mining pool preference. Another pool API should be architected to allow hardware owners to pay maintenance fees to their hosting provider out of pool revenue if they so choose. I also think that it might be worthwhile to investigate the idea of mining pools issuing a share-count statement whenever they discover a block. The statement would certify the percentages of work that each worker contributed to block discovery, referring to each worker by the address of its associated contract. Such certification could provide an indelible record of the performance of a piece of hardware, and enforce accountability for pool operators, hosting providers and investors alike.\n# Ownership Transfer\nAn investor may decide to sell his hardware at any time. The recent explosion of interest in DAOs have driven many centralized exchanges to support trading of tokens. Support for trading of contracts that represent mining hardware should be well within reach. Just as one must transfer tokens to an address corresponding to his account on an exchange, an investor looking to market his mining hardware need only call the ‘changeOwner’ function on the contract. Exchanges could use the metadata in the hardware contract to build a description of the equipment. Further, just as exchanges have accommodated users in execution of DAO functions through their tokens, a proxy for update/maintenance of miner information could be provided.\n# Tokenization of Equipment Ownership\nThe investor may decide to maintain some stake in the hardware when seeking to defer costs. This can be undertaken simply by creating a DAO contract and passing ownership of the hardware contract to the DAO. Details on how DAO members can then vote on changes to the miner’s pool status, request a provider transfer, or acommodate distribution of mining revenue to tokenholders are discussed at length in the DAO white paper (https://download.slock.it/public/DAO/WhitePaper.pdf) and are beyond the scope of this document.\n# Provider Transfer\nKeeping the market for miner hosting both open and flexible is crucial to the securitization of mining power. Protocols for issuing requests for hardware transfer from one hosting provider to another will need to be designed, but these tasks can be handled through the provider and hardware contract implementations. Requests can be initiated by the owner of a piece of hardware, perhaps via a function call to the new provider. The function call could carry fees to cover shipping along with initial maintenance fees and assay service Then, the “New Provider” would send a notification of transfer to the provider in custody of the hardware in question. This method call could reference the payment they received to vouch that the transaction came from the address listed as the owner of the hardware.\n\n# A note on Interoperability vs. Competition\nWhile it is crucial that the community develop contract interfaces which are interoperable, I see no problem at all with healthy competition between individual contract stacks. That is to say, though we may delineate standard function names and data fields, differences in the way these protocols are implemented will foster healthy growth for contract stacks across the board.\n\n\n````\n-----BEGIN SIGNATURE BLOCK TEXT-----\nDocument: Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock\nDate: July 9th, 2016\nAuthor: Gregory J. Mikeska \nSignatory Address:1KDPgyR4kvbazDMYNFzcyr8HrCaNPmSjLZ\n-----END SIGNATURE BLOCK TEXT-----\n\n-----BEGIN SIGNATURE BLOCK-----\nIPTVp5ZWZe3QAH8ZC26Ytte68T//8fYgEz6bLaWwD1VjJpDek31XaMF4CJQ+FEQ2wQfwXv1C3C0DDMs5Ds7kt3E=\n-----END SIGNATURE BLOCK-----````",
"json_metadata": "{\"tags\":[\"bitcoin\",\"bitcoin-mining\",\"cryptocurrency\",\"money\",\"decentralize\",\"d10e\",\"ethereum\",\"mining\"],\"users\":[\"gmikeska07\"],\"links\":[\"https://download.slock.it/public/DAO/WhitePaper.pdf\"]}"
}
]
}| voter | dmacshady |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3316377/Trx ca98c089471b54f67ad4170a1f5a1628618d736c |
View Raw JSON Data
{
"trx_id": "ca98c089471b54f67ad4170a1f5a1628618d736c",
"block": 3316377,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:06:51",
"op": [
"vote",
{
"voter": "dmacshady",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"weight": 10000
}
]
}| voter | asim |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3316287/Trx e12bcdf2985585a41fb2b36103accc32e80370a3 |
View Raw JSON Data
{
"trx_id": "e12bcdf2985585a41fb2b36103accc32e80370a3",
"block": 3316287,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-19T00:02:21",
"op": [
"vote",
{
"voter": "asim",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"weight": 10000
}
]
}| voter | bola |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3315544/Trx f2592f894bdf389835fc6c87050d943152b4c799 |
View Raw JSON Data
{
"trx_id": "f2592f894bdf389835fc6c87050d943152b4c799",
"block": 3315544,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T23:25:03",
"op": [
"vote",
{
"voter": "bola",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3315536/Trx a684d0b6a5cca6896f56148e91ba0291ad2a9021 |
View Raw JSON Data
{
"trx_id": "a684d0b6a5cca6896f56148e91ba0291ad2a9021",
"block": 3315536,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T23:24:39",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"weight": 10000
}
]
}gmikeska07published a new post: securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock
gmikeska07published a new post: securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock
| parent author | |
| parent permlink | bitcoin |
| author | gmikeska07 |
| permlink | securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock |
| title | Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock |
| body | # Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock A Brief White Paper by @gmikeska07 # Introduction Mining is a crucial function in the Bitcoin ecosystem. Concerns abound over potential centralization of mining power into the hands of mining cartels which may or may not be benevolent oligarchs. Attempts at innovation in the mining space, though well-intentioned and, often, well executed have fallen short of incentivizing a trend toward decentralization of mining power. Mining “contracts” and “bonds” were the first instruments used to allow investment in mining projects. Companies offering such investment opportunities set up warehouses of GPU and FPGA miners, and offered contracts at a flat rate based on hashrate offered and contract duration. Often, companies offering mining contracts would allow the investor to specify a pool toward which the mining power would be directed. Unfortunately, the hashrate avalanche that resulted from the flood of investment during this period caused many ingenuous offerings to lose production capability quickly because of Bitcoin’s rapidly increasing difficulty during this period. As the first ASIC machines came online, the community was excited to see the advent of “cloud mining” services which make investment in cryptocurrency mining trivial for anyone who has interacted with a modern trading interface. Many entries in this space failed to perform as expected, again, due to the difficulty increases from rapid innovation occurring at this point. Still other companies claiming to offer cloud mining services disappeared seemingly overnight, taking investor funds with them. Further, most cloud mining operations don’t allow the investor to specify a mining pool in which they would like their hashrate to participate. This incentivizes a trend toward centralization, with specific cases in mind of cloud providers approaching 51% of network mining power. Along with contracts and cloud mining, some companies offer miner hosting. With miner hosting, an investor retains ownership of the hardware and control over pool participation. The investor pays maintenance fees to the hosting provider, who is responsible for securing, powering, and maintaining the hardware. Investors can usually take delivery of their mining hardware at any time, and may then sell the miner, operate it locally, or find another hosting company for the miner. This approach, though properly incentivized, drastically reduces the liquidity of the miner as a resource, as the owner must take ownership of the hardware if he wishes to switch hosting companies or market the hardware to another investor. The approach described in this document uses smart contracts on the Rootstock (RSK) network to commoditize ownership of mining hardware and facilitate issue of derivative instruments, based upon the hashing power of the hardware in question, as tokens. I want this document to be read as a recommendation, or an “Invitation to discussion” if you will. Many details of implementation will require some modicum of community consensus before an approach like this can succeed. # Vocabulary Mining Hardware - Any device or group of devices that emit shares which can be directed toward a mining pool. Miner Hosting Provider - An individual or organization which take custody of mining hardware and operate it on behalf of an investor, collecting maintenance fees in return. Provider Contract - A contract which performs blockchain-data management functions on behalf of a specific hosting provider. Such a contract should be considered implementation of a protocol to facilitate interoperability with other provider contracts. Implementation should begin only after adequate community discussion. Hardware Contract - A contract issued by a provider when new mining hardware is brought online. The provider is responsible for configuring the contract to reflect ownership by an address specified by the initial investor. Again, care should be taken in implementing these contracts to maximize interoperability with related systems. Initial Investor - An individual or organization that puts down initial investment on mining hardware. # The Provider Contract The provider, to bootstrap his endeavor, issues a contract that holds all metadata about the operation. Contact information, number of hardware spots available (perhaps the community can come to an agreement on standard sizing of hardware) and maintenance fee information can all be enumerated in the contract, with “owner-only” accessor methods to provide update capabilities. Contracts representing hardware housed by a given provider will contain a reference to this contract so that the intrinsic “reputation” of the provider can substantiate the condition scores and other metrics the provider is responsible for maintaining. (More on these later). The establishment of a contract as the basis for reference to a hosting provider allows ownership to be passed on to other organizations (distributed or otherwise) in the future. # Equipment Purchase/Assay Process Initial investors may either purchase equipment and have it shipped to a hosting facility, or may order hardware through the hosting provider. The provider must then assay the hardware, (much like the process for admitting large-ingot gold bars to the financial system) checking for physical as well as performance issues. During assay, the provider rates the overall condition of the hardware (new, good, poor, etc), and may test the miner’s hashrate (Though as a sign of goodwill to the investor, I recommend that any assay related mining be conducted on testnet, or that revenue be identified and perhaps loaded into the investor’s account to cover initial maintenance fees). The provider then issues a contract, sets the variable for “owner” in the contract to the address specified by their investor at time of purchase or onboarding. # Mining Pools and Protocol Enhancements Mining pools stand to greatly benefit if a contract-focused securitization of mining power succeeds. That being said, these benefits will require some changes to the protocols that pools use to communicate to worker nodes, and APIs will need to be constructed to allow owner specification of mining pool preference. Another pool API should be architected to allow hardware owners to pay maintenance fees to their hosting provider out of pool revenue if they so choose. I also think that it might be worthwhile to investigate the idea of mining pools issuing a share-count statement whenever they discover a block. The statement would certify the percentages of work that each worker contributed to block discovery, referring to each worker by the address of its associated contract. Such certification could provide an indelible record of the performance of a piece of hardware, and enforce accountability for pool operators, hosting providers and investors alike. # Ownership Transfer An investor may decide to sell his hardware at any time. The recent explosion of interest in DAOs have driven many centralized exchanges to support trading of tokens. Support for trading of contracts that represent mining hardware should be well within reach. Just as one must transfer tokens to an address corresponding to his account on an exchange, an investor looking to market his mining hardware need only call the ‘changeOwner’ function on the contract. Exchanges could use the metadata in the hardware contract to build a description of the equipment. Further, just as exchanges have accommodated users in execution of DAO functions through their tokens, a proxy for update/maintenance of miner information could be provided. # Tokenization of Equipment Ownership The investor may decide to maintain some stake in the hardware when seeking to defer costs. This can be undertaken simply by creating a DAO contract and passing ownership of the hardware contract to the DAO. Details on how DAO members can then vote on changes to the miner’s pool status, request a provider transfer, or acommodate distribution of mining revenue to tokenholders are discussed at length in the DAO white paper (https://download.slock.it/public/DAO/WhitePaper.pdf) and are beyond the scope of this document. # Provider Transfer Keeping the market for miner hosting both open and flexible is crucial to the securitization of mining power. Protocols for issuing requests for hardware transfer from one hosting provider to another will need to be designed, but these tasks can be handled through the provider and hardware contract implementations. Requests can be initiated by the owner of a piece of hardware, perhaps via a function call to the new provider. The function call could carry fees to cover shipping along with initial maintenance fees and assay service Then, the “New Provider” would send a notification of transfer to the provider in custody of the hardware in question. This method call could reference the payment they received to vouch that the transaction came from the address listed as the owner of the hardware. # A note on Interoperability vs. Competition While it is crucial that the community develop contract interfaces which are interoperable, I see no problem at all with healthy competition between individual contract stacks. That is to say, though we may delineate standard function names and data fields, differences in the way these protocols are implemented will foster healthy growth for contract stacks across the board. ```` -----BEGIN SIGNATURE BLOCK TEXT----- Document: Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock Date: July 9th, 2016 Author: Gregory J. Mikeska Signatory Address:1KDPgyR4kvbazDMYNFzcyr8HrCaNPmSjLZ -----END SIGNATURE BLOCK TEXT----- -----BEGIN SIGNATURE BLOCK----- IPTVp5ZWZe3QAH8ZC26Ytte68T//8fYgEz6bLaWwD1VjJpDek31XaMF4CJQ+FEQ2wQfwXv1C3C0DDMs5Ds7kt3E= -----END SIGNATURE BLOCK-----```` |
| json metadata | {"tags":["bitcoin","bitcoin-mining","cryptocurrency","money","decentralize","d10e","ethereum","mining"],"users":["gmikeska07"],"links":["https://download.slock.it/public/DAO/WhitePaper.pdf"]} |
| Transaction Info | Block #3315536/Trx a684d0b6a5cca6896f56148e91ba0291ad2a9021 |
View Raw JSON Data
{
"trx_id": "a684d0b6a5cca6896f56148e91ba0291ad2a9021",
"block": 3315536,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T23:24:39",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "gmikeska07",
"permlink": "securitizing-cryptocurrency-miner-ownership-with-smart-contracts-on-rootstock",
"title": "Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock",
"body": "# Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock\nA Brief White Paper by @gmikeska07\n# Introduction\nMining is a crucial function in the Bitcoin ecosystem. Concerns abound over potential centralization of mining power into the hands of mining cartels which may or may not be benevolent oligarchs. Attempts at innovation in the mining space, though well-intentioned and, often, well executed have fallen short of incentivizing a trend toward decentralization of mining power.\n\nMining “contracts” and “bonds” were the first instruments used to allow investment in mining projects. Companies offering such investment opportunities set up warehouses of GPU and FPGA miners, and offered contracts at a flat rate based on hashrate offered and contract duration. Often, companies offering mining contracts would allow the investor to specify a pool toward which the mining power would be directed. Unfortunately, the hashrate avalanche that resulted from the flood of investment during this period caused many ingenuous offerings to lose production capability quickly because of Bitcoin’s rapidly increasing difficulty during this period.\n\tAs the first ASIC machines came online, the community was excited to see the advent of “cloud mining” services which make investment in cryptocurrency mining trivial for anyone who has interacted with a modern trading interface. Many entries in this space failed to perform as expected, again, due to the difficulty increases from rapid innovation occurring at this point. Still other companies claiming to offer cloud mining services disappeared seemingly overnight, taking investor funds with them. Further, most cloud mining operations don’t allow the investor to specify a mining pool in which they would like their hashrate to participate. This incentivizes a trend toward centralization, with specific cases in mind of cloud providers approaching 51% of network mining power.\nAlong with contracts and cloud mining, some companies offer miner hosting. With miner hosting, an investor retains ownership of the hardware and control over pool participation. The investor pays maintenance fees to the hosting provider, who is responsible for securing, powering, and maintaining the hardware. Investors can usually take delivery of their mining hardware at any time, and may then sell the miner, operate it locally, or find another hosting company for the miner. This approach, though properly incentivized, drastically reduces the liquidity of the miner as a resource, as the owner must take ownership of the hardware if he wishes to switch hosting companies or market the hardware to another investor.\nThe approach described in this document uses smart contracts on the Rootstock (RSK) network to commoditize ownership of mining hardware and facilitate issue of derivative instruments, based upon the hashing power of the hardware in question, as tokens.\nI want this document to be read as a recommendation, or an “Invitation to discussion” if you will. Many details of implementation will require some modicum of community consensus before an approach like this can succeed.\n# Vocabulary\nMining Hardware - Any device or group of devices that emit shares which can be directed toward a mining pool.\n\nMiner Hosting Provider - An individual or organization which take custody of mining hardware and operate it on behalf of an investor, collecting maintenance fees in return.\n\nProvider Contract - A contract which performs blockchain-data management functions on behalf of a specific hosting provider. Such a contract should be considered implementation of a protocol to facilitate interoperability with other provider contracts. Implementation should begin only after adequate community discussion.\n\nHardware Contract - A contract issued by a provider when new mining hardware is brought online. The provider is responsible for configuring the contract to reflect ownership by an address specified by the initial investor. Again, care should be taken in implementing these contracts to maximize interoperability with related systems.\n\t\nInitial Investor - An individual or organization that puts down initial investment on mining hardware.\n\n# The Provider Contract\nThe provider, to bootstrap his endeavor, issues a contract that holds all metadata about the operation. Contact information, number of hardware spots available (perhaps the community can come to an agreement on standard sizing of hardware) and maintenance fee information can all be enumerated in the contract, with “owner-only” accessor methods to provide update capabilities. Contracts representing hardware housed by a given provider will contain a reference to this contract so that the intrinsic “reputation” of the provider can substantiate the condition scores and other metrics the provider is responsible for maintaining. (More on these later). The establishment of a contract as the basis for reference to a hosting provider allows ownership to be passed on to other organizations (distributed or otherwise) in the future.\n# Equipment Purchase/Assay Process\nInitial investors may either purchase equipment and have it shipped to a hosting facility, or may order hardware through the hosting provider. The provider must then assay the hardware, (much like the process for admitting large-ingot gold bars to the financial system) checking for physical as well as performance issues. During assay, the provider rates the overall condition of the hardware (new, good, poor, etc), and may test the miner’s hashrate (Though as a sign of goodwill to the investor, I recommend that any assay related mining be conducted on testnet, or that revenue be identified and perhaps loaded into the investor’s account to cover initial maintenance fees). The provider then issues a contract, sets the variable for “owner” in the contract to the address specified by their investor at time of purchase or onboarding.\n\n# Mining Pools and Protocol Enhancements\nMining pools stand to greatly benefit if a contract-focused securitization of mining power succeeds. That being said, these benefits will require some changes to the protocols that pools use to communicate to worker nodes, and APIs will need to be constructed to allow owner specification of mining pool preference. Another pool API should be architected to allow hardware owners to pay maintenance fees to their hosting provider out of pool revenue if they so choose. I also think that it might be worthwhile to investigate the idea of mining pools issuing a share-count statement whenever they discover a block. The statement would certify the percentages of work that each worker contributed to block discovery, referring to each worker by the address of its associated contract. Such certification could provide an indelible record of the performance of a piece of hardware, and enforce accountability for pool operators, hosting providers and investors alike.\n# Ownership Transfer\nAn investor may decide to sell his hardware at any time. The recent explosion of interest in DAOs have driven many centralized exchanges to support trading of tokens. Support for trading of contracts that represent mining hardware should be well within reach. Just as one must transfer tokens to an address corresponding to his account on an exchange, an investor looking to market his mining hardware need only call the ‘changeOwner’ function on the contract. Exchanges could use the metadata in the hardware contract to build a description of the equipment. Further, just as exchanges have accommodated users in execution of DAO functions through their tokens, a proxy for update/maintenance of miner information could be provided.\n# Tokenization of Equipment Ownership\nThe investor may decide to maintain some stake in the hardware when seeking to defer costs. This can be undertaken simply by creating a DAO contract and passing ownership of the hardware contract to the DAO. Details on how DAO members can then vote on changes to the miner’s pool status, request a provider transfer, or acommodate distribution of mining revenue to tokenholders are discussed at length in the DAO white paper (https://download.slock.it/public/DAO/WhitePaper.pdf) and are beyond the scope of this document.\n# Provider Transfer\nKeeping the market for miner hosting both open and flexible is crucial to the securitization of mining power. Protocols for issuing requests for hardware transfer from one hosting provider to another will need to be designed, but these tasks can be handled through the provider and hardware contract implementations. Requests can be initiated by the owner of a piece of hardware, perhaps via a function call to the new provider. The function call could carry fees to cover shipping along with initial maintenance fees and assay service Then, the “New Provider” would send a notification of transfer to the provider in custody of the hardware in question. This method call could reference the payment they received to vouch that the transaction came from the address listed as the owner of the hardware.\n\n# A note on Interoperability vs. Competition\nWhile it is crucial that the community develop contract interfaces which are interoperable, I see no problem at all with healthy competition between individual contract stacks. That is to say, though we may delineate standard function names and data fields, differences in the way these protocols are implemented will foster healthy growth for contract stacks across the board.\n\n\n````\n-----BEGIN SIGNATURE BLOCK TEXT-----\nDocument: Securitizing Cryptocurrency Miner Ownership with Smart Contracts on Rootstock\nDate: July 9th, 2016\nAuthor: Gregory J. Mikeska \nSignatory Address:1KDPgyR4kvbazDMYNFzcyr8HrCaNPmSjLZ\n-----END SIGNATURE BLOCK TEXT-----\n\n-----BEGIN SIGNATURE BLOCK-----\nIPTVp5ZWZe3QAH8ZC26Ytte68T//8fYgEz6bLaWwD1VjJpDek31XaMF4CJQ+FEQ2wQfwXv1C3C0DDMs5Ds7kt3E=\n-----END SIGNATURE BLOCK-----````",
"json_metadata": "{\"tags\":[\"bitcoin\",\"bitcoin-mining\",\"cryptocurrency\",\"money\",\"decentralize\",\"d10e\",\"ethereum\",\"mining\"],\"users\":[\"gmikeska07\"],\"links\":[\"https://download.slock.it/public/DAO/WhitePaper.pdf\"]}"
}
]
}| voter | gmikeska07 |
| author | eeks |
| permlink | my-steemit-analysis-post-put-me-in-the-news-and-also-put-usd1-300-in-my-pocket |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3315407/Trx 6ea1863b16b8f99bfdd08ef2baaba916744a9c8b |
View Raw JSON Data
{
"trx_id": "6ea1863b16b8f99bfdd08ef2baaba916744a9c8b",
"block": 3315407,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T23:18:12",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "eeks",
"permlink": "my-steemit-analysis-post-put-me-in-the-news-and-also-put-usd1-300-in-my-pocket",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | positive |
| permlink | why-you-shouldn-t-criticize-liquidity-monopolists-or-why-liquidity-greater-than-spread-they-give-your-steem-value |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3315406/Trx 032c86d501097d9b4b8990a82d61e17a228b62c6 |
View Raw JSON Data
{
"trx_id": "032c86d501097d9b4b8990a82d61e17a228b62c6",
"block": 3315406,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T23:18:09",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "positive",
"permlink": "why-you-shouldn-t-criticize-liquidity-monopolists-or-why-liquidity-greater-than-spread-they-give-your-steem-value",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | neil-haran |
| permlink | are-we-heading-towards-a-dag-decentralized-autonomous-government |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3315379/Trx a9dd21cf7c09c60cf8c5e1d92fc0678538b37742 |
View Raw JSON Data
{
"trx_id": "a9dd21cf7c09c60cf8c5e1d92fc0678538b37742",
"block": 3315379,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T23:16:48",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "neil-haran",
"permlink": "are-we-heading-towards-a-dag-decentralized-autonomous-government",
"weight": 10000
}
]
}gmikeska07upvoted (100.00%) @sigmajin / not-like-the-others-why-steem-price-hasn-t-come-close-to-peaking
gmikeska07upvoted (100.00%) @sigmajin / not-like-the-others-why-steem-price-hasn-t-come-close-to-peaking
| voter | gmikeska07 |
| author | sigmajin |
| permlink | not-like-the-others-why-steem-price-hasn-t-come-close-to-peaking |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3315370/Trx 448968cf6c1f72c88f72eff2802edb007b7d20e4 |
View Raw JSON Data
{
"trx_id": "448968cf6c1f72c88f72eff2802edb007b7d20e4",
"block": 3315370,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T23:16:21",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "sigmajin",
"permlink": "not-like-the-others-why-steem-price-hasn-t-come-close-to-peaking",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | royaltiffany |
| permlink | hello-steemit-i-am-tiffany-bitcoin-enthusiast-cam-girl-and-recently-steemit-fan |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3315368/Trx 6a775a8b2f9dd75fa274eccec686acb4d820f373 |
View Raw JSON Data
{
"trx_id": "6a775a8b2f9dd75fa274eccec686acb4d820f373",
"block": 3315368,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T23:16:15",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "royaltiffany",
"permlink": "hello-steemit-i-am-tiffany-bitcoin-enthusiast-cam-girl-and-recently-steemit-fan",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | drinkzya |
| permlink | why-i-am-giving-away-all-the-majority-of-my-blogging-rewards-to-new-steemers-in-order-to-increase-my-overall-long-term-holdings |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3312749/Trx f693df75dd7a9caad4c7701426ef5457d54406b4 |
View Raw JSON Data
{
"trx_id": "f693df75dd7a9caad4c7701426ef5457d54406b4",
"block": 3312749,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T21:04:27",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "drinkzya",
"permlink": "why-i-am-giving-away-all-the-majority-of-my-blogging-rewards-to-new-steemers-in-order-to-increase-my-overall-long-term-holdings",
"weight": 10000
}
]
}| parent author | |
| parent permlink | steem |
| author | gmikeska07 |
| permlink | the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report |
| title | The macroeconomics of central bank issued digital currencies - Bank of England Report |
| body | @@ -1,8 +1,111 @@ +https://upload.wikimedia.org/wikipedia/en/thumb/0/0c/Bank_of_England.svg/220px-Bank_of_England.svg.png%0A From our |
| json metadata | {"tags":["steem","bitcoin","ethereum","cryptocurrency","banking","blockchain","coindesk","money"],"image":["https://upload.wikimedia.org/wikipedia/en/thumb/0/0c/Bank_of_England.svg/220px-Bank_of_England.svg.png"]} |
| Transaction Info | Block #3312701/Trx c58b2af8d3afa2d56dbebb8cd215f54a9a07adfe |
View Raw JSON Data
{
"trx_id": "c58b2af8d3afa2d56dbebb8cd215f54a9a07adfe",
"block": 3312701,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T21:02:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "steem",
"author": "gmikeska07",
"permlink": "the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report",
"title": "The macroeconomics of central bank issued digital currencies - Bank of England Report",
"body": "@@ -1,8 +1,111 @@\n+https://upload.wikimedia.org/wikipedia/en/thumb/0/0c/Bank_of_England.svg/220px-Bank_of_England.svg.png%0A\n From our\n",
"json_metadata": "{\"tags\":[\"steem\",\"bitcoin\",\"ethereum\",\"cryptocurrency\",\"banking\",\"blockchain\",\"coindesk\",\"money\"],\"image\":[\"https://upload.wikimedia.org/wikipedia/en/thumb/0/0c/Bank_of_England.svg/220px-Bank_of_England.svg.png\"]}"
}
]
}| voter | mrzazaful |
| author | gmikeska07 |
| permlink | the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3312688/Trx 8b49ec78cb3fb1e1dbb790d00418a2c5c5b0b944 |
View Raw JSON Data
{
"trx_id": "8b49ec78cb3fb1e1dbb790d00418a2c5c5b0b944",
"block": 3312688,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T21:01:18",
"op": [
"vote",
{
"voter": "mrzazaful",
"author": "gmikeska07",
"permlink": "the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report",
"weight": 10000
}
]
}| parent author | |
| parent permlink | steem |
| author | gmikeska07 |
| permlink | the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report |
| title | The macroeconomics of central bank issued digital currencies - Bank of England Report |
| body | From our friends at [Coindesk](http://www.coindesk.com/central-bank-digital-currencies-boost-gdp-bank-england-says/) >The Bank of England has released new research suggesting that a central bank-issued digital currency could lead to an increase in gross domestic product. The conclusions were drawn from a working paper published today that examined how a central bank-backed digital currency (referred to as a CBDC in the paper) could yield macroeconomic benefits, while providing banking regulators a clearer picture of the financial system. The full report is linked in the article, and is also available via [Scribd](http://go.redirectingat.com/?id=78380X1529106&site=coindesk.com&xs=1&isjs=1&url=https%3A%2F%2Fwww.scribd.com%2Fdocument%2F318596286%2FBoE-Paper%23from_embed&xguid=a80cd94ae9ffe52d4cac8856f6dc9033&xuuid=ea1c2a7b49847e7e0d95651a4750676a&xsessid=b8fbf9c3be2dafdc13c237d275e4eecf&xcreo=0&xed=0&sref=http%3A%2F%2Fwww.coindesk.com%2Fcentral-bank-digital-currencies-boost-gdp-bank-england-says%2F%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A%2BCoinDesk%2B%2528CoinDesk%2B-%2BThe%2BVoice%2Bof%2BDigital%2BCurrency%2529&pref=https%3A%2F%2Ft.co%2FMGOla1xv5p&xtz=300&abp=1) |
| json metadata | {"tags":["steem","bitcoin","ethereum","cryptocurrency","banking","blockchain","coindesk","money"],"links":["http://www.coindesk.com/central-bank-digital-currencies-boost-gdp-bank-england-says/"]} |
| Transaction Info | Block #3312685/Trx 41f23b601426851afb9f9a3ee5b77fbdf167c34f |
View Raw JSON Data
{
"trx_id": "41f23b601426851afb9f9a3ee5b77fbdf167c34f",
"block": 3312685,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T21:01:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "steem",
"author": "gmikeska07",
"permlink": "the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report",
"title": "The macroeconomics of central bank issued digital currencies - Bank of England Report",
"body": "From our friends at [Coindesk](http://www.coindesk.com/central-bank-digital-currencies-boost-gdp-bank-england-says/)\n>The Bank of England has released new research suggesting that a central bank-issued digital currency could lead to an increase in gross domestic product. The conclusions were drawn from a working paper published today that examined how a central bank-backed digital currency (referred to as a CBDC in the paper) could yield macroeconomic benefits, while providing banking regulators a clearer picture of the financial system.\n\nThe full report is linked in the article, and is also available via [Scribd](http://go.redirectingat.com/?id=78380X1529106&site=coindesk.com&xs=1&isjs=1&url=https%3A%2F%2Fwww.scribd.com%2Fdocument%2F318596286%2FBoE-Paper%23from_embed&xguid=a80cd94ae9ffe52d4cac8856f6dc9033&xuuid=ea1c2a7b49847e7e0d95651a4750676a&xsessid=b8fbf9c3be2dafdc13c237d275e4eecf&xcreo=0&xed=0&sref=http%3A%2F%2Fwww.coindesk.com%2Fcentral-bank-digital-currencies-boost-gdp-bank-england-says%2F%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A%2BCoinDesk%2B%2528CoinDesk%2B-%2BThe%2BVoice%2Bof%2BDigital%2BCurrency%2529&pref=https%3A%2F%2Ft.co%2FMGOla1xv5p&xtz=300&abp=1)",
"json_metadata": "{\"tags\":[\"steem\",\"bitcoin\",\"ethereum\",\"cryptocurrency\",\"banking\",\"blockchain\",\"coindesk\",\"money\"],\"links\":[\"http://www.coindesk.com/central-bank-digital-currencies-boost-gdp-bank-england-says/\"]}"
}
]
}gmikeska07upvoted (100.00%) @sigmajin / omg-inflation-the-sky-is-about-to-fall
gmikeska07upvoted (100.00%) @sigmajin / omg-inflation-the-sky-is-about-to-fall
| voter | gmikeska07 |
| author | sigmajin |
| permlink | omg-inflation-the-sky-is-about-to-fall |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3312668/Trx b9ae50ad3ceeb5fb46e15b0506f16d2badecb9ea |
View Raw JSON Data
{
"trx_id": "b9ae50ad3ceeb5fb46e15b0506f16d2badecb9ea",
"block": 3312668,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T21:00:12",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "sigmajin",
"permlink": "omg-inflation-the-sky-is-about-to-fall",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | cryptoiskey |
| permlink | re-sigmajin-omg-inflation-the-sky-is-about-to-fall-20160718t083449556z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3312667/Trx 7a99c720c9c116bdbd607837319706a636ad5374 |
View Raw JSON Data
{
"trx_id": "7a99c720c9c116bdbd607837319706a636ad5374",
"block": 3312667,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T21:00:09",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "cryptoiskey",
"permlink": "re-sigmajin-omg-inflation-the-sky-is-about-to-fall-20160718t083449556z",
"weight": 10000
}
]
}| voter | bola |
| author | gmikeska07 |
| permlink | the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3312664/Trx 8f7f7b4e383cefd526e30cbac1d8cbd1ca3a8875 |
View Raw JSON Data
{
"trx_id": "8f7f7b4e383cefd526e30cbac1d8cbd1ca3a8875",
"block": 3312664,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T21:00:00",
"op": [
"vote",
{
"voter": "bola",
"author": "gmikeska07",
"permlink": "the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | gmikeska07 |
| permlink | the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3312605/Trx c07fbef362eda0d41297c8961e1c32d424703b93 |
View Raw JSON Data
{
"trx_id": "c07fbef362eda0d41297c8961e1c32d424703b93",
"block": 3312605,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T20:57:00",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "gmikeska07",
"permlink": "the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report",
"weight": 10000
}
]
}| parent author | |
| parent permlink | steem |
| author | gmikeska07 |
| permlink | the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report |
| title | The macroeconomics of central bank issued digital currencies - Bank of England Report |
| body | From our friends at [Coindesk](http://www.coindesk.com/central-bank-digital-currencies-boost-gdp-bank-england-says/) >The Bank of England has released new research suggesting that a central bank-issued digital currency could lead to an increase in gross domestic product. The conclusions were drawn from a working paper published today that examined how a central bank-backed digital currency (referred to as a CBDC in the paper) could yield macroeconomic benefits, while providing banking regulators a clearer picture of the financial system. The full report is linked in the article, and is also available via [Scribd](http://go.redirectingat.com/?id=78380X1529106&site=coindesk.com&xs=1&isjs=1&url=https%3A%2F%2Fwww.scribd.com%2Fdocument%2F318596286%2FBoE-Paper%23from_embed&xguid=a80cd94ae9ffe52d4cac8856f6dc9033&xuuid=ea1c2a7b49847e7e0d95651a4750676a&xsessid=b8fbf9c3be2dafdc13c237d275e4eecf&xcreo=0&xed=0&sref=http%3A%2F%2Fwww.coindesk.com%2Fcentral-bank-digital-currencies-boost-gdp-bank-england-says%2F%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A%2BCoinDesk%2B%2528CoinDesk%2B-%2BThe%2BVoice%2Bof%2BDigital%2BCurrency%2529&pref=https%3A%2F%2Ft.co%2FMGOla1xv5p&xtz=300&abp=1) |
| json metadata | {"tags":["steem","bitcoin","ethereum","cryptocurrency","banking","blockchain","coindesk"],"links":["http://www.coindesk.com/central-bank-digital-currencies-boost-gdp-bank-england-says/"]} |
| Transaction Info | Block #3312605/Trx c07fbef362eda0d41297c8961e1c32d424703b93 |
View Raw JSON Data
{
"trx_id": "c07fbef362eda0d41297c8961e1c32d424703b93",
"block": 3312605,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T20:57:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "steem",
"author": "gmikeska07",
"permlink": "the-macroeconomics-of-central-bank-issued-digital-currencies-bank-of-england-report",
"title": "The macroeconomics of central bank issued digital currencies - Bank of England Report",
"body": "From our friends at [Coindesk](http://www.coindesk.com/central-bank-digital-currencies-boost-gdp-bank-england-says/)\n>The Bank of England has released new research suggesting that a central bank-issued digital currency could lead to an increase in gross domestic product. The conclusions were drawn from a working paper published today that examined how a central bank-backed digital currency (referred to as a CBDC in the paper) could yield macroeconomic benefits, while providing banking regulators a clearer picture of the financial system.\n\nThe full report is linked in the article, and is also available via [Scribd](http://go.redirectingat.com/?id=78380X1529106&site=coindesk.com&xs=1&isjs=1&url=https%3A%2F%2Fwww.scribd.com%2Fdocument%2F318596286%2FBoE-Paper%23from_embed&xguid=a80cd94ae9ffe52d4cac8856f6dc9033&xuuid=ea1c2a7b49847e7e0d95651a4750676a&xsessid=b8fbf9c3be2dafdc13c237d275e4eecf&xcreo=0&xed=0&sref=http%3A%2F%2Fwww.coindesk.com%2Fcentral-bank-digital-currencies-boost-gdp-bank-england-says%2F%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A%2BCoinDesk%2B%2528CoinDesk%2B-%2BThe%2BVoice%2Bof%2BDigital%2BCurrency%2529&pref=https%3A%2F%2Ft.co%2FMGOla1xv5p&xtz=300&abp=1)",
"json_metadata": "{\"tags\":[\"steem\",\"bitcoin\",\"ethereum\",\"cryptocurrency\",\"banking\",\"blockchain\",\"coindesk\"],\"links\":[\"http://www.coindesk.com/central-bank-digital-currencies-boost-gdp-bank-england-says/\"]}"
}
]
}gmikeska07upvoted (100.00%) @jasonmcz / the-good-the-bad-and-the-ugly-a-day-as-an-steemit-market-maker
gmikeska07upvoted (100.00%) @jasonmcz / the-good-the-bad-and-the-ugly-a-day-as-an-steemit-market-maker
| voter | gmikeska07 |
| author | jasonmcz |
| permlink | the-good-the-bad-and-the-ugly-a-day-as-an-steemit-market-maker |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3311073/Trx 4f47ab398dc715ceb29a0a0e01e763a7571fb573 |
View Raw JSON Data
{
"trx_id": "4f47ab398dc715ceb29a0a0e01e763a7571fb573",
"block": 3311073,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T19:39:54",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "jasonmcz",
"permlink": "the-good-the-bad-and-the-ugly-a-day-as-an-steemit-market-maker",
"weight": 10000
}
]
}gmikeska07started an SBD to STEEM conversion: 6.218 SBD
gmikeska07started an SBD to STEEM conversion: 6.218 SBD
| owner | gmikeska07 |
| requestid | 1468870733 |
| amount | 6.218 SBD |
| Transaction Info | Block #3311055/Trx a8581f840c7c8e0e3c760daaec7bd38630d3fb5b |
View Raw JSON Data
{
"trx_id": "a8581f840c7c8e0e3c760daaec7bd38630d3fb5b",
"block": 3311055,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T19:39:00",
"op": [
"convert",
{
"owner": "gmikeska07",
"requestid": 1468870733,
"amount": "6.218 SBD"
}
]
}gmikeska07received 6.174 SBD, 5.134 SP author reward for @gmikeska07 / bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin
gmikeska07received 6.174 SBD, 5.134 SP author reward for @gmikeska07 / bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| sbd payout | 6.174 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 8348.576130 VESTS |
| Transaction Info | Block #3310616/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 3310616,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2016-07-18T19:16:36",
"op": [
"author_reward",
{
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"sbd_payout": "6.174 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "8348.576130 VESTS"
}
]
}gmikeska07upvoted (100.00%) @pharesim / publishing-scientific-papers-on-steem
gmikeska07upvoted (100.00%) @pharesim / publishing-scientific-papers-on-steem
| voter | gmikeska07 |
| author | pharesim |
| permlink | publishing-scientific-papers-on-steem |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3309977/Trx 283c5e45b957fc5d7d9423da80bdbb8986ff1b05 |
View Raw JSON Data
{
"trx_id": "283c5e45b957fc5d7d9423da80bdbb8986ff1b05",
"block": 3309977,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T18:44:21",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "pharesim",
"permlink": "publishing-scientific-papers-on-steem",
"weight": 10000
}
]
}gmikeska07upvoted (100.00%) @heiditravels / let-s-get-uncomfortable
gmikeska07upvoted (100.00%) @heiditravels / let-s-get-uncomfortable
| voter | gmikeska07 |
| author | heiditravels |
| permlink | let-s-get-uncomfortable |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3309944/Trx b955e9e7426f71b3108dc1732a4522a232266ffb |
View Raw JSON Data
{
"trx_id": "b955e9e7426f71b3108dc1732a4522a232266ffb",
"block": 3309944,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T18:42:39",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "heiditravels",
"permlink": "let-s-get-uncomfortable",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | cryptoctopus |
| permlink | steemit-facebook-page-insights-from-the-guy-who-is-managing-it-7-17-2016 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3309941/Trx 4c46d40c71a9a4c5e6862b56a05f300b7262823c |
View Raw JSON Data
{
"trx_id": "4c46d40c71a9a4c5e6862b56a05f300b7262823c",
"block": 3309941,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T18:42:30",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "cryptoctopus",
"permlink": "steemit-facebook-page-insights-from-the-guy-who-is-managing-it-7-17-2016",
"weight": 10000
}
]
}gmikeska07upvoted (100.00%) @discombobulated / presenting-steemitx-com-a-simple-way-to-follow-users
gmikeska07upvoted (100.00%) @discombobulated / presenting-steemitx-com-a-simple-way-to-follow-users
| voter | gmikeska07 |
| author | discombobulated |
| permlink | presenting-steemitx-com-a-simple-way-to-follow-users |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3309940/Trx c42f3b4e4285fd85d9beda725fc69252b4ae12e0 |
View Raw JSON Data
{
"trx_id": "c42f3b4e4285fd85d9beda725fc69252b4ae12e0",
"block": 3309940,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T18:42:27",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "discombobulated",
"permlink": "presenting-steemitx-com-a-simple-way-to-follow-users",
"weight": 10000
}
]
}| voter | gmikeska07 |
| author | spaced |
| permlink | why-did-a-post-telling-people-to-report-bugs-make-3-000-usd-in-upvotes-and-my-actual-post-about-a-legitimate-security-issue-that |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3309938/Trx 619a1f267a0fdd1b9f6cada1c892ca71326662e4 |
View Raw JSON Data
{
"trx_id": "619a1f267a0fdd1b9f6cada1c892ca71326662e4",
"block": 3309938,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T18:42:21",
"op": [
"vote",
{
"voter": "gmikeska07",
"author": "spaced",
"permlink": "why-did-a-post-telling-people-to-report-bugs-make-3-000-usd-in-upvotes-and-my-actual-post-about-a-legitimate-security-issue-that",
"weight": 10000
}
]
}| voter | wynandvanrhyn |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3299610/Trx 7316eb535bfd6664d507d084ccb09abe58fd82f1 |
View Raw JSON Data
{
"trx_id": "7316eb535bfd6664d507d084ccb09abe58fd82f1",
"block": 3299610,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T10:02:12",
"op": [
"vote",
{
"voter": "wynandvanrhyn",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}| voter | johnsmith |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3295995/Trx ac00678837ba223bb62347cf3bba1b5a5d91cfaa |
View Raw JSON Data
{
"trx_id": "ac00678837ba223bb62347cf3bba1b5a5d91cfaa",
"block": 3295995,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T07:00:33",
"op": [
"vote",
{
"voter": "johnsmith",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}gmikeska07received 0.029 SBD, 0.028 SP author reward for @gmikeska07 / when-telling-friends-about-bitcoin
gmikeska07received 0.029 SBD, 0.028 SP author reward for @gmikeska07 / when-telling-friends-about-bitcoin
| author | gmikeska07 |
| permlink | when-telling-friends-about-bitcoin |
| sbd payout | 0.029 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 44.731676 VESTS |
| Transaction Info | Block #3291666/Virtual Operation #2 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 3291666,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 2,
"timestamp": "2016-07-18T03:22:54",
"op": [
"author_reward",
{
"author": "gmikeska07",
"permlink": "when-telling-friends-about-bitcoin",
"sbd_payout": "0.029 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "44.731676 VESTS"
}
]
}| voter | asim |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3288269/Trx 7f5b8fba92760f176bad31bec31a109e4380eea0 |
View Raw JSON Data
{
"trx_id": "7f5b8fba92760f176bad31bec31a109e4380eea0",
"block": 3288269,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T00:32:06",
"op": [
"vote",
{
"voter": "asim",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}howelltan01upvoted (100.00%) @gmikeska07 / when-telling-friends-about-bitcoin
howelltan01upvoted (100.00%) @gmikeska07 / when-telling-friends-about-bitcoin
| voter | howelltan01 |
| author | gmikeska07 |
| permlink | when-telling-friends-about-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3287916/Trx 3493cb6c56a5a1510e3bf20e1c220609a3a949fd |
View Raw JSON Data
{
"trx_id": "3493cb6c56a5a1510e3bf20e1c220609a3a949fd",
"block": 3287916,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-18T00:14:24",
"op": [
"vote",
{
"voter": "howelltan01",
"author": "gmikeska07",
"permlink": "when-telling-friends-about-bitcoin",
"weight": 10000
}
]
}| voter | stephencurry |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3286833/Trx 0878a4ad7726b7a573a5c4924271f448ff458f1d |
View Raw JSON Data
{
"trx_id": "0878a4ad7726b7a573a5c4924271f448ff458f1d",
"block": 3286833,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-17T23:20:03",
"op": [
"vote",
{
"voter": "stephencurry",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}| voter | mianeri |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3286036/Trx cae7f862b5c4ceb4a8688cedeb87fe983db5be6c |
View Raw JSON Data
{
"trx_id": "cae7f862b5c4ceb4a8688cedeb87fe983db5be6c",
"block": 3286036,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-17T22:40:09",
"op": [
"vote",
{
"voter": "mianeri",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}| voter | steampunkpowered |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3284943/Trx 93b556ce55677e0ae24bd417c24549beef755c61 |
View Raw JSON Data
{
"trx_id": "93b556ce55677e0ae24bd417c24549beef755c61",
"block": 3284943,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-17T21:45:18",
"op": [
"vote",
{
"voter": "steampunkpowered",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}| voter | sunnyray |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3284458/Trx 66fbd5ba642cdef46e10cb41fcca0a4b580e7b09 |
View Raw JSON Data
{
"trx_id": "66fbd5ba642cdef46e10cb41fcca0a4b580e7b09",
"block": 3284458,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-17T21:20:54",
"op": [
"vote",
{
"voter": "sunnyray",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}| voter | showmethecoinz |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3284160/Trx 249c558675b6882e5d666fb762e3e5885f6b1afd |
View Raw JSON Data
{
"trx_id": "249c558675b6882e5d666fb762e3e5885f6b1afd",
"block": 3284160,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-17T21:06:00",
"op": [
"vote",
{
"voter": "showmethecoinz",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}| voter | sean-king |
| author | gmikeska07 |
| permlink | bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3282270/Trx abf7061789c6c2f27e6adea9e4ba4580f0c8cdbd |
View Raw JSON Data
{
"trx_id": "abf7061789c6c2f27e6adea9e4ba4580f0c8cdbd",
"block": 3282270,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-07-17T19:31:06",
"op": [
"vote",
{
"voter": "sean-king",
"author": "gmikeska07",
"permlink": "bitcoin-as-the-ubiquitous-trust-anchor-the-system-is-iteself-to-bitcoin",
"weight": 10000
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress73.72%
{
"voting_manabar": {
"current_mana": 9938,
"last_update_time": 1469574558
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1468533213
},
"rc_account": {
"account": "gmikeska07",
"rc_manabar": {
"current_mana": "40637317665",
"last_update_time": 1537887600
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "40637317665"
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM7ekzkzmxfzLBhs18xdExG58TU8328TkYdzc11rpTNB8SGSCRXo1/1
Active
Single Signature
Public Keys
STM54Zfa2UnbvPU2za248PVxrk3s1gyCa3Kdnj4ogVQ3pv4upY6ga1/1
Posting
Single Signature
Public Keys
STM5rL6WMiUvnJXedsTqB4VmA8i95eYyYxmcMhqscYhaHArTniSzX1/1
Memo
STM6qzmXaDZJLoKjh9EgYzmzQ2PTbrtR5TndqV9HDPqfd4YxPkTrY
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7ekzkzmxfzLBhs18xdExG58TU8328TkYdzc11rpTNB8SGSCRXo",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM54Zfa2UnbvPU2za248PVxrk3s1gyCa3Kdnj4ogVQ3pv4upY6ga",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5rL6WMiUvnJXedsTqB4VmA8i95eYyYxmcMhqscYhaHArTniSzX",
1
]
]
},
"memo": "STM6qzmXaDZJLoKjh9EgYzmzQ2PTbrtR5TndqV9HDPqfd4YxPkTrY"
}Witness Votes
0 / 30
No active witness votes.
[]