Steemit.com: Blogging is the new Mining

[Supercomputing]

While they are resolving problem, they should rethink POW rewards, give more to miners and make more secure network

POS is a bullshit from the start, anyone defending it at full is just biased, POS should and will never survive without secure POW!

That would be nice but the Steemit platform has some other major security issues:

Depending on how a transaction was constructed, you can change the Security Keys of another user's account without their permission. See error log below:

    {"witness_owner":"supercomputing5"}
    th_a  database.cpp:700 operator()
3471006ms th_a       witness.cpp:383               maybe_produce_block  ] Clearing pending transactions and attempting again
3471006ms th_a       witness.cpp:382               maybe_produce_block  ] 10 assert_exception: Assert Exception
witness_obj.signing_key == block_signing_private_key.get_public_key():
    {}
    th_a  database.cpp:721 _generate_block

    {"witness_owner":"supercomputing5"}
    th_a  database.cpp:700 operator()
3471006ms th_a       witness.cpp:383               maybe_produce_block  ] Clearing pending transactions and attempting again
3471006ms th_a       witness.cpp:286               block_production_loo ] Failure when producing block with no transactions
3471999ms th_a       witness.cpp:274               block_production_loo ] Not producing block for supercomputing5 because I don't have the private key for STM5b3wkzd5cPuW8tYbHpsM6qo26R5eympAQsBaoEfeMDxxUCLvsY
3472999ms th_a       witness.cpp:274               block_production_loo ] Not producing block for supercomputing5 because I don't have the private key for STM5b3wkzd5cPuW8tYbHpsM6qo26R5eympAQsBaoEfeMDxxUCLvsY

[ljglug]

Why the mining will not succeed, has been such a state, has been in operation for more than a day

My system is Windows 7 X64

ransactions from network on block 4013269
291939ms th_a       witness.cpp:430               on_applied_block     ] hash ra
te: 82970 hps  target: 32 queue: 113 estimated time to produce: 862 minutes
294684ms th_a       witness.cpp:430               on_applied_block     ] hash ra
te: 82878 hps  target: 32 queue: 113 estimated time to produce: 863 minutes
294684ms th_a       application.cpp:439           handle_block         ] Got 1 t
ransactions from network on block 4013271
297524ms th_a       witness.cpp:430               on_applied_block     ] hash ra
te: 83110 hps  target: 32 queue: 113 estimated time to produce: 861 minutes
297524ms th_a       application.cpp:439           handle_block         ] Got 1 t
ransactions from network on block 4013272

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

My profile content:

rpc-endpoint = 127.0.0.1:8090
# Endpoint for P2P node to listen on
# p2p-endpoint =

# Maxmimum number of incoming connections on P2P endpoint
# p2p-max-connections =

# P2P nodes to connect to on startup (may specify multiple times)
seed-node = 85.214.65.220:2001

seed-node = 52.38.66.234:2001
seed-node = 52.37.169.52:2001
seed-node = 52.26.78.244:2001
seed-node = 192.99.4.226:2001
seed-node = 46.252.27.1:1337
seed-node = 81.89.101.133:2001
seed-node = 52.4.250.181:39705
seed-node = steemd.pharesim.me:2001
seed-node = seed.steemed.net:2001
seed-node = steem.clawmap.com:2001
seed-node = seed.steemwitness.com:2001
seed-node = steem-seed1.abit-more.com:200
# Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints.
# checkpoint =

# Endpoint for websocket RPC to listen on
# rpc-endpoint =

# Endpoint for TLS websocket RPC to listen on
# rpc-tls-endpoint =

# The TLS certificate file for this server
# server-pem =

# Password for this certificate
# server-pem-password =

# Block signing key to use for init witnesses, overrides genesis file
# dbg-init-key =

# API user specification, may be specified multiple times
# api-user =

# Set an API to be publicly available, may be specified multiple times
public-api = database_api login_api

# Plugin(s) to enable, may be specified multiple times
enable-plugin = witness account_history

# Defines a range of accounts to track as a json pair ["from","to"] [from,to)
# track-account-range =

# RPC endpoint of a trusted validating node (required)
# trusted-node =

