Dry Run 7: The Power of DPOS

[muse-umum]

Launching in Hong Kong or mainland?

Hong Kong.

HK is far more open mainland.

[bitder]

A fresh build of the current code can't sync with the network (starting with rm -rf ~/.BitSharesXTS )

• can't get more than 2 active connections
• quit - causes core dump
• stuck on block 4563 - in an infinite loop

Code Select Expand


Attempting to map P2P port 8701 with UPNP...
Listening for P2P connections on port 8701
Attempting to connect to peer 107.170.30.182:8701
Attempting to connect to peer 107.170.30.182:8702
Attempting to connect to peer 107.170.30.182:8703
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "fca5a763926ed77e7a349df9040d44d3fd2f1bf0",
  "bitshares_toolkit_revision_age": "2 hours ago",
  "fc_revision": "49cbe600f923762e6db2733d6dbddc4fbd1d185a",
  "fc_revision_age": "32 hours ago",
  "compile_date": "compiled on Jul  6 2014 at 20:11:17"
}
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 17014 blocks left to fetch
--- there are now 2 active connections to the p2p network
(wallet closed) >>> info
{
  "blockchain_head_block_num": 4562,
  "blockchain_head_block_age": "5 days old",
  "blockchain_head_block_timestamp": "20140702T170600",
  "blockchain_average_delegate_participation": 0.38880548177233709,
  "blockchain_delegate_pay_rate": 105087,
  "blockchain_blocks_left_in_round": 84,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199999343910827,
  "blockchain_random_seed": "7f4ef399073bc1ca64c1e54336780521bb85b2a5",
  "blockchain_database_version": 110,
  "blockchain_version": 104,
  "network_num_connections": 2,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": null,
  "ntp_error": null,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 101
}



snippet from log file

Code Select Expand


20140707T051340.560091       th_a       switch_to_fork ]     extend c8f5fe742ce207638618f3169831a7b664770148 chain_database.cpp:507
20140707T051340.562787       th_a   apply_transactions ] Applying transactions from block: 4563 chain_database.cpp:517
20140707T051340.564173       th_a         extend_chain ] error applying block: 35005 invalid_asset_amount: invalid asset amount

    {"maximum_share_supply":5000000000000000}
    th_a  asset_operations.cpp:22 evaluate

    {"*this":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}
    th_a  asset_operations.cpp:55 evaluate

    {"op":{"type":"create_asset_op_type","data":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}}
    th_a  operation_factory.hpp:52 evaluate

    {"trx":{"expiration":"20140702T190600","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS9pi8yG7ZA215b61hm1icucLZx39wMhmmr","amount":18740,"claim_input_data":""}},{"type":"create_asset_op_type","data":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}],"signatures":["1f9fcb7e2e9f421d39e152b0c791db7e9d32b5f76fbd8f448293e82d41c592f06d6c0be70f17830758b8c3d621769b994f73a73a548d9e07f86c6891f0104c6157","1fbaa98928e62b2d3cbfe81b0e7164aeee9a78ef356c3c81ae550e66c9efde3547933d1b3da0c9a615eb25c2ee848611328e13e823479fac64b6cb952a4831f843"]}}
    th_a  transaction_evaluation_state.cpp:218 evaluate

    {"trx_num":0}
    th_a  chain_database.cpp:550 apply_transactions chain_database.cpp:817
