[ANN][STEEM][POW] - NO IPO | NO PREMINE | NO INSTAMINE (relaunch)

[drays]

I've been mining this along with NextGenCrypto

Vesting Rich List

Code:

berniesanders : 5876.768662

ie. berniesanders    

Feels good up at the top.

I was mining this all the time without interruptions, but I am nowhere near that..

How many machines did you use?
Vps or spare PCs?

Botnets maybe?

[1714320129]

1714320129

[NextGenCrypto]

I've been mining this along with NextGenCrypto

Vesting Rich List

Code:

berniesanders : 5876.768662

ie. berniesanders    

Feels good up at the top.

I was mining this all the time without interruptions, but I am nowhere near that..

How many machines did you use?
Vps or spare PCs?

Botnets maybe?

lol, no botnets, I had credit on Google ad Azure and paid for some on AWS...

[Grandpa Jones]

Vesting Rich List Permanent Home

I put a vesting richlist at http://steem.synergycoin.com/richlist.html

It updates every 15 minutes.

[drays]

Number of vesting shares crosse 400K...

"total_vesting_shares": "400145.616840 VESTS",
Was much less yesterday.

What is the supposed dynamics of this number? Shouldn't it have a limit (better to say - "tend to a limit")? I know I should look in the code . But I am lazy.. maybe someone already did?

[drays]

Vesting Rich List Permanent Home

I put a vesting richlist at http://steem.synergycoin.com/richlist.html

It updates every 15 minutes.