# Track market history by grouping orders into buckets of equal size measured in seconds specified as a JSON array of numbers
bucket-size = [15,60,300,3600,86400]

# How far back in time to track history for each bucket size, measured in the number of buckets (default: 5760)
history-per-size = 5760

# Defines a range of accounts to private messages to/from as a json pair ["from","to"] [from,to)
# pm-account-range =

# Enable block production, even if the chain is stale.
enable-stale-production = false

# Percent of witnesses (0-99) that must be participating in order to produce blocks
required-participation = false

# name of witness controlled by this node (e.g. initwitness )
witness = "ljglug"

#name of miner and its private key (e.g. ["XXXXX","5KXXXXXXXXXXXXXXXXXXXXX"] )
miner =["XXXXXX","5KXXXXXXXXXXXXXXXXXXXXXXX"]

# Number of threads to use for proof of work mining
mining-threads =  30



# WIF PRIVATE KEY to be used by one or more witnesses or miners
# private-key =

# Account creation fee to be voted on upon successful POW - Minimum fee is 100.000 STEEM (written as 100000)
# miner-account-creation-fee =

# Maximum block size (in bytes) to be voted on upon successful POW - Max block size must be between 128 KB and 750 MB
# miner-maximum-block-size =

# SBD interest rate to be vote on upon successful POW - Default interest rate is 10% (written as 1000)
# miner-sbd-interest-rate =

# declare an appender named "stderr" that writes messages to the console
[log.console_appender.stderr]
stream=std_error

# declare an appender named "p2p" that writes messages to p2p.log
[log.file_appender.p2p]
filename=logs/p2p/p2p.log
# filename can be absolute or relative to this config file

# route any messages logged to the default logger to the "stderr" logger we
# declared above, if they are info level are higher
[logger.default]
level=warn
appenders=stderr

# route messages sent to the "p2p" logger to the p2p appender declared above
[logger.p2p]
level=warn
appenders=p2p

[Bubba-Gump]

WTB Vested accounts. 30M+ Vests. Serious inquiries only.

[ljglug]

WTB Vested accounts. 30M+ Vests. Serious inquiries only.

Is it right? Thank you for guidance!

[bones261]

Why the mining will not succeed, has been such a state, has been in operation for more than a day

According to this link, https://steemd.com/@ljglug, you found two recently. BTW after you find a POW block, your miner will stop while it waits in the witness queue. Do not disconnect your miner during this time. Solving the POW only puts you in the witness queue, you are actually rewarded when you become a witness and create a block. If your miner is offline when it is your time to create a block, you will miss it and not get the reward. To prevent down time, you may want to have a backup miner account. The backup miner account will then mine while your other account waits in the witness queue.

[remmacs]

if your looking for profits id consider Oracle Project which ends tonight.. some big investors jumping in https://bitcointalk.org/index.php?topic=1570693.0

oh im already in on that one 

[abitmore]

WTB Vested accounts. 30M+ Vests. Serious inquiries only.

I guess the price would be no more than 10BTC

[Bubba-Gump]

WTB Vested accounts. 30M+ Vests. Serious inquiries only.

I guess the price would be no more than 10BTC

I am looking to buy not sell.

[ljglug]

Why is there such a hint:

Now can not dig it?

3218029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3219029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3220039ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3221029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3222029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3223029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00

[bones261]

Why is there such a hint:

Now can not dig it?

3218029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3219029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3220039ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3221029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3222029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3223029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00

Yes, this indicates that you found a POW and you are now waiting in the miner witness queue for your time to actually create a POW block. Do not shut down your miner during this time. Nothing is wrong.  If you want to prevent the 2 hour down time, add a second miner or even a third or 4th. I'd add a link to an article in steemit on how to do this, but I don't want mprep to delete the post. So google it.

[ljglug]

Why is there such a hint:

Now can not dig it?

3218029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3219029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3220039ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3221029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3222029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3223029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00

Yes, this indicates that you found a POW and you are now waiting in the miner witness queue for your time to actually create a POW block. Do not shut down your miner during this time. Nothing is wrong.  If you want to prevent the 2 hour down time, add a second miner or even a third or 4th. I'd add a link to an article in steemit on how to do this, but I don't want mprep to delete the post. So google it.

