VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS61.36%
Net Worth
0.400USD
STEEM
0.000STEEM
SBD
0.024SBD
Own SP
7.182SP
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 | 7.182SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 7.182SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.024SBD | 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": "11695.203920 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.024 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | steves |
| id | 45200 |
| rank | 166,936 |
| reputation | 1511099072 |
| created | 2016-08-03T22:09:54 |
| recovery_account | steem |
| proxy | None |
| post_count | 7 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2016-10-06T10:51:03 |
| last_root_post | 2016-10-06T10:51:03 |
| last_vote_time | 2016-10-06T10:51:03 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,950 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.024 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 11695.203920 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 | 2016-08-05T07:10:39 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 45200,
"name": "steves",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8in5nErFp8U3GeR4cnJmfyMBucP9FNsMtotiREDU2P8fdpTDzd",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5u4cZvojzz1w8Xu25ahvotsxUXSimAZeG18cBUV5oU8BJk3vPr",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5tCsx2Ez5wYD5HezG9EbHKpmfdE8Qo18FH2F4mZnksuPekgaEb",
1
]
]
},
"memo_key": "STM5rWVyebBFXDixbYiBMgkHbGKuJAPWw7EmyoPKYsrgsPVwBoY8g",
"json_metadata": "",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2016-08-03T22:09:54",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 7,
"can_vote": true,
"voting_manabar": {
"current_mana": 9950,
"last_update_time": 1475751063
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1470262194
},
"voting_power": 9950,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.024 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2016-08-05T07:10:39",
"sbd_last_interest_payment": "2016-08-05T07:10:39",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "11695.203920 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 23,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2016-10-06T10:51:03",
"last_root_post": "2016-10-06T10:51:03",
"last_vote_time": "2016-10-06T10:51:03",
"post_bandwidth": 10000,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 1511099072,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 166936
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2019/08/03 23:31:48
2019/08/03 23:31:48
| parent author | steves |
| parent permlink | segregated-witness-s-soft-fork-and-a-vote-of-no-confidence |
| author | steemitboard |
| permlink | steemitboard-notify-steves-20190803t233147000z |
| title | |
| body | Congratulations @steves! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@steves/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/@steves) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=steves)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #35242873/Trx 537140c68edb7851d81d82e712f53fe1677aa931 |
View Raw JSON Data
{
"trx_id": "537140c68edb7851d81d82e712f53fe1677aa931",
"block": 35242873,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-08-03T23:31:48",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "segregated-witness-s-soft-fork-and-a-vote-of-no-confidence",
"author": "steemitboard",
"permlink": "steemitboard-notify-steves-20190803t233147000z",
"title": "",
"body": "Congratulations @steves! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@steves/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/@steves) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=steves)_</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\"]}"
}
]
}2017/08/03 22:55:57
2017/08/03 22:55:57
| parent author | steves |
| parent permlink | segregated-witness-s-soft-fork-and-a-vote-of-no-confidence |
| author | steemitboard |
| permlink | steemitboard-notify-steves-20170803t225559000z |
| title | |
| body | Congratulations @steves! You have received a personal award! [](http://steemitboard.com/@steves) Happy Birthday - 1 Year on Steemit Happy Birthday - 1 Year on Steemit Click on the badge to view your own Board of Honor on SteemitBoard. For more information about this award, click [here](https://steemit.com/steemitboard/@steemitboard/steemitboard-update-8-happy-birthday) > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #14263810/Trx caa8502a7446c89aecf4f3780745967e5b1c0983 |
View Raw JSON Data
{
"trx_id": "caa8502a7446c89aecf4f3780745967e5b1c0983",
"block": 14263810,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-03T22:55:57",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "segregated-witness-s-soft-fork-and-a-vote-of-no-confidence",
"author": "steemitboard",
"permlink": "steemitboard-notify-steves-20170803t225559000z",
"title": "",
"body": "Congratulations @steves! You have received a personal award!\n\n[](http://steemitboard.com/@steves) Happy Birthday - 1 Year on Steemit Happy Birthday - 1 Year on Steemit\nClick on the badge to view your own Board of Honor on SteemitBoard.\n\nFor more information about this award, click [here](https://steemit.com/steemitboard/@steemitboard/steemitboard-update-8-happy-birthday)\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}maxtill94replied to @steves / re-steves-btc12-com-20170721t070405980z2017/07/21 07:04:06
maxtill94replied to @steves / re-steves-btc12-com-20170721t070405980z
2017/07/21 07:04:06
| parent author | steves |
| parent permlink | btc12-com |
| author | maxtill94 |
| permlink | re-steves-btc12-com-20170721t070405980z |
| title | |
| body | 你的文已看完,我已申请关注了,我也写了第一篇文,有空请阅下~ 个人认为NEVERDIE ICO 也不错,在我个人热帖里,Neverdie.com https://steemit.com/cn/@maxtill94/neverdie-ico-erc20-ico |
| json metadata | {"tags":["cn"],"links":["https://steemit.com/cn/@maxtill94/neverdie-ico-erc20-ico"],"app":"steemit/0.1"} |
| Transaction Info | Block #13870652/Trx 6354be34adead359f8a9b1b363b8b2b521bb9d2e |
View Raw JSON Data
{
"trx_id": "6354be34adead359f8a9b1b363b8b2b521bb9d2e",
"block": 13870652,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-21T07:04:06",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "btc12-com",
"author": "maxtill94",
"permlink": "re-steves-btc12-com-20170721t070405980z",
"title": "",
"body": "你的文已看完,我已申请关注了,我也写了第一篇文,有空请阅下~\n个人认为NEVERDIE ICO 也不错,在我个人热帖里,Neverdie.com\nhttps://steemit.com/cn/@maxtill94/neverdie-ico-erc20-ico",
"json_metadata": "{\"tags\":[\"cn\"],\"links\":[\"https://steemit.com/cn/@maxtill94/neverdie-ico-erc20-ico\"],\"app\":\"steemit/0.1\"}"
}
]
}andre-agerupvoted (100.00%) @steves / segregated-witness-s-soft-fork-and-a-vote-of-no-confidence
andre-agerupvoted (100.00%) @steves / segregated-witness-s-soft-fork-and-a-vote-of-no-confidence
| voter | andre-ager |
| author | steves |
| permlink | segregated-witness-s-soft-fork-and-a-vote-of-no-confidence |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5593047/Trx dd33dc1bc3f0f193bdea05e6b00a9ef6d8c42980 |
View Raw JSON Data
{
"trx_id": "dd33dc1bc3f0f193bdea05e6b00a9ef6d8c42980",
"block": 5593047,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-10-06T11:24:00",
"op": [
"vote",
{
"voter": "andre-ager",
"author": "steves",
"permlink": "segregated-witness-s-soft-fork-and-a-vote-of-no-confidence",
"weight": 10000
}
]
}stevesupvoted (100.00%) @steves / segregated-witness-s-soft-fork-and-a-vote-of-no-confidence
stevesupvoted (100.00%) @steves / segregated-witness-s-soft-fork-and-a-vote-of-no-confidence
| voter | steves |
| author | steves |
| permlink | segregated-witness-s-soft-fork-and-a-vote-of-no-confidence |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5592388/Trx 989d72ed1d88919d6ba4e0fb6b99681d1804fb8c |
View Raw JSON Data
{
"trx_id": "989d72ed1d88919d6ba4e0fb6b99681d1804fb8c",
"block": 5592388,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-10-06T10:51:03",
"op": [
"vote",
{
"voter": "steves",
"author": "steves",
"permlink": "segregated-witness-s-soft-fork-and-a-vote-of-no-confidence",
"weight": 10000
}
]
}stevespublished a new post: segregated-witness-s-soft-fork-and-a-vote-of-no-confidence
stevespublished a new post: segregated-witness-s-soft-fork-and-a-vote-of-no-confidence
| parent author | |
| parent permlink | programming |
| author | steves |
| permlink | segregated-witness-s-soft-fork-and-a-vote-of-no-confidence |
| title | Segregated Witness's soft fork and a vote of no confidence |
| body | Hey, The Core's impending release of Segregated Witness represents a turning point for the Bitcoin industry. While the blocksize limitation has continued to hold back the currency for a year, until now there has never been a concrete deadline for people opposed to the Core leadership's roadmap. Segregated Witness changes that, as it represents a fundamental shift to how Bitcoin will operate moving forward. The promise of the proposed "soft fork" to Segregated Witness is that existing nodes will not be kicked off the network and will continue to run. While that sounds great in promise, in reality every programmer writes "assert" statements on a regular basis to create explicit exceptions when something goes wrong. One of the worst possible events that can happen to software is that it starts to behave differently and do bad things because nobody is ever notified that something has gone wrong. By activating through a soft fork, the deployment of Segregated Witness will break a large proportion of existing software. Furthermore, the additional complexity will reduce developer productivity for years to come. In this article, I will explain why Segregated Witness has significant disadvantages, and why the soft fork approach to rollout will have disproportionate consequences to regular users. I will encourage others to take a stand against the Core's "soft-fork" decision by escalating the soft fork to a hard fork, which will take the decision out of miners' hands and to place it into those of users and investors. I will point out that the window of opportunity to do so has been reduced to weeks or a few months at best. At a high level, Segregated Witness is an addition to the Bitcoin protocol that separates data into two formats: the existing blocks and a "witness" segment. Transactions in the existing blocks serve as pointers to the detailed data in the witness segments. For example, a transaction with many recipients may take up less space in the existing blocks because the signatures in the existing blocks don't describe everything that the transaction represents. Proponents of Segregated Witness point out a number of advantages to the scheme. For one, it solves the "transaction malleability" issue, which makes it difficult to rely on a transaction hash to track unconfirmed transactions. Supporters also believe that more data can be fit onto the blockchain with Segregated Witness, because although the proposal does not eliminate the 1MB transaction limit, it reduces the size of the data present in the original 1MB blocks. The Core's official statement suggests that future development will be easier because of the way that reserved operator statements are handled in the Bitcoin scripting language. Unfortunately, however, I believe that the drawbacks to Segregated Witness outnumber its benefits. I'll list the technical drawbacks first, and then focus on the deployment method, which is its largest drawback. First, it's important to examine the validity of increasing the number of transactions in a block. While Segregated Witness does indeed reduce space utilization in the existing 1MB blocks, all of the data describing the transactions still needs to be received and included in the blockchain. In Segregated Witness, that witness data is received separately, so a 1MB block can contain 100KB of additional transaction witness data, for a total of 1.1MB of data. It's not as simple as that, though: the transactions actually use more bandwidth than they would if the blocksize were simply increased. View this as two Excel spreadsheets - when two spreadsheets with different data about a list of cars exist, the license plate number needs to be present on both the accident report and on the inspection report. If one created a combined "accident/inspection report," then the license plate only needs to be listed once with both pieces of data below it. In Segregated Witness, this duplication of the transaction identifier results in extra data. Plus, as I pointed out in March, Segregated Witness only increases transaction space if most Bitcoin transactions are complicated and people use it. Simple transactions that send one input to one output do not significantly increase block capacity with Segregated Witness. People also have to use Segregated Witness for anyone to benefit, and soft-fork adoption is likely to happen slowly or not at all. Second, Segregated Witness breaks much of the existing software deployed across the cryptocurrency industry. Block explorers are likely to be one of the most noticeable losses - as soon as the first Segregated Witness transaction is mined, many explorers would go offline. Having created block explorers for 200 coins myself, I assert that handling non-standard transactions is an extremely complex task. Coin clients don't keep track of balances for all addresses, so the only way to do that is to rewrite your software to understand the new data format, and then reindex the entire blockchain. In our case, it took over three months before we were able to get a successful run of our block explorer code where there were no math errors or missing transactions. Because the transactions are summed since the beginning of time, bugs don't appear until days of indexing have occurred, and since it isn't apparent where the sum is wrong, debugging consists largely of guessing. The only way to confirm that the new code works is to delete the database and reindex again - and that assumes that one knows that the totals are right. We have 1.1TB of block explorer data for coins whose blockchains total about twice the size of bitcoin's, so that means constant reindexing of 500GB of linked and summarized data. Many analysis services would fail (or worse, return erroneous data) because developers can't afford the time to upgrade them, leading to increased centralization of many critical Bitcoin functions. But it's not just block explorers that would suffer. Exchanges, which often have custom implementations of the Bitcoin client, would need to modify production code that has in some cases been working for years with no issues. With huge amounts of money at stake, well-managed companies don't just change code in production without extensive testing. The cost to do this upgrade will be enormous, and that's why I believe that uptake of Segregated Witness would be far less than the Core projects. The companies that make the largest transactions (which offer the greatest benefit to Segregated Witness) are the most likely to judge that the cost of higher transaction fees is less than the cost of paying someone to write new code plus accepting the risk of a catastrophic loss. Third, even if all services were to be upgraded, the community would still face a burden of increased complexity that would hinder development. Instead of understanding and managing one single and simpler blockchain, developers would need to work with both the main blockchain and the witness data. Cryptocurrency is such a complex field that the ability of developers to get started is a serious concern. The system is approaching such complexity that no one person can understand every part of it, and adding Segregated Witness to the mix increases training time and will discourage a greater proportion of potential developers. Bitcoin already has a shortage of competent and (especially) of ethical developers, and that pool becomes even smaller as the system grows more complex. Fourth, even if every single developer sees the additional complexity as a small challenge that can be easily overcome, once Segregated Witness is deployed, it is deployed forever. That means that every change to every client will henceforth need to be tested against both the existing blockchain code and also against the witness data. Is it really worth slowing down development, permanently, for improvements that are relatively minor? The Core leadership estimates that there are over 3300 lines in additional tests required to maintain the stability of Segregated Witness. All of these tests need to be run and updated with every change, and there will be issues found that require additional tests that do not currently exist. Given that one of the two main selling points of Segregated Witness in the official Core statement is to increase the number of transactions contained in blocks, the few lines that need to be changed to provide for 32MB blocks pale in comparison to the 4824 lines of implementation and test code required for Segregated Witness. Fifth, it is true that Segregated Witness solves some problems that have been with Bitcoin since the beginning. For example, the "transaction malleability" problem is eliminated. However, the fixes that Segregated Witness provides can be accomplished in simpler ways. Bitcoin Unlimited pioneered Xtreme Thinblocks many months ago, a change which significantly reduces the odds that block processing will be delayed by requiring the receipt of a lot of data. Reducing block validation times can be accomplished with moral_agent's "alternating blocks" arrangement, which is a better way of addressing that problem. Segregated Witness also introduces fixes to problems that don't really need fixing. Thousands of cryptocurrencies have functioned just fine with malleable transactions for seven years. When handled correctly, malleability will never result in a loss of money. The Core suggests that fixing transaction malleability makes smart contracts easier on Bitcoin, which is also true - but there is already a coin that does smart contracts far better than Bitcoin. Core leadership should be focusing on what Bitcoin does best - sending and receiving money. Another reason to address transaction malleability now is to allow the Lightning Network to be deployed on Bitcoin - but the deployment of the Lightning Network will never happen. theymos, intentionally or not, ensured that the Lightning Network is dead on arrival when he split the Bitcoin community in August 2015. The stalemate and animosity he created on the blocksize debate will surely extend to the Lightning Network as well. The Core has been adding features since version 0.12 without taking the time to analyze whether anyone is actually using them. The slow uptake of that version and subsequent releases implies that people do not see a compelling reason to upgrade. Rather than hosting ridiculous weekly development meetings where the blocksize problem is never discussed, the Core should be performing cost-benefit analyses. The central question for any feature should be as follows: will this be used by enough people that the lost time in supporting it outweighs the delay in finding a fix for the blocksize problem? It isn't clear that the problems Segregated Witness is intended to fix have been analyzed to see if users even care about fixing them. Finally, the most important reason to be concerned about Segregated Witness is also the most catastrophic effect of it: that the Core is considering activating the change as a soft fork. A soft fork is the coward's way of pushing changes upon people who may not want them. In a soft fork, miners will be making an economic decision which does not affect them. They won't be paying developers to fix all the broken software, they won't have to worry about the risk of losing money from changing production code that has run fine for years, they don't care whether anyone will even use the features that Segregated Witness provides, and they won't even bother to notify people who don't check forums every day and therefore don't know a change is coming. They do not have the right to make that decision; the people who have to pay for the consequences do. There is an alternate path forward: a hard fork, which allows the people who have to pay for the changes to make the decision of whether the changes are worth it. That is why I believe that the community should escalate Segregated Witness to a hard fork. Exchanges should be contacted and at least one of them will agree to list the existing "simple" blockchain. The only large challenge is getting someone who has enough time to make the small change to Bitcoin Core or Bitcoin Unlimited to fork the network at the activation threshold, and who will do so without running out of time through endless discussion or jeopardizing the fork by including other things. The change can be a simple commandline argument that uses the Segregated Witness code itself to reject blocks with witness data. The btcfork reddit subreddit is an example of what is not needed here; the solution is obvious enough that no discussion is needed. One of the clear benefits of taking a stand on Segregated Witness, rather than on the blocksize itself, is because this issue allows people to cast an vote of no confidence independently of their stances on the highly contested blocksize issue. A fork here also prevents having to frame a later trivial change as a no-confidence fork. The rejection of the Segregated Witness fork, or even a prolonged battle that leads to fork acceptance, would send a clear message to the Core that the feature creep they have been introducing to Bitcoin since version 0.12 is not wanted or needed. It would refocus all attention to achieving a permanent and immediate resolution to the one single problem that is holding back the adoption of cryptocurrency: the limited blocksize of Bitcoin. It would teach the Core leadership that software doesn't get better if you just add lots of features that people don't use. The message would be the following: miners and developers exist to serve the software's users. Get on board with what the community has chosen, or get out. In conclusion, Segregated Witness has some benefits. A lot of people worked hard on it. It probably has a place somewhere in the cryptocurrency industry. The Segregated Witness hard fork may result in a majority adopting it. If a majority of users stick with the existing code, then Core developers who support Segregated Witness will still be able to use it on the less valuable fork, just as a minority of Ethereum users decided to go their separate way and both communities are largely fine with that decision. A soft fork places the decisionmaking authority in the hands of miners who will be unaffected by the economic consequences of that decision. Users should make that decision instead. If no action is taken before a soft fork, then everyone is stuck with the changes forever, and even a later successful fork to an unlimited blocksize will then have to deal with all the Segregated Witness transactions. If anyone is ever going to make a statement that Bitcoin exists for its users, not its developers or miners, it is time to put Segregated Witness to the test of a hard fork..... Thanks, @steves |
| json metadata | {"tags":["programming"],"users":["steves"]} |
| Transaction Info | Block #5592388/Trx 989d72ed1d88919d6ba4e0fb6b99681d1804fb8c |
View Raw JSON Data
{
"trx_id": "989d72ed1d88919d6ba4e0fb6b99681d1804fb8c",
"block": 5592388,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-10-06T10:51:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "programming",
"author": "steves",
"permlink": "segregated-witness-s-soft-fork-and-a-vote-of-no-confidence",
"title": "Segregated Witness's soft fork and a vote of no confidence",
"body": "Hey, \nThe Core's impending release of Segregated Witness represents a turning point for the Bitcoin industry. While the blocksize limitation has continued to hold back the currency for a year, until now there has never been a concrete deadline for people opposed to the Core leadership's roadmap. Segregated Witness changes that, as it represents a fundamental shift to how Bitcoin will operate moving forward.\n\nThe promise of the proposed \"soft fork\" to Segregated Witness is that existing nodes will not be kicked off the network and will continue to run. While that sounds great in promise, in reality every programmer writes \"assert\" statements on a regular basis to create explicit exceptions when something goes wrong. One of the worst possible events that can happen to software is that it starts to behave differently and do bad things because nobody is ever notified that something has gone wrong.\n\nBy activating through a soft fork, the deployment of Segregated Witness will break a large proportion of existing software. Furthermore, the additional complexity will reduce developer productivity for years to come. In this article, I will explain why Segregated Witness has significant disadvantages, and why the soft fork approach to rollout will have disproportionate consequences to regular users. I will encourage others to take a stand against the Core's \"soft-fork\" decision by escalating the soft fork to a hard fork, which will take the decision out of miners' hands and to place it into those of users and investors. I will point out that the window of opportunity to do so has been reduced to weeks or a few months at best.\n\nAt a high level, Segregated Witness is an addition to the Bitcoin protocol that separates data into two formats: the existing blocks and a \"witness\" segment. Transactions in the existing blocks serve as pointers to the detailed data in the witness segments. For example, a transaction with many recipients may take up less space in the existing blocks because the signatures in the existing blocks don't describe everything that the transaction represents.\n\nProponents of Segregated Witness point out a number of advantages to the scheme. For one, it solves the \"transaction malleability\" issue, which makes it difficult to rely on a transaction hash to track unconfirmed transactions. Supporters also believe that more data can be fit onto the blockchain with Segregated Witness, because although the proposal does not eliminate the 1MB transaction limit, it reduces the size of the data present in the original 1MB blocks. The Core's official statement suggests that future development will be easier because of the way that reserved operator statements are handled in the Bitcoin scripting language.\n\nUnfortunately, however, I believe that the drawbacks to Segregated Witness outnumber its benefits. I'll list the technical drawbacks first, and then focus on the deployment method, which is its largest drawback.\n\nFirst, it's important to examine the validity of increasing the number of transactions in a block. While Segregated Witness does indeed reduce space utilization in the existing 1MB blocks, all of the data describing the transactions still needs to be received and included in the blockchain. In Segregated Witness, that witness data is received separately, so a 1MB block can contain 100KB of additional transaction witness data, for a total of 1.1MB of data. It's not as simple as that, though: the transactions actually use more bandwidth than they would if the blocksize were simply increased.\n\nView this as two Excel spreadsheets - when two spreadsheets with different data about a list of cars exist, the license plate number needs to be present on both the accident report and on the inspection report. If one created a combined \"accident/inspection report,\" then the license plate only needs to be listed once with both pieces of data below it. In Segregated Witness, this duplication of the transaction identifier results in extra data.\n\nPlus, as I pointed out in March, Segregated Witness only increases transaction space if most Bitcoin transactions are complicated and people use it. Simple transactions that send one input to one output do not significantly increase block capacity with Segregated Witness. People also have to use Segregated Witness for anyone to benefit, and soft-fork adoption is likely to happen slowly or not at all.\n\nSecond, Segregated Witness breaks much of the existing software deployed across the cryptocurrency industry. Block explorers are likely to be one of the most noticeable losses - as soon as the first Segregated Witness transaction is mined, many explorers would go offline. Having created block explorers for 200 coins myself, I assert that handling non-standard transactions is an extremely complex task. Coin clients don't keep track of balances for all addresses, so the only way to do that is to rewrite your software to understand the new data format, and then reindex the entire blockchain.\n\nIn our case, it took over three months before we were able to get a successful run of our block explorer code where there were no math errors or missing transactions. Because the transactions are summed since the beginning of time, bugs don't appear until days of indexing have occurred, and since it isn't apparent where the sum is wrong, debugging consists largely of guessing. The only way to confirm that the new code works is to delete the database and reindex again - and that assumes that one knows that the totals are right. We have 1.1TB of block explorer data for coins whose blockchains total about twice the size of bitcoin's, so that means constant reindexing of 500GB of linked and summarized data. Many analysis services would fail (or worse, return erroneous data) because developers can't afford the time to upgrade them, leading to increased centralization of many critical Bitcoin functions.\n\nBut it's not just block explorers that would suffer. Exchanges, which often have custom implementations of the Bitcoin client, would need to modify production code that has in some cases been working for years with no issues. With huge amounts of money at stake, well-managed companies don't just change code in production without extensive testing. The cost to do this upgrade will be enormous, and that's why I believe that uptake of Segregated Witness would be far less than the Core projects. The companies that make the largest transactions (which offer the greatest benefit to Segregated Witness) are the most likely to judge that the cost of higher transaction fees is less than the cost of paying someone to write new code plus accepting the risk of a catastrophic loss.\n\nThird, even if all services were to be upgraded, the community would still face a burden of increased complexity that would hinder development. Instead of understanding and managing one single and simpler blockchain, developers would need to work with both the main blockchain and the witness data.\n\nCryptocurrency is such a complex field that the ability of developers to get started is a serious concern. The system is approaching such complexity that no one person can understand every part of it, and adding Segregated Witness to the mix increases training time and will discourage a greater proportion of potential developers. Bitcoin already has a shortage of competent and (especially) of ethical developers, and that pool becomes even smaller as the system grows more complex.\n\nFourth, even if every single developer sees the additional complexity as a small challenge that can be easily overcome, once Segregated Witness is deployed, it is deployed forever. That means that every change to every client will henceforth need to be tested against both the existing blockchain code and also against the witness data. Is it really worth slowing down development, permanently, for improvements that are relatively minor? The Core leadership estimates that there are over 3300 lines in additional tests required to maintain the stability of Segregated Witness. All of these tests need to be run and updated with every change, and there will be issues found that require additional tests that do not currently exist.\n\nGiven that one of the two main selling points of Segregated Witness in the official Core statement is to increase the number of transactions contained in blocks, the few lines that need to be changed to provide for 32MB blocks pale in comparison to the 4824 lines of implementation and test code required for Segregated Witness.\n\nFifth, it is true that Segregated Witness solves some problems that have been with Bitcoin since the beginning. For example, the \"transaction malleability\" problem is eliminated. However, the fixes that Segregated Witness provides can be accomplished in simpler ways. Bitcoin Unlimited pioneered Xtreme Thinblocks many months ago, a change which significantly reduces the odds that block processing will be delayed by requiring the receipt of a lot of data. Reducing block validation times can be accomplished with moral_agent's \"alternating blocks\" arrangement, which is a better way of addressing that problem.\n\nSegregated Witness also introduces fixes to problems that don't really need fixing. Thousands of cryptocurrencies have functioned just fine with malleable transactions for seven years. When handled correctly, malleability will never result in a loss of money. The Core suggests that fixing transaction malleability makes smart contracts easier on Bitcoin, which is also true - but there is already a coin that does smart contracts far better than Bitcoin. Core leadership should be focusing on what Bitcoin does best - sending and receiving money.\n\nAnother reason to address transaction malleability now is to allow the Lightning Network to be deployed on Bitcoin - but the deployment of the Lightning Network will never happen. theymos, intentionally or not, ensured that the Lightning Network is dead on arrival when he split the Bitcoin community in August 2015. The stalemate and animosity he created on the blocksize debate will surely extend to the Lightning Network as well.\n\nThe Core has been adding features since version 0.12 without taking the time to analyze whether anyone is actually using them. The slow uptake of that version and subsequent releases implies that people do not see a compelling reason to upgrade. Rather than hosting ridiculous weekly development meetings where the blocksize problem is never discussed, the Core should be performing cost-benefit analyses. The central question for any feature should be as follows: will this be used by enough people that the lost time in supporting it outweighs the delay in finding a fix for the blocksize problem? It isn't clear that the problems Segregated Witness is intended to fix have been analyzed to see if users even care about fixing them.\n\nFinally, the most important reason to be concerned about Segregated Witness is also the most catastrophic effect of it: that the Core is considering activating the change as a soft fork. A soft fork is the coward's way of pushing changes upon people who may not want them. In a soft fork, miners will be making an economic decision which does not affect them. They won't be paying developers to fix all the broken software, they won't have to worry about the risk of losing money from changing production code that has run fine for years, they don't care whether anyone will even use the features that Segregated Witness provides, and they won't even bother to notify people who don't check forums every day and therefore don't know a change is coming. They do not have the right to make that decision; the people who have to pay for the consequences do.\n\nThere is an alternate path forward: a hard fork, which allows the people who have to pay for the changes to make the decision of whether the changes are worth it. That is why I believe that the community should escalate Segregated Witness to a hard fork. Exchanges should be contacted and at least one of them will agree to list the existing \"simple\" blockchain. The only large challenge is getting someone who has enough time to make the small change to Bitcoin Core or Bitcoin Unlimited to fork the network at the activation threshold, and who will do so without running out of time through endless discussion or jeopardizing the fork by including other things. The change can be a simple commandline argument that uses the Segregated Witness code itself to reject blocks with witness data. The btcfork reddit subreddit is an example of what is not needed here; the solution is obvious enough that no discussion is needed.\n\nOne of the clear benefits of taking a stand on Segregated Witness, rather than on the blocksize itself, is because this issue allows people to cast an vote of no confidence independently of their stances on the highly contested blocksize issue. A fork here also prevents having to frame a later trivial change as a no-confidence fork. The rejection of the Segregated Witness fork, or even a prolonged battle that leads to fork acceptance, would send a clear message to the Core that the feature creep they have been introducing to Bitcoin since version 0.12 is not wanted or needed. It would refocus all attention to achieving a permanent and immediate resolution to the one single problem that is holding back the adoption of cryptocurrency: the limited blocksize of Bitcoin. It would teach the Core leadership that software doesn't get better if you just add lots of features that people don't use. The message would be the following: miners and developers exist to serve the software's users. Get on board with what the community has chosen, or get out.\n\nIn conclusion, Segregated Witness has some benefits. A lot of people worked hard on it. It probably has a place somewhere in the cryptocurrency industry. The Segregated Witness hard fork may result in a majority adopting it. If a majority of users stick with the existing code, then Core developers who support Segregated Witness will still be able to use it on the less valuable fork, just as a minority of Ethereum users decided to go their separate way and both communities are largely fine with that decision.\n\nA soft fork places the decisionmaking authority in the hands of miners who will be unaffected by the economic consequences of that decision. Users should make that decision instead. If no action is taken before a soft fork, then everyone is stuck with the changes forever, and even a later successful fork to an unlimited blocksize will then have to deal with all the Segregated Witness transactions. If anyone is ever going to make a statement that Bitcoin exists for its users, not its developers or miners, it is time to put Segregated Witness to the test of a hard fork..... \n\nThanks, \n@steves",
"json_metadata": "{\"tags\":[\"programming\"],\"users\":[\"steves\"]}"
}
]
}| parent author | steves |
| parent permlink | it-s-time-for-the-ethereum-foundation-to-move-forward |
| author | itay |
| permlink | re-it-s-time-for-the-ethereum-foundation-to-move-forward |
| title | |
| body | I upvoted You |
| json metadata | {} |
| Transaction Info | Block #4560663/Trx c39f302f0cfe743ec363e851f0032b40c98bddb4 |
View Raw JSON Data
{
"trx_id": "c39f302f0cfe743ec363e851f0032b40c98bddb4",
"block": 4560663,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-31T12:17:21",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "it-s-time-for-the-ethereum-foundation-to-move-forward",
"author": "itay",
"permlink": "re-it-s-time-for-the-ethereum-foundation-to-move-forward",
"title": "",
"body": "I upvoted You",
"json_metadata": "{}"
}
]
}itayupvoted (100.00%) @steves / it-s-time-for-the-ethereum-foundation-to-move-forward
itayupvoted (100.00%) @steves / it-s-time-for-the-ethereum-foundation-to-move-forward
| voter | itay |
| author | steves |
| permlink | it-s-time-for-the-ethereum-foundation-to-move-forward |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4560654/Trx 13288f7f3a366e8859f9240be95434bf73b5cbe1 |
View Raw JSON Data
{
"trx_id": "13288f7f3a366e8859f9240be95434bf73b5cbe1",
"block": 4560654,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-31T12:16:54",
"op": [
"vote",
{
"voter": "itay",
"author": "steves",
"permlink": "it-s-time-for-the-ethereum-foundation-to-move-forward",
"weight": 10000
}
]
}ladox123upvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
ladox123upvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
| voter | ladox123 |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| weight | 10000 (100.00%) |
| Transaction Info | Block #4196684/Trx 7834d9b21a64abaa5f7ac57b7fe08aa9096e4d84 |
View Raw JSON Data
{
"trx_id": "7834d9b21a64abaa5f7ac57b7fe08aa9096e4d84",
"block": 4196684,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-18T18:40:57",
"op": [
"vote",
{
"voter": "ladox123",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"weight": 10000
}
]
}| voter | belkin |
| author | steves |
| permlink | btc12-com |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3925368/Trx c9ec2ee416ae976e00d0d3a1b36beaa5f51f190a |
View Raw JSON Data
{
"trx_id": "c9ec2ee416ae976e00d0d3a1b36beaa5f51f190a",
"block": 3925368,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-09T07:31:24",
"op": [
"vote",
{
"voter": "belkin",
"author": "steves",
"permlink": "btc12-com",
"weight": 10000
}
]
}| voter | bestmz |
| author | steves |
| permlink | btc12-com |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3916450/Trx 0c39dd5ee690624b4e9a8a757972bb6fc00ccdf1 |
View Raw JSON Data
{
"trx_id": "0c39dd5ee690624b4e9a8a757972bb6fc00ccdf1",
"block": 3916450,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:59:45",
"op": [
"vote",
{
"voter": "bestmz",
"author": "steves",
"permlink": "btc12-com",
"weight": 10000
}
]
}| voter | dedriss |
| author | steves |
| permlink | btc12-com |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3916397/Trx c1a0911cd874dbffabeab0fe8a677c8de6376bfb |
View Raw JSON Data
{
"trx_id": "c1a0911cd874dbffabeab0fe8a677c8de6376bfb",
"block": 3916397,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:57:06",
"op": [
"vote",
{
"voter": "dedriss",
"author": "steves",
"permlink": "btc12-com",
"weight": 10000
}
]
}stevesupvoted (100.00%) @jamtaylor / steemit-photo-challenge-3-winners-announcement
stevesupvoted (100.00%) @jamtaylor / steemit-photo-challenge-3-winners-announcement
| voter | steves |
| author | jamtaylor |
| permlink | steemit-photo-challenge-3-winners-announcement |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3915600/Trx afe903f6ce27d950973d848cd4645432c060be0b |
View Raw JSON Data
{
"trx_id": "afe903f6ce27d950973d848cd4645432c060be0b",
"block": 3915600,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:17:12",
"op": [
"vote",
{
"voter": "steves",
"author": "jamtaylor",
"permlink": "steemit-photo-challenge-3-winners-announcement",
"weight": 10000
}
]
}stevesupvoted (100.00%) @ntomaino / silicon-valley-steem-meetup
stevesupvoted (100.00%) @ntomaino / silicon-valley-steem-meetup
| voter | steves |
| author | ntomaino |
| permlink | silicon-valley-steem-meetup |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3915599/Trx f28a3b2ece877ad336be7f9cbd75ec26bb3787e5 |
View Raw JSON Data
{
"trx_id": "f28a3b2ece877ad336be7f9cbd75ec26bb3787e5",
"block": 3915599,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:17:09",
"op": [
"vote",
{
"voter": "steves",
"author": "ntomaino",
"permlink": "silicon-valley-steem-meetup",
"weight": 10000
}
]
}| voter | steves |
| author | dollarvigilante |
| permlink | if-you-get-angry-others-are-making-money-on-steemit-you-need-to-stahp |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3915597/Trx 5969baa98347f12a038fd0072772cfb12f7a68b9 |
View Raw JSON Data
{
"trx_id": "5969baa98347f12a038fd0072772cfb12f7a68b9",
"block": 3915597,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:17:03",
"op": [
"vote",
{
"voter": "steves",
"author": "dollarvigilante",
"permlink": "if-you-get-angry-others-are-making-money-on-steemit-you-need-to-stahp",
"weight": 10000
}
]
}stevesupvoted (100.00%) @dedriss / the-unique-nature-of-kamchatka
stevesupvoted (100.00%) @dedriss / the-unique-nature-of-kamchatka
| voter | steves |
| author | dedriss |
| permlink | the-unique-nature-of-kamchatka |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3915592/Trx fe603b85522300bc70f8d1db4c645058dbe43c54 |
View Raw JSON Data
{
"trx_id": "fe603b85522300bc70f8d1db4c645058dbe43c54",
"block": 3915592,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:16:48",
"op": [
"vote",
{
"voter": "steves",
"author": "dedriss",
"permlink": "the-unique-nature-of-kamchatka",
"weight": 10000
}
]
}| voter | steves |
| author | steves |
| permlink | btc12-com |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3915573/Trx d30c477ac6f7da9ce3740f33ab88fab92d75277a |
View Raw JSON Data
{
"trx_id": "d30c477ac6f7da9ce3740f33ab88fab92d75277a",
"block": 3915573,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:15:51",
"op": [
"vote",
{
"voter": "steves",
"author": "steves",
"permlink": "btc12-com",
"weight": 10000
}
]
}| parent author | |
| parent permlink | cn |
| author | steves |
| permlink | btc12-com |
| title | btc12.com |
| body |  你好,亲爱的朋友们,我发现了很多关于这个博客为自己有用的信息。http://btc12.com/ 是中国博客提供最新ICO,ICO筹款的历史,黑名单和其他altcoins消息的内部。 该博客有谁幸存下来的许多诈骗老兵密码,他们是投机者也。 请找出所有不同altcoins和ICO项目FUD和支持。 我为我的中国道歉,谢谢你。 推广后是可用的,只要你能提供合法的后盾,你的ICO。 |
| json metadata | {"tags":["cn"],"image":["https://i.sli.mg/LaIDLa.jpg"]} |
| Transaction Info | Block #3915573/Trx d30c477ac6f7da9ce3740f33ab88fab92d75277a |
View Raw JSON Data
{
"trx_id": "d30c477ac6f7da9ce3740f33ab88fab92d75277a",
"block": 3915573,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:15:51",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cn",
"author": "steves",
"permlink": "btc12-com",
"title": "btc12.com",
"body": "\n\n你好,亲爱的朋友们,我发现了很多关于这个博客为自己有用的信息。http://btc12.com/ 是中国博客提供最新ICO,ICO筹款的历史,黑名单和其他altcoins消息的内部。\n\n\n该博客有谁幸存下来的许多诈骗老兵密码,他们是投机者也。\n\n\n请找出所有不同altcoins和ICO项目FUD和支持。 \n\n我为我的中国道歉,谢谢你。 \n\n\n\n推广后是可用的,只要你能提供合法的后盾,你的ICO。",
"json_metadata": "{\"tags\":[\"cn\"],\"image\":[\"https://i.sli.mg/LaIDLa.jpg\"]}"
}
]
}| voter | steves |
| author | falkvinge |
| permlink | it-was-never-about-capitalism-vs-communism-it-was-always-about-centralized-vs-decentralized |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3915383/Trx 12220704b6581d8e9b4a785f2f391ab2e8782946 |
View Raw JSON Data
{
"trx_id": "12220704b6581d8e9b4a785f2f391ab2e8782946",
"block": 3915383,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:06:21",
"op": [
"vote",
{
"voter": "steves",
"author": "falkvinge",
"permlink": "it-was-never-about-capitalism-vs-communism-it-was-always-about-centralized-vs-decentralized",
"weight": 10000
}
]
}stevesupvoted (100.00%) @falkvinge / the-founder-of-the-pirate-party-brings-liberty-ideas-to-steem
stevesupvoted (100.00%) @falkvinge / the-founder-of-the-pirate-party-brings-liberty-ideas-to-steem
| voter | steves |
| author | falkvinge |
| permlink | the-founder-of-the-pirate-party-brings-liberty-ideas-to-steem |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3915381/Trx 2d56cfa84d4e2228d2cf47803494d400e7a638bf |
View Raw JSON Data
{
"trx_id": "2d56cfa84d4e2228d2cf47803494d400e7a638bf",
"block": 3915381,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-08T23:06:15",
"op": [
"vote",
{
"voter": "steves",
"author": "falkvinge",
"permlink": "the-founder-of-the-pirate-party-brings-liberty-ideas-to-steem",
"weight": 10000
}
]
}| voter | steves |
| author | rok-sivante |
| permlink | the-organic-mafioso-exposed-how-what-you-eat-makes-you-a-superior-enlightened-being-or-maybe-just-an-arrogant-asshole |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3817024/Trx 1b1af2493b0a7060a7692926cdd7fc37933be440 |
View Raw JSON Data
{
"trx_id": "1b1af2493b0a7060a7692926cdd7fc37933be440",
"block": 3817024,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T12:45:21",
"op": [
"vote",
{
"voter": "steves",
"author": "rok-sivante",
"permlink": "the-organic-mafioso-exposed-how-what-you-eat-makes-you-a-superior-enlightened-being-or-maybe-just-an-arrogant-asshole",
"weight": 10000
}
]
}| voter | steves |
| author | calaber24p |
| permlink | fundamentals-for-life-2-creating-a-fulfilling-life-and-forgetting-about-status-anxiety |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3817021/Trx ea48974ab0d02a14652bb89ba596e2308566b234 |
View Raw JSON Data
{
"trx_id": "ea48974ab0d02a14652bb89ba596e2308566b234",
"block": 3817021,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T12:45:12",
"op": [
"vote",
{
"voter": "steves",
"author": "calaber24p",
"permlink": "fundamentals-for-life-2-creating-a-fulfilling-life-and-forgetting-about-status-anxiety",
"weight": 10000
}
]
}stevesupvoted (100.00%) @pairmike / learning-steemit-is-easy-as-1-2-3
stevesupvoted (100.00%) @pairmike / learning-steemit-is-easy-as-1-2-3
| voter | steves |
| author | pairmike |
| permlink | learning-steemit-is-easy-as-1-2-3 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3817018/Trx 525fea1c9ac87d36e30987d46a93d3545aacf1df |
View Raw JSON Data
{
"trx_id": "525fea1c9ac87d36e30987d46a93d3545aacf1df",
"block": 3817018,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T12:45:03",
"op": [
"vote",
{
"voter": "steves",
"author": "pairmike",
"permlink": "learning-steemit-is-easy-as-1-2-3",
"weight": 10000
}
]
}| voter | steves |
| author | krishtopa |
| permlink | what-are-neural-networks-why-they-are-so-popular-and-what-problems-can-solve |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3817012/Trx 215b730cb2f292d79655705938def98ecf9dfaaa |
View Raw JSON Data
{
"trx_id": "215b730cb2f292d79655705938def98ecf9dfaaa",
"block": 3817012,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T12:44:45",
"op": [
"vote",
{
"voter": "steves",
"author": "krishtopa",
"permlink": "what-are-neural-networks-why-they-are-so-popular-and-what-problems-can-solve",
"weight": 10000
}
]
}eternalaboveupvoted (0.10%) @steves / it-s-time-for-the-ethereum-foundation-to-move-forward
eternalaboveupvoted (0.10%) @steves / it-s-time-for-the-ethereum-foundation-to-move-forward
| voter | eternalabove |
| author | steves |
| permlink | it-s-time-for-the-ethereum-foundation-to-move-forward |
| weight | 10 (0.10%) |
| Transaction Info | Block #3817006/Trx 0af51f6155096bffa8e625d100aaf462ce51f340 |
View Raw JSON Data
{
"trx_id": "0af51f6155096bffa8e625d100aaf462ce51f340",
"block": 3817006,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T12:44:27",
"op": [
"vote",
{
"voter": "eternalabove",
"author": "steves",
"permlink": "it-s-time-for-the-ethereum-foundation-to-move-forward",
"weight": 10
}
]
}| parent author | steves |
| parent permlink | it-s-time-for-the-ethereum-foundation-to-move-forward |
| author | eternalabove |
| permlink | it-s-time-for-the-ethereum-foundation-to-move-forward |
| title | |
| body | Dear User known as @steves Steemit has a BOT problem! Your Vote Counts... Maybe https://steemit.com/steemit/@weenis/bots-steemit-s-first-community-based-decision-on-bots-your-vote-counts-to-be-or-not-to-be-details-inside |
| json metadata | |
| Transaction Info | Block #3817004/Trx 753082c4a61ca63f8e480b8a86e2d99de2c80910 |
View Raw JSON Data
{
"trx_id": "753082c4a61ca63f8e480b8a86e2d99de2c80910",
"block": 3817004,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T12:44:21",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "it-s-time-for-the-ethereum-foundation-to-move-forward",
"author": "eternalabove",
"permlink": "it-s-time-for-the-ethereum-foundation-to-move-forward",
"title": "",
"body": "Dear User known as @steves \n Steemit has a BOT problem! Your Vote Counts... Maybe \n https://steemit.com/steemit/@weenis/bots-steemit-s-first-community-based-decision-on-bots-your-vote-counts-to-be-or-not-to-be-details-inside",
"json_metadata": ""
}
]
}stevesupvoted (100.00%) @steves / it-s-time-for-the-ethereum-foundation-to-move-forward
stevesupvoted (100.00%) @steves / it-s-time-for-the-ethereum-foundation-to-move-forward
| voter | steves |
| author | steves |
| permlink | it-s-time-for-the-ethereum-foundation-to-move-forward |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3816991/Trx 90a9bfcf26e40f214a5e28e2e4f230b6ef37424e |
View Raw JSON Data
{
"trx_id": "90a9bfcf26e40f214a5e28e2e4f230b6ef37424e",
"block": 3816991,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T12:43:42",
"op": [
"vote",
{
"voter": "steves",
"author": "steves",
"permlink": "it-s-time-for-the-ethereum-foundation-to-move-forward",
"weight": 10000
}
]
}stevespublished a new post: it-s-time-for-the-ethereum-foundation-to-move-forward
stevespublished a new post: it-s-time-for-the-ethereum-foundation-to-move-forward
| parent author | |
| parent permlink | ethereum |
| author | steves |
| permlink | it-s-time-for-the-ethereum-foundation-to-move-forward |
| title | It's time for the Ethereum Foundation to move forward |
| body | Hello all! Recently, Ethereum Classic (ETC) increased significantly in value. Though ETC is declining now and I don't believe that Ethereum Classic is likely to retain much value, the success of the Ethereum main fork is in cryptocurrency's best interest. The purpose of this article is to explain why the Ethereum Foundation should announce a plan to draw down its Ethereum Classic holdings, which it inherited from the initial Ethereum pre-sale. Doing so would accomplish a number of objectives that would further the development of the cryptocurrency industry, while also setting a precedent for the future and providing the Foundation with more financial resources for continued development. Vitalik Buterin and the Foundation have made it clear that they intend to support more hard forks of Ethereum in the future, most notably to implement proof-of-stake and three second block times. Ethereum Classic was the first of what will eventually become many legacy blockchains, each of which is likely to be supported by a coalition of people with different objectives. Some will support the old chain on the basis of political ideology, some will try to profit by increasing the price of the old chain in bubbles and panics, and others will use the old chain to conduct replay attacks against exchanges and people like Coinbase who don't care. Aside from the criminals who will conduct attacks, it's fine for people to make their own decisions about other chains. That said, any coin that is premined, as Ethereum is, has a unique opportunity to shape its future development by using the premined holdings to place sell orders that cap the price of old blockchains. The Ethereum Foundation should place a cap on the value of Ethereum Classic through a massive sell order, beginning immediately, and do so for the legacy chain with each successive fork. First, while the majority of companies have indicated that they support Ethereum, and Buterin himself said that he will not support Ethereum Classic even if it were to increase in price above Ethereum, words are not as strong as action. The Foundation's sale of its coins, and the sale of their personal coins, would send a powerful message to businesses who are planning their strategies for the future of smart contracts. While Buterin's comments were enough to convince some to convert bitcoins into ETH yesterday, people who are skeptical of his character will be more convinced if the Foundation begins selling its holdings of Ethereum Classic. Second, the developers of ETC themselves have made it clear that they follow a different philosophy than do the developers of Ethereum, and that they will be taking different development paths in the future. Removing the influence of the Foundation from old blockchains is also the right thing to do for the developers of those chains, so that they can direct development effort where they wish without interference from the Foundation hanging over their heads. Third, the sale of the Foundation's holdings would raise needed capital to pay developers. The Foundation undoubtedly holds millions of dollars in Ethereum Classic right now, even with its falling value. The money can be converted into ETH, to demonstrate support for the currency and to be sold at a later time to pay labor costs. Given that ETH is already a more capable network than BTC, this is a golden opportunity to accelerate the development of ETH into the #1 blockchain. Fourth, this particular case of ETC is different than future cases in that at least 1/8 (and possibly 1/5) of the currency is controlled by attackers, counterattackers, and various unethical people. As these coins leave the DAO and replay attack wallets, they will eventually make their way to exchanges to be sold. The Foundation has a moral obligation to see that the money on the orderbooks is used to do good in the world, rather than to reward people for ethically questionable activities. In addition, hackers would see the Foundation's action and adjust their behavior in the future, since they will realize that they will place themselves at risk of arrest for little gain. It seems that there is still insufficient outrage over the idea that thieves were able to overrule justice and turn something that was worth nothing into ill-gotten gains worth millions of dollars. People seem to be forgetting that this wasn't a "bailout" for an organization with a poor business model, but a recovery of stolen money. Finally, the most important reason for liquidating the Foundation's holdings is because this time isn't the only time there will be multiple versions of Ethereum. Over time, there may be three, or four, or five old chains, each claiming to be Ethereum. Those old chains themselves will likely fork to implement features different from the main Ethereum fork. Neutrality is an untenable position when there are so many different versions of the same thing around. If nothing else, there would be a shortage of manpower to keep track of all the coins. In conclusion, the purpose of any open source association is to take action to further the interest of the software's users. In this case, the most useful action the Ethereum Foundation can take to increase business owner and investor confidence is to eliminate its holdings on the Ethereum Classic and any future old-fork chains. In addition to restoring certainty and stability to the markets, selling unneeded coins would provide additional funds for development, would prevent unethical people from cashing in on their profits, would eliminate the Foundation's unwanted influence over people who clearly do not want to be associated with it, and would set a precedent for future forks that the same action would be taken to set a clear direction for Ethereum development. There was plenty of time for debate and discussion. Every major poll, conducted using a number of different weighting methods for voting, indicated majority support for moving forward with ETH by users currently invested in Ethereum. While others are welcome to develop and invest in their chains as they see fit, the Foundation's job is to support one Ethereum blockchain, and it is time for the group to supplement words with action. Let those who support ETC go their own way without interference, and make a commitment to the support of one chain moving forward. Thanks @steves |
| json metadata | {"tags":["ethereum"],"users":["steves"]} |
| Transaction Info | Block #3816991/Trx 90a9bfcf26e40f214a5e28e2e4f230b6ef37424e |
View Raw JSON Data
{
"trx_id": "90a9bfcf26e40f214a5e28e2e4f230b6ef37424e",
"block": 3816991,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T12:43:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ethereum",
"author": "steves",
"permlink": "it-s-time-for-the-ethereum-foundation-to-move-forward",
"title": "It's time for the Ethereum Foundation to move forward",
"body": "Hello all! Recently, Ethereum Classic (ETC) increased significantly in value. Though ETC is declining now and I don't believe that Ethereum Classic is likely to retain much value, the success of the Ethereum main fork is in cryptocurrency's best interest. The purpose of this article is to explain why the Ethereum Foundation should announce a plan to draw down its Ethereum Classic holdings, which it inherited from the initial Ethereum pre-sale. Doing so would accomplish a number of objectives that would further the development of the cryptocurrency industry, while also setting a precedent for the future and providing the Foundation with more financial resources for continued development.\n\nVitalik Buterin and the Foundation have made it clear that they intend to support more hard forks of Ethereum in the future, most notably to implement proof-of-stake and three second block times. Ethereum Classic was the first of what will eventually become many legacy blockchains, each of which is likely to be supported by a coalition of people with different objectives. Some will support the old chain on the basis of political ideology, some will try to profit by increasing the price of the old chain in bubbles and panics, and others will use the old chain to conduct replay attacks against exchanges and people like Coinbase who don't care.\n\nAside from the criminals who will conduct attacks, it's fine for people to make their own decisions about other chains. That said, any coin that is premined, as Ethereum is, has a unique opportunity to shape its future development by using the premined holdings to place sell orders that cap the price of old blockchains. The Ethereum Foundation should place a cap on the value of Ethereum Classic through a massive sell order, beginning immediately, and do so for the legacy chain with each successive fork.\n\nFirst, while the majority of companies have indicated that they support Ethereum, and Buterin himself said that he will not support Ethereum Classic even if it were to increase in price above Ethereum, words are not as strong as action. The Foundation's sale of its coins, and the sale of their personal coins, would send a powerful message to businesses who are planning their strategies for the future of smart contracts. While Buterin's comments were enough to convince some to convert bitcoins into ETH yesterday, people who are skeptical of his character will be more convinced if the Foundation begins selling its holdings of Ethereum Classic.\n\nSecond, the developers of ETC themselves have made it clear that they follow a different philosophy than do the developers of Ethereum, and that they will be taking different development paths in the future. Removing the influence of the Foundation from old blockchains is also the right thing to do for the developers of those chains, so that they can direct development effort where they wish without interference from the Foundation hanging over their heads.\n\nThird, the sale of the Foundation's holdings would raise needed capital to pay developers. The Foundation undoubtedly holds millions of dollars in Ethereum Classic right now, even with its falling value. The money can be converted into ETH, to demonstrate support for the currency and to be sold at a later time to pay labor costs. Given that ETH is already a more capable network than BTC, this is a golden opportunity to accelerate the development of ETH into the #1 blockchain.\n\nFourth, this particular case of ETC is different than future cases in that at least 1/8 (and possibly 1/5) of the currency is controlled by attackers, counterattackers, and various unethical people. As these coins leave the DAO and replay attack wallets, they will eventually make their way to exchanges to be sold. The Foundation has a moral obligation to see that the money on the orderbooks is used to do good in the world, rather than to reward people for ethically questionable activities. In addition, hackers would see the Foundation's action and adjust their behavior in the future, since they will realize that they will place themselves at risk of arrest for little gain. It seems that there is still insufficient outrage over the idea that thieves were able to overrule justice and turn something that was worth nothing into ill-gotten gains worth millions of dollars. People seem to be forgetting that this wasn't a \"bailout\" for an organization with a poor business model, but a recovery of stolen money.\n\nFinally, the most important reason for liquidating the Foundation's holdings is because this time isn't the only time there will be multiple versions of Ethereum. Over time, there may be three, or four, or five old chains, each claiming to be Ethereum. Those old chains themselves will likely fork to implement features different from the main Ethereum fork. Neutrality is an untenable position when there are so many different versions of the same thing around. If nothing else, there would be a shortage of manpower to keep track of all the coins.\n\nIn conclusion, the purpose of any open source association is to take action to further the interest of the software's users. In this case, the most useful action the Ethereum Foundation can take to increase business owner and investor confidence is to eliminate its holdings on the Ethereum Classic and any future old-fork chains. In addition to restoring certainty and stability to the markets, selling unneeded coins would provide additional funds for development, would prevent unethical people from cashing in on their profits, would eliminate the Foundation's unwanted influence over people who clearly do not want to be associated with it, and would set a precedent for future forks that the same action would be taken to set a clear direction for Ethereum development.\n\nThere was plenty of time for debate and discussion. Every major poll, conducted using a number of different weighting methods for voting, indicated majority support for moving forward with ETH by users currently invested in Ethereum. While others are welcome to develop and invest in their chains as they see fit, the Foundation's job is to support one Ethereum blockchain, and it is time for the group to supplement words with action. Let those who support ETC go their own way without interference, and make a commitment to the support of one chain moving forward. \n\nThanks \n\n@steves",
"json_metadata": "{\"tags\":[\"ethereum\"],\"users\":[\"steves\"]}"
}
]
}stevesreceived 0.015 SBD, 0.017 SP author reward for @steves / why-ethereum-classic-is-overvalued
stevesreceived 0.015 SBD, 0.017 SP author reward for @steves / why-ethereum-classic-is-overvalued
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| sbd payout | 0.015 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 26.930856 VESTS |
| Transaction Info | Block #3810356/Virtual Operation #2 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 3810356,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 2,
"timestamp": "2016-08-05T07:10:39",
"op": [
"author_reward",
{
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"sbd_payout": "0.015 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "26.930856 VESTS"
}
]
}pictoriansupvoted (100.00%) @steves / dark-day-cryptocurrency-s
pictoriansupvoted (100.00%) @steves / dark-day-cryptocurrency-s
| voter | pictorians |
| author | steves |
| permlink | dark-day-cryptocurrency-s |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3805453/Trx bb6f0276d9397e265989a4a51f26c3fab758d5e2 |
View Raw JSON Data
{
"trx_id": "bb6f0276d9397e265989a4a51f26c3fab758d5e2",
"block": 3805453,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T03:04:06",
"op": [
"vote",
{
"voter": "pictorians",
"author": "steves",
"permlink": "dark-day-cryptocurrency-s",
"weight": 10000
}
]
}carlgetaladaupvoted (100.00%) @steves / is-bitcoin-worth-saving
carlgetaladaupvoted (100.00%) @steves / is-bitcoin-worth-saving
| voter | carlgetalada |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3805128/Trx 22e8e471c3420e2bb55bf3a7fbad134506c2002a |
View Raw JSON Data
{
"trx_id": "22e8e471c3420e2bb55bf3a7fbad134506c2002a",
"block": 3805128,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T02:47:48",
"op": [
"vote",
{
"voter": "carlgetalada",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10000
}
]
}| parent author | steves |
| parent permlink | is-bitcoin-worth-saving |
| author | carlgetalada |
| permlink | re-steves-is-bitcoin-worth-saving-20160805t024740893z |
| title | |
| body | Thank you for re-confirming my personal plans to switch to ETH for trading transactions from fiat to crypto & vice versa. Was really quite frustrated at waiting for BTC confirmations. I am also quite losing interest with BTC developments, & amuse at its hard core supporters who migrated to oppose ETH HF, only to be facing the same probabilities/necessities for BTC to improve. Nevertheless, I would say BTC is worth saving, even if only to the extent for the good of crypto world. If its fans want to, let it be like an elephant gold statue that never changes, & just become a storage of value. |
| json metadata | {"tags":["bitcoin"]} |
| Transaction Info | Block #3805126/Trx 4f090af5e14ee805844460b34e743dc2774c829e |
View Raw JSON Data
{
"trx_id": "4f090af5e14ee805844460b34e743dc2774c829e",
"block": 3805126,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T02:47:42",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "is-bitcoin-worth-saving",
"author": "carlgetalada",
"permlink": "re-steves-is-bitcoin-worth-saving-20160805t024740893z",
"title": "",
"body": "Thank you for re-confirming my personal plans to switch to ETH for trading transactions from fiat to crypto & vice versa. Was really quite frustrated at waiting for BTC confirmations. \n\nI am also quite losing interest with BTC developments, & amuse at its hard core supporters who migrated to oppose ETH HF, only to be facing the same probabilities/necessities for BTC to improve.\n\nNevertheless, I would say BTC is worth saving, even if only to the extent for the good of crypto world. If its fans want to, let it be like an elephant gold statue that never changes, & just become a storage of value.",
"json_metadata": "{\"tags\":[\"bitcoin\"]}"
}
]
}| parent author | steves |
| parent permlink | why-ethereum-classic-is-overvalued |
| author | hackecon |
| permlink | re-steves-why-ethereum-classic-is-overvalued-20160805t022910499z |
| title | |
| body | I'm personally concerned at the fact that the split even held traction. When I voted on Dwarfpool, the Yes to No ratio was nearly 92:8. IMHO ETC will die soon, and ETH will slowly regain community trust. |
| json metadata | {"tags":["ethereum"]} |
| Transaction Info | Block #3804754/Trx 429f302fca3a938534240fa457c746a1de4b7d52 |
View Raw JSON Data
{
"trx_id": "429f302fca3a938534240fa457c746a1de4b7d52",
"block": 3804754,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T02:29:03",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "why-ethereum-classic-is-overvalued",
"author": "hackecon",
"permlink": "re-steves-why-ethereum-classic-is-overvalued-20160805t022910499z",
"title": "",
"body": "I'm personally concerned at the fact that the split even held traction. When I voted on Dwarfpool, the Yes to No ratio was nearly 92:8.\n\nIMHO ETC will die soon, and ETH will slowly regain community trust.",
"json_metadata": "{\"tags\":[\"ethereum\"]}"
}
]
}hackeconupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
hackeconupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
| voter | hackecon |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3804730/Trx 32c1f8c80406135a16e5a22d72423cbd9a745466 |
View Raw JSON Data
{
"trx_id": "32c1f8c80406135a16e5a22d72423cbd9a745466",
"block": 3804730,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T02:27:48",
"op": [
"vote",
{
"voter": "hackecon",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"weight": 10000
}
]
}stevenh512upvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
stevenh512upvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
| voter | stevenh512 |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3804612/Trx 22531a80e4fe986292443f75649df5425c3020c1 |
View Raw JSON Data
{
"trx_id": "22531a80e4fe986292443f75649df5425c3020c1",
"block": 3804612,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-05T02:21:54",
"op": [
"vote",
{
"voter": "stevenh512",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"weight": 10000
}
]
}stevesreceived 0.009 SBD, 0.012 SP author reward for @steves / is-bitcoin-worth-saving
stevesreceived 0.009 SBD, 0.012 SP author reward for @steves / is-bitcoin-worth-saving
| author | steves |
| permlink | is-bitcoin-worth-saving |
| sbd payout | 0.009 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 19.269106 VESTS |
| Transaction Info | Block #3803102/Virtual Operation #3 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 3803102,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 3,
"timestamp": "2016-08-05T01:06:18",
"op": [
"author_reward",
{
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"sbd_payout": "0.009 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "19.269106 VESTS"
}
]
}kukuyupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
kukuyupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
| voter | kukuy |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3796867/Trx 38a21f865910497b1b279484d60c1f336329d94f |
View Raw JSON Data
{
"trx_id": "38a21f865910497b1b279484d60c1f336329d94f",
"block": 3796867,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T19:50:45",
"op": [
"vote",
{
"voter": "kukuy",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"weight": 10000
}
]
}vrdadupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
vrdadupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
| voter | vrdad |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3796394/Trx 1d602aa5ae3ee16cfe90e1edfc952a2089af7579 |
View Raw JSON Data
{
"trx_id": "1d602aa5ae3ee16cfe90e1edfc952a2089af7579",
"block": 3796394,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T19:24:51",
"op": [
"vote",
{
"voter": "vrdad",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"weight": 10000
}
]
}| parent author | steves |
| parent permlink | why-ethereum-classic-is-overvalued |
| author | vrdad |
| permlink | re-steves-why-ethereum-classic-is-overvalued-20160804t192439415z |
| title | |
| body | ETC will be worth something someday assuming the coin can find programmers. The next fork will fix the Replay Attacks for good. If you own any I would go long, well at least until the replay attack is fixed. I think I have a few but i am not going onto a hacked network until it's working. |
| json metadata | {"tags":["ethereum"]} |
| Transaction Info | Block #3796389/Trx dba300778d663ddae9ed5e34d542209d8ce1b9c4 |
View Raw JSON Data
{
"trx_id": "dba300778d663ddae9ed5e34d542209d8ce1b9c4",
"block": 3796389,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T19:24:33",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "why-ethereum-classic-is-overvalued",
"author": "vrdad",
"permlink": "re-steves-why-ethereum-classic-is-overvalued-20160804t192439415z",
"title": "",
"body": "ETC will be worth something someday assuming the coin can find programmers. The next fork will fix the Replay Attacks for good. If you own any I would go long, well at least until the replay attack is fixed. I think I have a few but i am not going onto a hacked network until it's working.",
"json_metadata": "{\"tags\":[\"ethereum\"]}"
}
]
}cats-and-kittensupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
cats-and-kittensupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
| voter | cats-and-kittens |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3796055/Trx 1286d1bc52be321491ca1c56a1234800678b2c11 |
View Raw JSON Data
{
"trx_id": "1286d1bc52be321491ca1c56a1234800678b2c11",
"block": 3796055,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T19:07:03",
"op": [
"vote",
{
"voter": "cats-and-kittens",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"weight": 10000
}
]
}toxonautupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
toxonautupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
| voter | toxonaut |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3795956/Trx b171633be8cd766c9bb02bf4524153e3517219f0 |
View Raw JSON Data
{
"trx_id": "b171633be8cd766c9bb02bf4524153e3517219f0",
"block": 3795956,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T19:01:48",
"op": [
"vote",
{
"voter": "toxonaut",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"weight": 10000
}
]
}| parent author | steves |
| parent permlink | why-ethereum-classic-is-overvalued |
| author | isaac.asimov |
| permlink | re-why-ethereum-classic-is-overvalued-20160804t185957 |
| title | Flesch Kincaid Grade Level |
| body | Hi! This post has a <a href="https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readability_tests">Flesch-Kincaid</a> grade level of 10.0 and reading ease of 63%. This puts the writing level on par with Michael Crichton and Mitt Romney. |
| json metadata | |
| Transaction Info | Block #3795921/Trx c553bcb7b150ca2e9e5480fe90a4e9bf074ab53f |
View Raw JSON Data
{
"trx_id": "c553bcb7b150ca2e9e5480fe90a4e9bf074ab53f",
"block": 3795921,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T18:59:57",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "why-ethereum-classic-is-overvalued",
"author": "isaac.asimov",
"permlink": "re-why-ethereum-classic-is-overvalued-20160804t185957",
"title": "Flesch Kincaid Grade Level",
"body": "Hi! This post has a <a href=\"https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readability_tests\">Flesch-Kincaid</a> grade level of 10.0 and reading ease of 63%. This puts the writing level on par with Michael Crichton and Mitt Romney.",
"json_metadata": ""
}
]
}alniskobsreplied to @steves / why-ethereum-classic-is-overvalued
alniskobsreplied to @steves / why-ethereum-classic-is-overvalued
| parent author | steves |
| parent permlink | why-ethereum-classic-is-overvalued |
| author | alniskobs |
| permlink | why-ethereum-classic-is-overvalued |
| title | |
| body | Nice @steves Shot you an Upvote :) |
| json metadata | |
| Transaction Info | Block #3795916/Trx f106be8a9792c489d1a75061ba72e52057a47ea7 |
View Raw JSON Data
{
"trx_id": "f106be8a9792c489d1a75061ba72e52057a47ea7",
"block": 3795916,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T18:59:42",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "why-ethereum-classic-is-overvalued",
"author": "alniskobs",
"permlink": "why-ethereum-classic-is-overvalued",
"title": "",
"body": "Nice @steves \n Shot you an Upvote :)",
"json_metadata": ""
}
]
}stevesupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
stevesupvoted (100.00%) @steves / why-ethereum-classic-is-overvalued
| voter | steves |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3795903/Trx b9d61a93595631bda22108a20709a86f0c3ab9c1 |
View Raw JSON Data
{
"trx_id": "b9d61a93595631bda22108a20709a86f0c3ab9c1",
"block": 3795903,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T18:59:00",
"op": [
"vote",
{
"voter": "steves",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"weight": 10000
}
]
}stevespublished a new post: why-ethereum-classic-is-overvalued
stevespublished a new post: why-ethereum-classic-is-overvalued
| parent author | |
| parent permlink | ethereum |
| author | steves |
| permlink | why-ethereum-classic-is-overvalued |
| title | Why Ethereum Classic is overvalued |
| body | Hello! This is a quick post to point out a few issues with the notion that Ethereum Classic is going to overtake Ethereum and become the dominant chain. I mentioned earlier that when a major blockchain forks, markets will spring up in both forks and the old chain will always retain some value. Because the old chain has value, it will always have hashrate. Indeed, we moved our GPUs to mining Ethereum Classic because it was so ridiculously profitable that they were justified being on even when it was very hot outside. ETC's having hashrate is not an indicator of success. In addition, the current price of Ethereum Classic is overvalued because of technical factors that few people seem to be mentioning. For one, the issue of replay attacks makes handling Ethereum Classic very difficult and risky. We had a cold wallet containing hundreds of ETH and ETC that was offsite. I intended to never spend that ETH, and a share of pool profits would periodically be sent to the wallet. When ETC first debuted at Poloniex and crashed, the value of that wallet in ETC fell to just $300, and the opportunity cost of taking away time from the business and the risk of replay attacks on the thousands of dollars of ETH didn't justify our caring about that money. When the value of Ethereum Classic rose, I rushed home to ask Chris to get started with this process so we could liquidate as quickly as possible. But to mitigate against the replay attacks, we had to create yet another secure virtual machine to store our ETH, destroy and write new CD-Rs with the new wallet, regenerate the passwords, and take everything out of the house back to the other locations. Selling ETC is not as simple as pressing "send" - it involves time-consuming safeguards to make sure the more valuable ETH is not stolen. People with large amounts of ETC are holding them in cold storage, and they need time (like we did) to get access to the funds. The other problem with ditching ETC is that it is not simple to get the daemon set up and configured. Chris had to modify the code of the Ethereum Classic client based on some forum suggestions to get it to download the correct blockchain. A command line parameter needs to be used that isn't obvious. Many ETH holders are not knowledgeable enough to be able to learn how to do that very quickly. He spent hours trying to get the daemon configured correctly. Finally, there is the problem of getting the blockchain downloaded itself. The Ethereum blockchain is huge, and even if replay attacks were not a concern, one cannot simply start up the client and send money. It took over a day for the blockchain to download and validate, during which time the bubble had already deflated and we lost 33% of the value of our ETC. Ethereum Classic, like Bitcoin, is an illiquid market where most of the value is being held on paper. The BTC network is so unreliable that it usually takes hours to get money to exchanges, but there has been plenty of time for buyers and sellers to get their money where they need it to be. By contrast, the ETC markets appeared without warning. Buy orders were easily able to flood in, but people could only sell what just bought or ETH they previously held on Poloniex. Now, enough time has passed that people are starting to finally figure out how to configure ETC, have had time to download its blockchain, and will be able to execute their transactions to avoid replay attacks. Ethereum Classic will always have some value; however, the coins from people who see this as free money and wanted to sell as soon as the bubble started will start to arrive at the exchanges in increasing numbers. Many people who haven't actually installed ETC have failed to notice the difficulty in transmitting it, and the price of ETC will decline to a level representative of actual demand as the sellers can finally trade freely. Thanks @steves |
| json metadata | {"tags":["ethereum"],"users":["steves"]} |
| Transaction Info | Block #3795903/Trx b9d61a93595631bda22108a20709a86f0c3ab9c1 |
View Raw JSON Data
{
"trx_id": "b9d61a93595631bda22108a20709a86f0c3ab9c1",
"block": 3795903,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T18:59:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ethereum",
"author": "steves",
"permlink": "why-ethereum-classic-is-overvalued",
"title": "Why Ethereum Classic is overvalued",
"body": "Hello! This is a quick post to point out a few issues with the notion that Ethereum Classic is going to overtake Ethereum and become the dominant chain.\n\nI mentioned earlier that when a major blockchain forks, markets will spring up in both forks and the old chain will always retain some value. Because the old chain has value, it will always have hashrate. Indeed, we moved our GPUs to mining Ethereum Classic because it was so ridiculously profitable that they were justified being on even when it was very hot outside. ETC's having hashrate is not an indicator of success. In addition, the current price of Ethereum Classic is overvalued because of technical factors that few people seem to be mentioning.\n\nFor one, the issue of replay attacks makes handling Ethereum Classic very difficult and risky. We had a cold wallet containing hundreds of ETH and ETC that was offsite. I intended to never spend that ETH, and a share of pool profits would periodically be sent to the wallet. When ETC first debuted at Poloniex and crashed, the value of that wallet in ETC fell to just $300, and the opportunity cost of taking away time from the business and the risk of replay attacks on the thousands of dollars of ETH didn't justify our caring about that money.\n\nWhen the value of Ethereum Classic rose, I rushed home to ask Chris to get started with this process so we could liquidate as quickly as possible. But to mitigate against the replay attacks, we had to create yet another secure virtual machine to store our ETH, destroy and write new CD-Rs with the new wallet, regenerate the passwords, and take everything out of the house back to the other locations. Selling ETC is not as simple as pressing \"send\" - it involves time-consuming safeguards to make sure the more valuable ETH is not stolen. People with large amounts of ETC are holding them in cold storage, and they need time (like we did) to get access to the funds.\n\nThe other problem with ditching ETC is that it is not simple to get the daemon set up and configured. Chris had to modify the code of the Ethereum Classic client based on some forum suggestions to get it to download the correct blockchain. A command line parameter needs to be used that isn't obvious. Many ETH holders are not knowledgeable enough to be able to learn how to do that very quickly. He spent hours trying to get the daemon configured correctly.\n\nFinally, there is the problem of getting the blockchain downloaded itself. The Ethereum blockchain is huge, and even if replay attacks were not a concern, one cannot simply start up the client and send money. It took over a day for the blockchain to download and validate, during which time the bubble had already deflated and we lost 33% of the value of our ETC.\n\nEthereum Classic, like Bitcoin, is an illiquid market where most of the value is being held on paper. The BTC network is so unreliable that it usually takes hours to get money to exchanges, but there has been plenty of time for buyers and sellers to get their money where they need it to be. By contrast, the ETC markets appeared without warning. Buy orders were easily able to flood in, but people could only sell what just bought or ETH they previously held on Poloniex.\n\nNow, enough time has passed that people are starting to finally figure out how to configure ETC, have had time to download its blockchain, and will be able to execute their transactions to avoid replay attacks. Ethereum Classic will always have some value; however, the coins from people who see this as free money and wanted to sell as soon as the bubble started will start to arrive at the exchanges in increasing numbers. Many people who haven't actually installed ETC have failed to notice the difficulty in transmitting it, and the price of ETC will decline to a level representative of actual demand as the sellers can finally trade freely. \n\nThanks \n\n@steves",
"json_metadata": "{\"tags\":[\"ethereum\"],\"users\":[\"steves\"]}"
}
]
}williamgerupvoted (100.00%) @steves / is-bitcoin-worth-saving
williamgerupvoted (100.00%) @steves / is-bitcoin-worth-saving
| voter | williamger |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3793104/Trx 70c12fe2928075353422c5b7a7e5f6f05d1389d7 |
View Raw JSON Data
{
"trx_id": "70c12fe2928075353422c5b7a7e5f6f05d1389d7",
"block": 3793104,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T16:32:09",
"op": [
"vote",
{
"voter": "williamger",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10000
}
]
}dedrissupvoted (100.00%) @steves / is-bitcoin-worth-saving
dedrissupvoted (100.00%) @steves / is-bitcoin-worth-saving
| voter | dedriss |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3789503/Trx bbfc9bcaa74285af88810e4c2bee0315119b26d3 |
View Raw JSON Data
{
"trx_id": "bbfc9bcaa74285af88810e4c2bee0315119b26d3",
"block": 3789503,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T13:31:30",
"op": [
"vote",
{
"voter": "dedriss",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10000
}
]
}loewanremoved vote from (0.00%) @steves / is-bitcoin-worth-saving
loewanremoved vote from (0.00%) @steves / is-bitcoin-worth-saving
| voter | loewan |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 0 (0.00%) |
| Transaction Info | Block #3787390/Trx cd19d57117d776bc8d45de51dbefb51f2dc4e723 |
View Raw JSON Data
{
"trx_id": "cd19d57117d776bc8d45de51dbefb51f2dc4e723",
"block": 3787390,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:45:27",
"op": [
"vote",
{
"voter": "loewan",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 0
}
]
}loewanupvoted (100.00%) @steves / is-bitcoin-worth-saving
loewanupvoted (100.00%) @steves / is-bitcoin-worth-saving
| voter | loewan |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3787385/Trx 9a980b831fe694f78d43649f82053c646b3d5afb |
View Raw JSON Data
{
"trx_id": "9a980b831fe694f78d43649f82053c646b3d5afb",
"block": 3787385,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:45:12",
"op": [
"vote",
{
"voter": "loewan",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10000
}
]
}metu2222upvoted (100.00%) @steves / is-bitcoin-worth-saving
metu2222upvoted (100.00%) @steves / is-bitcoin-worth-saving
| voter | metu2222 |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3787356/Trx 441f372d2a4f24b097ab59d491edbdc1d5650f75 |
View Raw JSON Data
{
"trx_id": "441f372d2a4f24b097ab59d491edbdc1d5650f75",
"block": 3787356,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:43:42",
"op": [
"vote",
{
"voter": "metu2222",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10000
}
]
}| parent author | steves |
| parent permlink | is-bitcoin-worth-saving |
| author | iamrohitkgupta |
| permlink | re-steves-is-bitcoin-worth-saving-20160804t114214635z |
| title | |
| body | @@ -560,8 +560,50 @@ opicseen +%0A%0AI may be wrong, feel free to correct me! |
| json metadata | {"tags":["bitcoin"],"links":["https://bitcointalk.org/index.php?topic=1574127.0;topicseen"]} |
| Transaction Info | Block #3787334/Trx 9e145a3442237e77e75fc950404439e4791e9db5 |
View Raw JSON Data
{
"trx_id": "9e145a3442237e77e75fc950404439e4791e9db5",
"block": 3787334,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:42:36",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "is-bitcoin-worth-saving",
"author": "iamrohitkgupta",
"permlink": "re-steves-is-bitcoin-worth-saving-20160804t114214635z",
"title": "",
"body": "@@ -560,8 +560,50 @@\n opicseen\n+%0A%0AI may be wrong, feel free to correct me!\n",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://bitcointalk.org/index.php?topic=1574127.0;topicseen\"]}"
}
]
}| parent author | steves |
| parent permlink | is-bitcoin-worth-saving |
| author | iamrohitkgupta |
| permlink | re-steves-is-bitcoin-worth-saving-20160804t114214635z |
| title | |
| body | Only time will tell what happens to bitcoin. Ethereum and bitcoin both have been hacked but they both recovered pretty quickly. Ethereum was hard forked and ETC was created and made it messy. Although I see ETH rising and ETC declining, I'm gonna stay away from both because it could change at any moment. Rumors suggest that people supporting ETC and Bitfinex hack are somehow related which if is true, will harm both BTC and ETH. Also if you haven't heard about this 1000BTC giveaway please check it out : https://bitcointalk.org/index.php?topic=1574127.0;topicseen |
| json metadata | {"tags":["bitcoin"],"links":["https://bitcointalk.org/index.php?topic=1574127.0;topicseen"]} |
| Transaction Info | Block #3787323/Trx eae3f8ab1d887088d0664caf1a4cbdc1ee654d23 |
View Raw JSON Data
{
"trx_id": "eae3f8ab1d887088d0664caf1a4cbdc1ee654d23",
"block": 3787323,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:42:03",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "is-bitcoin-worth-saving",
"author": "iamrohitkgupta",
"permlink": "re-steves-is-bitcoin-worth-saving-20160804t114214635z",
"title": "",
"body": "Only time will tell what happens to bitcoin. Ethereum and bitcoin both have been hacked but they both recovered pretty quickly. Ethereum was hard forked and ETC was created and made it messy. Although I see ETH rising and ETC declining, I'm gonna stay away from both because it could change at any moment. Rumors suggest that people supporting ETC and Bitfinex hack are somehow related which if is true, will harm both BTC and ETH. Also if you haven't heard about this 1000BTC giveaway please check it out : https://bitcointalk.org/index.php?topic=1574127.0;topicseen",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://bitcointalk.org/index.php?topic=1574127.0;topicseen\"]}"
}
]
}iamrohitkguptaupvoted (100.00%) @steves / is-bitcoin-worth-saving
iamrohitkguptaupvoted (100.00%) @steves / is-bitcoin-worth-saving
| voter | iamrohitkgupta |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3787207/Trx 21cccaf9d76c3a0feb9e237b853cf43402c57483 |
View Raw JSON Data
{
"trx_id": "21cccaf9d76c3a0feb9e237b853cf43402c57483",
"block": 3787207,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:36:15",
"op": [
"vote",
{
"voter": "iamrohitkgupta",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10000
}
]
}michaellamden68upvoted (100.00%) @steves / is-bitcoin-worth-saving
michaellamden68upvoted (100.00%) @steves / is-bitcoin-worth-saving
| voter | michaellamden68 |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3787128/Trx 69fe449de839d7f69542a6d3668e752f28f57517 |
View Raw JSON Data
{
"trx_id": "69fe449de839d7f69542a6d3668e752f28f57517",
"block": 3787128,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:32:15",
"op": [
"vote",
{
"voter": "michaellamden68",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10000
}
]
}cheremetupvoted (0.10%) @steves / is-bitcoin-worth-saving
cheremetupvoted (0.10%) @steves / is-bitcoin-worth-saving
| voter | cheremet |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10 (0.10%) |
| Transaction Info | Block #3787096/Trx 9ccd72ea94af555fc0da50de6a960ea4b320fa97 |
View Raw JSON Data
{
"trx_id": "9ccd72ea94af555fc0da50de6a960ea4b320fa97",
"block": 3787096,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:30:39",
"op": [
"vote",
{
"voter": "cheremet",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10
}
]
}cheremetreplied to @steves / is-bitcoin-worth-saving
cheremetreplied to @steves / is-bitcoin-worth-saving
| parent author | steves |
| parent permlink | is-bitcoin-worth-saving |
| author | cheremet |
| permlink | is-bitcoin-worth-saving |
| title | |
| body | Keep up the great work @steves Upvoted |
| json metadata | |
| Transaction Info | Block #3787095/Trx 4f1a6f4dd131df14bc70f8dccc10a66fe91c95e9 |
View Raw JSON Data
{
"trx_id": "4f1a6f4dd131df14bc70f8dccc10a66fe91c95e9",
"block": 3787095,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:30:36",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "is-bitcoin-worth-saving",
"author": "cheremet",
"permlink": "is-bitcoin-worth-saving",
"title": "",
"body": "Keep up the great work @steves \n Upvoted ",
"json_metadata": ""
}
]
}stevesupvoted (100.00%) @steves / is-bitcoin-worth-saving
stevesupvoted (100.00%) @steves / is-bitcoin-worth-saving
| voter | steves |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3787072/Trx 95767779171c4bba75494c2f0de9c95513ab35f3 |
View Raw JSON Data
{
"trx_id": "95767779171c4bba75494c2f0de9c95513ab35f3",
"block": 3787072,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:29:27",
"op": [
"vote",
{
"voter": "steves",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"weight": 10000
}
]
}stevespublished a new post: is-bitcoin-worth-saving
stevespublished a new post: is-bitcoin-worth-saving
| parent author | |
| parent permlink | bitcoin |
| author | steves |
| permlink | is-bitcoin-worth-saving |
| title | Is Bitcoin worth saving? |
| body | Hello! Anyone who has been using the Bitcoin network recently knows that events are quickly approaching a turning point. The Chinese miners have reneged on their promise to fork the Bitcoin network on August 1, adding yet another lie to a series of their dishonest statements dating back for years. There no longer appears to be any chance that the existing people involved with Bitcoin, most of whom continue to lie and take no action, will do anything to resolve Bitcoin's usability problems. As I suggested a few months ago, there is not enough time for the world to wait for the Lightning Network or for one of the complex solutions the Core wants to implement. While some are trying to explain the breach of support in bitcoin price as a short-term panic over recent meetings, I suspect that few believe these "discussions" will accomplish anything more than the tens of expensive conferences and "meetups" have over the past year. Instead, the bitcoin price is likely falling due to a more fundamental issue - the network is unusuable. A few days ago, we rushed to sell all of our Ethereum Classic (ETC). We decided to convert it to 40 ETH and $170, but mistakenly forgot that the GDAX supported ETH - so we thought we had to use BTC to send the cash to be sold as dollars to the GDAX. It took about 24 hours between the time that Chris began to transfer the BTC until we submitted the ACH request. The BTC transfer took 18 hours to confirm, and the confirmations happened while he was asleep, and then he had to come back later and log in, wait for my cell phone because his is associated with another account, and execute the trade. Meanwhile, Chris withdrew the ETH to an offline wallet, where it was received and confirmed in about 30 seconds. The transaction cost 1/100 of the BTC transfer. Until now, BTC was the only product supported by most exchanges and businesses. When Coinbase added ETH to its wallets, that changed. We will never again use BTC to sell out to dollars, because the opportunity cost in Chris's time in having to log in again later is enormous. With ETH, we can get our profit to the GDAX and converted to dollars within a few minutes, using only one login session. Plus, the gas costs for Ethereum are so much lower that it just doesn't make sense to use BTC when transferring money between customers anymore. We have a task in our bugtracking system to convert the currency we fund customers' Coinbase dollar payouts with into ETH so that we can retain more profit from the reduced fees. This is a small change that we estimate will save $300/yr even if BTC fees never increase any more. In many of the non-censored Bitcoin forums, it seems that a movement is brewing to hard fork the Bitcoin blockchain without consulting miners. There are multiple suggestions being considered. One idea is to use merge mining like I proposed on July 12. There is already code written to use scrypt, in order to get rid of the Chinese miners while still providing ASIC protection. User singularity87 wants to use a new proof of work algorithm, one which can be mined with GPUs, at least initially. The major disagreement between all the users seems to be about how the blocksize limit should be increased in the fork, with some people believing that the problem should be resolved permanently and others believing that it will be possible to hard fork again later. While I don't think there is a need for a blocksize limit at all, I fully support all of these efforts and believe that Bitcoin will be better off if someone makes a last-ditch effort before the network begins to collapse. However, as I've thought about these plans, the enormity of the work required to pull them off becomes very plain. It would take hundreds of hours in a very short period of time to get a fork client ready for release. Advertising would be needed, and someone would have to contact and work with exchanges to support the fork. If the fork includes a new transaction format to prevent replay attacks as some are suggesting, backwards compatibility will be broken and that alone may doom the effort. Testing may reveal a critical flaw that requires significant rework. Even then, the odds of getting significant support from businesses and others who actually use the network is low. Like Ethereum Classic, it would likely initially be propped up by people pushing a political ideology, but eventually the supply of those type of people will run out and actual users will determine the coin's success. The effort required is huge, and there nobody has stated he will work the 80 hours per week required for the next few months to lead everyone and get the fork released. Even if the code is able to be tested, and released, and exchanges support it, and support grows, and the old chain becomes worth very little, and it has users beyond the initial political protestors, it will not resolve most of the problems currently present. Even if scrypt successfully bankrupts the Chinese miners, people like Michael Marquadt and Gregory Maxwell aren't going to disappear; they will likely continue to participate in the new currency. Marquadt will still control all of the Bitcoin media, and the DDoS attackers will continue to fight. And in the end, the system will still be technically inferior to many altcoins. Nobody has yet convinced me why so much time should be dedicated to forking Bitcoin, and that's why I haven't joined any of these efforts. A few months ago, forking Bitcoin seemed like the best solution, but since then Ethereum support has grown dramatically. The most important change is the addition of trading pairs for ETH at exchanges, and within the past few weeks it is now possible to use ETH interchangeably with Bitcoin for transferring value. Ethereum already has blocks 50 times faster than Bitcoin's, it long ago solved the blocksize problem, it has competent leadership, and the level of ethics amongst its Core contributors is higher. It can do everything Bitcoin can do and more. In conclusion, while I would love to see Bitcoin fork, I think that the time for that has probably passed. If everyone is going to devote thousands of hours to creating a Bitcoin fork just to end up with a marginally better system hindered by some of the same problems that exist today, isn't it better to devote that time to converting existing applications to Ethereum instead? There already exists a system that is tested, widely supported, and outperforms Bitcoin in every way. Those who are considering forking the Bitcoin network should consider that it may be worth letting Bitcoin decline, instead of putting more work into a system to produce something that, even in the best case, will now be an inferior product. Thanks @steves |
| json metadata | {"tags":["bitcoin"],"users":["steves"]} |
| Transaction Info | Block #3787072/Trx 95767779171c4bba75494c2f0de9c95513ab35f3 |
View Raw JSON Data
{
"trx_id": "95767779171c4bba75494c2f0de9c95513ab35f3",
"block": 3787072,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T11:29:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "steves",
"permlink": "is-bitcoin-worth-saving",
"title": "Is Bitcoin worth saving?",
"body": "Hello! Anyone who has been using the Bitcoin network recently knows that events are quickly approaching a turning point. The Chinese miners have reneged on their promise to fork the Bitcoin network on August 1, adding yet another lie to a series of their dishonest statements dating back for years. There no longer appears to be any chance that the existing people involved with Bitcoin, most of whom continue to lie and take no action, will do anything to resolve Bitcoin's usability problems. As I suggested a few months ago, there is not enough time for the world to wait for the Lightning Network or for one of the complex solutions the Core wants to implement.\n\nWhile some are trying to explain the breach of support in bitcoin price as a short-term panic over recent meetings, I suspect that few believe these \"discussions\" will accomplish anything more than the tens of expensive conferences and \"meetups\" have over the past year. Instead, the bitcoin price is likely falling due to a more fundamental issue - the network is unusuable.\n\nA few days ago, we rushed to sell all of our Ethereum Classic (ETC). We decided to convert it to 40 ETH and $170, but mistakenly forgot that the GDAX supported ETH - so we thought we had to use BTC to send the cash to be sold as dollars to the GDAX. It took about 24 hours between the time that Chris began to transfer the BTC until we submitted the ACH request. The BTC transfer took 18 hours to confirm, and the confirmations happened while he was asleep, and then he had to come back later and log in, wait for my cell phone because his is associated with another account, and execute the trade. Meanwhile, Chris withdrew the ETH to an offline wallet, where it was received and confirmed in about 30 seconds. The transaction cost 1/100 of the BTC transfer.\n\nUntil now, BTC was the only product supported by most exchanges and businesses. When Coinbase added ETH to its wallets, that changed. We will never again use BTC to sell out to dollars, because the opportunity cost in Chris's time in having to log in again later is enormous. With ETH, we can get our profit to the GDAX and converted to dollars within a few minutes, using only one login session. Plus, the gas costs for Ethereum are so much lower that it just doesn't make sense to use BTC when transferring money between customers anymore. We have a task in our bugtracking system to convert the currency we fund customers' Coinbase dollar payouts with into ETH so that we can retain more profit from the reduced fees. This is a small change that we estimate will save $300/yr even if BTC fees never increase any more.\n\nIn many of the non-censored Bitcoin forums, it seems that a movement is brewing to hard fork the Bitcoin blockchain without consulting miners. There are multiple suggestions being considered. One idea is to use merge mining like I proposed on July 12. There is already code written to use scrypt, in order to get rid of the Chinese miners while still providing ASIC protection. User singularity87 wants to use a new proof of work algorithm, one which can be mined with GPUs, at least initially.\n\nThe major disagreement between all the users seems to be about how the blocksize limit should be increased in the fork, with some people believing that the problem should be resolved permanently and others believing that it will be possible to hard fork again later. While I don't think there is a need for a blocksize limit at all, I fully support all of these efforts and believe that Bitcoin will be better off if someone makes a last-ditch effort before the network begins to collapse.\n\nHowever, as I've thought about these plans, the enormity of the work required to pull them off becomes very plain. It would take hundreds of hours in a very short period of time to get a fork client ready for release. Advertising would be needed, and someone would have to contact and work with exchanges to support the fork. If the fork includes a new transaction format to prevent replay attacks as some are suggesting, backwards compatibility will be broken and that alone may doom the effort. Testing may reveal a critical flaw that requires significant rework.\n\nEven then, the odds of getting significant support from businesses and others who actually use the network is low. Like Ethereum Classic, it would likely initially be propped up by people pushing a political ideology, but eventually the supply of those type of people will run out and actual users will determine the coin's success. The effort required is huge, and there nobody has stated he will work the 80 hours per week required for the next few months to lead everyone and get the fork released.\n\nEven if the code is able to be tested, and released, and exchanges support it, and support grows, and the old chain becomes worth very little, and it has users beyond the initial political protestors, it will not resolve most of the problems currently present. Even if scrypt successfully bankrupts the Chinese miners, people like Michael Marquadt and Gregory Maxwell aren't going to disappear; they will likely continue to participate in the new currency. Marquadt will still control all of the Bitcoin media, and the DDoS attackers will continue to fight. And in the end, the system will still be technically inferior to many altcoins.\n\nNobody has yet convinced me why so much time should be dedicated to forking Bitcoin, and that's why I haven't joined any of these efforts. A few months ago, forking Bitcoin seemed like the best solution, but since then Ethereum support has grown dramatically. The most important change is the addition of trading pairs for ETH at exchanges, and within the past few weeks it is now possible to use ETH interchangeably with Bitcoin for transferring value. Ethereum already has blocks 50 times faster than Bitcoin's, it long ago solved the blocksize problem, it has competent leadership, and the level of ethics amongst its Core contributors is higher. It can do everything Bitcoin can do and more.\n\nIn conclusion, while I would love to see Bitcoin fork, I think that the time for that has probably passed. If everyone is going to devote thousands of hours to creating a Bitcoin fork just to end up with a marginally better system hindered by some of the same problems that exist today, isn't it better to devote that time to converting existing applications to Ethereum instead? There already exists a system that is tested, widely supported, and outperforms Bitcoin in every way. Those who are considering forking the Bitcoin network should consider that it may be worth letting Bitcoin decline, instead of putting more work into a system to produce something that, even in the best case, will now be an inferior product. \n\nThanks \n\n@steves",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"users\":[\"steves\"]}"
}
]
}| parent author | steves |
| parent permlink | dark-day-cryptocurrency-s |
| author | vladon |
| permlink | re-steves-dark-day-cryptocurrency-s-20160804t001903800z |
| title | |
| body | Read the original bitcoin white paper written by the mysterious Satoshi Nakamoto- http://bitcoinx.io/bitcoin-a-peer-to-peer-electronic-cash-system |
| json metadata | {"tags":["ethereum"],"links":["http://bitcoinx.io/bitcoin-a-peer-to-peer-electronic-cash-system"]} |
| Transaction Info | Block #3773704/Trx f41e505157f03f8ea3f6835b0fd8f3a1c6ae4491 |
View Raw JSON Data
{
"trx_id": "f41e505157f03f8ea3f6835b0fd8f3a1c6ae4491",
"block": 3773704,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T00:19:06",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "dark-day-cryptocurrency-s",
"author": "vladon",
"permlink": "re-steves-dark-day-cryptocurrency-s-20160804t001903800z",
"title": "",
"body": "Read the original bitcoin white paper written by the mysterious Satoshi Nakamoto- http://bitcoinx.io/bitcoin-a-peer-to-peer-electronic-cash-system",
"json_metadata": "{\"tags\":[\"ethereum\"],\"links\":[\"http://bitcoinx.io/bitcoin-a-peer-to-peer-electronic-cash-system\"]}"
}
]
}vladonupvoted (100.00%) @steves / dark-day-cryptocurrency-s
vladonupvoted (100.00%) @steves / dark-day-cryptocurrency-s
| voter | vladon |
| author | steves |
| permlink | dark-day-cryptocurrency-s |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3773582/Trx 4e032e007996733bdaa90f786a5463eb2b5e9b81 |
View Raw JSON Data
{
"trx_id": "4e032e007996733bdaa90f786a5463eb2b5e9b81",
"block": 3773582,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-04T00:13:00",
"op": [
"vote",
{
"voter": "vladon",
"author": "steves",
"permlink": "dark-day-cryptocurrency-s",
"weight": 10000
}
]
}leonaugusupvoted (100.00%) @steves / dark-day-cryptocurrency-s
leonaugusupvoted (100.00%) @steves / dark-day-cryptocurrency-s
| voter | leonaugus |
| author | steves |
| permlink | dark-day-cryptocurrency-s |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3772571/Trx 68d8dbcd057eb25eb3082b815bc82cd9eadaeded |
View Raw JSON Data
{
"trx_id": "68d8dbcd057eb25eb3082b815bc82cd9eadaeded",
"block": 3772571,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T23:22:24",
"op": [
"vote",
{
"voter": "leonaugus",
"author": "steves",
"permlink": "dark-day-cryptocurrency-s",
"weight": 10000
}
]
}| parent author | steves |
| parent permlink | dark-day-cryptocurrency-s |
| author | steves |
| permlink | re-steves-dark-day-cryptocurrency-s-20160803t230921300z |
| title | |
| body | This is my first post to the Steemit. |
| json metadata | {"tags":["ethereum"]} |
| Transaction Info | Block #3772311/Trx 6ff57ca5671b905506b838cf7e909c0c98073087 |
View Raw JSON Data
{
"trx_id": "6ff57ca5671b905506b838cf7e909c0c98073087",
"block": 3772311,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T23:09:24",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "dark-day-cryptocurrency-s",
"author": "steves",
"permlink": "re-steves-dark-day-cryptocurrency-s-20160803t230921300z",
"title": "",
"body": "This is my first post to the Steemit.",
"json_metadata": "{\"tags\":[\"ethereum\"]}"
}
]
}allmonitorsupvoted (100.00%) @steves / dark-day-cryptocurrency-s
allmonitorsupvoted (100.00%) @steves / dark-day-cryptocurrency-s
| voter | allmonitors |
| author | steves |
| permlink | dark-day-cryptocurrency-s |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3771370/Trx 551e2a8bc5acea8ea16bad473a8dac7e9b3255e5 |
View Raw JSON Data
{
"trx_id": "551e2a8bc5acea8ea16bad473a8dac7e9b3255e5",
"block": 3771370,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:22:12",
"op": [
"vote",
{
"voter": "allmonitors",
"author": "steves",
"permlink": "dark-day-cryptocurrency-s",
"weight": 10000
}
]
}litaliupvoted (100.00%) @steves / dark-day-cryptocurrency-s
litaliupvoted (100.00%) @steves / dark-day-cryptocurrency-s
| voter | litali |
| author | steves |
| permlink | dark-day-cryptocurrency-s |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3771362/Trx cfafedb13ddc45a6394c346b9fce552c2e41d0b0 |
View Raw JSON Data
{
"trx_id": "cfafedb13ddc45a6394c346b9fce552c2e41d0b0",
"block": 3771362,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:21:48",
"op": [
"vote",
{
"voter": "litali",
"author": "steves",
"permlink": "dark-day-cryptocurrency-s",
"weight": 10000
}
]
}joujou666upvoted (0.10%) @steves / dark-day-cryptocurrency-s
joujou666upvoted (0.10%) @steves / dark-day-cryptocurrency-s
| voter | joujou666 |
| author | steves |
| permlink | dark-day-cryptocurrency-s |
| weight | 10 (0.10%) |
| Transaction Info | Block #3771343/Trx b78da68e7eefc96d4dd5aa43909c03b24d215e2a |
View Raw JSON Data
{
"trx_id": "b78da68e7eefc96d4dd5aa43909c03b24d215e2a",
"block": 3771343,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:20:51",
"op": [
"vote",
{
"voter": "joujou666",
"author": "steves",
"permlink": "dark-day-cryptocurrency-s",
"weight": 10
}
]
}joujou666replied to @steves / dark-day-cryptocurrency-s
joujou666replied to @steves / dark-day-cryptocurrency-s
| parent author | steves |
| parent permlink | dark-day-cryptocurrency-s |
| author | joujou666 |
| permlink | dark-day-cryptocurrency-s |
| title | |
| body | Keep up the great work @steves Upvoted |
| json metadata | |
| Transaction Info | Block #3771342/Trx 1f16504bea2701ee89739844cfaaab809e063027 |
View Raw JSON Data
{
"trx_id": "1f16504bea2701ee89739844cfaaab809e063027",
"block": 3771342,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:20:48",
"op": [
"comment",
{
"parent_author": "steves",
"parent_permlink": "dark-day-cryptocurrency-s",
"author": "joujou666",
"permlink": "dark-day-cryptocurrency-s",
"title": "",
"body": "Keep up the great work @steves \n Upvoted ",
"json_metadata": ""
}
]
}stevesupvoted (100.00%) @steves / dark-day-cryptocurrency-s
stevesupvoted (100.00%) @steves / dark-day-cryptocurrency-s
| voter | steves |
| author | steves |
| permlink | dark-day-cryptocurrency-s |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3771330/Trx 055ce57d52232042763727f815a3f780e7d0eeff |
View Raw JSON Data
{
"trx_id": "055ce57d52232042763727f815a3f780e7d0eeff",
"block": 3771330,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:20:12",
"op": [
"vote",
{
"voter": "steves",
"author": "steves",
"permlink": "dark-day-cryptocurrency-s",
"weight": 10000
}
]
}stevespublished a new post: dark-day-cryptocurrency-s
stevespublished a new post: dark-day-cryptocurrency-s
| parent author | |
| parent permlink | ethereum |
| author | steves |
| permlink | dark-day-cryptocurrency-s |
| title | Dark day cryptocurrency's |
| body | Hello respected Steemit community. Eight years ago today, with two days remaining until the Games, the focus in world news was on preparations for the Summer Olympics. After years of economic growth and a winding down of the wars against terrorism, the world was turning a corner. Just as it seemed that the inevitable march of progress continued forward, Russia suddenly invaded Georgia, seizing control of South Ossetia. A series of events that followed, including the stark authoritarianism on display at the opening ceremony two days later, showed everyone that what we had thought was progress was actually an illusion: the world's most brutal dictatorships reminded us they were still there and that they were superior at taking decisive action to accomplish massive tasks quickly. Shortly after the closing ceremony, the economy in the West then crashed, shattering the economic prosperity that was thought to be certain to continue. With two days remaining until this year's Summer Olympics, we are once again reminded that what seems like progress is often a façade that easily crumbles. Tuesday, August 2, 2016 will be remembered as one of the darkest days in cryptocurrency's history. After months of headlines where it appeared that businesses and financial institutions were finally coming around to Bitcoin, Ethereum, and other blockchain technologies, cryptocurrency took two huge steps back yesterday. Rather than continued growth, the latest events have set back progress and reminded everyone of the dark instincts of many cryptocurrency users. The scum of the planet rejoiced in their $70m haul from Bitfinex and their success in achieving a valuation of stolen funds on ETC of at least $20m. The Bitfinex hack has destroyed lives and set back bitcoin's development. The theft itself, having occurred so many years after criminals stole money from a number of other institutions, brings to the forefront a fundamental question posed by user moral_agent last year: if thefts keep happening over and over, is it even possible for humans to secure cryptocurrencies? This fact is assumed to be true despite the mounting evidence that it is not possible to secure cryptocurrency with the confidence necessary to operate business models which rely on large amounts of money. The industry is at a point where it needs to consider whether the current design of cryptocurrency is fatally flawed, because the theoretical possibility of securing coins is not playing out in reality. But as bad as Bitfinex is, the rise in the valuation of Ethereum Classic (ETC) is even worse. ETC's rise isn't as shocking, visible, or quick as the Bitfinex hack, but it also represents a transfer of wealth to thieves and hackers. We definitely know that 1/8 of the entire ETC value is held by the DAO thieves or the various subsequent attackers alone. When the replay attacks against Coinbase and other exchanges are included, it wouldn't be surprising to find that 17% or even 20% of all ETC is held by criminals. These criminals have been placing ads on reddit and in forums advertising ETC as an investment, a tactic reminiscent of those used to pump penny stocks. People who place buy orders in ETC slowly bleed out money to the criminals, who have done a masterful job at hijacking a political ideology to enrich themselves. When the hype dries up, the ETC thieves will have stolen millions of dollars, just as their kin did at Bitfinex. With ETC, the theft is worse because the buyers have no recourse, and the perpetrators are much less likely to be caught. Few people seem to recognize that what is occurring actually is theft, because the money is flowing so slowly towards the thieves. Both Bitfinex and ETC lay bare the hypocrisy of many people involved in crytocurrency. Bitfinex exposes the mismanagement of the US government, which has been wasting the tax dollars that people like me slave away every day to give them. They devote taskforces of highly paid agents and prosecutors to arrest people who sell a few bitcoins to someone who buys weed. Meanwhile, Alex Green, Paul Vernon, and a large number of other scam artists who actually ruined people's lives remain at large. There is little reason to suspect that the theft of Bitfinex's coins will be investigated any more thoroughly. While the government jails people who handle money involved with drugs, hackers repeatedly execute some of the largest bank robberies in the history of the world - because they see the number of agents devoted to those investigations is dwarfed by those assigned to deal with drugs. With ETC, we see that a large number of normal cryptocurrency users, some of whom are the same people who loudly protest that they were ruined by Bitfinex, are willing to turn a blind eye to actual criminal activity that hurts other people. Barry Silbert, an investor who claims to support the emerging blockchain industry and who gives funding to cryptocurrency companies, took to twitter to recommend Ethereum Classic. Like many others who loudly complain about blockchain security (until they see an opportunity to get rich), Silbert carries on about the promise of blockchains for legitimate companies while at the same time siding with a blockchain where, if it were to succeed, thousands of people would have seen their DAO tokens transferred to the hands of criminals. The general public, rightly so, sees cryptocurrency as a haven for illegal activity because hypocritical people like Silbert claim one thing and then do another. Thus, seven years after bitcoin was founded, we find ourselves back to the same old scams, thefts, and shady characters. Just when it looked like people like Mark Karpeles and Trendon Shavers were done for and the industry had moved on, cryptocurrency took one of the biggest steps backward in its history yesterday. Over the next few months, we can look forward to another bankruptcy proceeding. We can look forward to the panic that will ensue when the criminals cash out of Ethereum Classic and leave investors with nothing. And since it's only a matter of time, we can also look forward to the protracted battle when someone finally decides to be bold and hard forks Bitcoin Core. Yesterday, the illusion of progress was shattered. The same problems continue to plague the industry, and the same battles are being waged over and over and over. While I would like to be optimistic about the future, cryptocurrency will never be successful if criminals are allowed to roam free and hackers are rewarded on the basis of political ideology. After seven entire years, there is still no sign that honest, ethical people will ever be rewarded in this arena, and unless that changes, it will be the industry's fatal flaw. Thanks.... @steves |
| json metadata | {"tags":["ethereum"],"users":["steves"]} |
| Transaction Info | Block #3771330/Trx 055ce57d52232042763727f815a3f780e7d0eeff |
View Raw JSON Data
{
"trx_id": "055ce57d52232042763727f815a3f780e7d0eeff",
"block": 3771330,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:20:12",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ethereum",
"author": "steves",
"permlink": "dark-day-cryptocurrency-s",
"title": "Dark day cryptocurrency's",
"body": "Hello respected Steemit community. Eight years ago today, with two days remaining until the Games, the focus in world news was on preparations for the Summer Olympics. After years of economic growth and a winding down of the wars against terrorism, the world was turning a corner. Just as it seemed that the inevitable march of progress continued forward, Russia suddenly invaded Georgia, seizing control of South Ossetia. A series of events that followed, including the stark authoritarianism on display at the opening ceremony two days later, showed everyone that what we had thought was progress was actually an illusion: the world's most brutal dictatorships reminded us they were still there and that they were superior at taking decisive action to accomplish massive tasks quickly. Shortly after the closing ceremony, the economy in the West then crashed, shattering the economic prosperity that was thought to be certain to continue.\n\nWith two days remaining until this year's Summer Olympics, we are once again reminded that what seems like progress is often a façade that easily crumbles. Tuesday, August 2, 2016 will be remembered as one of the darkest days in cryptocurrency's history. After months of headlines where it appeared that businesses and financial institutions were finally coming around to Bitcoin, Ethereum, and other blockchain technologies, cryptocurrency took two huge steps back yesterday. Rather than continued growth, the latest events have set back progress and reminded everyone of the dark instincts of many cryptocurrency users. The scum of the planet rejoiced in their $70m haul from Bitfinex and their success in achieving a valuation of stolen funds on ETC of at least $20m.\n\nThe Bitfinex hack has destroyed lives and set back bitcoin's development. The theft itself, having occurred so many years after criminals stole money from a number of other institutions, brings to the forefront a fundamental question posed by user moral_agent last year: if thefts keep happening over and over, is it even possible for humans to secure cryptocurrencies? This fact is assumed to be true despite the mounting evidence that it is not possible to secure cryptocurrency with the confidence necessary to operate business models which rely on large amounts of money. The industry is at a point where it needs to consider whether the current design of cryptocurrency is fatally flawed, because the theoretical possibility of securing coins is not playing out in reality.\n\nBut as bad as Bitfinex is, the rise in the valuation of Ethereum Classic (ETC) is even worse. ETC's rise isn't as shocking, visible, or quick as the Bitfinex hack, but it also represents a transfer of wealth to thieves and hackers. We definitely know that 1/8 of the entire ETC value is held by the DAO thieves or the various subsequent attackers alone. When the replay attacks against Coinbase and other exchanges are included, it wouldn't be surprising to find that 17% or even 20% of all ETC is held by criminals. These criminals have been placing ads on reddit and in forums advertising ETC as an investment, a tactic reminiscent of those used to pump penny stocks.\n\nPeople who place buy orders in ETC slowly bleed out money to the criminals, who have done a masterful job at hijacking a political ideology to enrich themselves. When the hype dries up, the ETC thieves will have stolen millions of dollars, just as their kin did at Bitfinex. With ETC, the theft is worse because the buyers have no recourse, and the perpetrators are much less likely to be caught. Few people seem to recognize that what is occurring actually is theft, because the money is flowing so slowly towards the thieves.\n\nBoth Bitfinex and ETC lay bare the hypocrisy of many people involved in crytocurrency. Bitfinex exposes the mismanagement of the US government, which has been wasting the tax dollars that people like me slave away every day to give them. They devote taskforces of highly paid agents and prosecutors to arrest people who sell a few bitcoins to someone who buys weed. Meanwhile, Alex Green, Paul Vernon, and a large number of other scam artists who actually ruined people's lives remain at large. There is little reason to suspect that the theft of Bitfinex's coins will be investigated any more thoroughly. While the government jails people who handle money involved with drugs, hackers repeatedly execute some of the largest bank robberies in the history of the world - because they see the number of agents devoted to those investigations is dwarfed by those assigned to deal with drugs.\n\nWith ETC, we see that a large number of normal cryptocurrency users, some of whom are the same people who loudly protest that they were ruined by Bitfinex, are willing to turn a blind eye to actual criminal activity that hurts other people. Barry Silbert, an investor who claims to support the emerging blockchain industry and who gives funding to cryptocurrency companies, took to twitter to recommend Ethereum Classic. Like many others who loudly complain about blockchain security (until they see an opportunity to get rich), Silbert carries on about the promise of blockchains for legitimate companies while at the same time siding with a blockchain where, if it were to succeed, thousands of people would have seen their DAO tokens transferred to the hands of criminals. The general public, rightly so, sees cryptocurrency as a haven for illegal activity because hypocritical people like Silbert claim one thing and then do another.\n\nThus, seven years after bitcoin was founded, we find ourselves back to the same old scams, thefts, and shady characters. Just when it looked like people like Mark Karpeles and Trendon Shavers were done for and the industry had moved on, cryptocurrency took one of the biggest steps backward in its history yesterday. Over the next few months, we can look forward to another bankruptcy proceeding. We can look forward to the panic that will ensue when the criminals cash out of Ethereum Classic and leave investors with nothing. And since it's only a matter of time, we can also look forward to the protracted battle when someone finally decides to be bold and hard forks Bitcoin Core.\n\nYesterday, the illusion of progress was shattered. The same problems continue to plague the industry, and the same battles are being waged over and over and over. While I would like to be optimistic about the future, cryptocurrency will never be successful if criminals are allowed to roam free and hackers are rewarded on the basis of political ideology. After seven entire years, there is still no sign that honest, ethical people will ever be rewarded in this arena, and unless that changes, it will be the industry's fatal flaw. \n\nThanks....\n\n@steves",
"json_metadata": "{\"tags\":[\"ethereum\"],\"users\":[\"steves\"]}"
}
]
}| voter | steves |
| author | b0y2k |
| permlink | convert-your-steem-dollars-to-physical-money-to-spend-or-withdraw-anywhere-part-2 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3771169/Trx 9d65c9c9ae9622511b50136ac5e15a312cc46482 |
View Raw JSON Data
{
"trx_id": "9d65c9c9ae9622511b50136ac5e15a312cc46482",
"block": 3771169,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:12:09",
"op": [
"vote",
{
"voter": "steves",
"author": "b0y2k",
"permlink": "convert-your-steem-dollars-to-physical-money-to-spend-or-withdraw-anywhere-part-2",
"weight": 10000
}
]
}| voter | steves |
| author | cryptoctopus |
| permlink | bookmark-this-a-grandma-proof-way-of-cashing-out-your-hard-earned-steem-dollars-in-the-bank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3771166/Trx 042bbb126a25252d380827eb2527d34e3949eadf |
View Raw JSON Data
{
"trx_id": "042bbb126a25252d380827eb2527d34e3949eadf",
"block": 3771166,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:12:00",
"op": [
"vote",
{
"voter": "steves",
"author": "cryptoctopus",
"permlink": "bookmark-this-a-grandma-proof-way-of-cashing-out-your-hard-earned-steem-dollars-in-the-bank",
"weight": 10000
}
]
}| voter | steves |
| author | rok-sivante |
| permlink | the-evil-steemit-whale-bot-conspiracy-an-elite-crypto-agenda-for-minnow-domination-or-sound-investment-strategy-for-the |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3771164/Trx a68b40b67f0304d856bf878a68ec34a6dead658a |
View Raw JSON Data
{
"trx_id": "a68b40b67f0304d856bf878a68ec34a6dead658a",
"block": 3771164,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:11:54",
"op": [
"vote",
{
"voter": "steves",
"author": "rok-sivante",
"permlink": "the-evil-steemit-whale-bot-conspiracy-an-elite-crypto-agenda-for-minnow-domination-or-sound-investment-strategy-for-the",
"weight": 10000
}
]
}| fee | 3.000 STEEM |
| creator | steem |
| new account name | steves |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM8in5nErFp8U3GeR4cnJmfyMBucP9FNsMtotiREDU2P8fdpTDzd",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5u4cZvojzz1w8Xu25ahvotsxUXSimAZeG18cBUV5oU8BJk3vPr",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5tCsx2Ez5wYD5HezG9EbHKpmfdE8Qo18FH2F4mZnksuPekgaEb",1]]} |
| memo key | STM5rWVyebBFXDixbYiBMgkHbGKuJAPWw7EmyoPKYsrgsPVwBoY8g |
| json metadata | |
| Transaction Info | Block #3771124/Trx 8f515bbf3214271680a4ed09252ba54e6cc4d098 |
View Raw JSON Data
{
"trx_id": "8f515bbf3214271680a4ed09252ba54e6cc4d098",
"block": 3771124,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2016-08-03T22:09:54",
"op": [
"account_create",
{
"fee": "3.000 STEEM",
"creator": "steem",
"new_account_name": "steves",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8in5nErFp8U3GeR4cnJmfyMBucP9FNsMtotiREDU2P8fdpTDzd",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5u4cZvojzz1w8Xu25ahvotsxUXSimAZeG18cBUV5oU8BJk3vPr",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5tCsx2Ez5wYD5HezG9EbHKpmfdE8Qo18FH2F4mZnksuPekgaEb",
1
]
]
},
"memo_key": "STM5rWVyebBFXDixbYiBMgkHbGKuJAPWw7EmyoPKYsrgsPVwBoY8g",
"json_metadata": ""
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress61.36%
{
"voting_manabar": {
"current_mana": 9950,
"last_update_time": 1475751063
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1470262194
},
"rc_account": {
"account": "steves",
"rc_manabar": {
"current_mana": "13715952893",
"last_update_time": 1537887600
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "13715952893"
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM8in5nErFp8U3GeR4cnJmfyMBucP9FNsMtotiREDU2P8fdpTDzd1/1
Active
Single Signature
Public Keys
STM5u4cZvojzz1w8Xu25ahvotsxUXSimAZeG18cBUV5oU8BJk3vPr1/1
Posting
Single Signature
Public Keys
STM5tCsx2Ez5wYD5HezG9EbHKpmfdE8Qo18FH2F4mZnksuPekgaEb1/1
Memo
STM5rWVyebBFXDixbYiBMgkHbGKuJAPWw7EmyoPKYsrgsPVwBoY8g
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8in5nErFp8U3GeR4cnJmfyMBucP9FNsMtotiREDU2P8fdpTDzd",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5u4cZvojzz1w8Xu25ahvotsxUXSimAZeG18cBUV5oU8BJk3vPr",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5tCsx2Ez5wYD5HezG9EbHKpmfdE8Qo18FH2F4mZnksuPekgaEb",
1
]
]
},
"memo": "STM5rWVyebBFXDixbYiBMgkHbGKuJAPWw7EmyoPKYsrgsPVwBoY8g"
}Witness Votes
0 / 30
No active witness votes.
[]