<html> <p><img src="https://cdn.pbrd.co/images/1SdrOZJY.jpg" width="725" height="368"/></p> <p>So far so kinda good in the Steemit world, but as those of us who are starting to get addicted to the platform realize, the increased traffic and popularity of the site will bring its own set of issues. Steemit is a startup and it is run by real people using real hardware, resources, and software. Add exponential growth in users, data, and economic value and that’s when things can start breaking down. </p> <p><ins><strong>Scalability</strong></ins></p> <p>The first big question is whether Steemit can scale to keep pace with its exponential growth? What level of traffic and content creation and data storage can the infrastructure handle? Just this morning I was having issues loading the site and basic functionality, like filtering tags hasn’t been working. </p> <p><ins><strong>Security</strong></ins></p> <p>Since Steemit runs on servers and has a bunch of users and network admins who are mere human beings, it’s reasonable to think the system is vulnerable to hackers. That’s scary because this isn’t Reddit, and we now have accumulating real economic value stored in accounts across the network. </p> <p>Network security for hosting the site and keeping it live involves a whole bunch of behind-the-scenes activities we’ll likely never really be privy to, but since we’re all stakeholders of varying degree in this fun experiment, it’d be nice to know that there’s serious thought and effort involved in keeping things running safely. </p> <p>Individual accounts are always as vulnerable as the users themselves, and sometimes we’re just straight-up outwitted by conniving hackers who infiltrate our systems. Steemit involves real money, though, so hacking an account here could mean serious money stolen; for better or worse, we don’t have recourse to calling our banks and crying to get refunded, nor do we have handy FDIC bailouts, so the full onus of securing our accounts is on us. That said, those really running things at Steemit should quickly get 2FA security features in place to help us layer up. </p> <p><ins><strong>Other Points of Failure</strong></ins></p> <p>Can courts and governments shut us down? Steemit is a startup that’s clearly crowdsourcing equity investment. This is an awesome idea economically because it’s creating a dedicated community with real interests in seeing it grow as enhanced stakeholders; a warm fuzzy feeling we don’t get from other social media platforms like Facebook, Twitter, or Reddit. But does anyone really understand the legal issues we’re up against? </p> <p>First of all, what’s our legal jurisdiction? Is Steemit a registered business, are we on the hook for legal compliance where our servers are located? How will the world view our little, but growing, hive? The user community is already spread around the world, and since anyone with some Bitcoin, Bitshares, or Ether can buy in as investors (including shareholders), there’s no way of actually pinning down who owns what in the long run. However, there are a handful of founders and early investors supporting this project, so, clearly, these people can be targeted and their resources made vulnerable. </p> <p>Finally, this experiment is all about decentralization and openness, censorship is something we censor. What implications does that have for copyright or trademark violations? What happens when one of our users posts material that someone else, or some company, decides violates their IP? It is guaranteed that it is merely just a matter of time before some court orders Steemit to remove content. Then what? Even worse, what happens when some douchebag jihadist posts a marketing pitch for ISIS and the FBI orders it taken down? </p> <p>Servers and people are always vulnerable and until projects like Maidsafe or other meshnets are operational, we need to plan ahead to make sure we avoid future catastrophe. It would be a disaster if the community exploded along with STEEM’s market cap and we had a single court decision to shut us down wipe out a billion dollars in value. </p> </html>
| author | cylonmaker2053 |
|---|---|
| permlink | steemit-infrastructure-security-scalability-and-points-of-failure |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues","steemit-ideas"]} |
| created | 2016-06-22 13:59:03 |
| last_update | 2016-06-22 14:09:42 |
| depth | 0 |
| children | 8 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 37.712 HBD |
| curator_payout_value | 37.621 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 4,188 |
| author_reputation | 9,195,287,625,027 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,378 |
| net_rshares | 29,688,656,211,712 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| lafona-miner | 0 | 2,916,665,887,200 | 100% | ||
| enki | 0 | 4,926,402,034,902 | 100% | ||
| lafona | 0 | 221,811,281,382 | 100% | ||
| tombstone | 0 | 19,247,528,200,000 | 100% | ||
| ihashfury | 0 | 916,996,592,562 | 100% | ||
| ajvest | 0 | 374,910,988,800 | 100% | ||
| benjojo | 0 | 588,789,986,529 | 100% | ||
| pheonike | 0 | 115,185,686,936 | 100% | ||
| konelectric | 0 | 915,075,749 | 100% | ||
| chitty | 0 | 5,749,426,729 | 100% | ||
| makishart | 0 | 535,786,578 | 100% | ||
| jamtaylor | 0 | 533,724,043 | 100% | ||
| coinbitgold | 0 | 5,954,021,157 | 100% | ||
| stellabelle | 0 | 5,698,936,949 | 100% | ||
| kenny-crane | 0 | 6,009,855,420 | 100% | ||
| anwenbaumeister | 0 | 307,197,221 | 100% | ||
| sean-king | 0 | 338,882,190,251 | 100% | ||
| finpunk | 0 | 301,782,482 | 100% | ||
| gtg | 0 | 27,547,358 | 100% | ||
| nicholasparr | 0 | 167,455,442 | 100% | ||
| aeoniumlie | 0 | 255,019,111 | 100% | ||
| alexriethmeier | 0 | 15,027,534,911 | 100% | ||
| the-traveller | 0 | 0 | 100% |
Very well written and well though out. I am very curious to find out the answers to your questions.
| author | anwenbaumeister |
|---|---|
| permlink | re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t140517291z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 14:05:21 |
| last_update | 2016-06-22 14:05:21 |
| depth | 1 |
| children | 0 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.058 HBD |
| curator_payout_value | 0.059 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 99 |
| author_reputation | 147,454,223,191,114 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,391 |
| net_rshares | 344,424,654,264 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| cylonmaker2053 | 0 | 344,424,654,264 | 100% |
<html> <p>In terms of website performance our underlying technology can easily scale. The primary database that powers steemit is the C++ code that runs the blockchain. This database is trivially replicated and kept in sync across the globe. (The power of blockchains). The internals are based upon the graphene code which is about as efficient as any database can be. I see no problem with scaling our database or our front end assuming we have steady / predictable growth. </p> <p>In terms of security, it is something we take very seriously. It is also something that is very difficult. Overall, our security is built on better fundamentals than most other blockchains for the following reasons:</p> <ol> <li>99% of the value is time-locked and secured by owner keys</li> <li>99% of activity is done with posting keys which don't have access to spend funds</li> <li>Keys never get sent to the server</li> </ol> <p>In the event our server is compromised, only users who load compromised HTML from our server are vulnerable. If this were to happen then most users would only have their posting key compromised. Fortunately, this does not compromise their funds. Some smaller set of users who login to do financial transactions with their active key could have it compromised as well. </p> <p>In the long run, the best security will take the form of a browser plugin that manages your keys and prevents Steemit.com from swaping out the JavaScript that loads your keys and signs messages.</p> <p>We are taking measures to deploy watchdog bots that automatically detect changes in the deployed HTML and alert us to changes. </p> <p>Nothing is perfect, but in terms of performance, scalability, and security I am sure our team is up to the task. </p> <p><br></p> </html>
| author | dantheman |
|---|---|
| permlink | re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t142812326z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 14:28:12 |
| last_update | 2016-06-22 14:28:12 |
| depth | 1 |
| children | 1 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 91.240 HBD |
| curator_payout_value | 91.238 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1,824 |
| author_reputation | 240,292,002,602,347 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,421 |
| net_rshares | 45,836,634,531,116 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| dantheman | 0 | 19,020,405,948,039 | 100% | ||
| proskynneo | 0 | 4,741,311,950,000 | 100% | ||
| tombstone | 0 | 19,247,528,200,000 | 100% | ||
| xeroc | 0 | 885,267,661,643 | 100% | ||
| testz | 0 | 15,185,291,419 | 100% | ||
| ajvest | 0 | 374,910,988,800 | 100% | ||
| benjojo | 0 | 588,789,986,529 | 100% | ||
| pheonike | 0 | 115,185,686,936 | 100% | ||
| konelectric | 0 | 897,133,087 | 100% | ||
| hipster | 0 | 512,906,025,404 | 100% | ||
| stellabelle | 0 | 5,698,936,949 | 100% | ||
| cylonmaker2053 | 0 | 328,546,722,310 | 100% |
What about open sourcing a client? It will give extra credit for users as well give community ability to improve security. Are you going to do this? When?
| author | hipster |
|---|---|
| permlink | re-dantheman-re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160624t124401204z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-24 12:44:00 |
| last_update | 2016-06-24 12:44:00 |
| depth | 2 |
| children | 0 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 1.313 HBD |
| curator_payout_value | 1.313 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 154 |
| author_reputation | 43,811,990,885,529 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 42,622 |
| net_rshares | 4,074,008,319,910 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| hipster | 0 | 561,317,825,404 | 100% | ||
| satoshifund | 0 | 3,512,497,411,885 | 100% | ||
| herethengone | 0 | 193,082,621 | 100% |
<html> <p>You may be on Steemit.com but this is just one web wallet for the Steem network which is a decentralized blockchain database built for security and scale with DPOS+POW consensus algorithms. If Steemit's servers go down, the blockchain will keep running and Steem community may access their account from other interfaces. Please read the terms of service and the Steem white paper.</p> </html>
| author | ned-reddit-login |
|---|---|
| permlink | re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t141742875z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 14:17:42 |
| last_update | 2016-06-22 14:18:42 |
| depth | 1 |
| children | 0 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.060 HBD |
| curator_payout_value | 0.060 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 408 |
| author_reputation | -681,981,461,850 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,406 |
| net_rshares | 350,123,591,213 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| stellabelle | 0 | 5,698,936,949 | 100% | ||
| cylonmaker2053 | 0 | 344,424,654,264 | 100% |
<html> <p>Glad to see folks thinking ahead! As a lawyer, I'm less concerned about the legal issues you raise and more concerned about the security issues, perhaps because my grasp of the latter is wanting.</p> <p>Legally, state censorship of Steemit would be incredibly difficult, at least once it reaches sufficient scale. Judges cannot order individuals to do things beyond their control. For instance, a judge cannot legally order me to paint the sky red. And, reversing entries on a sufficiently secure blockchain is the rough digital equivalent of painting the sky red. To the extent that such a reversal is possible at all, it could only be done by a large group of people (called "witnesses" in the Steemit system, I think) acting in concert. Provided that this group is sufficiently large and sufficiently distributed across multiple legal jurisdictions, successful state censorship becomes very, very unlikely. </p> <p>It's also unlikely that a judge (in the US at least) could compel a person to write code. Code is speech, and speech is Constitutionally protected. So, targeting developers probably isn't a winning strategy for the state either. </p> <p>Nonetheless there will be community policing and community censorship to some degree via the down voting process. It will be fascinating to see how that works and evolves. I imagine that organizations like ISIS would get down voted to irrelevance, but perhaps not. And perhaps they can find ways of gaming the system to work in their favor. </p> </html>
| author | sean-king |
|---|---|
| permlink | re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t143424871z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 14:34:24 |
| last_update | 2016-06-22 14:34:24 |
| depth | 1 |
| children | 1 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 66.796 HBD |
| curator_payout_value | 66.796 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1,638 |
| author_reputation | 84,123,051,136,467 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,430 |
| net_rshares | 38,943,639,373,300 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| dantheman | 0 | 19,020,464,696,957 | 100% | ||
| tombstone | 0 | 19,247,528,200,000 | 100% | ||
| sean-king | 0 | 331,180,322,290 | 100% | ||
| cylonmaker2053 | 0 | 344,424,654,264 | 100% | ||
| brianreecegreen | 0 | 41,499,789 | 100% |
I've already seen evidence of bad stuff being downvoted. As long as the hive is sane then the hive thrives.
| author | stellabelle |
|---|---|
| permlink | re-sean-king-re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t200307307z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 20:03:09 |
| last_update | 2016-06-22 20:03:09 |
| depth | 2 |
| children | 0 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.055 HBD |
| curator_payout_value | 0.055 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 107 |
| author_reputation | 516,061,669,130,124 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,720 |
| net_rshares | 323,671,536,951 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| sean-king | 0 | 323,478,454,330 | 100% | ||
| herethengone | 0 | 193,082,621 | 100% |
<html> <p>Steemit, Inc is not crowdsourcing equity investment. Steemit has mined, purchased, or earned all Steem in its possession. Steemit is a peer on the peer to peer network just like blockchain.info to Bitcoin. </p> <p><br></p> </html>
| author | steemitblog |
|---|---|
| permlink | re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t141054269z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 14:10:54 |
| last_update | 2016-06-22 14:10:54 |
| depth | 1 |
| children | 1 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 246 |
| author_reputation | 332,472,558,821,177 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,400 |
| net_rshares | 5,698,936,949 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| stellabelle | 0 | 5,698,936,949 | 100% |
<html> <p>It's nice to see a logical explanation following other precedent. The risk is that none of this has legal clarification yet, so hopefully there aren't unforeseen issues. Steem Power smells like equity investment since it implies some ownership stake and a vesting schedule for funds being locked up. </p> </html>
| author | cylonmaker2053 |
|---|---|
| permlink | re-steemitblog-re-cylonmaker2053-steemit-infrastructure-security-scalability-and-points-of-failure-20160622t141747469z |
| category | steemit-issues |
| json_metadata | {"tags":["steemit-issues"]} |
| created | 2016-06-22 14:17:48 |
| last_update | 2016-06-22 14:17:48 |
| depth | 2 |
| children | 0 |
| last_payout | 2016-08-20 12:03:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 327 |
| author_reputation | 9,195,287,625,027 |
| root_title | "Steemit infrastructure security, scalability, and points of failure" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 40,407 |
| net_rshares | 0 |
hiveblocks