Multiple accounts are required to register a different steemit account, using different user names and KEY ACTIVE to receive coins, that is not the resulting coins will be distributed to different steemit accounts?
Dig to the hard disk need to wait 2 years before it can be taken out?
Thank you ！

[amesterdamer]

MASSIVE preaching with Steemit's First ThunderClap Campaign [Now LIVE across Social Media]

Finally, the moment I've been waiting for 10 days. That moment when the Steemit's First Thunderclap Campaign goes live and hopefully a little bit viral!

LINK: https://steemit.com/steemit/@brunopro/massive-preaching-with-steemit-s-first-thunderclap-campaign-now-live-across-social-media

[bones261]

Why is there such a hint:

Now can not dig it?

3218029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3219029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3220039ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3221029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3222029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00
3223029ms th_a       witness.cpp:231               block_production_loo ] waitin
g until genesis time to produce block: 2016-03-24T16:00:00

Yes, this indicates that you found a POW and you are now waiting in the miner witness queue for your time to actually create a POW block. Do not shut down your miner during this time. Nothing is wrong.  If you want to prevent the 2 hour down time, add a second miner or even a third or 4th. I'd add a link to an article in steemit on how to do this, but I don't want mprep to delete the post. So google it.

Multiple accounts are required to register a different steemit account, using different user names and KEY ACTIVE to receive coins, that is not the resulting coins will be distributed to different steemit accounts?
Dig to the hard disk need to wait 2 years before it can be taken out?
Thank you ！

I'm not certain because I let my machine take a break while waiting in the miner witness queue. I have an older computer, so it's good to give it a break. I think if you are using one machine, you can use the same private key for both accounts. Since all mining reward are now converted to steem power, you will have to choose power down and get weekly payments of steem for 2 years. I don't think that you need to register your backup miner account first.

[seedtrue]

I guess I can't post a link, but Jackson Palmer(from dogecoin) just made a post. It is at the top of trending and probably will be there for the next 10 hours if anyone wants to take a look. I think it's great that a lot of well known people are starting to get involved.

[Bubba-Gump]

WTB Vested accounts. 30M+ Vests. Serious inquiries only.

Is it right? Thank you for guidance!

Yes, it is right. I am looking to buy vested accounts with 30M+ VESTS (8,000 Steem power or more per account).

[serejandmyself]

I guess I can't post a link, but Jackson Palmer(from dogecoin) just made a post. It is at the top of trending and probably will be there for the next 10 hours if anyone wants to take a look. I think it's great that a lot of well known people are starting to get involved.

That just another small proove that steemit is working and will be soon much more then your average social network (it is already)

[xtester]

Here's my latest analysis of Steemit: Measuring Steemit Growth: What Every Investor, Developer And User Should Know

"1. Transactions Volume: has experienced a significant growth since 4th of July and has reached a healthy state where on most days we see on average more than 100,000 transactions per day. By contrast, Bitcoin has on average more than 200,000 per day, and Ethereum less than 50,000.

2. Registered Accounts: presently Steemit has passed 60,500 registered accounts and has grown with ~17,500 new accounts or ~40,5% during the last 14 days. That’s 1250 new accounts or ~2,9% per day. As it stands now, we could reach ~75,000 – 80,000 registered accounts by the end of August.

3. Community dynamics: the community is growing and evolving at a rapid pace. Indeed, people seem to be very adaptive and strive to understand, contribute and improve things as much as possible. There are also disagreements and some apparent conflicts of interest between some well known community members(whales), but things are moving forward.  Indeed, I have not seen in crypto a community as diverse as this one. In fact, I am quite impressed at the rapidly growing number of well-connected influencers which have jumped in. As @roelandp put it, you’ve got Playmates, Vigilantes, Pirates and many others with hundreds of thousands of followers. Try to imagine what will follow.

4. Ecosystem/exchanges/developers: The ecosystem is also booming. Indeed, if you look at steemtools.com you can see that we have already 59(!) listed tools and apps. Number of exchanges has also increased. Although Poloniex and Bittrex were there, you can see that another three have listed Steem: Livecoin, HitBTC and alcurEX.

