Dry Run 2: The Real Deal

[crazybit]

btw,i upgrade myself to be a delegate, please vote "crazybit" , thanks

to vote me, you just need to issue the follow command before you perform transfer. thanks

wallet_set_delegate_trust_level crazybit 1

[crazybit]

Most of this team only started working effectively this month.. so I think we have enough people to do the job now.

you guys make a great  progress this month. well done!

[bytemaster]

I got a backup chain file from ubuntu and run on windows because windows version always stuck on block 173.

We are well aware of the Windows client getting stuck on 173.  It is the result of a stack corruption exception that has us truly baffled.  Tomorrow that is Eric's top priority to track down as the bug likely effects other platforms but expresses itself differently.

[bytemaster]

Our team of developers:

Eric Frias - responsible for most of the P2P network code, RPC code gen, and other items.
Toast  - helping everywhere , currently web wallet / C++ integration
Nikita - helping with web wallet
HackFisher - helping everywhere, currently web wallet  (Just in from China last week)
Dan N - working toward robust test suites
Nathan - Starting Monday (C++)
Vikram - Starting Monday (C++ / everywhere)
Myself  - everywhere
Valentine -  C++ / Web  (part time, hopefully full time)
3 polish devs -  Keyhotee / BitShares integration / Nightly Support
1 Indian - tester
James - part time (currently busy, but will return in 2 weeks) JS support for signing transactions


Most of this team only started working effectively this month.. so I think we have enough people to do the job now.

[cgafeng]

I got a backup chain file from ubuntu and run on windows because windows version always stuck on block 173.
And the backup chain is on block 5563.
It works well on windows at the begin.

After get the block 5666, the client is crash every time on windows, but it work well on ubuntu.
The last log on windows:

Code: [Select]

3473443ms       th_a         on_new_block ] Received a new block from the p2p network, current head block is 5666, new block is {"previous":"f0b54dea22b16d33ab319ff31b21514a9dc0893a","block_num":5667,"fee_rate":1000,"delegate_pay_rate":63853,"timestamp":"20140615T032800","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"81e526a9e2871b33164d3f09ad3311deb6191fd4","previous_secret":"bb8dc9dce058218a2f39b3a358ea2b78179bf906","delegate_signature":"1fdfc08bf36daad0a7ec31ccaedd25ad2e89fd082a6814f36b7aac25f70059355aabc9da9fb2570c7fa5bfed9eb6e6cbb00d9f8a29631de7c3dbe297e58a141e6a","user_transactions":[{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS4UTfbDwf5TvoYpMbqcviYpPFSpEFbwuwt","amount":10495702,"claim_input_data":""}},{"type":"update_account_op_type","data":{"account_id":315,"public_data":null,"active_key":null,"is_delegate":true}}],"signatures":["1f80dd5137f742b842da2dbf6bcfb4c23d94e62bafac751b4ea22da8cb918ce318ff739104db8c51f7a9da8320b17441dbfb7be57f717199fa26d50780e9bf805d","1f5742fb4e069b8b18496b7879fd00608d598f66aa13635060f0f215b884f5788a042107c1ccd28d5b059e0e090470130531b13396bb1b51a18ec6fa7caabf363d"]}]}, current head block is 5666 client.cpp:518
3473444ms       th_a         get_property ] property last_random_seed_id chain_database.cpp:1711
3473445ms       th_a      store_and_index ]            we already know about its previous: f0b54dea22b16d33ab319ff31b21514a9dc0893a chain_database.cpp:350
3473446ms       th_a         get_property ] property active_delegate_list_id chain_database.cpp:1711
3473446ms       th_a         get_property ] property active_delegate_list_id chain_database.cpp:1711
3473450ms       th_a         get_property ] property active_delegate_list_id chain_database.cpp:1711
3473451ms       th_a         get_property ] property confirmation_requirement chain_database.cpp:1711
3473451ms       th_a         get_property ] property active_delegate_list_id chain_database.cpp:1711
3473452ms       th_a         get_property ] property active_delegate_list_id chain_database.cpp:1711
3473453ms       th_a         get_property ] property active_delegate_list_id chain_database.cpp:1711
3473453ms       th_a         get_property ] property active_delegate_list_id chain_database.cpp:1711



[crazybit]

