 A few Miners might be supporting the new Token
| author | rafaelzauner |
|---|---|
| permlink | possible-hard-fork-segwit2x |
| category | news |
| json_metadata | {"tags":["news","bitcoin","cryptocurrency","hardfork"],"image":["https://steemitimages.com/DQmcKR3FzZdJv6SSvHzMBENYHoDMkFYkBxeDxTVCDxEEHcE/Hard%20Fork%20Segwit2x.jpg"],"app":"steemit/0.1","format":"markdown"} |
| created | 2017-11-17 14:33:15 |
| last_update | 2017-11-17 14:33:15 |
| depth | 0 |
| children | 2 |
| last_payout | 2017-11-24 14:33:15 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.344 HBD |
| curator_payout_value | 0.019 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 175 |
| author_reputation | 29,792,485,342,828 |
| root_title | "Possible Hard Fork Segwit2x" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 20,684,302 |
| net_rshares | 168,610,258,709 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| livingfree | 0 | 62,864,854,238 | 1% | ||
| rafaelzauner | 0 | 71,582,556,143 | 100% | ||
| yzomri | 0 | 366,699,537 | 100% | ||
| detlev | 0 | 5,813,751,553 | 5% | ||
| neiraurdaneta | 0 | 6,125,696,969 | 100% | ||
| muler | 0 | 573,232,361 | 100% | ||
| vykislya | 0 | 586,569,491 | 100% | ||
| ridaazhar | 0 | 234,651,521 | 100% | ||
| kuksa | 0 | 1,103,660,973 | 100% | ||
| tiparov | 0 | 580,534,852 | 100% | ||
| pezhuzesho | 0 | 584,167,007 | 100% | ||
| infidel1258 | 0 | 16,609,660,034 | 100% | ||
| iren007 | 0 | 661,590,557 | 100% | ||
| mdrahamatkhan | 0 | 922,633,473 | 100% |
I saw a notice of this in my email from Coinbase. They made it seemas if they expect it to be unsafe in terms of splitting, I guess because of no replay protection. But in truth I dont fully understand the risks associated with the split.
| author | infidel1258 |
|---|---|
| permlink | re-rafaelzauner-possible-hard-fork-segwit2x-20171117t143902939z |
| category | news |
| json_metadata | {"tags":["news"],"app":"steemit/0.1"} |
| created | 2017-11-17 14:39:06 |
| last_update | 2017-11-17 14:39:06 |
| depth | 1 |
| children | 1 |
| last_payout | 2017-11-24 14:39:06 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 238 |
| author_reputation | 76,702,759,028,442 |
| root_title | "Possible Hard Fork Segwit2x" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 20,684,858 |
| net_rshares | 0 |
You are right with the no replay. I've read a few things a while back, hard to remember everything I read. But one two things involve the mix up of names. If they call the new Chain Token Bitcoin there will definitely be a lot of confusion, but sending the new Token could also cause that your Original Bitcoins disappear with the new ones and there should be quite a price difference. But I'm sure there are others that can explain it better then I did.
| author | rafaelzauner |
|---|---|
| permlink | re-infidel1258-re-rafaelzauner-possible-hard-fork-segwit2x-20171117t145505154z |
| category | news |
| json_metadata | {"tags":["news"],"app":"steemit/0.1"} |
| created | 2017-11-17 14:55:06 |
| last_update | 2017-11-17 14:55:06 |
| depth | 2 |
| children | 0 |
| last_payout | 2017-11-24 14:55:06 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 454 |
| author_reputation | 29,792,485,342,828 |
| root_title | "Possible Hard Fork Segwit2x" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 20,686,272 |
| net_rshares | 0 |
hiveblocks