What’s even more intriguing is how involved various community developers are. And yes, the number is growing. Indeed, this seems to be at least in part due to the direct and immediate rewards they receive after implementing a solution to one of the many community needs. As things stand, this may be one of the most interesting platforms developers should engage. The reason is simple and potent: incentives. They’ve got both healthy immediate rewards, and promising future prospects if Steemit succeeds.

5. Investors, VCs, Startup Founders: another important metric to consider is what some of the bright minds of Sillicon Valley tend to think about the platform. Why? Well, because a good word from some of these people can add a lot of value and credibility to a very early stage platform and so significantly increase its exposure. Indeed, this kind of exposure is like gold, since it not only exposes Steemit to people who would merely love it if they would hear about it, but exposes it to other investors, VC’s or startup founders which could add significant value to the platform if they would join. Among these kind of people you have Fred Wilson, top Sillicon Valley investor, who is rooting for Steemit, Fred Ehrsam, Co-founder of Coinbase, mentioning it in his essay, Albert Wenger, early stage VC, mentioning it in his essay and many other startup founders who have already joined the platform."

[serejandmyself]

Ive just tried my first post on Steemit. Interesting platform.

My images have a gray swirl across them, how do I prevent this please?

Are you uploading images with a directl link or via steemimg or anything similar.

It could be that the image itself has a border, then you need to cut it on any programm on your pc.

[gyo9i]

You have many places to buy/sell Steem & Steem Dollars https://steemit.com/steem/@karoline/steem-and-steem-dollar-exchanges#

[Eclipse Crypto]

I write this post to address a quote within the Coin Telegraph story "Legitimacy of Crytpoassets or App Coins, Their Real World Value" by Joseph Young (https://cointelegraph.com/news/legitimacy-of-cryptoassets-or-app-coins-their-real-world-value).

Within the article, this quote is misattributed to bitcointalk user cryptohunter. This quote is actually mine, posted as user Eclipse Crypto, and quoted in its entirety at https://bitcointalk.org/index.php?topic=1410943.msg14404632#msg14404632. I am not the only Eclipse Crypto dev. I simply happened to be logged into the developer account when I started mining Steem, and never logged out, much to the eventual dismay of other developers on the Eclipse project. I deleted the original quote at the request of the Steem developers, although I knew copies persisted as quotes by other users.

The reason I deleted the original post from which Coin Telegraph took this quote is that I eventually felt that the rant was unfair. First, being used to so many launch shenanigans from other coins, I, like most other miners, am quick to throw around the word "scam". Given that Steem has been good for early miners and early exchange buyers, this label does not fit. The developers are still around, fully support Steem, and do very little selling of their coins from early mining, relatively speaking. Any selling that they do seems reasonable, given the scope of the Steem project and the size of the Steem markets on Bittrex and Poloniex. Additionally, the Steem developers have created and fully support the steemit.com website. Moreover, they have fully compensated users who lost funds during a limited site compromise in July. In short, no coin that has the benefit of support from a such an experienced and dedicated team could be a "scam". Time reveals whether projects fit this label, and I believe, along with many other users, that the label does not fit Steem.

My quote also claims the developers gave poor mining instructions. This was indeed the case for the original launch. Most of the instructions were accurate, but one in particular was not. It had to do with the format for the account name when issuing the mining command. Although explaining their error would require getting into the minutiae of JSON and command line parsers, this error turned out to be an honest mistake. Indeed, this mistake was corrected in the instructions for relaunch, and many clarifying instructions were added, making it less difficult (though not easy per se) for those who mined the relaunch.

Finally, as explained to me by the developers, the approximately 100 different accounts were required because their plan was to dominate the mining pool. Their intent was not to hide their mining presence, but to have enough accounts to accommodate their large hashing power. Steem uses a queued miner system, and each account may exist in the queue only as a single instance. Because the mining queue is generally about 100 in length, the 100 different addresses were reasonable to fully prevent wasted hashes. Several users, including myself, complained about the numerous accounts for the first launch. In response, the development team used very generic names, like steemit01, steemit02, etc., for the re-launch so that the team would not squat on good account names, many of which I claimed during subsequent mining.

In closing, I hope this puts the quote in context and clears up any misconceptions that reproducing it could propagate.