Dry Run 9: [Block]Chain Hang Low (featuring guest performer: ~~BitUSD~~)

[bytemaster]

I just updated the OP with example commands.

[bytemaster]

Tried to import my private key but I have this error:

Code: [Select]

default (unlocked) >>> wallet_account_create spartako
default (unlocked) >>>wallet_import_private_key 5...BTC..PRIVATE...KEY.... spartako
10 assert_exception: Assert Exception
oacct.valid(): just imported a key but now the key has no owner
    {}
    th_a  client.cpp:1733 wallet_import_private_key

    {}
    th_a  common_api_client.cpp:563 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:538 execute_command

EDIT: even if there is this error after wallet_rescan_blockchain command the balance is CORRECT

Known issue, Toast is on it.

[Fox]

I had to up my RAM allocation to compile this Dry Run version. 

Off we go:

Code: [Select]

wallet_approve_delegate fox

[spartako]

Tried to import my private key but I have this error:

Code: [Select]

default (unlocked) >>> wallet_account_create spartako
default (unlocked) >>>wallet_import_private_key 5...BTC..PRIVATE...KEY.... spartako
10 assert_exception: Assert Exception
oacct.valid(): just imported a key but now the key has no owner
    {}
    th_a  client.cpp:1733 wallet_import_private_key

    {}
    th_a  common_api_client.cpp:563 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:538 execute_command

EDIT: even if there is this error after wallet_rescan_blockchain command the balance is CORRECT

[liondani]

Loading blockchain from "/var/bts/chain"
Loading config "/var/bts/config.json"
------------ error --------------
10001 db_in_use_exception: Database in Use
Unable to open database /var/bts/peers.leveldb
        IO error: lock /var/bts/peers.leveldb/LOCK: Resource temporarily unavail