btw, i use command "wallet_account_rename" to change the account name with positive result , but when i wanna change it back, the following error encountered, is the result  expected?

I'm on 5618 right now. The  "blockchain_head_block_time_rel": "10 minutes ago"  is suspicious... Are you on the latest?

i think i am on the lastest

crazybit (unlocked) >>> about
{
  "bitshares_toolkit_revision": "e9582b7fbca06c7dc53f19bc75c0402c7870afa1",
  "bitshares_toolkit_revision_age": "3 hours ago",
  "fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
  "fc_revision_age": "53 hours ago",
  "compile_date": "compiled on Jun 14 2014 at 19:04:15"
}
crazybit (unlocked) >>> get_info
{
  "blockchain_head_block_num": 5730,
  "blockchain_head_block_time": "20140615T035415",
  "blockchain_head_block_time_rel": "27 seconds ago",
  "blockchain_confirmation_requirement": 287,
  "blockchain_average_delegate_participation": 61.587301587301589,
  "network_num_connections": 7,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140615T035442",
  "blockchain_random_seed": "88b0c83dc6fcfa7e2ced9cbfd8be42e8fe6c44dd",
  "blockchain_shares": 10000076678208,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "19700101T000000",
  "wallet_version": 100
}

btw,i upgrade myself to be a delegate, please vote "crazybit" , thanks

[tianshi]

problems on latest build

Code: [Select]

Loading blockchain from "/root/.BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7ffff58ae700 (LWP 27247)]
Listening for P2P connections on port 53893
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
[New Thread 0x7ffff4ead700 (LWP 27248)]
[New Thread 0x7fffeffff700 (LWP 27249)]
--- there are now 1 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
(wallet closed) >>> wallet_open default
OK
default (locked) >>> wallet_unlock 99999999
passphrase:
OK
default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 5141,
  "blockchain_head_block_time": "20140614T235030",
  "blockchain_head_block_time_rel": "in the future",
  "blockchain_confirmation_requirement": 279,
  "blockchain_average_delegate_participation": 57.396449704142015,
  "network_num_connections": 0,
  "wallet_unlocked_seconds_remaining": 99999993,
  "wallet_next_block_production_time": "20140614T235700",
  "wallet_seconds_until_next_block_production": 297,
  "wallet_local_time": "20140614T235203",
  "blockchain_random_seed": "fb039b4dd5ec0bef959de04a02fd0192f3caad69",
  "blockchain_shares": 10000061092614,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20170815T093836",
  "wallet_version": 100
}
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab14aa in EVP_EncryptUpdate ()
(gdb)


That problem has been fixed and we now know the problem for the peer connection issues as well and should have that fixed tonight.

HI BM. you did a good job!

I have some suggestions, i think there are not enough programme developers  for 3I. because 3I has got a lot of money due to AGS, so i suggest that all the staff's (not programmers' ) first priority should be to find more talents to join the team to promote the progress of programming.

we do not lack of money, we have so many things to do, and i thinkg the other employees(not programmers) should really try their every effort to find more talented programmers to join 3I.  and that's even equally imporant than the development of BTS X. 

I do not know if i am right because i know little about softwares, IT or programming. this is just some advices. But I am once in charge of a team of about 100 people, and this is just some of my experience. we should really really pay attention to recruiting more talents to your team and give more time on this job.

At last, hope you guys be successful one day and become heros.


 

[welk1n]

It is working well now ?

Code: [Select]

--- there are now 4 active connections to the p2p network
welk1n (unlocked) >>> info
{
  "blockchain_head_block_num": 5654,
  "blockchain_head_block_time": "20140615T032230",
  "blockchain_head_block_time_rel": "32 seconds ago",
  "blockchain_confirmation_requirement": 285,
  "blockchain_average_delegate_participation": 61.237373737373737,
  "network_num_connections": 4,
  "wallet_unlocked_seconds_remaining": 9996219,
  "wallet_next_block_production_time": "20140615T032915",
  "wallet_seconds_until_next_block_production": 373,
  "wallet_local_time": "20140615T032302",
  "blockchain_random_seed": "ca281b06e58c7f9f52d211baf7911bf38691525d",
  "blockchain_shares": 10000092853224,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20141008T200641",
  "wallet_version": 100
}


Lookin' good!

 ,Thanks!