20140707T051342.545960       th_a           push_block ] attempt to switch to fork failed: 35005 invalid_asset_amount: invalid asset amount

    {"maximum_share_supply":5000000000000000}
    th_a  asset_operations.cpp:22 evaluate

    {"*this":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}
    th_a  asset_operations.cpp:55 evaluate

    {"op":{"type":"create_asset_op_type","data":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}}
    th_a  operation_factory.hpp:52 evaluate

    {"trx":{"expiration":"20140702T190600","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS9pi8yG7ZA215b61hm1icucLZx39wMhmmr","amount":18740,"claim_input_data":""}},{"type":"create_asset_op_type","data":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}],"signatures":["1f9fcb7e2e9f421d39e152b0c791db7e9d32b5f76fbd8f448293e82d41c592f06d6c0be70f17830758b8c3d621769b994f73a73a548d9e07f86c6891f0104c6157","1fbaa98928e62b2d3cbfe81b0e7164aeee9a78ef356c3c81ae550e66c9efde3547933d1b3da0c9a615eb25c2ee848611328e13e823479fac64b6cb952a4831f843"]}}
    th_a  transaction_evaluation_state.cpp:218 evaluate

    {"trx_num":0}
    th_a  chain_database.cpp:550 apply_transactions

    {"block":{"previous":"e8892a6ddeb85a0d036007c30816f80228e9824a","block_num":4563,"fee_rate":1000,"delegate_pay_rate":105075,"timestamp":"20140702T170615","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"00183a252b822414119750d28786fe5084443912","previous_secret":"4eec7785fb7956810f53e14a13cb430225ecd0f0","delegate_signature":"1fa89eec0182c1536553d5ae7b5544b61792b38039d64a9e29616462425e7c821a7498704dc704ff7b6d6309b248250e4c86b73ae9edcfcc9fdc86836bfd6696b4","user_transactions":[{"expiration":"20140702T190600","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS9pi8yG7ZA215b61hm1icucLZx39wMhmmr","amount":18740,"claim_input_data":""}},{"type":"create_asset_op_type","data":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}],"signatures":["1f9fcb7e2e9f421d39e152b0c791db7e9d32b5f76fbd8f448293e82d41c592f06d6c0be70f17830758b8c3d621769b994f73a73a548d9e07f86c6891f0104c6157","1fbaa98928e62b2d3cbfe81b0e7164aeee9a78ef356c3c81ae550e66c9efde3547933d1b3da0c9a615eb25c2ee848611328e13e823479fac64b6cb952a4831f843"]},{"expiration":"20140702T190554","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSJWKU4xsnjf72cos4FCQt98DJy2z1fyNGw","amount":10000000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSNyQWJX1qYhJXUn2e3gYfL9wgYdJfWBEce","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000000,"condition":{"asset_id":7,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSF5gmfmgjVBrJ9GzkYk4s8CsdCtSVNE9Rh","memo":{"one_time_key":"XTS6hqwJtjMzKRLZw2uCRULbAT7BZNxiGZ1CRBLDTGgYFgu22aiLM","encrypted_memo_data":"ffa52fb7dc480f2cb8ded59ab2d396d2017f159cee99ef4f8f8cd3b671f8777d00d5e5dfdbfac811e2b1c85b2c437c36dcdb7034ba3a4577e3219c1ce5a1d942"}}}}}],"signatures":["205ba142cd84196a1ad4ea995cd6f1746d8048c5a460008b6085aa6e59d6dd781758048d93596d8700f57eecf4ce120825f166c340538ee00cf4227b5af61cb10d","20dec717e1052e2f8de5e3cbc6968cf558cd6c5121615db8293f80cfcee00bd5fc5f97bbc3de46913d41d3e7e4ee044708ea50fe160665509c496123d9770e87c3"]},{"expiration":"20140702T190554","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSJWKU4xsnjf72cos4FCQt98DJy2z1fyNGw","amount":10000000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSNyQWJX1qYhJXUn2e3gYfL9wgYdJfWBEce","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000000,"condition":{"asset_id":7,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSNhtMDntuCeA3SVwYyziV5keQ7maTcUPvz","memo":{"one_time_key":"XTS7QcGiUmxff4h4tBiMEonkcHrDBQNkMHHmDpENeQdc6HaB5Dr3f","encrypted_memo_data":"d17151390fafdb0368168ea2062861f9609ccc2cf3034b06e948da87afdfffe00c616cb73e2fa9bc00fa0ac22b2a97b5bcc5a90236b0ba7d952bd86fb3a8a795"}}}}}],"signatures":["2051466675808368ea7e0bc17bb72dc3cb1e1833aeba17bcba881bd0245663e95d4a619cd38e61b9b10b560e121b4e117faf26172293338ba00a91868e5ed2ed3f","1fa042dd82a6f14f9489324d06f55ef923711bb7f4fbfdad416a5de8ed52b1d823a393cbbb82bd6a2ae6e83fd1054d83adcbbce30378add38d674144dde46d4a6d"]}]}}
    th_a  chain_database.cpp:832 extend_chain

    {"block_id":"4d421c0542c10b1c20f721e1afe1e547cfe78796"}
    th_a  chain_database.cpp:510 switch_to_fork, reverting


[onceuponatime]

on a russian moon base

I think the regulations are different in Hong Kong and mainland China (though neither is less regulated than a Russian moon base I would assume  ??? )

[liondani]

on a russian moon base

[onceuponatime]

what's the plane, do we need next dry run?

The next dry run will focus on market operations (bid/ask/short/etc) and will likely start toward the end of this week.   

I actually think we will attempt to upgrade in place and keep the XTS test network around as long as possible to test upgradability and discover issues such as sync time that may be hidden if we didn't keep the test net going for more than a week.   

Good work everyone, Dry Run 7 is a complete success and the first of many.

So do you mean that XT will be released with market functionality?

I mean that the launch / release of BTSX is being done in parallel with XT development.   

I3 will focus on software dev and a never ending series of test networks that get reset.    There are other organizations that will launch and support live networks in parallel with ongoing testing.   

Dry Run 7 has proven basic functions for the first live network... meanwhile I am moving forward rapidly to start testing the next phase.

from the news letter, DACs Unlimited will release bitshares X.
do you think it's time for the first release?
and can we get the plane for bitshares x release from DACs Unlimited? :)

Last I heard DACs Unlimited was in the process of rebranding the test GUI and adding international support for Chinese and will be launching in China.   I think they will release as soon as they have all of the packaging ready and are properly organized.

Launching in Hong Kong or mainland?

[alt]

DAC Unlimited is trusted.

Got it!
The show is beginning  ;D

[bytemaster]

DAC Unlimited is trusted.

[alt]

what's the plane, do we need next dry run?

The next dry run will focus on market operations (bid/ask/short/etc) and will likely start toward the end of this week.   

I actually think we will attempt to upgrade in place and keep the XTS test network around as long as possible to test upgradability and discover issues such as sync time that may be hidden if we didn't keep the test net going for more than a week.   

Good work everyone, Dry Run 7 is a complete success and the first of many.

So do you mean that XT will be released with market functionality?

I mean that the launch / release of BTSX is being done in parallel with XT development.   

I3 will focus on software dev and a never ending series of test networks that get reset.    There are other organizations that will launch and support live networks in parallel with ongoing testing.   

Dry Run 7 has proven basic functions for the first live network... meanwhile I am moving forward rapidly to start testing the next phase.

from the news letter, DACs Unlimited will release bitshares X.
do you think it's time for the first release?
and can we get the plane for bitshares x release from DACs Unlimited? :)

