VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS17.86%
Net Worth
1.373USD
STEEM
0.000STEEM
SBD
1.695SBD
Own SP
9.645SP
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 | 9.645SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 9.645SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 1.695SBD | 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": "15687.363031 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "1.695 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | prohashing |
| id | 40692 |
| rank | 136,873 |
| reputation | 48585587591 |
| created | 2016-07-29T00:23:15 |
| recovery_account | steem |
| proxy | None |
| post_count | 1 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2016-08-13T13:10:12 |
| last_root_post | 2016-08-13T13:10:12 |
| last_vote_time | 2016-08-13T20:49:33 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,949 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 1.695 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 15687.363031 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 | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM5yaAQ5WuuhP7AJgp9qCcHvkTabMSo23E5N9ezEWANbTRmiRSf8",
1
]
],
"weight_threshold": 1
},
"balance": "0.000 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2016-07-29T00:23:15",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1469751795
},
"guest_bloggers": [],
"id": 40692,
"json_metadata": "",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2016-08-13T13:10:12",
"last_root_post": "2016-08-13T13:10:12",
"last_vote_time": "2016-08-13T20:49:33",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM5CW99rE55MeopKcEgqbmnQSVeRZn7mJ7PCCLhuwyhuTfcoszwV",
"mined": false,
"name": "prohashing",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5s8WVxBqDnxTF5kLqvVwg23mAfgbzTpKwCg9u2MvdJHN2L66zw",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 10000,
"post_count": 1,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7kfU8P8R1bZhgP4Gu14Uz3JnnV6vnLyRgw3GcLwtbUzAmsKgWH",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "",
"posting_rewards": 1960,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "0.000000 VESTS",
"recovery_account": "steem",
"reputation": "48585587591",
"reset_account": "null",
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"sbd_balance": "1.695 SBD",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2016-08-14T09:34:39",
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "15687.363031 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": 9949,
"last_update_time": 1471121373
},
"voting_power": 9949,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 136873
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2019/07/29 01:27:54
2019/07/29 01:27:54
| author | steemitboard |
| body | Congratulations @prohashing! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@prohashing/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/@prohashing) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=prohashing)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | steemitboard-notify-prohashing-20190729t012753000z |
| title | |
| Transaction Info | Block #35072721/Trx 79fd87d68baf20083e373196c4e2a667d5cad923 |
View Raw JSON Data
{
"block": 35072721,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @prohashing! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@prohashing/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/@prohashing) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=prohashing)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "steemitboard-notify-prohashing-20190729t012753000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-07-29T01:27:54",
"trx_id": "79fd87d68baf20083e373196c4e2a667d5cad923",
"trx_in_block": 2,
"virtual_op": 0
}2018/07/29 01:10:54
2018/07/29 01:10:54
| author | steemitboard |
| body | Congratulations @prohashing! You have received a personal award! [](http://steemitboard.com/@prohashing) 2 Years on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | steemitboard-notify-prohashing-20180729t011053000z |
| title | |
| Transaction Info | Block #24586120/Trx 46d40d3da980f5bf45149ee81beff5abafd0bfc6 |
View Raw JSON Data
{
"block": 24586120,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @prohashing! You have received a personal award!\n\n[](http://steemitboard.com/@prohashing) 2 Years on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "steemitboard-notify-prohashing-20180729t011053000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-07-29T01:10:54",
"trx_id": "46d40d3da980f5bf45149ee81beff5abafd0bfc6",
"trx_in_block": 0,
"virtual_op": 0
}gohdarupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences2017/08/01 13:48:27
gohdarupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
2017/08/01 13:48:27
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | gohdar |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14195286/Trx 9aad3ad41af9f626af6162e7233943968113cb20 |
View Raw JSON Data
{
"block": 14195286,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "gohdar",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-01T13:48:27",
"trx_id": "9aad3ad41af9f626af6162e7233943968113cb20",
"trx_in_block": 41,
"virtual_op": 0
}razyconersupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences2017/07/21 13:59:00
razyconersupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
2017/07/21 13:59:00
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | razyconers |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13878942/Trx ee380ee9df80dd0e5aea31c0b36e5fc1aaedbc3b |
View Raw JSON Data
{
"block": 13878942,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "razyconers",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-07-21T13:59:00",
"trx_id": "ee380ee9df80dd0e5aea31c0b36e5fc1aaedbc3b",
"trx_in_block": 27,
"virtual_op": 0
}sophiedezielupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences2017/07/17 21:38:21
sophiedezielupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
2017/07/17 21:38:21
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | sophiedeziel |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13773002/Trx 0ff9816898322d1898231ae5ca19e00954e29075 |
View Raw JSON Data
{
"block": 13773002,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "sophiedeziel",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-07-17T21:38:21",
"trx_id": "0ff9816898322d1898231ae5ca19e00954e29075",
"trx_in_block": 4,
"virtual_op": 0
}queenwikiupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences2017/07/09 08:05:45
queenwikiupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
2017/07/09 08:05:45
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | queenwiki |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13526645/Trx 40e4f5b4d31cb703a9c4fc1b40ff1274fd1b9ab8 |
View Raw JSON Data
{
"block": 13526645,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "queenwiki",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-07-09T08:05:45",
"trx_id": "40e4f5b4d31cb703a9c4fc1b40ff1274fd1b9ab8",
"trx_in_block": 9,
"virtual_op": 0
}ramirodachapadaupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences2017/07/02 14:51:27
ramirodachapadaupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
2017/07/02 14:51:27
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | ramirodachapada |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13333732/Trx 40502b9c544624626990656a37fda29683c461fd |
View Raw JSON Data
{
"block": 13333732,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "ramirodachapada",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-07-02T14:51:27",
"trx_id": "40502b9c544624626990656a37fda29683c461fd",
"trx_in_block": 3,
"virtual_op": 0
}blue8044upvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences2017/06/24 17:10:00
blue8044upvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
2017/06/24 17:10:00
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | blue8044 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13106496/Trx 17d44d8a4073213b293ebab594599d39186b76ea |
View Raw JSON Data
{
"block": 13106496,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "blue8044",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-06-24T17:10:00",
"trx_id": "17d44d8a4073213b293ebab594599d39186b76ea",
"trx_in_block": 30,
"virtual_op": 0
}paredaoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
paredaoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | paredao |
| weight | 10000 (100.00%) |
| Transaction Info | Block #7303287/Trx 4de531fe2ea2ea75bd5843e1e682b2340af63185 |
View Raw JSON Data
{
"block": 7303287,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "paredao",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-12-04T22:03:54",
"trx_id": "4de531fe2ea2ea75bd5843e1e682b2340af63185",
"trx_in_block": 3,
"virtual_op": 0
}klidexupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
klidexupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | klidex |
| weight | 10000 (100.00%) |
| Transaction Info | Block #7139666/Trx 472fdecc7e5b2fa80e2c5685a8dab7889598f234 |
View Raw JSON Data
{
"block": 7139666,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "klidex",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-11-29T05:35:51",
"trx_id": "472fdecc7e5b2fa80e2c5685a8dab7889598f234",
"trx_in_block": 1,
"virtual_op": 0
}artem-sokoloffupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
artem-sokoloffupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | artem-sokoloff |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5675422/Trx 010b258a4587f4296fe3d4c21ff0b6a5960d1492 |
View Raw JSON Data
{
"block": 5675422,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "artem-sokoloff",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-10-09T08:03:42",
"trx_id": "010b258a4587f4296fe3d4c21ff0b6a5960d1492",
"trx_in_block": 5,
"virtual_op": 0
}| author | kyle.lapo |
| body | Holy moly. This puts a much different perspective on the cryptocurrency economy. Why doesn't this post have more up votes? |
| json metadata | {"tags":["bitcoin"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160818t234532270z |
| title | |
| Transaction Info | Block #4202683/Trx cff54584feb43e66fe3b193f256c8bdffe61953c |
View Raw JSON Data
{
"block": 4202683,
"op": [
"comment",
{
"author": "kyle.lapo",
"body": "Holy moly. This puts a much different perspective on the cryptocurrency economy. Why doesn't this post have more up votes?",
"json_metadata": "{\"tags\":[\"bitcoin\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160818t234532270z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-18T23:45:36",
"trx_id": "cff54584feb43e66fe3b193f256c8bdffe61953c",
"trx_in_block": 0,
"virtual_op": 0
}kyle.lapoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
kyle.lapoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | kyle.lapo |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4202638/Trx b78a6df7fb84d201e9bda0727d3374a6549088a4 |
View Raw JSON Data
{
"block": 4202638,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "kyle.lapo",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-18T23:43:21",
"trx_id": "b78a6df7fb84d201e9bda0727d3374a6549088a4",
"trx_in_block": 4,
"virtual_op": 0
}niknightupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
niknightupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | niknight |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4176563/Trx 0e34ba11e9594afd2bd074f5373728f5e544d29f |
View Raw JSON Data
{
"block": 4176563,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "niknight",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-18T01:51:30",
"trx_id": "0e34ba11e9594afd2bd074f5373728f5e544d29f",
"trx_in_block": 0,
"virtual_op": 0
}kenmonkeyupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
kenmonkeyupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | kenmonkey |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4098616/Trx 5f693d59f2900be0bb05eb885c76fb6483eee28e |
View Raw JSON Data
{
"block": 4098616,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "kenmonkey",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-15T08:32:09",
"trx_id": "5f693d59f2900be0bb05eb885c76fb6483eee28e",
"trx_in_block": 0,
"virtual_op": 0
}ejhongupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
ejhongupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | ejhong |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4091022/Trx e3f11fff9d2931ffb8cff5bdedfc4a1fc1d9b0fe |
View Raw JSON Data
{
"block": 4091022,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "ejhong",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-15T02:11:24",
"trx_id": "e3f11fff9d2931ffb8cff5bdedfc4a1fc1d9b0fe",
"trx_in_block": 3,
"virtual_op": 0
}| author | painlord2k |
| body | What is missing in the OP is what we read about in the last 24 hours: "I am currently in the midst of crowdfunding my own smart contract network tailored to the needs of the music industry, called Tao. Tao is designed to execute Bitcoin transactions automatically in order to settle royalty payments." "I had the opportunity to have a quick chat with Kim Dotcom and our goals are aligned. Tao and Kim's BitCache system stand to generate thousands of transactions per block, exceeding the tolerances calculated by SegWit. Lightning networks simply are not an applicable solution to our applications." What I point out is these (or anything like these) are the killer applications for BTC-B(ig)B(blocks). These will generate value outside the BTC-S(mall)B(locks) branch and only in the BTC-BB In this case, the BB branch can execute all txs the SB branch can and many more. Given the higher fee required to confirm on the SB branch, all transactions in the SB would confirm in the BB but not the reverse. The fork coders could avoid and ignore the need to separate the txs in a branch from the tx in the other. This is matter for wallets. Every tx would be validable in both branches, but once a tx is validated in the BB but not in the SB, the same bitcoin in the SB can not be used anymore in the BB. If there is a demand for BTCs in the BB branch (to be used to pay for songs rights or downloads) the buyers will only have the BTC mined in the BB branch, and the BTC mined before the fork and not splitted. More pre-fork BTC are used in the BB-branch to pay for small transactions with small fees (outstripping the ability of the SB-branch to keep up and splitting, de facto, the coins in two different chains) more demand there will be and less BTC will be available to be dumped in the new chain from the old chain. It don't matter if the SB-branch split the coins and dump them on the BB-chain, because the use case will anyway support a price different from zero and accepting the transactions in the other branch (valid in both of the branches) as valid will always give something to mine. The problem is protecting the branch from a 51% attack and the initial change of difficulty, but there are pretty easy ways to do it with small changes to the PoW and rules to accept new blocks. As the use increase, the price of the BB-BTC would continue to rise against the SM-BTC. |
| json metadata | {"tags":["bitcoin"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160814t144756607z |
| title | |
| Transaction Info | Block #4077429/Trx 8f325edd7cc400f3d89aefe97386ca9c397e867e |
View Raw JSON Data
{
"block": 4077429,
"op": [
"comment",
{
"author": "painlord2k",
"body": "What is missing in the OP is what we read about in the last 24 hours:\n\n\"I am currently in the midst of crowdfunding my own smart contract network tailored to the needs of the music industry, called Tao. Tao is designed to execute Bitcoin transactions automatically in order to settle royalty payments.\"\n\n\"I had the opportunity to have a quick chat with Kim Dotcom and our goals are aligned. Tao and Kim's BitCache system stand to generate thousands of transactions per block, exceeding the tolerances calculated by SegWit. Lightning networks simply are not an applicable solution to our applications.\"\n\nWhat I point out is these (or anything like these) are the killer applications for BTC-B(ig)B(blocks). These will generate value outside the BTC-S(mall)B(locks) branch and only in the BTC-BB\n\nIn this case, the BB branch can execute all txs the SB branch can and many more. Given the higher fee required to confirm on the SB branch, all transactions in the SB would confirm in the BB but not the reverse.\n\nThe fork coders could avoid and ignore the need to separate the txs in a branch from the tx in the other. This is matter for wallets.\nEvery tx would be validable in both branches, but once a tx is validated in the BB but not in the SB, the same bitcoin in the SB can not be used anymore in the BB.\n\nIf there is a demand for BTCs in the BB branch (to be used to pay for songs rights or downloads) the buyers will only have the BTC mined in the BB branch, and the BTC mined before the fork and not splitted. More pre-fork BTC are used in the BB-branch to pay for small transactions with small fees (outstripping the ability of the SB-branch to keep up and splitting, de facto, the coins in two different chains) more demand there will be and less BTC will be available to be dumped in the new chain from the old chain.\n\nIt don't matter if the SB-branch split the coins and dump them on the BB-chain, because the use case will anyway support a price different from zero and accepting the transactions in the other branch (valid in both of the branches) as valid will always give something to mine.\n\nThe problem is protecting the branch from a 51% attack and the initial change of difficulty, but there are pretty easy ways to do it with small changes to the PoW and rules to accept new blocks.\n\nAs the use increase, the price of the BB-BTC would continue to rise against the SM-BTC.",
"json_metadata": "{\"tags\":[\"bitcoin\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160814t144756607z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T14:48:21",
"trx_id": "8f325edd7cc400f3d89aefe97386ca9c397e867e",
"trx_in_block": 0,
"virtual_op": 0
}prohashingreceived 1.695 SBD, 2.184 SP author reward for @prohashing / bitcoin-will-fork-soon-with-significant-consequences
prohashingreceived 1.695 SBD, 2.184 SP author reward for @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| sbd payout | 1.695 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 3552.696429 VESTS |
| Transaction Info | Block #4071200/Virtual Operation #15 |
View Raw JSON Data
{
"block": 4071200,
"op": [
"author_reward",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"sbd_payout": "1.695 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "3552.696429 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T09:34:39",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 15
}totoskyupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
totoskyupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | totosky |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4069990/Trx 62723a369ce2ca8900392f08f98cd6bf3a1def79 |
View Raw JSON Data
{
"block": 4069990,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "totosky",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T08:33:30",
"trx_id": "62723a369ce2ca8900392f08f98cd6bf3a1def79",
"trx_in_block": 1,
"virtual_op": 0
}steemidupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
steemidupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | steemid |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4067059/Trx 78020923f80314fc1c894864a619b4024e68124e |
View Raw JSON Data
{
"block": 4067059,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "steemid",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T06:06:00",
"trx_id": "78020923f80314fc1c894864a619b4024e68124e",
"trx_in_block": 0,
"virtual_op": 0
}mreichardtupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
mreichardtupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | mreichardt |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4066426/Trx bbbd7f513f55c4446707f056d3a9df4437bcee87 |
View Raw JSON Data
{
"block": 4066426,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "mreichardt",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T05:34:12",
"trx_id": "bbbd7f513f55c4446707f056d3a9df4437bcee87",
"trx_in_block": 0,
"virtual_op": 0
}john-agupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
john-agupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | john-ag |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4066117/Trx 56626219f8487748cb27ccfacd374981e8f9a863 |
View Raw JSON Data
{
"block": 4066117,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "john-ag",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T05:18:45",
"trx_id": "56626219f8487748cb27ccfacd374981e8f9a863",
"trx_in_block": 0,
"virtual_op": 0
}hedge-xupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
hedge-xupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | hedge-x |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4065113/Trx 44f22665ae4f5fdcbeff443a9e12bcebcfa344ac |
View Raw JSON Data
{
"block": 4065113,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "hedge-x",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T04:28:15",
"trx_id": "44f22665ae4f5fdcbeff443a9e12bcebcfa344ac",
"trx_in_block": 0,
"virtual_op": 0
}cryptoheadflagged (-100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
cryptoheadflagged (-100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | cryptohead |
| weight | -10000 (-100.00%) |
| Transaction Info | Block #4061524/Trx 612d5ae067cbb7803694f986412cc6e440511ca2 |
View Raw JSON Data
{
"block": 4061524,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "cryptohead",
"weight": -10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T01:27:45",
"trx_id": "612d5ae067cbb7803694f986412cc6e440511ca2",
"trx_in_block": 0,
"virtual_op": 0
}| author | cryptohead |
| body | @@ -143,9 +143,8 @@ alt- -= coin |
| json metadata | {"tags":["bitcoin"],"image":["https://coin.dance/blocks/image/summary.png"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160814t012316495z |
| title | |
| Transaction Info | Block #4061450/Trx 5603ef0d8c607fea3d8658dc087fddcb7fad6571 |
View Raw JSON Data
{
"block": 4061450,
"op": [
"comment",
{
"author": "cryptohead",
"body": "@@ -143,9 +143,8 @@\n alt-\n-=\n coin\n",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"image\":[\"https://coin.dance/blocks/image/summary.png\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160814t012316495z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T01:24:00",
"trx_id": "5603ef0d8c607fea3d8658dc087fddcb7fad6571",
"trx_in_block": 1,
"virtual_op": 0
}| author | cryptohead |
| body | You are way out of line in your assertions. Anybody can fork Bitcoin at anytime, just copy the code, and name it whatever. This is how most alt-=coins have come into existence. ### There is an indisputable consensus among Bitcoin miners in support of BTC Core and its road-map Please see who is securing 96.5% of all the BTC blocks:  Coindance : https://coin.dance/blocks This is old news, it was decided in a miners' meeting held in Hong Kong last year. But some hard heads keep on spreading FUD ... ;) Core's road-map points to deploying Segregated Witness first. This will bring about 75% more capacity with the current block size, and a myriad of other advantages that will accelerate further development without the need for hard forks. Yes, as you pointed out, **hard forks are dangerous!** SegWit is already being tested and it will soon be ready to implement in real BTC blockchain. And YES, 96.5% of miners will support it. As long as you grow, **scaling will be a never-ending challenge** ## Bitcoin has been growing and maturing for 8 years already Please be patient |
| json metadata | {"tags":["bitcoin"],"image":["https://coin.dance/blocks/image/summary.png"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160814t012316495z |
| title | |
| Transaction Info | Block #4061434/Trx 5cb799b0672cc1e3a356936f83c026505b937f67 |
View Raw JSON Data
{
"block": 4061434,
"op": [
"comment",
{
"author": "cryptohead",
"body": "You are way out of line in your assertions.\n\nAnybody can fork Bitcoin at anytime, just copy the code, and name it whatever. This is how most alt-=coins have come into existence.\n\n### There is an indisputable consensus among Bitcoin miners in support of BTC Core and its road-map\nPlease see who is securing 96.5% of all the BTC blocks:\n\nCoindance : https://coin.dance/blocks\nThis is old news, it was decided in a miners' meeting held in Hong Kong last year. But some hard heads keep on spreading FUD ... ;)\nCore's road-map points to deploying Segregated Witness first.\nThis will bring about 75% more capacity with the current block size, and a myriad of other advantages that will accelerate further development without the need for hard forks. Yes, as you pointed out, **hard forks are dangerous!**\nSegWit is already being tested and it will soon be ready to implement in real BTC blockchain. And YES, 96.5% of miners will support it.\n\nAs long as you grow, **scaling will be a never-ending challenge**\n\n## Bitcoin has been growing and maturing for 8 years already\n\nPlease be patient",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"image\":[\"https://coin.dance/blocks/image/summary.png\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160814t012316495z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T01:23:12",
"trx_id": "5cb799b0672cc1e3a356936f83c026505b937f67",
"trx_in_block": 0,
"virtual_op": 0
}limzeroupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
limzeroupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | limzero |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4060432/Trx 34139e28e7fe8cb3ed6fac9c9b00c6a71a7712c8 |
View Raw JSON Data
{
"block": 4060432,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "limzero",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-14T00:32:42",
"trx_id": "34139e28e7fe8cb3ed6fac9c9b00c6a71a7712c8",
"trx_in_block": 8,
"virtual_op": 0
}murhupvoted (33.01%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
murhupvoted (33.01%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | murh |
| weight | 3301 (33.01%) |
| Transaction Info | Block #4058095/Trx d8ca889738b1c546aeba601044b64ef3100f3156 |
View Raw JSON Data
{
"block": 4058095,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "murh",
"weight": 3301
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T22:35:06",
"trx_id": "d8ca889738b1c546aeba601044b64ef3100f3156",
"trx_in_block": 3,
"virtual_op": 0
}creatorupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
creatorupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | creator |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4058084/Trx 3c2a9be159ddf7aafa43614d45b00ff030dd0da3 |
View Raw JSON Data
{
"block": 4058084,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "creator",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T22:34:33",
"trx_id": "3c2a9be159ddf7aafa43614d45b00ff030dd0da3",
"trx_in_block": 5,
"virtual_op": 0
}geronimoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
geronimoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | geronimo |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4058075/Trx a7cb92aad779185281b6755ca5761c375527ddf3 |
View Raw JSON Data
{
"block": 4058075,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "geronimo",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T22:34:03",
"trx_id": "a7cb92aad779185281b6755ca5761c375527ddf3",
"trx_in_block": 4,
"virtual_op": 0
}kbeupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
kbeupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | kbe |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4057162/Trx 5ef470a83d01a79b332af166a65ef8cc47f7274d |
View Raw JSON Data
{
"block": 4057162,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "kbe",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T21:48:00",
"trx_id": "5ef470a83d01a79b332af166a65ef8cc47f7274d",
"trx_in_block": 0,
"virtual_op": 0
}cryptoruneupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
cryptoruneupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | cryptorune |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4056465/Trx 9a81c4faa10e4def678e9c10e9b69eb213ae4a86 |
View Raw JSON Data
{
"block": 4056465,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "cryptorune",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T21:13:03",
"trx_id": "9a81c4faa10e4def678e9c10e9b69eb213ae4a86",
"trx_in_block": 0,
"virtual_op": 0
}oyvindupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
oyvindupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | oyvind |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4056302/Trx d7c3c75c5eaddbc9e00bc7e3c806b41737158ba1 |
View Raw JSON Data
{
"block": 4056302,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "oyvind",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T21:04:51",
"trx_id": "d7c3c75c5eaddbc9e00bc7e3c806b41737158ba1",
"trx_in_block": 1,
"virtual_op": 0
}joelcanupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
joelcanupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | joelcan |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4056251/Trx f6863cc8f978a6c2f1c68dc3f83b6a05d35f76d8 |
View Raw JSON Data
{
"block": 4056251,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "joelcan",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T21:02:15",
"trx_id": "f6863cc8f978a6c2f1c68dc3f83b6a05d35f76d8",
"trx_in_block": 0,
"virtual_op": 0
}fran2kremoved vote from (0.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
fran2kremoved vote from (0.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | fran2k |
| weight | 0 (0.00%) |
| Transaction Info | Block #4056158/Trx a4c8c7bda8f5f453936b0d9ec55db765d2739f89 |
View Raw JSON Data
{
"block": 4056158,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "fran2k",
"weight": 0
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T20:57:36",
"trx_id": "a4c8c7bda8f5f453936b0d9ec55db765d2739f89",
"trx_in_block": 4,
"virtual_op": 0
}fran2kupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
fran2kupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | fran2k |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4056151/Trx 81ded0af2aeeb817e673ae610e1392e196020635 |
View Raw JSON Data
{
"block": 4056151,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "fran2k",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T20:57:15",
"trx_id": "81ded0af2aeeb817e673ae610e1392e196020635",
"trx_in_block": 0,
"virtual_op": 0
}| author | cryptocylon |
| permlink | re-mamma-re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t170020350z |
| voter | prohashing |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4055998/Trx b31b7f5a371cae06f78f234cb1fd770974655c14 |
View Raw JSON Data
{
"block": 4055998,
"op": [
"vote",
{
"author": "cryptocylon",
"permlink": "re-mamma-re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t170020350z",
"voter": "prohashing",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T20:49:33",
"trx_id": "b31b7f5a371cae06f78f234cb1fd770974655c14",
"trx_in_block": 1,
"virtual_op": 0
}toxonautupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
toxonautupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | toxonaut |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4055727/Trx cff8513b95b98d21a01d49a88e9b3d5a5c0e5e9b |
View Raw JSON Data
{
"block": 4055727,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "toxonaut",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T20:35:54",
"trx_id": "cff8513b95b98d21a01d49a88e9b3d5a5c0e5e9b",
"trx_in_block": 5,
"virtual_op": 0
}newtherapyupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
newtherapyupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | newtherapy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4053563/Trx 9b62d1204ac20c8e05e92802d9d5640db39d030a |
View Raw JSON Data
{
"block": 4053563,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "newtherapy",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T18:47:03",
"trx_id": "9b62d1204ac20c8e05e92802d9d5640db39d030a",
"trx_in_block": 4,
"virtual_op": 0
}greenmanupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
greenmanupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | greenman |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4053384/Trx 54df647f27a4effd3181ce3e50e89529fa7e1dc0 |
View Raw JSON Data
{
"block": 4053384,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "greenman",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T18:38:03",
"trx_id": "54df647f27a4effd3181ce3e50e89529fa7e1dc0",
"trx_in_block": 4,
"virtual_op": 0
}kylarkupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
kylarkupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | kylark |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4052786/Trx 226c917adda8d273d59236aca40d77f463ea7376 |
View Raw JSON Data
{
"block": 4052786,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "kylark",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T18:08:00",
"trx_id": "226c917adda8d273d59236aca40d77f463ea7376",
"trx_in_block": 1,
"virtual_op": 0
}fatboyupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
fatboyupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | fatboy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4052556/Trx 78e17a582fe0251441c44fe1852c9d4e4f33c129 |
View Raw JSON Data
{
"block": 4052556,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "fatboy",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T17:56:30",
"trx_id": "78e17a582fe0251441c44fe1852c9d4e4f33c129",
"trx_in_block": 2,
"virtual_op": 0
}themonetaryfewupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
themonetaryfewupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | themonetaryfew |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4052538/Trx f91f1a8ee168d8290dc30a9dd2486f05dafa797b |
View Raw JSON Data
{
"block": 4052538,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "themonetaryfew",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T17:55:36",
"trx_id": "f91f1a8ee168d8290dc30a9dd2486f05dafa797b",
"trx_in_block": 4,
"virtual_op": 0
}pattayapeteupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
pattayapeteupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | pattayapete |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4052528/Trx 5401769b1cddfca1d52b49c5c0b65be2fbe9fd16 |
View Raw JSON Data
{
"block": 4052528,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "pattayapete",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T17:55:06",
"trx_id": "5401769b1cddfca1d52b49c5c0b65be2fbe9fd16",
"trx_in_block": 0,
"virtual_op": 0
}rubberhosecryptoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
rubberhosecryptoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | rubberhosecrypto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4051621/Trx 2bb1553f90219ddbb27fcf3d5048cfa56fc19bb6 |
View Raw JSON Data
{
"block": 4051621,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "rubberhosecrypto",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T17:09:33",
"trx_id": "2bb1553f90219ddbb27fcf3d5048cfa56fc19bb6",
"trx_in_block": 1,
"virtual_op": 0
}cryptocylonupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
cryptocylonupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | cryptocylon |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4051372/Trx 9f3012540d9fd04248809c0c937f71e045dd26ea |
View Raw JSON Data
{
"block": 4051372,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "cryptocylon",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T16:57:00",
"trx_id": "9f3012540d9fd04248809c0c937f71e045dd26ea",
"trx_in_block": 0,
"virtual_op": 0
}joergupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
joergupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | joerg |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4051290/Trx 5f03c591f10f4c7a3a232d034bd6ade1c4ea3a5a |
View Raw JSON Data
{
"block": 4051290,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "joerg",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T16:52:54",
"trx_id": "5f03c591f10f4c7a3a232d034bd6ade1c4ea3a5a",
"trx_in_block": 0,
"virtual_op": 0
}| author | pigeons |
| body | This is really horrible utter nonsense. From Craig Wright, to claiming users support a fork from a totally inaccurate and unscientific poll. There is nothing of value in this piece. Sorry to be harsh but you should not write things that are false. |
| json metadata | {"tags":["bitcoin"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t164256879z |
| title | |
| Transaction Info | Block #4051092/Trx 5bf5e844496927627c3a050290c974b03f37f781 |
View Raw JSON Data
{
"block": 4051092,
"op": [
"comment",
{
"author": "pigeons",
"body": "This is really horrible utter nonsense. From Craig Wright, to claiming users support a fork from a totally inaccurate and unscientific poll. There is nothing of value in this piece. Sorry to be harsh but you should not write things that are false.",
"json_metadata": "{\"tags\":[\"bitcoin\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t164256879z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T16:42:57",
"trx_id": "5bf5e844496927627c3a050290c974b03f37f781",
"trx_in_block": 1,
"virtual_op": 0
}pigeonsflagged (-100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
pigeonsflagged (-100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | pigeons |
| weight | -10000 (-100.00%) |
| Transaction Info | Block #4051052/Trx 3aad3f5d746288483e9758671cb0f8b91ffe296a |
View Raw JSON Data
{
"block": 4051052,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "pigeons",
"weight": -10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T16:40:54",
"trx_id": "3aad3f5d746288483e9758671cb0f8b91ffe296a",
"trx_in_block": 1,
"virtual_op": 0
}makingearworkupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
makingearworkupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | makingearwork |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4049960/Trx 70fe7ad86333559678e416a34a0ad2ba026892e6 |
View Raw JSON Data
{
"block": 4049960,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "makingearwork",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T15:46:03",
"trx_id": "70fe7ad86333559678e416a34a0ad2ba026892e6",
"trx_in_block": 0,
"virtual_op": 0
}stevenh512upvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
stevenh512upvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | stevenh512 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4048650/Trx 6c3780d0e9aa20180e8451fe06ec7e453d5d5152 |
View Raw JSON Data
{
"block": 4048650,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "stevenh512",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T14:40:06",
"trx_id": "6c3780d0e9aa20180e8451fe06ec7e453d5d5152",
"trx_in_block": 1,
"virtual_op": 0
}| author | nikolai |
| body | @@ -723,8 +723,189 @@ anymore. + And miners follow price, as you said. So who cares if they all leave? I'll tell you who, exactly the people that need their chain secured by POW with no risk of unexpected changes. |
| json metadata | {"tags":["bitcoin"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t142959882z |
| title | |
| Transaction Info | Block #4048469/Trx 40674b88f5f4bde376de2b087be06c02cd05c2a7 |
View Raw JSON Data
{
"block": 4048469,
"op": [
"comment",
{
"author": "nikolai",
"body": "@@ -723,8 +723,189 @@\n anymore.\n+ And miners follow price, as you said. So who cares if they all leave? I'll tell you who, exactly the people that need their chain secured by POW with no risk of unexpected changes.\n",
"json_metadata": "{\"tags\":[\"bitcoin\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t142959882z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T14:31:03",
"trx_id": "40674b88f5f4bde376de2b087be06c02cd05c2a7",
"trx_in_block": 2,
"virtual_op": 0
}| author | nikolai |
| body | Let me try to summarize: * Miners follow follow the price * Users follow the media * In the ETH vs ETC case, media heavily favors ETH for several reasons (including faster and cheaper transaction), which is why that fork dominates * In the BTC case, the media is split and in particular theymos is a kind of tiebreaker * A BTC fork is incoming because a significant fraction of bitcoiners follow media which believes a crypto's long term value is maximized when it can have many cheap transactions. My response is this, you seem to realize the significance of names when it comes to forking. If "Bitcoin" forks to prioritize "usable" (consumer frequency) TPS, it will also become a thing which doesn't even need miners anymore. |
| json metadata | {"tags":["bitcoin"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t142959882z |
| title | |
| Transaction Info | Block #4048447/Trx 08c6986446d1f517359f10caa442be0a9964e950 |
View Raw JSON Data
{
"block": 4048447,
"op": [
"comment",
{
"author": "nikolai",
"body": "Let me try to summarize:\n\n* Miners follow follow the price\n* Users follow the media\n* In the ETH vs ETC case, media heavily favors ETH for several reasons (including faster and cheaper transaction), which is why that fork dominates\n* In the BTC case, the media is split and in particular theymos is a kind of tiebreaker\n* A BTC fork is incoming because a significant fraction of bitcoiners follow media which believes a crypto's long term value is maximized when it can have many cheap transactions.\n\nMy response is this, you seem to realize the significance of names when it comes to forking. If \"Bitcoin\" forks to prioritize \"usable\" (consumer frequency) TPS, it will also become a thing which doesn't even need miners anymore.",
"json_metadata": "{\"tags\":[\"bitcoin\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t142959882z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T14:29:57",
"trx_id": "08c6986446d1f517359f10caa442be0a9964e950",
"trx_in_block": 0,
"virtual_op": 0
}demotrukupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
demotrukupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | demotruk |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4048439/Trx 7c2841e4331a10db88eb04d15b1092e2f34941b6 |
View Raw JSON Data
{
"block": 4048439,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "demotruk",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T14:29:33",
"trx_id": "7c2841e4331a10db88eb04d15b1092e2f34941b6",
"trx_in_block": 7,
"virtual_op": 0
}| author | mamma |
| body | Bitcoin as a store of value won't be dethroned for at least 5 years. ETH still has to prove its PoS transition among other issues. You make some good points, but your predictions are probably very inacurate. |
| json metadata | {"tags":["bitcoin"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t141133278z |
| title | |
| Transaction Info | Block #4048082/Trx 9162761ec85b86856f3610b3b29717ca3ccc0f44 |
View Raw JSON Data
{
"block": 4048082,
"op": [
"comment",
{
"author": "mamma",
"body": "Bitcoin as a store of value won't be dethroned for at least 5 years. ETH still has to prove its PoS transition among other issues. You make some good points, but your predictions are probably very inacurate.",
"json_metadata": "{\"tags\":[\"bitcoin\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t141133278z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T14:11:33",
"trx_id": "9162761ec85b86856f3610b3b29717ca3ccc0f44",
"trx_in_block": 1,
"virtual_op": 0
}nikolaiupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
nikolaiupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | nikolai |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4048046/Trx 181521f23a2ef955fbfe4f43c1db041659b4433d |
View Raw JSON Data
{
"block": 4048046,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "nikolai",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T14:09:45",
"trx_id": "181521f23a2ef955fbfe4f43c1db041659b4433d",
"trx_in_block": 4,
"virtual_op": 0
}helikopterbenupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
helikopterbenupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | helikopterben |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047787/Trx a84ccbea37df840835bba7f78450f9597499b1b3 |
View Raw JSON Data
{
"block": 4047787,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "helikopterben",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:56:42",
"trx_id": "a84ccbea37df840835bba7f78450f9597499b1b3",
"trx_in_block": 0,
"virtual_op": 0
}alecoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
alecoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | aleco |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047734/Trx b45b89cd10590d75f5c3c36b7198f500d7e029f8 |
View Raw JSON Data
{
"block": 4047734,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "aleco",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:54:03",
"trx_id": "b45b89cd10590d75f5c3c36b7198f500d7e029f8",
"trx_in_block": 1,
"virtual_op": 0
}neowenyuan27upvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
neowenyuan27upvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | neowenyuan27 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047724/Trx a8fba0c43f1758258a25553ad0f443d4a0648fd7 |
View Raw JSON Data
{
"block": 4047724,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "neowenyuan27",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:53:33",
"trx_id": "a8fba0c43f1758258a25553ad0f443d4a0648fd7",
"trx_in_block": 0,
"virtual_op": 0
}lukestokesupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
lukestokesupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | lukestokes |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047452/Trx 3116ff584fac836cec28e0693c20455218ccca82 |
View Raw JSON Data
{
"block": 4047452,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "lukestokes",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:39:51",
"trx_id": "3116ff584fac836cec28e0693c20455218ccca82",
"trx_in_block": 1,
"virtual_op": 0
}cybernanoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
cybernanoupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | cybernano |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047395/Trx 6f0ccbd8b76de73d70a1db551a994962d7f958c1 |
View Raw JSON Data
{
"block": 4047395,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "cybernano",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:37:00",
"trx_id": "6f0ccbd8b76de73d70a1db551a994962d7f958c1",
"trx_in_block": 0,
"virtual_op": 0
}alsprintingupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
alsprintingupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | alsprinting |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047382/Trx 8dcc7538705c15cd40d8d7c2f5b766cfef03ba89 |
View Raw JSON Data
{
"block": 4047382,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "alsprinting",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:36:21",
"trx_id": "8dcc7538705c15cd40d8d7c2f5b766cfef03ba89",
"trx_in_block": 0,
"virtual_op": 0
}gbertupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
gbertupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | gbert |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047364/Trx c2c8d98c7c8d4da652d17ff9549b86b044311f4d |
View Raw JSON Data
{
"block": 4047364,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "gbert",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:35:27",
"trx_id": "c2c8d98c7c8d4da652d17ff9549b86b044311f4d",
"trx_in_block": 2,
"virtual_op": 0
}mammaupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
mammaupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | mamma |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047291/Trx ad1ec6f29c12c72feb865cbd82f4195650dd3190 |
View Raw JSON Data
{
"block": 4047291,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "mamma",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:31:45",
"trx_id": "ad1ec6f29c12c72feb865cbd82f4195650dd3190",
"trx_in_block": 3,
"virtual_op": 0
}alanslaugupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
alanslaugupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | alanslaug |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047197/Trx 52f7bd6c45285e1c2a2f09a63302b44d08fc43e4 |
View Raw JSON Data
{
"block": 4047197,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "alanslaug",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:27:03",
"trx_id": "52f7bd6c45285e1c2a2f09a63302b44d08fc43e4",
"trx_in_block": 0,
"virtual_op": 0
}dskloetupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
dskloetupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | dskloet |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047172/Trx fd6590e509be0850e63bfa61e190766bce46b693 |
View Raw JSON Data
{
"block": 4047172,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "dskloet",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:25:48",
"trx_id": "fd6590e509be0850e63bfa61e190766bce46b693",
"trx_in_block": 0,
"virtual_op": 0
}| author | allmonitors |
| body | Bitcoiners far outnumber Ethereum fans. Of course the majority of interest will come from the Bitcoin side. |
| json metadata | {"tags":["bitcoin"]} |
| parent author | prohashing |
| parent permlink | bitcoin-will-fork-soon-with-significant-consequences |
| permlink | re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t132241898z |
| title | |
| Transaction Info | Block #4047111/Trx 3f911aa63ac33d83dea36a74de4a32303040ef30 |
View Raw JSON Data
{
"block": 4047111,
"op": [
"comment",
{
"author": "allmonitors",
"body": "Bitcoiners far outnumber Ethereum fans. Of course the majority of interest will come from the Bitcoin side.",
"json_metadata": "{\"tags\":[\"bitcoin\"]}",
"parent_author": "prohashing",
"parent_permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"permlink": "re-prohashing-bitcoin-will-fork-soon-with-significant-consequences-20160813t132241898z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:22:42",
"trx_id": "3f911aa63ac33d83dea36a74de4a32303040ef30",
"trx_in_block": 0,
"virtual_op": 0
}allmonitorsupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
allmonitorsupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | allmonitors |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4047072/Trx 049893a8f14ab8bf3dca3e22a7d962b7c8752fd5 |
View Raw JSON Data
{
"block": 4047072,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "allmonitors",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:20:45",
"trx_id": "049893a8f14ab8bf3dca3e22a7d962b7c8752fd5",
"trx_in_block": 1,
"virtual_op": 0
}prohashingupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
prohashingupvoted (100.00%) @prohashing / bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| voter | prohashing |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4046862/Trx fd6fd2e5b1d92ad8b9f3350a63e63fb09117e4ab |
View Raw JSON Data
{
"block": 4046862,
"op": [
"vote",
{
"author": "prohashing",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"voter": "prohashing",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:10:12",
"trx_id": "fd6fd2e5b1d92ad8b9f3350a63e63fb09117e4ab",
"trx_in_block": 3,
"virtual_op": 0
}prohashingpublished a new post: bitcoin-will-fork-soon-with-significant-consequences
prohashingpublished a new post: bitcoin-will-fork-soon-with-significant-consequences
| author | prohashing |
| body | **Introduction** I've heard a lot about the Steem platform, so I decided to try posting on it for this one topic. I'm looking for a place where I can control my own content without it being at risk of deletion, and where there is generally a higher comment quality available than those seen at reddit. We'll see how it goes. Today, I thought it would be a good idea to review my earlier outlook on the future of Bitcoin and Ethereum, which was initially posted at http://forums.prohashing.com/viewtopic.php?f=11&t=782. In general, I believe that the predictions made earlier, despite being delayed by the Ethereum fork, will continue to play out. The major difference from my earlier predictions is that I had only considered an "official" fork supported by the Core, and didn't include the possibility of a fork initiated without prior consensus. I'm now pretty sure that Bitcoin will have a hostile, non-Core fork, but so much time has passed that I don't think it has a high probability of success because, as I'll show, the outcome will be determined by the media, which is controlled by theymos. Even if the fork beats the odds, the outlook in the short term is grim regardless. <br> **Ethereum provided a wakeup call** What has been preventing Bitcoin from forking seems to be that many people believe that miners control coins' destiny. As I pointed out at http://forums.prohashing.com/viewtopic.php?f=11&t=717, markets always pop up for both chains after a fork of a widely traded coin, because exchanges can make more profit that way. It's one of the reasons I've reiterated that the idea of creating a "2MB" fork has little chance of success. A temporary blocksize increase just increases the number of forks that are traded, causing confusion and confrontation. Furthermore, we know that hashrate follows price, not the other way around. Many people continue to rail against the Bitcoin Core developers and expect miners to revolt without providing them an alternative fork first where they can earn profit. We saw the causality between hashrate and price in action with Ethereum Classic (ETC), which had almost no hashrate immediately after the fork. Then, investor Barry Silbert led the charge in pushing up its price through his articles and Twitter posts. People like me started mining it - not because I have any belief whatsoever that ETC will surpass ETH, but simply because there were buy orders that I could sell into. ETC mining was so profitable that I turned on a house full of miners, on one of the hottest summer days with temperatures around 85 degrees. We mine ETC and have our payouts auto-sold into ETH. Most of the ETC miners, like us, don't care about ETC; they just want to get rid of the coins so that they could make more profit. If you still have trouble believing that miners care only about money, consider that over 95% of the payout coins we issue at our pool occur in coins other than the coin that was mined. Despite so much hashrate being pointed towards ETC, the polls before the ETH fork indicated widespread support among users when weighted by holdings. It was pointless to ask ETH miners before the fork what their opinions were, because I've pointed out before that exchanges, not miners, have the power to decide these things. ETH will continue to be the canonical chain, and and ETC will remain a sideshow, but that doesn't mean that miners won't exploit ETC for profit while it lasts. <br> **A Bitcoin fork is certain** With BTC, we also know that a similar poll of users indicated that a 50% plurality supported the BIP101 blocksize plan when it was announced back in September. Because developers Mike Hearn and Gavin Andresen were unwilling to force a fork, the 50% of users never had the chance to voice their opinions with their money on the markets. While more recent polling is not available, it is reasonable to suggest that the plurality would have turned into a majority as some supporters of other the blocksize expansion plans in that poll came onboard. There clearly exists a significant proportion of users who would bid up the price of a large blocksize BTC fork today if one were released. At the same time, it seems that the ETH fork has caused many users to finally wake up and recognize that Bitcoin will remain stagnant and inferior unless they take matters into their own hands. For now, they are still mired in discussion at /r/btcfork. At some point, someone is finally going to end the debate and publish a fork client to put the choice to users. A precedent has been set that trading volume will be enormous, so exchanges would likely race to offer it for trading. If the fork has even a small chance of success, there will always be traders who buy it up the minute it is listed and try to convince others to do so, as happened with ETC. What would a successful fork look like? First, it would occur soon - instead of yet more discussion, someone will simply take the well-tested Bitcoin Unlimited or BIP101 and add a few lines of code to fork the chain at a specific block. Second, it won't modify the proof-of-work to a different algorithm - people who blame miners for the current problem should be looking at themselves, who are failing to provide an alternate option for miners to mine. Third, the fork will permanently resolve this problem - a temporary solution like a 2MB fork won't succeed in adversarial conditions because another fork with a larger size (perhaps created by the Core itself, to cause chaos) will come along and supplant it. Finally, it needs to resolve only this problem - the blocksize is the only issue in Bitcoin that has enough importance to be worth the risk, and adding other features like Segregated Witness can only turn away people who would otherwise support the fork. <br> **Potential outcomes** Now that we know that a fork is definitely going to come, it's worth discussing what will happen as a result. I review three possible outcomes below. In all of these outcomes, market forces and the actions of people involved will have a far greater impact on the result than the actual code in the fork. *Outcome A: Surge and collapse* One potential outcome is similar to what is happening with Ethereum Classic - an initial surge as proponents try to create an impression that the fork is taking over, and when they see momentum stall, they sell out and let the fork bleed down to a very low value. The probability of this outcome occurring with the new Bitcoin fork is lower than that of the old ETC fork, because there was a distinct dynamic in ETC of criminals having a lot to gain from its acceptance. That's why we continue to see paid ads and spam encouraging people to buy ETC, because the hackers are slowly leeching out the buy orders from people who respond to these advertisements. With Bitcoin, criminals don't stand to gain tens of millions of dollars by pumping up one fork over the other. In this outcome, as with the other, we would see exchanges offering both forks. Here, however, wallet providers would sit on the sidelines. Since many people use bitcoins through wallet providers, they probably wouldn't even know that a fork had occurred, limiting the success of the fork. It's difficult to see this result ending up in any way other than Bitcoin's slow death. Assuming that the fork was a serious attempt, the outcome would have demonstrated that the Bitcoin community is completely unable to come to any agreement whatsoever about moving forward. It implies that Segregated Witness, the Lightning Network, and any other solutions are also dead, because they too require a hard fork - and those hard forks will be far more risky and even more contentious. Remember, the default outcome for Bitcoin in the absence of at least one successful fork is death. The Bitcoin network is already close to unusuable, and is inferior to Ethereum in all ways except volatility. If a fork fails simply due to low community acceptance, a huge amount of time would have passed and it would all but certain that the next fork would also fail. *Outcome B: Immediate success* In this outcome, a fork is released and most members of the community quickly rally around it. Its price exceeds that of the old fork and a rapid changeover occurs. We would probably see a slow rise for a period of time, and then over the course of a few hours the forks will switch trading positions, with people holding on to the old fork losing 80% of their wealth. This outcome, like outcome A, hinges on the actions of wallet providers. Coinbase, in particular, controls 10% of bitcoin and has stated that they support a Bitcoin fork. Coinbase's refusal to support Ethereum Classic while they still released ETC for people to sell, is one of the key reasons why ETC failed to gain traction. Coinbase's switching to the new fork may be sufficient to turn the tide. Other providers, like Blockchain.info, would also play a pivotal role by declaring to uninformed users that the "official" fork is the new client. On the other hand, there are forces that make this outcome less likely than the other outcomes. Core developers, who have a lot of money at stake both in holdings and in their business models, would make public statements declaring that they will quit cryptocurrency rather than work on the new fork. Some people will trust them to follow through on their word, and see their contributions as irreplaceable. Furthermore, journalists often contact Core developers for comments on Bitcoin events without asking ordinary users as well, so the media narrative would be one-sided. theymos would use his control of the Bitcoin media to create an "insulated world" where people visiting his sites would be tricked into downloading the Core client, even if the majority of Bitcoin users have moved onto the new chain. These users would present a challenge to reach. They would download the Core client, visit theymos's linked "Core" wallet providers, and buy Core bitcoins. A stream of confused users would continue to prop up the Core's influence. Even if theymos himself doesn't become involved in outright scams, his misinformation will allow fraudsters to sell people lower-valued Core bitcoins at the higher new fork price and significantly damage Bitcoin's image. *Outcome C: Repeated forks and attacks* When previous Bitcoin clients were released, they were quickly subject to attacks from criminals who supported the status quo. It is reasonable to believe that a definite fork that does not require consensus would be subject to attacks even more massive than the previous attacks on the nodes that had not yet achieved the required consensus. In this outcome, a fork is released, but criminals conduct the largest DDoS attacks in the history of the Internet, shutting down nodes and exchanges that offer trading in the fork. In addition to DDoS, replay attacks are used to steal money from the new fork. Some people may spend large amounts of money to fill up the blocks on the new fork and procure miners to mine those transactions, using up disk space for the new chain if they can get those blocks transmitted in time. Theymos would attempt to seize control of more domains and media outlets associated with the fork by registering them or buying out existing owners. At the same time, some Core developers continue with their previous legal threats to deter people supporting the fork, or even file suits against them, tying them up in time-consuming and expensive litigation. The end result in this case would be that the fork's blockchain stalls and its price collapses. Then, the fork creators would address the issue the caused the fork to fail. For example, if the fork failed because paid-off miners attacked the chain and the difficulty rose too high, then a minor adjustment to the difficulty algorithm might be made. Then another fork would be attempted by the same or a different group, and this would happen again and again, throwing the Bitcoin world into chaos until Bitcoin is eclipsed by Ethereum. <br> **Factors determining the outcome** Astute readers will notice that, in this post and others, I repeatedly mention theymos as the key player responsible for the current Bitcoin deadlock. That's because the upcoming Bitcoin civil war will be determined by whoever can control the media narrative of what "Bitcoin" is. People listen to the media and use that information to move markets. It will be a battle between theymos and commercial wallet providers, and the winner will be whichever fork is considered as "Bitcoin" on the most websites and services. Exchanges will play little role because they will likely offer both coins, and miners will split hashrate between both forks at a ratio close to that of their prices. The ETH fork was resolved very quickly because influential people in ETH quickly announced that they considered ETH to be Ethereum. Vitalik Buterin declared that he would never support Ethereum Classic, even if ETC grew to become more valuable than ETH. His statement stabilized markets and wallet providers followed his lead, leaving ETC as a slowly declining sideshow for hacker wars and speculation. ETC's decline will continue now that Coinbase and the "white hat" DAOs have announced that millions of previously locked up coins will be made available for people to sell out. For BTC to fork successfully, someone will need to take a stand and back up his words with action. A huge bitcoin owner or wallet provider will need to place its business on the line and announce, like Buterin, that they will only support the new fork and will never return even if the fork falls significantly in value. There are only a few people who have the power to do that. Here's an incomplete list: * Craig Wright could sign a message with his keys and say so, since he is known to support an unlimited blocksize. If a threat isn't enough, he could simply place an impenetrable sell wall of 1m bitcoins at $10 or $50 on his unfavored fork. * Blockchain.info could change its entire website to work only with the new fork and ignore the old one. * Coinbase could follow up on its founders' posts and announce they will never provide services related to the old fork, and like ETC, return the other fork's coins to users for sale. * An ETF or trust could announce that its holdings will be valid only on the new fork. Unfortunately, the odds of any business taking a stand are low, because businesses are incentivized to earn short-term profit, not long-term returns. They are also inclined to avoid legal risk. Yet, there is almost no risk and it requires little effort for an ordinary person to release a version of an existing Bitcoin client that simply allows larger blocks. That is why I believe it most likely that Bitcoin will move into a phase of "fork wars" (outcome C), where people will continually try to fork the Bitcoin network, and major businesses will decline to take a stand. The result will be that Bitcoin will remain deadlocked and that people will become exposed to Ethereum, see how much faster and less expensive it is, and its use will overtake that of Bitcoin. If you are an investor, the outlook for Bitcoin is negative. In the unlikely event there is never a fork, other coins will continue to surpass it. If a fork succeeds, the total value of bitcoin will fall sharply during the changeover. If the multiple forks and attacks chaos scenario plays out, the networks will be grind to a halt, reminiscent of John Ringo's "Council Wars" series, where all the world's electricity is spent towards energy strikes between warring factions. No matter what happens, the price of bitcoin will fall. I still believe the total value of bitcoin will fall into the $200 range even in the best scenario, as previously predicted. <br> **Conclusion** It seems that every time that I post, I keep looking for reasons to be optimistic about the future of Bitcoin, and I just can't find them. In the 4.5 months since I made the original post, there has been absolutely no progress on the blocksize issue, the Chinese miners reneged on their agreement to fork, and Segregated Witness is delayed even more than I predicted it would be. Nobody has stepped forward to offer a fork, and communities like /r/btcfork are mired in endless discussion when what needs to be included is simple. Meanwhile, the Ethereum community chose legal legitimacy over an "anything goes" approach, which will attract the major corporations that are being turned away from Bitcoin due to its image. Ethereum is now so widely supported that it can, in just the past few weeks, be used to send value between people and exchanges interchangeably with bitcoin. Ethereum's transactions confirm 100 times more quickly at 1/100 the price. Ethereum's only major issue at present is its volatility, which is likely to decline as it gains adoption. It is the media that will determine what Bitcoin is and how it moves forward, not exchanges, miners, or even users. With Ethereum, the media sided with Vitalik Buterin. With Bitcoin, theymos owns most of the media. Whichever side controls the most media in the end will most likely win the Bitcoin civil war. The only way that a fork will win that war is if businesses band together and seize or drown out theymos's media control. I hope that Bitcoin users create a hard fork without miner consensus that eliminates the blocksize issue soon. But even if the fork succeeds, Bitcoin's odds of success are significantly overestimated by the prices in the current markets. Many people have not used Ethereum and they do not recognize how it has become a superior way to transfer value over the past two months, even disregarding its contractual features. The upcoming Bitcoin fork, which will happen one way or another, and which will be extremely ugly, is going to be a wakeup call to a lot of people, who are going to have to reexamine their beliefs that Bitcoin will remain the leading cryptocurrency. |
| json metadata | {"tags":["bitcoin","ethereum","classic","blocksize","fork"],"links":["http://forums.prohashing.com/viewtopic.php?f=11&t=717,"]} |
| parent author | |
| parent permlink | bitcoin |
| permlink | bitcoin-will-fork-soon-with-significant-consequences |
| title | Bitcoin will fork soon, with significant consequences |
| Transaction Info | Block #4046862/Trx fd6fd2e5b1d92ad8b9f3350a63e63fb09117e4ab |
View Raw JSON Data
{
"block": 4046862,
"op": [
"comment",
{
"author": "prohashing",
"body": "**Introduction**\n\nI've heard a lot about the Steem platform, so I decided to try posting on it for this one topic. I'm looking for a place where I can control my own content without it being at risk of deletion, and where there is generally a higher comment quality available than those seen at reddit. We'll see how it goes.\n\nToday, I thought it would be a good idea to review my earlier outlook on the future of Bitcoin and Ethereum, which was initially posted at http://forums.prohashing.com/viewtopic.php?f=11&t=782. In general, I believe that the predictions made earlier, despite being delayed by the Ethereum fork, will continue to play out. The major difference from my earlier predictions is that I had only considered an \"official\" fork supported by the Core, and didn't include the possibility of a fork initiated without prior consensus. I'm now pretty sure that Bitcoin will have a hostile, non-Core fork, but so much time has passed that I don't think it has a high probability of success because, as I'll show, the outcome will be determined by the media, which is controlled by theymos. Even if the fork beats the odds, the outlook in the short term is grim regardless.\n<br>\n**Ethereum provided a wakeup call**\n\nWhat has been preventing Bitcoin from forking seems to be that many people believe that miners control coins' destiny. As I pointed out at http://forums.prohashing.com/viewtopic.php?f=11&t=717, markets always pop up for both chains after a fork of a widely traded coin, because exchanges can make more profit that way. It's one of the reasons I've reiterated that the idea of creating a \"2MB\" fork has little chance of success. A temporary blocksize increase just increases the number of forks that are traded, causing confusion and confrontation.\n\nFurthermore, we know that hashrate follows price, not the other way around. Many people continue to rail against the Bitcoin Core developers and expect miners to revolt without providing them an alternative fork first where they can earn profit.\n\nWe saw the causality between hashrate and price in action with Ethereum Classic (ETC), which had almost no hashrate immediately after the fork. Then, investor Barry Silbert led the charge in pushing up its price through his articles and Twitter posts. People like me started mining it - not because I have any belief whatsoever that ETC will surpass ETH, but simply because there were buy orders that I could sell into. ETC mining was so profitable that I turned on a house full of miners, on one of the hottest summer days with temperatures around 85 degrees. We mine ETC and have our payouts auto-sold into ETH. Most of the ETC miners, like us, don't care about ETC; they just want to get rid of the coins so that they could make more profit. If you still have trouble believing that miners care only about money, consider that over 95% of the payout coins we issue at our pool occur in coins other than the coin that was mined.\n\nDespite so much hashrate being pointed towards ETC, the polls before the ETH fork indicated widespread support among users when weighted by holdings. It was pointless to ask ETH miners before the fork what their opinions were, because I've pointed out before that exchanges, not miners, have the power to decide these things. ETH will continue to be the canonical chain, and and ETC will remain a sideshow, but that doesn't mean that miners won't exploit ETC for profit while it lasts.\n<br>\n**A Bitcoin fork is certain**\n\nWith BTC, we also know that a similar poll of users indicated that a 50% plurality supported the BIP101 blocksize plan when it was announced back in September. Because developers Mike Hearn and Gavin Andresen were unwilling to force a fork, the 50% of users never had the chance to voice their opinions with their money on the markets. While more recent polling is not available, it is reasonable to suggest that the plurality would have turned into a majority as some supporters of other the blocksize expansion plans in that poll came onboard. There clearly exists a significant proportion of users who would bid up the price of a large blocksize BTC fork today if one were released.\n\nAt the same time, it seems that the ETH fork has caused many users to finally wake up and recognize that Bitcoin will remain stagnant and inferior unless they take matters into their own hands. For now, they are still mired in discussion at /r/btcfork. At some point, someone is finally going to end the debate and publish a fork client to put the choice to users. A precedent has been set that trading volume will be enormous, so exchanges would likely race to offer it for trading. If the fork has even a small chance of success, there will always be traders who buy it up the minute it is listed and try to convince others to do so, as happened with ETC.\n\nWhat would a successful fork look like? First, it would occur soon - instead of yet more discussion, someone will simply take the well-tested Bitcoin Unlimited or BIP101 and add a few lines of code to fork the chain at a specific block. Second, it won't modify the proof-of-work to a different algorithm - people who blame miners for the current problem should be looking at themselves, who are failing to provide an alternate option for miners to mine. Third, the fork will permanently resolve this problem - a temporary solution like a 2MB fork won't succeed in adversarial conditions because another fork with a larger size (perhaps created by the Core itself, to cause chaos) will come along and supplant it. Finally, it needs to resolve only this problem - the blocksize is the only issue in Bitcoin that has enough importance to be worth the risk, and adding other features like Segregated Witness can only turn away people who would otherwise support the fork.\n<br>\n**Potential outcomes**\n\nNow that we know that a fork is definitely going to come, it's worth discussing what will happen as a result. I review three possible outcomes below. In all of these outcomes, market forces and the actions of people involved will have a far greater impact on the result than the actual code in the fork.\n\n*Outcome A: Surge and collapse*\n\nOne potential outcome is similar to what is happening with Ethereum Classic - an initial surge as proponents try to create an impression that the fork is taking over, and when they see momentum stall, they sell out and let the fork bleed down to a very low value. The probability of this outcome occurring with the new Bitcoin fork is lower than that of the old ETC fork, because there was a distinct dynamic in ETC of criminals having a lot to gain from its acceptance. That's why we continue to see paid ads and spam encouraging people to buy ETC, because the hackers are slowly leeching out the buy orders from people who respond to these advertisements. With Bitcoin, criminals don't stand to gain tens of millions of dollars by pumping up one fork over the other.\n\nIn this outcome, as with the other, we would see exchanges offering both forks. Here, however, wallet providers would sit on the sidelines. Since many people use bitcoins through wallet providers, they probably wouldn't even know that a fork had occurred, limiting the success of the fork.\n\nIt's difficult to see this result ending up in any way other than Bitcoin's slow death. Assuming that the fork was a serious attempt, the outcome would have demonstrated that the Bitcoin community is completely unable to come to any agreement whatsoever about moving forward. It implies that Segregated Witness, the Lightning Network, and any other solutions are also dead, because they too require a hard fork - and those hard forks will be far more risky and even more contentious.\n\nRemember, the default outcome for Bitcoin in the absence of at least one successful fork is death. The Bitcoin network is already close to unusuable, and is inferior to Ethereum in all ways except volatility. If a fork fails simply due to low community acceptance, a huge amount of time would have passed and it would all but certain that the next fork would also fail.\n\n*Outcome B: Immediate success*\n\nIn this outcome, a fork is released and most members of the community quickly rally around it. Its price exceeds that of the old fork and a rapid changeover occurs. We would probably see a slow rise for a period of time, and then over the course of a few hours the forks will switch trading positions, with people holding on to the old fork losing 80% of their wealth.\n\nThis outcome, like outcome A, hinges on the actions of wallet providers. Coinbase, in particular, controls 10% of bitcoin and has stated that they support a Bitcoin fork. Coinbase's refusal to support Ethereum Classic while they still released ETC for people to sell, is one of the key reasons why ETC failed to gain traction. Coinbase's switching to the new fork may be sufficient to turn the tide. Other providers, like Blockchain.info, would also play a pivotal role by declaring to uninformed users that the \"official\" fork is the new client.\n\nOn the other hand, there are forces that make this outcome less likely than the other outcomes. Core developers, who have a lot of money at stake both in holdings and in their business models, would make public statements declaring that they will quit cryptocurrency rather than work on the new fork. Some people will trust them to follow through on their word, and see their contributions as irreplaceable. Furthermore, journalists often contact Core developers for comments on Bitcoin events without asking ordinary users as well, so the media narrative would be one-sided. theymos would use his control of the Bitcoin media to create an \"insulated world\" where people visiting his sites would be tricked into downloading the Core client, even if the majority of Bitcoin users have moved onto the new chain.\n\nThese users would present a challenge to reach. They would download the Core client, visit theymos's linked \"Core\" wallet providers, and buy Core bitcoins. A stream of confused users would continue to prop up the Core's influence. Even if theymos himself doesn't become involved in outright scams, his misinformation will allow fraudsters to sell people lower-valued Core bitcoins at the higher new fork price and significantly damage Bitcoin's image.\n\n*Outcome C: Repeated forks and attacks*\n\nWhen previous Bitcoin clients were released, they were quickly subject to attacks from criminals who supported the status quo. It is reasonable to believe that a definite fork that does not require consensus would be subject to attacks even more massive than the previous attacks on the nodes that had not yet achieved the required consensus.\n\nIn this outcome, a fork is released, but criminals conduct the largest DDoS attacks in the history of the Internet, shutting down nodes and exchanges that offer trading in the fork. In addition to DDoS, replay attacks are used to steal money from the new fork. Some people may spend large amounts of money to fill up the blocks on the new fork and procure miners to mine those transactions, using up disk space for the new chain if they can get those blocks transmitted in time. Theymos would attempt to seize control of more domains and media outlets associated with the fork by registering them or buying out existing owners.\n\nAt the same time, some Core developers continue with their previous legal threats to deter people supporting the fork, or even file suits against them, tying them up in time-consuming and expensive litigation.\n\nThe end result in this case would be that the fork's blockchain stalls and its price collapses. Then, the fork creators would address the issue the caused the fork to fail. For example, if the fork failed because paid-off miners attacked the chain and the difficulty rose too high, then a minor adjustment to the difficulty algorithm might be made. Then another fork would be attempted by the same or a different group, and this would happen again and again, throwing the Bitcoin world into chaos until Bitcoin is eclipsed by Ethereum.\n<br>\n**Factors determining the outcome**\n\nAstute readers will notice that, in this post and others, I repeatedly mention theymos as the key player responsible for the current Bitcoin deadlock. That's because the upcoming Bitcoin civil war will be determined by whoever can control the media narrative of what \"Bitcoin\" is. People listen to the media and use that information to move markets. It will be a battle between theymos and commercial wallet providers, and the winner will be whichever fork is considered as \"Bitcoin\" on the most websites and services. Exchanges will play little role because they will likely offer both coins, and miners will split hashrate between both forks at a ratio close to that of their prices.\n\nThe ETH fork was resolved very quickly because influential people in ETH quickly announced that they considered ETH to be Ethereum. Vitalik Buterin declared that he would never support Ethereum Classic, even if ETC grew to become more valuable than ETH. His statement stabilized markets and wallet providers followed his lead, leaving ETC as a slowly declining sideshow for hacker wars and speculation. ETC's decline will continue now that Coinbase and the \"white hat\" DAOs have announced that millions of previously locked up coins will be made available for people to sell out.\n\nFor BTC to fork successfully, someone will need to take a stand and back up his words with action. A huge bitcoin owner or wallet provider will need to place its business on the line and announce, like Buterin, that they will only support the new fork and will never return even if the fork falls significantly in value. There are only a few people who have the power to do that. Here's an incomplete list:\n\n* Craig Wright could sign a message with his keys and say so, since he is known to support an unlimited blocksize. If a threat isn't enough, he could simply place an impenetrable sell wall of 1m bitcoins at $10 or $50 on his unfavored fork.\n* Blockchain.info could change its entire website to work only with the new fork and ignore the old one.\n* Coinbase could follow up on its founders' posts and announce they will never provide services related to the old fork, and like ETC, return the other fork's coins to users for sale.\n* An ETF or trust could announce that its holdings will be valid only on the new fork.\n\nUnfortunately, the odds of any business taking a stand are low, because businesses are incentivized to earn short-term profit, not long-term returns. They are also inclined to avoid legal risk. Yet, there is almost no risk and it requires little effort for an ordinary person to release a version of an existing Bitcoin client that simply allows larger blocks. That is why I believe it most likely that Bitcoin will move into a phase of \"fork wars\" (outcome C), where people will continually try to fork the Bitcoin network, and major businesses will decline to take a stand. The result will be that Bitcoin will remain deadlocked and that people will become exposed to Ethereum, see how much faster and less expensive it is, and its use will overtake that of Bitcoin.\n\nIf you are an investor, the outlook for Bitcoin is negative. In the unlikely event there is never a fork, other coins will continue to surpass it. If a fork succeeds, the total value of bitcoin will fall sharply during the changeover. If the multiple forks and attacks chaos scenario plays out, the networks will be grind to a halt, reminiscent of John Ringo's \"Council Wars\" series, where all the world's electricity is spent towards energy strikes between warring factions. No matter what happens, the price of bitcoin will fall. I still believe the total value of bitcoin will fall into the $200 range even in the best scenario, as previously predicted.\n<br>\n**Conclusion**\n\nIt seems that every time that I post, I keep looking for reasons to be optimistic about the future of Bitcoin, and I just can't find them. In the 4.5 months since I made the original post, there has been absolutely no progress on the blocksize issue, the Chinese miners reneged on their agreement to fork, and Segregated Witness is delayed even more than I predicted it would be. Nobody has stepped forward to offer a fork, and communities like /r/btcfork are mired in endless discussion when what needs to be included is simple.\n\nMeanwhile, the Ethereum community chose legal legitimacy over an \"anything goes\" approach, which will attract the major corporations that are being turned away from Bitcoin due to its image. Ethereum is now so widely supported that it can, in just the past few weeks, be used to send value between people and exchanges interchangeably with bitcoin. Ethereum's transactions confirm 100 times more quickly at 1/100 the price. Ethereum's only major issue at present is its volatility, which is likely to decline as it gains adoption.\n\nIt is the media that will determine what Bitcoin is and how it moves forward, not exchanges, miners, or even users. With Ethereum, the media sided with Vitalik Buterin. With Bitcoin, theymos owns most of the media. Whichever side controls the most media in the end will most likely win the Bitcoin civil war. The only way that a fork will win that war is if businesses band together and seize or drown out theymos's media control.\n\nI hope that Bitcoin users create a hard fork without miner consensus that eliminates the blocksize issue soon. But even if the fork succeeds, Bitcoin's odds of success are significantly overestimated by the prices in the current markets. Many people have not used Ethereum and they do not recognize how it has become a superior way to transfer value over the past two months, even disregarding its contractual features. The upcoming Bitcoin fork, which will happen one way or another, and which will be extremely ugly, is going to be a wakeup call to a lot of people, who are going to have to reexamine their beliefs that Bitcoin will remain the leading cryptocurrency.",
"json_metadata": "{\"tags\":[\"bitcoin\",\"ethereum\",\"classic\",\"blocksize\",\"fork\"],\"links\":[\"http://forums.prohashing.com/viewtopic.php?f=11&t=717,\"]}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "bitcoin-will-fork-soon-with-significant-consequences",
"title": "Bitcoin will fork soon, with significant consequences"
}
],
"op_in_trx": 0,
"timestamp": "2016-08-13T13:10:12",
"trx_id": "fd6fd2e5b1d92ad8b9f3350a63e63fb09117e4ab",
"trx_in_block": 3,
"virtual_op": 0
}steemcreated a new account: @prohashing
steemcreated a new account: @prohashing
| active | {"account_auths":[],"key_auths":[["STM5yaAQ5WuuhP7AJgp9qCcHvkTabMSo23E5N9ezEWANbTRmiRSf8",1]],"weight_threshold":1} |
| creator | steem |
| fee | 3.000 STEEM |
| json metadata | |
| memo key | STM5CW99rE55MeopKcEgqbmnQSVeRZn7mJ7PCCLhuwyhuTfcoszwV |
| new account name | prohashing |
| owner | {"account_auths":[],"key_auths":[["STM5s8WVxBqDnxTF5kLqvVwg23mAfgbzTpKwCg9u2MvdJHN2L66zw",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM7kfU8P8R1bZhgP4Gu14Uz3JnnV6vnLyRgw3GcLwtbUzAmsKgWH",1]],"weight_threshold":1} |
| Transaction Info | Block #3601860/Trx 4e63e7b1e4cd51d0b169f0008e1557ed99e7b9a4 |
View Raw JSON Data
{
"block": 3601860,
"op": [
"account_create",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM5yaAQ5WuuhP7AJgp9qCcHvkTabMSo23E5N9ezEWANbTRmiRSf8",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"fee": "3.000 STEEM",
"json_metadata": "",
"memo_key": "STM5CW99rE55MeopKcEgqbmnQSVeRZn7mJ7PCCLhuwyhuTfcoszwV",
"new_account_name": "prohashing",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5s8WVxBqDnxTF5kLqvVwg23mAfgbzTpKwCg9u2MvdJHN2L66zw",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7kfU8P8R1bZhgP4Gu14Uz3JnnV6vnLyRgw3GcLwtbUzAmsKgWH",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2016-07-29T00:23:15",
"trx_id": "4e63e7b1e4cd51d0b169f0008e1557ed99e7b9a4",
"trx_in_block": 0,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress17.86%
{
"voting_manabar": {
"current_mana": 9949,
"last_update_time": 1471121373
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1469751795
},
"rc_account": {
"account": "prohashing",
"max_rc": "17708112004",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "17708112004",
"last_update_time": 1537887600
}
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM5s8WVxBqDnxTF5kLqvVwg23mAfgbzTpKwCg9u2MvdJHN2L66zw1/1
Active
Single Signature
Public Keys
STM5yaAQ5WuuhP7AJgp9qCcHvkTabMSo23E5N9ezEWANbTRmiRSf81/1
Posting
Single Signature
Public Keys
STM7kfU8P8R1bZhgP4Gu14Uz3JnnV6vnLyRgw3GcLwtbUzAmsKgWH1/1
Memo
STM5CW99rE55MeopKcEgqbmnQSVeRZn7mJ7PCCLhuwyhuTfcoszwV
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5s8WVxBqDnxTF5kLqvVwg23mAfgbzTpKwCg9u2MvdJHN2L66zw",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM5yaAQ5WuuhP7AJgp9qCcHvkTabMSo23E5N9ezEWANbTRmiRSf8",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7kfU8P8R1bZhgP4Gu14Uz3JnnV6vnLyRgw3GcLwtbUzAmsKgWH",
1
]
],
"weight_threshold": 1
},
"memo": "STM5CW99rE55MeopKcEgqbmnQSVeRZn7mJ7PCCLhuwyhuTfcoszwV"
}Witness Votes
0 / 30
No active witness votes.
[]