The four delegates of mine (30,31,32,33)
I use the blockchain_list_delegates commands .
It seems that  they produced blocks well.
Please vote them , thank you !

[toast]

It is working well now ?

Code: [Select]

--- there are now 4 active connections to the p2p network
welk1n (unlocked) >>> info
{
  "blockchain_head_block_num": 5654,
  "blockchain_head_block_time": "20140615T032230",
  "blockchain_head_block_time_rel": "32 seconds ago",
  "blockchain_confirmation_requirement": 285,
  "blockchain_average_delegate_participation": 61.237373737373737,
  "network_num_connections": 4,
  "wallet_unlocked_seconds_remaining": 9996219,
  "wallet_next_block_production_time": "20140615T032915",
  "wallet_seconds_until_next_block_production": 373,
  "wallet_local_time": "20140615T032302",
  "blockchain_random_seed": "ca281b06e58c7f9f52d211baf7911bf38691525d",
  "blockchain_shares": 10000092853224,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20141008T200641",
  "wallet_version": 100
}


Lookin' good!

[welk1n]

It is working well now ?

Code: [Select]

--- there are now 4 active connections to the p2p network
welk1n (unlocked) >>> info
{
  "blockchain_head_block_num": 5654,
  "blockchain_head_block_time": "20140615T032230",
  "blockchain_head_block_time_rel": "32 seconds ago",
  "blockchain_confirmation_requirement": 285,
  "blockchain_average_delegate_participation": 61.237373737373737,
  "network_num_connections": 4,
  "wallet_unlocked_seconds_remaining": 9996219,
  "wallet_next_block_production_time": "20140615T032915",
  "wallet_seconds_until_next_block_production": 373,
  "wallet_local_time": "20140615T032302",
  "blockchain_random_seed": "ca281b06e58c7f9f52d211baf7911bf38691525d",
  "blockchain_shares": 10000092853224,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20141008T200641",
  "wallet_version": 100
}


[Xeldal]

Wipe your old data-dir

Ubuntu: rm -r ~/.BitShares\ XTS

This command has never done anything for me.  I feel I'm missing some implied instruction.  Anyone care to clue me in.

I've just been either completely rebuilding the server from scratch or using the following

Code: [Select]

rm -r bitshares*
and then cloneing etc.

Does this have the same effect?
I notice i still have my wallet and imported keys, where as, when building from scratch I have to re create wallet and import keys again.

# about
tells me im on the latest revision but was i supposed to remove something that "# rm -r bits*"   misses?

[cgafeng]

I rebuild from the latest code.
There only 1 connections on windows and 5 connections on ubuntu.
Are the windows version can't get node?

[toast]

I'm on 5618 right now. The  "blockchain_head_block_time_rel": "10 minutes ago"  is suspicious... Are you on the latest?

btw, i use command "wallet_account_rename" to change the account name with positive result , but when i wanna change it back, the following error encountered, is the result  expected?

Definitely no, filing an issue now

[crazybit]

crazybit (unlocked) >>> get_info
get_info
{
  "blockchain_head_block_num": 5569,
  "blockchain_head_block_time": "20140615T024715",
  "blockchain_head_block_time_rel": "10 minutes ago",
  "blockchain_confirmation_requirement": 289,
  "blockchain_average_delegate_participation": 58.823529411764703,
  "network_num_connections": 0,
  "wallet_unlocked_seconds_remaining": 998702,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140615T025744",
  "blockchain_random_seed": "5595be7ce679bdb82557f88929972129d46ed9c1",
  "blockchain_shares": 10000087488444,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140626T162246",
  "wallet_version": 100
}

am i on the main chain now?

btw, i use command "wallet_account_rename" to change the account name with positive result , but when i wanna change it back, the following error encountered, is the result  expected?

wallet_account_rename james crazybit
10 assert_exception: Assert Exception
!new_account.valid():
    {}
    th_a  wallet.cpp:896 rename_account

    {"old_account_name":"james","new_account_name":"crazybit"}
    th_a  wallet.cpp:901 rename_account

    {}
    th_a  common_api_client.cpp:542 wallet_account_rename

    {"command":"wallet_account_rename"}
    th_a  cli.cpp:547 execute_command

[bytemaster]

Please update your node, if you updated recently there is a bug that can cause problems for other nodes.