Last I heard DACs Unlimited was in the process of rebranding the test GUI and adding international support for Chinese and will be launching in China.   I think they will release as soon as they have all of the packaging ready and are properly organized.

But I think we should still download the client from bitshares.org right?
or they have I3's promise,  their client are trusted.

[bytemaster]

Win  GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe

last block  synced   4562  to stop

me too

Me too....

We are stuck on this block because:

Code Select Expand


35005 invalid_asset_amount: invalid asset amount

    {"maximum_share_supply":5000000000000000}
    th_a  asset_operations.cpp:22 evaluate

    {"*this":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}
    th_a  asset_operations.cpp:55 evaluate

    {"op":{"type":"create_asset_op_type","data":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}}
    th_a  operation_factory.hpp:52 evaluate

    {"trx":{"expiration":"20140702T190600","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS9pi8yG7ZA215b61hm1icucLZx39wMhmmr","amount":18740,"claim_input_data":""}},{"type":"create_asset_op_type","data":{"symbol":"MFMC","name":"MFM Co.","description":"MFM Share Split","public_data":"","issuer_account_id":456,"maximum_share_supply":5000000000000000,"precision":1000000}}],"signatures":["1f9fcb7e2e9f421d39e152b0c791db7e9d32b5f76fbd8f448293e82d41c592f06d6c0be70f17830758b8c3d621769b994f73a73a548d9e07f86c6891f0104c6157","1fbaa98928e62b2d3cbfe81b0e7164aeee9a78ef356c3c81ae550e66c9efde3547933d1b3da0c9a615eb25c2ee848611328e13e823479fac64b6cb952a4831f843"]}}
    th_a  transaction_evaluation_state.cpp:218 evaluate

    {"trx_num":0}
    th_a  chain_database.cpp:550 apply_transactions


On July 3rd Dan N. fixed a validation bug by adding the following check:

Code Select Expand

if( this->maximum_share_supply > BTS_BLOCKCHAIN_MAX_SHARES
        FC_CAPTURE_AND_THROW( invalid_asset_amount, (maximum_share_supply) );

This block was produced prior to that date and apparently no one has updated or attempted to resync until now.

[bytemaster]

Win  GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe

last block  synced   4562  to stop

me too

Me too....

[yangsbo]

Win  GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe

last block  synced   4562  to stop

me too

[gyhy]

Win  GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe

last block  synced   4562  to stop

[laow]

 +5%
What's relationship between 3I and DACs Unlimited ？ btc38 add bts/btc trade just now.

[bytemaster]

what's the plane, do we need next dry run?

The next dry run will focus on market operations (bid/ask/short/etc) and will likely start toward the end of this week.   

I actually think we will attempt to upgrade in place and keep the XTS test network around as long as possible to test upgradability and discover issues such as sync time that may be hidden if we didn't keep the test net going for more than a week.   

Good work everyone, Dry Run 7 is a complete success and the first of many.

So do you mean that XT will be released with market functionality?

I mean that the launch / release of BTSX is being done in parallel with XT development.   

I3 will focus on software dev and a never ending series of test networks that get reset.    There are other organizations that will launch and support live networks in parallel with ongoing testing.   

Dry Run 7 has proven basic functions for the first live network... meanwhile I am moving forward rapidly to start testing the next phase.

from the news letter, DACs Unlimited will release bitshares X.
do you think it's time for the first release?
and can we get the plane for bitshares x release from DACs Unlimited? :)

Last I heard DACs Unlimited was in the process of rebranding the test GUI and adding international support for Chinese and will be launching in China.   I think they will release as soon as they have all of the packaging ready and are properly organized.

[liondani]

I'm just outside as well, 110 or so, pls vote for me!

Code Select Expand


liondani (unlocked) >>> wallet_approve_delegate svk-delegate true 
OK