Nice work. It could be enhanced by adding an option to combine the accounts supposedly belonging to one person/teem (for example find connected accoounts using "get_account_history" and checking which accounts have transferred STEEM to another account's vesting)... Would be still inaccurate (especially when trading begins), but that would help to get better idea on how much unique miners there are.

[thereverseflash]

Number of vesting shares crosse 400K...

"total_vesting_shares": "400145.616840 VESTS",
Was much less yesterday.

What is the supposed dynamics of this number? Shouldn't it have a limit? I know I should look in the code . But I am lazy.. maybe someone already did?

The dynamics of this number is as follows:  

new VESTS can always be created by converting STEEM to VESTS at the current VESTING_FUND_STEEM to TOTAL_VESTING_SHARES ratio.

New STEEM is constantly being created; therefore we know that total possible VESTS must also grow
New STEEM is constantly being added to VESTING_FUND_STEEM at a rate 9x faster than it is being created outside the fund; therefore, the conversion rate from STEEM to VESTS is constantly falling.

We can expect the rate of VESTS creation to fall while the rate of STEEM creation is constant in absolute terms.

Eventually (about 1 year) STEEM will switch from being created at a fixed rate and start being created at a fixed APR. At this point in time the rate at which VESTS grows will level off.

The critical thing to remember is that growing of the number of VESTS never reduces the number of STEEM per VESTS.  

VESTS are diluted in percentage terms any time more than 90% of STEEM is held as vests.  

At the moment we have the following: 7652767.495/8477724.000:  0.902691276

This means that over 90% of all STEEM has been converted to vests. Most of the STEEM that hasn't been converted to VESTS is held in the REWARD FUND (786706.000) (9.27%) which leaves just 0.47% of STEEM liquid in people's accounts.

On July 4th, the REWARD fund will be distributed by the protocol, 50% VESTS and 50% SBD.  Assuming things don't change much between now and then, 95% of STEEM will be held in VESTS and 5% will be held in SBD (STEEM Backed Dollars).

The incentive to hold VESTS will fall dramatically over the next few weeks as the rate of change in the supply of STEEM falls.

[SalimNagamato]

can you teach us how to use withdraw vesting command ?

[pharesim]

withdraw_vesting "username" "1.000000 VESTS" true

[Grandpa Jones]

Vesting Rich List Permanent Home

I put a vesting richlist at http://steem.synergycoin.com/richlist.html

It updates every 15 minutes.

Nice work. It could be enhanced by adding an option to combine the accounts supposedly belonging to one person/teem (for example find connected accoounts using "get_account_history" and checking which accounts have transferred STEEM to another account's vesting)... Would be still inaccurate (especially when trading begins), but that would help to get better idea on how much unique miners there are.

Thank you

I'd follow your suggestion, but I happen to know that this type of taint analysis will already give erroneous results for STEEM.

[Grandpa Jones]

The incentive to hold VESTS will fall dramatically over the next few weeks as the rate of change in the supply of STEEM falls.

Do you mean the incentive to hold VESTS or the incentive to create new VESTS from STEEM?

[penambang]

what is this?:

Code:

156712ms th_a       application.cpp:386           handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old
    {"item->num":417706,"head":423308,"max_size":1024}
    th_a  fork_database.cpp:55 _push_block

    {"new_block":{"previous":"00065fa93f02732c37b207145d68832237846c5f","timestamp":"2016-04-08T16:02:36","witness":"bitcoin2016","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f46adba5c28a08a5e1571cad216c3e7ca13f2894a1ba4fe5ac4eefd016b5300b419d643f181ad976d80c681cef8c7259d868f54769a6eeda5b2557a96409227ec","transactions":[]}}
    th_a  database.cpp:530 _push_block
157123ms th_a       application.cpp:386           handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old
    {"item->num":417706,"head":423308,"max_size":1024}
    th_a  fork_database.cpp:55 _push_block

    {"new_block":{"previous":"00065fa93f02732c37b207145d68832237846c5f","timestamp":"2016-04-08T16:02:36","witness":"bitcoin2016","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f46adba5c28a08a5e1571cad216c3e7ca13f2894a1ba4fe5ac4eefd016b5300b419d643f181ad976d80c681cef8c7259d868f54769a6eeda5b2557a96409227ec","transactions":[]}}
    th_a  database.cpp:530 _push_block
219728ms th_a       application.cpp:386           handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old
    {"item->num":417707,"head":423308,"max_size":1024}
    th_a  fork_database.cpp:55 _push_block

    {"new_block":{"previous":"00065faae316b50b8d94173c8f060b875fc6843d","timestamp":"2016-04-08T16:03:39","witness":"bitcoin2016","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"203da4ca37cdec4d70eb8db42aff724e3d95d44de31df1f6a1706316788773dc4d02b580d35710b99fdd725f9ff68a83b716ee7d3210cdeb13ba7a42de3da0f9a0","transactions":[]}}
    th_a  database.cpp:530 _push_block
220060ms th_a       application.cpp:386           handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old
    {"item->num":417707,"head":423308,"max_size":1024}
    th_a  fork_database.cpp:55 _push_block

    {"new_block":{"previous":"00065faae316b50b8d94173c8f060b875fc6843d","timestamp":"2016-04-08T16:03:39","witness":"bitcoin2016","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"203da4ca37cdec4d70eb8db42aff724e3d95d44de31df1f6a1706316788773dc4d02b580d35710b99fdd725f9ff68a83b716ee7d3210cdeb13ba7a42de3da0f9a0","transactions":[]}}
    th_a  database.cpp:530 _push_block
282706ms th_a       application.cpp:386           handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old
    {"item->num":417708,"head":423308,"max_size":1024}
    th_a  fork_database.cpp:55 _push_block

    {"new_block":{"previous":"00065fabaa395edfa8c729582058a89fafaa0b4e","timestamp":"2016-04-08T16:04:42","witness":"bitcoin2016","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20040af5d0d9cc2da6ad2fd2b57b913bbd1bf8e827355e68000d61a2c6f6a8df557e7a851dd24069bad84a12a361d1d0aba06ecd3974f78a7b757496b3df198d68","transactions":[]}}
    th_a  database.cpp:530 _push_block
345720ms th_a       application.cpp:386           handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old
    {"item->num":417709,"head":423308,"max_size":1024}
    th_a  fork_database.cpp:55 _push_block

    {"new_block":{"previous":"00065fac3a0b14b118b354302ffae6b3e2f12bdb","timestamp":"2016-04-08T16:05:45","witness":"bitcoin2016","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"202ae5ee73710577ef07edb6c434730b58d9323d6da04d5afdfbeb2244704a8fca67df4fcb980076c2f88a11298b5764f29669aabb872e2209321ec43c1b07ebf6","transactions":[]}}
    th_a  database.cpp:530 _push_block
408657ms th_a       application.cpp:386           handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old
    {"item->num":417710,"head":423308,"max_size":1024}
    th_a  fork_database.cpp:55 _push_block

    {"new_block":{"previous":"00065fad5ca87369fb9cf80517fd2e194654a2da","timestamp":"2016-04-08T16:06:48","witness":"bitcoin2016","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f62b73535b18410434090e3c0045a3a1fddba011240b1146e22cecd320612663d30c1390f28cc2c6992cc42d37c3b8b9f830d4af5d236aaa32c6523f783658a85","transactions":[]}}
    th_a  database.cpp:530 _push_block

I got bunch of this error since yesterday

[Neon~]

How to find the total pow hash rate of Steem network? Is it  "total_pow" field in info?

[thereverseflash]

How to find the total pow hash rate of Steem network? Is it  "total_pow" field in info?

A more accurate measure of TOTAL POW effort would be "num_pow_witnesses" which is about 105 (near all time high).

total_pow = sum of num_pow_witnesses over all blocks, a blockchain with the most total_pow has the highest average difficulty, while the one with the highest num_pow_witnesses has the highest current difficulty.

The other number to look at is head_block_number, the chain with the most blocks has had the least missed blocks and therefore is the one the majority of miners are building on.

A fork was created by some miners, but the real chain is:

Code:

  
  "head_block_number": 426200,
  "head_block_id": "000680d842d8e1f0b7037ff78165a6824185359b",
  "time": "2016-04-08T16:50:12",
  "current_witness": "aramco",
  "total_pow": 1985727,
  "num_pow_witnesses": 105,
  "participation": "100.00000000000000000"

You can get this information in the cli_wallet using the 'info' command.  

You are probably on a fork if you do not see your hashrate update every 3 seconds.

These are the active miners, 100% of the miners scheduled have been producing on the main chain.

Code:

[
  "steemtrain",
  "mail",
  "aramco",
  "steemit122",
  "ashley",
  "turtlesteem2",
  "tombstone5",
  "jasmine",
  "tombstone6",
  "another18",
  "steemit214",
  "hannah",
  "coldstorage25",
  "steemit161",
  "steemit173",
  "steemit154",
  "coldstorage12",
  "steemit113",
  "dog",
  "soupper3",
  "chu",
  "steemit240",
  "steemit119",
  "feng",
  "ppp",
  "stickleyman",
  "another13",
  "articmine",
  "btstools11",
  "mailer",
  "tombstone30",
  "wayfairer",
  "expir",
  "another1",
  "neon1",
  "turtle",
  "anna",
  "chris",
  "another7",
  "steems",
  "another3",
  "ani625",
  "fury",
  "rossco91",
  "steemit191",
  "wayfairer3",
  "tombstone50",
  "tombstone40",
  "lostcity",
  "coldstorage18",
  "tombstone25",
  "tombstone35",
  "monsternal",
  "kitten",
  "zhou",
  "steemit114",
  "soupper21",
  "tombstone16",
  "steemit223",
  "soupper44",
  "bison",
  "tombstone17",
  "soupper10",
  "emily",
  "exxonmobile",
  "steemit117",
  "donaldtrump",
  "email",
  "bitshares.org",
  "steem-id",
  "soupper14",
  "steemit109",
  "steemit174",
  "tombstone75",
  "tombstone85",
  "nxtgencrpto16",
  "abderus",
  "another2",
  "soupper45",
  "btstools6",
  "xeldal",
  "steemit137",
  "steemit195",
  "another16",
  "americanpegasus",
  "brianna",
  "tombstone26",
  "another",
  "steemit215",
  "rossco92",
  "steemit192",
  "steemit101",
  "numberofdays",
  "steemit145",
  "steemit181",
  "wayfairer2",
  "steemit177",
  "steemit231",
  "steemit196",
  "stephie",
  "sex",
  "tombstone76",
  "tombstone41",
  "zhu",
  "tombstone95"
]

We are investigating what caused some miners to get lost, but it appears that most are are the proper chain based upon the POW difficulty.

[Neon~]

Thanks for replying. I believe I'm on the main chain as I can see my miner in the miner queue (neon1)  I've got a hashrate of around 80khps, how many miners should I configure to get the best efficiency out of my hash power?

[thereverseflash]

Thanks for replying. I believe I'm on the main chain as I can see my miner in the miner queue (neon1)  I've got a hashrate of around 80khps, how many miners should I configure to get the best efficiency out of my hash power?

For your hash rate, at least 2 maybe 3.  Just make sure all of your miners are not in the queue at the same time or you will idle.

[Neon~]

If I configure 2 miners, will it affect my current efficiency of solving the pow? Will the miners be trying to solve the pow in parallel (thus reducing my efficiency by half) or the second miner will kick-off to solve the block only when my first miner gets into the queue?

[thereverseflash]

If I configure 2 miners, will it affect my current efficiency of solving the pow? Will the miners be trying to solve the pow in parallel (thus reducing my efficiency by half) or the second miner will kick-off to solve the block only when my first miner gets into the queue?

It won't hurt your efficiency at all.

[Neon~]

If I configure 2 miners, will it affect my current efficiency of solving the pow? Will the miners be trying to solve the pow in parallel (thus reducing my efficiency by half) or the second miner will kick-off to solve the block only when my first miner gets into the queue?

It won't hurt your efficiency at all.

Thanks for confirming. I will configure 2 then..

[stoner19]

anyone else have issues with their daemon stopping when trying to sync the chain? mine says

Code:

Floating point exception

then it just stops. When I restart it it'll sync another few thousand blocks then stop again.

[SalimNagamato]

how to send STEEM to openledger-wallet ?

tried to send 10 coins to "openledger" with memo open.steem:myopenledgeraccount