able
    {"db":"/var/bts/peers.leveldb","msg":"IO error: lock /var/bts/peers.leveldb/
LOCK: Resource temporarily unavailable"}
    p2p  level_pod_map.hpp:45 open
zsh: segmentation fault  /var/bts/bitshares_toolkit/programs/client/bitshares_cl
ient --data-dir   6553

also ports are not releasing and full reboot is required.

had same issue
and was fixed after a hard reset...

On this Dry Run and Dry Run 6 if I can remember well (linux Mint 17 64bit)

[toast]

We've reset, please wipe your chain directory to reconnect

[liondani]

Some funds please 

XTS7yMLAdUFEDdEjuyy75NncKP6N4LDf3SRrdxQEFa4nZLyVaHWaE

Sent.

thank you 

[liondani]

Is this thread gonna be about expensive play dough?

On another note, I said that ‘I will not try to be a delegate’ (post is dilated now due to semi-smooth start to this run).
So I made the right decision and end up saving a lot of fake money! Should I jump with joy?

It is obvious not a problem with Dry Runs and fake money, we are only discussing it now so maybe we prevent problems on the original chain run...
I guess on the real chain everything will be smoother due to real coin value...

[jbutta2k13]

Loading blockchain from "/var/bts/chain"
Loading config "/var/bts/config.json"
------------ error --------------
10001 db_in_use_exception: Database in Use
Unable to open database /var/bts/peers.leveldb
        IO error: lock /var/bts/peers.leveldb/LOCK: Resource temporarily unavail
able
    {"db":"/var/bts/peers.leveldb","msg":"IO error: lock /var/bts/peers.leveldb/
LOCK: Resource temporarily unavailable"}
    p2p  level_pod_map.hpp:45 open
zsh: segmentation fault  /var/bts/bitshares_toolkit/programs/client/bitshares_cl
ient --data-dir   6553

also ports are not releasing and full reboot is required.

[bytemaster]

By popular demand, the delegate fee calculation is clearly way more volatile than I intended so we are going to reset this dryrun before we get too far into it.

New calculations:

Code: [Select]

delegate_pay = total_accumulated_fees / (blocks_per_day*14)
delegate_registration = delegate_pay * blocks_per_hour * 2 / 101

The effect of this change is that delegate pay will rise much slower, and registration will have a much smaller impact on delegate pay.  (14 days vs 2 hours). 

[dxtr]

I can not cover a short position (I think I'm doing it right way, and have sufficient funds...):

Code: [Select]

dxtr-wallet (unlocked) >>> blockchain_market_list_shorts USD
TYPE        QUANTITY            PRICE                         BALANCE             COST                COLLATERAL          ID                                 
--------------------------------------------------------------------------------------------------------------------------------
short_order 111.11111 XTS       0.9 USD / XTS                 111.11111 XTS       99.9999 USD         N/A                 XTS7H8Bnrk5iFHP9rXcj6Kj5VJPRbd6aWJPz
dxtr-wallet (unlocked) >>>  wallet_market_cover dxtr 10 USD XTS7H8Bnrk5iFHP9rXcj6Kj5VJPRbd6aWJPz
10 assert_exception: Assert Exception
order_to_cover.valid():
    {}
    th_a  wallet.cpp:3215 cover_short

    {"from_account_name":"dxtr","real_quantity_usd":10,"quote_symbol":"USD","owner_address":"XTS7H8Bnrk5iFHP9rXcj6Kj5VJPRbd6aWJPz","sign":true}
    th_a  wallet.cpp:3288 cover_short

    {}
    th_a  common_api_client.cpp:1299 wallet_market_cover

    {"command":"wallet_market_cover"}
    th_a  cli.cpp:538 execute_command

[Simeon II]

Is this thread gonna be about expensive play dough?

On another note, I said that ‘I will not try to be a delegate’ (post is dilated now due to semi-smooth start to this run).
So I made the right decision and end up saving a lot of fake money! Should I jump with joy?

[liondani]

Something needs to be done about delegate registration fees.

Code: [Select]

2014-07-15T18:16:37 544       bitcoiners          bitcoiners          0.00000 XTS           856,060.89468 XTS   register bitcoiners as a delegate       92fe4244


The registration fees are doing their job of rate-limiting delegate signup.   They are currently 4 million, and in an hour will be under 60K if no one else signs up and pays the huge price.    In 2 hours it will be under 6000 (assuming few fees are collected during that time).

so that means only the BitSharesX whales will have the oportumity to be the first delegates, and I assume the last ones as well...

Ridiculous.   Even at todays BTSX prices on BTER the current signup fee is only $1800 and falling.   That is hardly whale level.

I think you are wrong. To get a delegate right now it costs 6,312,291 XTS
that means 6,312,291*0.0000203 BTC = 128.1395073 BTC * $620 = $79,446

Code: [Select]

liondani (unlocked) >>> config
{
  "blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
  "symbol": "XTS",
  "name": "BitShares XTS",
  "version": 107,
  "genesis_timestamp": "20140715T000000",
  "block_interval": 10,
  "target_block_size": 25600,
  "max_block_size": 51200,
  "max_blockchain_size": 107374182400,
  "address_prefix": "XTS",
  "min_block_fee": 1,
  "inactivity_fee_apr": 10,
  "delegate_num": 101,
  "delegate_reg_fee": "6,312,291.61188 XTS",
  "name_size_max": 63,
  "memo_size_max": 19,
  "data_size_max": 65536,
  "symbol_size_max": 5,
  "symbol_size_min": 3,
  "asset_reg_fee": "637,541,452.80000 XTS",
  "asset_shares_max": 1000000000000000,
  "proposal_vote_message_max": 1024,
  "max_pending_queue_size": 100,
  "max_trx_per_second": 10
}


[bitcoinerS]

Funds please?

Account Key: XTS542XFkGR9Fvj4hdQZYivZeEEDQCHv3gqA7TUzPPG4eUJ3SSKpm

thx

Sent.

[dxtr]

It seems delegate registration fees are changing quite randomly. It dropped down below 100,000 XTS and now back up to over 10 million..

Code: [Select]

>> blockchain_get_config

{
  "blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
  "symbol": "XTS",
  "name": "BitShares XTS",
  "version": 107,
  "genesis_timestamp": "20140715T000000",
  "block_interval": 10,
  "target_block_size": 25600,
  "max_block_size": 51200,
  "max_blockchain_size": 107374182400,
  "address_prefix": "XTS",
  "min_block_fee": 1,
  "inactivity_fee_apr": 10,
  "delegate_num": 101,
  "delegate_reg_fee": "11,444,627.53767 XTS",
  "name_size_max": 63,
  "memo_size_max": 19,
  "data_size_max": 65536,
  "symbol_size_max": 5,
  "symbol_size_min": 3,
  "asset_reg_fee": "1,155,907,381.30560 XTS",
  "asset_shares_max": 1000000000000000,
  "proposal_vote_message_max": 1024,
  "max_pending_queue_size": 100,
  "max_trx_per_second": 10
}
>> blockchain_get_config

{
  "blockchain_id": "5a50ec8c2433e7d5fce13187be2db73d112dcdc6b3766751fbff6162e90836b0",
  "symbol": "XTS",
  "name": "BitShares XTS",
  "version": 107,
  "genesis_timestamp": "20140715T000000",
  "block_interval": 10,
  "target_block_size": 25600,
  "max_block_size": 51200,
  "max_blockchain_size": 107374182400,
  "address_prefix": "XTS",
  "min_block_fee": 1,
  "inactivity_fee_apr": 10,
  "delegate_num": 101,
  "delegate_reg_fee": "116,088.31803 XTS",
  "name_size_max": 63,
  "memo_size_max": 19,
  "data_size_max": 65536,
  "symbol_size_max": 5,
  "symbol_size_min": 3,
  "asset_reg_fee": "11,724,920.12160 XTS",
  "asset_shares_max": 1000000000000000,
  "proposal_vote_message_max": 1024,
  "max_pending_queue_size": 100,
  "max_trx_per_second": 10
}

No it goes with what BM said - the price melts down to amount the next candidate is willing to pay, if he pays - it is automatically increasing total_fees and reseting the clock waiting for next rich candidate for a delegate to participate.

But it goes along with: Rich get richer, poor get poorer...