Dryrun 7: The Power of DPOS
The power of DPOS is a currious thing,
Make one man weep, make another man sing,
....
You don't need money, don't take fame
Don't need no credit card to ride this chain
Its strong and its sudden and it forks sometimes
But it might just save your life
Thats the power of DPOS
First time you see it, it might make you sad
Next time you see it it might make you mad
But you'll be glad baby when you've found
That's the power makes the world go round
https://www.youtube.com/watch?v=aMkU-Qf_3N0
Start your engines, we are going back to 15 second blocks with a few new features:
1) You can now upgrade registered accounts to delegates and reduce your pay
2) Accelerated transaction validation times
3) All transactions must now expire in less than 48 hours, and by default expire in 24 if they are not included in the chain.
Win GUI http://www.bitshares.org/BitSharesXT-0.0.9.exe (http://www.bitshares.org/BitSharesXT-0.0.9.exe)
Mac GUIhttp://www.bitshares.org/BitSharesXT-0.0.9.dmg (http://www.bitshares.org/BitSharesXT-0.0.9.dmg)
This is a new chain, if you do not delete your data directory from the last chain things may not work.
rm -r ~/Library/Application\ Support/BitShares\ XTS
emski (unlocked) >>> info
{
"blockchain_head_block_num": 191,
"blockchain_head_block_age": "6 seconds old",
"blockchain_head_block_timestamp": "20140701T213330",
"blockchain_average_delegate_participation": 89.252336448598129,
Seems to be OK.
same procedure? data dir should wiped out and then import privkeys?
i am building new client..........
thx. I re create my wallet, it works :)
can't use the backup wallet
yup works for me also - thx
liondani (unlocked) >>> wallet_account_create liondani
"XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv"
some funds please to start the party! :D
about
{
"bitshares_toolkit_revision": "cefbe5fb173846e21568226f9a944fbdbcfbc339",
"bitshares_toolkit_revision_age": "62 minutes ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "2 hours ago",
"compile_date": "compiled on Jul 1 2014 at 14:35:35"
}
>>> list_errors
20140701T214347.113479 (33 minutes ago )
30007 duplicate_transaction: duplicate transaction
{"trx_id":"bbe8260147dcd2ac9b58929e488bb272b99b9168"}
th_a transaction_evaluation_state.cpp:132 evaluate
{"trx":{"expiration":"20140701T234341","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSA5b7kGfSLfbhx9YYRAxUpo6UPGH6L7Dqi","amount":110000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":100000,"condition":{"asset_id":0,"delegate_slate_id":10757185462704248148,"type":"withdraw_signature_type","data":{"owner":"XTSJoC3877y9USqB3VP9EnTnR6kEt9GtXzES","memo":{"one_time_key":"XTS7uUc6TvrPMvSRpmuxNVDwTbYmTrjrTP8pwxfGs1NRD548bGPE9","encrypted_memo_data":"6cc413210387a0136ee3b5e40b3f2544ccf166ecfdb3820c5c1c67c57902aa2478dae9f38140254a35a30289f6b5f10ab866771338eb9932e7e9d5572c05725f"}}}}}],"signatures":["1fd20f43a588738afe5c6f01cd40e5f48b0edf86d5f0855c64ea7873c5241ed1c6f977cbf0617ef23cb45404d05a13b5f2ac695a17721289b87fa192fde62e78d1"]}}
th_a transaction_evaluation_state.cpp:158 evaluate
{"trx":{"expiration":"20140701T234341","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSA5b7kGfSLfbhx9YYRAxUpo6UPGH6L7Dqi","amount":110000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":100000,"condition":{"asset_id":0,"delegate_slate_id":10757185462704248148,"type":"withdraw_signature_type","data":{"owner":"XTSJoC3877y9USqB3VP9EnTnR6kEt9GtXzES","memo":{"one_time_key":"XTS7uUc6TvrPMvSRpmuxNVDwTbYmTrjrTP8pwxfGs1NRD548bGPE9","encrypted_memo_data":"6cc413210387a0136ee3b5e40b3f2544ccf166ecfdb3820c5c1c67c57902aa2478dae9f38140254a35a30289f6b5f10ab866771338eb9932e7e9d5572c05725f"}}}}}],"signatures":["1fd20f43a588738afe5c6f01cd40e5f48b0edf86d5f0855c64ea7873c5241ed1c6f977cbf0617ef23cb45404d05a13b5f2ac695a17721289b87fa192fde62e78d1"]}}
th_a chain_database.cpp:1084 evaluate_transaction
{"trx":{"expiration":"20140701T234341","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSA5b7kGfSLfbhx9YYRAxUpo6UPGH6L7Dqi","amount":110000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":100000,"condition":{"asset_id":0,"delegate_slate_id":10757185462704248148,"type":"withdraw_signature_type","data":{"owner":"XTSJoC3877y9USqB3VP9EnTnR6kEt9GtXzES","memo":{"one_time_key":"XTS7uUc6TvrPMvSRpmuxNVDwTbYmTrjrTP8pwxfGs1NRD548bGPE9","encrypted_memo_data":"6cc413210387a0136ee3b5e40b3f2544ccf166ecfdb3820c5c1c67c57902aa2478dae9f38140254a35a30289f6b5f10ab866771338eb9932e7e9d5572c05725f"}}}}}],"signatures":["1fd20f43a588738afe5c6f01cd40e5f48b0edf86d5f0855c64ea7873c5241ed1c6f977cbf0617ef23cb45404d05a13b5f2ac695a17721289b87fa192fde62e78d1"]}}
th_a chain_database.cpp:1447 store_pending_transaction
Quote from: liondani on July 01, 2014, 10:16:49 PM
liondani (unlocked) >>> wallet_account_create liondani
"XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv"
some funds please to start the party! :D
Sent
Quote from: bitcoinerS on July 01, 2014, 10:18:02 PM
about
{
"bitshares_toolkit_revision": "cefbe5fb173846e21568226f9a944fbdbcfbc339",
"bitshares_toolkit_revision_age": "62 minutes ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "2 hours ago",
"compile_date": "compiled on Jul 1 2014 at 14:35:35"
}
>>> list_errors
20140701T214347.113479 (33 minutes ago )
30007 duplicate_transaction: duplicate transaction
{"trx_id":"bbe8260147dcd2ac9b58929e488bb272b99b9168"}
th_a transaction_evaluation_state.cpp:132 evaluate
{"trx":{"expiration":"20140701T234341","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSA5b7kGfSLfbhx9YYRAxUpo6UPGH6L7Dqi","amount":110000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":100000,"condition":{"asset_id":0,"delegate_slate_id":10757185462704248148,"type":"withdraw_signature_type","data":{"owner":"XTSJoC3877y9USqB3VP9EnTnR6kEt9GtXzES","memo":{"one_time_key":"XTS7uUc6TvrPMvSRpmuxNVDwTbYmTrjrTP8pwxfGs1NRD548bGPE9","encrypted_memo_data":"6cc413210387a0136ee3b5e40b3f2544ccf166ecfdb3820c5c1c67c57902aa2478dae9f38140254a35a30289f6b5f10ab866771338eb9932e7e9d5572c05725f"}}}}}],"signatures":["1fd20f43a588738afe5c6f01cd40e5f48b0edf86d5f0855c64ea7873c5241ed1c6f977cbf0617ef23cb45404d05a13b5f2ac695a17721289b87fa192fde62e78d1"]}}
th_a transaction_evaluation_state.cpp:158 evaluate
{"trx":{"expiration":"20140701T234341","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSA5b7kGfSLfbhx9YYRAxUpo6UPGH6L7Dqi","amount":110000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":100000,"condition":{"asset_id":0,"delegate_slate_id":10757185462704248148,"type":"withdraw_signature_type","data":{"owner":"XTSJoC3877y9USqB3VP9EnTnR6kEt9GtXzES","memo":{"one_time_key":"XTS7uUc6TvrPMvSRpmuxNVDwTbYmTrjrTP8pwxfGs1NRD548bGPE9","encrypted_memo_data":"6cc413210387a0136ee3b5e40b3f2544ccf166ecfdb3820c5c1c67c57902aa2478dae9f38140254a35a30289f6b5f10ab866771338eb9932e7e9d5572c05725f"}}}}}],"signatures":["1fd20f43a588738afe5c6f01cd40e5f48b0edf86d5f0855c64ea7873c5241ed1c6f977cbf0617ef23cb45404d05a13b5f2ac695a17721289b87fa192fde62e78d1"]}}
th_a chain_database.cpp:1084 evaluate_transaction
{"trx":{"expiration":"20140701T234341","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSA5b7kGfSLfbhx9YYRAxUpo6UPGH6L7Dqi","amount":110000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":100000,"condition":{"asset_id":0,"delegate_slate_id":10757185462704248148,"type":"withdraw_signature_type","data":{"owner":"XTSJoC3877y9USqB3VP9EnTnR6kEt9GtXzES","memo":{"one_time_key":"XTS7uUc6TvrPMvSRpmuxNVDwTbYmTrjrTP8pwxfGs1NRD548bGPE9","encrypted_memo_data":"6cc413210387a0136ee3b5e40b3f2544ccf166ecfdb3820c5c1c67c57902aa2478dae9f38140254a35a30289f6b5f10ab866771338eb9932e7e9d5572c05725f"}}}}}],"signatures":["1fd20f43a588738afe5c6f01cd40e5f48b0edf86d5f0855c64ea7873c5241ed1c6f977cbf0617ef23cb45404d05a13b5f2ac695a17721289b87fa192fde62e78d1"]}}
th_a chain_database.cpp:1447 store_pending_transaction
Some times we receive the same transaction twice, in this case these errors are harmless and we will probably stop logging them.
I removed / cleaned up some posts so new users don't have to see some of the early issues they are unlikely to experience.
10 assert_exception: Assert Exception
account_name.size(): You must specify an account name because the private key does not belong to any known accounts
Help pls .. how i could enter account?
Quote from: cass on July 01, 2014, 10:35:28 PM
10 assert_exception: Assert Exception
account_name.size(): You must specify an account name because the private key does not belong to any known accounts
Help pls .. how i could enter account?
wallet_account_create name
wallet_import_private_key KEY name
We are now handling 2 trx per second with no missed blocks or forks.
Quote from: bytemaster on July 01, 2014, 10:20:27 PM
Quote from: liondani on July 01, 2014, 10:16:49 PM
liondani (unlocked) >>> wallet_account_create liondani
"XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv"
some funds please to start the party! :D
Sent
thanks... Marty McFly ;)
Quote from: bytemaster on July 01, 2014, 10:44:01 PM
Quote from: cass on July 01, 2014, 10:35:28 PM
10 assert_exception: Assert Exception
account_name.size(): You must specify an account name because the private key does not belong to any known accounts
Help pls .. how i could enter account?
wallet_account_create name
wallet_import_private_key KEY name
thx yes i get message >>>> ok ; but after rescan blockchain ... i don't see my funded account on acc overview
I made the right steps to create a delegate but with the command
blockchain_list_delegates
I don't see my name "liondani" ???
liondani (unlocked) >>> wallet_account_register liondani liondani null 99
{
"index": 10,
"trx": {
"expiration": "20140702T003748",
"delegate_slate_id": null,
"operations": [{
"type": "register_account_op_type",
"data": {
"name": "liondani",
"public_data": null,
"owner_key": "XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv",
"active_key": "XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv",
"delegate_pay_rate": 99,
"meta_data": null
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTS44u4CafBUNTWXQJSu8Re2guHDrHetGiMA",
"amount": 18739,
"claim_input_data": ""
}
}
],
"signatures": [
"1f8c53b72f3caaa51ae229f638a26280be4bb138bd**********************************17e73236b91feaf8a1ef00edab11498f1862e8"
]
},
"transaction_id": "c1728e5f62d6e210cffbac0d379916f1e3688b76",
"to_account": "XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv",
"from_account": "XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv",
"amount": {
"amount": 0,
"asset_id": 0
},
"fees": 18739,
"memo_message": "register liondani as a delegate",
"created_time": "20140701T223748",
"received_time": "20140701T223748",
"block_num": 0,
"transmit_count": 0
}
liondani (unlocked) >>> wallet_approve_delegate liondani true
OK
liondani (unlocked) >>> wallet_approve_delegate liondani true
OK
liondani (unlocked) >>> info
{
"blockchain_head_block_num": 479,
"blockchain_head_block_age": "0 second old",
"blockchain_head_block_timestamp": "20140701T224815",
"blockchain_average_delegate_participation": 93.372319688109158,
"blockchain_blocks_left_in_round": 26,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999978076557,
"blockchain_random_seed": "f0c0a5a8e55e1affb5afd63068e8226361ab6c00",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140701T224815",
"ntp_error": -0.016229,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "20140713T120035",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
liondani (unlocked) >>> about
{
"bitshares_toolkit_revision": "6b59f34f1941b67978252271ef98bc206c6091c0",
"bitshares_toolkit_revision_age": "66 minutes ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "3 hours ago",
"compile_date": "compiled on Jul 2 2014 at 01:09:29"
}
liondani (unlocked) >>> wallet_account_balance
liondani:
999.81261 XTS
liondani (unlocked) >>> blockchain_list_delegates
ID NAME APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
------------------------------------------------------------------------------------------------------------------------
7 init6 0.0687500156 % 4 2 66.67 % 100 % 0.08496 XTS 514
4 init3 0.0687500143 % 2 3 40.00 % 100 % 0.05946 XTS 504
5 init4 0.0687500135 % 4 2 66.67 % 100 % 0.04264 XTS 452
309 vikram2 0.0687500133 % 2 0 100.00 % 100 % 0.03880 XTS 464
300 vikram11 0.0625000140 % 3 0 100.00 % 100 % 0.07280 XTS 506
302 vikram9 0.0625000130 % 2 0 100.00 % 100 % 0.05447 XTS 495
305 vikram4 0.0625000127 % 2 0 100.00 % 100 % 0.04864 XTS 484
304 vikram12 0.0625000125 % 2 0 100.00 % 100 % 0.04407 XTS 474
6 init5 0.0625000120 % 4 2 66.67 % 100 % 0.03322 XTS 424
312 vikram15 0.0625000116 % 2 0 100.00 % 100 % 0.02530 XTS 434
308 vikram10 0.0625000113 % 2 0 100.00 % 100 % 0.02017 XTS 412
298 vikram1 0.0562500144 % 3 0 100.00 % 100 % 0.10201 XTS 510
306 vikram5 0.0562500121 % 2 0 100.00 % 100 % 0.05707 XTS 500
299 vikram8 0.0562500119 % 2 0 100.00 % 100 % 0.05279 XTS 492
311 vikram13 0.0562500112 % 2 0 100.00 % 100 % 0.03894 XTS 465
303 vikram7 0.0562500111 % 2 0 100.00 % 100 % 0.03633 XTS 460
313 vikram16 0.0562500105 % 2 0 100.00 % 100 % 0.02340 XTS 427
301 vikram3 0.0500000094 % 2 0 100.00 % 100 % 0.02251 XTS 422
307 vikram6 0.0437500091 % 2 0 100.00 % 100 % 0.03715 XTS 461
310 vikram14 0.0375000097 % 3 0 100.00 % 100 % 0.06998 XTS 505
324 bits 0.0249499802 % 1 0 100.00 % 100 % 0.01001 XTS 413
315 bitcoiners 0.0244499402 % 1 1 50.00 % 100 % 0.01006 XTS 393
325 blockchainer 0.0125000021 % 0 0 -nan % 100 % 0.00000 XTS NONE
321 delegate-baozi 0.0098500032 % 1 0 100.00 % 100 % 0.03160 XTS 470
319 delegate-alt 0.0071500036 % 1 0 100.00 % 100 % 0.04746 XTS 501
322 delegate-watchman 0.0069500016 % 1 0 100.00 % 100 % 0.01004 XTS 410
323 delegate-dragon 0.0058000020 % 1 0 100.00 % 100 % 0.02022 XTS 448
320 delegate-dorian 0.0057500021 % 1 0 100.00 % 100 % 0.02321 XTS 454
296 lotto 0.0055317531 % 3 0 100.00 % 100 % 0.04329 XTS 472
297 emski-delegate3 0.0055314021 % 3 0 100.00 % 44 % 0.02460 XTS 497
314 xeldal 0.0050000018 % 2 0 100.00 % 100 % 0.02038 XTS 415
329 delegate-fenglang 0.0025000004 % 0 0 -nan % 100 % 0.00000 XTS NONE
327 delegate-cgafeng 0.0020000003 % 0 1 0.00 % 100 % 0.00000 XTS NONE
332 dele-puppy 0.0002804565 % 0 0 -nan % 10 % 0.00000 XTS NONE
338 happyshares-10 0.0002000000 % 0 0 -nan % 100 % 0.00000 XTS NONE
342 happyshares-3 0.0001750000 % 0 0 -nan % 100 % 0.00000 XTS NONE
336 happyshares-5 0.0001500000 % 0 0 -nan % 100 % 0.00000 XTS NONE
337 happyshares-6 0.0001500000 % 0 0 -nan % 100 % 0.00000 XTS NONE
344 happyshares-7 0.0001500000 % 0 0 -nan % 100 % 0.00000 XTS NONE
341 happyshares-8 0.0001250026 % 1 0 100.00 % 100 % 0.05093 XTS 508
335 happyshares-1 0.0001250000 % 0 0 -nan % 100 % 0.00000 XTS NONE
330 sexy 0.0001111000 % 0 0 -nan % 80 % 0.00000 XTS NONE
340 happyshares-9 0.0001000000 % 0 0 -nan % 100 % 0.00000 XTS NONE
343 happyshares-4 0.0001000000 % 0 0 -nan % 100 % 0.00000 XTS NONE
339 happyshares-2 0.0000750000 % 0 0 -nan % 100 % 0.00000 XTS NONE
326 chinese 0.0000555500 % 0 0 -nan % 80 % 0.00000 XTS NONE
331 pan2pan 0.0000555500 % 0 0 -nan % 80 % 0.00000 XTS NONE
295 angel 0.0000050013 % 3 0 100.00 % 100 % 0.02536 XTS 433
75 init74 0.0000000055 % 6 0 100.00 % 100 % 0.11037 XTS 507
52 init51 0.0000000050 % 7 0 100.00 % 100 % 0.10077 XTS 513
30 init29 0.0000000049 % 7 0 100.00 % 100 % 0.09841 XTS 512
Quote from: bytemaster on July 01, 2014, 10:44:30 PM
We are now handling 2 trx per second with no missed blocks or forks.
(https://c2.staticflickr.com/8/7121/6866942206_2a1ddf562c.jpg)
Quote from: alt on July 01, 2014, 10:01:23 PM
thx. I re create my wallet, it works :)
can't use the backup wallet
For back up your wallet, it's better to choose "wallet_export_to_json" and "wallet_create_from_json", rather than backup the wallet folder.
Quote from: vlight on July 01, 2014, 11:11:09 PM
Quote from: liondani on July 01, 2014, 11:01:56 PM
I made the right steps to create a delegate but with the command
blockchain_list_delegates
I don't see my name "liondani" ???
We are at the bottom
"blockchain_list_delegates [first] [count]"
thanks ;)
liondani (unlocked) >>> wallet_approve_delegate light true
OK
Quote from: bytemaster on July 01, 2014, 10:44:30 PM
We are now handling 2 trx per second with no missed blocks or forks.
+5% +5% +5%
:)
con!
Quote from: HackFisher on July 01, 2014, 11:13:04 PM
Quote from: alt on July 01, 2014, 10:01:23 PM
thx. I re create my wallet, it works :)
can't use the backup wallet
For back up your wallet, it's better to choose "wallet_export_to_json" and "wallet_create_from_json", rather than backup the wallet folder.
thx :)
XTS6cGg9pwp2etirVRc9RKyJS2Vph6UBDW4GS8GrsMH9pfYkqCd3T some funds pls ..thx
edit: thx vlight :)
Quote from: cass on July 01, 2014, 11:35:19 PM
XTS6cGg9pwp2etirVRc9RKyJS2Vph6UBDW4GS8GrsMH9pfYkqCd3T some funds pls ..thx
edit: thx vlight :)
liondani (locked) >>> wallet_transfer 100 XTS liondani cassFinished scanning for new transactions.
OK
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-01T23:41:46 liondani cass 100.00000 XTS 0.10000 XTS 0a5b8a6c
now I know why his name is v
light 8)
but still don't get my old account imported ...
Building. Definitely smoother than the last few times. Gonna get back to this thread tomorrow morning.
Great work bytemaster!
Quote from: cass on July 01, 2014, 11:46:57 PM
but still don't get my old account imported ...
This is a chain reset (a brand new chain), so even you have the backup private keys, there are no registered accounts binding to it (suppose they are not the accounts in genesis block).
liondani (unlocked) >>> wallet_account_transaction_history liondani
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
438.0 2014-07-01T22:38:00 liondani liondani 0000000 XTS 0.18739 XTS register liondani as a delegate c1728e5f
the fee of 0.18739 XTS to create a delegate was not a mistake I suppose?
Quote from: HackFisher on July 01, 2014, 11:51:04 PM
Quote from: cass on July 01, 2014, 11:46:57 PM
but still don't get my old account imported ...
This is a chain reset (a brand new chain), so even you have the backup private keys, there are no registered accounts binding to it (suppose they are not the accounts in genesis block).
thx for info
press test begin from block 745.
1000 transactions coming....
the most latency is 9 seconds.
I think we can limit the speed of trx broadcast too, if we have limit the trx confirm speed to 2trx/s.
Can you send some XTS to me for testing dry run 7?
mywallet (unlocked) >>> wallet_account_create jeffreylee
"XTS5i1eWiWThrZgYVjNruQZuZW2vQKZtjEeZjRJMqev3S9XnheFw9"
sent
+5%
can't wait to see the formal release.
would it be better for the original BTSX chain that
1 node = max 1 delegate ? (or max y delegates)
Because someone he don't "respect" money(for a reason/plan) and want to harm bitshares (especially at the beginning) would spam the network with hundreds of delegates (not with the same name of-course) and control at the end in some point the network... Am I missing something?
PS + it will be not fair for the poor delegates....
PS2 I saw the last days so much delegates from "init" that's why I was thinking about it.... If somebody has so much delegates compared with the network, even if he has the worst equipment, statistically he will sign the most of the total blocks (all from same delegates owner)
+5% +5%
max one delegate per client and Max 5 delegates per IP
Quote from: liondani on July 02, 2014, 12:55:38 AM
would it be better for the original BTSX chain that
1 node = max 1 delegate ?
Because someone he don't "respect" money(for a reason/plan) and want to harm bitshares (especially at the beginning) would spam the network with hundreds of delegates (not with the same name of-course) and control at the end in some point the network... Am I missing something?
PS + it will be not fair for the poor delegates....
wallet_transfer 111 XTS chinese a1 "mmmmm"
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-02T01:05:36 chinese a1 111.00000 XTS 0.10000 XTS mmmmm 6343a789
Quote from: JeffreyLee on July 02, 2014, 12:31:41 AM
Can you send some XTS to me for testing dry run 7?
mywallet (unlocked) >>> wallet_account_create jeffreylee
"XTS5i1eWiWThrZgYVjNruQZuZW2vQKZtjEeZjRJMqev3S9XnheFw9"
Quote from: sfinder on July 02, 2014, 01:03:18 AM
+5% +5%
max one delegate per client and Max 5 delegates per IP
something like that...
PS What think you about our concerns bytemaster?
Quote from: liondani on July 02, 2014, 01:17:42 AM
Quote from: sfinder on July 02, 2014, 01:03:18 AM
+5% +5%
max one delegate per client and Max 5 delegates per IP
something like that...
PS What think you about our concerns bytemaster?
Neither of those constraints stop me from making many delegates, and having many delegates is not an attack since they still have to get voted in.
In other words, who cares, and why?
Quote from: liondani on July 02, 2014, 01:17:42 AM
Quote from: sfinder on July 02, 2014, 01:03:18 AM
+5% +5%
max one delegate per client and Max 5 delegates per IP
something like that...
PS What think you about our concerns bytemaster?
I think the main issue with this type of restriction is that someone trying to damage the system will just write it out of their clients. My understanding is that a node rebroadcasting a block looks exactly like a delegate broadcasting it for the first time. If for no other reason we should maintain that semi anonymity for delegates to prevent DDOS attacks from crippling the system.
Quote from: puppies on July 02, 2014, 01:23:45 AM
Quote from: liondani on July 02, 2014, 01:17:42 AM
Quote from: sfinder on July 02, 2014, 01:03:18 AM
+5% +5%
max one delegate per client and Max 5 delegates per IP
something like that...
PS What think you about our concerns bytemaster?
I think the main issue with this type of restriction is that someone trying to damage the system will just write it out of their clients. My understanding is that a node rebroadcasting a block looks exactly like a delegate broadcasting it for the first time. If for no other reason we should maintain that semi anonymity for delegates to prevent DDOS attacks from crippling the system.
+1
It is all about getting the approval to stay in.
the new wallet looks absolutely unreal!
Quote from: clout on July 02, 2014, 01:34:28 AM
the new wallet looks absolutely unreal!
Cass's magic touch ;)
Quote
Quote from: toast on July 02, 2014, 01:21:11 AM
Quote from: liondani on July 02, 2014, 01:17:42 AM
Quote from: sfinder on July 02, 2014, 01:03:18 AM
+5% +5%
max one delegate per client and Max 5 delegates per IP
something like that...
PS What think you about our concerns bytemaster?
Quote
Neither of those constraints stop me from making many delegates...
It must be not only money depended if possible...
Quote
....and having many delegates is not an attack since they still have to get voted in.
In other words, who cares, and why?
I disagree. I will explain tomorrow my reasoning's with examples...
PS theoretical you are right of course
Some command changes:
renamed wallet_enable_delegate_block_production -> wallet_delegate_set_block_production
renamed wallet_withdraw_delegate_pay -> wallet_delegate_withdraw_pay
added wallet_delegate_set_transaction_scanning: if you want to live dangerously
This is me right now.... https://www.youtube.com/watch?v=AM5EYO5wWMA#t=118
I am waiting for Windows GUI. :)
Quote from: bytemaster on July 02, 2014, 01:40:28 AM
This is me right now.... https://www.youtube.com/watch?v=AM5EYO5wWMA#t=118
lol :D
cheers
Scanning for new transactions looks like slow...
liondani (unlocked) >>> blockchain_list_forks
No forks.
(http://1.bp.blogspot.com/-7VGKYK_du8w/U7NmaR9onoI/AAAAAAAAC9Q/CRT5NJl9wRQ/s1600/noforks.png)
Up and running, some funding would be nice "XTS6sNSFLArmweG2btYXvB3eYjBtuWHhFBAUG3e6CkzuchrPQi31B"
Thanks in advance,
Support Bitsapphire
http://bitsapphire.com/Bitshares-Delegate/
Quote from: maverica on July 02, 2014, 01:59:33 AM
Up and running, some funding would be nice "XTS6sNSFLArmweG2btYXvB3eYjBtuWHhFBAUG3e6CkzuchrPQi31B"
Thanks in advance,
Support Bitsapphire
http://bitsapphire.com/Bitshares-Delegate/
sent
Quote from: dexinwong on July 02, 2014, 01:41:11 AM
I am waiting for Windows GUI. :)
Here you go http://valzav.com/BitSharesXT-0.0.8.exe
XTS6eoybjKRZun6NgxuL7UW6A5hRfcapcHGG3Ls12YDUTKGUaFsHL
Please send some funds, thx.
Quote from: radiumlau on July 02, 2014, 03:20:13 AM
XTS6eoybjKRZun6NgxuL7UW6A5hRfcapcHGG3Ls12YDUTKGUaFsHL
Please send some funds, thx.
sent 111 xts
I need some XTS for test. Can someone send me some? Thanks!
account:networker
address: XTS8kMTXnSdk6PL9hobTKpEXcYZRFzmL9cXt
waiting for the mac Gui
Quote from: valzav on July 02, 2014, 03:16:15 AM
Quote from: dexinwong on July 02, 2014, 01:41:11 AM
I am waiting for Windows GUI. :)
Here you go http://valzav.com/BitSharesXT-0.0.8.exe
thanks, but we should not use wallet not released by I3, for the security reason.
Looking for some funds to register an account as a delegate.
wallet_account_create fox-delegate-98
"XTS6v8tFJEVEtFtNSJk7tHpEiTYyiEAag15wMsBZd87aFG3CcQXEa"
Thanks in advance!
Quote from: Fox on July 02, 2014, 03:40:48 AM
Looking for some funds to register an account as a delegate.
wallet_account_create fox-delegate-98
"XTS6v8tFJEVEtFtNSJk7tHpEiTYyiEAag15wMsBZd87aFG3CcQXEa"
Thanks in advance!
sent
i sent funds to myself. found the transaction in block 1462 but I did not receive the funds in my account. my wallet showed the transaction previously. i cleared the pending transactions and that transaction disappeared but the funds were not in my account. what does this mean?
Quote from: clout on July 02, 2014, 04:09:18 AM
i sent funds to myself. found the transaction in block 1462 but I did not receive the funds in my account. my wallet showed the transaction previously. i cleared the pending transactions and that transaction disappeared but the funds were not in my account. what does this mean?
Maybe wait 24 hour
Quote from: ebit on July 02, 2014, 04:12:12 AM
Quote from: clout on July 02, 2014, 04:09:18 AM
i sent funds to myself. found the transaction in block 1462 but I did not receive the funds in my account. my wallet showed the transaction previously. i cleared the pending transactions and that transaction disappeared but the funds were not in my account. what does this mean?
Maybe wait 24 hour
is it delegate wallet? if yes , you many not able to see your updated balance. need to create a new wallet with delegate production disable
alt: Thanks for the funds. fox-delegate-98 all set and produced its first block (1857).
All:
I cannot seem to make proper use of my wallet from the Dry Run 6 within the current client on Dry Run 7. Oddly, I can receive funds to my named account, but cannot send them.
The wallet contains the account "fox" imported from Keyhotee a few rounds back. I've built a clean Bitshares Client on a new VM and copied the "wallets" folder to the ~\.BitSharesXTS folder. The client starts normally, and successfully opens, unlocks and lists a balance.
about
"bitshares_toolkit_revision": "57d5b15aecb682d8426d067458fec2da851b248f",
"bitshares_toolkit_revision_age": "3 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "9 hours ago",
"compile_date": "compiled on Jul 2 2014 at 04:04:17"
get_info
{
"blockchain_head_block_num": 1917,
"blockchain_head_block_age": "36 seconds old",
"blockchain_head_block_timestamp": "20140702T045330",
"blockchain_average_delegate_participation": 98.92262487757101,
"blockchain_blocks_left_in_round": 2,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999593864828,
"blockchain_random_seed": "577ce365588a0bbc0efb115efa67ead8a6223d93",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T045406",
"ntp_error": -0.37929400000000002,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "27 hours in the future",
"wallet_unlocked_until_timestamp": "20140703T080438",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
The account is registered on the blockchain:
blockchain_list_accounts fox 1
I can receive funds, but sending fails:
wallet_transfer 100 XTS fox alt "thanks for the funds"
7 bad_cast_exception: Bad Cast
Invalid cast from type 'int64_type' to Object
{"type":"int64_type"}
th_a variant.cpp:505 get_object
{}
th_a wallet.cpp:2492 get_priority_fee
{"real_amount_to_transfer":100,"amount_to_transfer_symbol":"XTS","from_account_name":"fox","to_account_name":"alt","memo_message":"thanks for the funds"}
th_a wallet.cpp:1877 transfer_asset
{}
th_a common_api_client.cpp:771 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:538 execute_command
What must I do to resolve my sending issues and restore full wallet functionality? Perhaps my wallet copy/paste (export/import) method is flawed. Any insight is greatly appreciated.
-Fox
XTSDHscJaQZYn7qzmhGWd3uUY49xD7W62Beb
Please send some XTS, thanks a lot.
XTS8WtZMx61kxVawKs1F17bwR7HEorm9KfhHTjxkKR5DcFuNPmNUJ
account name:uinno
beg some funds plz..thanks!
Quote from: lzr1900 on July 02, 2014, 05:31:28 AM
XTS8WtZMx61kxVawKs1F17bwR7HEorm9KfhHTjxkKR5DcFuNPmNUJ
account name:uinno
beg some funds plz..thanks!
sent
Quote from: cgafeng on July 02, 2014, 05:35:31 AM
Quote from: lzr1900 on July 02, 2014, 05:31:28 AM
XTS8WtZMx61kxVawKs1F17bwR7HEorm9KfhHTjxkKR5DcFuNPmNUJ
account name:uinno
beg some funds plz..thanks!
sent
thank you so much.received.:D
Quote from: valzav on July 02, 2014, 03:16:15 AM
Quote from: dexinwong on July 02, 2014, 01:41:11 AM
I am waiting for Windows GUI. :)
Here you go http://valzav.com/BitSharesXT-0.0.8.exe
Thanks for your share.
Quote from: clout on July 02, 2014, 04:09:18 AM
i sent funds to myself. found the transaction in block 1462 but I did not receive the funds in my account. my wallet showed the transaction previously. i cleared the pending transactions and that transaction disappeared but the funds were not in my account. what does this mean?
Disable block production，then rescan wallet.
@bytemaste
QuoteAll transactions must now expire in less than 48 hours
.
All？Really？Why？
damn, still cannot import keyhotee, problem is in my brainkey because it contains characters like "!" and "@", after "!" no letters are scanned and get wrong keyhotee id scanned :-\
so i join to the population of beggars, please send me some funds to play with
domis-1
XTS8c3oGHR9XNSRPV9yYZspcPC2HMowrp6pyadyywpRMFeCSw94E8
thanks
Quote from: radiumlau on July 02, 2014, 05:12:29 AM
XTSDHscJaQZYn7qzmhGWd3uUY49xD7W62Beb
Please send some XTS, thanks a lot.
give the right "
native_pubkey"
to find your "native_pubkey" type command
wallet_account_list_public_keys [account_name]
and the post it here again... ;)
PS seems you gave us the "native_address"...
EDIT: I manage to sent you 50 XTS to the address you posted a few post's back .... XTS6eoybjKRZun6NgxuL7UW6A5hRfcapcHGG3Ls12YDUTKGUaFsHL
Can I have some funds to start my delegate?
(I read about export to json too late)
scroodge XTS67u5mjusU3XXna7EmqyeGedMwREEUYKg7k5g6GeFTLqyLBEify
Thx a lot!
Quote from: alt on July 02, 2014, 03:37:45 AM
Quote from: valzav on July 02, 2014, 03:16:15 AM
Quote from: dexinwong on July 02, 2014, 01:41:11 AM
I am waiting for Windows GUI. :)
Here you go http://valzav.com/BitSharesXT-0.0.8.exe
thanks, but we should not use wallet not released by I3, for the security reason.
+5% +5% +5%
Quote from: dxtr on July 02, 2014, 06:56:41 AM
Can I have some funds to start my delegate?
(I read about export to json too late)
scroodge XTS67u5mjusU3XXna7EmqyeGedMwREEUYKg7k5g6GeFTLqyLBEify
Thx a lot!
sent
XTS6TtY8Mf97nyqtqjRg94NobLY15Korc3XNXFzkuXj1oiTex5GNs
beg some funds plz!
Quote from: dexinwong on July 02, 2014, 07:16:51 AM
XTS6TtY8Mf97nyqtqjRg94NobLY15Korc3XNXFzkuXj1oiTex5GNs
beg some funds plz!
sent
some fuel sent @ dexinwong / domis-1 / radiumlau2 / scroodge /
Quote from: CalabiYau on July 02, 2014, 08:05:15 AM
some fuel sent @ dexinwong / domis-1 / radiumlau2 / scroodge /
sent
only error with radiumlau2
liondani (unlocked) >>> wallet_transfer 33 XTS liondani radiumlau2
10 assert_exception: Assert Exception
is_valid_account( to_account_name ):
{}
th_a wallet.cpp:1792 transfer_asset
{"real_amount_to_transfer":33,"amount_to_transfer_symbol":"XTS","from_account_name":"liondani","to_account_name":"radiumlau2","memo_message":""}
th_a wallet.cpp:1874 transfer_asset
{}
th_a common_api_client.cpp:771 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:538 execute_command
Quote from: liondani on July 02, 2014, 08:15:16 AM
Quote from: CalabiYau on July 02, 2014, 08:05:15 AM
some fuel sent @ dexinwong / domis-1 / radiumlau2 / scroodge /
sent
radiumlau2 XTS8k9Vv9MBMgJcivZFgNa41jBW5wsVAH9c3Pwv9cNQTrba3oz8iF
name due to "forensic" address approach ;)
sent
Quote from: clout on July 02, 2014, 04:09:18 AM
i sent funds to myself. found the transaction in block 1462 but I did not receive the funds in my account. my wallet showed the transaction previously. i cleared the pending transactions and that transaction disappeared but the funds were not in my account. what does this mean?
If you have any enabled delegate accounts, try using the 'wallet_delegate_enable_transaction_scanning true' command and then rescan that block. Let us know if this does not fix the problem.
Quote from: Fox on July 02, 2014, 05:01:51 AM
alt: Thanks for the funds. fox-delegate-98 all set and produced its first block (1857).
All:
I cannot seem to make proper use of my wallet from the Dry Run 6 within the current client on Dry Run 7. Oddly, I can receive funds to my named account, but cannot send them.
The wallet contains the account "fox" imported from Keyhotee a few rounds back. I've built a clean Bitshares Client on a new VM and copied the "wallets" folder to the ~\.BitSharesXTS folder. The client starts normally, and successfully opens, unlocks and lists a balance.
about
"bitshares_toolkit_revision": "57d5b15aecb682d8426d067458fec2da851b248f",
"bitshares_toolkit_revision_age": "3 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "9 hours ago",
"compile_date": "compiled on Jul 2 2014 at 04:04:17"
get_info
{
"blockchain_head_block_num": 1917,
"blockchain_head_block_age": "36 seconds old",
"blockchain_head_block_timestamp": "20140702T045330",
"blockchain_average_delegate_participation": 98.92262487757101,
"blockchain_blocks_left_in_round": 2,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999593864828,
"blockchain_random_seed": "577ce365588a0bbc0efb115efa67ead8a6223d93",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T045406",
"ntp_error": -0.37929400000000002,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "27 hours in the future",
"wallet_unlocked_until_timestamp": "20140703T080438",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
The account is registered on the blockchain:
blockchain_list_accounts fox 1
I can receive funds, but sending fails:
wallet_transfer 100 XTS fox alt "thanks for the funds"
7 bad_cast_exception: Bad Cast
Invalid cast from type 'int64_type' to Object
{"type":"int64_type"}
th_a variant.cpp:505 get_object
{}
th_a wallet.cpp:2492 get_priority_fee
{"real_amount_to_transfer":100,"amount_to_transfer_symbol":"XTS","from_account_name":"fox","to_account_name":"alt","memo_message":"thanks for the funds"}
th_a wallet.cpp:1877 transfer_asset
{}
th_a common_api_client.cpp:771 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:538 execute_command
What must I do to resolve my sending issues and restore full wallet functionality? Perhaps my wallet copy/paste (export/import) method is flawed. Any insight is greatly appreciated.
-Fox
It is currently not recommended to keep wallets between Dry Runs, but for this particular issue, you can try running 'wallet_set_priority_fee 0.1' to fix it.
DATE FROM TO MEMO AMOUNT FEE
2014年7月2日 GMT+8下午4:13:00 liondani dexinwong 33 XTS 0 XTS
2014年7月2日 GMT+8下午3:40:15 liondani dexinwong 50 XTS 0 XT
:D :D :D
Quote from: Kenof on July 02, 2014, 05:50:48 AM
damn, still cannot import keyhotee, problem is in my brainkey because it contains characters like "!" and "@", after "!" no letters are scanned and get wrong keyhotee id scanned :-\
so i join to the population of beggars, please send me some funds to play with
domis-1
XTS8c3oGHR9XNSRPV9yYZspcPC2HMowrp6pyadyywpRMFeCSw94E8
thanks
So even entering you brainkey in quotes "<brainkey>" does not work?
If you are on Windows, you can try running the latest nightly build of Keyhotee from: http://bitshares.org/resources/downloads/ which has a button to copy your private key for an identity. You can then import this private key into the BitShares client using 'wallet_import_private_key <keyhotee_private_key>'. I was able to successfully claim my name from the genesis block using this method. Updated Mac and Linux Keyhotee builds coming soon.
Others please let us know if you have trouble with the brainkeys as well.
Quote from: vlight on July 02, 2014, 08:57:43 AM
Found this today:
wallet-1 (unlocked) >>>
Program received signal SIGBUS, Bus error.
__memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:37
37 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory.
(gdb)
Then tried to run and exit manually and got this:
(wallet closed) >>> exit
[Thread 0x7fffebd3d700 (LWP 7840) exited]
Program received signal SIGSEGV, Segmentation fault.
bts::db::level_map<fc::ripemd160, bts::blockchain::block_record>::find (this=0xe8, key=...)
at /root/bitshares_toolkit/libraries/db/include/bts/db/level_map.hpp:170
170 iterator itr( _db->NewIterator( ldb::ReadOptions() ) );
(gdb)
Restarted the whole system and everything works , for now. ???
Make sure you are using the latest build and wiped your data directory from the previous dry run, and let us know if it happens again. Thanks!
Quote from: vlight on July 02, 2014, 08:57:43 AM
Found this today:
wallet-1 (unlocked) >>>
Program received signal SIGBUS, Bus error.
__memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:37
37 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory.
(gdb)
happened to me too in a previous run, searched for quite some time, and then realized this happened because I ran out of space on my VPS (because p2p.log exploded and ate > 50GB). Maybe this is the same for you (and the reboot cleaned some stuff hence why it seems to work for you now)
delegate (unlocked) >>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2840
e44923abbdc141cb2fa3e9338d89029e152256c7 vikram10 34 8862 2014-07-02T09:11:00 2 YES NO
6f1a88b185cf482735dc3921ab9f090bae9146e9 alexxy 32 8854 2014-07-02T09:10:45 18 YES YES
get 1 fork
delegate (unlocked) >>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2840
6f1a88b185cf482735dc3921ab9f090bae9146e9 alexxy 32 8854 2014-07-02T09:10:45 16 YES YES
e44923abbdc141cb2fa3e9338d89029e152256c7 vikram10 34 8862 2014-07-02T09:11:00 4 N/A NO
alexxy should produce block 2841 at 09:10:45, but I get this block at 09:11:01(latency 16s)
vikram10 didn't get that block in time by alexxy obvious, produce another block after 2840 at 09:11:00.
delegate (unlocked) >>> blockchain_list_blocks 2840 3
HEIGHT TIMESTAMP SIGNING DELEGATE # TXS SIZE TOTAL FEES LATENCY PROCESSING TIME
-------------------------------------------------------------------------------------------------------------------
2840 2014-07-02T09:10:30 init76 31 8717 3.10000 XTS 3 0.626981
2841 2014-07-02T09:10:45 alexxy 32 8854 3.20000 XTS 16 0.634879
N/A MISSED N/A N/A N/A N/A N/A N/A
2842 2014-07-02T09:11:15 testz 33 8714 3.30000 XTS 5 0.613875
Quote from: vikram on July 02, 2014, 08:54:59 AM
So even entering you brainkey in quotes "<brainkey>" does not work?
(...)
Others please let us know if you have trouble with the brainkeys as well.
This hint solved my "é" problem - import o.k. thx
May I ask if you guys are planning to add some functionality that's allowing automatic payouts from a delegate to a configurable account after defined threshold is crossed?
Quote from: valzav on July 02, 2014, 03:16:15 AM
Quote from: dexinwong on July 02, 2014, 01:41:11 AM
I am waiting for Windows GUI. :)
Here you go http://valzav.com/BitSharesXT-0.0.8.exe
Added to OP (https://bitsharestalk.org/index.php?topic=5381.msg71795#msg71795) and even uploaded it to bitshares.org
https://bitsharestalk.org/index.php?topic=5381.msg71795#msg71795
Quote from: cass on July 02, 2014, 10:10:09 AM
Quote from: valzav on July 02, 2014, 03:16:15 AM
Quote from: dexinwong on July 02, 2014, 01:41:11 AM
I am waiting for Windows GUI. :)
Here you go http://valzav.com/BitSharesXT-0.0.8.exe
Added to OP (https://bitsharestalk.org/index.php?topic=5381.msg71795#msg71795) and even uploaded it to bitshares.org
https://bitsharestalk.org/index.php?topic=5381.msg71795#msg71795
Cheers!thx!
Quote from: CalabiYau on July 02, 2014, 08:29:22 AM
Quote from: liondani on July 02, 2014, 08:15:16 AM
Quote from: CalabiYau on July 02, 2014, 08:05:15 AM
some fuel sent @ dexinwong / domis-1 / radiumlau2 / scroodge /
sent
radiumlau2 XTS8k9Vv9MBMgJcivZFgNa41jBW5wsVAH9c3Pwv9cNQTrba3oz8iF
name due to "forensic" address approach ;)
some EUR sent :)
Quote from: lzr1900 on July 02, 2014, 10:13:13 AM
Quote from: cass on July 02, 2014, 10:10:09 AM
Quote from: valzav on July 02, 2014, 03:16:15 AM
Quote from: dexinwong on July 02, 2014, 01:41:11 AM
I am waiting for Windows GUI. :)
Here you go http://valzav.com/BitSharesXT-0.0.8.exe
Added to OP (https://bitsharestalk.org/index.php?topic=5381.msg71795#msg71795) and even uploaded it to bitshares.org
https://bitsharestalk.org/index.php?topic=5381.msg71795#msg71795
Cheers!thx!
glad to help
Mac GUI binaries coming soon...
Guys if you thing scroodge is a trustworthy delegate, then please
wallet_approve_delegate scroodge true
or send some funds here:
scroodge XTS67u5mjusU3XXna7EmqyeGedMwREEUYKg7k5g6GeFTLqyLBEify
I'm out of circulation on 103rd position right now :(
XTS7B7LTGRQhQoCNasogZ9mKJhBExyL1TG2MmFUWqsp9LkhpKvvdc
thx!
Does anyone know if keyhotee founders should have some initial funds after importing keyhotee id?
I did so, and have 0, maybe there is something one should do in order to receive it?
Quote from: dxtr on July 02, 2014, 10:48:04 AM
Does anyone know if keyhotee founders should have some initial funds after importing keyhotee id?
I did so, and have 0, maybe there is something one should do in order to receive it?
did you try
wallet_rescan_blockchain
maybe this could help!?
Quote from: free on July 02, 2014, 10:41:58 AM
XTS7B7LTGRQhQoCNasogZ9mKJhBExyL1TG2MmFUWqsp9LkhpKvvdc
thx!
could you pls also post your account name!? thx
who send me somt xts and otherasset
XTS81rHVftvQ5N2oCddEmKrtpVaEtxfKe8oiMHMAjvrTqzgfrLamu
duduhua
Quote from: yangsbo on July 02, 2014, 10:56:38 AM
who send me somt xts and otherasset
XTS81rHVftvQ5N2oCddEmKrtpVaEtxfKe8oiMHMAjvrTqzgfrLamu
duduhua
just sent (XTS / EUR)
Quote from: free on July 02, 2014, 10:41:58 AM
XTS7B7LTGRQhQoCNasogZ9mKJhBExyL1TG2MmFUWqsp9LkhpKvvdc
thx!
sent
All founder funds were allocated to us in the test runs.
Quote from: cass on July 02, 2014, 10:54:18 AM
Quote from: dxtr on July 02, 2014, 10:48:04 AM
Does anyone know if keyhotee founders should have some initial funds after importing keyhotee id?
I did so, and have 0, maybe there is something one should do in order to receive it?
did you try
wallet_rescan_blockchain
maybe this could help!?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Please send me some xts,thanks
XTS6nAft9YGBtweSKVpuE9E5hcr6EXfpzQezxy1Fv8RsAmcvALxqv
Quote from: cass on July 02, 2014, 10:54:18 AM
Quote from: dxtr on July 02, 2014, 10:48:04 AM
Does(...)
did you try
wallet_rescan_blockchain
maybe this could help!?
I tried it, but not really :(
I'm afraid keyhotee funds are not included in this blockchain, but I'm not sure about that...
Quote from: demonstra on July 02, 2014, 11:32:53 AM
Please send me some xts,thanks
XTS6nAft9YGBtweSKVpuE9E5hcr6EXfpzQezxy1Fv8RsAmcvALxqv
Sent
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
3370.6 2014-07-02T11:43:00 spartako-w demonstra 100.00000 XTS 0.10000 XTS 270ecf0f
I tried also to send FREE but It is pending from 3 minutes
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-02T11:43:02 spartako-w demonstra 100.000000 FREE 0.10000 XTS f989d035
wanna help testing.
send some funds please: XTS7ms7F25oUjGSZuMFaobyKoTuAtMLuDqUfN8szsrCtEeieHEa5x
xts sent @ duduhua / demonstra / scroodge - traffic !
Quote from: bitdraw on July 02, 2014, 11:58:18 AM
wanna help testing.
send some funds please: XTS7ms7F25oUjGSZuMFaobyKoTuAtMLuDqUfN8szsrCtEeieHEa5x
sent you 33 XTS
have fun ;)
Quote from: bitdraw on July 02, 2014, 11:58:18 AM
wanna help testing.
send some funds please: XTS7ms7F25oUjGSZuMFaobyKoTuAtMLuDqUfN8szsrCtEeieHEa5x
Sent
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
3440.10 2014-07-02T12:03:30 spartako-w bitdraw 100.00000 XTS 0.10000 XTS 99b6fb1d
3447.9 2014-07-02T12:05:30 spartako-w bitdraw 100.000000 FREE 0.10000 XTS 30626c46
It seems I lost 100 FREE.
I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:
Init balance: 1,000,0000 FREE
3411.11 2014-07-02T11:55:15 spartako-w spartako-w 1.000000 FREE 0.10000 XTS 1b8b05d1
3432.12 2014-07-02T12:01:00 spartako-w demonstra 100.000000 FREE 0.10000 XTS 68a98a80
3447.9 2014-07-02T12:05:30 spartako-w bitdraw 100.000000 FREE 0.10000 XTS 30626c46
Finale balance: 999,700.000000 FREE but should be 999,800 FREE
stuck at 2050 for 7 hours?????
"blockchain_head_block_num": 2050,
"blockchain_head_block_age": "7 hours old",
info
{
"blockchain_head_block_num": 2050,
"blockchain_head_block_age": "7 hours old",
"blockchain_head_block_timestamp": "20140702T053215",
"blockchain_average_delegate_participation": 38.373860182370819,
"blockchain_blocks_left_in_round": 71,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999560990366,
"blockchain_random_seed": "3876cc2ea5d4ec6d98d3ac02680af636f8f2ded4",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T121010",
"ntp_error": -0.0031089999999999998,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "15 weeks in the future",
"wallet_unlocked_until_timestamp": "20141012T204512",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "6 minutes in the future",
"wallet_next_block_production_timestamp": "20140702T121600",
"wallet_version": 101
}
th_a chain_database.cpp:1196 push_block
Error pushing block 2053 - 5b22d869b51851413c66f97e698aa94eb8ee1f98
{"block_id":"5b22d869b51851413c66f97e698aa94eb8ee1f98","block_number":2053,"block":{"previous":"6c58e1343339e41c04f196437f02c1b16f474410","block_num":2053,"fee_rate":1000,"delegate_pay_rate":74902,"timestamp":"20140702T053300","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"97f096259a027326cc4b8cdaea32742b21c3840e","previous_secret":"0a03a2852a42f54c1ac0362393f70ef9a9978764","delegate_signature":"1fcf0e33fa5486d7a2e645e15fb4c419c018794975ea6998c06f7821a621ff2aee29296680edb773cb1c6bbd7cdc29e90ded8c498dd4433da0337c3c2928da4986","user_transactions":[{"expiration":"20140702T073256","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSHvEBpXSpWvXBdUVhFp3dteFKNMACrWgkB","memo":{"one_time_key":"XTS5GXpefTRn8jXrK5B2dgnfrqBK3gHTpoQGKgZi1wMESfw56GQc4","encrypted_memo_data":"8d49c99682b688e9d3e76e460f3462dc1b1d18dc9d68af4a3ed8786d5d1e9c35e925f71af3f85a7393f51f969e97f0e07b719122e82c591fa25535cd2bd092fb"}}}}}],"signatures":["1f4e131e38f984af5d3b0f40deeaf80e424839dccf602ec39ef7eb229b8d9b6b683c0147eaf23c61ae92b3bb037b02281d375acd72a6ef67c49904965d5418775b"]},{"expiration":"20140702T073253","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSAgzLWoHot674Btf1guNGRj3uKBKhNQHjB","memo":{"one_time_key":"XTS5AUG2ptH2sKBHXgsTp64WFHS7LXntCQmmev2AEXydECabSnSbF","encrypted_memo_data":"f580e5d8f7a1f42c7d3b9b158a7acec721460672f753717ab7c7d055891697af20fc61af45b6ad647b3de29d4064d73c0799b5e4595b3bbc051e042c45fc8449"}}}}}],"signatures":["205c0ac54c6cc1eb04b79ceb78d4360b6c526bf92e989facb160d13c70f5285c1d2f2cb019421d9e3ef91a1c66b4f344a5cb33ae91438c090555fdf5a07a83a950"]},{"expiration":"20140702T073247","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSPkQ5Ts4DReXF5Kns5NRq2fjWVNgFUmaLZ","memo":{"one_time_key":"XTS7WEVai44Uup6oCdJNTKJgnSEUfnDRRq3qxFrW14fM763yASq3Z","encrypted_memo_data":"a02d7f07664a0ff99351cfe244cdd4664ef48eee63356e910b520cc727ce7553e02c425f7df41f21b50e0525355f769e19f3efb97376e9aebd1d77ef5160a0c5"}}}}}],"signatures":["20cc7ea59b2a9655a8ce619b09bf949bf8e9859743e10b0e933f796c835e6979920dd3dd9c255ddf72c6634e2b0b3e0691bd806fe834214eb890e98451bdc139aa"]},{"expiration":"20140702T073250","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSHeiJtE1gvw9adXM8Pti4eWZFJYq3qEjUP","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTS4yza9hjrRxKyzx6dhPSCAbDRX16PrcnCK","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSF5sZpgbdaLhi8EUJGU2EuPvBwQgcGwngV","memo":{"one_time_key":"XTS7yRk9gie9VeF1fKSGFy7hcSEqXxfaQU8fvd6ow8r5TUPUDQJt8","encrypted_memo_data":"6654d0a15ee7a5f220d355d47a67867758c6e908cf5f1dec17483b1de94e1fbdc0ea252032538793ac5d94c40e1404ad95041d354acd79d75202c89eb8be5954"}}}}}],"signatures":["207a4c4c52156fc7648a933e0061cf760d14d85759f9b852a2bcb64ad1d5d1c9ceec5be53f630964a7594036b2d8455c0ae25b3849a9e17eb1563bc1d2329039ba","201dfa4e0f31414b6f662eba0fc092ec1df7b3f44d22a4745e7b418ef434eddb0babdeb59a8af9fe46ad51fff4d7cb5dd84808654fe535591f218911ece28e5b48"]},{"expiration":"20140702T073256","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSNN7TXdqrXGp5XZg5XHdUEvB2HKJ7XoZ2F","memo":{"one_time_key":"XTS6QUaVsDpvtp1YuCnhrXrFjc8iMcg1FGnKxHdxSqngncUuuSt9D","encrypted_memo_data":"f2162857df7f9543a5d4630257803d0c704d4f9ac071b618c2e33093c11fe273a3f67e22aba8fc31c271ed40039389ef843b77a539a0869d421fd9412b07d485"}}}}}],"signatures":["20a5f2da343ddbbbe4a8c5e9575a8576306e05c263474f1801f2f05a26c8437d1e6f1a96c7666a3faabc144ff233d60587f083cd46c16c4902dfcccb313b1cea10"]},{"expiration":"20140702T073249","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS61Vuqz8zHQ3r14ay7cbzPQYFAJJcye8kL","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTS71NNzCXA8ihM9STf3VAP28u2XRZTCNsRL","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTS3ZbZ76kzRmkPSAv6bXQmCzQMyuJXhKE84","memo":{"one_time_key":"XTS67mnx4TLmafMoKVEpbGAHkMe3qWTSHoxZRhwGvZXstWcNaQazq","encrypted_memo_data":"7c609cbec9b35cb7a676f2f07048aad50fa437b3ee298f33712e9614e71a45c081f7abeb1b77556e09d22c06eaa766e2b11bcf1619406cb32aac47b8c9401226"}}}}}],"signatures":["2091fa6ca66343f3134098f8a97bb5ae0470c35c049ee7dc77ee08a32f17c4f72ea8d31761e417d0d2eabfa1a623ec44ded3d7cf2575dac05e000ee7db646a79c1","20beb2dfb7c179dbd2c6401594fd8c998e0ea58aff7574adf0517f61483d867ae29b34775038a68f1fcf9abb650a472a73f63aaf85e2dd1d68fe6a081fe6cae95d"]},{"expiration":"20140702T073258","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSLKytozCME2xm4nbFwYtSm6EGNGRvxXn9z","memo":{"one_time_key":"XTS5qkLEkqSPQLXCXxNr1CP1UnrDEiB6ZUv4G1q9wfq8jgC7zRb2n","encrypted_memo_data":"2e782c6e1480cea409cab3b57def2989acee50feaa94df0daecdb7e5411425a5916b0a56d332a7dfc4b0621ed8c5267d428ee84a2676066d021e3c6d448f05c8"}}}}}],"signatures":["1f88267025483d8243676c7a0593e27dfc0d1b5f7312eb4f30b58feb43c5beaf247f2f426587eeede94a32138222edc379022caef9c56be01dda14d981f70cdc98"]},{"expiration":"20140702T073246","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSGWzQwRMgJqe3TNRUpctCSYFVB3CewFs5w","memo":{"one_time_key":"XTS7Et8YFdwYYLT22QPnndQMV5GrqrZteRRoxLyFvQnfjtgJtfMZB","encrypted_memo_data":"97af6e8fcd6f28f4f0635c1ca201260007c19a78bc7193fb75c918b8f30b5367f9da7a81657382578936e8c350da999dce9f7d272e70c9d22ed0da9dbdb37616"}}}}}],"signatures":["1f0fc0db5486fc2d2252f4f4db333cd988e75fcc417810daacc33a9060bb892d5d00a16e7432ca58816b4564b04dd4da1ebe850c4b33cab890f4a39f878f98009f"]},{"expiration":"20140702T073257","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTS54DPjWLWNhtr26jP25aCfuREFpjYWwGYP","memo":{"one_time_key":"XTS7HVjuy9RomTVhmUBFiZzfcTKS7Tm3TH7Ef7uwo8yruPmZB1oCS","encrypted_memo_data":"46b4de4b2913c55dcb6cb94d3d0ec0bd8943ebbef903a5a152d3fc64982ad97c45eb000a28daf980c4e19240e708bf22a3fb348fe3e97b55ca47caf3d6ca7ce5"}}}}}],"signatures":["201c9f8fa751be1d8c5bd48233db8f11fc7e2c2937aaedc220b9998c15b81a284e45d91b51e3811e5c58c1449aa75d6e8b8f98380e38074d8091e173d619a1395f"]},{"expiration":"20140702T073253","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSPWAzYXfSsMGL5WeJcdcZGyfncKDamjrhj","memo":{"one_time_key":"XTS88oVEgGxh6Uascchnkrm5YPZPdkAwqTcBuvQGqquig3q6uqLzT","encrypted_memo_data":"2857f9691341d32e5992092e77116850b4fd5e520dac9568faf72a80070381e2de4355416a8fb9af4fbb6282b17917c3f493145dcb8bfbf616bb4e2fd923f5bb"}}}}}],"signatures":["20cd6a20cadf95dbd3026d677f8c71bbf97b9b307fcbcb0c25829656472517d83cea635de73603333e29630e11a6b3d2cda9423692e270d695d2a7d7e945355673"]},{"expiration":"20140702T073251","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSAtCKCXuqwZreHFSSg36zSCdqa6SBps2Kc","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSGrjFu44CW8dZzjQHVJchALWEYR9VVT1re","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSLDbcoUQQfeLx7vAXroQwr2uYWVJqh3mjS","memo":{"one_time_key":"XTS7syAWJBzLPAxZWhfHEeQAx8opSAAWFixZehJtoooy1AZo6fYtJ","encrypted_memo_data":"a96dae1d5b5645e9319e0f695d736949975657ad4fbbff6cd265ba71a74502b9ed08748525ad3ce476cb9ae41f230474056e711b54bba64c37bf6110cefad7cd"}}}}}],"signatures":["1fd8841dca3bae7d2d20d363c5ddaff20344889572a262156259e219300bb5d05eb66bb2e2dc97eafc0169750c0555e4b853f61f114433fb486f8967332daebb55","203ee300c9dadf9e696a4615d2674d0bf3f15b7d09a756cb012143df2394792ddcf9d866ad4a8070836e0c0494c2380c6f337377757e886032d954e894a0e3dc44"]},{"expiration":"20140702T073245","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTS2r97jENFbDwRKmyUagHagDUJWooY3Leqb","memo":{"one_time_key":"XTS6kKjuEBw5KRdDotvet7bviuG9DoZppNgfvNaqRgvKHPaWBadTC","encrypted_memo_data":"d0044f1957dd90fee42fbdfb3342ad1ab858831e8e8084d1465a7f6ce2d1b0a6253aab4f196c15e8a440c5acf20afb296dee694fec75b20219cca3eab20de85a"}}}}}],"signatures":["1f4658e21fa908ac9c2df9c15732bdca404ab70503ffc850bef8794f2ae21ed635211344073e0a48c2e2a291594646a05c6ea39a435789a793dec3403c79f62ae0"]},{"expiration":"20140702T073252","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSK8GXKripnD6CMB1b5nPhEfEvJ1siER5go","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTS46CNqS6asouRuHWrivppgyUUfmuYLYxd4","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTS86Xg4Puuwz7jZbgCtdDrwtcUsqzhBmWQy","memo":{"one_time_key":"XTS5Ts5Qd8RH7Tf2uJ1nS4TNM8yDYg22hEraU1oPsQcgmkUA4LkFu","encrypted_memo_data":"dbb71a319944e9e4c72fbbdbc5195a80d4e3541a8ec1ce91806aec7eb69d4634813f1600c9ed5f845d4f5285fabc67ba18b3c704366cc30afeff7340913e718a"}}}}}],"signatures":["1fdc8635606948f7db9e54f442c48ba6e691924772da65455764b54ddf3b0e7c4f9a9793eb2ef607cbb03c14e61bd7814bc833f5b35ba5eab72d4406e82513f43d","1fa4fbdd5fa5ea0ffb57dc86a866efabc724413c165b3279763f92f68c796862e1560df9e5cd9205ef62028ca591d3ea173a981fe30afded809a3d8bcef32f1604"]},{"expiration":"20140702T073254","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSDq9t9M31iAPMEsjiTGnGMEMZBkxdekK1L","memo":{"one_time_key":"XTS4wrgvxWsmW11feXetRXucHyCaPe86ngWpwWc6EjHQta3kBfpLZ","encrypted_memo_data":"559e1f55d4fe451b7d4bb8cf40cc88d0efa7a69dae55a40645f35123a89a5800672915616c48e4d7ca8c2597ec1f107dcef0b542babab007da1be1e9bf67bdc4"}}}}}],"signatures":["1f15564e8fd93a18a832627fbbfbfb878ccf5b52436f02c98c3d81854a197b6643e45729cc682745d06cf4de80f7689b530256f7a4f9ffed11424ad6061c300726"]},{"expiration":"20140702T073249","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS825j8wbdrpzmsRtV5iVALh1jDKk6SExw3","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSKqjfG4MUBQiEbaxaAMdgpghWXSAnVqkxi","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSHgpY9EHkNLof8xaiTsP33HFYUfP81ZNFs","memo":{"one_time_key":"XTS5S6JUsAcqd9AwKfWh5gmKsn61TQq2JQUSTsbjvXwti6fhm6Nft","encrypted_memo_data":"ce3fb2466f833a0f437e9692218f85e403b6491c62087c2ff9cfcad1e94f258a798c704371190df0b35bb42bbfbb75d1d6eca7cdff815e69528008929af65a1d"}}}}}],"signatures":["1fbd1487e434fdaece013fc2dfb40575f40c5b6ea78a3a0c0276281d0a2c4560755258b7a431bd4a191c2fd5ab27f8d4f181a546704a9736748320dc0e2a84c87c","1fe133f23d0aefd9259bccb7b203aaf33a6c043ada2012ebf93674d3f554c973c5ae5d3044387d6f56d1b470cc5b0475640115539a12daf2d40c27f52dc7a22de6"]},{"expiration":"20140702T073251","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS4cXdYbb41sArKGV65AQt3x32WwFNxwUAp","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSDCCqai8wFjUCkyYSjTduSTrt8igHBg9qb","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTS5NayDUiSBfFZZH9oAsmu8Twg9jaoWYsqz","memo":{"one_time_key":"XTS6nibyJYCo4AukiXCeSZHHTBoW4jvjg1hmQwMkxuzRMD8pbfJv2","encrypted_memo_data":"30c66d2d327f5fba111e5bd7a82099365902d3e57df9fd90d44232f13d7ad66d971154dfaa678fd17ae413e730f84f26527c1208a7ba803ea749ef9783ebc7e2"}}}}}],"signatures":["1f9df0fcc9401a3a936382c2e8bc73ef0f82de0ac0370bfff94d8ed17d634ddea9198df18e4007b3186016c36e44495e6b7471665a5e20f02df75b2d920bfcf1d1","20010506283193f8668fd5715bf9272aca3af14757b9235e8288355b078ff0cc4aa68a9fa91cc476516e3ce629795fe8d813d38947ac185a4f3b794707874738b9"]},{"expiration":"20140702T073252","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTS8WZzV9REKcvuMgTBL5F7Y3bwhWC2SpBTy","memo":{"one_time_key":"XTS83QxWeA3dXJybQTb6S4Kf6wcN85mDcVp4PCwWvCnjc1DsuaCuy","encrypted_memo_data":"411c07105963f59326df29610e49dd3722cd1aae4a905307c7db0453a3039b27f794d89cfe97500c44a6b0e579b6c68a30e47ff03e7638209d2c320ad6b03e3a"}}}}}],"signatures":["208a4b7f5a0008209af60a3cd4f83f1c939599a971c668b85e1aea011fea17b718bcf114a72d588176a7cd51fa55ada0317e57c40a8a7190af1f6f0c00d03fd636"]},{"expiration":"20140702T073255","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSE2FbCpZhjeEL2bhfgPE43ew6ecSiTJigH","memo":{"one_time_key":"XTS5RLcHNf6XZWNnh49Mriypwh2PawZSuzDzpbJ75jzMpLkzyWJ5B","encrypted_memo_data":"cbbeb7c487e884f4fd96369b09d036e4c64408171a44964235f560d7c8b91eac7ee729aff43e947bb3e310005ed65ceb35f47b1a34b142198153f91ff11af7d8"}}}}}],"signatures":["1f02597619ff5950e36e042ba8c551be2237a6b0e8720920177f2664a56f54fd5971777997d5df50f3f5ead176e99a0a8cc6430bbba44dacc7a7744bb3336df2fc"]},{"expiration":"20140702T073246","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSAzEVJosCS15jYBmNh722pPvDwVSMx1Xmh","memo":{"one_time_key":"XTS7uXFUWqxeKXX1KjXxKaW75mkegCdPyi3VRpa3rVZUxuF5osGYk","encrypted_memo_data":"73336ecb6d366bee90f67c9daf729b4ee13a53d15cf0205d1cbe928800ddfc9893711e62cc340c04974814c4fb928c830ebf8c625e3eb5d37f7f532bdea0f68d"}}}}}],"signatures":["20b3fe42fdc85716c4b7bc7d32d52c77370af05e811ad9cb6e270352530ff96c8187ed09b6b668879862dc9f6b04d35d33e3b4850c95213a898b14e9cc43d8560a"]},{"expiration":"20140702T073257","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSF3q6Rwsy4tKtHrQJPjgbYAW3Etajqusxb","memo":{"one_time_key":"XTS5EE78tu3U8p5XwLnj1h9H9K6ahPUr9VAoPZJVBf3UwZmoauNhn","encrypted_memo_data":"51a8150546dd593b358a01fde349f60e3c8a05c1881f88d788da587391cf46fb9c6072319999b43cfe94f27f0be4c8a2a256a14f13d3ec197fd17d24f4eada27"}}}}}],"signatures":["1fc64a5f41663b264809b5b7d20ae70a01be04265a9382e0d275d1f2f47ce5651345b1bfdee9a7093c9807b0bbafd9576739c8f404e7c5ee7ad598cecbfe5e76dc"]},{"expiration":"20140702T073245","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSFJ9ad6exEUYhhn2g3iP6AxRcbJZ6wQBFY","memo":{"one_time_key":"XTS5oWatYZViKEfLw5nkmxifNmZQeJ7h1x2rchZL6hiUV7hTvkz5F","encrypted_memo_data":"5b1b5d71dff5510d759d81b3732e9c56f35d251699928ace9f0351bc20e69da79a7a67c953dcf1309a5123194437e4b2653e6ad5f3c6fff8a9d1c344e78c4aa9"}}}}}],"signatures":["208513543302e2de2e9a7e28b6131b236755f13dda5fa83f2733b982a52a1b799dafd411a94ccef787369194c7abb7de8e9e39457061c69ebd8ed61132da2be1ad"]},{"expiration":"20140702T073258","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSQJ9aYLoFw9abrqxCq4tgYmohdtPGm3UHR","memo":{"one_time_key":"XTS6nyA4vDFUh2QWztC3vHq7U9Yi3x8ZgMW2n321tfHd8XFT15Fxc","encrypted_memo_data":"bebb600d920d45671ff81d4409a51e938855e0b58931ce676e3604214e12121d74611accea31cd636dcd9f7ed8ed62de78a97a8a722473479988f10b39674903"}}}}}],"signatures":["1fe462c7fac3dd351e36a8aa8e3317f7688803b8dc67e7897ba3fb05b0f65bb65299a427673827ec84ebb1f179a632f1b663a583b4666f61a4cbee270595471821"]},{"expiration":"20140702T073254","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSKM7N5gd819BK7RJQykvd2whLichMAgB1R","memo":{"one_time_key":"XTS63zqDcjFw9zMfiQJKq2P2LsyoVZCzhaUycJGGTmPghsex9sfAS","encrypted_memo_data":"0cae5f9bff56427f1ed05cb6cfb62fd00b07e8409d8ec84f617f73e6e6d2f6cefdb93cd784a7e21e9d5c8ce4edf356a6f82bf3cfb266cd8934078aca510cdbc0"}}}}}],"signatures":["1f4d1268f48a749a9072366a5a89aeb4a7e4ee88fe7bce49d2668e60a4a7eea1f62b3d29cd13b4d31e13a6d33090bfea3252b627c7c2af32350870c09cca0bf309"]},{"expiration":"20140702T073255","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSJM7VTZuDPadQbku4WMLCFekrFqR2FWnhE","memo":{"one_time_key":"XTS6QYHf8R1Xv6gmXgTWdp6HPSAFCVKm1iECk41oYfvMBLHWfvgV7","encrypted_memo_data":"0aebd5803c1dd7d79670fc4bc44795d70392edc15bb03b4294cc4566a99f5c3c87c98ebf2a7f09217d5b8bd35c24f23dca58b8c8de751dac89fe7af775414325"}}}}}],"signatures":["201c92b6cafe641d1cc751ac9bada0feee7527a7379157159866ad2a44e2d6f65378fb32b5dfada3384d19ce5be8600d8975a0b9ee432d96247744a57c32e53370"]},{"expiration":"20140702T073247","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSDLS63ULWdXL2r34CjCP4MbSAaJSVY5jDy","memo":{"one_time_key":"XTS7quUAZtDpqaZ16vAjq9G1TxdKbLAAjmkvn5gznrLwy18wXc6hH","encrypted_memo_data":"1bc4e05f58a6febe4755b80492e1d6cb9922bfc46621f6c41608b4f0b39f9c13ca218f73fa37046485446a6a698098b5a85346bd267b7c953af83a23bb6ccc3e"}}}}}],"signatures":["1f633872e959a8aac02619824b2ada57b7bbf57b580e7e3f950a9f15719d5b0bb1481b5065050f2de72d82de535feea102eac8c802ca6d4be9531ef0a91430a8b3"]},{"expiration":"20140702T073250","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS6sFqcEez4vDiEFk4dtiLWGwdi2Yj3HHHk","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSFjbeuCQiGmtiAvNa3vLd1ViW9baHh3gj6","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSM4TVhVipU85uFVfpcEjXkLdJ148Hp4XXq","memo":{"one_time_key":"XTS6KezCpNfPMeY8ucjTSFhq3gEB6UXixBU4tbZ2QBgVy3ku1qosc","encrypted_memo_data":"a8c1921b0580066211bc1742a2a7d2badb401eeb8a97165c0a06c4d71f88614e2afa76670758cb5fef40372e18d19f76706fccafe22d48b2b515f84e36724349"}}}}}],"signatures":["2092261e0797ba673939376dffded3c86d582a4616ef1e069063ddf9c10eefab0d847939e86b4a5ace811c752cabc21c2f78406880fd93e661015d9bce3f8ac352","20cc4046b94e379f84a5bfad214cdb52c8cae27e0d35428a98c49c2531faa25678948cb5b2ea6665bafa399c91da34626eee30bdcad23f07cabd75aa05eeeba379"]},{"expiration":"20140702T065948","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS2G5exY1QXqopW9MDFtMXevTYbzrQusfp2","amount":20000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSEn2bs1VKZmYjxHEuBAYpc5t5FVs9wCSah","memo":{"one_time_key":"XTS64t6CmTAc7JMbugUioDG4fCeeKa2VY8RKuc1kgWK9QxE2wfVJY","encrypted_memo_data":"89ab3033f425dd91c05da59bfc7e8ce962fa4573493d7c507b24aea1c00a5ae15ab85849be7ae0ec195a85cb6911f39e90fc344942b6d57dbef89acc77c2f552"}}}}}],"signatures":["20f1e755ce73f311a24cdf5904cd362b11fcf9dfa05a5a510558972d3b987b3e51fecb3ac2d1f042f9f3d28615b308cfd58283d02c427d81c499aab5e1902bca6d"]},{"expiration":"20140702T071006","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS3D8qLFyCqY5ZeMs2BkyVvrnNXER9XRApD","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSChsX39dUcGhNebv2Xjp2hqWZdPw5VNkA","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSFwj1cwwPSerK5XF3dPntbAjwc9sciV9LK","memo":{"one_time_key":"XTS8CmsSjnm2ZKzMvydjXdV7m9wufoZmHZsMhAZiq4D38SQqBTSEw","encrypted_memo_data":"25389f5dc199e16ce5c3096ec57800df32ae768a655cd73526e34dfc105ee7c7a4e74c9af85930fa951c52bc43536a431b4f9de5dd09366070c1a32c6f68a156"}}}}}],"signatures":
Quote from: sfinder on July 02, 2014, 12:11:52 PM
stuck at 2050 for 7 hours?????
"blockchain_head_block_num": 2050,
"blockchain_head_block_age": "7 hours old",
info
{
"blockchain_head_block_num": 2050,
"blockchain_head_block_age": "7 hours old",
"blockchain_head_block_timestamp": "20140702T053215",
"blockchain_average_delegate_participation": 38.373860182370819,
"blockchain_blocks_left_in_round": 71,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999560990366,
"blockchain_random_seed": "3876cc2ea5d4ec6d98d3ac02680af636f8f2ded4",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T121010",
"ntp_error": -0.0031089999999999998,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "15 weeks in the future",
"wallet_unlocked_until_timestamp": "20141012T204512",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "6 minutes in the future",
"wallet_next_block_production_timestamp": "20140702T121600",
"wallet_version": 101
}
You have 0 connections:
"network_num_connections": 0
Try to remove the peers directory:
rm -rf ~/.BitSharesXTS/peers.leveldb/
please send me some funds to test the delegate: XTS5BqxLL4um17tU8FjsdLwPSR42i6cGNcyEZWPcG65agg9JLXzhd， thanks.
ID NAME APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
366 clout-delegate2 0.0075000283 % 0 18 0.00 % 50 % 0.00000 XTS NONE
397 webber 0.0025000094 % 0 7 0.00 % 100 % 0.00000 XTS NONE
Whats going on guys?
Quote from: bytemaster on July 02, 2014, 12:24:20 PM
ID NAME APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
366 clout-delegate2 0.0075000283 % 0 18 0.00 % 50 % 0.00000 XTS NONE
397 webber 0.0025000094 % 0 7 0.00 % 100 % 0.00000 XTS NONE
297 emski-delegate3 0.0130323604 % 35 0 100.00 % 44 % 10.46205 XTS 3466
Whats going on guys?
meaning of the question?
EDIT: Everything looks fine on my end. No missed blocks on any delegate. All transactions passed in timely manner. Sky is blue and sun is shining.
Interested in testing, please send some funds to XTS7e4oBdiHZWpU2qLCm12LuNcnNpeSR7g2tWFFqnbv1faAYxU5f9 . Account name is wlz. Thanks in advance :)
Quote from: vlight on July 02, 2014, 12:24:00 PM
Peer 24.127.xxx.xxx:xxxx disconnected us: You offered us a block that we reject as invalid
My delegate currently is not even in top 101. What does this warning mean? :o
I have been seeing that as well... I think it may be due to receiving the same block from 2 peers, you lost the race in sending the block to that peer. I think we need to more specific about why the block was invalid.
Quote from: mmlmmlmml on July 02, 2014, 12:21:02 PM
please send me some funds to test the delegate: XTS5BqxLL4um17tU8FjsdLwPSR42i6cGNcyEZWPcG65agg9JLXzhd， thanks.
Sent
3518.0 2014-07-02T12:26:00 spartako-w mmlmmlmml 100.00000 XTS 0.10000 XTS 3c392db7
3519.0 2014-07-02T12:26:15 spartako-w mmlmmlmml 100.000000 FREE 0.10000 XTS 8836dd1c
Quote from: emski on July 02, 2014, 12:25:38 PM
Quote from: bytemaster on July 02, 2014, 12:24:20 PM
ID NAME APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
366 clout-delegate2 0.0075000283 % 0 18 0.00 % 50 % 0.00000 XTS NONE
397 webber 0.0025000094 % 0 7 0.00 % 100 % 0.00000 XTS NONE
297 emski-delegate3 0.0130323604 % 35 0 100.00 % 44 % 10.46205 XTS 3466
Whats going on guys?
meaning of the question?
Sorry, copy/paste must have screwed up. I meant to only highlight delegates with low reliability.
Quote from: wilz on July 02, 2014, 12:26:25 PM
Interested in testing, please send some funds to XTS7e4oBdiHZWpU2qLCm12LuNcnNpeSR7g2tWFFqnbv1faAYxU5f9 . Account name is wlz. Thanks in advance :)
Sent
3527.0 2014-07-02T12:28:45 spartako-w wlz 100.00000 XTS 0.10000 XTS 9984efd4
3529.0 2014-07-02T12:29:15 spartako-w wlz 100.000000 FREE 0.10000 XTS 44816031
thanks a lot, the Tx so fast, great.
Quote from: spartako on July 02, 2014, 12:27:19 PM
Quote from: mmlmmlmml on July 02, 2014, 12:21:02 PM
please send me some funds to test the delegate: XTS5BqxLL4um17tU8FjsdLwPSR42i6cGNcyEZWPcG65agg9JLXzhd， thanks.
Sent
3518.0 2014-07-02T12:26:00 spartako-w mmlmmlmml 100.00000 XTS 0.10000 XTS 3c392db7
3519.0 2014-07-02T12:26:15 spartako-w mmlmmlmml 100.000000 FREE 0.10000 XTS 8836dd1c
windows wallet issues: (win 7)
- when i try to log in with my password i just see the rotating symbol but it doesnt log me in and goes on forever
(temporary issue)
- when i click on accounts in the top left of the gui next to file, and select "my accounts" the ui just turns white and nothing happens
(temporary issue)
- when closing bitshares xt with the file>quit option it says bitshares xt is not working anymore and asks if u wanna close the task
- before logging in when the blockchain syncy and you hover over the sync icon in the bottom right, the information only shows up for a split second. you can not get it to stay and see at what blocks you are
Quote from: bytemaster on July 02, 2014, 12:24:20 PM
ID NAME APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
366 clout-delegate2 0.0075000283 % 0 18 0.00 % 50 % 0.00000 XTS NONE
397 webber 0.0025000094 % 0 7 0.00 % 100 % 0.00000 XTS NONE
Whats going on guys?
I sent funds to myself and they did not go through. I tried to rescan blockchain and my terminal stalled. I attempted to reboot the client and it gave me an error saying the database was in use. so I deleted my directory and rebooted the client and it would not connect to any peers. I could not send funds to take my delegates offline because non of the funds were going through. I just got the client working now.
Quote from: bitdraw on July 02, 2014, 12:49:20 PM
windows wallet issues: (win 7)
- when i try to log in with my password i just see the rotating symbol but it doesnt log me in and goes on forever
(temporary issue)
- when i click on accounts in the top left of the gui next to file, and select "my accounts" the ui just turns white and nothing happens
(temporary issue)
- when closing bitshares xt with the file>quit option it says bitshares xt is not working anymore and asks if u wanna close the task
- before logging in when the blockchain syncy and you hover over the sync icon in the bottom right, the information only shows up for a split second. you can not get it to stay and see at what blocks you are
Thanks for the report.
client keep on been disconnected form peers. look like my client not able to re-sync with p2p network always showing "1722 blocks left to fetch"
I may need to delete all the data folder
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "15 seconds old",
"blockchain_head_block_timestamp": "20140702T132130",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132145",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>>
[detached from 1587.bts]
coins@coins:~$ ^C
coins@coins:~$ screen -r bts
I am disconnecting peer 107.170.30.182:8701 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1716 blocks left to fetch
--- there are now 2 active connections to the p2p network
I am disconnecting peer 107.170.90.142:8701 for reason: You offered us a block that we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
I am disconnecting peer 84.238.140.192:36350 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39931 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.112:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.187.91.24:35790 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1718 blocks left to fetch
I am disconnecting peer 176.9.234.167:39967 for reason: You offered us a block that we reject as invalid
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, 1719 blocks left to fetch
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8703 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.170.214:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 162.243.160.72:46456 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 92.243.18.20:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 188.138.107.159:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.19:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
I am disconnecting peer 146.185.186.245:54482 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.185.24.234:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1720 blocks left to fetch
I am disconnecting peer 176.9.234.167:39978 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "18 seconds old",
"blockchain_head_block_timestamp": "20140702T132445",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132503",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1722 blocks left to fetch
I am disconnecting peer 176.9.234.167:39984 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1723 blocks left to fetch
I am disconnecting peer 176.9.234.167:39997 for reason: You offered us a block that we reject as invalid
Quote from: clout on July 02, 2014, 01:09:51 PM
Quote from: bytemaster on July 02, 2014, 12:24:20 PM
ID NAME APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
366 clout-delegate2 0.0075000283 % 0 18 0.00 % 50 % 0.00000 XTS NONE
397 webber 0.0025000094 % 0 7 0.00 % 100 % 0.00000 XTS NONE
Whats going on guys?
I sent funds to myself and they did not go through. I tried to rescan blockchain and my terminal stalled. I attempted to reboot the client and it gave me an error saying the database was in use. so I deleted my directory and rebooted the client and it would not connect to any peers. I could not send funds to take my delegates offline because non of the funds were going through. I just got the client working now.
Rescanning the blockchain under the heavy load we had takes a long time due to TITAN crypto-graphic operations and currently being limited to a single thread. This is probably why the terminal was stalled.
Quote from: sfinder on July 02, 2014, 01:24:25 PM
client keep on been disconnected form peers.
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
This peer is showing up on both of our seed nodes....
Peer 209.141.182.156:8701 disconnected us: You offered us a block that we reject as invalidWe are looking into the cause of this message...
more info below
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "15 seconds old",
"blockchain_head_block_timestamp": "20140702T132130",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132145",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>>
[detached from 1587.bts]
coins@coins:~$ ^C
coins@coins:~$ screen -r bts
I am disconnecting peer 107.170.30.182:8701 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1716 blocks left to fetch
--- there are now 2 active connections to the p2p network
I am disconnecting peer 107.170.90.142:8701 for reason: You offered us a block that we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
I am disconnecting peer 84.238.140.192:36350 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39931 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.112:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.187.91.24:35790 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1718 blocks left to fetch
I am disconnecting peer 176.9.234.167:39967 for reason: You offered us a block that we reject as invalid
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, 1719 blocks left to fetch
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8703 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.170.214:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 162.243.160.72:46456 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 92.243.18.20:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 188.138.107.159:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.19:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
I am disconnecting peer 146.185.186.245:54482 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.185.24.234:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1720 blocks left to fetch
I am disconnecting peer 176.9.234.167:39978 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "18 seconds old",
"blockchain_head_block_timestamp": "20140702T132445",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132503",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1722 blocks left to fetch
I am disconnecting peer 176.9.234.167:39984 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1723 blocks left to fetch
I am disconnecting peer 176.9.234.167:39997 for reason: You offered us a block that we reject as invalidQuote from: bytemaster on July 02, 2014, 01:27:46 PM
Quote from: sfinder on July 02, 2014, 01:24:25 PM
client keep on been disconnected form peers.
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
This peer is showing up on both of our seed nodes....
Peer 209.141.182.156:8701 disconnected us: You offered us a block that we reject as invalid
We are looking into the cause of this message... so don't take it personally if a peer rejects you right now.
Quote from: bytemaster on July 02, 2014, 01:26:19 PM
Quote from: clout on July 02, 2014, 01:09:51 PM
Quote from: bytemaster on July 02, 2014, 12:24:20 PM
ID NAME APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
366 clout-delegate2 0.0075000283 % 0 18 0.00 % 50 % 0.00000 XTS NONE
397 webber 0.0025000094 % 0 7 0.00 % 100 % 0.00000 XTS NONE
Whats going on guys?
I sent funds to myself and they did not go through. I tried to rescan blockchain and my terminal stalled. I attempted to reboot the client and it gave me an error saying the database was in use. so I deleted my directory and rebooted the client and it would not connect to any peers. I could not send funds to take my delegates offline because non of the funds were going through. I just got the client working now.
Rescanning the blockchain under the heavy load we had takes a long time due to TITAN crypto-graphic operations and currently being limited to a single thread. This is probably why the terminal was stalled.
I'm up and running now.
build on osx, when I quit the client, it shows the error.
Program received signal SIGSEGV, Segmentation fault.
bts::blockchain::chain_database::get_head_block_id (this=0x101703048)
at /Users/bts101/bitshares_toolkit/libraries/blockchain/chain_database.cpp:1704
1704 return my->_head_block_id;
Quote from: bts101 on July 02, 2014, 01:40:19 PM
build on osx, when I quit the client, it shows the error.
Program received signal SIGSEGV, Segmentation fault.
bts::blockchain::chain_database::get_head_block_id (this=0x101703048)
at /Users/bts101/bitshares_toolkit/libraries/blockchain/chain_database.cpp:1704
1704 return my->_head_block_id;
All issues on exit are known (err... we know we have bugs to solve at exit)
Quote from: sfinder on July 02, 2014, 01:34:14 PM
more info below
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "15 seconds old",
"blockchain_head_block_timestamp": "20140702T132130",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132145",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>>
[detached from 1587.bts]
coins@coins:~$ ^C
coins@coins:~$ screen -r bts
I am disconnecting peer 107.170.30.182:8701 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1716 blocks left to fetch
--- there are now 2 active connections to the p2p network
I am disconnecting peer 107.170.90.142:8701 for reason: You offered us a block that we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
I am disconnecting peer 84.238.140.192:36350 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39931 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.112:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.187.91.24:35790 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1718 blocks left to fetch
I am disconnecting peer 176.9.234.167:39967 for reason: You offered us a block that we reject as invalid
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, 1719 blocks left to fetch
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8703 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.170.214:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 162.243.160.72:46456 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 92.243.18.20:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 188.138.107.159:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.19:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
I am disconnecting peer 146.185.186.245:54482 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.185.24.234:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1720 blocks left to fetch
I am disconnecting peer 176.9.234.167:39978 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "18 seconds old",
"blockchain_head_block_timestamp": "20140702T132445",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132503",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1722 blocks left to fetch
I am disconnecting peer 176.9.234.167:39984 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1723 blocks left to fetch
I am disconnecting peer 176.9.234.167:39997 for reason: You offered us a block that we reject as invalid
Quote from: bytemaster on July 02, 2014, 01:27:46 PM
Quote from: sfinder on July 02, 2014, 01:24:25 PM
client keep on been disconnected form peers.
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
This peer is showing up on both of our seed nodes....
Peer 209.141.182.156:8701 disconnected us: You offered us a block that we reject as invalid
We are looking into the cause of this message... so don't take it personally if a peer rejects you right now.
Very interesting you are rejecting the very first block as invalid...
Quote from: bytemaster on July 02, 2014, 01:55:08 PM
Quote from: sfinder on July 02, 2014, 01:34:14 PM
more info below
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "15 seconds old",
"blockchain_head_block_timestamp": "20140702T132130",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132145",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>>
[detached from 1587.bts]
coins@coins:~$ ^C
coins@coins:~$ screen -r bts
I am disconnecting peer 107.170.30.182:8701 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1716 blocks left to fetch
--- there are now 2 active connections to the p2p network
I am disconnecting peer 107.170.90.142:8701 for reason: You offered us a block that we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
I am disconnecting peer 84.238.140.192:36350 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39931 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.112:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.187.91.24:35790 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1718 blocks left to fetch
I am disconnecting peer 176.9.234.167:39967 for reason: You offered us a block that we reject as invalid
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, 1719 blocks left to fetch
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8703 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.170.214:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 162.243.160.72:46456 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 92.243.18.20:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 188.138.107.159:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.19:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
I am disconnecting peer 146.185.186.245:54482 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.185.24.234:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1720 blocks left to fetch
I am disconnecting peer 176.9.234.167:39978 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "18 seconds old",
"blockchain_head_block_timestamp": "20140702T132445",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132503",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1722 blocks left to fetch
I am disconnecting peer 176.9.234.167:39984 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1723 blocks left to fetch
I am disconnecting peer 176.9.234.167:39997 for reason: You offered us a block that we reject as invalid
Quote from: bytemaster on July 02, 2014, 01:27:46 PM
Quote from: sfinder on July 02, 2014, 01:24:25 PM
client keep on been disconnected form peers.
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
This peer is showing up on both of our seed nodes....
Peer 209.141.182.156:8701 disconnected us: You offered us a block that we reject as invalid
We are looking into the cause of this message... so don't take it personally if a peer rejects you right now.
Very interesting you are rejecting the very first block as invalid...
If you start with a fresh data directory do you always get this problem?
Quote from: bytemaster on July 02, 2014, 01:55:08 PM
Very interesting you are rejecting the very first block as invalid...
Could it be a
difficulty/bug to sign the very first block after the delegate gets active for the first time(after enabling delegate block production) ?
I have lost multiple times only the first block on Dry Runs.... check out the last one... (DryRun7)
I thought it was a coincidence until now....
PS and my machine had no network issues from the beginning and I have nothing changed (settings etc.)....
liondani (unlocked) >>> blockchain_get_delegate_block_stats liondani
[[
778,{
"missed": true,
"id": "0000000000000000000000000000000000000000"
}
],[
895,{
"missed": false,
"id": "559668424b0f22892a7db99353c2a1680b6ce075"
}
],[
912,{
"missed": false,
"id": "dc5904414782e0a82c04dd0e4f9dfdc037d1437e"
}
],[
1079,{
"missed": false,
"id": "aef2b58a6324bbf4e031d53221f2afeb4a5d8cf2"
}
],[
1200,{
"missed": false,
"id": "e3a788d25fe3f7f66f7806b24c308240326c051d"
}
],[
1262,{
"missed": false,
"id": "59bb636e3c353c530767547aa9f7423911452f53"
}
],[
1398,{
"missed": false,
"id": "4c0dd0788ebb02066d24192bb3c28faced788a86"
}
],[
1505,{
"missed": false,
"id": "79686306ff4f5f6abfe92972d27a7e6c17b2d696"
}
],[
1524,{
"missed": false,
"id": "819b68e6eb89afde79f6a532f5fde68517b4177a"
}
],[
1626,{
"missed": false,
"id": "9ab5c5a9fa2bedb9a63c7362b1ca9a71311ceb5e"
}
],[
1767,{
"missed": false,
"id": "846c2eb9498eee12db101776fb1ff14bd02aae1b"
}
],[
1855,{
"missed": false,
"id": "77e0911483519a8957b0d9ccf364f6c5b58e319a"
}
],[
1998,{
"missed": false,
"id": "05400cad9f0d7c0ba35f4757d3bde830be32dc47"
}
],[
2063,{
"missed": false,
"id": "ec6b1cc99067a8469cf9258b4937c3039edf7041"
}
],[
2206,{
"missed": false,
"id": "f58d04112fafe2e5c9f75cc2bc4a0fdfdbb1df63"
}
],[
2275,{
"missed": false,
"id": "cc8189b63390694196b70a94dda85076a09c5f08"
}
],[
2414,{
"missed": false,
"id": "efbbf75bb7959fd349c572b7af478ac070c9c7e9"
}
],[
2467,{
"missed": false,
"id": "a26841124820b7bfb86efd6e437b5f5791250794"
}
],[
2530,{
"missed": false,
"id": "8adbd228199325504837c330bbad03011253138c"
}
],[
2622,{
"missed": false,
"id": "f8f3174318a68f5ada03c0197a4842a5a6b81e1f"
}
],[
2681,{
"missed": false,
"id": "0f548f57779b9332dd2ba46bbfa2543ff9544a91"
}
],[
2817,{
"missed": false,
"id": "b67ed6543c2b6ce2177e854b240d1de99ff04cd3"
}
],[
2853,{
"missed": false,
"id": "2725166c2d524fda986f9a7aca9c6c08aa9f70cb"
}
],[
2959,{
"missed": false,
"id": "0813ab8d1a46c52c190adea4488d0a5f2c9a4499"
}
],[
3749,{
"missed": false,
"id": "207fedba49f4a5ff614adc7b9aee358e99823bc8"
}
]
]
I experienced the same problem many times from different dry run . It always happened after many hours running and suddenly client stop synchronize with main chain and block number count stop . if I quit the client and re-run it following error will appear and client crashed
(wallet closed) >>> open doggy
Program received signal SIGSEGV, Segmentation fault.
_int_malloc (av=0x7ffff697e760 <main_arena>, bytes=128) at malloc.c:3302
3302 malloc.c: No such file or directory.
(gdb) then I will reboot my linux box and delete the "peers.leveldb" folder and restart my client then client will restart but keeping on disconnecting form peer as I posted in my last post.
the only way for me to get back to normal is to delete all the /.BitSharesXTS folder and re-sync the block chain form beginning
Quote from: bytemaster on July 02, 2014, 01:57:21 PM
Quote from: bytemaster on July 02, 2014, 01:55:08 PM
Quote from: sfinder on July 02, 2014, 01:34:14 PM
more info below
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "15 seconds old",
"blockchain_head_block_timestamp": "20140702T132130",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132145",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>>
[detached from 1587.bts]
coins@coins:~$ ^C
coins@coins:~$ screen -r bts
I am disconnecting peer 107.170.30.182:8701 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1716 blocks left to fetch
--- there are now 2 active connections to the p2p network
I am disconnecting peer 107.170.90.142:8701 for reason: You offered us a block that we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
I am disconnecting peer 84.238.140.192:36350 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39931 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.112:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.187.91.24:35790 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1718 blocks left to fetch
I am disconnecting peer 176.9.234.167:39967 for reason: You offered us a block that we reject as invalid
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, 1719 blocks left to fetch
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8703 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.170.214:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 162.243.160.72:46456 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 92.243.18.20:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 188.138.107.159:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.19:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
I am disconnecting peer 146.185.186.245:54482 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.185.24.234:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1720 blocks left to fetch
I am disconnecting peer 176.9.234.167:39978 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "18 seconds old",
"blockchain_head_block_timestamp": "20140702T132445",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132503",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1722 blocks left to fetch
I am disconnecting peer 176.9.234.167:39984 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1723 blocks left to fetch
I am disconnecting peer 176.9.234.167:39997 for reason: You offered us a block that we reject as invalid
Quote from: bytemaster on July 02, 2014, 01:27:46 PM
Quote from: sfinder on July 02, 2014, 01:24:25 PM
client keep on been disconnected form peers.
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
This peer is showing up on both of our seed nodes....
Peer 209.141.182.156:8701 disconnected us: You offered us a block that we reject as invalid
We are looking into the cause of this message... so don't take it personally if a peer rejects you right now.
Very interesting you are rejecting the very first block as invalid...
If you start with a fresh data directory do you always get this problem?
XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98
Some funds please. :D :D
Quote from: metalallen on July 02, 2014, 02:16:23 PM
XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98
Some funds please. :D :D
50 XTS on the way
Quote from: metalallen on July 02, 2014, 02:16:23 PM
XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98
Some funds please. :D :D
Sent
3921.0 2014-07-02T14:17:45 spartako-w metalallen 100.00000 XTS 0.10000 XTS e30da037
3925.0 2014-07-02T14:18:45 spartako-w metalallen 100.000000 FREE 0.10000 XTS 2e6cff90
Quote from: metalallen on July 02, 2014, 02:16:23 PM
XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98
Some funds please. :D :D
111xts on the way
Quote from: sfinder on July 02, 2014, 02:13:08 PM
I experienced the same problem many times from different dry run . It always happened after many hours running and suddenly client stop synchronize with main chain and block number count stop . if I quit the client and re-run it following error will appear and client crashed
(wallet closed) >>> open doggy
Program received signal SIGSEGV, Segmentation fault.
_int_malloc (av=0x7ffff697e760 <main_arena>, bytes=128) at malloc.c:3302
3302 malloc.c: No such file or directory.
(gdb)
then I will reboot my linux box and delete the "peers.leveldb" folder and restart my client then client will restart but keeping on disconnecting form peer as I posted in my last post.
the only way for me to get back to normal is to delete all the /.BitSharesXTS folder and re-sync the block chain form beginning
Quote from: bytemaster on July 02, 2014, 01:57:21 PM
Quote from: bytemaster on July 02, 2014, 01:55:08 PM
Quote from: sfinder on July 02, 2014, 01:34:14 PM
more info below
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "15 seconds old",
"blockchain_head_block_timestamp": "20140702T132130",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132145",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>>
[detached from 1587.bts]
coins@coins:~$ ^C
coins@coins:~$ screen -r bts
I am disconnecting peer 107.170.30.182:8701 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1716 blocks left to fetch
--- there are now 2 active connections to the p2p network
I am disconnecting peer 107.170.90.142:8701 for reason: You offered us a block that we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
I am disconnecting peer 84.238.140.192:36350 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39931 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.112:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.187.91.24:35790 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1718 blocks left to fetch
I am disconnecting peer 176.9.234.167:39967 for reason: You offered us a block that we reject as invalid
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, 1719 blocks left to fetch
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8703 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.170.214:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 162.243.160.72:46456 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 92.243.18.20:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 188.138.107.159:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.19:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
I am disconnecting peer 146.185.186.245:54482 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.185.24.234:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1720 blocks left to fetch
I am disconnecting peer 176.9.234.167:39978 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "18 seconds old",
"blockchain_head_block_timestamp": "20140702T132445",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140702T132503",
"ntp_error": -0.0023029999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "77 days in the future",
"wallet_unlocked_until_timestamp": "20140917T171137",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1722 blocks left to fetch
I am disconnecting peer 176.9.234.167:39984 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1723 blocks left to fetch
I am disconnecting peer 176.9.234.167:39997 for reason: You offered us a block that we reject as invalid
Quote from: bytemaster on July 02, 2014, 01:27:46 PM
Quote from: sfinder on July 02, 2014, 01:24:25 PM
client keep on been disconnected form peers.
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
This peer is showing up on both of our seed nodes....
Peer 209.141.182.156:8701 disconnected us: You offered us a block that we reject as invalid
We are looking into the cause of this message... so don't take it personally if a peer rejects you right now.
Very interesting you are rejecting the very first block as invalid...
If you start with a fresh data directory do you always get this problem?
Ok, so I think I can summarize your problem as:
1) log files getting to large (32 bit machine?)
2) crashing that leaves the database in inconsistent state.
3) unable to synchronize with a database in an inconsistent state.
Our solutions are:
1) We need to add extra validation checks on startup
2) We are putting in code today to greatly reduce logging now that we have found most issues.
Quote from: bitdraw on July 02, 2014, 12:49:20 PM
- when i try to log in with my password i just see the rotating symbol but it doesnt log me in and goes on forever
(temporary issue)
same with me after first log-out
that means you must have it open all the time
but even that is not possible because the "Logout timeout, seconds" option on Preferences didnt't work !!!so the client log automaticaly out even when you have updated to 6000 seconds....
PS only after I deleted directories:
1.chain
EDIT (only delete this folder and it schould be enough....)
2.exceptions
3.peers.leveldb
(not wallets)
I could sign-in again
Quote from: xeroc on July 02, 2014, 02:17:53 PM
Quote from: metalallen on July 02, 2014, 02:16:23 PM
XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98
Some funds please. :D :D
50 XTS on the way
Quote from: spartako on July 02, 2014, 02:19:22 PM
Quote from: metalallen on July 02, 2014, 02:16:23 PM
XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98
Some funds please. :D :D
Sent
3921.0 2014-07-02T14:17:45 spartako-w metalallen 100.00000 XTS 0.10000 XTS e30da037
3925.0 2014-07-02T14:18:45 spartako-w metalallen 100.000000 FREE 0.10000 XTS 2e6cff90
Quote from: sfinder on July 02, 2014, 02:23:15 PM
Quote from: metalallen on July 02, 2014, 02:16:23 PM
XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98
Some funds please. :D :D
111xts on the way
Got it! Thx guys~ +5%
send me some funs for test,pls!
XTS7g35g4ZYA9NQ7xjpbXac6s7qogDPTRwbeg47XzeMyGKNp9skUL
Quote from: kinglaw0577 on July 02, 2014, 02:35:43 PM
send me some funs for test,pls!
XTS7g35g4ZYA9NQ7xjpbXac6s7qogDPTRwbeg47XzeMyGKNp9skUL
sent
Quote from: liondani on July 02, 2014, 02:27:51 PM
Quote from: bitdraw on July 02, 2014, 12:49:20 PM
- when i try to log in with my password i just see the rotating symbol but it doesnt log me in and goes on forever
(temporary issue)
same with me after first log-out
that means you must have it open all the time
but even that is not possible because the "Logout timeout, seconds" option on Preferences didnt't work !!!
so the client log automaticaly out even when you have updated to 6000 seconds....
PS only after I deleted directories:
1.chain
2.exceptions
3.peers.leveldb
(not wallets)
I could sign-in again
Yes same issue and solution, only problem is that by the time it syncs it locks again.
CPU is active 16 / 17 percent whilst spinning and trying to login, I guess this is due to the UI.
Other issues. Importing multibit wallet did not get any response.
When deleting chain and peers, I am able to see and navigate through the wallet before I get redirected to the logon screen.
Quote from: bytemaster on July 02, 2014, 12:24:20 PM
ID NAME APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
366 clout-delegate2 0.0075000283 % 0 18 0.00 % 50 % 0.00000 XTS NONE
397 webber 0.0025000094 % 0 7 0.00 % 100 % 0.00000 XTS NONE
Whats going on guys?
I am also very confused.My server is in China,i guess is network problem in china.delay with us/eur more than 250ms.
How about somebody else's server in chian?
send me some funds please, Thanks.
XTS6fFRG8YePxSRwMNvvpQndEc7HqmxmcqmLvTsCn8J9F3vtMg5k4
what is below error??
RPC Server Error
In method 'batch': 6 key_not_found_exception: Key Not Found unable to find key 539 {"key":539} bitshares level_map.hpp:74 bts::db::level_map::fetch error fetching key 539 {"key":539} bitshares level_map.hpp:84 bts::db::level_map::fetch {"block_num":539} bitshares chain_database.cpp:1109 bts::blockchain::chain_database::get_block_id {} bitshares common_api_client.cpp:339 bts::rpc_stubs::common_api_client (500)
want some funds for testing purpose.thanks!!
lzr1900
XTS7XaDD7TB8CR5zoxuZmc2hPAaVD7ybE8knTW7CC2afdv99PEC29
Quote from: spartako on July 02, 2014, 12:11:20 PM
It seems I lost 100 FREE.
I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:
Init balance: 1,000,0000 FREE
3411.11 2014-07-02T11:55:15 spartako-w spartako-w 1.000000 FREE 0.10000 XTS 1b8b05d1
3432.12 2014-07-02T12:01:00 spartako-w demonstra 100.000000 FREE 0.10000 XTS 68a98a80
3447.9 2014-07-02T12:05:30 spartako-w bitdraw 100.000000 FREE 0.10000 XTS 30626c46
Finale balance: 999,700.000000 FREE but should be 999,800 FREE
I have made an issue: https://github.com/BitShares/bitshares_toolkit/issues/444
Quote from: bennyliaa on July 02, 2014, 03:20:58 PM
what is below error??
RPC Server Error
In method 'batch': 6 key_not_found_exception: Key Not Found unable to find key 539 {"key":539} bitshares level_map.hpp:74 bts::db::level_map::fetch error fetching key 539 {"key":539} bitshares level_map.hpp:84 bts::db::level_map::fetch {"block_num":539} bitshares chain_database.cpp:1109 bts::blockchain::chain_database::get_block_id {} bitshares common_api_client.cpp:339 bts::rpc_stubs::common_api_client (500)
Looks like you went to the block explorer and the web interface attempted to fetch a block prior to it being downloaded.
Quote from: vikram on July 02, 2014, 03:51:13 PM
Quote from: spartako on July 02, 2014, 12:11:20 PM
It seems I lost 100 FREE.
I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:
Init balance: 1,000,0000 FREE
3411.11 2014-07-02T11:55:15 spartako-w spartako-w 1.000000 FREE 0.10000 XTS 1b8b05d1
3432.12 2014-07-02T12:01:00 spartako-w demonstra 100.000000 FREE 0.10000 XTS 68a98a80
3447.9 2014-07-02T12:05:30 spartako-w bitdraw 100.000000 FREE 0.10000 XTS 30626c46
Finale balance: 999,700.000000 FREE but should be 999,800 FREE
I have made an issue: https://github.com/BitShares/bitshares_toolkit/issues/444
Thanks! I monitor the balance if 100 FREE come back in my wallet
Quote from: dxtr on July 02, 2014, 11:40:05 AM
Quote from: cass on July 02, 2014, 10:54:18 AM
Quote from: dxtr on July 02, 2014, 10:48:04 AM
Does anyone know if keyhotee founders should have some initial funds after importing keyhotee id?
I did so, and have 0, maybe there is something one should do in order to receive it?
did you try
wallet_rescan_blockchain
maybe this could help!?
I tried it, but not really :(
I'm afraid keyhotee funds are not included in this blockchain, but I'm not sure about that...
Do you get the funds if you import the private key for the PTS address which you used to donate as a Keyhotee Founder?
I will double check which key they are supposed to be associated with.
Quote from: spartako on July 02, 2014, 03:56:51 PM
Quote from: vikram on July 02, 2014, 03:51:13 PM
Quote from: spartako on July 02, 2014, 12:11:20 PM
It seems I lost 100 FREE.
I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:
Init balance: 1,000,0000 FREE
3411.11 2014-07-02T11:55:15 spartako-w spartako-w 1.000000 FREE 0.10000 XTS 1b8b05d1
3432.12 2014-07-02T12:01:00 spartako-w demonstra 100.000000 FREE 0.10000 XTS 68a98a80
3447.9 2014-07-02T12:05:30 spartako-w bitdraw 100.000000 FREE 0.10000 XTS 30626c46
Finale balance: 999,700.000000 FREE but should be 999,800 FREE
I have made an issue: https://github.com/BitShares/bitshares_toolkit/issues/444
Thanks! I monitor the balance if 100 FREE come back in my wallet
You should be able to rescan to get them back, but beware the rescan may take a long time.
Quote from: vikram on July 02, 2014, 03:57:37 PM
Quote from: spartako on July 02, 2014, 03:56:51 PM
Quote from: vikram on July 02, 2014, 03:51:13 PM
Quote from: spartako on July 02, 2014, 12:11:20 PM
It seems I lost 100 FREE.
I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:
Init balance: 1,000,0000 FREE
3411.11 2014-07-02T11:55:15 spartako-w spartako-w 1.000000 FREE 0.10000 XTS 1b8b05d1
3432.12 2014-07-02T12:01:00 spartako-w demonstra 100.000000 FREE 0.10000 XTS 68a98a80
3447.9 2014-07-02T12:05:30 spartako-w bitdraw 100.000000 FREE 0.10000 XTS 30626c46
Finale balance: 999,700.000000 FREE but should be 999,800 FREE
I have made an issue: https://github.com/BitShares/bitshares_toolkit/issues/444
Thanks! I monitor the balance if 100 FREE come back in my wallet
You should be able to rescan to get them back, but beware the rescan may take a long time.
Yes, I tried to rescan but the balance was the same. I will retry in next hours
oh, got it. actually I did what you said. :P
Quote from: bytemaster on July 02, 2014, 03:53:41 PM
Quote from: bennyliaa on July 02, 2014, 03:20:58 PM
what is below error??
RPC Server Error
In method 'batch': 6 key_not_found_exception: Key Not Found unable to find key 539 {"key":539} bitshares level_map.hpp:74 bts::db::level_map::fetch error fetching key 539 {"key":539} bitshares level_map.hpp:84 bts::db::level_map::fetch {"block_num":539} bitshares chain_database.cpp:1109 bts::blockchain::chain_database::get_block_id {} bitshares common_api_client.cpp:339 bts::rpc_stubs::common_api_client (500)
Looks like you went to the block explorer and the web interface attempted to fetch a block prior to it being downloaded.
I am on 64bit ubuntu 14.04
coins@coins:~$ uname -a
Linux coins 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
coins@coins:~$
Quote from: bytemaster on July 02, 2014, 02:26:54 PM
Ok, so I think I can summarize your problem as:
1) log files getting to large (32 bit machine?)
2) crashing that leaves the database in inconsistent state.
3) unable to synchronize with a database in an inconsistent state.
Our solutions are:
1) We need to add extra validation checks on startup
2) We are putting in code today to greatly reduce logging now that we have found most issues.
Quote from: lzr1900 on July 02, 2014, 03:22:30 PM
want some funds for testing purpose.thanks!!
lzr1900
XTS7XaDD7TB8CR5zoxuZmc2hPAaVD7ybE8knTW7CC2afdv99PEC29
111 xts on the way
Quote from: vikram on July 02, 2014, 03:57:03 PM
Quote from: dxtr on July 02, 2014, 11:40:05 AM
Quote from: cass on July 02, 2014, 10:54:18 AM
Quote from: dxtr on July 02, 2014, 10:48:04 AM
Does anyone know if keyhotee founders should have some initial funds after importing keyhotee id?
I did so, and have 0, maybe there is something one should do in order to receive it?
did you try
wallet_rescan_blockchain
maybe this could help!?
I tried it, but not really :(
I'm afraid keyhotee funds are not included in this blockchain, but I'm not sure about that...
Do you get the funds if you import the private key for the PTS address which you used to donate as a Keyhotee Founder?
I will double check which key they are supposed to be associated with.
Thanks, I did import wallet.dat and it works fine, I got some XTS fromthere, not by wallet_import_keyhotee (as I thought I would get - my bad).
Mac GUI
http://www.bitshares.org/BitSharesXT-0.0.8.dmg (http://www.bitshares.org/BitSharesXT-0.0.7.dmg)
This is a new chain, if you do not delete your data directory from the last chain things may not work.
rm -r ~/Library/Application\ Support/BitShares\ XTS
Every 15 seconds !!!
(http://wmhagency.com/wp/wp-content/uploads/2013/01/420-back_to_the_future-420x01.jpg)
My delegate node on a VPS server with 20GB HDD ran out of space overnight. Looks like more disk space is needed. I wonder how much is enough..
98% of delegates produced in the last round and most of them are not the init delegates!
Quote from: bitcoinerS on July 02, 2014, 04:41:45 PM
My delegate node on a VPS server with 20GB HDD ran out of space overnight. Looks like more disk space is needed. I wonder how much is enough..
No more disk space is required, just restart and it will clear the logs.
Guys could you vote for us wallet_approve_delegate bitsapphire true.
We need to test our server performance this timje around.
Quote from: bytemaster on July 01, 2014, 09:14:47 PM
3) All transactions must now expire in less than 48 hours, and by default expire in 24 if they are not included in the chain.
Really all the transactions including the ones got confirmed ? Why?
Quote from: heyD on July 02, 2014, 05:09:02 PM
Quote from: bytemaster on July 01, 2014, 09:14:47 PM
3) All transactions must now expire in less than 48 hours, and by default expire in 24 if they are not included in the chain.
Really all the transactions including the ones got confirmed ? Why?
Expire simply means they cannot be applied a second time and allows the validators to remove them from memory. They result of the transaction is still valid if it was confirmed.
TXN ID SIZE OPERATION COUNT SIGNATURE COUNT
----------------------------------------------------------------------
8b3495ae 9844 102 101
ae3af881 340 3 2
c8908453 244 2 1
ce04af40 244 2 1
d5c5e0e0 253 3 1
dd3514a1 244 2 1
f2242b6c 320 3 2
f33fa096 340 3 2
fac67bf9 320 3 2
When are those pending transactions being served?
I made some transfers between my accounts that are not registered (there was also one from registered -> unregistered), and those went into pending, and keep on hanging...
I thought that maybe only approved delegates validate them, but apparently they don't...
the link is still 0.0.7.
current version of the gui wallet has a problem: once you exit the wallet, next time when you open the wallet you can't unlock it.
Quote from: bytemaster on July 02, 2014, 04:32:54 PM
Mac GUI
http://www.bitshares.org/BitSharesXT-0.0.8.dmg (http://www.bitshares.org/BitSharesXT-0.0.7.dmg)
This is a new chain, if you do not delete your data directory from the last chain things may not work.
rm -r ~/Library/Application\ Support/BitShares\ XTS
Quote from: itnom on July 02, 2014, 05:01:22 PM
Guys could you vote for us wallet_approve_delegate bitsapphire true.
We need to test our server performance this timje around.
+5% +5%
I'm trying to use only the web wallet this time around, it's looking very nice!
It might need a bit more info on the account key; something like "give this to anyone who wants to send you XTS".
I'm assuming the "account key" is the one I need for someone to send me some XTS? If so, can someone please send me some so I can register a delegate?
XTS57p8jJKZJ5xDGs4T7AdxNR1mjtPbkKEmHmkfM519Lxn6nSxv7w
Thanks
Quote from: vlight on July 02, 2014, 06:09:29 PM
Quote from: spartako on July 02, 2014, 03:56:51 PM
Quote from: vikram on July 02, 2014, 03:51:13 PM
Quote from: spartako on July 02, 2014, 12:11:20 PM
It seems I lost 100 FREE.
I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:
Init balance: 1,000,0000 FREE
3411.11 2014-07-02T11:55:15 spartako-w spartako-w 1.000000 FREE 0.10000 XTS 1b8b05d1
3432.12 2014-07-02T12:01:00 spartako-w demonstra 100.000000 FREE 0.10000 XTS 68a98a80
3447.9 2014-07-02T12:05:30 spartako-w bitdraw 100.000000 FREE 0.10000 XTS 30626c46
Finale balance: 999,700.000000 FREE but should be 999,800 FREE
I have made an issue: https://github.com/BitShares/bitshares_toolkit/issues/444
Thanks! I monitor the balance if 100 FREE come back in my wallet
Yes, my 3 transactions got stuck so i cleared them and the balance did not increase back. Lost 2400 XTS :'(
If you close and re-open your wallet does the balance come back?
Quote from: vlight on July 02, 2014, 06:30:56 PM
Quote from: bytemaster on July 02, 2014, 06:11:08 PM
If you close and re-open your wallet does the balance come back?
I restarted the system. All XTS finally went through and were received by the correct recipients in other wallets. :)
However, the transaction history looks like this now.
wallet-2 (unlocked) >>> wallet_account_transaction_history
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
376.1 2014-07-01T22:22:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS cab14a52
4670.0 2014-07-02T17:33:45 light1 light4 800.00000 XTS 0.10000 XTS 5921bca7
4741.5 2014-07-02T17:52:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS cc49f64c
4741.3 2014-07-02T17:52:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS c6ca00e1
4741.0 2014-07-02T17:52:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 9e9abf50
Can you list your unregistered accounts?
How do you explain that my best delegates "liondani" (27 produced 1 missed) is in the stand by list and 4 of my worst delegates that have 0 produced and about 2-3 missed are on the top delegates?(liondani-delegate-1, -3, -4, -8)
PS only liondani-delegate-1 has funds
Quote from: liondani on July 02, 2014, 06:44:14 PM
How do you explain that my best delegates "liondani" (27 produced 1 missed) is in the stand by list and 4 of my worst delegates that have 0 produced and about 2-3 missed are on the top delegates?(liondani-delegate-1, -3, -4, -8)
PS only liondani-delegate-1 has funds
There is no auto-voting right now. Unless someone has given you an approval vote and then made transactions to that effect it will not change your ranking.
QuoteQuote from: liondani on Today at 06:44:14 PM
How do you explain that my best delegates "liondani" (27 produced 1 missed) is in the stand by list and 4 of my worst delegates that have 0 produced and about 2-3 missed are on the top delegates?(liondani-delegate-1, -3, -4, -8)
PS only liondani-delegate-1 has funds
QuoteThere is no auto-voting right now. Unless someone has given you an approval vote and then made transactions to that effect it will not change your ranking.
Is the delegate ranking based on the amount of funds transmitted by wallet(s) with wallet_approve_delegate <delegate(s)> in each round, in total, other? Perhaps you could direct me to some reference material pm the subject.
Thanks,
Fox
Quote from: Fox on July 02, 2014, 07:02:45 PM
QuoteQuote from: liondani on Today at 06:44:14 PM
How do you explain that my best delegates "liondani" (27 produced 1 missed) is in the stand by list and 4 of my worst delegates that have 0 produced and about 2-3 missed are on the top delegates?(liondani-delegate-1, -3, -4, -8)
PS only liondani-delegate-1 has funds
QuoteThere is no auto-voting right now. Unless someone has given you an approval vote and then made transactions to that effect it will not change your ranking.
Is the delegate ranking based on the amount of funds transmitted by wallet(s) with wallet_approve_delegate <delegate(s)> in each round, in total, other? Perhaps you could direct me to some reference material pm the subject.
Thanks,
Fox
It isn't based on transaction volume, but instead every balance is voting for N delegates. When you transfer funds you update the balance and the votes.
Quote from: bytemaster on July 02, 2014, 07:10:08 PM
It isn't based on transaction volume, but instead every balance is voting for N delegates. When you transfer funds you update the balance and the votes.
Does it affect the votes if N is smal or not and how are they divided?
For example with the same balance 2 different scenarios:
1. transfer x funds and had voted N delegates
2. transfer x funds and had voted (2*N) delegates
will each delegate in the second senario get the same votes like in scenario 1 ?
Not sure if I have to post here...
I have installed the GUI 0.8 version. I have created an account "zeus" and put a password.
The account showed some numbers 3 Accounts, 2 delegates etc. when I was clicking on them nothing was showing.
I pressed the button "lock" and after a couple of minutes my wallet was locked. I put the password to unlock it and just waiting and waiting and waiting and never unlocked...
:(
On another note... From the 5 minutes I got the chance to look at it the first thing that came to my mind was that this looks like counterparty..and I don't like counterparty..Nxt platform is much nicer... :(
Like I said earlier the web wallet is looking good, and Hackfisher immediately corrected a spelling error I pointed out on github :)
There's one function currently throwing errors, it's the delegate list. It's simply because in the blockchain service list_delegates is called with "count" parameter set to -1. This throws an error. Setting it to a positive number fixes it, it's on line 133 of "blockchain.coffee", I've set it to 200 here:
@q.all({dels: @blockchain_api.list_delegates(0,200), config: @get_config()}).then (results) =>
To Zeus: Those numbers you're seeing are currently hardcoded simply as numbers, they're not actually being updated. Will get updated soon I'm sure.
Do you guys now why some windows computers will not open the gui? On one of my computers says "There is no disk in the drive. Please insert a disk into drive F:."
Looks like we got some forks..
>>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2840
e44923abbdc141cb2fa3e9338d89029e152256c7 vikram10 34 8862 2014-07-02T09:11:00 2 YES NO
6f1a88b185cf482735dc3921ab9f090bae9146e9 alexxy 32 8854 2014-07-02T09:10:45 18 YES YES
3378
29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb lexx-6 34 8862 2014-07-02T11:45:45 14 YES YES
745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978 heyd-haiyaoce100lun 33 8618 2014-07-02T11:46:00 5 N/A NO
4852
0204f5c0b49fddcff6bfd2659975e3f0549ea626 init5 0 182 2014-07-02T18:22:45 0 YES YES
f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d longclaw 1 426 2014-07-02T18:42:30 41 N/A NO
5099
4361a302b417e72030ee4a7a54f6cbb12246ef18 init3 35 8722 2014-07-02T19:30:30 8 YES YES
279026c0485e73d51f435bd08b14c59b45cdb9a2 oathkeeper 35 8722 2014-07-02T19:31:00 8 N/A NO
>>> about
{
"bitshares_toolkit_revision": "85d44b47f23e66c7fb8c6c639a298dba9b20e09a",
"bitshares_toolkit_revision_age": "6 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "24 hours ago",
"compile_date": "compiled on Jul 2 2014 at 09:46:48"
}
Quote from: bitcoinerS on July 02, 2014, 07:41:50 PM
Looks like we got some forks..
>>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2840
e44923abbdc141cb2fa3e9338d89029e152256c7 vikram10 34 8862 2014-07-02T09:11:00 2 YES NO
6f1a88b185cf482735dc3921ab9f090bae9146e9 alexxy 32 8854 2014-07-02T09:10:45 18 YES YES
3378
29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb lexx-6 34 8862 2014-07-02T11:45:45 14 YES YES
745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978 heyd-haiyaoce100lun 33 8618 2014-07-02T11:46:00 5 N/A NO
4852
0204f5c0b49fddcff6bfd2659975e3f0549ea626 init5 0 182 2014-07-02T18:22:45 0 YES YES
f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d longclaw 1 426 2014-07-02T18:42:30 41 N/A NO
5099
4361a302b417e72030ee4a7a54f6cbb12246ef18 init3 35 8722 2014-07-02T19:30:30 8 YES YES
279026c0485e73d51f435bd08b14c59b45cdb9a2 oathkeeper 35 8722 2014-07-02T19:31:00 8 N/A NO
>>> about
{
"bitshares_toolkit_revision": "85d44b47f23e66c7fb8c6c639a298dba9b20e09a",
"bitshares_toolkit_revision_age": "6 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "24 hours ago",
"compile_date": "compiled on Jul 2 2014 at 09:46:48"
}
Dont know if it is coincidence but I attempted to make ~2k transactions around block 5095.
EDIT: Some of them are still pending but they are processed at steady rate.
Quote from: vikram on July 02, 2014, 08:54:59 AM
Quote from: Kenof on July 02, 2014, 05:50:48 AM
damn, still cannot import keyhotee, problem is in my brainkey because it contains characters like "!" and "@", after "!" no letters are scanned and get wrong keyhotee id scanned :-\
so i join to the population of beggars, please send me some funds to play with
domis-1
XTS8c3oGHR9XNSRPV9yYZspcPC2HMowrp6pyadyywpRMFeCSw94E8
thanks
So even entering you brainkey in quotes "<brainkey>" does not work?
If you are on Windows, you can try running the latest nightly build of Keyhotee from: http://bitshares.org/resources/downloads/ which has a button to copy your private key for an identity. You can then import this private key into the BitShares client using 'wallet_import_private_key <keyhotee_private_key>'. I was able to successfully claim my name from the genesis block using this method. Updated Mac and Linux Keyhotee builds coming soon.
Others please let us know if you have trouble with the brainkeys as well.
1st method unfortunately didn't work, then tried as suggested with keyhotee exporting private key, that worked like charm, thanks
@liondani
Thank you very much for funds, you have my vote ;)
PS.
more forks :-\
Our XTS balance will be reset on the next dry run right?
I'm asking this because i sent ~700K XTS by mistake (trying to vote for a delegate).
Dry runs take the last snapshot of the blockchain? or is always using the original genesis.json balance?
(don't make me cry ... :'()
Quote from: ElMato on July 02, 2014, 08:00:58 PM
Our XTS balance will be reset on the next dry run right?
I'm asking this because i sent ~700K XTS by mistake (trying to vote for a delegate).
Dry runs take the last snapshot of the blockchain? or is always using the original genesis.json balance?
(don't make me cry ... :'()
They always reset to genesis and are not snapshots. XTS networks should never have any value, they are just like the BTC test network.
just wondering how you can list the assets that other than XTS. which command do you use for following list?
Quote from: spartako on July 02, 2014, 12:11:20 PM
It seems I lost 100 FREE.
I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:
Init balance: 1,000,0000 FREE
3411.11 2014-07-02T11:55:15 spartako-w spartako-w 1.000000 FREE 0.10000 XTS 1b8b05d1
3432.12 2014-07-02T12:01:00 spartako-w demonstra 100.000000 FREE 0.10000 XTS 68a98a80
3447.9 2014-07-02T12:05:30 spartako-w bitdraw 100.000000 FREE 0.10000 XTS 30626c46
Finale balance: 999,700.000000 FREE but should be 999,800 FREE
kind of bad news after one day's hardworking.....
Quote from: bitcoinerS on July 02, 2014, 07:41:50 PM
Looks like we got some forks..
>>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2840
e44923abbdc141cb2fa3e9338d89029e152256c7 vikram10 34 8862 2014-07-02T09:11:00 2 YES NO
6f1a88b185cf482735dc3921ab9f090bae9146e9 alexxy 32 8854 2014-07-02T09:10:45 18 YES YES
3378
29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb lexx-6 34 8862 2014-07-02T11:45:45 14 YES YES
745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978 heyd-haiyaoce100lun 33 8618 2014-07-02T11:46:00 5 N/A NO
4852
0204f5c0b49fddcff6bfd2659975e3f0549ea626 init5 0 182 2014-07-02T18:22:45 0 YES YES
f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d longclaw 1 426 2014-07-02T18:42:30 41 N/A NO
5099
4361a302b417e72030ee4a7a54f6cbb12246ef18 init3 35 8722 2014-07-02T19:30:30 8 YES YES
279026c0485e73d51f435bd08b14c59b45cdb9a2 oathkeeper 35 8722 2014-07-02T19:31:00 8 N/A NO
>>> about
{
"bitshares_toolkit_revision": "85d44b47f23e66c7fb8c6c639a298dba9b20e09a",
"bitshares_toolkit_revision_age": "6 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "24 hours ago",
"compile_date": "compiled on Jul 2 2014 at 09:46:48"
}
Quote from: sfinder on July 02, 2014, 08:35:36 PM
kind of bad news after one day's hardworking.....
Quote from: bitcoinerS on July 02, 2014, 07:41:50 PM
Looks like we got some forks..
>>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2840
e44923abbdc141cb2fa3e9338d89029e152256c7 vikram10 34 8862 2014-07-02T09:11:00 2 YES NO
6f1a88b185cf482735dc3921ab9f090bae9146e9 alexxy 32 8854 2014-07-02T09:10:45 18 YES YES
3378
29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb lexx-6 34 8862 2014-07-02T11:45:45 14 YES YES
745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978 heyd-haiyaoce100lun 33 8618 2014-07-02T11:46:00 5 N/A NO
4852
0204f5c0b49fddcff6bfd2659975e3f0549ea626 init5 0 182 2014-07-02T18:22:45 0 YES YES
f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d longclaw 1 426 2014-07-02T18:42:30 41 N/A NO
5099
4361a302b417e72030ee4a7a54f6cbb12246ef18 init3 35 8722 2014-07-02T19:30:30 8 YES YES
279026c0485e73d51f435bd08b14c59b45cdb9a2 oathkeeper 35 8722 2014-07-02T19:31:00 8 N/A NO
>>> about
{
"bitshares_toolkit_revision": "85d44b47f23e66c7fb8c6c639a298dba9b20e09a",
"bitshares_toolkit_revision_age": "6 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "24 hours ago",
"compile_date": "compiled on Jul 2 2014 at 09:46:48"
}
Yes, apparently processing time on the database accesses is growing with the dataset. Empty blocks use to take .005 seconds are now taking 1 second which turns into 1 second per hop and thus increases the potential for forks. We know ways to accelerate this.
Quote from: bennyliaa on July 02, 2014, 03:19:04 PM
send me some funds please, Thanks.
XTS6fFRG8YePxSRwMNvvpQndEc7HqmxmcqmLvTsCn8J9F3vtMg5k4
just sent
Quote from: Zeus on July 02, 2014, 07:25:36 PM
Not sure if I have to post here...
I have installed the GUI 0.8 version. I have created an account "zeus" and put a password.
The account showed some numbers 3 Accounts, 2 delegates etc. when I was clicking on them nothing was showing.
I pressed the button "lock" and after a couple of minutes my wallet was locked. I put the password to unlock it and just waiting and waiting and waiting and never unlocked...
:(
On another note... From the 5 minutes I got the chance to look at it the first thing that came to my mind was that this looks like counterparty..and I don't like counterparty..Nxt platform is much nicer... :(
thats a bug!
don't lock it next time...
delete folder chain
path:
C:\Users\********yourrusername*******\AppData\Roaming\BitShares XTS\chain
and run the client again
Quote from: liondani on July 02, 2014, 08:53:23 PM
Quote from: Zeus on July 02, 2014, 07:25:36 PM
Not sure if I have to post here...
I have installed the GUI 0.8 version. I have created an account "zeus" and put a password.
The account showed some numbers 3 Accounts, 2 delegates etc. when I was clicking on them nothing was showing.
I pressed the button "lock" and after a couple of minutes my wallet was locked. I put the password to unlock it and just waiting and waiting and waiting and never unlocked...
:(
On another note... From the 5 minutes I got the chance to look at it the first thing that came to my mind was that this looks like counterparty..and I don't like counterparty..Nxt platform is much nicer... :(
thats a bug!
don't lock it next time...
delete folder chain
path:
C:\Users\********yourrusername*******\AppData\Roaming\BitShares XTS\chain
and run the client again
This is a known issue, they are waiting because scanning transactions in the background, we need enhancement of ui feedback of this.
I do not think you need to delete you chain dir, you can see the scanning progress if you are in cli.
https://github.com/BitShares/web_wallet/issues/91
How is the network going to deal with transaction flooding?
I know that when there is value put in network, then making thousands of transactions means money, but let's assume that there is a triggering event, that causes hundreds or even thousands of users to, simultaneously, create a transaction of any kind.
Now there are max 30tx/blk, but there might be a peak demand of network for 500 or 15k transactions per minute - then all those transactions are pending, effectively blocking new transactions from entering into blockchain.
On the other hand all delegates know what those pending transactions are, and how many are there.
What if delegates could control block production rate and/or block capacity in order to deal with pending transactions faster.
Something like delegate A sees that there are over 500 pending transactions, so he issues a block with indicator that block creation rate should be increased.
Now the whole network can agree or disagree - they all have necessary data to verify.
Next in queue, delegate B validates this aswell and if he agrees, he confirms A's suggestion, and delegate C will produce next block faster.
Then, if pending operation decreases to 100, delegate D can suggest decreasing rate to normal, delegate E can confirm, and delegate F can produce a block at normal rate.
There could be more than one thresholds for pending operations amount so that rate and/or capacity of a block could have many shifting gears.
I don't know if it's worth something, or am I just making a fool of myself :D
Please help me understand how transaction size (# of XTS within a tx) impacts the block commitment time. I have many transactions marked as PENDING.
wallet_account_transaction_history
I have sent numerous transactions of varying the size from 10, 100, 1000 and 10000 XTS per transaction. The 10 & 100 XTS transactions typically approve in the very next block. The 1000 XTS transactions are hit and miss, with some going straight away and others left PENDING for a number of minutes. The 10000 XTS transactions nearly all are left PENDING, now for hours. Each PENDING transactions lists a FEE of 0.10000 XTS.
I have restarted the client, clearing the peer database and resyncing the blockchain:
./bitshares_client --clear-peer-database --resync-blockchain
I have rescanned the blockchain:
wallet_rescan_blockchain
The transactions remain PENDING. I believe they will expire in 48 hours, but am wondering how the network [should] process these transaction when posted with:
wallet_transfer <amount_to_transfer> <asset_symbol> <from_account_name> <to_account_name> [memo_message]
Thanks,
Fox
send me some XTS please, Thanks.
XTS7rhnNyCyjwBNnDtqRPkUEEC7kbycrDFdxHfD76cozHcV17KCLY
Quote from: suwoder on July 02, 2014, 09:57:36 PM
send me some XTS please, Thanks.
XTS7rhnNyCyjwBNnDtqRPkUEEC7kbycrDFdxHfD76cozHcV17KCLY
sent
Just downloaded the windows wallet for the first time, and it looks great.
Please send some funds here XTS67fu5FNdB6VgGK1QGjyvUGEJhrddDH1x649zypCZSNrf15UR6V
I will play with it and see if I can set up a delegate.
Quote from: sumantso on July 02, 2014, 10:31:02 PM
Just downloaded the windows wallet for the first time, and it looks great.
Please send some funds here XTS67fu5FNdB6VgGK1QGjyvUGEJhrddDH1x649zypCZSNrf15UR6V
I will play with it and see if I can set up a delegate.
sent
Quote from: cass on July 02, 2014, 10:33:30 PM
Quote from: sumantso on July 02, 2014, 10:31:02 PM
Just downloaded the windows wallet for the first time, and it looks great.
Please send some funds here XTS67fu5FNdB6VgGK1QGjyvUGEJhrddDH1x649zypCZSNrf15UR6V
I will play with it and see if I can set up a delegate.
sent
Thanks, waiting for it to sync now.
Most of my delegates are missing blocks because windows gui unlocks automaticaly (preferences don't work)
and it takes an eternity to scan the blockchain from the beginning. (I don't want to reimagine how long it takes after month's of transactions even with a "light weight" client...)
Is it so difficult to fix at least the bug related with the auto log-out?... very fustrating and windows user's can not help testing. We are loosing precius time!
It stops syncing after block 1611. I deleted and resynced and got stuck at the same point. I have got 3 connections.
Quote from: Zeus on July 02, 2014, 07:25:36 PM
The account showed some numbers 3 Accounts, 2 delegates etc. when I was clicking on them nothing was showing.
Dashboard panel is currently not functional
I found while client try to fetch more than 1000 blocks data the client will almost stop responding to any keyboard input from user. it is not a bug but will give user very bad experience.
os:ubuntu 14.04
user interface: command line
Quote from: sumantso on July 02, 2014, 10:50:17 PM
It stops syncing after block 1611. I deleted and resynced and got stuck at the same point. I have got 3 connections.
Deleted again and downloading again without unlocking and seems to be syncing fine. Guess it doesn't like to try and get data while syncing.
EDIT: Now stuck at 1937 :(
To begin testing：XTS6n4GnKsg7yaZkHgERb2NZinTTCEPtQjT7wLnsuAQaf2qZiwwLW
Quote from: sfinder on July 02, 2014, 10:59:05 PM
I found while client try to fetch more than 1000 blocks data the client will almost stop responding to any keyboard input from user. it is not a bug but will give user very bad experience.
os:ubuntu 14.04
user interface: command line
yes during fetching blocks on start CPU usage is very high .. it a known issue
Quote from: cike on July 02, 2014, 11:08:25 PM
To begin testing：XTS6n4GnKsg7yaZkHgERb2NZinTTCEPtQjT7wLnsuAQaf2qZiwwLW
sent 33 XTS
Quote from: cike on July 02, 2014, 11:08:25 PM
To begin testing：XTS6n4GnKsg7yaZkHgERb2NZinTTCEPtQjT7wLnsuAQaf2qZiwwLW
ssseent
Hi
funds please for testing thanks 8)
XTS7txRFGTzKmoxfDUeUtM3MkZc4v9kwhU9xmccNQuu8qK2MwPFHf
Forks are back :'(
liondani (unlocked) >>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2840
6f1a88b185cf482735dc3921ab9f090bae9146e9 alexxy 32 8854 2014-07-02T09:10:45 17 YES YES
e44923abbdc141cb2fa3e9338d89029e152256c7 vikram10 34 8862 2014-07-02T09:11:00 4 N/A NO
3378
29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb lexx-6 34 8862 2014-07-02T11:45:45 14 YES YES
745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978 heyd-haiyaoce100lun 33 8618 2014-07-02T11:46:00 5 N/A NO
4852
0204f5c0b49fddcff6bfd2659975e3f0549ea626 init5 0 182 2014-07-02T18:22:45 0 YES YES
f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d longclaw 1 426 2014-07-02T18:42:30 41 N/A NO
5099
4361a302b417e72030ee4a7a54f6cbb12246ef18 init3 35 8722 2014-07-02T19:30:30 14 YES YES
279026c0485e73d51f435bd08b14c59b45cdb9a2 oathkeeper 35 8722 2014-07-02T19:31:00 8 N/A NO
5106
c7c0538c85eaab36606bd44aa7e0eaf243175d80 vikram 35 8722 2014-07-02T19:32:30 14 YES YES
59b8f634961d5cdd417eedade7d7bdb031827029 webber 35 8722 2014-07-02T19:45:00 7 N/A NO
Quote from: jwiz168 on July 02, 2014, 11:14:18 PM
Hi
funds please for testing thanks 8)
XTS7txRFGTzKmoxfDUeUtM3MkZc4v9kwhU9xmccNQuu8qK2MwPFHf
have fun ;D
wallet_create_from_json
works great :) and safes a lot of time - cool
Quote from: liondani on July 02, 2014, 11:14:59 PM
Forks are back :'(
liondani (unlocked) >>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2840
6f1a88b185cf482735dc3921ab9f090bae9146e9 alexxy 32 8854 2014-07-02T09:10:45 17 YES YES
e44923abbdc141cb2fa3e9338d89029e152256c7 vikram10 34 8862 2014-07-02T09:11:00 4 N/A NO
3378
29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb lexx-6 34 8862 2014-07-02T11:45:45 14 YES YES
745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978 heyd-haiyaoce100lun 33 8618 2014-07-02T11:46:00 5 N/A NO
4852
0204f5c0b49fddcff6bfd2659975e3f0549ea626 init5 0 182 2014-07-02T18:22:45 0 YES YES
f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d longclaw 1 426 2014-07-02T18:42:30 41 N/A NO
5099
4361a302b417e72030ee4a7a54f6cbb12246ef18 init3 35 8722 2014-07-02T19:30:30 14 YES YES
279026c0485e73d51f435bd08b14c59b45cdb9a2 oathkeeper 35 8722 2014-07-02T19:31:00 8 N/A NO
5106
c7c0538c85eaab36606bd44aa7e0eaf243175d80 vikram 35 8722 2014-07-02T19:32:30 14 YES YES
59b8f634961d5cdd417eedade7d7bdb031827029 webber 35 8722 2014-07-02T19:45:00 7 N/A NO
Those forks are nothing to worry about, we have gone 10 rounds with no forks and 93% participation.
Quote from: bytemaster on July 03, 2014, 12:06:10 AM
Those forks are nothing to worry about, we have gone 10 rounds with no forks and 93% participation.
dryrun7 is really wonderful.
do you have a plane for the official release?
or which issues should be fixed before the release?
>>> get_info
10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
{}
th_a chain_database.cpp:1057 get_slot_signee
{"timestamp":"20140703T012330"}
th_a chain_database.cpp:1059 get_slot_signee
{}
th_a chain_database.cpp:1075 get_next_producible_block_timestamp
{}
th_a common_api_client.cpp:1971 get_info
{"command":"get_info"}
th_a cli.cpp:538 execute_command
--- there are now 7 active connections to the p2p network
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "03df152999c1e9b5feacd623e1022d2e315a4d2c",
"bitshares_toolkit_revision_age": "3 hours ago",
"fc_revision": "6dbcba505b230ee77a0a7fe8af5f5e43c59b0b75",
"fc_revision_age": "4 hours ago",
"compile_date": "compiled on Jul 2 2014 at 17:43:16"
}
crazy node: 61.153.44.85
something is wrong or it's an attack from this node?
alt@li721-162:~$ grep "Remote peer 61.153.44.85:" ~/.BitSharesXTS/p2p.log | wc -l
1663
alt@li721-162:~$ grep "Remote peer 61.153.44.85:" ~/.BitSharesXTS/p2p.log
.....
20140703T012616.113701 th_a on_connection_closed ] Remote peer 61.153.44.85:11027 closed their connection to us node.cpp:1948
20140703T012616.899581 th_a on_connection_closed ] Remote peer 61.153.44.85:11466 closed their connection to us node.cpp:1948
20140703T012617.960703 th_a on_connection_closed ] Remote peer 61.153.44.85:12039 closed their connection to us node.cpp:1948
20140703T012619.285493 th_a on_connection_closed ] Remote peer 61.153.44.85:12814 closed their connection to us node.cpp:1948
20140703T012619.737201 th_a on_connection_closed ] Remote peer 61.153.44.85:13084 closed their connection to us node.cpp:1948
20140703T012620.312692 th_a on_connection_closed ] Remote peer 61.153.44.85:13430 closed their connection to us node.cpp:1948
20140703T012620.785433 th_a on_connection_closed ] Remote peer 61.153.44.85:13604 closed their connection to us node.cpp:1948
20140703T012621.832208 th_a on_connection_closed ] Remote peer 61.153.44.85:14092 closed their connection to us node.cpp:1948
20140703T012622.821614 th_a on_connection_closed ] Remote peer 61.153.44.85:14603 closed their connection to us node.cpp:1948
20140703T012623.706685 th_a on_connection_closed ] Remote peer 61.153.44.85:15021 closed their connection to us node.cpp:1948
20140703T012624.166869 th_a on_connection_closed ] Remote peer 61.153.44.85:15251 closed their connection to us node.cpp:1948
20140703T012624.591421 th_a on_connection_closed ] Remote peer 61.153.44.85:15474 closed their connection to us node.cpp:1948
20140703T012626.658167 th_a on_connection_closed ] Remote peer 61.153.44.85:16427 closed their connection to us node.cpp:1948
20140703T012627.115003 th_a on_connection_closed ] Remote peer 61.153.44.85:16589 closed their connection to us node.cpp:1948
.....
please send me for testing, thanks
XTS7eAKXbvDgHbuFQ8GkSpYUAsXwnGX5txNQ1ng7kfYQHVMbuZ3DX
Quote from: gyhy on July 03, 2014, 01:47:30 AM
please send me for testing, thanks
XTS7eAKXbvDgHbuFQ8GkSpYUAsXwnGX5txNQ1ng7kfYQHVMbuZ3DX
sent
Windows 7 64 bit. I've re-installed twic and wiped app data both times. When I install and try to run the client opens and then disappears. No events in event viewer. Is this to be expected for my version of windows or, am I missing something?
Some fund pls to start testing :D
XTS5rnk29FBnCfNTsVtQCXs9jEAtxQTVY4taeiGBBCJFAmqipxS8v
thanks
client stop sync blocks at 23:46:00 , here is the message when this happened.
received a block with invalid sign
20140702T234600.476280 th_a handle_message ] CLIENT: just received block d4908ed79c8cca84c26c4ef0ead903377fb20473 client.cpp:891
20140702T234600.476360 th_a on_new_block ] Received a new block from the p2p network, current head block is 6059, new block is {"previous":"fba6a332aa0b14467fd384ada0a8db9242a6f275","block_num":6060,"fee_rate":1000,"delegate_pay_rate":83292,"timestamp":"20140702T234600","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"977164c0085c8f6e4c9dedd95347f7b917abe86e","previous_secret":"1a990f6be14faf8e0b25c96accf531aae6aa2812","delegate_signature":"1f3cee95de04b6713bc2319054a6d2b79613f4245b67495f2658523c0b3c65da1a63c36cae49d0d37a3b414bd0f28e4ad0f9071cc7778b783d973d0f4ae3bc461f","user_transactions":[]}, current head block is 6059 client.cpp:801
20140702T234600.476573 th_a store_and_index ] we already know about its previous: fba6a332aa0b14467fd384ada0a8db9242a6f275 chain_database.cpp:408
20140702T234600.478033 th_a apply_transactions ] Applying transactions from block: 6060 chain_database.cpp:502
20140702T234600.480006 th_a on_new_block ] After push_block, current head block is 6060 client.cpp:817
20140702T234615.479492 th_a handle_message ] CLIENT: just received block 47d84601c497133e63b1ccac86d70bc59bcc3f85 client.cpp:891
20140702T234615.479573 th_a on_new_block ] Received a new block from the p2p network, current head block is 6060, new block is {"previous":"d4908ed79c8cca84c26c4ef0ead903377fb20473","block_num":6061,"fee_rate":1000,"delegate_pay_rate":83277,"timestamp":"20140702T234615","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"55fbf3a9fe6dd0d3aa277127d44c5b6f92c5652a","previous_secret":"bf8fc763de5712b1cc1ac761a4bc57abc8b11210","delegate_signature":"1fca2e45f2f352e7690e841bed9d5900f68748ba13151c1153a34cd529075ed746e7c1975609be8a28b0d661b22f06f9818dec028d6cdbc40407c976d3c5658f8d","user_transactions":[]}, current head block is 6060 client.cpp:801
20140702T234615.479768 th_a store_and_index ] we already know about its previous: d4908ed79c8cca84c26c4ef0ead903377fb20473 chain_database.cpp:408
20140702T234615.482675 th_a extend_chain ] error applying block: 30021 invalid_delegate_signee: invalid delegate signee
then switch fork out of control, these messages happen again and again, never switch to the main chain.
20140702T234645.494907 th_a handle_message ] CLIENT: just received block a1655804f29e7aec0c016434a2cb6c8fad7d3514 client.cpp:891
20140702T234645.494990 th_a on_new_block ] Received a new block from the p2p network, current head block is 6060, new block is {"previous":"47d84601c497133e63b1ccac86d70bc59bcc3f85","block_num":6062,"fee_rate":1000,"delegate_pay_rate":83262,"timestamp":"20140702T234645","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"7e8c09519baed6dde4fd3e338b63e06d2f725159","previous_secret":"2dd6dd72ce38d4da157cd9c553064dc3497852a0","delegate_signature":"1f4c7637ab1c2499de927c158431e9a3edc8d3c6fcdccfe8523c84e3caa9ca5cee2843831d0c5a6af43b4f2b903cd4e018fcc41055114db4df3dc6e7b230175a23","user_transactions":[]}, current head block is 6060 client.cpp:801
20140702T234645.495203 th_a store_and_index ] we already know about its previous: 47d84601c497133e63b1ccac86d70bc59bcc3f85 chain_database.cpp:408
20140702T234645.495390 th_a switch_to_fork ] switch from fork d4908ed79c8cca84c26c4ef0ead903377fb20473 to a1655804f29e7aec0c016434a2cb6c8fad7d3514 chain_database.cpp:482
20140702T234645.495428 th_a get_fork_history ] chain_database.cpp:796
20140702T234645.495463 th_a get_fork_history ] return: ["a1655804f29e7aec0c016434a2cb6c8fad7d3514","47d84601c497133e63b1ccac86d70bc59bcc3f85","d4908ed79c8cca84c26c4ef0ead903377fb20473"] chain_database.cpp:817
20140702T234645.495501 th_a switch_to_fork ] extend 47d84601c497133e63b1ccac86d70bc59bcc3f85 chain_database.cpp:492
20140702T234645.496384 th_a extend_chain ] error applying block: 30021 invalid_delegate_signee: invalid delegate signee
Quote from: gordonhucn on July 03, 2014, 02:04:48 AM
Some fund pls to start testing :D
XTS5rnk29FBnCfNTsVtQCXs9jEAtxQTVY4taeiGBBCJFAmqipxS8v
thanks
sent
Quote from: wesphily on July 03, 2014, 01:53:54 AM
Windows 7 64 bit. I've re-installed twic and wiped app data both times. When I install and try to run the client opens and then disappears. No events in event viewer. Is this to be expected for my version of windows or, am I missing something?
Also tried the following.
Run as administrator (domain and local)
Run in xp mode.
Run from program files(x86) instead of the shortcut.
Quote from: wesphily on July 03, 2014, 01:53:54 AM
Windows 7 64 bit. I've re-installed twic and wiped app data both times. When I install and try to run the client opens and then disappears. No events in event viewer. Is this to be expected for my version of windows or, am I missing something?
It should work on Windows 7. Any log files in C:\Users\USER\AppData\Roaming\BitShares XTS ?
RPC server error
any node?
Quote from: valzav on July 03, 2014, 02:22:46 AM
Quote from: wesphily on July 03, 2014, 01:53:54 AM
Windows 7 64 bit. I've re-installed twic and wiped app data both times. When I install and try to run the client opens and then disappears. No events in event viewer. Is this to be expected for my version of windows or, am I missing something?
It should work on Windows 7. Any log files in C:\Users\USER\AppData\Roaming\BitShares XTS ?
Nothing with .log. Just .dll's and an exe.
Quote from: wesphily on July 03, 2014, 02:30:11 AM
Quote from: valzav on July 03, 2014, 02:22:46 AM
Quote from: wesphily on July 03, 2014, 01:53:54 AM
Windows 7 64 bit. I've re-installed twic and wiped app data both times. When I install and try to run the client opens and then disappears. No events in event viewer. Is this to be expected for my version of windows or, am I missing something?
It should work on Windows 7. Any log files in C:\Users\USER\AppData\Roaming\BitShares XTS ?
Nothing with .log. Just .dll's and an exe.
Firewall/AV disabled. AV is ESET. Cisco web filter also disabled just in case. No host file entries. DNS pointed to ISP.
thanks a lot
Quote from: alt on July 03, 2014, 02:14:20 AM
Quote from: gordonhucn on July 03, 2014, 02:04:48 AM
Some fund pls to start testing :D
XTS5rnk29FBnCfNTsVtQCXs9jEAtxQTVY4taeiGBBCJFAmqipxS8v
thanks
sent
XTS5Qp5LSvK1eTfdQrj3mRsm46KdbHcTniq2BAZjuMYzoSYa4GBUH
for test
thanks
XTS55ufnprdAjyXR1qu5vForzPvT73wGVs8cnRHwRyKGdZjr45VWA
thanks
is anyone else having trouble getting connections on the windows gui? i'm only getting 3
+5%
Quote from: seusnow on July 03, 2014, 02:41:17 AM
XTS5Qp5LSvK1eTfdQrj3mRsm46KdbHcTniq2BAZjuMYzoSYa4GBUH
for test
thanks
send
Quote from: mhd91314 on July 03, 2014, 02:42:44 AM
XTS55ufnprdAjyXR1qu5vForzPvT73wGVs8cnRHwRyKGdZjr45VWA
thanks
send
After I registered one account, all transactions are pending. How can I return to normal?(gui client on win7)
>> wallet_account_transaction_history]
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
6684.8 2014-07-03T02:52:00 dc-aoni dc 100,000.00000 XTS 0.10000 XTS 65bba1b5
6693.13 2014-07-03T02:55:15 dc dc-aoni 3.00000 XTS 0.10000 XTS b41513b7
6697.0 2014-07-03T02:56:30 dc dc 0.00000 XTS 0.10047 XTS register dc aa9274d9
PENDING 2014-07-03T03:15:58 dc-aoni dc-delegate 50,000.00000 XTS 0.10000 XTS 25be3f2f
PENDING 2014-07-03T03:19:47 dc dc-test 1,000.00000 XTS 0.10000 XTS 4de8be23
PENDING 2014-07-03T03:22:42 dc seusnow 100.00000 XTS 0.10000 XTS 5337a152/code]
can't connect
delegate (locked) >>> getinfo
{
"blockchain_head_block_num": 6754,
"blockchain_head_block_age": "20 minutes old",
"blockchain_head_block_timestamp": "20140703T032030",
"blockchain_average_delegate_participation": 79.340141398271797,
"blockchain_blocks_left_in_round": 13,
"blockchain_confirmation_requirement": 39,
"blockchain_share_supply": 199999438180548,
"blockchain_random_seed": "65142b77d31b078764ed859f50bbdc3911e17abc",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
Quote from: cgafeng on July 03, 2014, 03:41:18 AM
can't connect
delegate (locked) >>> getinfo
{
"blockchain_head_block_num": 6754,
"blockchain_head_block_age": "20 minutes old",
"blockchain_head_block_timestamp": "20140703T032030",
"blockchain_average_delegate_participation": 79.340141398271797,
"blockchain_blocks_left_in_round": 13,
"blockchain_confirmation_requirement": 39,
"blockchain_share_supply": 199999438180548,
"blockchain_random_seed": "65142b77d31b078764ed859f50bbdc3911e17abc",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
Me too.
Quote from: heyD on July 03, 2014, 03:41:40 AM
Quote from: cgafeng on July 03, 2014, 03:41:18 AM
can't connect
delegate (locked) >>> getinfo
{
"blockchain_head_block_num": 6754,
"blockchain_head_block_age": "20 minutes old",
"blockchain_head_block_timestamp": "20140703T032030",
"blockchain_average_delegate_participation": 79.340141398271797,
"blockchain_blocks_left_in_round": 13,
"blockchain_confirmation_requirement": 39,
"blockchain_share_supply": 199999438180548,
"blockchain_random_seed": "65142b77d31b078764ed859f50bbdc3911e17abc",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
Me too.
>> get_info
{
"blockchain_head_block_num": 6747,
"blockchain_head_block_age": "29 minutes old",
"blockchain_head_block_timestamp": "20140703T031345",
"blockchain_average_delegate_participation": 78.173374613003091,
"blockchain_blocks_left_in_round": 20,
"blockchain_confirmation_requirement": 6,
"blockchain_share_supply": 199999440153712,
"blockchain_random_seed": "ee1735169e58fe4debd06865b4ea4a7519626d84",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": null,
"ntp_error": null,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "17 hours in the future",
"wallet_unlocked_until_timestamp": "20140703T201954",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
i have 1 connection
The latest code can no longer get any connections when running inside a VM.
Initializing genesis state from built-in genesis file
Please be patient, this could take a few minutes.
Successfully re-indexed 0 blocks in 0 seconds.
Not starting RPC server, use --server to enable the RPC interface
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) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "15 seconds old",
"blockchain_head_block_timestamp": "20140703T033300",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140703T033315",
"ntp_error": 0.058606999999999999,
"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
}
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "03df152999c1e9b5feacd623e1022d2e315a4d2c",
"bitshares_toolkit_revision_age": "5 hours ago",
"fc_revision": "6dbcba505b230ee77a0a7fe8af5f5e43c59b0b75",
"fc_revision_age": "6 hours ago",
"compile_date": "compiled on Jul 2 2014 at 21:08:13"
}
(wallet closed) >>>
Mind if I play! Please send some funds to register. Thanks!
XTS8iPPeWfDQLRjAh7zoXKowQzdgjcquyNZcooUjqHJYrpLHbNEYj
Looks like I'm out at block 6743. Currently 0 connects following client restart. Looks like delegate participation is dropping as well.
dr7wallet100 (unlocked) >>> get_info
{
"blockchain_head_block_num": 6743,
"blockchain_head_block_age": "42 minutes old",
"blockchain_head_block_timestamp": "20140703T031145",
"blockchain_average_delegate_participation": 75.373134328358205,
"blockchain_blocks_left_in_round": 24,
"blockchain_confirmation_requirement": 2,
"blockchain_share_supply": 199999441190396,
"blockchain_random_seed": "ebb566055bc751be7d4570cb91f4c0fd218e887f",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140703T035409",
"ntp_error": -0.067518999999999996,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "28 hours in the future",
"wallet_unlocked_until_timestamp": "20140704T074016",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
Sorry everyone I left a 5 trx/second flood test running at the office, I may have killed a few delegates... surprisingly I see no forks, only long periods without blocks getting signed. That could just mean the network is split though.
Quote from: toast on July 03, 2014, 04:50:02 AM
Sorry everyone I left a 5 trx/second flood test running at the office, I may have killed a few delegates... surprisingly I see no forks, only long periods without blocks getting signed. That could just mean the network is split though.
well，looks like flooding attack is easy.
Quote from: Webber on July 03, 2014, 04:56:05 AM
Quote from: toast on July 03, 2014, 04:50:02 AM
Sorry everyone I left a 5 trx/second flood test running at the office, I may have killed a few delegates... surprisingly I see no forks, only long periods without blocks getting signed. That could just mean the network is split though.
well，looks like flooding attack is easy.
Don't speak out..... we can keep this secret for profit once it launched ---LOL
I don't have connections anymore. What happened?
emski (unlocked) >>> info
{
"blockchain_head_block_num": 6809,
"blockchain_head_block_age": "20 seconds old",
"blockchain_head_block_timestamp": "20140703T054800",
"blockchain_average_delegate_participation": 58.449074074074076,
"blockchain_blocks_left_in_round": 59,
"blockchain_confirmation_requirement": 303,
"blockchain_share_supply": 199999420978427,
"blockchain_random_seed": "37522394a028ea99a29ed8847f9733d29c940fa3",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 1,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140703T054820",
"ntp_error": -0.001727,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "3 years 2 months in the future",
"wallet_unlocked_until_timestamp": "20170901T071004",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "85 seconds in the future",
"wallet_next_block_production_timestamp": "20140703T054945",
"wallet_version": 101
}
Quote from: toast on July 03, 2014, 04:50:02 AM
Sorry everyone I left a 5 trx/second flood test running at the office, I may have killed a few delegates... surprisingly I see no forks, only long periods without blocks getting signed. That could just mean the network is split though.
+5%
>> get_info
{
"blockchain_head_block_num": 6818,
"blockchain_head_block_age": "1 second old",
"blockchain_head_block_timestamp": "20140703T055445",
"blockchain_average_delegate_participation": 57.879656160458453,
"blockchain_blocks_left_in_round": 50,
"blockchain_confirmation_requirement": 303,
"blockchain_share_supply": 199999421356243,
"blockchain_random_seed": "56ae4030bcc37344ce4f8b2ab055696450dc0ce6",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 2,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": null,
"ntp_error": null,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "17 hours in the future",
"wallet_unlocked_until_timestamp": "20140703T222557",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
2 connections
>> blockchain_list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
6762
2cb57eaf8fd2a19e8abc910d59f25f3377bfe80f xeroc-delegate-4 35 8914 2014-07-03T03:45:30 323 YES YES
7fe2b8fa90e184d24a7ea976b7f0a1d0e6fc5a17 btsjohn 35 8805 2014-07-03T05:13:45 2021 N/A NO
Connections constantly changing in waves here the last 24 hours:
--- there are now 3 active connections to the p2p network
--- in sync with p2p network
--- there are now 4 active connections to the p2p network
--- in sync with p2p network
--- there are now 3 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- in sync with p2p network
--- there are now 3 active connections to the p2p network
--- in sync with p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- in sync with p2p network
--- there are now 2 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- in sync with p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- in sync with p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- in sync with p2p network
--- there are now 4 active connections to the p2p network
--- in sync with p2p network
--- there are now 5 active connections to the p2p network
--- in sync with p2p network
--- there are now 4 active connections to the p2p network
--- there are now 12 active connections to the p2p network
--- syncing with p2p network, 336419 blocks left to fetch
--- syncing with p2p network, 368403 blocks left to fetch
--- syncing with p2p network, 394390 blocks left to fetch
--- syncing with p2p network, 424375 blocks left to fetch
--- syncing with p2p network, 456359 blocks left to fetch
--- syncing with p2p network, 484345 blocks left to fetch
????
Quote from: clout on July 03, 2014, 03:03:51 AM
is anyone else having trouble getting connections on the windows gui? i'm only getting 3
I have no connections on windows!
and 5 on linux now...(I had 8-12 last days)
Quote from: liondani on July 03, 2014, 07:23:34 AM
Quote from: clout on July 03, 2014, 03:03:51 AM
is anyone else having trouble getting connections on the windows gui? i'm only getting 3
I have no connections on windows!
and 5 on linux now...(I had 8-12 last days)
Lost all connections on the Windows GUI some 2 hours back.
Quote from: sumantso on July 03, 2014, 07:24:22 AM
Quote from: liondani on July 03, 2014, 07:23:34 AM
Quote from: clout on July 03, 2014, 03:03:51 AM
is anyone else having trouble getting connections on the windows gui? i'm only getting 3
I have no connections on windows!
and 5 on linux now...(I had 8-12 last days)
Lost all connections on the Windows GUI some 2 hours back.
Me too. ???
Quote from: sfinder on July 02, 2014, 03:30:07 AM
Quote from: radiumlau on July 02, 2014, 03:20:13 AM
XTS6eoybjKRZun6NgxuL7UW6A5hRfcapcHGG3Ls12YDUTKGUaFsHL
Please send some funds, thx.
sent 111 xts
can someone send me some XTS for test.
account:networker
address: XTS8kMTXnSdk6PL9hobTKpEXcYZRFzmL9cXt
I closed my windows client because of no connections and restarted...
same results ("undefined network connections")...
BUT it signed flawsly in without needing to wipe "chain" directory like the last times! (maybe the problem persist only if they are connections available)
Quote from: liondani on July 03, 2014, 07:33:45 AM
I closed my windows client because of no connections and restarted...
same results ("undefined network connections")...
BUT it signed flawsly in without needing to wipe "chain" directory like the last times! (maybe the problem persist only if they are connections available)
Me too. :'(
it seems like the seed nodes went offline ...
try this:
Quote
network_add_node 114.215.104.153:8701 add
Quote from: xeroc on July 03, 2014, 07:37:44 AM
it seems like the seed nodes went offline ...
try this:
Quote
network_add_node 114.215.104.153:8701 add
syntax error?
>> network_add_node 114.215.104.153:8701 add
4 parse_error_exception: Parse Error
Can't parse a number with two decimal places
{}
bitshares json.cpp:249 fc::number_from_stream
Error parsing argument 1 of command "network_add_node": [{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]
{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]}
bitshares cli.cpp:428 bts::cli::detail::cli_impl::parse_argument_of_known_type
{"parameter_index":0}
bitshares cli.cpp:431 bts::cli::detail::cli_impl::parse_argument_of_known_type
Error parsing argument 1 of command "network_add_node": [{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}},{"context":{"level":"error","file":"cli.cpp","line":428,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]}},{"context":{"level":"warn","file":"cli.cpp","line":431,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"","data":{"parameter_index":0}}]
{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}},{"context":{"level":"error","file":"cli.cpp","line":428,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]}},{"context":{"level":"warn","file":"cli.cpp","line":431,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"","data":{"parameter_index":0}}]}
bitshares cli.cpp:343 bts::cli::detail::cli_impl::parse_recognized_interactive_command
{}
bitshares cli.cpp:350 bts::cli::detail::cli_impl::parse_recognized_interactive_command
Error parsing command "network_add_node": Parse Error(4)
Can't parse a number with two decimal places
Error parsing argument 1 of command "network_add_node": [{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]
Error parsing argument 1 of command "network_add_node": [{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}},{"context":{"level":"error","file":"cli.cpp","line":428,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]}},{"context":{"level":"warn","file":"cli.cpp","line":431,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"","data":{"parameter_index":0}}]
Usage:
network_add_node <node> <command> Attempts add or remove <node> from the peer list or try a connection to <node> once
Attempts add or remove <node> from the peer list or try a connection to <node> once
Parameters:
node (ip_endpoint, required): The node (see network_get_peer_info for nodes)
command (std::string, required): 'add' to add a node to the list, 'remove' to remove a node from the list, 'onetry' to try a connection to the node once
Returns:
void
maybe bytemaster are testing us with various attacks? :P
don't miss the quote
network_add_node "114.215.104.153:8701" add
Quote from: liondani on July 03, 2014, 07:42:20 AM
Quote from: xeroc on July 03, 2014, 07:37:44 AM
it seems like the seed nodes went offline ...
try this:
Quote
network_add_node 114.215.104.153:8701 add
syntax error?
>> network_add_node 114.215.104.153:8701 add
4 parse_error_exception: Parse Error
Can't parse a number with two decimal places
{}
bitshares json.cpp:249 fc::number_from_stream
Error parsing argument 1 of command "network_add_node": [{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]
{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]}
bitshares cli.cpp:428 bts::cli::detail::cli_impl::parse_argument_of_known_type
{"parameter_index":0}
bitshares cli.cpp:431 bts::cli::detail::cli_impl::parse_argument_of_known_type
Error parsing argument 1 of command "network_add_node": [{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}},{"context":{"level":"error","file":"cli.cpp","line":428,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]}},{"context":{"level":"warn","file":"cli.cpp","line":431,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"","data":{"parameter_index":0}}]
{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}},{"context":{"level":"error","file":"cli.cpp","line":428,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]}},{"context":{"level":"warn","file":"cli.cpp","line":431,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"","data":{"parameter_index":0}}]}
bitshares cli.cpp:343 bts::cli::detail::cli_impl::parse_recognized_interactive_command
{}
bitshares cli.cpp:350 bts::cli::detail::cli_impl::parse_recognized_interactive_command
Error parsing command "network_add_node": Parse Error(4)
Can't parse a number with two decimal places
Error parsing argument 1 of command "network_add_node": [{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]
Error parsing argument 1 of command "network_add_node": [{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}},{"context":{"level":"error","file":"cli.cpp","line":428,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"network_add_node","detail":[{"context":{"level":"error","file":"json.cpp","line":249,"method":"fc::number_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"Can't parse a number with two decimal places","data":{}}]}},{"context":{"level":"warn","file":"cli.cpp","line":431,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140703T074103.136887"},"format":"","data":{"parameter_index":0}}]
Usage:
network_add_node <node> <command> Attempts add or remove <node> from the peer list or try a connection to <node> once
Attempts add or remove <node> from the peer list or try a connection to <node> once
Parameters:
node (ip_endpoint, required): The node (see network_get_peer_info for nodes)
command (std::string, required): 'add' to add a node to the list, 'remove' to remove a node from the list, 'onetry' to try a connection to the node once
Returns:
void
Quote
network_add_node "114.215.104.153:8701" add
Quote from: alt on July 03, 2014, 07:48:45 AM
don't miss the quote
it worked now is syncing with one node "Last block is synced 35 hours old "
I will add more nodes.....
I will see them on my linux machine with "network_get_peer_info"
Quote from: sfinder on July 02, 2014, 08:27:03 PM
just wondering how you can list the assets that other than XTS. which command do you use for following list?
I think there isn't an option in the command wallet_account_transaction_history for filtering transaction of a given asset. I copied each transaction by hand in my output.
Any ideas why latest git build throws exception on get_info?
alexxy (unlocked) >>> get_info
10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
{}
th_a chain_database.cpp:1057 get_slot_signee
{"timestamp":"20140703T075730"}
th_a chain_database.cpp:1059 get_slot_signee
{}
th_a chain_database.cpp:1075 get_next_producible_block_timestamp
{}
th_a common_api_client.cpp:1971 get_info
{"command":"get_info"}
th_a cli.cpp:538 execute_command
Quote from: liondani on July 03, 2014, 07:55:38 AM
Quote from: alt on July 03, 2014, 07:48:45 AM
don't miss the quote
it worked now is syncing with one node "Last block is synced 35 hours old "
I will add more nodes.....
I will see them on my linux machine with "network_get_peer_info"
it was not necessary to add more nodes it get +4 nodes automatically ;)
connections are changing from 1 to 5 every now and then ???
Quote from: alexxy on July 03, 2014, 07:58:42 AM
Any ideas why latest git build throws exception on get_info?
alexxy (unlocked) >>> get_info
10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
{}
th_a chain_database.cpp:1057 get_slot_signee
{"timestamp":"20140703T075730"}
th_a chain_database.cpp:1059 get_slot_signee
{}
th_a chain_database.cpp:1075 get_next_producible_block_timestamp
{}
th_a common_api_client.cpp:1971 get_info
{"command":"get_info"}
th_a cli.cpp:538 execute_command
I have similar error but when I run blockchain_list_delegates (get_info is ok)
default (unlocked) >>> blockchain_list_delegates
10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
{}
th_a client.cpp:729 blockchain_list_delegates
{}
th_a common_api_client.cpp:259 blockchain_list_delegates
{"command":"blockchain_list_delegates"}
th_a cli.cpp:538 execute_command
EDIT: I solved after removing the .BitSharesXTS/chain/ directory
I noticed that max transactions is 35 every block,this is a limited?
Getting a strange error..
default (unlocked) >>> blockchain_get_account bitcoiners
10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
{}
th_a chain_database.cpp:1057 get_slot_signee
{"timestamp":"20140703T091730"}
th_a chain_database.cpp:1059 get_slot_signee
trying again..
default (unlocked) >>> blockchain_get_account bitcoiners
Name: bitcoiners
Registered: 2014-07-01T21:48:30
Last Updated: 35 hours ago
Owner Key: XTS5128THEELVyphp57Ri7zemMhdPaayWBgHGUwmGeuuG3RbGubXy
ID NAME (* next) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
------------------------------------------------------------------------------------------------------------------------
315 bitcoiners 0.0644553198 % 47 19 71.21 % 100 % 36.85315 XTS 6231
about
{
"bitshares_toolkit_revision": "03df152999c1e9b5feacd623e1022d2e315a4d2c",
"bitshares_toolkit_revision_age": "11 hours ago",
"fc_revision": "6dbcba505b230ee77a0a7fe8af5f5e43c59b0b75",
"fc_revision_age": "12 hours ago",
"compile_date": "compiled on Jul 3 2014 at 01:47:30"
}
Quote from: xeroc on July 03, 2014, 07:52:03 AM
Quote
network_add_node "114.215.104.153:8701" add
Got 1 connection, but it stays on 1 and doesn't download any blocks :(
me too :(
Quote
network_add_node "54.187.102.138:49216" add
network_add_node "191.235.210.4:1024" add
network_add_node "50.174.230.86:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "50.89.106.103:8701" add
network_add_node "95.85.33.16:8764" add
I'm so sorry everyone.:-[ :-[ :-[.I made 24261 transactions in 18 minutes aboout one hour ago.And I think bts is not work now.
Flooding attack is so cheap,We need to find some way to avoid.
mywallet (unlocked) >>> wallet_transfer 0.1 XTS webber-test1 webber-test5 test24261
wallet_transfer 0.1 XTS webber-test1 webber-test5 test24295
wallet_transfer 0.1 XTS webber-test1 webber-test5 test24296
wallet_transfer 0.1 XTS webber-test1 webber-test5 test24297
wallet_transfer 0.1 XTS BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-03T08:45:39 webber-test1 webber-test5 0.10000 XTS 0.10000 XTS test24261 9372bbcc
webber-test1 webber-test5 test24298
wallet_transfer 0.1 XTS webber-test1 webber-test5 test24299
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, our last block was created 36 hours ago
--- syncing with p2p network, 1411 blocks left to fetch
--- syncing with p2p network, our last block was created 36 hours ago
--- syncing with p2p network, our last block was created 35 hours ago
--- syncing with p2p network, our last block was created 35 hours ago
Peer 188.138.107.159:8701 disconnected us: You offered us a block that we reject as invalid
--- syncing with p2p network, our last block was created 35 hours ago
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, 3131 blocks left to fetch
--- there are now 2 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- syncing with p2p network, 2434 blocks left to fetch
Peer 188.138.107.159:8701 disconnected us: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
mywallet (unlocked) >>>
Quote from: Webber on July 03, 2014, 09:49:13 AM
I'm so sorry everyone.:-[ :-[ :-[.I made 24261 transactions in 18 minutes aboout one hour ago.And I think bts is not work now.
Flooding attack is so cheap,We need to find some way to avoid.
You are wrong .. network still active ..
Quote
default (unlocked) >>> getinfo
{
"blockchain_head_block_num": 7085,
"blockchain_head_block_age": "80 seconds old",
"blockchain_head_block_timestamp": "20140703T095015",
"blockchain_average_delegate_participation": 41.978387364921034,
"blockchain_blocks_left_in_round": 86,
"blockchain_confirmation_requirement": 303,
"blockchain_share_supply": 199999392383082,
"blockchain_random_seed": "67de4b090798dd86f594bf236bd637a9a5a615b6",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 13,
"network_num_connections_max": 64,
"network_protocol_version": 104,
"ntp_time": "20140703T095135",
"ntp_error": -0.0036280000000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "48 years ago",
"wallet_unlocked_until_timestamp": "19660102T055113",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "55 seconds in the future",
"wallet_next_block_production_timestamp": "20140703T095230",
"wallet_version": 101
}
Maybe some delegates just screwed ...
Quote from: xeroc on July 03, 2014, 09:51:55 AM
Quote from: Webber on July 03, 2014, 09:49:13 AM
I'm so sorry everyone.:-[ :-[ :-[.I made 24261 transactions in 18 minutes aboout one hour ago.And I think bts is not work now.
Flooding attack is so cheap,We need to find some way to avoid.
You are wrong .. network still active ..
Quote
default (unlocked) >>> getinfo
{
"blockchain_head_block_num": 7085,
"blockchain_head_block_age": "80 seconds old",
"blockchain_head_block_timestamp": "20140703T095015",
"blockchain_average_delegate_participation": 41.978387364921034,
"blockchain_blocks_left_in_round": 86,
"blockchain_confirmation_requirement": 303,
"blockchain_share_supply": 199999392383082,
"blockchain_random_seed": "67de4b090798dd86f594bf236bd637a9a5a615b6",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 13,
"network_num_connections_max": 64,
"network_protocol_version": 104,
"ntp_time": "20140703T095135",
"ntp_error": -0.0036280000000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "48 years ago",
"wallet_unlocked_until_timestamp": "19660102T055113",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "55 seconds in the future",
"wallet_next_block_production_timestamp": "20140703T095230",
"wallet_version": 101
}
Maybe some delegates just screwed ...
maybe,but must be something wrong.
> blockchain_get_pending_transactions
gives an 'aweful' long list of transactions!
Quote from: liondani on July 03, 2014, 07:23:34 AM
Quote from: clout on July 03, 2014, 03:03:51 AM
is anyone else having trouble getting connections on the windows gui? i'm only getting 3
I have no connections on windows!
and 5 on linux now...(I had 8-12 last days)
I checked now and my linux delegate "liondani-linux"
missed over night-morning (04.00-10.00 eet Greece) 7 blocks
so I assume even on linux it was due all connections was lost for some hours....
Seems like the last tx was in block 7124 .. no tx pending any longer
no idea what happend to all the other delegates though :(
Quote from: xeroc on July 03, 2014, 11:22:27 AM
Seems like the last tx was in block 7124 .. no tx pending any longer
no idea what happend to all the other delegates though :(
I don't have any connection anymore even after adding the nodes you provided.
still have 2 network connections on win7....
6 on linux but (has changed a lot times from 3 to 6 connections)
Quote from: liondani on July 03, 2014, 11:35:13 AM
still have 2 network connections on win7....
6 on linux but (has changed a lot times from 3 to 6 connections)
network_set_advanced_node_parameters {"desired_number_of_connections":40 "maximum_number_of_connections":64}
Take on of these .. or all of them
Quote from: xeroc on July 03, 2014, 09:46:54 AM
Quote
network_add_node "54.187.102.138:49216" add
network_add_node "191.235.210.4:1024" add
network_add_node "50.174.230.86:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "50.89.106.103:8701" add
network_add_node "95.85.33.16:8764" add
Quote from: xeroc on July 03, 2014, 11:42:09 AM
Take on of these .. or all of them
Quote from: xeroc on July 03, 2014, 09:46:54 AM
Quote
network_add_node "54.187.102.138:49216" add
network_add_node "191.235.210.4:1024" add
network_add_node "50.174.230.86:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "50.89.106.103:8701" add
network_add_node "95.85.33.16:8764" add
thanks added all nodes
now
7 connections linux
3 connections win7
only 1 added on each...
(http://1.bp.blogspot.com/-Cz2PXiR-F6I/U7VDm17TP7I/AAAAAAAAC9k/kk0196jbT-8/s1600/Screenshot+2014-07-03+14.47.32.png)
(http://farm7.staticflickr.com/6139/6015681608_9cd84ac843_z.jpg)
Quote from: liondani on July 03, 2014, 11:55:05 AM
(http://1.bp.blogspot.com/-Cz2PXiR-F6I/U7VDm17TP7I/AAAAAAAAC9k/kk0196jbT-8/s1600/Screenshot+2014-07-03+14.47.32.png)
Bam .. How could I miss that :)
BTW. for stronger connectivity use:
Quote
network_set_advanced_node_parameters {"desired_number_of_connections":40 "maximum_number_of_connections":64}
started having problems, so I built from master, clean home dir, and now I get this:
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "b6aa9950db53ecc9753f7c4cbf2a00a3b6dff800",
"bitshares_toolkit_revision_age": "50 minutes ago",
"fc_revision": "6dbcba505b230ee77a0a7fe8af5f5e43c59b0b75",
"fc_revision_age": "16 hours ago",
"compile_date": "compiled on Jul 3 2014 at 14:41:17"
}
(wallet closed) >>> get_info
6 key_not_found_exception: Key Not Found
{"key":31757}
th_a cached_level_map.hpp:51 fetch
{"key":31757}
th_a cached_level_map.hpp:52 fetch
{"block_num":31757}
th_a chain_database.cpp:1116 get_block_id
{"block_num":31757}
th_a chain_database.cpp:1101 get_block_header
{}
th_a common_api_client.cpp:1971 get_info
{"command":"get_info"}
th_a cli.cpp:538 execute_command
I go to bed for a few lousy hours and you all let the blockchain die. What am I going to do with you?
I am trying to figure out what happened and I think we killed it with a series of unfortunate events:
1) Webber flooded us at 22 trx per second which was probably triggered a ton of forks
2) I upgraded the database in an attempt to improve processing speed, this upgrade was probably ill-advised as it looks like it broke everyone who upgraded.
So what do we do now? We use this as a dry run on how to handle massive chain disruption. Our mission is to get delegate participation back up to 90% or more.
We are now preparing a series of significant enhancements to address the flooding issue:
1) Every client will limit the number of pending transactions it will store. This will delay propagation of transactions until the blockchain can process them. In the event the network is saturated you can still broadcast additional transactions at exponential increases in the required fee.
2) The database bug exposed a bug in network syncing, so we are adding extra validation checks on messages we receive from peers
3) We have implemented rotating logs with compression which should help limit the impact of our verbose test logs.
4) Fixed a bug with importing old BTS wallets which was keeping some of my delegates off line
5) Roll back my database updates.
Once these changes are committed then we will let everyone know and try to recover the test network.
Quote from: bytemaster on July 03, 2014, 01:49:28 PM
I go to bed for a few lousy hours and you all let the blockchain die. What am I going to do with you?
Sorry :) luckly we have people in the testnet flooding like hell :)
And for those who are following the parallels between the test chains and back to the future... this is where I am now..
https://www.youtube.com/watch?v=jFuKfTjR2q4#t=99
I am looking for more peers. Currently I have only the following 4:
network_add_node "146.185.186.245:48628" add
network_add_node "107.170.30.182:8701" add
network_add_node "106.187.91.24:8701" add
network_add_node "188.138.107.159:56497" add
It is my understanding that 5 peers are required to produce a block. My slot is upcoming in less than 10 minutes. Anyone have some active peers I may add?
Thanks,
Fox
Quote from: bytemaster on July 03, 2014, 02:07:50 PM
And for those who are following the parallels between the test chains and back to the future... this is where I am now..
https://www.youtube.com/watch?v=jFuKfTjR2q4#t=99
If you don't want to see that all go to 2:05 ...
And you will get the picture :P
Quote from: Fox on July 03, 2014, 02:22:02 PM
I am looking for more peers. Currently I have only the following 4:
network_add_node "146.185.186.245:48628" add
network_add_node "107.170.30.182:8701" add
network_add_node "106.187.91.24:8701" add
network_add_node "188.138.107.159:56497" add
It is my understanding that 5 peers are required to produce a block. My slot is upcoming in less than 10 minutes. Anyone have some active peers I may add?
Thanks,
Fox
network_add_node "106.187.91.24:8701" add
network_add_node "114.215.104.153:8701" add
network_add_node "146.185.186.245:8701" add
network_add_node "84.238.140.192:8701" add
network_add_node "188.138.107.159:8701" add
network_add_node "107.170.172.14:46952" add
network_add_node "128.199.180.19:55430" add
hope that help's
Also:
Quote
network_set_advanced_node_parameters {"desired_number_of_connections":40 "maximum_number_of_connections":65}
Quote from: liondani on July 03, 2014, 02:29:15 PM
hope that help's
I added your list. However (unlikely as a result), now down to the following 3:
network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
First of all thanks for you funds.
One issue that today I just got one connection. Is it a problem? Are you normal, guys?
Quote from: cass on July 02, 2014, 10:15:02 PM
Quote from: suwoder on July 02, 2014, 09:57:36 PM
send me some XTS please, Thanks.
XTS7rhnNyCyjwBNnDtqRPkUEEC7kbycrDFdxHfD76cozHcV17KCLY
sent
Quote from: bennyliaa on July 03, 2014, 03:25:33 PM
First of all thanks for you funds.
One issue that today I just got one connection. Is it a problem? Are you normal, guys?
Quote from: cass on July 02, 2014, 10:15:02 PM
Quote from: suwoder on July 02, 2014, 09:57:36 PM
send me some XTS please, Thanks.
XTS7rhnNyCyjwBNnDtqRPkUEEC7kbycrDFdxHfD76cozHcV17KCLY
sent
I haven't even managed to fully sync once yet :D
I'm now producing blocks. Good news!
],[
7432,{
"missed": false,
"id": "29a4765219d6808f4a6010b180ec0070d239fff7"
}
],[
7485,{
"missed": false,
"id": "4abd2ae19253212a89238f43dd8dec071649ea8c"
}
Please add me as an approved delegate:
wallet_approve_delegate fox-delegate-98
Quote from: Fox on July 03, 2014, 03:37:09 PM
I'm now producing blocks. Good news!
],[
7432,{
"missed": false,
"id": "29a4765219d6808f4a6010b180ec0070d239fff7"
}
],[
7485,{
"missed": false,
"id": "4abd2ae19253212a89238f43dd8dec071649ea8c"
}
Please add me as an approved delegate:
wallet_approve_delegate fox-delegate-98
>> wallet_approve_delegate fox-delegate-98
OK
OK, rescanned the blockchain and reset delegate block production. Everything is working perfectly now.
The weird thing is that some people sent us XTS yesterday but it didn't show up in the account. Even the XTS we send to ourselves didn't show up in our wallet balance before rescanning. See the below screenshot:
http://i.imgur.com/zmzSwrq.jpg
Furthermore, before rescanning we nonetheless processed 1 block as a delegate, even though according to our own blockchain read we had insufficient votes.
Any feedback?
Quote from: itnom on July 03, 2014, 03:47:03 PM
OK, rescanned the blockchain and reset delegate block production. Everything is working perfectly now.
The weird thing is that some people sent us XTS yesterday but it didn't show up in the account. Even the XTS we send to ourselves didn't show up in our wallet balance before rescanning. See the below screenshot:
http://i.imgur.com/zmzSwrq.jpg
If you had delegates enabled it won't scan new transactions. That's why it appeared you disabled and rescanned.
Quote
Furthermore, before rescanning we nonetheless processed 1 block as a delegate, even though according to our own blockchain read we had insufficient votes.
Any feedback?
Maybe you got into a round and then dropped back out?
Quote from: liondani on July 03, 2014, 03:44:55 PM
Quote from: Fox on July 03, 2014, 03:37:09 PM
I'm now producing blocks. Good news!
],[
7432,{
"missed": false,
"id": "29a4765219d6808f4a6010b180ec0070d239fff7"
}
],[
7485,{
"missed": false,
"id": "4abd2ae19253212a89238f43dd8dec071649ea8c"
}
Please add me as an approved delegate:
wallet_approve_delegate fox-delegate-98
>> wallet_approve_delegate fox-delegate-98
OK
liondani, take your delegates off, you havent produced a single block
Quote from: clout on July 03, 2014, 04:10:32 PM
liondani, take your delegates off, you havent produced a single block
that means I am on a fork?
delegates off do you mean:
wallet_enable_delegate_block_production liondani false
or delete chain directories and rebuild toolkit ?
PS sorry for my stupid question :-[
Quote from: liondani on July 03, 2014, 04:17:47 PM
Quote from: clout on July 03, 2014, 04:10:32 PM
liondani, take your delegates off, you havent produced a single block
that means I am on a fork?
delegates off do you mean:
wallet_enable_delegate_block_production liondani false
or delete chain directories and rebuild toolkit ?
PS sorry for my stupid question :-[
Are your delegates even enabled? I doubt you are on a fork.
do "wallet_list_my_accounts"
if they say "NO" for block production enabled do:
"wallet_delegate_set_block_production ALL true"
and make sure wallet is unlocked
Quote from: toast on July 03, 2014, 04:22:09 PM
Quote from: liondani on July 03, 2014, 04:17:47 PM
Quote from: clout on July 03, 2014, 04:10:32 PM
liondani, take your delegates off, you havent produced a single block
that means I am on a fork?
delegates off do you mean:
wallet_enable_delegate_block_production liondani false
or delete chain directories and rebuild toolkit ?
PS sorry for my stupid question :-[
Are your delegates even enabled? I doubt you are on a fork.
do "wallet_list_my_accounts"
if they say "NO" for block production enabled do:
"wallet_delegate_set_block_production ALL true"
On my linux system (Mint 17)
liondani (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVED BLOCK PRODUCTION ENABLED
liondani * XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv 2014-07-01T22:37:45 NO 1 YES
liondani-linux * XTS7kn3gC9d6iKeFxieMj2Sf5PSLuerYZZFzGBQC7Ktu2p1dsyGGE 2014-07-02T00:26:15 NO 1 YES
liondaniel XTS6d5fuzezqyaBqzSJY6ityNWV59nGxoaf3ydHLPhFZQGKpuSfhP NO NO 0 N/A
On my win7 system
YES the where ALL NOT ENABLED
I fixed that , many thanks!
One question. I was sur I had them enabled....
Is it possible they switch off automatically when directory "chain" is deleted or for other reasons? (forks etc.)
Quote from: toast on July 03, 2014, 04:06:34 PM
If you had delegates enabled it won't scan new transactions. That's why it appeared you disabled and rescanned.
Ok makes sense now!
can someone please explain this voting thing. i approved of vikram's delegates. i want to disapprove them but when i make transactions there approval stays. I also want to add approval to my own delegates but they currently have a fraction of my approval. from what i think i know each transaction votes for three delegates. is there a way that i can make transaction that votes or unvotes for more than that?
Quote
Quote from: clout on July 03, 2014, 04:47:08 PM
can someone please explain this voting thing. i approved of vikram's delegates. i want to disapprove them but when i make transactions there approval stays. I also want to add approval to my own delegates but they currently have a fraction of my approval. from what i think i know each transaction votes for three delegates. is there a way that i can make transaction that votes or unvotes for more than that?
This answer from bytemaster a few post back maybe will partially help...
Quote
Quote from: bytemaster on July 02, 2014, 07:10:08 PM
Quote from: Fox on July 02, 2014, 07:02:45 PM
QuoteQuote from: liondani on Today at 06:44:14 PM
How do you explain that my best delegates "liondani" (27 produced 1 missed) is in the stand by list and 4 of my worst delegates that have 0 produced and about 2-3 missed are on the top delegates?(liondani-delegate-1, -3, -4, -8)
PS only liondani-delegate-1 has funds
QuoteThere is no auto-voting right now. Unless someone has given you an approval vote and then made transactions to that effect it will not change your ranking.
Is the delegate ranking based on the amount of funds transmitted by wallet(s) with wallet_approve_delegate <delegate(s)> in each round, in total, other? Perhaps you could direct me to some reference material pm the subject.
Thanks,
Fox
It isn't based on transaction volume, but instead every balance is voting for N delegates. When you transfer funds you update the balance and the votes.
PS Actually I believe if "auto-voting" was enabled we would not had the lasts problems (not so hard at least)
Because right now many delegates that was disconnected where on the top 101 only because of trust improvement (they where disconnected for a reason and that's why many of them would get is standby mode after some autovotes when they started to miss blocks.... (or am I missing something!
Quote from: bytemaster on July 01, 2014, 10:20:27 PM
Sent
Not Working
(http://s12.postimg.org/cw8ixemjd/Untitled.jpg) (http://postimg.org/image/cw8ixemjd/)
when i close the program. it crashes!
Maybe a simple tut for non-programmers?
--- syncing with p2p network, 10764 blocks left to fetch
Peer 59.54.114.187:53545 disconnected us: You offered us a block that we reject as invalid
--- syncing with p2p network, 16761 blocks left to fetch
--- there are now 23 active connections to the p2p network
What is "16761 blocks left to fetch" standing for?
Why is that number constantly increasing ?
--- syncing with p2p network, 86726 blocks left to fetch
--- there are now 25 active connections to the p2p network
Quote from: emski on July 03, 2014, 05:49:32 PM
--- syncing with p2p network, 10764 blocks left to fetch
Peer 59.54.114.187:53545 disconnected us: You offered us a block that we reject as invalid
--- syncing with p2p network, 16761 blocks left to fetch
--- there are now 23 active connections to the p2p network
What is "16761 blocks left to fetch" standing for?
Why is that number constantly increasing ?
--- syncing with p2p network, 86726 blocks left to fetch
--- there are now 25 active connections to the p2p network
That's a bug, you can restart and it'll go away
Quote from: toast on July 03, 2014, 05:51:31 PM
Quote from: emski on July 03, 2014, 05:49:32 PM
--- syncing with p2p network, 10764 blocks left to fetch
Peer 59.54.114.187:53545 disconnected us: You offered us a block that we reject as invalid
--- syncing with p2p network, 16761 blocks left to fetch
--- there are now 23 active connections to the p2p network
What is "16761 blocks left to fetch" standing for?
Why is that number constantly increasing ?
--- syncing with p2p network, 86726 blocks left to fetch
--- there are now 25 active connections to the p2p network
That's a bug, you can restart and it'll go away
I just restarted...
This is 50 secs after starting the client.
Should I wipe datadir?
Quote from: emski on July 03, 2014, 05:53:04 PM
Quote from: toast on July 03, 2014, 05:51:31 PM
Quote from: emski on July 03, 2014, 05:49:32 PM
--- syncing with p2p network, 10764 blocks left to fetch
Peer 59.54.114.187:53545 disconnected us: You offered us a block that we reject as invalid
--- syncing with p2p network, 16761 blocks left to fetch
--- there are now 23 active connections to the p2p network
What is "16761 blocks left to fetch" standing for?
Why is that number constantly increasing ?
--- syncing with p2p network, 86726 blocks left to fetch
--- there are now 25 active connections to the p2p network
That's a bug, you can restart and it'll go away
I just restarted...
This is 50 secs after starting the client.
Should I wipe datadir?
Weird... wiping shouldn't change anything. But also it's not a critical bug I think, doesn't affect anything
I haven't had a chance to read all 22 pages. What happened to the network last night. Seems like my delegate node forked, and now on a rebuild I am having a hard time rebuilding the chain. I've gotten stuck around block 2700 a few times now. Looks like I am past it now (haven't unlocked my wallet)
"blockchain_average_delegate_participation": 28.973034997131382,
And it looks like I am not the only one having difficulties?
Quote from: puppies on July 03, 2014, 05:55:36 PM
I haven't had a chance to read all 22 pages. What happened to the network last night. Seems like my delegate node forked, and now on a rebuild I am having a hard time rebuilding the chain. I've gotten stuck around block 2700 a few times now. Looks like I am past it now (haven't unlocked my wallet)
"blockchain_average_delegate_participation": 28.973034997131382,
And it looks like I am not the only one having difficulties?
Everything looked nice at first... until people started using/stressing/testing it.
Quote from: puppies on July 03, 2014, 05:55:36 PM
I haven't had a chance to read all 22 pages. What happened to the network last night. Seems like my delegate node forked, and now on a rebuild I am having a hard time rebuilding the chain. I've gotten stuck around block 2700 a few times now. Looks like I am past it now (haven't unlocked my wallet)
"blockchain_average_delegate_participation": 28.973034997131382,
And it looks like I am not the only one having difficulties?
Several people did massive flood tests, and Dan checked in a bad DB change which prevented syncing. So lots of delegates got knocked off.
The good news is that we seem to have recovered, in the sense that there is one longest chain and most delegates are on it. Participation is on the rise as more people build the latest / vote in new delegates.
I'm currently seeing the greatest number of peer connections ( 8 ) in 13 hours for my client. Here are the most resent peers that I have successfully connected to in the past two hours:
network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
network_add_node "106.185.26.162:8761" add
network_add_node "107.170.30.182:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "107.170.170.214:48387" add
network_add_node "95.85.33.16:8764" add
network_add_node "84.238.140.192:8701" add
network_add_node "176.9.234.166:8701" add
It may be helpful to increase the number of peer connections to your client:
network_set_advanced_node_parameters {"desired_number_of_connections":40 "maximum_number_of_connections":64}
Let's increase delegate participation. Please approve my actively block creating delegate:
wallet_enable_delegate_block_production fox-delegate-98 true
wtb xts!
XTS5wChfoa3ZgMus8xUnDFgVmN4ix5dRJkovt8ahhuCozZDGQC8Zi
Our approval rating and produced blocks is increasing however our missed blocks is increasing also? Anyone knows if that is normal?
How do you keep the wallet open in the Windows GUI?
Quote from: sumantso on July 03, 2014, 07:12:13 PM
How do you keep the wallet open in the Windows GUI?
Not working in most recent GUI binary. Maybe fixed on github? not sure
Quote from: toast on July 03, 2014, 07:15:20 PM
Quote from: sumantso on July 03, 2014, 07:12:13 PM
How do you keep the wallet open in the Windows GUI?
Not working in most recent GUI binary. Maybe fixed on github? not sure
Never managed to fully sync once either; always gets stuck around 3k blocks :( Any idea why?
Quote from: sumantso on July 03, 2014, 07:18:50 PM
Quote from: toast on July 03, 2014, 07:15:20 PM
Quote from: sumantso on July 03, 2014, 07:12:13 PM
How do you keep the wallet open in the Windows GUI?
Not working in most recent GUI binary. Maybe fixed on github? not sure
Never managed to fully sync once either; always gets stuck around 3k blocks :( Any idea why?
list_errors
Quote from: bytemaster on July 03, 2014, 07:34:33 PM
Quote from: sumantso on July 03, 2014, 07:18:50 PM
Quote from: toast on July 03, 2014, 07:15:20 PM
Quote from: sumantso on July 03, 2014, 07:12:13 PM
How do you keep the wallet open in the Windows GUI?
Not working in most recent GUI binary. Maybe fixed on github? not sure
Never managed to fully sync once either; always gets stuck around 3k blocks :( Any idea why?
list_errors
Stuck again at 3050
list_error
Quote20140703T193132.806858 (15 minutes ago )
31004 unknown_balance_record: unknown balance record
{"balance_id":"XTSK1bz4Y8ts9Er5Cbpuo8L6zGZmXYMeLE9W"}
bitshares balance_operations.cpp:80 bts::blockchain::withdraw_operation::evaluate
{"*this":{"balance_id":"XTSK1bz4Y8ts9Er5Cbpuo8L6zGZmXYMeLE9W","amount":10000,"claim_input_data":""}}
bitshares balance_operations.cpp:170 bts::blockchain::withdraw_operation::evaluate
{"op":{"type":"withdraw_op_type","data":{"balance_id":"XTSK1bz4Y8ts9Er5Cbpuo8L6zGZmXYMeLE9W","amount":10000,"claim_input_data":""}}}
bitshares operation_factory.hpp:51 bts::blockchain::operation_factory::operation_converter<struct bts::blockchain::withdraw_operation>::evaluate
{"trx":{"expiration":"20140702T054403","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSK1bz4Y8ts9Er5Cbpuo8L6zGZmXYMeLE9W","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSA4zqdwCupV5zeR7PgQYUizYueMcQZS3tA","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTS7TpjmH6ucfUxs95KjTzQnMpQQtwc7jgWV","memo":{"one_time_key":"XTS5bq6fi1nc37kJDdk56YDjH2wjSFFLmVGmYGvxWRU66EB6Y5E62","encrypted_memo_data":"720c8c884dac7c77804c799a6f0360dd09cf3a26b73d9dcedc2e185633681624ae61d44e7f6ff7c72e64e40824540322cf0b9a1ada45d2aa565162a636bc8d01"}}}}}],"signatures":["2036a680e78725edcff3c950d2beaacb1ff569bb16245656e0a2bc0c94e83fbeaba4f51344949de77b119971907cfab774f14cb7e2ef41c0d210e77445b12b9fdf","1f39e8a603c9c5cf697c3d0a0fd77ab9eab1f0a3be8baccf52d8e3b3f66255b7ac586e9bce583f4d502d7dcd8c7bf5ad5013b22413882cf8cd486ead05a2c7b81f"]}}
bitshares transaction_evaluation_state.cpp:158 bts::blockchain::transaction_evaluation_state::evaluate
{"trx_num":19}
bitshares chain_database.cpp:531 bts::blockchain::detail::chain_database_impl::apply_transactions
...
..
Theres a lot more after this.
EDIT: Should I delete my wallet also? I was keeping the wallet only everytime and deleting the rest.
Anyone able to send me some XTS please?
XTS5UMgDNLkJKpevFxFpK74L72ZrDA1p4HFY444jVt8ok85wKnznz
seems no one knows how to help me or should i take couple of years to learn programming?
Quote from: bytemaster on July 03, 2014, 07:34:33 PM
Quote from: sumantso on July 03, 2014, 07:18:50 PM
Quote from: toast on July 03, 2014, 07:15:20 PM
Quote from: sumantso on July 03, 2014, 07:12:13 PM
How do you keep the wallet open in the Windows GUI?
Not working in most recent GUI binary. Maybe fixed on github? not sure
Never managed to fully sync once either; always gets stuck around 3k blocks :( Any idea why?
list_errors
Quote from: sumantso on July 03, 2014, 07:47:14 PM
Quote from: bytemaster on July 03, 2014, 07:34:33 PM
Quote from: sumantso on July 03, 2014, 07:18:50 PM
Quote from: toast on July 03, 2014, 07:15:20 PM
Quote from: sumantso on July 03, 2014, 07:12:13 PM
How do you keep the wallet open in the Windows GUI?
Not working in most recent GUI binary. Maybe fixed on github? not sure
Never managed to fully sync once either; always gets stuck around 3k blocks :( Any idea why?
list_errors
Stuck again at 3050
list_error
Quote20140703T193132.806858 (15 minutes ago )
31004 unknown_balance_record: unknown balance record
{"balance_id":"XTSK1bz4Y8ts9Er5Cbpuo8L6zGZmXYMeLE9W"}
bitshares balance_operations.cpp:80 bts::blockchain::withdraw_operation::evaluate
{"*this":{"balance_id":"XTSK1bz4Y8ts9Er5Cbpuo8L6zGZmXYMeLE9W","amount":10000,"claim_input_data":""}}
bitshares balance_operations.cpp:170 bts::blockchain::withdraw_operation::evaluate
{"op":{"type":"withdraw_op_type","data":{"balance_id":"XTSK1bz4Y8ts9Er5Cbpuo8L6zGZmXYMeLE9W","amount":10000,"claim_input_data":""}}}
bitshares operation_factory.hpp:51 bts::blockchain::operation_factory::operation_converter<struct bts::blockchain::withdraw_operation>::evaluate
{"trx":{"expiration":"20140702T054403","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSK1bz4Y8ts9Er5Cbpuo8L6zGZmXYMeLE9W","amount":10000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSA4zqdwCupV5zeR7PgQYUizYueMcQZS3tA","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTS7TpjmH6ucfUxs95KjTzQnMpQQtwc7jgWV","memo":{"one_time_key":"XTS5bq6fi1nc37kJDdk56YDjH2wjSFFLmVGmYGvxWRU66EB6Y5E62","encrypted_memo_data":"720c8c884dac7c77804c799a6f0360dd09cf3a26b73d9dcedc2e185633681624ae61d44e7f6ff7c72e64e40824540322cf0b9a1ada45d2aa565162a636bc8d01"}}}}}],"signatures":["2036a680e78725edcff3c950d2beaacb1ff569bb16245656e0a2bc0c94e83fbeaba4f51344949de77b119971907cfab774f14cb7e2ef41c0d210e77445b12b9fdf","1f39e8a603c9c5cf697c3d0a0fd77ab9eab1f0a3be8baccf52d8e3b3f66255b7ac586e9bce583f4d502d7dcd8c7bf5ad5013b22413882cf8cd486ead05a2c7b81f"]}}
bitshares transaction_evaluation_state.cpp:158 bts::blockchain::transaction_evaluation_state::evaluate
{"trx_num":19}
bitshares chain_database.cpp:531 bts::blockchain::detail::chain_database_impl::apply_transactions
...
..
Theres a lot more after this.
Can you let me know your revision, it looks like you may have the DB bug.
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "1a8aa36482ce046570e643886ef0842ed66f041b",
"bitshares_toolkit_revision_age": "69 minutes ago",
"fc_revision": "c020913cb8928d767fc9849b58b8c817b2577a7f",
"fc_revision_age": "6 hours ago",
"compile_date": "compiled on Jul 3 2014 at 11:23:46"
}
>> about
{
"bitshares_toolkit_revision": "507cb6cb21ad74d3b92eb447bf3e051f31804aed",
"bitshares_toolkit_revision_age": "45 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "48 hours ago",
"compile_date": "compiled on Jul 1 2014 at 19:58:21"
}
I have been using the GUI I installed yesterday in Win 7 32 bit.
"chinese", "sexy", and "pan2pan" are all stuck on a fork... we're chugging along without you!
Quote from: svk on July 03, 2014, 07:47:26 PM
Anyone able to send me some XTS please?
XTS5UMgDNLkJKpevFxFpK74L72ZrDA1p4HFY444jVt8ok85wKnznz
sent you some play money.
Quote from: bitcoinerS on July 03, 2014, 08:23:58 PM
Quote from: svk on July 03, 2014, 07:47:26 PM
Anyone able to send me some XTS please?
XTS5UMgDNLkJKpevFxFpK74L72ZrDA1p4HFY444jVt8ok85wKnznz
sent you some play money.
Cheers, well received, approved you as delegate.
I've set up a delegate too: please approve svk-delegate!
Quote from: svk on July 03, 2014, 08:33:20 PM
Quote from: bitcoinerS on July 03, 2014, 08:23:58 PM
Quote from: svk on July 03, 2014, 07:47:26 PM
Anyone able to send me some XTS please?
XTS5UMgDNLkJKpevFxFpK74L72ZrDA1p4HFY444jVt8ok85wKnznz
sent you some play money.
Cheers, well received, approved you as delegate.
I've set up a delegate too: please approve svk-delegate!
Ok, will do. Thanks.
In the interest of increasing our delegate participation level closer to Bytemaster's goal of 90%, I suggest we vote out current delegates not producing blocks, thereby allowing in new delegates able to produce blocks consistently. It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).
There are two delegate names that stick out:
init* (4 delegates this round)
vikram* (13 delegates this round)
Please take a moment to remove them from your approved list:
wallet_approve_delegate init3 false
wallet_approve_delegate vikram false
Quote from: Fox on July 03, 2014, 08:46:52 PM
It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).
That's all in the client though, and hardly anyone is online.
But yes everyone please check your votes.
Quote from: Fox on July 03, 2014, 08:46:52 PM
In the interest of increasing our delegate participation level closer to Bytemaster's goal of 90%, I suggest we vote out current delegates not producing blocks, thereby allowing in new delegates able to produce blocks consistently. It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).
There are two delegate names that stick out:
init* (4 delegates this round)
vikram* (13 delegates this round)
Please take a moment to remove them from your approved list:
wallet_approve_delegate init3 false
wallet_approve_delegate vikram false
Those are all one guy and I know where he is sitting... init12+ is the seed node, init<12 is vikram.... I'll get on his case :)
Quote
Those are all one guy and I know where he is sitting... init12+ is the seed node, init<12 is vikram.... I'll get on his case :)
Not intending to point a finger. Together we all make this a success. :)
Respectfully,
Fox
Quote from: Fox on July 03, 2014, 09:03:37 PM
Quote
Those are all one guy and I know where he is sitting... init12+ is the seed node, init<12 is vikram.... I'll get on his case :)
Not intending to point a finger. Together we all make this a success. :)
Respectfully,
Fox
+1 Agreed... he was heads down working on code ignoring his delegates :)
We have checked in some updates that will significantly reduce the ability of anyone to spam the network and resolved many smaller issues.
If you have not updated recently it might be a good idea, then we can try another massive flood of 100 trx per second and see how things behave.
I have just pushed some updates to the new log rotation: https://github.com/InvictusInnovations/fc/pull/34
I believe the old code may have been causing some problems.
Please pull and build the latest bitshares_toolkit and and fc code, and delete all the log files and config.json from your data directory, then start the client.
Quote from: vikram on July 03, 2014, 11:18:56 PM
I have just pushed some updates to the new log rotation: https://github.com/InvictusInnovations/fc/pull/34
I believe the old code may have been causing some problems.
Please pull and build the latest bitshares_toolkit and and fc code, and delete all the log files and config.json from your data directory, then start the client.
one of my client can't connect to network, disconnect from every node with same error message:
20140703T234435.698552 th_a terminate_inactive_c ] Disconnecting peer 106.185.26.162:8761 because they didn't respond to my request for sync item 19af68ebd504e1 fbd41d3b98532772b709412fd0 node.cpp:872
We fucked up! All the seed nodes are dead and not coming back.
Working on building new default seeds into the client soon now.
What a convenient opportunity to ask for seed nodes for the Real Thing (wink wink nudge). Please send an IP if you want to be a seed.
In the meantime if you want to connect to the network for the first time:
network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
network_add_node "106.185.26.162:8761" add
network_add_node "107.170.30.182:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "107.170.170.214:48387" add
network_add_node "95.85.33.16:8764" add
network_add_node "84.238.140.192:8701" add
network_add_node "176.9.234.166:8701" add
network_add_node "162.243.219.145:8701" add
Quote from: toast on July 03, 2014, 11:55:02 PM
In the meantime if you want to connect to the network for the first time:
network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
network_add_node "106.185.26.162:8761" add
network_add_node "107.170.30.182:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "107.170.170.214:48387" add
network_add_node "95.85.33.16:8764" add
network_add_node "84.238.140.192:8701" add
network_add_node "176.9.234.166:8701" add
network_add_node "162.243.219.145:8701" add
Edit:
Works now after wiping the data dir but the sync is very slow with 1000+ for about half an hour.
End of edit.
Didn't work for me with the latest code.
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "9ed7cd7ce32914af1cb5055140f30f51351ec1d7",
"bitshares_toolkit_revision_age": "78 minutes ago",
"fc_revision": "0fced2ddffb380572ed50c181e8496a9d8777a62",
"fc_revision_age": "80 minutes ago",
"compile_date": "compiled on Jul 4 2014 at 07:41:33"
}
(wallet closed) >>> network_add_node "188.138.107.159:56497" add
OK
(wallet closed) >>> network_add_node "146.185.186.245:8701" add
OK
(wallet closed) >>> network_add_node "106.185.26.162:8761" add
OK
(wallet closed) >>> network_add_node "107.170.30.182:8701" add
OK
(wallet closed) >>> network_add_node "107.170.172.14:8701" add
OK
(wallet closed) >>> network_add_node "162.243.219.145:8701" add
OK
(wallet closed) >>> network_add_node "107.170.170.214:48387" add
OK
(wallet closed) >>> network_add_node "95.85.33.16:8764" add
OK
(wallet closed) >>> network_add_node "84.238.140.192:8701" add
OK
(wallet closed) >>> network_add_node "176.9.234.166:8701" add
OK
(wallet closed) >>>
(wallet closed) >>> network_add_node "162.243.219.145:8701" add
OK
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- syncing with p2p network, 8797 blocks left to fetch
--- there are now 5 active connections to the p2p network
--- there are now 4 active connections to the p2p network
Quote from: Fox on July 03, 2014, 08:46:52 PM
In the interest of increasing our delegate participation level closer to Bytemaster's goal of 90%, I suggest we vote out current delegates not producing blocks, thereby allowing in new delegates able to produce blocks consistently. It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).
There are two delegate names that stick out:
init* (4 delegates this round)
vikram* (13 delegates this round)
Please take a moment to remove them from your approved list:
wallet_approve_delegate init3 false
wallet_approve_delegate vikram false
It would be great to have the option to click on a delegate in the "delegates list"
and see a a produced/missed ratio graph (or better a 1-3 days moving everage of that).I situations like yesterday it would be much easier to make the "right" decisions related with votes. I mean it is much more importand how a delegate behaves in present and the last days compared with what they do in the past....
For example:
1.so yesterday if delegate spartako had 150 produced blocks and has lost only 15 I wouldn't take my vote back
2....and if delegate clout had 150 produced blocks and has lost 120 I would vote him out to help the network...
but what if I could
easy see on a graph that the 15 block's that spartako lost was the 15 last blocks?
and for example clout on the other side
has produced without problem the 100 last blocks ?
of course I wouldn't take my vote back on clout and maybe I would take my vote back for spartako until he convince me everything is ok again...
Conclusion:
It must be easy for the wallet users to see statistics like that mentionned
so we can make better decisions without the need to spend too much time...and maybe even make bad decisions...
In situation's like yesterday we would "come back" easier and ... sooner!
PS it would be great also , in casse a delegate has lost his last y blocks (for example y=10) that the font color of the delegate get red and is blinking so it will "steal" our attention for further investigation.
PS2 I see the pottential right now for jobs that will only watching close delegates behavior and give advices and a ton of different statistics, via deticated sites for that reason (of course in the future)
Quote from: toast on July 03, 2014, 11:55:02 PM
We fucked up! All the seed nodes are dead and not coming back.
Working on building new default seeds into the client soon now.
What a convenient opportunity to ask for seed nodes for the Real Thing (wink wink nudge). Please send an IP if you want to be a seed.
In the meantime if you want to connect to the network for the first time:
network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
network_add_node "106.185.26.162:8761" add
network_add_node "107.170.30.182:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "107.170.170.214:48387" add
network_add_node "95.85.33.16:8764" add
network_add_node "84.238.140.192:8701" add
network_add_node "176.9.234.166:8701" add
network_add_node "162.243.219.145:8701" add
I go out to eat dinner and you all take down the delegates and seed nodes, I cannot leave you alone for a second..... *shakes head*...
Seed nodes are building again, but init delegates will have to wait until tomorrow for me to recover the private keys and get active again.
Quote from: bytemaster on July 04, 2014, 01:10:11 AM
I go out to eat dinner and you all take down the delegates and seed nodes, I cannot leave you alone for a second..... *shakes head*...
Seed nodes are building again, but init delegates will have to wait until tomorrow for me to recover the private keys and get active again.
lol :P
This is stange..
1899819 blocks left to fetch
--- syncing with p2p network, 1899819 blocks left to fetch
--- there are now 34 active connections to the p2p network
--- there are now 35 active connections to the p2p network
--- syncing with p2p network, 1907815 blocks left to fetch
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 9046,
"blockchain_head_block_age": "14 seconds old",
"blockchain_head_block_timestamp": "20140704T013415",
"blockchain_average_delegate_participation": 89.380530973451329,
"blockchain_blocks_left_in_round": 44,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999359471140,
"blockchain_random_seed": "bd3595fbda4450347902205d3ed8d4213a683ab3",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 35,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140704T013429",
"ntp_error": -0.038683000000000002,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "31 years in the future",
"wallet_unlocked_until_timestamp": "19100203T195710",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "4 minutes in the future",
"wallet_next_block_production_timestamp": "20140704T013800",
"wallet_version": 101
}
--- there are now 34 active connections to the p2p network
--- there are now 35 active connections to the p2p network
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "9ed7cd7ce32914af1cb5055140f30f51351ec1d7",
"bitshares_toolkit_revision_age": "3 hours ago",
"fc_revision": "0fced2ddffb380572ed50c181e8496a9d8777a62",
"fc_revision_age": "3 hours ago",
"compile_date": "compiled on Jul 4 2014 at 00:28:40"
}
I have on win7 one delagate that was never an active one
"liondani-delegate-5"
Please vote me in. I want to see after an experiment "marketing effort"* how much
time it gets to get active ;)
so for the first 10 voters they answer with a
pts address on this post, will get 0.1 PTS !!!**
wallet_approve_delegate liondani-delegate-5 true
* this post 8)
** make sure you answer first and then vote me...
we are talking about real PTS!
Quote from: liondani on July 04, 2014, 02:02:02 AM
I have on win7 one delagate that was never an active one
"liondani-delegate-5"
Please vote me in. I want to see after a experiment "marketing effort"* how much
time it gets to get active ;)
so for the first 10 voters they answer with a
pts address on this post will get 0.1 PTS !!!!**
wallet_approve_delegate liondani-delegate-5 true
* this post 8)
** make sure you answer first and then vote me...
mywallet (unlocked) >>> wallet_approve_delegate liondani-delegate-5 true
OK
Quotemywallet (unlocked) >>> wallet_transfer 10000 XTS webber-test3 webber-test4
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-04T02:20:52 webber-test3 webber-test4 10,000.00000 XTS 0.10000 XTS 5f6d287f
mywallet (unlocked) >>>
Quote from: bitcoinerS on July 04, 2014, 01:35:32 AM
This is stange..
1899819 blocks left to fetch
--- syncing with p2p network, 1899819 blocks left to fetch
--- there are now 34 active connections to the p2p network
--- there are now 35 active connections to the p2p network
--- syncing with p2p network, 1907815 blocks left to fetch
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 9046,
"blockchain_head_block_age": "14 seconds old",
"blockchain_head_block_timestamp": "20140704T013415",
"blockchain_average_delegate_participation": 89.380530973451329,
"blockchain_blocks_left_in_round": 44,
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": 199999359471140,
"blockchain_random_seed": "bd3595fbda4450347902205d3ed8d4213a683ab3",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 35,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140704T013429",
"ntp_error": -0.038683000000000002,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "31 years in the future",
"wallet_unlocked_until_timestamp": "19100203T195710",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "4 minutes in the future",
"wallet_next_block_production_timestamp": "20140704T013800",
"wallet_version": 101
}
--- there are now 34 active connections to the p2p network
--- there are now 35 active connections to the p2p network
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "9ed7cd7ce32914af1cb5055140f30f51351ec1d7",
"bitshares_toolkit_revision_age": "3 hours ago",
"fc_revision": "0fced2ddffb380572ed50c181e8496a9d8777a62",
"fc_revision_age": "3 hours ago",
"compile_date": "compiled on Jul 4 2014 at 00:28:40"
}
Known issue: https://github.com/BitShares/bitshares_toolkit/issues/450
how can I check which one gave me a vote?
Or from how much delegates I get a voted?
Quote from: Webber on July 04, 2014, 02:21:44 AM
Quote from: liondani on July 04, 2014, 02:02:02 AM
I have on win7 one delagate that was never an active one
"liondani-delegate-5"
Please vote me in. I want to see after a experiment "marketing effort"* how much
time it gets to get active ;)
so for the first 10 voters they answer with a
pts address on this post will get 0.1 PTS !!!!**
wallet_approve_delegate liondani-delegate-5 true
* this post 8)
** make sure you answer first and then vote me...
mywallet (unlocked) >>> wallet_approve_delegate liondani-delegate-5 true
OK
Quotemywallet (unlocked) >>> wallet_transfer 10000 XTS webber-test3 webber-test4
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-04T02:20:52 webber-test3 webber-test4 10,000.00000 XTS 0.10000 XTS 5f6d287f
mywallet (unlocked) >>>
Status: 0/unconfirmed
Date: 4/7/2014 05:44
To: Webber PvqN4cZrQSVTojSryGZ9EChNHUA4MyudBM
Debit: -0.10 PTS
Transaction fee: -0.0001 PTS
Net amount: -0.1001 PTS
Transaction ID: cb2743f3ba6444b4a0d90efa78d0bcf621afdd6c6ad4ba837c98f69d0ed460e4
Thank you Webber ;)
Quote from: liondani on July 04, 2014, 02:40:20 AM
how can I check which one gave me a vote?
Or from how much delegates I get a voted?
wallet_account_vote_summary
blockchain_get_transaction transactionID
Quote from: Webber on July 04, 2014, 02:47:48 AM
Quote from: liondani on July 04, 2014, 02:40:20 AM
how can I check which one gave me a vote?
Or from how much delegates I get a voted?
wallet_account_vote_summary
blockchain_get_transaction transactionID
Thanks again Webber :)
Quote from: liondani on July 04, 2014, 02:02:02 AM
I have on win7 one delagate that was never an active one
"liondani-delegate-5"
Please vote me in. I want to see after an experiment "marketing effort"* how much
time it gets to get active ;)
so for the first 10 voters they answer with a
pts address on this post, will get 0.1 PTS !!!**
wallet_approve_delegate liondani-delegate-5 true
* this post 8)
** make sure you answer first and then vote me...
we are talking about real PTS!
Vikram pointed out that this is a historic moment - the first instance of vote buying for a DPOS delegate!
This is 10k-BTC-pizza level infamous!
Quote from: liondani on July 04, 2014, 02:40:20 AM
how can I check which one gave me a vote?
Or from how much delegates I get a voted?
Good question!
The voting details should be transparent.
Quote from: heyD on July 04, 2014, 03:45:54 AM
Quote from: liondani on July 04, 2014, 02:40:20 AM
how can I check which one gave me a vote?
Or from how much delegates I get a voted?
Good question!
The voting details should be transparent.
It is open source, and no centralization, thus is transparent, everyone can review the algorithm.
But in the same time, TITAN protect the privacy of users/voters.
Quote from: liondani on July 04, 2014, 02:02:02 AM
I have on win7 one delagate that was never an active one
"liondani-delegate-5"
Please vote me in. I want to see after an experiment "marketing effort"* how much
time it gets to get active ;)
so for the first 10 voters they answer with a
pts address on this post, will get 0.1 PTS !!!**
wallet_approve_delegate liondani-delegate-5 true
* this post 8)
** make sure you answer first and then vote me...
we are talking about real PTS!
You have my votes.
heyddryrun7 (unlocked) >>> wallet_account_vote_summary heyd-haiyaoce100lun
DELEGATE VOTES
------------------------------------------------
heyd-haiyaoce100lun 3299970000
liondani-delegate-5 2000000000
Please send the bribe pts to forum donation address PforumPLfVQXTi4QpQqKwoChXHkoHcxGuA
8) 8)
Can we get an updated compiled Windows wallet?
Couldn't unlock (Win GUI) so deleted the wallet.
Please send some funds XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
Connectivity not resolved yet:
--- there are now 2 active connections to the p2p network
--- in sync with p2p network
--- there are now 3 active connections to the p2p network
--- in sync with p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- in sync with p2p network
No connections using the git-head built ... not even to a machine with an (12h) older built .. just nothing :(
edit: i deleted every thing extecpt 'chain' and 'wallet' and am no connecting again!
Quote from: sumantso on July 04, 2014, 07:09:20 AM
Couldn't unlock (Win GUI) so deleted the wallet.
Please send some funds XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
Anybody? Will try a hand at this delegate business and see if it works :D
Quote from: xeroc on July 04, 2014, 07:38:10 AM
No connections using the git-head built ... not even to a machine with an (12h) older built .. just nothing :(
edit: i deleted every thing extecpt 'chain' and 'wallet' and am no connecting again!
try add this node 106.185.26.162:8761
My delegates emski-delegate3 and lotto are out of top101.
They are well performing testing delegates helping diversify delegate pool.
Also they help me test the functionality and report issues back.
If there are some good souls out there willing to upvote them I'll be eternally grateful for that.
Quote from: emski on July 04, 2014, 08:13:00 AM
My delegates emski-delegate3 and lotto are out of top101.
They are well performing testing delegates helping diversify delegate pool.
Also they help me test the functionality and report issues back.
If there are some good souls out there willing to upvote them I'll be eternally grateful for that.
I will if you
a) tell me how to do it
b) send me some funds to play with at XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
I don't see a vote option in the GUI.
EDIT: So I set wallet_set_delegate_trust delegate true and then when I transact, even to myself, it gets voted? How do I set the remaining 2 votes?
Quote from: sumantso on July 04, 2014, 08:25:46 AM
Quote from: emski on July 04, 2014, 08:13:00 AM
My delegates emski-delegate3 and lotto are out of top101.
They are well performing testing delegates helping diversify delegate pool.
Also they help me test the functionality and report issues back.
If there are some good souls out there willing to upvote them I'll be eternally grateful for that.
I will if you
a) tell me how to do it
b) send me some funds to play with at XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
I don't see a vote option in the GUI.
Cant help you with the GUI.
a) commandline is "wallet_approve_delegate <delegatename>"
Then you need to make a transaction.
b) done
Quote from: emski on July 04, 2014, 08:47:06 AM
Quote from: sumantso on July 04, 2014, 08:25:46 AM
Quote from: emski on July 04, 2014, 08:13:00 AM
My delegates emski-delegate3 and lotto are out of top101.
They are well performing testing delegates helping diversify delegate pool.
Also they help me test the functionality and report issues back.
If there are some good souls out there willing to upvote them I'll be eternally grateful for that.
I will if you
a) tell me how to do it
b) send me some funds to play with at XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
I don't see a vote option in the GUI.
Cant help you with the GUI.
a) commandline is "wallet_approve_delegate <delegatename>"
Then you need to make a transaction.
b) done
Thanks
I did, did it work?
Quote from: emski on July 04, 2014, 08:13:00 AM
My delegates emski-delegate3 and lotto are out of top101.
They are well performing testing delegates helping diversify delegate pool.
Also they help me test the functionality and report issues back.
If there are some good souls out there willing to upvote them I'll be eternally grateful for that.
calyauwall (unlocked) >>> wallet_approve_delegate emski-delegate3
OK
calyauwall (unlocked) >>> wallet_approve_delegate lotto
OK
calyauwall (unlocked) >>> wallet_transfer 1000 XTS calyaux calabiyau traffic
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-04T08:52:41 calyaux calabiyau 1,000.00000 XTS 0.10000 XTS traffic 240b06f5
Couldn`t resist for eternally gratefulness :)
I have recompiled the new code but now I have serious problem.
I restarted the client, I had some network connections (about 6) but the client was no more able to add new blocks and I was stuck at the last block I had in the database.
For this problem my delegates started to create forks as you can see in this one:
10418
2e4b78625a321f183b8de35ae29c0f50b779e6ba vikram9 0 182 2014-07-04T08:23:15 1269 YES YES
6c2c9d95b9a3aef9699e376759784a460d8d1a5d spartako4 0 182 2014-07-04T08:27:15 1030 N/A NO
Now I disabled my delegates so they will miss all blocks until I am able to recover from this problem.
I tried also to remove the chain/ directory but now I am stuck at block 0
default (locked) >>> getinfo
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": "16 seconds old",
"blockchain_head_block_timestamp": "20140704T085945",
"blockchain_average_delegate_participation": 0,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": 199999999981923,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 6,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140704T090001",
"ntp_error": -0.0035049999999999999,
"wallet_open": true,
"wallet_unlocked": false,
"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
}
{
"bitshares_toolkit_revision": "86dea979e9ccffb763edc8a2456408c9e116d85d",
"bitshares_toolkit_revision_age": "8 hours ago",
"fc_revision": "0fced2ddffb380572ed50c181e8496a9d8777a62",
"fc_revision_age": "10 hours ago",
"compile_date": "compiled on Jul 4 2014 at 10:12:56"
}
EDIT: I solved the problem deleting the entire ~/.BitSharesXTS and using the command wallet_create_from_json, now spartako delegates are back.
Ok, it worked
>> wallet_account_vote_summary
DELEGATE VOTES
------------------------------------------------
emski-delegate3 9661215
lotto 9661215
Can somebody vote for sumantso please?
Quote from: sumantso on July 04, 2014, 08:25:46 AM
b) send me some funds to play with at XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
Done
Quote from: CalabiYau on July 04, 2014, 09:01:58 AM
Quote from: sumantso on July 04, 2014, 08:25:46 AM
b) send me some funds to play with at XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
Done
Thanks :)
My delegate sumantso is inching up; by default more than anything else, I guess :D
EDIT: It has got 1 approval, from yours truly :D
Quote from: emski on July 04, 2014, 08:47:06 AM
Quote from: sumantso on July 04, 2014, 08:25:46 AM
Quote from: emski on July 04, 2014, 08:13:00 AM
My delegates emski-delegate3 and lotto are out of top101.
They are well performing testing delegates helping diversify delegate pool.
Also they help me test the functionality and report issues back.
If there are some good souls out there willing to upvote them I'll be eternally grateful for that.
I will if you
a) tell me how to do it
b) send me some funds to play with at XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
I don't see a vote option in the GUI.
Cant help you with the GUI.
a) commandline is "wallet_approve_delegate <delegatename>"
Then you need to make a transaction.
b) done
Voted from my delegate, my windows wallet has screwed up (out of funds) at least you get up vote :)
Quote from: betax on July 04, 2014, 09:09:28 AM
Quote from: emski on July 04, 2014, 08:47:06 AM
Quote from: sumantso on July 04, 2014, 08:25:46 AM
Quote from: emski on July 04, 2014, 08:13:00 AM
My delegates emski-delegate3 and lotto are out of top101.
They are well performing testing delegates helping diversify delegate pool.
Also they help me test the functionality and report issues back.
If there are some good souls out there willing to upvote them I'll be eternally grateful for that.
I will if you
a) tell me how to do it
b) send me some funds to play with at XTS5sBWGBjwcR4FBE6H4yzNhbvZCY5oetY7Bkgoouh4da4bFVPZ9c
I don't see a vote option in the GUI.
Cant help you with the GUI.
a) commandline is "wallet_approve_delegate <delegatename>"
Then you need to make a transaction.
b) done
Voted from my delegate, my windows wallet has screwed up (out of funds) at least you get up vote :)
I now have funds to play with :), post your address.
Don't worry my delegate is producing blocks at the moment, just vote me up.
Thanks!
Ill spin up an ubuntu VM and see if I can recover the wallet.
pls gimme your vote :)
Quote from: betax on July 04, 2014, 09:25:51 AM
Don't worry my delegate is producing blocks at the moment, just vote me up.
Thanks!
Ill spin up an ubuntu VM and see if I can recover the wallet.
for backup your wallet and recovering!
wallet_export_to_json <filename>.json
wallet_create_from_json <filename>.json.json file is saved on bitshares_toolkit root layer
This helps me a lot! Hope it helps you too
Quote from: cass on July 04, 2014, 09:31:53 AM
pls gimme your vote :)
I did!
>> wallet_account_vote_summary
DELEGATE VOTES
------------------------------------------------
bitsapphire 39641215
calyau2 39641215
calyau3 39641215
calyau4 39641215
cass-delegate 39641215
chinese 39641215
emski-delegate3 9761215
light 39641215
liondani 39641215
lotto 9661215
spartako 39641215
sumantso 200000
There seems a problem now, though. My transactions are not getting included, was voting for betax.
EDIT: My last 4 transactions haven't been included.
Cleared pending transactions and those funds haven't returned. Made some new transactions but same problem.
Anyways, can you please approve my delegate sumantso?
Yo baby .. Yo baby .. yo:
"blockchain_average_delegate_participation": 95.283018867924525,
No idea how they did it .. but TITAN scanning is MUCH faster for me now
however .. once I unlocked my wallet and the transactions were scanned .. I lost all connections to the network :((
My transactions are getting included, but I am not receiving the funds or able to change my vote.
Quote from: sumantso on July 04, 2014, 10:06:49 AM
My transactions are getting included, but I am not receiving the funds or able to change my vote.
If you run a delegate in your wallet you currently can't scan for that transaction ..
disable your delegate or run a second client without delegates!
Quote from: heyD on July 04, 2014, 04:52:57 AM
Quote from: liondani on July 04, 2014, 02:02:02 AM
I have on win7 one delagate that was never an active one
"liondani-delegate-5"
Please vote me in. I want to see after an experiment "marketing effort"* how much
time it gets to get active ;)
so for the first 10 voters they answer with a
pts address on this post, will get 0.1 PTS !!!**
wallet_approve_delegate liondani-delegate-5 true
* this post 8)
** make sure you answer first and then vote me...
we are talking about real PTS!
You have my votes.
heyddryrun7 (unlocked) >>> wallet_account_vote_summary heyd-haiyaoce100lun
DELEGATE VOTES
------------------------------------------------
heyd-haiyaoce100lun 3299970000
liondani-delegate-5 2000000000
Please send the bribe pts to forum donation address PforumPLfVQXTi4QpQqKwoChXHkoHcxGuA
8) 8)
Status: 0/unconfirmed, broadcast through 2 nodes
Date: 4/7/2014 13:23
To: heyD PforumPLfVQXTi4QpQqKwoChXHkoHcxGuA
Debit: -0.10 PTS
Transaction fee: -0.0001 PTS
Net amount: -0.1001 PTS
Transaction ID: 6310b236744bfaf6754e0ee7bf3c2c256f8f7c43fec5519bc7c2349c27a16d35
Thanks heyD ;)
My balance was enough after I rescaned chain,but when I transfer 500000XTS ,the wallet will give a huge amount of error log.
ftp://ftp-webber:
[email protected]/tra-err.txt (ftp://ftp-webber:
[email protected]/tra-err.txt)
after I voted up cass
from my windows gui I transferred 10 XTS
from liondani-delegate-1 to liondani-delegate-3
the block that included the transaction is 10877
BUT the 10 XTS don't show up on liondani-delegate-3
Quote from: liondani on July 04, 2014, 10:50:35 AM
after I voted up cass
from my windows gui I transferred 10 XTS
from liondani-delegate-1 to liondani-delegate-3
the block that included the transaction is 10877
BUT the 10 XTS don't show up on liondani-delegate-3
Same problem as mine, you have to disable delegates.
Quote from: sumantso on July 04, 2014, 10:54:38 AM
Quote from: liondani on July 04, 2014, 10:50:35 AM
after I voted up cass
from my windows gui I transferred 10 XTS
from liondani-delegate-1 to liondani-delegate-3
the block that included the transaction is 10877
BUT the 10 XTS don't show up on liondani-delegate-3
Same problem as mine, you have to disable delegates.
>> wallet_approve_delegate sumantso true
OK
;)
wallet scanning for new transactions seems to take a long time now. ~ 40 a second.
calyauwall (unlocked) >>> wallet_approve_delegate liondani true
OK
calyauwall (unlocked) >>> wallet_approve_delegate liondani-delegate-5 true
OK
calyauwall (unlocked) >>> wallet_transfer 500 XTS calyaux calabiyau
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-04T12:40:25 calyaux calabiyau 500.00000 XTS 0.10000 XTS 747ce138
for free ;)
Quote from: CalabiYau on July 04, 2014, 12:42:54 PM
calyauwall (unlocked) >>> wallet_approve_delegate liondani true
OK
calyauwall (unlocked) >>> wallet_approve_delegate liondani-delegate-5 true
OK
calyauwall (unlocked) >>> wallet_transfer 500 XTS calyaux calabiyau
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-04T12:40:25 calyaux calabiyau 500.00000 XTS 0.10000 XTS 747ce138
for free ;)
>> wallet_approve_delegate calyau1 true
OK
>> wallet_transfer 50 XTS liondani-delegate-10 liondani-delegate-3
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
PENDING 2014-07-04T12:56:26 liondani-delegat... liondani-delegate-3 50.00000 XTS 0.10000 XTS eda08d29
please give me your PTS address ;)
guys vote for me plz....
wallet_approve_delegate jwizmyxts true
Wallet fixed.. voted for
wallet_approve_delegate bitsapphire true
wallet_approve_delegate calyau2 true
wallet_approve_delegate calyau3 true
wallet_approve_delegate calyau4 true
wallet_approve_delegate cass-delegate true
wallet_approve_delegate chinese true
wallet_approve_delegate emski-delegate3 true
wallet_approve_delegate light true
wallet_approve_delegate liondani true
wallet_approve_delegate lotto true
wallet_approve_delegate spartako true
wallet_approve_delegate sumantso true
wallet_approve_delegate betax true
wallet_approve_delegate jwizmyxts true
Anybody needs votes or XTS let me know
Quote from: jwiz168 on July 04, 2014, 01:04:07 PM
guys vote for me plz....
wallet_approve_delegate jwizmyxts true
>> wallet_approve_delegate jwizmyxts true
OK
and of course :P
wallet_approve_delegate liondani-delegate-5
wallet_transfer 19999 XTS betax1 betax1
Quote from: sumantso on July 04, 2014, 10:54:38 AM
Quote from: liondani on July 04, 2014, 10:50:35 AM
after I voted up cass
from my windows gui I transferred 10 XTS
from liondani-delegate-1 to liondani-delegate-3
the block that included the transaction is 10877
BUT the 10 XTS don't show up on liondani-delegate-3
Same problem as mine, you have to disable delegates.
how can I disable delegates ???
wallet_delegate_set_block_production command
don't work anymore....
Quote from: liondani on July 04, 2014, 11:05:19 AM
Quote from: sumantso on July 04, 2014, 10:54:38 AM
Quote from: liondani on July 04, 2014, 10:50:35 AM
after I voted up cass
from my windows gui I transferred 10 XTS
from liondani-delegate-1 to liondani-delegate-3
the block that included the transaction is 10877
BUT the 10 XTS don't show up on liondani-delegate-3
Same problem as mine, you have to disable delegates.
>> wallet_approve_delegate sumantso true
OK
;)
Thanks mate, but it got messed up anyway. I tried disabling delegate, and after restarting it won't let me unlock. I deleted everything and started again and its now syncing like a snail ::)
How do you manage to keep it unlocked in windows?
Quote from: sumantso on July 04, 2014, 01:32:11 PM
Quote from: liondani on July 04, 2014, 11:05:19 AM
Quote from: sumantso on July 04, 2014, 10:54:38 AM
Quote from: liondani on July 04, 2014, 10:50:35 AM
after I voted up cass
from my windows gui I transferred 10 XTS
from liondani-delegate-1 to liondani-delegate-3
the block that included the transaction is 10877
BUT the 10 XTS don't show up on liondani-delegate-3
Same problem as mine, you have to disable delegates.
>> wallet_approve_delegate sumantso true
OK
;)
Thanks mate, but it got messed up anyway. I tried disabling delegate, and after restarting it won't let me unlock. I deleted everything and started again and its now syncing like a snail ::)
How do you manage to keep it unlocked in windows?
I don't know why but when it get's locked I sign in again without problem now!(?)
>> about
{
"bitshares_toolkit_revision": "507cb6cb21ad74d3b92eb447bf3e051f31804aed",
"bitshares_toolkit_revision_age": "63 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "66 hours ago",
"compile_date": "compiled on Jul 1 2014 at 19:58:21"
}
PS How do you disable the delegates?
Quote from: liondani on July 04, 2014, 01:41:51 PM
PS How do you disable the delegates?
I think it just means setting them off for block production. After that I tried rescanning the blockchain to get those transactions when it messed up. Now I am back to square 0 :(
My advise: forget those balances :D
Btw, even if you can sign in, you will miss blocks if it is locked when your turn comes.
Won't let me log in again. I am going to delete wallet again *sigh*
Sorry for all those who funded and voted for me :(
Quote from: betax on July 04, 2014, 01:15:05 PM
and of course :P
wallet_approve_delegate liondani-delegate-5
wallet_transfer 19999 XTS betax1 betax1
thanks betax :)
please give me your pts address ;)
wallet_approve_delegate betax
wallet_transfer 20 XTS liondani-win7 liondani-delegate-1
Quote from: sumantso on July 04, 2014, 02:10:48 PM
Won't let me log in again. I am going to delete wallet again *sigh*
Sorry for all those who funded and voted for me :(
This is a major concern... if your wallet password got corrupted we have issues.
Quote from: bytemaster on July 04, 2014, 02:43:30 PM
Quote from: sumantso on July 04, 2014, 02:10:48 PM
Won't let me log in again. I am going to delete wallet again *sigh*
Sorry for all those who funded and voted for me :(
This is a major concern... if your wallet password got corrupted we have issues.
I had the same problem the last days .
I deleted all files ecxept directory wallets
and after reinstall I could sign in with the same password.
Quote from: Webber on July 04, 2014, 10:38:25 AM
My balance was enough after I rescaned chain,but when I transfer 500000XTS ,the wallet will give a huge amount of error log.
ftp://ftp-webber:[email protected]/tra-err.txt (ftp://ftp-webber:[email protected]/tra-err.txt)
To send 50K XTS you needed to combine many small balances in one transaction which created one VERY BIG transaction yet we just included the standard fee. There is also the possibility to create a transaction larger than what is allowed by blocks. If you were stress-testing with this account then that is likely what the problem is.
The solution is to send yourself several smaller transactions that will combine values first.
Quote from: liondani on July 04, 2014, 02:46:53 PM
Quote from: bytemaster on July 04, 2014, 02:43:30 PM
Quote from: sumantso on July 04, 2014, 02:10:48 PM
Won't let me log in again. I am going to delete wallet again *sigh*
Sorry for all those who funded and voted for me :(
This is a major concern... if your wallet password got corrupted we have issues.
I had the same problem the last days .
I deleted all files ecxept directory wallets
and after reinstall I could sign in with the same password.
So you are telling me the wallet file is fine, but something else is causing the password check to fail. Likely means we are mis-reporting the real error somehow.
Quote from: bytemaster on July 04, 2014, 02:49:15 PM
So you are telling me the wallet file is fine, but something else is causing the password check to fail. Likely means we are mis-reporting the real error somehow.
Yep, I think so...
Actualy password check didn't fail but this:
Quote from: liondani on July 02, 2014, 02:27:51 PM
Quote from: bitdraw on July 02, 2014, 12:49:20 PM
- when i try to log in with my password i just see the rotating symbol but it doesnt log me in and goes on forever
(temporary issue)
My windows wallet was fine, so I move that wallet to an ubuntu VM. The GUI once is locked you cannot unlock it.
Quote from: betax on July 04, 2014, 03:03:13 PM
My windows wallet was fine, so I move that wallet to an ubuntu VM. The GUI once is locked you cannot unlock it.
I had the same issue the last days but not now!
I can unlock now without problem...
what is your version to compare it?
My is:
>> about
{
"bitshares_toolkit_revision": "507cb6cb21ad74d3b92eb447bf3e051f31804aed",
"bitshares_toolkit_revision_age": "64 hours ago",
"fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
"fc_revision_age": "67 hours ago",
"compile_date": "compiled on Jul 1 2014 at 19:58:21"
}
similar problem on osx gui wallet. I notice that you have unlock it, but the overview page is broken, so you will stay at the login page.
I use the menu "Go to My Accounts" go to the account page, now you can use the wallet.
Quote from: betax on July 04, 2014, 03:03:13 PM
My windows wallet was fine, so I move that wallet to an ubuntu VM. The GUI once is locked you cannot unlock it.
I have been naming my wallets sumantso. Now I wonder if there are multiple sumantsos out there :D How can I delete them? I can't access those wallets.
Can somebody check?
Quote from: sumantso on July 04, 2014, 03:26:10 PM
I have been naming my wallets sumantso. Now I wonder if there are multiple sumantsos out there :D How can I delete them? I can't access those wallets.
Can somebody check?
guess you can't delete them.. but don't know it exactly
You can't delete them feom gui, but you can't make multiple wallets with the same name and you can't make multiple wallets with the gui at all except via console
Sent from my SCH-I535 using Tapatalk
Quote from: bytemaster on July 04, 2014, 02:47:53 PM
Quote from: Webber on July 04, 2014, 10:38:25 AM
My balance was enough after I rescaned chain,but when I transfer 500000XTS ,the wallet will give a huge amount of error log.
ftp://ftp-webber:[email protected]/tra-err.txt (ftp://ftp-webber:[email protected]/tra-err.txt)
To send 50K XTS you needed to combine many small balances in one transaction which created one VERY BIG transaction yet we just included the standard fee. There is also the possibility to create a transaction larger than what is allowed by blocks. If you were stress-testing with this account then that is likely what the problem is.
The solution is to send yourself several smaller transactions that will combine values first.
I see, you are right!
Guys we just fixed our bad terrible block production rate. We weren't hitting almost any blocks over this dry run. Works now without a hitch.
Might be helpful to some of you in the future:
- Rescan the blockchain
- Wallet unlocked
- Block production enabled
If you're using putty on your client to manipulate your server be sure to check whether putty is messing with your true/false commands when you close putty. Putty on our windows machine had a weird random bug where it would sometimes turn our wallet locked when we closed putty at the end of our working day. Hence our server wasn't doing anything overnight. We are using our Linux machine now for SSH to our server.
Quote from: ding on July 04, 2014, 03:15:34 PM
similar problem on osx gui wallet. I notice that you have unlock it, but the overview page is broken, so you will stay at the login page.
I use the menu "Go to My Accounts" go to the account page, now you can use the wallet.
Quote from: betax on July 04, 2014, 03:03:13 PM
My windows wallet was fine, so I move that wallet to an ubuntu VM. The GUI once is locked you cannot unlock it.
Denny is working on this issue now. Should be resolved later today.
I decided to run a new flood test where I would pump out 1000 trx per second and the network just laughed at my node and is slowly incorporating them at about 20 trx per block or so. Flood failed, network won!
holy moly .. can we stresstest the whole weekend ... to be sure
Quote from: bytemaster on July 04, 2014, 04:51:57 PM
I decided to run a new flood test where I would pump out 1000 trx per second and the network just laughed at my node and is slowly incorporating them at about 20 trx per block or so. Flood failed, network won!
This made my day :D
Go Daniel go!
We just introduced a hard fork... everyone should update. GUI wallet will be on minority fork until we get a new one out.
Still can't get the Windows GUI to run for the life of me. It just opens the splash page with bitsharesXT logo and then closes 3 seconds later. I have tried opening my firewall, ports, downloading in different browsers and nothing will get this going.
I am not sure if it's a comparability issue or if my computer is blocking something. I think Cass said he was having the same problem for one of his Windows laptops.
Any ideas?
I am using Windows 7 64bit.
Seems that this test is going very well, congrats! +5% +5%
Quote from: GregGozzo on July 04, 2014, 06:18:25 PM
Still can't get the Windows GUI to run for the life of me. It just opens the splash page with bitsharesXT logo and then closes 3 seconds later. I have tried opening my firewall, ports, downloading in different browsers and nothing will get this going.
I am not sure if it's a comparability issue or if my computer is blocking something. I think Cass said he was having the same problem for one of his Windows laptops.
Any ideas?
I am using Windows 7 64bit.
You have to wait for the updated wallet anyway. The network has been hardforked.
What does this mean?
>>> get_info
{
"blockchain_delegate_pay_rate": 77111,
Quote from: liondani on July 04, 2014, 02:21:57 PM
Quote from: betax on July 04, 2014, 01:15:05 PM
and of course :P
wallet_approve_delegate liondani-delegate-5
wallet_transfer 19999 XTS betax1 betax1
thanks betax :)
please give me your pts address ;)
wallet_approve_delegate betax
wallet_transfer 20 XTS liondani-win7 liondani-delegate-1
its ok my pleasure :)
Quote from: bitcoinerS on July 04, 2014, 07:05:36 PM
What does this mean?
>>> get_info
{
"blockchain_delegate_pay_rate": 77111,
# of satoshi the block producer will get
Quote from: bitcoinerS on July 04, 2014, 07:05:36 PM
What does this mean?
>>> get_info
{
"blockchain_delegate_pay_rate": 77111,
This is how much (in shares) a delegate gets paid per block. It is based upon the moving average of transaction fees over the past 24 hours.
I've got my delegate and seed node (95.85.33.16:8764) on the new chain. dele-puppy is #101 though and my 10% delegate pay will not keep me in long. Please vote for dele-puppy
I am also looking at experimenting with running a delegate through tor. If you would also like to see if this is possible, vote for tor-delegate.
Quote from: puppies on July 04, 2014, 07:40:48 PM
I've got my delegate and seed node (95.85.33.16:8764) on the new chain. dele-puppy is #101 though and my 10% delegate pay will not keep me in long. Please vote for dele-puppy
I am also looking at experimenting with running a delegate through tor. If you would also like to see if this is possible, vote for tor-delegate.
voted for dele-puppy and tor-delegate
Quote from: vlight on July 04, 2014, 07:59:31 PM
Running the latest wallet. Please vote for "light" delegate, which has 0% payrate. Unlike those with 100% payrate that belong to the same person ;D
its all fake money
Quote from: bitcoinerS on July 04, 2014, 07:57:48 PM
Quote from: puppies on July 04, 2014, 07:40:48 PM
I've got my delegate and seed node (95.85.33.16:8764) on the new chain. dele-puppy is #101 though and my 10% delegate pay will not keep me in long. Please vote for dele-puppy
I am also looking at experimenting with running a delegate through tor. If you would also like to see if this is possible, vote for tor-delegate.
voted for dele-puppy and tor-delegate
Thanks bitcoiners.
I have a compile problem:
[ 91%] Building CXX object libraries/api/CMakeFiles/bts_rpc_stubs.dir/__/rpc_stubs/common_api_rpc_client.cpp.o
/home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/common_api_rpc_client.cpp: In member function 'virtual bts::blockchain::signed_transaction bts::rpc_stubs::common_api_rpc_client::wallet_asset_create(const string&, const string&, const string&, const string&, const fc::variant&, int64_t, int64_t, bool)':
/home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/common_api_rpc_client.cpp:302:286: error: no matching function for call to 'fc::rpc::json_connection::async_call(const char [20], fc::variant, fc::variant, fc::variant, fc::variant, fc::variant, fc::variant, fc::variant, fc::variant)'
fc::variant result = get_json_connection()->async_call("wallet_asset_create", fc::variant(symbol), fc::variant(asset_name), fc::variant(issuer_name), fc::variant(description), fc::variant(data), fc::variant(maximum_share_supply), fc::variant(precision), fc::variant(is_market_issued)).wait();
^
/home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/common_api_rpc_client.cpp:302:286: note: candidates are:
In file included from /home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp:19:0,
from /home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/common_api_rpc_client.cpp:18:
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:56:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant_object&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:56:26: note: candidate expects 2 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:59:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, fc::mutable_variant_object)
future<variant> async_call( const fc::string& method, mutable_variant_object args );
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:59:26: note: candidate expects 2 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:62:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const variants&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:62:26: note: candidate expects 2 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:65:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&)
future<variant> async_call( const fc::string& method );
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:65:26: note: candidate expects 1 argument, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:67:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:67:26: note: candidate expects 2 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:70:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:70:26: note: candidate expects 3 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:74:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:74:26: note: candidate expects 4 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:79:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:79:26: note: candidate expects 5 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:85:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:85:26: note: candidate expects 6 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:92:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:92:26: note: candidate expects 7 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:100:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:100:26: note: candidate expects 8 arguments, 9 provided
make[2]: *** [libraries/api/CMakeFiles/bts_rpc_stubs.dir/__/rpc_stubs/common_api_rpc_client.cpp.o] Error 1
make[1]: *** [libraries/api/CMakeFiles/bts_rpc_stubs.dir/all] Error 2
make: *** [all] Error 2
Git submodule update
Sent from my SCH-I535 using Tapatalk
Quote from: clout on July 04, 2014, 08:13:36 PM
Quote from: vlight on July 04, 2014, 07:59:31 PM
Running the latest wallet. Please vote for "light" delegate, which has 0% payrate. Unlike those with 100% payrate that belong to the same person ;D
its all fake money
fake money, real competition :P
Quote from: vlight on July 04, 2014, 07:59:31 PM
Running the latest wallet. Please vote for "light" delegate, which has 0% payrate. Unlike those with 100% payrate that belong to the same person ;D
Voted for you ;)
Quote
328 light 0.0505237855 % 18 1 94.74 % 0 % 6.84165 XTS 2947
Quote from: toast on July 04, 2014, 09:06:16 PM
Git submodule update
Sent from my SCH-I535 using Tapatalk
same problem with git submodule update, this is the last fc commit:
commit 0fced2ddffb380572ed50c181e8496a9d8777a62
Merge: c020913 c9c56ff
Author: Nikolai Mushegian <[email protected]>
Date: Thu Jul 3 19:01:14 2014 -0400
Quote from: spartako on July 04, 2014, 09:05:22 PM
I have a compile problem:
[ 91%] Building CXX object libraries/api/CMakeFiles/bts_rpc_stubs.dir/__/rpc_stubs/common_api_rpc_client.cpp.o
/home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/common_api_rpc_client.cpp: In member function 'virtual bts::blockchain::signed_transaction bts::rpc_stubs::common_api_rpc_client::wallet_asset_create(const string&, const string&, const string&, const string&, const fc::variant&, int64_t, int64_t, bool)':
/home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/common_api_rpc_client.cpp:302:286: error: no matching function for call to 'fc::rpc::json_connection::async_call(const char [20], fc::variant, fc::variant, fc::variant, fc::variant, fc::variant, fc::variant, fc::variant, fc::variant)'
fc::variant result = get_json_connection()->async_call("wallet_asset_create", fc::variant(symbol), fc::variant(asset_name), fc::variant(issuer_name), fc::variant(description), fc::variant(data), fc::variant(maximum_share_supply), fc::variant(precision), fc::variant(is_market_issued)).wait();
^
/home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/common_api_rpc_client.cpp:302:286: note: candidates are:
In file included from /home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/include/bts/rpc_stubs/common_api_rpc_client.hpp:19:0,
from /home/spartako/ssd/bitshares_toolkit/libraries/rpc_stubs/common_api_rpc_client.cpp:18:
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:56:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant_object&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:56:26: note: candidate expects 2 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:59:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, fc::mutable_variant_object)
future<variant> async_call( const fc::string& method, mutable_variant_object args );
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:59:26: note: candidate expects 2 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:62:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const variants&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:62:26: note: candidate expects 2 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:65:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&)
future<variant> async_call( const fc::string& method );
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:65:26: note: candidate expects 1 argument, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:67:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:67:26: note: candidate expects 2 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:70:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:70:26: note: candidate expects 3 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:74:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:74:26: note: candidate expects 4 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:79:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:79:26: note: candidate expects 5 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:85:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:85:26: note: candidate expects 6 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:92:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:92:26: note: candidate expects 7 arguments, 9 provided
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:100:26: note: fc::future<fc::variant> fc::rpc::json_connection::async_call(const string&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&, const fc::variant&)
future<variant> async_call( const fc::string& method,
^
/home/spartako/ssd/bitshares_toolkit/libraries/fc/include/fc/rpc/json_connection.hpp:100:26: note: candidate expects 8 arguments, 9 provided
make[2]: *** [libraries/api/CMakeFiles/bts_rpc_stubs.dir/__/rpc_stubs/common_api_rpc_client.cpp.o] Error 1
make[1]: *** [libraries/api/CMakeFiles/bts_rpc_stubs.dir/all] Error 2
make: *** [all] Error 2
I just checked in code to fc that should address this.
Quote from: bytemaster on July 04, 2014, 09:25:05 PM
I just checked in code to fc that should address this.
Thanks, now it works!
Quote from: GregGozzo on July 04, 2014, 06:18:25 PM
Still can't get the Windows GUI to run for the life of me. It just opens the splash page with bitsharesXT logo and then closes 3 seconds later. I have tried opening my firewall, ports, downloading in different browsers and nothing will get this going.
I am not sure if it's a comparability issue or if my computer is blocking something. I think Cass said he was having the same problem for one of his Windows laptops.
Any ideas?
I am using Windows 7 64bit.
Anyone?
Updated Mac GUI
Mac GUI
http://www.bitshares.org/BitSharesXT-0.0.9.dmg (http://www.bitshares.org/BitSharesXT-0.0.9.dmg)
Quote from: liondani on July 01, 2014, 11:56:25 PM
liondani (unlocked) >>> wallet_account_transaction_history liondani
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
438.0 2014-07-01T22:38:00 liondani liondani 0000000 XTS 0.18739 XTS register liondani as a delegate c1728e5f
the fee of 0.18739 XTS to create a delegate was not a mistake I suppose?
Fixed for the next chain: https://github.com/BitShares/bitshares_toolkit/compare/194e7ba23b...0d02aa48fe#diff-2
Quote from: GregGozzo on July 04, 2014, 09:35:49 PM
Quote from: GregGozzo on July 04, 2014, 06:18:25 PM
Still can't get the Windows GUI to run for the life of me. It just opens the splash page with bitsharesXT logo and then closes 3 seconds later. I have tried opening my firewall, ports, downloading in different browsers and nothing will get this going.
I am not sure if it's a comparability issue or if my computer is blocking something. I think Cass said he was having the same problem for one of his Windows laptops.
Any ideas?
I am using Windows 7 64bit.
Anyone?
So I'm guessing you're running it in command line? It doesn't throw any errors?
Have you deleted your data directory?
If nothing else I would download a Windows debugger. That might tell you when it's getting stuck.
Quote from: puppies on July 04, 2014, 10:07:28 PM
Quote from: GregGozzo on July 04, 2014, 09:35:49 PM
Quote from: GregGozzo on July 04, 2014, 06:18:25 PM
Still can't get the Windows GUI to run for the life of me. It just opens the splash page with bitsharesXT logo and then closes 3 seconds later. I have tried opening my firewall, ports, downloading in different browsers and nothing will get this going.
I am not sure if it's a comparability issue or if my computer is blocking something. I think Cass said he was having the same problem for one of his Windows laptops.
Any ideas?
I am using Windows 7 64bit.
Anyone?
So I'm guessing you're running it in command line? It doesn't throw any errors?
Have you deleted your data directory?
If nothing else I would download a Windows debugger. That might tell you when it's getting stuck.
I have deleted the data dir.
Not command line, just trying to run the .exe and it opens the splash page then closes.
Tried trouble shooting and get nowhere. Ill try the debugger.
I am able to get it running on an Amazon instance no problem. So it is something to do with my computer. Something isnt connecting or blocking the connection and I cant figure out what it is.
Thanks
update to latest code, show some error when run command "blockchain_list_forks"
12738
57620b2635c939eb9cb0d26ebb1310a3cee0e527 vikram13 22 5626 2014-07-04T19:01:15 0 NO NO
20ac56fa4e6c10a0546ebf9a00f5cf0e86a580eb delegate-baozi 22 5550 2014-07-04T19:01:45 0 YES YES
REASONS FOR INVALID BLOCKS
Wb
&5�9뜰�n�����': 35007 over_issue: over issue
{"amount":{"amount":1,"asset_id":28},"current_asset_record":{"id":28,"symbol":"FORK","name":"ForKoin","description":"The coin of forking","public_data":"Fork on first issue","issuer_account_id":537,"precision":1,"current_share_supply":0,"maximum_share_supply":1,"collected_fees":0,"registration_date":"20140704T174215"}}
th_a asset_operations.cpp:118 evaluate
{"*this":{"amount":{"amount":1,"asset_id":28}}}
th_a asset_operations.cpp:126 evaluate
{"op":{"type":"issue_asset_op_type","data":{"amount":{"amount":1,"asset_id":28}}}}
th_a operation_factory.hpp:51 evaluate
{"trx":{"expiration":"20140704T194319","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS389tfuYMjGWAJWwr54NEcqRZNVTtz5gze","amount":10000,"claim_input_data":""}},{"type":"issue_asset_op_type","data":{"amount":{"amount":1,"asset_id":28}}},{"type":"deposit_op_type","data":{"amount":1,"condition":{"asset_id":28,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSNcCA2QGJwX5HjshSgnzXaRsDSjzd71TGK","memo":{"one_time_key":"XTS5eN7GXh28RK5YZgXruuVh7sKzn285Bx8UeKXN932qSpfVLTLEY","encrypted_memo_data":"11fa71c909b863b39dccf8fa0d41ade4814830cf7d083c35d30026c4ed518e03881c57f7c0fd895be7194d9ac1f4c759862aefa6e4ed5721947dff6a4000f99a"}}}}}],"signatures":["1ff194d81b7758c92175e53f8e0ee073a534d115bf2dec344990184f1b99968724d59f8600134f67618d92d7028f72ba6308e3f6f113711f493a6281f2d26b9a14","206d8cf587df36c4c0c3521a5eefcea439b069a09c679336619539aa78d51222d8a14f3924e8cdbcbb82a123f558ef8784e4c9fb3e57e1070177e06577fd182061"]}}
th_a transaction_evaluation_state.cpp:164 evaluate
{"trx_num":0}
th_a chain_database.cpp:535 apply_transactions
Quote from: bytemaster on July 04, 2014, 09:49:29 PM
Updated Mac GUI
Mac GUI
http://www.bitshares.org/BitSharesXT-0.0.9.dmg (http://www.bitshares.org/BitSharesXT-0.0.9.dmg)
It's still has no connections in network.
Quote from: ding on July 05, 2014, 12:44:02 AM
update to latest code, show some error when run command "blockchain_list_forks"
12738
57620b2635c939eb9cb0d26ebb1310a3cee0e527 vikram13 22 5626 2014-07-04T19:01:15 0 NO NO
20ac56fa4e6c10a0546ebf9a00f5cf0e86a580eb delegate-baozi 22 5550 2014-07-04T19:01:45 0 YES YES
REASONS FOR INVALID BLOCKS
Wb
&5�9뜰�n�����': 35007 over_issue: over issue
{"amount":{"amount":1,"asset_id":28},"current_asset_record":{"id":28,"symbol":"FORK","name":"ForKoin","description":"The coin of forking","public_data":"Fork on first issue","issuer_account_id":537,"precision":1,"current_share_supply":0,"maximum_share_supply":1,"collected_fees":0,"registration_date":"20140704T174215"}}
th_a asset_operations.cpp:118 evaluate
{"*this":{"amount":{"amount":1,"asset_id":28}}}
th_a asset_operations.cpp:126 evaluate
{"op":{"type":"issue_asset_op_type","data":{"amount":{"amount":1,"asset_id":28}}}}
th_a operation_factory.hpp:51 evaluate
{"trx":{"expiration":"20140704T194319","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS389tfuYMjGWAJWwr54NEcqRZNVTtz5gze","amount":10000,"claim_input_data":""}},{"type":"issue_asset_op_type","data":{"amount":{"amount":1,"asset_id":28}}},{"type":"deposit_op_type","data":{"amount":1,"condition":{"asset_id":28,"delegate_slate_id":0,"type":"withdraw_signature_type","data":{"owner":"XTSNcCA2QGJwX5HjshSgnzXaRsDSjzd71TGK","memo":{"one_time_key":"XTS5eN7GXh28RK5YZgXruuVh7sKzn285Bx8UeKXN932qSpfVLTLEY","encrypted_memo_data":"11fa71c909b863b39dccf8fa0d41ade4814830cf7d083c35d30026c4ed518e03881c57f7c0fd895be7194d9ac1f4c759862aefa6e4ed5721947dff6a4000f99a"}}}}}],"signatures":["1ff194d81b7758c92175e53f8e0ee073a534d115bf2dec344990184f1b99968724d59f8600134f67618d92d7028f72ba6308e3f6f113711f493a6281f2d26b9a14","206d8cf587df36c4c0c3521a5eefcea439b069a09c679336619539aa78d51222d8a14f3924e8cdbcbb82a123f558ef8784e4c9fb3e57e1070177e06577fd182061"]}}
th_a transaction_evaluation_state.cpp:164 evaluate
{"trx_num":0}
th_a chain_database.cpp:535 apply_transactions
This was the bug we fixed today when attempt to issue last asset. If you got this exception it meant your client wasn't updated before a transaction was processed that included tested the fork condition.
Quote from: liondani on July 05, 2014, 04:04:13 AM
Before I delete all directories
I made a wallet backup using command:
"wallet_export_to_json"
Then after I rebuilded the bitshares_toolkit etc.
I tried to create my wallet from the json file I had but these error occured:
(wallet closed) >>> wallet_create_from_json Dry7_050714
wallet_name: liondani
imported_wallet_passphrase: ***********
10 assert_exception: Assert Exception
fc::exists( filename ):
{}
th_a wallet.cpp:812 create_from_json
{"filename":"Dry7_050714","wallet_name":"liondani"}
th_a wallet.cpp:830 create_from_json
{}
th_a common_api_client.cpp:579 wallet_create_from_json
{"command":"wallet_create_from_json"}
th_a cli.cpp:538 execute_command
any suggestions ? ::)
Are you sure you do not have a wallet named 'liondani' already? The output of 'wallet_list' does not show anything?
Quote from: liondani on July 05, 2014, 04:08:43 AM
Quote from: vikram on July 05, 2014, 04:06:53 AM
Quote from: liondani on July 05, 2014, 04:04:13 AM
Before I delete all directories
I made a wallet backup using command:
"wallet_export_to_json"
Then after I rebuilded the bitshares_toolkit etc.
I tried to create my wallet from the json file I had but these error occured:
(wallet closed) >>> wallet_create_from_json Dry7_050714
wallet_name: liondani
imported_wallet_passphrase: ***********
10 assert_exception: Assert Exception
fc::exists( filename ):
{}
th_a wallet.cpp:812 create_from_json
{"filename":"Dry7_050714","wallet_name":"liondani"}
th_a wallet.cpp:830 create_from_json
{}
th_a common_api_client.cpp:579 wallet_create_from_json
{"command":"wallet_create_from_json"}
th_a cli.cpp:538 execute_command
any suggestions ? ::)
Are you sure you do not have a wallet named 'liondani' already? The output of 'wallet_list' does not show anything?
I am sure!
(wallet closed) >>> wallet_list
No wallets found.
Actually this is the error for when the specified JSON file cannot be found (I know we need a better error message). Are you absolutely sure you are entering the correct filename to import from?
Quote from: vikram on July 05, 2014, 04:13:39 AM
Quote from: liondani on July 05, 2014, 04:08:43 AM
Quote from: vikram on July 05, 2014, 04:06:53 AM
Quote from: liondani on July 05, 2014, 04:04:13 AM
Before I delete all directories
I made a wallet backup using command:
"wallet_export_to_json"
Then after I rebuilded the bitshares_toolkit etc.
I tried to create my wallet from the json file I had but these error occured:
(wallet closed) >>> wallet_create_from_json Dry7_050714
wallet_name: liondani
imported_wallet_passphrase: ***********
10 assert_exception: Assert Exception
fc::exists( filename ):
{}
th_a wallet.cpp:812 create_from_json
{"filename":"Dry7_050714","wallet_name":"liondani"}
th_a wallet.cpp:830 create_from_json
{}
th_a common_api_client.cpp:579 wallet_create_from_json
{"command":"wallet_create_from_json"}
th_a cli.cpp:538 execute_command
any suggestions ? ::)
Are you sure you do not have a wallet named 'liondani' already? The output of 'wallet_list' does not show anything?
I am sure!
(wallet closed) >>> wallet_list
No wallets found.
Actually this is the error for when the specified JSON file cannot be found (I know we need a better error message). Are you absolutely sure you are entering the correct filename to import from?
SOLVED!
You are right I typed
Dry7_050714 instead of
dry7_050714
Sorry for freaking you out :P
Thanks ;)
PS As you said a better error message would be helpful
On linux everything worked fine with wallet creation from json file...
On win gui I tried to export a json file:
>> wallet_export_to_json liondani_backup_json
OK
I don't find the file anywhere.
Is it somewhere or is it a false message and actualy never created?
Quote from: bytemaster on July 04, 2014, 09:49:29 PM
Updated Mac GUI
Mac GUI
http://www.bitshares.org/BitSharesXT-0.0.9.dmg (http://www.bitshares.org/BitSharesXT-0.0.9.dmg)
Ah. Forgive me. The sync icon does not revolve around the center. :-[
No love for Windoze? :(
Quote from: bytemaster on July 04, 2014, 04:51:57 PM
I decided to run a new flood test where I would pump out 1000 trx per second and the network just laughed at my node and is slowly incorporating them at about 20 trx per block or so. Flood failed, network won!
I ran a stress-test today,and system works well.Good job!
when I give the commands:
wallet_approve_delegate liondani
wallet_approve_delegate liondani true
both times the result message is: "ok"
but in reality it approves only with the second command (+true)!
look please....
wallet_approve_delegate liondani (without true)
liondani (unlocked) >>> wallet_approve_delegate liondani
OK
liondani (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVED BLOCK PRODUCTION ENABLED
liondani * XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv 2014-07-01T22:37:45 NO 0 YES
liondani-linux * XTS7kn3gC9d6iKeFxieMj2Sf5PSLuerYZZFzGBQC7Ktu2p1dsyGGE 2014-07-02T00:26:15 NO 0 YES
liondani-linux-1 * XTS5mJjufSgJWmm9yNyWfAAoZSUKFfxphzmvYZzY7WtDHTDQ15bwL 2014-07-05T14:29:45 NO 0 YES
liondani-linux-2 * XTS7ackbkNREQgzVK9GJrTuMNGxigH2F7qQbf5ePnGU4hH4DyPDJ3 2014-07-05T14:33:00 NO 0 YES
liondaniel XTS6d5fuzezqyaBqzSJY6ityNWV59nGxoaf3ydHLPhFZQGKpuSfhP NO NO 0 N/A
user123 XTS747iL3PPsWy5ZyxjXVArdkv8hRCEZMFwudkYsnjsUb3dX6Znjj NO NO 0 N/A
wallet_approve_delegate liondani true
liondani (unlocked) >>> wallet_approve_delegate liondani true
OK
liondani (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVED BLOCK PRODUCTION ENABLED
liondani * XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv 2014-07-01T22:37:45 NO 1 YES
liondani-linux * XTS7kn3gC9d6iKeFxieMj2Sf5PSLuerYZZFzGBQC7Ktu2p1dsyGGE 2014-07-02T00:26:15 NO 0 YES
liondani-linux-1 * XTS5mJjufSgJWmm9yNyWfAAoZSUKFfxphzmvYZzY7WtDHTDQ15bwL 2014-07-05T14:29:45 NO 0 YES
liondani-linux-2 * XTS7ackbkNREQgzVK9GJrTuMNGxigH2F7qQbf5ePnGU4hH4DyPDJ3 2014-07-05T14:33:00 NO 0 YES
liondaniel XTS6d5fuzezqyaBqzSJY6ityNWV59nGxoaf3ydHLPhFZQGKpuSfhP NO NO 0 N/A
user123 XTS747iL3PPsWy5ZyxjXVArdkv8hRCEZMFwudkYsnjsUb3dX6Znjj NO NO 0 N/A
so it is better if someone don't use false or true that an error message will appear
or the best solution is that when someone not type false or true , then by default should true be assigned...
Quote from: GregGozzo on July 04, 2014, 09:35:49 PM
Quote from: GregGozzo on July 04, 2014, 06:18:25 PM
Still can't get the Windows GUI to run for the life of me. It just opens the splash page with bitsharesXT logo and then closes 3 seconds later. I have tried opening my firewall, ports, downloading in different browsers and nothing will get this going.
I am not sure if it's a comparability issue or if my computer is blocking something. I think Cass said he was having the same problem for one of his Windows laptops.
Any ideas?
I am using Windows 7 64bit.
Anyone?
No more crashing here after installed with the "run as administrator" option - found the pw and is working now nearly flawless.
Quote from: liondani on July 05, 2014, 05:04:14 AM
On linux everything worked fine with wallet creation from json file...
On win gui I tried to export a json file:
>> wallet_export_to_json liondani_backup_json
OK
I don't find the file anywhere.
Is it somewhere or is it a false message and actualy never created?
Anybody?
PS I Used Guis Console...
With the latest GUI you will be able to include links like:
xts:delegate_name/approve => Open wallet and ask user if they would like to approve delegate name.
xts:delegate_name/disapprove => Open wallet and ask user if they would like to remove approval of a delegate name.
xtd:private_name:XTSAccountKeyBase58 => automatically add an account/private key
xts:account_name/pay?amount=...,to=...
xts:private_account_name:XTSKey.../pay?amount=...,to=...
This will help all of you delegates direct users to the action you would like them to take.
+5%
see my signature
edit: not working in forum
Quote from: xeroc on July 05, 2014, 04:25:54 PM
+5%
see my signature
Remove the http:// from the front of your link...
Quote from: bytemaster on July 05, 2014, 04:28:37 PM
Quote from: xeroc on July 05, 2014, 04:25:54 PM
+5%
see my signature
Remove the http:// from the front of your link...
The board added it :( cant remove :(
Quote from: xeroc on July 05, 2014, 04:29:30 PM
Quote from: bytemaster on July 05, 2014, 04:28:37 PM
Quote from: xeroc on July 05, 2014, 04:25:54 PM
+5%
see my signature
Remove the http:// from the front of your link...
The board added it :( cant remove :(
what you mean!? Sry just dip into discussion now again! http:// on signature!?
Quote from: liondani on July 05, 2014, 03:24:34 PM
Quote from: liondani on July 05, 2014, 05:04:14 AM
On linux everything worked fine with wallet creation from json file...
On win gui I tried to export a json file:
>> wallet_export_to_json liondani_backup_json
OK
I don't find the file anywhere.
Is it somewhere or is it a false message and actualy never created?
Anybody?
PS I Used Guis Console...
on bitshares_toolkit root data dir ... but you should save it as <yourfilename>.json i guess
see
Quote from: cass on July 04, 2014, 09:34:24 AM
Quote from: betax on July 04, 2014, 09:25:51 AM
Don't worry my delegate is producing blocks at the moment, just vote me up.
Thanks!
Ill spin up an ubuntu VM and see if I can recover the wallet.
for backup your wallet and recovering!
wallet_export_to_json <filename>.json
wallet_create_from_json <filename>.json
.json file is saved on bitshares_toolkit root layer
This helps me a lot! Hope it helps you too
you're using windows, right!?
>>> wallet_list_unspent_balances
BALANCE OWNER VOTE
--------------------------------------------------------------------------------------------------------------------------
10.00000 XTS XTSLGQGRwandP7ZyVGRUJcApTMgd8dsg2cd610 assert_exception: Assert Exception
!"unimplemented condition type":
{}
th_a cli.cpp:1065 print_unspent_balances
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "58b7e7c6d361a9af34cf5d99e1df33d1d2100feb",
"bitshares_toolkit_revision_age": "16 hours ago",
"fc_revision": "ace06d775c285673d4ade7683e332095d2440646",
"fc_revision_age": "22 hours ago",
"compile_date": "compiled on Jul 5 2014 at 10:13:26"
}
Quote from: bitcoinerS on July 05, 2014, 07:52:46 PM
>>> wallet_list_unspent_balances
BALANCE OWNER VOTE
--------------------------------------------------------------------------------------------------------------------------
10.00000 XTS XTSLGQGRwandP7ZyVGRUJcApTMgd8dsg2cd610 assert_exception: Assert Exception
!"unimplemented condition type":
{}
th_a cli.cpp:1065 print_unspent_balances
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "58b7e7c6d361a9af34cf5d99e1df33d1d2100feb",
"bitshares_toolkit_revision_age": "16 hours ago",
"fc_revision": "ace06d775c285673d4ade7683e332095d2440646",
"fc_revision_age": "22 hours ago",
"compile_date": "compiled on Jul 5 2014 at 10:13:26"
}
We'll get to it..: https://github.com/BitShares/bitshares_toolkit/issues/330
Quote from: liondani on July 05, 2014, 04:23:57 AM
Quote from: vikram on July 05, 2014, 04:13:39 AM
Quote from: liondani on July 05, 2014, 04:08:43 AM
Quote from: vikram on July 05, 2014, 04:06:53 AM
Quote from: liondani on July 05, 2014, 04:04:13 AM
Before I delete all directories
I made a wallet backup using command:
"wallet_export_to_json"
Then after I rebuilded the bitshares_toolkit etc.
I tried to create my wallet from the json file I had but these error occured:
(wallet closed) >>> wallet_create_from_json Dry7_050714
wallet_name: liondani
imported_wallet_passphrase: ***********
10 assert_exception: Assert Exception
fc::exists( filename ):
{}
th_a wallet.cpp:812 create_from_json
{"filename":"Dry7_050714","wallet_name":"liondani"}
th_a wallet.cpp:830 create_from_json
{}
th_a common_api_client.cpp:579 wallet_create_from_json
{"command":"wallet_create_from_json"}
th_a cli.cpp:538 execute_command
any suggestions ? ::)
Are you sure you do not have a wallet named 'liondani' already? The output of 'wallet_list' does not show anything?
I am sure!
(wallet closed) >>> wallet_list
No wallets found.
Actually this is the error for when the specified JSON file cannot be found (I know we need a better error message). Are you absolutely sure you are entering the correct filename to import from?
SOLVED!
You are right I typed Dry7_050714 instead of dry7_050714
Sorry for freaking you out :P
Thanks ;)
PS As you said a better error message would be helpful
Slightly improved error message done: https://github.com/BitShares/bitshares_toolkit/commit/c1a6602bcc95efba92c826578b1946113db674ad
Quote from: liondani on July 05, 2014, 02:48:34 PM
when I give the commands:
wallet_approve_delegate liondani
wallet_approve_delegate liondani true
both times the result message is: "ok"
but in reality it approves only with the second command (+true)!
look please....
wallet_approve_delegate liondani (without true)
liondani (unlocked) >>> wallet_approve_delegate liondani
OK
liondani (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVED BLOCK PRODUCTION ENABLED
liondani * XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv 2014-07-01T22:37:45 NO 0 YES
liondani-linux * XTS7kn3gC9d6iKeFxieMj2Sf5PSLuerYZZFzGBQC7Ktu2p1dsyGGE 2014-07-02T00:26:15 NO 0 YES
liondani-linux-1 * XTS5mJjufSgJWmm9yNyWfAAoZSUKFfxphzmvYZzY7WtDHTDQ15bwL 2014-07-05T14:29:45 NO 0 YES
liondani-linux-2 * XTS7ackbkNREQgzVK9GJrTuMNGxigH2F7qQbf5ePnGU4hH4DyPDJ3 2014-07-05T14:33:00 NO 0 YES
liondaniel XTS6d5fuzezqyaBqzSJY6ityNWV59nGxoaf3ydHLPhFZQGKpuSfhP NO NO 0 N/A
user123 XTS747iL3PPsWy5ZyxjXVArdkv8hRCEZMFwudkYsnjsUb3dX6Znjj NO NO 0 N/A
wallet_approve_delegate liondani true
liondani (unlocked) >>> wallet_approve_delegate liondani true
OK
liondani (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVED BLOCK PRODUCTION ENABLED
liondani * XTS7DcP75mjsqxMSKUjoS7pKZQd6ZVgJcE2LbJSyApHAjDEhT7ijv 2014-07-01T22:37:45 NO 1 YES
liondani-linux * XTS7kn3gC9d6iKeFxieMj2Sf5PSLuerYZZFzGBQC7Ktu2p1dsyGGE 2014-07-02T00:26:15 NO 0 YES
liondani-linux-1 * XTS5mJjufSgJWmm9yNyWfAAoZSUKFfxphzmvYZzY7WtDHTDQ15bwL 2014-07-05T14:29:45 NO 0 YES
liondani-linux-2 * XTS7ackbkNREQgzVK9GJrTuMNGxigH2F7qQbf5ePnGU4hH4DyPDJ3 2014-07-05T14:33:00 NO 0 YES
liondaniel XTS6d5fuzezqyaBqzSJY6ityNWV59nGxoaf3ydHLPhFZQGKpuSfhP NO NO 0 N/A
user123 XTS747iL3PPsWy5ZyxjXVArdkv8hRCEZMFwudkYsnjsUb3dX6Znjj NO NO 0 N/A
so it is better if someone don't use false or true that an error message will appear
or the best solution is that when someone not type false or true , then by default should true be assigned...
Done: https://github.com/BitShares/bitshares_toolkit/commit/6abc0803dca9aadb0376327c014c4f81e6d88acb
I'm a newbee, that would like to learn how to use this Dry Run stuff. Is there by any chance a simple step by step guide a newbee could follow anywhere?
Here's one question to start with:
Quote from: bytemaster on July 01, 2014, 09:14:47 PM
Win GUI
http://www.bitshares.org/BitSharesXT-0.0.8.exe (http://www.bitshares.org/BitSharesXT-0.0.8.exe)
Mac GUI
http://www.bitshares.org/BitSharesXT-0.0.9.dmg (http://www.bitshares.org/BitSharesXT-0.0.9.dmg)
What is the significance of the fact that the Win version is crossed out?
I don't have a mac system, only windows. Is this not the binary I want to work with?
Brent
Quote from: Brent.Allsop on July 06, 2014, 12:43:38 AM
I'm a newbee, that would like to learn how to use this Dry Run stuff. Is there by any chance a simple step by step guide a newbee could follow anywhere?
Here's one question to start with:
Quote from: bytemaster on July 01, 2014, 09:14:47 PM
Win GUI
http://www.bitshares.org/BitSharesXT-0.0.8.exe (http://www.bitshares.org/BitSharesXT-0.0.8.exe)
Mac GUI
http://www.bitshares.org/BitSharesXT-0.0.9.dmg (http://www.bitshares.org/BitSharesXT-0.0.9.dmg)
What is the significance of the fact that the Win version is crossed out?
I don't have a mac system, only windows. Is this not the binary I want to work with?
Brent
you could work with v0.0.8 the last days now because of a hard fork and too many improvements on the bitshares toolkit source code it is better to wait version 0.0.9 ... it could be a matter of hours... everything is moving fast lately :)
sorry for not producing blocks. my client is not able to connect to more than 2 peers. what can i do to fix this?
nvm, got it working using the nodes that toast posted earlier
I import my PTS private key to windows clints ,but no balance in the accounts , who can help me thanks
Thank you to everyone that has voted tor-delegate up. Just a little bit further and we will get to see if we can reliably produce blocks through a tor connection.
wallet (unlocked) >>> blockchain_get_delegates 108 1
ID NAME (* next) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
------------------------------------------------------------------------------------------------------------------------
392 tor-delegate 0.0051560135 % 0 0 -nan % 100 % 0.00000 XTS NONE
wallet (unlocked) >>>
Quote from: puppies on July 06, 2014, 06:14:08 AM
Thank you to everyone that has voted tor-delegate up. Just a little bit further and we will get to see if we can reliably produce blocks through a tor connection.
wallet (unlocked) >>> blockchain_get_delegates 108 1
ID NAME (* next) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
------------------------------------------------------------------------------------------------------------------------
392 tor-delegate 0.0051560135 % 0 0 -nan % 100 % 0.00000 XTS NONE
wallet (unlocked) >>>
liondani (unlocked) >>> wallet_approve_delegate tor-delegate true
OK
I have significant amounts of connection requests from 61.177.35.218.
The following message is repeated numerous times:
20140706T110138.922728 th_a accept_loop ] accepted inbound connection from 61.177.35.218:64332 node.cpp:2446
20140706T110138.935862 th_a accept_connection ] established inbound connection from 61.177.35.218:64332, sending hello peer_connection.cpp:53
20140706T110139.002767 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.002809 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.002843 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.002864 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.002892 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.002912 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.002940 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.002959 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.002986 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003006 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003032 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003052 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003079 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003099 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003126 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003145 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003225 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003247 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003274 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003294 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003321 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003341 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003368 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003387 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003414 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003434 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003469 th_a terminate_inactive_c ] Sending a keepalive message to peer 89.231.94.1:58089 who hasn't sent us any messages in the last 18 seconds node.cpp:905
20140706T110140.542476 th_a read_loop ] disconnected 11 eof_exception: End Of File
End of file
{"message":"End of file"}
asio asio.cpp:22 read_write_handler
{"len":16}
th_a stcp_socket.cpp:73 readsome message_oriented_connection.cpp:144
20140706T110140.542517 th_a on_connection_closed ] Remote peer 61.177.35.218:64332 closed their connection to us node.cpp:1986
20140706T110140.861861 th_a accept_loop ] accepted inbound connection from 61.177.35.218:64353 node.cpp:2446
emski@myServer:~/bitsharesnode/bitshares_toolkit/programs/client$ netstat -an | grep 61.177.35.218
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56467 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55809 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56255 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56847 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56911 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57203 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56377 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55852 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56635 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56956 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56510 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56443 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56659 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57042 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55705 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56203 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56051 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56132 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56704 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55915 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55644 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55871 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56744 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56529 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55831 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55768 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56090 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57130 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57022 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57156 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55788 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56348 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56489 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57108 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56786 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56015 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57086 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55528 SYN_SENT
tcp 0 369 myIP.myIP.myIP.myIP:8701 61.177.35.218:60359 ESTABLISHED
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57181 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56806 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55726 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56280 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56681 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55502 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57000 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56178 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55680 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56154 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56614 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55586 SYN_SENT
Also each second i get the following message
--- there are now 30 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 30 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 30 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 30 active connections to the p2p network
In the logs it says I've disconnected some peers due to timeout.
Is this a bug?
Unable to open database /home/ubuntu/.BitSharesXTS/chain/index/undo_state_db
Corruption: 21 missing files; e.g.: /home/ubuntu/.BitSharesXTS/chain/index/undo_state_db/000037.sst
{"db":"/home/ubuntu/.BitSharesXTS/chain/index/undo_state_db","msg":"Corruption: 21 missing files; e.g.: /home/ubuntu/.BitSharesXTS/chain/index/undo_state_db/000037.sst"}
th_a level_map.hpp:46 open
{"data_dir":"/home/ubuntu/.BitSharesXTS/chain"}
th_a chain_database.cpp:244 open_database
{"data_dir":"/home/ubuntu/.BitSharesXTS/chain"}
th_a chain_database.cpp:988 open
{"data_dir":"/home/ubuntu/.BitSharesXTS"}
th_a client.cpp:1270 open
any idea how to solve this issue!? I didn't check up all pages in Dry 7 discussion here ...
Quote from: cass on July 06, 2014, 01:11:45 PM
Unable to open database /home/ubuntu/.BitSharesXTS/chain/index/undo_state_db
Corruption: 21 missing files; e.g.: /home/ubuntu/.BitSharesXTS/chain/index/undo_state_db/000037.sst
{"db":"/home/ubuntu/.BitSharesXTS/chain/index/undo_state_db","msg":"Corruption: 21 missing files; e.g.: /home/ubuntu/.BitSharesXTS/chain/index/undo_state_db/000037.sst"}
th_a level_map.hpp:46 open
{"data_dir":"/home/ubuntu/.BitSharesXTS/chain"}
th_a chain_database.cpp:244 open_database
{"data_dir":"/home/ubuntu/.BitSharesXTS/chain"}
th_a chain_database.cpp:988 open
{"data_dir":"/home/ubuntu/.BitSharesXTS"}
th_a client.cpp:1270 open
any idea how to solve this issue!? I didn't check up all pages in Dry 7 discussion here ...
solved with
rm -r ~/.BitSharesXTSsry pls ignore last message...
Quote from: liondani on July 06, 2014, 02:01:08 AM
Quote from: Brent.Allsop on July 06, 2014, 12:43:38 AM
I'm a newbee, that would like to learn how to use this Dry Run stuff. Is there by any chance a simple step by step guide a newbee could follow anywhere?
Here's one question to start with:
Quote from: bytemaster on July 01, 2014, 09:14:47 PM
Win GUI
http://www.bitshares.org/BitSharesXT-0.0.8.exe (http://www.bitshares.org/BitSharesXT-0.0.8.exe)
Mac GUI
http://www.bitshares.org/BitSharesXT-0.0.9.dmg (http://www.bitshares.org/BitSharesXT-0.0.9.dmg)
What is the significance of the fact that the Win version is crossed out?
I don't have a mac system, only windows. Is this not the binary I want to work with?
Brent
you could work with v0.0.8 the last days now because of a hard fork and too many improvements on the bitshares toolkit source code it is better to wait version 0.0.9 ... it could be a matter of hours... everything is moving fast lately :)
It has been 2 days now :(
"blockchain_average_delegate_participation": 69.178082191780817,
and even my best delegates are out of the top 101... :'(
wallet_approve_delegate liondani true
wallet_approve_delegate liondani-linux true
thanks guys ;)
Alright, Looks like I should be able to get some votes.
Please vote "wallet_approve_delegate smoo true"
Thanks!
Quote from: plazmashart on July 06, 2014, 08:53:14 PM
Alright, Looks like I should be able to get some votes.
Please vote "wallet_approve_delegate smoo true"
Thanks!
done pls - vote for also -- look at my signature ;)
Quick question about the win binary wallet. I enter my password, and it says its incorrect, but allows me access. Is this a known issue?
Quote from: cass on July 06, 2014, 08:58:05 PM
Quote from: plazmashart on July 06, 2014, 08:53:14 PM
Alright, Looks like I should be able to get some votes.
Please vote "wallet_approve_delegate smoo true"
Thanks!
done pls - vote for also -- look at my signature ;)
Done
Quote from: vlight on July 06, 2014, 09:02:04 PM
Apparently, some transactions became "UNKNOWN". These were mostly sent XTS to various people here on the forum. I'm going to make a fresh install.
wallet-1 (unlocked) >>> wallet_account_transaction_history
BLK.TRX TIMESTAMP FROM TO AMOUNT FEE MEMO ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------
376.1 2014-07-01T22:22:30 XTS6aYKzgat1fShq... light 1,000.00000 XTS 0.00000 XTS cab14a52
392.1 2014-07-01T22:26:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 489dd448
665.24 2014-07-01T23:37:15 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS edc4a98b
3356.20 2014-07-02T11:38:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS a4e18bea
3420.20 2014-07-02T11:57:45 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS a3121764
3430.15 2014-07-02T12:00:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 8e6ecab4
3476.15 2014-07-02T12:13:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS f954153b
3491.0 2014-07-02T12:18:00 free light 5.00000 XTS 0.00000 XTS thx 0dfbac8c
3492.0 2014-07-02T12:18:15 free light 200.0 BTC 0.00000 XTS 1b3db9f9
3517.0 2014-07-02T12:25:45 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 040795aa
5214.0 2014-07-02T20:01:15 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 40f082bd
5756.0 2014-07-02T22:25:00 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS f321b8a0
PENDING 2014-07-03T13:09:30 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 589db86c
PENDING 2014-07-03T13:10:15 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 9d57b0b8
10850.0 2014-07-04T10:24:45 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 71f94258
10864.0 2014-07-04T10:28:15 UNKNOWN UNKNOWN 0.00000 XTS 0.00000 XTS 3d63b615
11005.0 2014-07-04T11:07:30 bitcoiners light 100. BOMB 0.00000 XTS bombs for you 8cce083c
12947.0 2014-07-04T20:00:31 light tor-delegate 5.00000 XTS 0.10000 XTS 303f9c86
20080.10 2014-07-06T09:11:08 light tor-delegate 5.00000 XTS 0.10000 XTS ef1fb3b5
22131.0 2014-07-06T20:17:19 light liondani 5.00000 XTS 0.10000 XTS 3e5ed038
22132.0 2014-07-06T20:17:39 light liondani-linux 5.00000 XTS 0.10000 XTS 2bb62b8d
22242.0 2014-07-06T20:54:51 light smoo 5.00000 XTS 0.10000 XTS 3accf0f0
This would happen if for some reason you lost all of your unregistered accounts.
Quote from: liondani on July 06, 2014, 06:50:40 PM
"blockchain_average_delegate_participation": 69.178082191780817,
and even my best delegates are out of the top 101... :'(
wallet_approve_delegate liondani true
wallet_approve_delegate liondani-linux true
thanks guys ;)
Done!
I'm just outside as well, 110 or so, pls vote for me!
Quote from: vikram on July 05, 2014, 08:07:52 PM
Quote from: bitcoinerS on July 05, 2014, 07:52:46 PM
>>> wallet_list_unspent_balances
BALANCE OWNER VOTE
--------------------------------------------------------------------------------------------------------------------------
10.00000 XTS XTSLGQGRwandP7ZyVGRUJcApTMgd8dsg2cd610 assert_exception: Assert Exception
!"unimplemented condition type":
{}
th_a cli.cpp:1065 print_unspent_balances
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "58b7e7c6d361a9af34cf5d99e1df33d1d2100feb",
"bitshares_toolkit_revision_age": "16 hours ago",
"fc_revision": "ace06d775c285673d4ade7683e332095d2440646",
"fc_revision_age": "22 hours ago",
"compile_date": "compiled on Jul 5 2014 at 10:13:26"
}
We'll get to it..: https://github.com/BitShares/bitshares_toolkit/issues/330
wallet_list_unspent_balances has been removed in favor of wallet_account_balance: https://github.com/BitShares/bitshares_toolkit/commit/99645181d06b54909c75d5905a7ef0d4ead415d2
Quote from: puppies on July 06, 2014, 06:14:08 AM
Thank you to everyone that has voted tor-delegate up. Just a little bit further and we will get to see if we can reliably produce blocks through a tor connection.
wallet (unlocked) >>> blockchain_get_delegates 108 1
ID NAME (* next) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
------------------------------------------------------------------------------------------------------------------------
392 tor-delegate 0.0051560135 % 0 0 -nan % 100 % 0.00000 XTS NONE
wallet (unlocked) >>>
Should no longer print NaN for invalid percentages: https://github.com/BitShares/bitshares_toolkit/commit/257686e214cc39fe99b2546043ad61fcfd767047
what's wrong with this log?
mywallet (locked) >>> unlock
timeout: 999999
passphrase:
10 assert_exception: Assert Exceptionck: 0/2841
oissuer.valid():
{}
th_a wallet.cpp:429 scan_create_asset
{"start":19803,"end":22644}
th_a wallet.cpp:1242 scan_chain
{"timeout_seconds":999999}
th_a wallet.cpp:860 unlock
{}
th_a common_api_client.cpp:659 wallet_unlock
{"command":"unlock"}
th_a cli.cpp:538 execute_command
mywallet (unlocked) >>>
mywallet (unlocked) >>> wallet_rescan_blockchain ==========================================================10 assert_exception: Assert Exception
oissuer.valid():
{}
th_a wallet.cpp:429 scan_create_asset
{"start":1,"end":4294967295}
th_a wallet.cpp:1242 scan_chain
mywallet (unlocked) >>>
Quote from: Webber on July 06, 2014, 11:10:11 PM
what's wrong with this log?
mywallet (locked) >>> unlock
timeout: 999999
passphrase:
10 assert_exception: Assert Exceptionck: 0/2841
oissuer.valid():
{}
th_a wallet.cpp:429 scan_create_asset
{"start":19803,"end":22644}
th_a wallet.cpp:1242 scan_chain
{"timeout_seconds":999999}
th_a wallet.cpp:860 unlock
{}
th_a common_api_client.cpp:659 wallet_unlock
{"command":"unlock"}
th_a cli.cpp:538 execute_command
mywallet (unlocked) >>>
mywallet (unlocked) >>> wallet_rescan_blockchain ==========================================================10 assert_exception: Assert Exception
oissuer.valid():
{}
th_a wallet.cpp:429 scan_create_asset
{"start":1,"end":4294967295}
th_a wallet.cpp:1242 scan_chain
mywallet (unlocked) >>>
Likely a bug in the wallet... :)
what's the plane, do we need next dry run?
Win GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe (http://www.bitshares.org/BitSharesXT-0.0.9.exe)
Quote from: bytemaster on July 07, 2014, 12:30:03 AM
Quote from: Webber on July 06, 2014, 11:10:11 PM
what's wrong with this log?
mywallet (locked) >>> unlock
timeout: 999999
passphrase:
10 assert_exception: Assert Exceptionck: 0/2841
oissuer.valid():
{}
th_a wallet.cpp:429 scan_create_asset
{"start":19803,"end":22644}
th_a wallet.cpp:1242 scan_chain
{"timeout_seconds":999999}
th_a wallet.cpp:860 unlock
{}
th_a common_api_client.cpp:659 wallet_unlock
{"command":"unlock"}
th_a cli.cpp:538 execute_command
mywallet (unlocked) >>>
mywallet (unlocked) >>> wallet_rescan_blockchain ==========================================================10 assert_exception: Assert Exception
oissuer.valid():
{}
th_a wallet.cpp:429 scan_create_asset
{"start":1,"end":4294967295}
th_a wallet.cpp:1242 scan_chain
mywallet (unlocked) >>>
Likely a bug in the wallet... :)
I believe this is fixed.
Quote from: alt on July 07, 2014, 01:58:55 AM
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.
Quote from: bytemaster on July 07, 2014, 02:06:37 AM
Quote from: alt on July 07, 2014, 01:58:55 AM
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?
XTS5Dj1MxP7UNwHF8TRG8QSFVL3wouaWnHDvSfjPpQ6ZdoQHiXskQ
some funds pls ..thx
Quote from: heyD on July 07, 2014, 02:30:29 AM
Quote from: bytemaster on July 07, 2014, 02:06:37 AM
Quote from: alt on July 07, 2014, 01:58:55 AM
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.
Quote from: bytemaster on July 07, 2014, 02:46:04 AM
Quote from: heyD on July 07, 2014, 02:30:29 AM
Quote from: bytemaster on July 07, 2014, 02:06:37 AM
Quote from: alt on July 07, 2014, 01:58:55 AM
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.
+5% +5%
Quote from: bytemaster on July 07, 2014, 02:46:04 AM
Quote from: heyD on July 07, 2014, 02:30:29 AM
Quote from: bytemaster on July 07, 2014, 02:06:37 AM
Quote from: alt on July 07, 2014, 01:58:55 AM
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? :)
Quote from: svk on July 06, 2014, 09:15:13 PM
I'm just outside as well, 110 or so, pls vote for me!
liondani (unlocked) >>> wallet_approve_delegate svk-delegate true
OK
Quote from: alt on July 07, 2014, 03:09:27 AM
Quote from: bytemaster on July 07, 2014, 02:46:04 AM
Quote from: heyD on July 07, 2014, 02:30:29 AM
Quote from: bytemaster on July 07, 2014, 02:06:37 AM
Quote from: alt on July 07, 2014, 01:58:55 AM
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.
+5%
What's relationship between 3I and DACs Unlimited ？ btc38 add bts/btc trade just now.
Quote from: bytemaster on July 07, 2014, 02:01:35 AM
Win GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe (http://www.bitshares.org/BitSharesXT-0.0.9.exe)
last block synced 4562 to stop
Quote from: gyhy on July 07, 2014, 03:24:04 AM
Quote from: bytemaster on July 07, 2014, 02:01:35 AM
Win GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe (http://www.bitshares.org/BitSharesXT-0.0.9.exe)
last block synced 4562 to stop
me too
Quote from: yangsbo on July 07, 2014, 03:25:39 AM
Quote from: gyhy on July 07, 2014, 03:24:04 AM
Quote from: bytemaster on July 07, 2014, 02:01:35 AM
Win GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe (http://www.bitshares.org/BitSharesXT-0.0.9.exe)
last block synced 4562 to stop
me too
Me too....
Quote from: bytemaster on July 07, 2014, 03:27:12 AM
Quote from: yangsbo on July 07, 2014, 03:25:39 AM
Quote from: gyhy on July 07, 2014, 03:24:04 AM
Quote from: bytemaster on July 07, 2014, 02:01:35 AM
Win GUI
http://www.bitshares.org/BitSharesXT-0.0.9.exe (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:
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:
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.
Quote from: bytemaster on July 07, 2014, 03:18:41 AM
Quote from: alt on July 07, 2014, 03:09:27 AM
Quote from: bytemaster on July 07, 2014, 02:46:04 AM
Quote from: heyD on July 07, 2014, 02:30:29 AM
Quote from: bytemaster on July 07, 2014, 02:06:37 AM
Quote from: alt on July 07, 2014, 01:58:55 AM
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.
DAC Unlimited is trusted.
Quote from: bytemaster on July 07, 2014, 03:45:02 AM
DAC Unlimited is trusted.
Got it!
The show is beginning ;D
Quote from: bytemaster on July 07, 2014, 03:18:41 AM
Quote from: alt on July 07, 2014, 03:09:27 AM
Quote from: bytemaster on July 07, 2014, 02:46:04 AM
Quote from: heyD on July 07, 2014, 02:30:29 AM
Quote from: bytemaster on July 07, 2014, 02:06:37 AM
Quote from: alt on July 07, 2014, 01:58:55 AM
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?
on a russian moon base
Quote from: liondani on July 07, 2014, 04:00:07 AM
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 ??? )
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
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
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
Quote from: onceuponatime on July 07, 2014, 03:48:44 AM
Launching in Hong Kong or mainland?
Hong Kong.
HK is far more open mainland.
"blockchain_average_delegate_participation": 39.763779527559052,
39% ? What is happening guys ?
I have seven connections....
I am on block 23642
liondani (unlocked) >>> info
{
"blockchain_head_block_num": 23642,
"blockchain_head_block_age": "14 seconds old",
"blockchain_head_block_timestamp": "20140707T053600",
"blockchain_average_delegate_participation": 40.562248995983936,
"blockchain_delegate_pay_rate": 70568,
"blockchain_blocks_left_in_round": 93,
"blockchain_confirmation_requirement": 302,
"blockchain_share_supply": 199999113138786,
"blockchain_random_seed": "afbbc2be73040e591dce84c9f540053feb4559ad",
"blockchain_database_version": 109,
"blockchain_version": 104,
"network_num_connections": 7,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140707T053614",
"ntp_error": -0.072475999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "11 days in the future",
"wallet_unlocked_until_timestamp": "20140718T083454",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 101
}
vote me up please ;)
Quote from: liondani on July 07, 2014, 05:38:01 AM
"blockchain_average_delegate_participation": 39.763779527559052,
39% ? What is happening guys ?
Theres a bug thats causes users to be stuck on block 4562 when resyncing .. no idea if this is fixed already
Quote from: emski on July 06, 2014, 11:25:50 AM
I have significant amounts of connection requests from 61.177.35.218.
The following message is repeated numerous times:
20140706T110138.922728 th_a accept_loop ] accepted inbound connection from 61.177.35.218:64332 node.cpp:2446
20140706T110138.935862 th_a accept_connection ] established inbound connection from 61.177.35.218:64332, sending hello peer_connection.cpp:53
20140706T110139.002767 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.002809 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.002843 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.002864 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.002892 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.002912 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.002940 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.002959 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.002986 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003006 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003032 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003052 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003079 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003099 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003126 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003145 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003225 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003247 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003274 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003294 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003321 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003341 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003368 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003387 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003414 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140706T110139.003434 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140706T110139.003469 th_a terminate_inactive_c ] Sending a keepalive message to peer 89.231.94.1:58089 who hasn't sent us any messages in the last 18 seconds node.cpp:905
20140706T110140.542476 th_a read_loop ] disconnected 11 eof_exception: End Of File
End of file
{"message":"End of file"}
asio asio.cpp:22 read_write_handler
{"len":16}
th_a stcp_socket.cpp:73 readsome message_oriented_connection.cpp:144
20140706T110140.542517 th_a on_connection_closed ] Remote peer 61.177.35.218:64332 closed their connection to us node.cpp:1986
20140706T110140.861861 th_a accept_loop ] accepted inbound connection from 61.177.35.218:64353 node.cpp:2446
emski@myServer:~/bitsharesnode/bitshares_toolkit/programs/client$ netstat -an | grep 61.177.35.218
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56467 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55809 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56255 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56847 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56911 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57203 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56377 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55852 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56635 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56956 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56510 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56443 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56659 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57042 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55705 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56203 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56051 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56132 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56704 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55915 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55644 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55871 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56744 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56529 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55831 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55768 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56090 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57130 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57022 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57156 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55788 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56348 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56489 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57108 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56786 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56015 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57086 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55528 SYN_SENT
tcp 0 369 myIP.myIP.myIP.myIP:8701 61.177.35.218:60359 ESTABLISHED
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57181 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56806 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55726 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56280 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56681 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55502 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:57000 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56178 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55680 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56154 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:56614 SYN_SENT
tcp 0 1 myIP.myIP.myIP.myIP:8701 61.177.35.218:55586 SYN_SENT
Also each second i get the following message
--- there are now 30 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 30 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 30 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 30 active connections to the p2p network
In the logs it says I've disconnected some peers due to timeout.
Is this a bug?
Any comments on this?
That user opens significant amount of connections per second.
I get connection errors for other peers after some of failed connections from that host.
It is either a serious bug or someone tries to exploit this.
PS: Anyone recognizes 61.177.35.218 as his own?
forks are back again...
liondani (unlocked) >>> list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
5512
4749f3a468ad4257695875f643907f49fb1f015d spartako9 35 8722 2014-07-02T21:20:30 196191 YES YES
601ac7e2cc1266c7cdcb320401311efab9a82cc6 happyshares-2 0 182 2014-07-06T18:36:00 0 N/A NO
14732
60d40aa4832877a005a9e73b9736e4ac387d870e clout6 0 182 2014-07-05T04:14:00 0 YES YES
8758e625be44eda07bab115689c19a31e36b9b29 emski-delegate3 0 182 2014-07-06T06:08:15 0 N/A NO
19305
e70d4494c86eebfb32a4ddb3cf840d65fa5b5f21 happyshares-2 22 5550 2014-07-06T05:17:45 0 YES YES
fd95363f0b244a047dd14e254ab31426547582ba delegate-baozi 0 182 2014-07-06T14:57:00 1 N/A NO
19476
a94a32fe87afcfa0137ead722627412f91fc0202 init6 24 6038 2014-07-06T06:09:45 3 YES YES
cb1f990676f4c08a940871d2c6493cc5464332be happyshares-1 0 182 2014-07-06T18:56:00 6 N/A NO
20875
d45eac91a48c6470167af53352055f0174cb7821 betax 0 182 2014-07-06T13:18:15 0 YES YES
c1546ce5107fd7740730605eddf5718ee6b1a621 happyshares-1 0 182 2014-07-06T18:59:00 1 N/A NO
21105
f5bc0338ad7a7f7dcc4ac182f4639c3106f182ce happyshares-2 0 182 2014-07-06T14:39:15 0 YES YES
66e83fd9261b4ab6a969f998829ddacb7961c9a2 malcolmjmr5 0 182 2014-07-06T16:14:154294967294 N/A NO
21806
c554ceef54ea9edd0a4d5b0666c69a6d0ec402fa bits 0 182 2014-07-06T18:19:45 0 YES YES
228dc23ed265e473221d78fc93e1fb1a0283aff1 happyshares-6 0 182 2014-07-06T19:00:15 0 N/A NO
21899
6b47771bd798c6ef4add1e5e8c35b62a7fee9e33 delegate-dragon 0 182 2014-07-06T18:56:00 0 YES YES
53186ffef818c8c9aa7323299db4b588a3f908c8 clout9 0 182 2014-07-06T18:56:30 0 N/A NO
Quote from: liondani on July 07, 2014, 06:34:55 AM
forks are back again...
liondani (unlocked) >>> list_forks
FORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
5512
4749f3a468ad4257695875f643907f49fb1f015d spartako9 35 8722 2014-07-02T21:20:30 196191 YES YES
601ac7e2cc1266c7cdcb320401311efab9a82cc6 happyshares-2 0 182 2014-07-06T18:36:00 0 N/A NO
14732
60d40aa4832877a005a9e73b9736e4ac387d870e clout6 0 182 2014-07-05T04:14:00 0 YES YES
8758e625be44eda07bab115689c19a31e36b9b29 emski-delegate3 0 182 2014-07-06T06:08:15 0 N/A NO
19305
e70d4494c86eebfb32a4ddb3cf840d65fa5b5f21 happyshares-2 22 5550 2014-07-06T05:17:45 0 YES YES
fd95363f0b244a047dd14e254ab31426547582ba delegate-baozi 0 182 2014-07-06T14:57:00 1 N/A NO
19476
a94a32fe87afcfa0137ead722627412f91fc0202 init6 24 6038 2014-07-06T06:09:45 3 YES YES
cb1f990676f4c08a940871d2c6493cc5464332be happyshares-1 0 182 2014-07-06T18:56:00 6 N/A NO
20875
d45eac91a48c6470167af53352055f0174cb7821 betax 0 182 2014-07-06T13:18:15 0 YES YES
c1546ce5107fd7740730605eddf5718ee6b1a621 happyshares-1 0 182 2014-07-06T18:59:00 1 N/A NO
21105
f5bc0338ad7a7f7dcc4ac182f4639c3106f182ce happyshares-2 0 182 2014-07-06T14:39:15 0 YES YES
66e83fd9261b4ab6a969f998829ddacb7961c9a2 malcolmjmr5 0 182 2014-07-06T16:14:154294967294 N/A NO
21806
c554ceef54ea9edd0a4d5b0666c69a6d0ec402fa bits 0 182 2014-07-06T18:19:45 0 YES YES
228dc23ed265e473221d78fc93e1fb1a0283aff1 happyshares-6 0 182 2014-07-06T19:00:15 0 N/A NO
21899
6b47771bd798c6ef4add1e5e8c35b62a7fee9e33 delegate-dragon 0 182 2014-07-06T18:56:00 0 YES YES
53186ffef818c8c9aa7323299db4b588a3f908c8 clout9 0 182 2014-07-06T18:56:30 0 N/A NO
I think these forks are harmless.
Have a test
XTS8UZeAgALwLhn84CfpqsL3CW1HRZEduQd5WGQGoNCJ7aan7GDE9
Thanks
Quote from: seusnow on July 07, 2014, 07:06:20 AM
Have a test
XTS8UZeAgALwLhn84CfpqsL3CW1HRZEduQd5WGQGoNCJ7aan7GDE9
Thanks
sent
23767.3 2014-07-07T07:16:30 baozi seusnowa 100.00000 XTS 0.10000 XTS test fund 685c8b19
Quote from: bytemaster on July 07, 2014, 03:32:32 AM
We are stuck on this block because:
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:
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.
What to do about this?!
I just wake up and I find my client with delegates with 0 connections, this is the console log that I found:
Peer 146.185.186.245:56182 disconnected us: You offered us a block that we reject as invalid
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 30 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 33 active connections to the p2p network
--- there are now 0 active connections to the p2p network
I restarted the client and now I have 12 connections
EDIT:
emski suggest me to check my p2p.log and I found similar log error (the ip address is the same):
20140707T030112.485619 th_a accept_loop ] accepted inbound connection from 61.177.35.218:64623 node.cpp:2446
20140707T030112.487557 th_a accept_connection ] established inbound connection from 61.177.35.218:64623, sending hello peer_connection.cpp:53
20140707T030113.765456 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140707T030113.765514 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140707T030113.765551 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140707T030113.765574 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140707T030113.765605 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140707T030113.765627 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140707T030113.765656 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140707T030113.765677 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140707T030113.765707 th_a terminate_inactive_c ] Forcibly disconnecting from handshaking peer due to inactivity of at least 5 seconds node.cpp:835
20140707T030113.765728 th_a terminate_inactive_c ] Peer's negotiating status: closing, bytes sent: 0, bytes received: 0 node.cpp:839
20140707T030113.765769 th_a terminate_inactive_c ] Sending a keepalive message to peer 89.231.94.1:56559 who hasn't sent us any messages in the last 18 seconds node.cpp:905
20140707T030113.765795 th_a terminate_inactive_c ] Sending a keepalive message to peer 188.138.107.159:47755 who hasn't sent us any messages in the last 18 seconds node.cpp:905
20140707T030114.687815 th_a read_loop ] disconnected 11 eof_exception: End Of File
End of file
{"message":"End of file"}
asio asio.cpp:22 read_write_handler
{"len":16}
th_a stcp_socket.cpp:73 readsome message_oriented_connection.cpp:144
Quote from: spartako on July 07, 2014, 07:29:18 AM
I just wake up and I find my client with delegates with 0 connections, this is the console log that I found:
Peer 146.185.186.245:56182 disconnected us: You offered us a block that we reject as invalid
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 30 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 31 active connections to the p2p network
--- there are now 32 active connections to the p2p network
--- there are now 33 active connections to the p2p network
--- there are now 0 active connections to the p2p network
I restarted the client and now I have 12 connections
Can you post a few nodes?
My Windows GUI is still locking up on its own :( Its still not unlocking properly, but it does when I use the Accounts tab on top.
Quote from: sumantso on July 07, 2014, 07:39:15 AM
Can you post a few nodes?
My Windows GUI is still locking up on its own :( Its still not unlocking properly, but it does when I use the Accounts tab on top.
Here you are a list of nodes not firewalled:
23.239.5.30:47400
202.96.137.243:8701
79.173.81.171:8764
wow,poor network now! What happening?
mywallet (unlocked) >>> blockchain_list_blocks
HEIGHT TIMESTAMP SIGNING DELEGATE # TXS SIZE TOTAL FEES LATENCY PROCESSING TIME
-------------------------------------------------------------------------------------------------------------------
23831 2014-07-07T07:58:30 scroodge 0 182 0.00000 XTS 0 0.012386
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
23830 2014-07-07T07:57:15 happyshares-4 0 182 0.00000 XTS 0 0.017685
N/A MISSED N/A N/A N/A N/A N/A N/A
23829 2014-07-07T07:56:45 bits 0 182 0.00000 XTS 1 0.012268
23828 2014-07-07T07:56:30 xeldal 0 182 0.00000 XTS 0 0.011529
23827 2014-07-07T07:56:15 spartako10 0 182 0.00000 XTS 0 0.012798
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
23826 2014-07-07T07:54:30 happyshares-9 0 182 0.00000 XTS 0 0.018675
23825 2014-07-07T07:54:15 spartako7 0 182 0.00000 XTS 0 0.012045
23824 2014-07-07T07:54:00 spartako1 0 182 0.00000 XTS 0 0.018131
23823 2014-07-07T07:53:45 richie-rich 0 182 0.00000 XTS 0 0.014996
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
23822 2014-07-07T07:51:45 spartako2 0 182 0.00000 XTS 0 0.012847
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
23821 2014-07-07T07:50:30 remember-the-titan 0 182 0.00000 XTS 0 0.013762
23820 2014-07-07T07:50:15 bts102 0 182 0.00000 XTS 0 0.014755
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
23819 2014-07-07T07:49:00 this-toast-is-so-fresh 0 182 0.00000 XTS 0 0.020328
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
23818 2014-07-07T07:48:15 lotto 0 182 0.00000 XTS 0 0.011272
23817 2014-07-07T07:48:00 spartako 0 182 0.00000 XTS 0 0.013373
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
23816 2014-07-07T07:47:15 blockchainer 0 182 0.00000 XTS 0 0.017503
23815 2014-07-07T07:47:00 webber-test6 0 182 0.00000 XTS 0 0.012647
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
N/A MISSED N/A N/A N/A N/A N/A N/A
23814 2014-07-07T07:46:00 how-many-delegates-will-you-... 0 182 0.00000 XTS 0 0.015117
N/A MISSED N/A N/A N/A N/A N/A N/A
23813 2014-07-07T07:45:30 smeagol 0 182 0.00000 XTS 0 0.011809
23812 2014-07-07T07:45:15 bitcoiners 0 182 0.00000 XTS 0 0.018123
mywallet (unlocked) >>> blockchain_get_security_state
{
"alert_level": "red",
"estimated_confirmation_seconds": 4545,
"participation_rate": 33.55481727574751
}
mywallet (unlocked) >>>
Quote from: Webber on July 07, 2014, 08:03:15 AM
wow,poor network now! What happening?
latest github master has a bug that makes client stuck on a block .. no idea when they will update that :(
Quote from: sumantso on July 07, 2014, 07:39:15 AM
QuoteMy Windows GUI is still locking up on its own :( Its still not unlocking properly, but it does when I use the Accounts tab on top.
Same here.
why my mac client always told me" wrong password "!I input it absolutely correct.
Quote from: lzr1900 on July 07, 2014, 09:57:30 AM
why my mac client always told me" wrong password "!I input it absolutely correct.
me too
input password ,then wrong password
you can use" go to account" into main windows
what's going on?
the security state turn to red alert!
Quote from: lzr1900 on July 07, 2014, 10:43:31 AM
what's going on?
the security state turn to red alert!
There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..
Quote from: xeroc on July 07, 2014, 10:49:03 AM
Quote from: lzr1900 on July 07, 2014, 10:43:31 AM
what's going on?
the security state turn to red alert!
There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..
～So that is what it is. thanks.
Quote from: xeroc on July 07, 2014, 10:49:03 AM
Quote from: lzr1900 on July 07, 2014, 10:43:31 AM
what's going on?
the security state turn to red alert!
There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..
Thx for the info, everything is stuck (new win7 gui & new git version)
Quote from: xeroc on July 07, 2014, 10:49:03 AM
Quote from: lzr1900 on July 07, 2014, 10:43:31 AM
what's going on?
the security state turn to red alert!
There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..
It is a good opportunity to act like we would on the real chain...
we can vote up delegates that successfully produced the last blocks and some stand-by delegates to test them out and take our votes back for delegates that lost the last blocks (even if they have over all great statistics)....
That action will be temporary until "blockchain_average_delegate_participation" is over 70% again for example.... When we know that we have the problem behind us (bug,attacks ddos etc.) we can vote again our favorite delegates....)
PS
It would be great if there was available a command that informed us which delegates has missed their last 5 blocks for example and which one produced successful their last 5...
so we could very quick make the "right" votes to bring the network to a better "blockchain_average_delegate_participation" percentage...
Quote from: liondani on July 07, 2014, 12:00:26 PM
Quote from: xeroc on July 07, 2014, 10:49:03 AM
Quote from: lzr1900 on July 07, 2014, 10:43:31 AM
what's going on?
the security state turn to red alert!
There's a sync bug in the git-master .. and a few delegates have a auto-make toolchain installed .. so they cant sync atm ..
It is a good opportunity to act like we would on the real chain...
we can vote up delegates that successfully produced the last blocks and some stand-by delegates to test them out and take our votes back for delegates that lost the last blocks (even if they have over all great statistics)....
That action will be temporary until "blockchain_average_delegate_participation" is over 70% again for example.... When we know that we have the problem behind us (bug,attacks ddos etc.) we can vote again our favorite delegates....)
PS
It would be great if there was available a command that informed us which delegates has missed their last 5 blocks for example and which one produced successful their last 5...
so we could very quick make the "right" votes to bring the network to a better "blockchain_average_delegate_participation" percentage...
I voted for you and now you are in the top 100:
334 liondani 0.0505564810 % 64 1 98.46 % 99 % 0.45385 XTS 14534
Do you have other delegates so I can vote for them?
It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.
Quote from: spartako on July 07, 2014, 01:27:49 PM
It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.
+5%
Also we need auto-voting to kick out non-producing delegates
Quote from: xeroc on July 07, 2014, 01:44:31 PM
Quote from: spartako on July 07, 2014, 01:27:49 PM
It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.
+5%
Also we need auto-voting to kick out non-producing delegates
+5%
Quote from: xeroc on July 07, 2014, 01:44:31 PM
Quote from: spartako on July 07, 2014, 01:27:49 PM
It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.
+5%
Also we need auto-voting to kick out non-producing delegates
Without negative votes that might be a little difficult to accomplish.
Quote from: xeroc on July 07, 2014, 01:44:31 PM
Quote from: spartako on July 07, 2014, 01:27:49 PM
It should be very useful having some short time analytics on the delegate behavior to take decision in events like this one.
+5%
Also we need auto-voting to kick out non-producing delegates
+5%
Quote from: xeroc on July 07, 2014, 08:35:12 AM
Quote from: Webber on July 07, 2014, 08:03:15 AM
wow,poor network now! What happening?
latest github master has a bug that makes client stuck on a block .. no idea when they will update that :(
guess we'll start a new Dry Run today... or better asap .. no exact timeframe currently
Quote from: bytemaster on July 07, 2014, 03:45:02 AM
DAC Unlimited is trusted.
is it an Hyperetas project!? So i could help on design if needed!?
Vote also for some of my delegates =D
We're taking this one down. Great success all around, except for our sloppy hard fork at the end.
Next test net:
* 10 transactions per second
* 10 second blocks
* Bids/asks/shorts (but no order matching, ha ha)