BitShares Forum
Main => General Discussion => Topic started by: toast on June 12, 2014, 11:24:02 pm
-
We'll use this chain for voting for initial delegates for the real launch (assuming nothing goes wrong). Keep your shares if you want to have a say in who the initial delegates are.
Of course we cannot expect delegate campaigns to start or the masses to start voting until our GUI is ready. We'll start a separate thread for that, with pretty pictures. Soon.
Initial delegates, do this: https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-initial-delegate-setup
Note that we removed some delegates for this round due to inactivity (or rather, inactivity as seen on our fork).
You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json
Notes
* All delegates were registered with "init-delegate-N" as names, this is expected. These are pre-registered accounts and you do not need to make new
* for people trying to get this to work on debian and getting import errors for keys, make sure that you compile with gcc 4.8, as gcc 4.7 doesn't work (compiles correctly but then crashes randomly or fails importing keys in weird places...)
-
does it mean the the top 100 active delegates in this test chain will be selected as the initial delegates for the real launch? can i apply the initial delegates in this test chain?if yes, how many initial delegates can i apply??
if it is not too late to apply the initial delegates in this test chain, please help to include the following delegates. thanks
public key: XTS7H28tfWkAcJDvxW7wJBPRdM4UHbmdcP3JP8vFv1cQP7KNtaq2Z
public key: XTS5g1QvMhU88HdZcySwqQRg4fqsGwNZ9nLSZFpBofp6XVfyyNP8n
public key: XTS8dhZN4jLXmTDivEXWLB227KhzJpuvVX7M8y6AQPovw7bVTBR7m
public key: XTS5p6iXruAGpneXPt252xWk8STpBNvqkwwNw7uaWYFRQ1ankgTMV
public key: XTS5KKdtjAXAjFbQbB4bwPiyPShp1o47QWRPVKqaxvffnhTZfq9cF
-
when somebody try now to get a delegate is it to late?
-
when somebody try now to get a delegate is it to late?
Nothing is every too late... if you work hard and help in the testing then you will likely be selected and voted in.
-
getinfo
{
"blockchain_head_block_num": 8,
"blockchain_head_block_time": "20140613T001830",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 3.053435114503817,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": "20140613T002415",
"wallet_seconds_until_next_block_production": 25,
"wallet_local_time": "20140613T002350",
"blockchain_random_seed": "23eeea969c96c5f75eb865bc42852939f6014923",
"blockchain_shares": 9999999984584,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "",
"wallet_version": 100
}
-
Can I import my delegate key in 2 nodes this time?
-
As long as only one is unlocked at a time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
As long as only one is unlocked at a time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
What if both 2 nodes are unlocked ? Get fired ?
-
Try it. I dare you.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
I've got my delegates up and creating blocks. I also have a seed node running on 95.85.33.16:8764. On a side note, has anyone managed to get the Qt wallet to work outside of OSX?
-
As long as only one is unlocked at a time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
What if both 2 nodes are unlocked ? Get fired ?
Not automatically. You should try it, see if you can cause a fork.
Even better, get two of your clients connected to each other and not to the rest of the network, then reconnect once you have your own chain.
-
Just pulled latest code and rebuilt delegate node. Deleted .Bitshares/ dir and recreated wallet. Tried to re-import delegate private keys, but now I get this error on every delegate key:
wallet_import_private_key <mykey>
10 assert_exception: Assert Exception
registered_account: the key must belong to a registered account or an account name must be specified
{}
th_a wallet.cpp:931 import_private_key
{"account_name":""}
th_a wallet.cpp:970 import_private_key
{"account_name":""}
th_a wallet.cpp:989 import_wif_private_key
{}
th_a common_api_client.cpp:252 wallet_import_private_key
and it seems I am on new blockchain
get_info
{
"blockchain_head_block_num": 74,
"blockchain_head_block_time": "20140613T015945",
my delegates were
init-delegate-38 through 41
-
Just pulled latest code and rebuilt delegate node. Deleted .Bitshares/ dir and recreated wallet. Tried to re-import delegate private keys, but now I get this error on every delegate key:
wallet_import_private_key <mykey>
10 assert_exception: Assert Exception
registered_account: the key must belong to a registered account or an account name must be specified
{}
th_a wallet.cpp:931 import_private_key
{"account_name":""}
th_a wallet.cpp:970 import_private_key
{"account_name":""}
th_a wallet.cpp:989 import_wif_private_key
{}
th_a common_api_client.cpp:252 wallet_import_private_key
and it seems I am on new blockchain
get_info
{
"blockchain_head_block_num": 74,
"blockchain_head_block_time": "20140613T015945",
my delegates were
init-delegate-38 through 41
You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json
Were you inactive during the last test? I only removed delegates with 0 blocks produced according to my client.
-
As long as only one is unlocked at a time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
What if both 2 nodes are unlocked ? Get fired ?
Not automatically. You should try it, see if you can cause a fork.
Even better, get two of your clients connected to each other and not to the rest of the network, then reconnect once you have your own chain.
Installing another Ubuntu now to try.
-
Just pulled latest code and rebuilt delegate node. Deleted .Bitshares/ dir and recreated wallet. Tried to re-import delegate private keys, but now I get this error on every delegate key:
wallet_import_private_key <mykey>
10 assert_exception: Assert Exception
registered_account: the key must belong to a registered account or an account name must be specified
{}
th_a wallet.cpp:931 import_private_key
{"account_name":""}
th_a wallet.cpp:970 import_private_key
{"account_name":""}
th_a wallet.cpp:989 import_wif_private_key
{}
th_a common_api_client.cpp:252 wallet_import_private_key
and it seems I am on new blockchain
get_info
{
"blockchain_head_block_num": 74,
"blockchain_head_block_time": "20140613T015945",
my delegates were
init-delegate-38 through 41
You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json
Were you inactive during the last test? I only removed delegates with 0 blocks produced according to my client.
I was active and it seems that list genesis.json includes my delegate names but keys changed..
There were many forks in the chain, my delegate node must have been tracking a different one from yours.
{
"name": "init-delegate-38",
"is_delegate": true,
"owner": "XTS7Fbh67uWB1vfvxpqLMYrxJVpy1eqW1S9sgGTFs5GRF3tKsusuz"
},{
"name": "init-delegate-39",
"is_delegate": true,
"owner": "XTS7DEUd9uPyY8TVZ9BxJbTTkV5qK9a49sFDL7Y5DHbehUc89bPzX"
},{
"name": "init-delegate-40",
"is_delegate": true,
"owner": "XTS8XD2PcH9BoiLT1gtLrnUcSAob41YDr1enLp3oaWoqzUj5xNsUS"
},{
"name": "init-delegate-41",
"is_delegate": true,
"owner": "XTS73tZqCAgRxNTeBCt2CMSvoMZQLQFodvrJWLvAebVVNYee6TVJs"
},{
Here are my keys that were active yesterday.
XTS6ezsAe72hVoMq4mC4fnAAF2XYqprcpt4vZ5nkqUoZn8xsSWB5Z
XTS72Xc5wBYmWQrAqcPoU6RSEegB3CosNh82wbf4QkKquJtbhgPWL
XTS7DeMWhGV8P7oiKoigtGqFKDfauB83Nrxy5FpMwLEjMw7wC8UVe
XTS73iK3RkkijdfgzH5mioB4wzWFNsmsvwtsNPnkoHAApHK6cbMz3
How do I get them working again?
-
init-delegate-90~93 are working now.
-
Just pulled latest code and rebuilt delegate node. Deleted .Bitshares/ dir and recreated wallet. Tried to re-import delegate private keys, but now I get this error on every delegate key:
wallet_import_private_key <mykey>
10 assert_exception: Assert Exception
registered_account: the key must belong to a registered account or an account name must be specified
{}
th_a wallet.cpp:931 import_private_key
{"account_name":""}
th_a wallet.cpp:970 import_private_key
{"account_name":""}
th_a wallet.cpp:989 import_wif_private_key
{}
th_a common_api_client.cpp:252 wallet_import_private_key
and it seems I am on new blockchain
get_info
{
"blockchain_head_block_num": 74,
"blockchain_head_block_time": "20140613T015945",
my delegates were
init-delegate-38 through 41
You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json
Were you inactive during the last test? I only removed delegates with 0 blocks produced according to my client.
I was active and it seems that list genesis.json includes my delegate names but keys changed..
There were many forks in the chain, my delegate node must have been tracking a different one from yours.
{
"name": "init-delegate-38",
"is_delegate": true,
"owner": "XTS7Fbh67uWB1vfvxpqLMYrxJVpy1eqW1S9sgGTFs5GRF3tKsusuz"
},{
"name": "init-delegate-39",
"is_delegate": true,
"owner": "XTS7DEUd9uPyY8TVZ9BxJbTTkV5qK9a49sFDL7Y5DHbehUc89bPzX"
},{
"name": "init-delegate-40",
"is_delegate": true,
"owner": "XTS8XD2PcH9BoiLT1gtLrnUcSAob41YDr1enLp3oaWoqzUj5xNsUS"
},{
"name": "init-delegate-41",
"is_delegate": true,
"owner": "XTS73tZqCAgRxNTeBCt2CMSvoMZQLQFodvrJWLvAebVVNYee6TVJs"
},{
Here are my keys that were active yesterday.
XTS6ezsAe72hVoMq4mC4fnAAF2XYqprcpt4vZ5nkqUoZn8xsSWB5Z
XTS72Xc5wBYmWQrAqcPoU6RSEegB3CosNh82wbf4QkKquJtbhgPWL
XTS7DeMWhGV8P7oiKoigtGqFKDfauB83Nrxy5FpMwLEjMw7wC8UVe
XTS73iK3RkkijdfgzH5mioB4wzWFNsmsvwtsNPnkoHAApHK6cbMz3
How do I get them working again?
You're not an initial delegate in this chain then, wait until we get some voting tutorials up for the stakeholders to start vote testing
-
You're not an initial delegate in this chain then, wait until we get some voting tutorials up for the stakeholders to start vote testing
This sucks. I did everything as instructed and my delegate was making blocks, but now my keys got removed out due to no fault of mine. Hope this can be recovered.
-
You're not an initial delegate in this chain then, wait until we get some voting tutorials up for the stakeholders to start vote testing
This sucks. I did everything as instructed and my delegate was making blocks, but now my keys got removed out due to no fault of mine. Hope this can be recovered.
I don't see why it would matter, the initial delegates are intended to all be quickly voted out anyway. We can include some keys in the real genesis block if it's about being recognized or something.
-
You're not an initial delegate in this chain then, wait until we get some voting tutorials up for the stakeholders to start vote testing
This sucks. I did everything as instructed and my delegate was making blocks, but now my keys got removed out due to no fault of mine. Hope this can be recovered.
Yeah, we can get that corrected... if your blocks were on a fork then we didn't count it. Register an account and i'll vote you in to be a delegate.
-
It has come to our attention that some nodes may 'hang' and stop syncing with the network. Closing and reopening the client allows it to reconnect. If you notice that your client is stuck, close and re-open it.
-
Register an account and i'll vote you in to be a delegate.
Ok. Created a local account and registered it, then updated registration to make delegate.
wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
bitcoiners XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk 2014-06-13T03:08:45 0
blockchain_list_registered_accounts
NAME (* delegate) KEY REGISTERED VOTES FOR VOTES AGAINST TRUST LEVEL
bitcoiners * XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk 2014-06-13T03:08:45 0 0 0
How do I export this account to another computer? I created this one on my desktop and I need to move it to the VPS server.
-
I just added an RPC call: wallet_account_export_private_key that will give you the key you want. Simply import that key into your other wallet.
-
I just added an RPC call: wallet_account_export_private_key that will give you the key you want. Simply import that key into your other wallet.
Ok. Thanks. Done. Please enable (vote for) this delegate (bitcoiners)
-
Am I on the main chain?
welk1n (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
welk1n-d-5 XTS6z7aMnBmXi7qL9uHfgWS6d1wedEpvQNTrwgeGb8h1MH9WVXtRC NO 0
init-delegate-33 * XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA 2014-06-01T00:00:00 0
init-delegate-32 * XTS7p56UNQLyWc3NB2yeT4VVtYhanf6wFC356c6vbfpvQ9CHUmg6X 2014-06-01T00:00:00 0
init-delegate-31 * XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj 2014-06-01T00:00:00 0
init-delegate-30 * XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx 2014-06-01T00:00:00 0
"OK"
welk1n (unlocked) >>> info
{
"blockchain_head_block_num": 452,
"blockchain_head_block_time": "20140613T060600",
"blockchain_confirmation_requirement": 290,
"blockchain_average_delegate_participation": 27.713059472716125,
"network_num_connections": 7,
"wallet_unlocked_seconds_remaining": 997346,
"wallet_next_block_production_time": "20140613T060700",
"wallet_seconds_until_next_block_production": 52,
"wallet_local_time": "20140613T060608",
"blockchain_random_seed": "32fa7e7088b6984898073462f227a7e24c9e5630",
"blockchain_shares": 9999980679465,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140624T190834",
"wallet_version": 100
}
-
Note that we removed some delegates for this round due to inactivity (or rather, inactivity as seen on our fork).
You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json
Interestingly I had 4 delegates running (on the same node, same client, same wallet) all of which produced blocks in the SAME fork (I guess) and only one of them made it to this particular genesis.json. How can it be that one delegate is accepted for producing block in the 'main fork' while the others are not? Only thing I can think about is that a fork started with one of my delegates?!
Delegates in question:
init-delegate-58
init-delegate-59
init-delegate-60
init-delegate-61 (up, running and producing blocks)
-
init-delegate-21,init-delegate-22,init-delegate-23,init-delegate-24 are working.
I have also created a new delegate spartako, and tried to vote for other non-init delegates (bitcoiners and bts101) but I see only bitcoiners with some votes and bts101 remains at zero votes.
-
+5%
-
Please add me too if there is a vacancy
networker-01: XTS7hVUNvkxAwspen2XkTwY2sD3JB5g1GhviK5isvXzM6HRVVZ1TA
networker-02: XTS5P8rbowbZaNsmUJ6biWRa2y7qHDHSdEosAN16SyABpfjzyG7qe
networker-03: XTS7ut6vArPQvCzb4xNVxHuuQCnwxL9aZGSNwwJsnDYo5MRnbA6Ja
networker-04: XTS8dN5PS1abbWDC5kRoVveiGrjVJCV1ByC6LUahbwyZ8qetTpepY
networker-05: XTS5MYSmHzern8b6TMS42N2BB3cPCkHg9RxC5ogeiBseqGoYnhVDB
Name:
Location: GuangDong, China
Hardware:
Intel i7 3770k
4 GB ddr3 1600mhz ram
500GB HD
Software:
OS Ubuntu server 14.04 64bit
-
Interestingly I had 4 delegates running (on the same node, same client, same wallet) all of which produced blocks in the SAME fork (I guess) and only one of them made it to this particular genesis.json.
Same issue here, I had delegates 82 -> 85 included, and the new genesis.json only lists 82 and 84 with the correct keys (which are up and running now), but 83 and 85 don't have the same key as before. Not that it matters a lot, if this was done on purpose then don't bother, but maybe something else went wrong? Let us know if we can help in any other way than just having the delegate running.
-
Strangly my delegate nr 61 is up and running but not producing a block according to blockchain_get_account_record init-delegate-61
-
cgafeng (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
cgafeng * XTS8daF9rX4LiWghT2LbkV1ds2NtiZjEdCiXkkmP6ua3S6s2Vsx8n 2014-06-13T09:28:00 0
I would like to run delegate and register as delegate, can i get vote?
Hardware:
Amazon EC2
Location:
us west
-
roy (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
roy001 XTS7warBpmsDK7zEvEGYCmbdTwn6P9FP8fDQWCLuj3Ay3gBrAXRqw 2014-06-13T11:54:15 0
"OK"
I d like to become a delegate ,
could you vote me a delegate ,thank you
CPU :i7-3370K ; RAM:32GB, netspeed:50M, Shanghai or Qingdao China ,
I also can hire a VPS in aliyun
Br
-
Info:
djdexter-1 * XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y 2014-06-10T23:23:00 0
Physical machine:
Intel i3 (last gen)
8 GB rm
Stable DSL(15 Mbps up/down)
UPS backup
Regular backups / maintenance (system administration)
Virtual machine (only one running)
OS: Ubuntu 14.04
Bitshares_toolkit
-Development/IT background
-Log analysis
-Debugging
-OBDR restore procedures ( one button disaster recovery )
If needed in future i can spin more machines on dedicated systems or cloud.
-
I have one question.
I have latest build (pulled one hour ago from this post time)
I'm seeing following value:
"blocks_produced": 0
But i see
"last_block_num_produced": 4294967295
So it basically says that there is at least one block produced with following number "4294967295", but it does not count this block on blocks_produced placeholder.
Can someone explain this to me ?
djdexter (unlocked) >>> wallet_get_account djdexter-1
{
"index": 4,
"id": 301,
"name": "djdexter-1",
"public_data": null,
"owner_key": "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y",
"active_key_history": [[
"20140610T232300",
"XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y"
]
],
"delegate_info": {
"votes_for": 3000000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140610T232300",
"last_update": "20140610T232300",
"meta_data": null,
"account_address": "XTSFhKaGFphYT6avaCFWpTVGRVSGhw9r9Pxh",
"trust_level": 0,
"private_data": null
}
-
Damm it, off for a week (not checked) and I am not a delegate now :(. Time to catch up!
-
I have one question.
I have latest build (pulled one hour ago from this post time)
I'm seeing following value:
"blocks_produced": 0
But i see
"last_block_num_produced": 4294967295
So it basically says that there is at least one block produced with following number "4294967295", but it does not count this block on blocks_produced placeholder.
Can someone explain this to me ?
djdexter (unlocked) >>> wallet_get_account djdexter-1
{
"index": 4,
"id": 301,
"name": "djdexter-1",
"public_data": null,
"owner_key": "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y",
"active_key_history": [[
"20140610T232300",
"XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y"
]
],
"delegate_info": {
"votes_for": 3000000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140610T232300",
"last_update": "20140610T232300",
"meta_data": null,
"account_address": "XTSFhKaGFphYT6avaCFWpTVGRVSGhw9r9Pxh",
"trust_level": 0,
"private_data": null
}
4294967295 is the maximum value for an unsigned (never negative) 32 bit integer, and is not an actual block number that has been created in the chain. Basically it says that because it was never changed to something legitimate, because you never produced a block.
-
I created some LOVE and voted all delegated not-init :)
wallet_set_delegate_trust_level bitcoiners 5
wallet_set_delegate_trust_level cgafeng 5
wallet_set_delegate_trust_level puppies 5
wallet_set_delegate_trust_level bts101 5
1363.1 2014-06-13T12:51:15 spartako bts101 some love and votes 100.000000 LOVE 0.010000 XTS 099ce495
1363.0 2014-06-13T12:51:15 spartako bitcoiners some love and votes 100.000000 LOVE 0.010000 XTS 05565fb6
1363.2 2014-06-13T12:51:15 spartako cgafeng some love and votes 100.000000 LOVE 0.010000 XTS 5dc0461f
1363.3 2014-06-13T12:51:15 spartako puppies some love and votes 100.000000 LOVE 0.010000 XTS 9b4a97ba
Please vote for spartako :)
-
Strangly my delegate nr 61 is up and running but not producing a block according to blockchain_get_account_record init-delegate-61
So .. I installed NTP and ran a synchronization .. and my delegate now builds blocks.. No idea weather this can be the cause :-(
However:
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "5517b4ca8d1b2383bbe3cc0b66d8ef7ee9480d5c",
"bitshares_toolkit_revision_age": "in the future",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "14 hours ago",
"compile_date": "compiled on Jun 13 2014 at 14:41:50"
}
-
I created some LOVE and voted all delegated not-init :)
wallet_set_delegate_trust_level bitcoiners 5
wallet_set_delegate_trust_level cgafeng 5
wallet_set_delegate_trust_level puppies 5
wallet_set_delegate_trust_level bts101 5
1363.1 2014-06-13T12:51:15 spartako bts101 some love and votes 100.000000 LOVE 0.010000 XTS 099ce495
1363.0 2014-06-13T12:51:15 spartako bitcoiners some love and votes 100.000000 LOVE 0.010000 XTS 05565fb6
1363.2 2014-06-13T12:51:15 spartako cgafeng some love and votes 100.000000 LOVE 0.010000 XTS 5dc0461f
1363.3 2014-06-13T12:51:15 spartako puppies some love and votes 100.000000 LOVE 0.010000 XTS 9b4a97ba
Please vote for spartako :)
Can you vote me and send me some love :P
NAME BALANCE KEY REGISTERED TRUST LEVEL
networker 0.000000 XTS XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO 0
-
can i get some test funds.
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
init-delegate-42 * XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit 2014-06-01T00:00:00 0
Thanks.
-
Can you vote me and send me some love :P
NAME BALANCE KEY REGISTERED TRUST LEVEL
networker 0.000000 XTS XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO 0
I sent you some XTS for register your name and some LOVE.
1400.0 2014-06-13T13:20:45 spartako networker 10.000000 XTS 0.010000 XTS 0865528f
1400.1 2014-06-13T13:20:45 spartako networker 100.000000 LOVE 0.010000 XTS 526193c9
When you will become delegate I am able to vote for you.
-
can i get some test funds.
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
init-delegate-42 * XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit 2014-06-01T00:00:00 0
Thanks.
I sent you 1 XTS
1405.0 2014-06-13T13:26:15 spartako xeldal-del 1.000000 XTS 0.010000 XTS 3e6c9b30
-
I have one question.
I have latest build (pulled one hour ago from this post time)
I'm seeing following value:
"blocks_produced": 0
But i see
"last_block_num_produced": 4294967295
So it basically says that there is at least one block produced with following number "4294967295", but it does not count this block on blocks_produced placeholder.
Can someone explain this to me ?
djdexter (unlocked) >>> wallet_get_account djdexter-1
{
"index": 4,
"id": 301,
"name": "djdexter-1",
"public_data": null,
"owner_key": "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y",
"active_key_history": [[
"20140610T232300",
"XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y"
]
],
"delegate_info": {
"votes_for": 3000000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140610T232300",
"last_update": "20140610T232300",
"meta_data": null,
"account_address": "XTSFhKaGFphYT6avaCFWpTVGRVSGhw9r9Pxh",
"trust_level": 0,
"private_data": null
}
4294967295 is the maximum value for an unsigned (never negative) 32 bit integer, and is not an actual block number that has been created in the chain. Basically it says that because it was never changed to something legitimate, because you never produced a block.
Actually i did not thought about the numeric value :)
You are absolutely right !
Thanks for the info +5%
-
Dear all ,
Can someone also explain me this situation?
My delegate is marked as inactive, and i'm running bitshares_client in background all day ?
** Inactive:
301 djdexter-1 3000000 0 2.99997e-05 % 0 0
Should i do anything ? Or this is normal?
Here is my blockchain head info:
"blockchain_head_block_num": 6416,
"blockchain_head_block_time": "20140612T073600",
-
Hi,
Can anybody send me some funds. My wallet etc is gone, enough to register as a delegate.
Thanks,
XTS8E7T1qxvfWKVZtq9HBZ8Nmv8RUSxwksukhCx3gcGEKenZN3bfh
-
Here is my blockchain head info:
"blockchain_head_block_num": 6416,
"blockchain_head_block_time": "20140612T073600",
I think you are in an old fork, this is my state:
"blockchain_head_block_num": 1431,
"blockchain_head_block_time": "20140613T135645",
Try to recompile, erase your data-dir and relunch
-
Please also give me some test fund for joining this dry run 2
ffwong-delegate-5 XTS819hyNrhVFkjEDrqM5sJmaTCS9qbUuTeFJkh81wogQFQWbRxQm NO 0
ffwong-delegate-4 XTS6sL31fo2DSrbFzwKvMbkYQx63fwES1AcfVWdLXg9pqkRPxuXzG NO 0
ffwong-delegate-3 XTS84LNqrGb9zhMUUUkK5FSoZWYJCBSbaovEA7q7NbAohkzTByxPN NO 0
ffwong-delegate-2 XTS6yjjUj4t6XZWzaF41DJgghDrxVC31XoiWwgeDfzPTcAzLkjMtk NO 0
ffwong-delegate-1 XTS7Zm1t5sHKS9Cm7XJDTNWgzQUi2V1WoFzJDeB4PzX9cLGENjGxj NO 0
Thanks.
-
Please also give me some test fund for joining this dry run 2
ffwong-delegate-5 XTS819hyNrhVFkjEDrqM5sJmaTCS9qbUuTeFJkh81wogQFQWbRxQm NO 0
ffwong-delegate-4 XTS6sL31fo2DSrbFzwKvMbkYQx63fwES1AcfVWdLXg9pqkRPxuXzG NO 0
ffwong-delegate-3 XTS84LNqrGb9zhMUUUkK5FSoZWYJCBSbaovEA7q7NbAohkzTByxPN NO 0
ffwong-delegate-2 XTS6yjjUj4t6XZWzaF41DJgghDrxVC31XoiWwgeDfzPTcAzLkjMtk NO 0
ffwong-delegate-1 XTS7Zm1t5sHKS9Cm7XJDTNWgzQUi2V1WoFzJDeB4PzX9cLGENjGxj NO 0
Thanks.
1434.0 2014-06-13T14:02:45 spartako ffwong-delegate-1 1.000000 XTS 0.010000 XTS 2ef04b2d
-
Hi,
Can anybody send me some funds. My wallet etc is gone, enough to register as a delegate.
Thanks,
XTS8E7T1qxvfWKVZtq9HBZ8Nmv8RUSxwksukhCx3gcGEKenZN3bfh
1437.0 2014-06-13T14:06:00 spartako betax 1.000000 XTS 0.010000 XTS b2a49d5d
-
You mean to delete ~/.BitSharesXTS folder by "data-dir" ?
i did that 2 hours ago and made git pull and recompiled the code
Here is my blockchain head info:
"blockchain_head_block_num": 6416,
"blockchain_head_block_time": "20140612T073600",
I think you are in an old fork, this is my state:
"blockchain_head_block_num": 1431,
"blockchain_head_block_time": "20140613T135645",
Try to recompile, erase your data-dir and relunch
-
You mean to delete ~/.BitSharesXTS folder by "data-dir" ?
Yes, ~/.BitSharesXTS is the data-dir. It is strange, try do launch this command:
addnode "95.85.33.16:8764" "add"
-
Hi,
Can anybody send me some funds. My wallet etc is gone, enough to register as a delegate.
Thanks,
XTS8E7T1qxvfWKVZtq9HBZ8Nmv8RUSxwksukhCx3gcGEKenZN3bfh
Set you some funds.
-
Please also give me some test fund for joining this dry run 2
ffwong-delegate-5 XTS819hyNrhVFkjEDrqM5sJmaTCS9qbUuTeFJkh81wogQFQWbRxQm NO 0
ffwong-delegate-4 XTS6sL31fo2DSrbFzwKvMbkYQx63fwES1AcfVWdLXg9pqkRPxuXzG NO 0
ffwong-delegate-3 XTS84LNqrGb9zhMUUUkK5FSoZWYJCBSbaovEA7q7NbAohkzTByxPN NO 0
ffwong-delegate-2 XTS6yjjUj4t6XZWzaF41DJgghDrxVC31XoiWwgeDfzPTcAzLkjMtk NO 0
ffwong-delegate-1 XTS7Zm1t5sHKS9Cm7XJDTNWgzQUi2V1WoFzJDeB4PzX9cLGENjGxj NO 0
Thanks.
1434.0 2014-06-13T14:02:45 spartako ffwong-delegate-1 1.000000 XTS 0.010000 XTS 2ef04b2d
1457.0 2014-06-13T14:33:45 dan betax 10.000000 XTS 0.010000 XTS 3bf6b6da
1457.1 2014-06-13T14:33:45 dan ffwong-delegate-5 10.000000 XTS 0.010000 XTS 75a50de8
-
djdexter (unlocked) >>> addnode "95.85.33.16:8764" "add"
OK
--- there are now 0 active connections to the p2p network
After 2 mins i tried
djdexter (unlocked) >>> bitcoin_getconnectioncount
0
I'm getting no connections on network , but i can ping that addr
djdexter@ficko:~/bitshares_toolkit/programs/client$ ping 95.85.33.16
PING 95.85.33.16 (95.85.33.16) 56(84) bytes of data.
64 bytes from 95.85.33.16: icmp_seq=1 ttl=55 time=45.8 ms
You mean to delete ~/.BitSharesXTS folder by "data-dir" ?
Yes, ~/.BitSharesXTS is the data-dir. It is strange, try do launch this command:
addnode "95.85.33.16:8764" "add"
-
"blockchain_head_block_num": 1458,
"blockchain_head_block_time": "20140613T143515",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 49.489795918367349,
"network_num_connections": 30,
-
djdexter (unlocked) >>> addnode "95.85.33.16:8764" "add"
OK
--- there are now 0 active connections to the p2p network
After 2 mins i tried
djdexter (unlocked) >>> bitcoin_getconnectioncount
0
I'm getting no connections on network , but i can ping that addr
djdexter@ficko:~/bitshares_toolkit/programs/client$ ping 95.85.33.16
PING 95.85.33.16 (95.85.33.16) 56(84) bytes of data.
64 bytes from 95.85.33.16: icmp_seq=1 ttl=55 time=45.8 ms
You mean to delete ~/.BitSharesXTS folder by "data-dir" ?
Yes, ~/.BitSharesXTS is the data-dir. It is strange, try do launch this command:
addnode "95.85.33.16:8764" "add"
Run this command to make sure you are on the same chain ID.
blockchain_get_config
{
"blockchain_id": "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843",
-
How long does it take for XTS to transfer?
can i get some test funds.
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
init-delegate-42 * XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit 2014-06-01T00:00:00 0
Thanks.
I sent you 1 XTS
1405.0 2014-06-13T13:26:15 spartako xeldal-del 1.000000 XTS 0.010000 XTS 3e6c9b30
I still havn't receive them evidently.
Xeldal (unlocked) >>> wallet_account_balance xeldal-del
xeldal-del:
0.000000 XTS
-
Hi Bytemaster,
djdexter (unlocked) >>> blockchain_get_config
{
"blockchain_id": "964b38343dc7337f8d87a16323faaa7c63b95160c73739c6d0a276ef41f37312",
It seems i'm on different chain .
How can i fix this ? i tried git pull / recompile / and deleted ~/.BitSharesXTS.
djdexter (unlocked) >>> addnode "95.85.33.16:8764" "add"
OK
--- there are now 0 active connections to the p2p network
After 2 mins i tried
djdexter (unlocked) >>> bitcoin_getconnectioncount
0
I'm getting no connections on network , but i can ping that addr
djdexter@ficko:~/bitshares_toolkit/programs/client$ ping 95.85.33.16
PING 95.85.33.16 (95.85.33.16) 56(84) bytes of data.
64 bytes from 95.85.33.16: icmp_seq=1 ttl=55 time=45.8 ms
You mean to delete ~/.BitSharesXTS folder by "data-dir" ?
Yes, ~/.BitSharesXTS is the data-dir. It is strange, try do launch this command:
addnode "95.85.33.16:8764" "add"
Run this command to make sure you are on the same chain ID.
blockchain_get_config
{
"blockchain_id": "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843",
-
Xeldal (unlocked) >>> wallet_account_balance xeldal-del
xeldal-del:
0.000000 XTS
Try the wallet_rescan_blockchain command, otherwise we could be in different chain.
Launch the command: blockchain_get_config and check blockchain_id is "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843"
-
Xeldal (unlocked) >>> wallet_account_balance xeldal-del
xeldal-del:
0.000000 XTS
Try the wallet_rescan_blockchain command, otherwise we could be in different chain.
Launch the command: blockchain_get_config and check blockchain_id is "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843"
Rescanned ... same chain... no dice :(
Xeldal (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
Xeldal (unlocked) >>> wallet_account_balance xeldal-del
xeldal-del:
0.000000 XTS
Xeldal (unlocked) >>> blockchain_get_config
{
"blockchain_id": "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843",
hrrmmm
-
hrrmmm
Really strange...
Is it correct your KEY that I added to my wallet?
NAME (* delegate) KEY REGISTERED TRUST LEVEL
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
-
hrrmmm
Really strange...
Is it correct your KEY that I added to my wallet?
NAME (* delegate) KEY REGISTERED TRUST LEVEL
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
Now I have sent 1 XTS to init-delegate-42
1470.0 2014-06-13T14:53:15 spartako init-delegate-42 1.000000 XTS 0.010000 XTS bb72e318
-
hrrmmm
Really strange...
Is it correct your KEY that I added to my wallet?
NAME (* delegate) KEY REGISTERED TRUST LEVEL
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
Correct
Xeldal (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
init-delegate-45 * XTS5ttrjXKJPiWYm6EL7LAYRWV4GWnAaBPjGvkydy86yaKQdxTcHg 2014-06-01T00:00:00 0
init-delegate-44 * XTS8QLeHvaYQqFRdTP46EZq4GVdvj65Fp9wbKBGhBx5kvDnNFTDtM 2014-06-01T00:00:00 0
init-delegate-43 * XTS6whTVdWVb4KFvBDfKeawRjWPa6rsG5etsMvmg1MuybWhpVTf2u 2014-06-01T00:00:00 0
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
init-delegate-42 * XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit 2014-06-01T00:00:00 0
"OK"
-
We have identified a problem in the fork management that is resulting in the network being flooded and large log files being written to disk. We are actively working to resolve this issue ASAP stand by for an update.
-
Now I have sent 1 XTS to init-delegate-42
1470.0 2014-06-13T14:53:15 spartako init-delegate-42 1.000000 XTS 0.010000 XTS bb72e318
Not sure how long it should take but nothing there yet either.
Xeldal (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
Xeldal (unlocked) >>> wallet_account_balance init-delegate-42
init-delegate-42:
0.000000 XTS
-
How long does it take for XTS to transfer?
can i get some test funds.
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
init-delegate-42 * XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit 2014-06-01T00:00:00 0
Thanks.
I sent you 1 XTS
1405.0 2014-06-13T13:26:15 spartako xeldal-del 1.000000 XTS 0.010000 XTS 3e6c9b30
I still havn't receive them evidently.
Xeldal (unlocked) >>> wallet_account_balance xeldal-del
xeldal-del:
0.000000 XTS
It normally takes just 1 block, depends upon how many delegates are producing blocks. Right now it is about 1 minute on average, however, the network is experiencing some major difficulties due to bug in the fork syncing code.
-
If it helps (I assume this is due to the bug so not much)
I have not got anything from you yet and I cannot find the transaction in the network.
I also imported some keys and registered as a delegate but is still pending.
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
703.0 2014-06-13T08:12:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 231fcf83
pending 2014-06-13T14:51:52 betax betax register betax as a delegate 0.000000 XTS 10.495702 XTS 36a1af5e
-
I imported my pts wallet, and rescaned blockchain, but my balance is still 0. Nor can I transfer any XTS to anybody. But I made it to register myself as a delegate, which was not able before importing of pts wallet because of lack of funds.
Does anybody know why?
-
I run 2 clients on my 2 linux pc and this morning I found they have different blockchain_head_block_num.
{
"blockchain_head_block_num": 497,
"blockchain_head_block_time": "20140613T072200",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 12.8291171915333,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": "20140613T152700",
"wallet_seconds_until_next_block_production": 10,
"wallet_local_time": "20140613T152650",
"blockchain_random_seed": "098e339373bd101d5aa1b783efca8fb0d36c596c",
"blockchain_shares": 9999981042660,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "",
"wallet_version": 100
}
{
"blockchain_head_block_num": 1471,
"blockchain_head_block_time": "20140613T145500",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 45.518535898639136,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140613T152454",
"blockchain_random_seed": "ed6a132dd035baac467e1171d20737a5ffb46304",
"blockchain_shares": 9999943623741,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "",
"wallet_version": 100
}
-
Can you vote me and send me some love :P
NAME BALANCE KEY REGISTERED TRUST LEVEL
networker 0.000000 XTS XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO 0
I sent you some XTS for register your name and some LOVE.
1400.0 2014-06-13T13:20:45 spartako networker 10.000000 XTS 0.010000 XTS 0865528f
1400.1 2014-06-13T13:20:45 spartako networker 100.000000 LOVE 0.010000 XTS 526193c9
When you will become delegate I am able to vote for you.
Why my balance still is zero?
networker (unlocked) >>> wallet_account_register
account_name: networker
pay_from_account: networker
10
!"Insufficient Funds": Requested 0.010001 XTS but only 0.000000 XTS available
{"required":"0.010001 XTS","available":"0.000000 XTS"}
th_a wallet.cpp:178 withdraw_to_transaction
networker (unlocked) >>> wallet_list_receive_accounts
NAME BALANCE KEY REGISTERED TRUST LEVEL
networker 0.000000 XTS XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO
Please help!
-
I run 2 clients on my 2 linux pc and this morning I found they have different blockchain_head_block_num.
Mine is stuck on block count 751. May be it is the bug mentioned by bytemaster.
This may be also the reason I did not receive the fund yet.
{
"blockchain_head_block_num": 751,
"blockchain_head_block_time": "20140613T083415",
"blockchain_confirmation_requirement": 290,
"blockchain_average_delegate_participation": 18.718843469591228,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 2892292014,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140613T160121",
"blockchain_random_seed": "5ca9a6ed6ca1850ae6b01ab46e935390bc701e39",
"blockchain_shares": 9999962538849,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19691231T235959",
"wallet_version": 100
}
-
I guess I am on a forked chain again. Others are in block 16XX
{
"blockchain_head_block_num": 1415,
"blockchain_head_block_time": "20140613T153330",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 42.450765864332602,
"network_num_connections": 10,
"wallet_unlocked_seconds_remaining": 9948066,
"wallet_next_block_production_time": "20140613T153730",
"wallet_seconds_until_next_block_production": 201,
"wallet_local_time": "20140613T153409",
"blockchain_random_seed": "83f58d24b891bc8db6c7673827c3ada0eedf440c",
"blockchain_shares": 9999952974179,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141006T185515",
"wallet_version": 100
}
-
From above posts , I found we at least have 3 chains running (forked again) :P :P :P :P :P :P :P :P
-
No is due to the bug Im stuck in 1402
-
From above posts , I found we at least have 3 chains running (forked again) :P :P :P :P :P :P :P :P
+ 1 ?
"blockchain_head_block_num": 1704,
"blockchain_head_block_time": "20140613T162115",
-
{
"blockchain_head_block_num": 751,
"blockchain_head_block_time": "20140613T083415",
"blockchain_confirmation_requirement": 290,
"blockchain_average_delegate_participation": 18.718843469591228,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 2892292014,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140613T160121",
"blockchain_random_seed": "5ca9a6ed6ca1850ae6b01ab46e935390bc701e39",
"blockchain_shares": 9999962538849,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19691231T235959",
"wallet_version": 100
}
Is it a bug? I set a very big constant (for unlock time) when I unlocked the wallet.
-
Can you vote me and send me some love :P
NAME BALANCE KEY REGISTERED TRUST LEVEL
networker 0.000000 XTS XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO 0
I sent you some XTS for register your name and some LOVE.
1400.0 2014-06-13T13:20:45 spartako networker 10.000000 XTS 0.010000 XTS 0865528f
1400.1 2014-06-13T13:20:45 spartako networker 100.000000 LOVE 0.010000 XTS 526193c9
When you will become delegate I am able to vote for you.
Why my balance still is zero?
networker (unlocked) >>> wallet_account_register
account_name: networker
pay_from_account: networker
10
!"Insufficient Funds": Requested 0.010001 XTS but only 0.000000 XTS available
{"required":"0.010001 XTS","available":"0.000000 XTS"}
th_a wallet.cpp:178 withdraw_to_transaction
networker (unlocked) >>> wallet_list_receive_accounts
NAME BALANCE KEY REGISTERED TRUST LEVEL
networker 0.000000 XTS XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO
Please help!
I think, I sent funds in an other chain fork.
I tried again:
1479.0 2014-06-13T15:48:45 spartako networker 10.000000 XTS 0.010000 XTS add543bb
-
it's a fork or just stop sync?
try command in both 2 nodes to see if block 497 is the same.
blockchain_get_block_by_number 497
I run 2 clients on my 2 linux pc and this morning I found they have different blockchain_head_block_num.
{
"blockchain_head_block_num": 497,
"blockchain_head_block_time": "20140613T072200",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 12.8291171915333,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": "20140613T152700",
"wallet_seconds_until_next_block_production": 10,
"wallet_local_time": "20140613T152650",
"blockchain_random_seed": "098e339373bd101d5aa1b783efca8fb0d36c596c",
"blockchain_shares": 9999981042660,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "",
"wallet_version": 100
}
{
"blockchain_head_block_num": 1471,
"blockchain_head_block_time": "20140613T145500",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 45.518535898639136,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140613T152454",
"blockchain_random_seed": "ed6a132dd035baac467e1171d20737a5ffb46304",
"blockchain_shares": 9999943623741,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "",
"wallet_version": 100
}
-
Just deleted the .BitsharesXTS folder and restart everything. Now the wallet sync to the block 1495.
But I still did not receive any fund previously sent by bytemaster and others (thanks anyway), even after rescan the chain. Can someone please sent me again?
Edited: Got the fund. But have another problem. ... (see next post)
{
"blockchain_head_block_num": 1495,
"blockchain_head_block_time": "20140613T165430",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 39.770397703977039,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 999999735,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140613T165620",
"blockchain_random_seed": "b0c4704bee5b8951544428447e35c24d1992b240",
"blockchain_shares": 9999944179437,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19100114T121019",
"wallet_version": 100
}
-
Now everytime I open my wallet and then type wallet_list_unspent_balances
BALANCE OWNER VOTE
--------------------------------------------------------------------------------------------------------------------------
1000000 XTSHYSKmUfq1YMb9P7pMpajbwyn7qUJES6cT +bts101
Segmentation fault (core dumped)
Program received signal SIGSEGV, Segmentation fault.
0x0000000000651b93 in bts::cli::detail::cli_impl::format_and_print_result (
this=0x158b370, command=..., arguments=..., result=...)
at /home/ttwong/bitshares_toolkit/libraries/cli/cli.cpp:798
798 if (delegate_rec->name.size() > 21)
-
Trying to upgrade from registered account to delegate. But the required fund is higher than my balance. Can anyone send me more for testing? Thanks.
"required":"10.495702 XTS","available":"9.989999 XTS"
ffwong-delegate-1 XTS7Zm1t5sHKS9Cm7XJDTNWgzQUi2V1WoFzJDeB4PzX9cLGENjGxj NO 0
ffwong-delegate-2 XTS6yjjUj4t6XZWzaF41DJgghDrxVC31XoiWwgeDfzPTcAzLkjMtk NO 0
ffwong-delegate-3 XTS84LNqrGb9zhMUUUkK5FSoZWYJCBSbaovEA7q7NbAohkzTByxPN NO 0
ffwong-delegate-4 XTS6sL31fo2DSrbFzwKvMbkYQx63fwES1AcfVWdLXg9pqkRPxuXzG NO 0
ffwong-delegate-5 XTS819hyNrhVFkjEDrqM5sJmaTCS9qbUuTeFJkh81wogQFQWbRxQm 2014-06-13T17:00:00 0
-
anyone can spare me some xts to following address. I would like to register to be a delegate by myself.
XTS6synRW1rpdarMk4ELRkUQUAxMQwNm87MoppFGJ4jqAz9fgGe2L
-
ffwong-delegate-1 XTS7Zm1t5sHKS9Cm7XJDTNWgzQUi2V1WoFzJDeB4PzX9cLGENjGxj
send.
XTS5vTWzNLkbr2XcFRJTq49x47npNc6D5hsTgYYNaVFZAPxvpn2Rf
send.
-
could you please send it to XTS6synRW1rpdarMk4ELRkUQUAxMQwNm87MoppFGJ4jqAz9fgGe2L?
i miss copy paste my address
ffwong-delegate-1 XTS7Zm1t5sHKS9Cm7XJDTNWgzQUi2V1WoFzJDeB4PzX9cLGENjGxj
send.
XTS5vTWzNLkbr2XcFRJTq49x47npNc6D5hsTgYYNaVFZAPxvpn2Rf
send.
-
ffwong-delegate-1 XTS7Zm1t5sHKS9Cm7XJDTNWgzQUi2V1WoFzJDeB4PzX9cLGENjGxj
send.
XTS5vTWzNLkbr2XcFRJTq49x47npNc6D5hsTgYYNaVFZAPxvpn2Rf
send.
Got it. Thanks. Make one account as delegate "ffwong-delegate-5".
-
could you please send it to XTS6synRW1rpdarMk4ELRkUQUAxMQwNm87MoppFGJ4jqAz9fgGe2L?
i miss copy paste my address
ffwong-delegate-1 XTS7Zm1t5sHKS9Cm7XJDTNWgzQUi2V1WoFzJDeB4PzX9cLGENjGxj
send.
XTS5vTWzNLkbr2XcFRJTq49x47npNc6D5hsTgYYNaVFZAPxvpn2Rf
send.
send.
-
I just set everything up on our server. I hope it isn't too late.
XTS8C53PZp3dkkUyfxZyrfcwqazXV6dRWA7UGgaPFR88zNWdb7D2M
XTS7Y3iCckmTj428PDAiqStkN1W1HTH6LzFWrewwEHxbK8dTCvCqc
XTS5V4sJqepPR34T6bDrjw3QigJLx9gC9cfUaPasTLHPDksBSsCeC
XTS623e6h5zuyvU9rhnU58XF5QA63QPpwxzdbAj1Po6e18AqFAoTC
XTS78otuA76BjeFwcE8YDeREGsedLiFzncCuVrWFax2CQX4KStB9K
If any more info is needed I'll put it up on the forum asap.
My team Bitsapphire is creating a one-pager explaining why we think we'll be an awesome delegate!
-
I just set everything up on our server. I hope it isn't too late.
XTS8C53PZp3dkkUyfxZyrfcwqazXV6dRWA7UGgaPFR88zNWdb7D2M
XTS7Y3iCckmTj428PDAiqStkN1W1HTH6LzFWrewwEHxbK8dTCvCqc
XTS5V4sJqepPR34T6bDrjw3QigJLx9gC9cfUaPasTLHPDksBSsCeC
XTS623e6h5zuyvU9rhnU58XF5QA63QPpwxzdbAj1Po6e18AqFAoTC
XTS78otuA76BjeFwcE8YDeREGsedLiFzncCuVrWFax2CQX4KStB9K
If any more info is needed I'll put it up on the forum asap.
My team Bitsapphire is creating a one-pager explaining why we think we'll be an awesome delegate!
This network has already started, but delegate campaigns should start soon and so you can still be a delegate on this network.
-
XTS5Q7j3ZAYwjGAuK6AfWiqDuahnah9MVHXxGAr8yjsxWwuEAX9xg
XTS5K6TmQjqReTUhWMg3EBjQ26VB6r26jMn4r2VEG2ykWh2xFkUpP
XTS5HHx85ASdW3b4UmyV8g2rLyYRfHeTj8aH6E1DTE11jFUBr96as
Would anyone please send me some xts ?
-
For everyone stuck, it seems to work now if you restart and clear your data at BitSharesXTS
-
PRIVATE KEYS REMOVED
Would anyone please send me some xts ?
hmm .. arent these supposed to be private keys?
adresses start with XTS
-
PRIVATE KEYS REMOVED
Would anyone please send me some xts ?
hmm .. arent these supposed to be private keys?
adresses start with XTS
Yes it seems like that
-
hmm .. arent these supposed to be private keys?
adresses start with XTS
[/quote]
I am stupid. Remove my quote from your post ? :-X :-X
-
hmm .. arent these supposed to be private keys?
adresses start with XTS
Yes it seems like that
[/quote]
I am stupid. Remove my quote from your post ? :-X :-X
-
Would anyone please send me some xts ?
hmm .. arent these supposed to be private keys?
adresses start with XTS
Both addresses and public keys start with XTS.
HeyD just posted his private keys...
-
+5%
I didn't look. I promise.
-
XTS5Q7j3ZAYwjGAuK6AfWiqDuahnah9MVHXxGAr8yjsxWwuEAX9xg
XTS5K6TmQjqReTUhWMg3EBjQ26VB6r26jMn4r2VEG2ykWh2xFkUpP
XTS5HHx85ASdW3b4UmyV8g2rLyYRfHeTj8aH6E1DTE11jFUBr96as
Would anyone please send me some xts ?
pending 2014-06-13T18:42:33 betax heyd 10.000000 XTS 0.010000 XTS 4b493368
-
Someone try sending test funds to me again please. I has none.
xeldal-del XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4 NO 0
-
The test network seems to be working fine now.
I am running delegate 96 in two separate clients. Let's see what'll happen.
-
how can i transfer xts from wallet A to wallet B？
-
I think I'm back on the main chain. Actived delegates 13,14,15, and 16. Inactive delegate puppies (I'm gonna have to change that name before this goes live.)
I've got the qt wallet compiled and running on Ubuntu. First time I run it, it runs great. Creates a wallet for me, and has most functions working correctly. I had to close it due to the fork, and now I don't know how to unlock my wallet from within Qt wallet. Does anyone know how to wallet_open in Qt client?
-
FYI
Restarted the client and I am now stuck on 1393.
-
My delegate node (bitcoiners) seems to be inactive. Please vote for it, so it starts producing blocks.
get_info
{
"blockchain_head_block_num": 1998,
"blockchain_head_block_time": "20140613T193245",
default (unlocked) >>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 0,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
default (unlocked) >>> blockchain_list_delegates
...
** Inactive:
...
304 puppies 17531378 0 0.000175315 % 0 0
297 bts101 5000000 0 5.00003e-05 % 0 0
299 bitcoiners 0 0 0 % 0 0
-
We have some significant forking still going on at this point in time. We are working very hard over here to identify the cause.
Some of the steps we have take to mitigate (but not solve) the problem is by increasing the required connection count before a delegate will start producing blocks.
Now we need to solve a bug where a node just stops receiving (or processing) blocks.
-
Am I on fork?
"blockchain_head_block_num": 1395,
"blockchain_head_block_time": "20140613T203115",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 27.556818181818183,
-
Am I on fork?
"blockchain_head_block_num": 1395,
"blockchain_head_block_time": "20140613T203115",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 27.556818181818183,
{
"blockchain_head_block_num": 1577,
"blockchain_head_block_time": "20140613T204045",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 30.417058639071808,
"network_num_connections": 22,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140613T204435",
"blockchain_random_seed": "7a2a2b3fecebb31be4824a1624877493c8bbf0d0",
"blockchain_shares": 9999914511592,
"network_num_connections_max": 100,
"network_protocol_version": 101,
"wallet_open": false,
"wallet_unlocked_until": "",
"wallet_version": 100
}
-
After blockchain resync
"blockchain_head_block_num": 2166,
"blockchain_head_block_time": "20140613T211630",
Btw does keyhotee id import works?
-
After blockchain resync
"blockchain_head_block_num": 2166,
"blockchain_head_block_time": "20140613T211630",
Btw does keyhotee id import works?
{
"blockchain_head_block_num": 2166,
"blockchain_head_block_time": "20140613T211630",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 42.395104895104893,
"network_num_connections": 6,
"wallet_unlocked_seconds_remaining": 2892273106,
"wallet_next_block_production_time": "20140613T212815",
"wallet_seconds_until_next_block_production": 706,
"wallet_local_time": "20140613T211629",
"blockchain_random_seed": "4f489d9f2842b59467d9fdec51913a1fd565178e",
"blockchain_shares": 9999952247143,
"network_num_connections_max": 100,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19691231T235959",
"wallet_version": 100
}
-
@bytemaster can you share you connected nodes ip? I still have only one connection
-
Btw seems like importing keyhotee id doent work. It always said
10 assert_exception: Assert Exception
!"Account name is already registered under a different key":
{}
th_a wallet.cpp:817 add_contact_account
-
@bytemaster can you share you connected nodes ip? I still have only one connection
I think the problem is all nodes with a public IP are filled up. If you are running a public node set the "--maximum-number-of-connections" argument to something higher than 12.
I too am only seeing 1 connection from my local computer.
-
Btw seems like importing keyhotee id doent work. It always said
10 assert_exception: Assert Exception
!"Account name is already registered under a different key":
{}
th_a wallet.cpp:817 add_contact_account
Yep, there are apparently issues here as this code was implemented quickly without testing.
-
@bytemaster can you share you connected nodes ip? I still have only one connection
I think the problem is all nodes with a public IP are filled up. If you are running a public node set the "--maximum-number-of-connections" argument to something higher than 12.
I too am only seeing 1 connection from my local computer.
Yep i'm running public node (xeon.gentoo.ru:8764) and i set num connections to 64
-
@bytemaster can you share you connected nodes ip? I still have only one connection
I think the problem is all nodes with a public IP are filled up. If you are running a public node set the "--maximum-number-of-connections" argument to something higher than 12.
I too am only seeing 1 connection from my local computer.
Yep i'm running public node (xeon.gentoo.ru:8764) and i set num connections to 64
I cannot connect to you.. are you sure it is actually running on that port?
default (unlocked) >>> network_get_info
{
"listening_on": "0.0.0.0:8764",
"node_id": "6ee4de063a50a4d0e15db46273802822f3b90069"
}
-
@bytemaster can you share you connected nodes ip? I still have only one connection
I think the problem is all nodes with a public IP are filled up. If you are running a public node set the "--maximum-number-of-connections" argument to something higher than 12.
I too am only seeing 1 connection from my local computer.
Yep i'm running public node (xeon.gentoo.ru:8764) and i set num connections to 64
I cannot connect to you.. are you sure it is actually running on that port?
default (unlocked) >>> network_get_info
{
"listening_on": "0.0.0.0:8764",
"node_id": "6ee4de063a50a4d0e15db46273802822f3b90069"
}
Yep i'm running on this port
network_get_info
{
"listening_on": "0.0.0.0:8764",
"node_id": "a194c59317e1c848347a00f48e71b8ed8088e41b"
}
ip is 79.173.81.171
-
forked again. please check block 1393 information from 2 of my bitshares clients
blockchain_get_block_by_number 1393
pan2pan (locked) >>> blockchain_get_block_by_number 1393
{
"previous": "0b2923fad01d7f85c8710b138b64b096ebd15e3e",
"block_num": 1393,
"fee_rate": 1000,
"delegate_pay_rate": 21887,
"timestamp": "20140613T130615",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "a3692fdcecf3c4405a3b873f74e7443d09c626a9",
"previous_secret": "d3bcc6efdfff53e030957afe668ac46cd8e65337",
"delegate_signature": "202002954e4399c634020a42eeb6e9f5100001dd74088eeb6f6ce76088694f1a626a5cf34c6bd090172fb3c85ad1c4d392a9a4c498e0513d879
fdc39b1b3ae4c4e",
"user_transactions": []
}
wallet-A (locked) >>> blockchain_get_block_by_number 1393
{
"previous": "c12b644291f035dc4323877b5f0f6525d7f90d78",
"block_num": 1393,
"fee_rate": 1000,
"delegate_pay_rate": 21887,
"timestamp": "20140613T130815",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "0482eee15a5f1489689acf429f161c36ca283118",
"previous_secret": "f760e8b976f9d9a4c24f2be3604ae5eca88f4f47",
"delegate_signature": "20a6ebb539d512aa10b1c381bb040bef240af5abd8af4c16f42e608900b2995fa6a9f943ea1a5220ebaa809c679856f175c7e84ec8e7a562d94
6222f2707857323",
"user_transactions": []
}
How many connections do you have?
-
I want to thank everyone who is helping us work through these bugs and resolve forks. I know these forks are frustrating and you all are putting a lot of time on your end to help us out.
-
How many connections do you have?
only one connection for each client
-
I'm seeing 3 connections at the moment, from the 64 I've set. I'm trying to run a seed node, does that need something else apart from the client running? Like a well stocked wallet or something?
ip is 149.210.177.219
network_get_info
{
"listening_on": "0.0.0.0:8764",
"node_id": "bfec892b9ae373cb4c59b5cf678cc922a5dc2b99"
}
I figured there were enough delegates to keep the network running, but I'm not seeing that many. Would you like met to setup an extra delegate for the testnet or are all delegate seats filled even though they seem to be inactive?
-
I'm seeing 3 connections at the moment, from the 64 I've set. I'm trying to run a seed node, does that need something else apart from the client running? Like a well stocked wallet or something?
ip is 149.210.177.219
network_get_info
{
"listening_on": "0.0.0.0:8764",
"node_id": "bfec892b9ae373cb4c59b5cf678cc922a5dc2b99"
}
I figured there were enough delegates to keep the network running, but I'm not seeing that many. Would you like met to setup an extra delegate for the testnet or are all delegate seats filled even though they seem to be inactive?
Delegate seats are all up for grabs based upon participating in these tests. Helping us out earns your stripes and it should pay in the long run.
-
he means in this test net...
they are all filled, but hopefully we will have delegate voting later in this round
-
he means in this test net...
they are all filled, but hopefully we will have delegate voting later in this round
Yeah I meant to help with the testnet. I'll only setup a non-testnet delegate to help bootstrap the system and if I don't get penalized for getting voted out later on, when I make way for people who want to do this as a job. I'm unable to guarantee a 24/7 full uptime for years to come and eventhough I'm not in it purely for the money, that doesn't mean I can just afford to lose the little stake I have.
In the meantime if the net is still up, would someone be so kind to send some testXTS to XTS8dQUhrQt45ovDRkXU18dag5Mpktu83N58sGfxpUKRjJcYp5W2V?
-
0 connection now.....................
pan2pan (locked) >>> getinfo
{
"blockchain_head_block_num": 2319,
"blockchain_head_block_time": "20140613T223830",
"blockchain_confirmation_requirement": 290,
"blockchain_average_delegate_participation": 39.176090468497577,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": "20140613T232530",
"wallet_seconds_until_next_block_production": 1203,
"wallet_local_time": "20140613T230527",
"blockchain_random_seed": "e8c4065391a7494cf1812b80c36b77c6e869090b",
"blockchain_shares": 9999957255332,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "",
"wallet_version": 100
}
-
Hi,
Could be a reason for the forking importing your private keys from PTS, BTC ? Am I just being silly or is it an timing coincidence.
Around 5 hours ago bytemaster and spartakus sent me 10 and 1 XTS
I also imported my keys around the same time.
Their transactions never appeared and I was already in a fork.
Restart and import wallets and things keep breaking.
Move to a VM and import the private key from XTC wallet, rescan and start seeing the transactions.
Import the wallet keys and breaks again.
Move to a VPS (just for kicks) and import the private key from XTC wallet, rescan and I don't see any balance from other wallets (PTS, BTC).
-
Hi,
Could be a reason for the forking importing your private keys from PTS, BTC ? Am I just being silly or is it an timing coincidence.
Around 5 hours ago bytemaster and spartakus sent me 10 and 1 XTS
I also imported my keys around the same time.
Their transactions never appeared and I was already in a fork.
Restart and import wallets and things keep breaking.
Move to a VM and import the private key from XTC wallet, rescan and start seeing the transactions.
Import the wallet keys and breaks again.
Move to a VPS (just for kicks) and import the private key from XTC wallet, rescan and I don't see any balance from other wallets (PTS, BTC).
Ignore that my vm and vps has just catched up on blocks, but balance is not being reflected for pts / btc
-
Hi,
Can you vote for me "betax" I have the same delegate running on a VPS and another machine.
Time for bed for me anyway.
Have fun !
-
My delegate node (bitcoiners) still has not produced any blocks. Please vote for it, so it starts working.
blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 0,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
-
I've just wiped data dir on my seed node. 95.85.33.16:8764. Feel free to connect. I'm at work, but PM me if its not visible from the main chain and I will get it back on the main chain.
-
My delegate node (bitcoiners) still has not produced any blocks. Please vote for it, so it starts working.
blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 0,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
You are now the leading contender.. :)
-
My delegate node (bitcoiners) still has not produced any blocks. Please vote for it, so it starts working.
blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 0,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
You are now the leading contender.. :)
init-delegate-1 is now out, you are in :)
-
roy (unlocked) >>> blockchain_get_blockcount
1473
roy (unlocked) >>> blockchain_get_block_by_number 1473
{
"previous": "594cb100e841b0ec850b28b5528ba35eed0137cf",
"block_num": 1473,
"fee_rate": 1000,
"delegate_pay_rate": 23007,
"timestamp": "20140613T155145",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "4e5a9bcdc3176c15677a9bb626ad1afebd2fb03d",
"previous_secret": "359c9980528d0256c421a7e7cbf0ba288f353a4c",
"delegate_signature": "1fa3ea891232bb8196c528e54f6b17782497a09cb63ca6b1f0785f9d93e529673eb0e99ef7a88dd9f3c09d3eb2488bc85d4fdf34a76e424e5d1ed8187b3bbb373f",
"user_transactions": []
}
I can not regester accounts now ,if I am in main chain
-
cgafeng (unlocked) >>> wallet_get_account
account_name: cgafeng
{
"index": 7,
"id": 303,
"name": "cgafeng",
"public_data": "cgafeng is good person",
"owner_key": "XTS8daF9rX4LiWghT2LbkV1ds2NtiZjEdCiXkkmP6ua3S6s2Vsx8n",
"active_key_history": [[
"20140613T092800",
"XTS8daF9rX4LiWghT2LbkV1ds2NtiZjEdCiXkkmP6ua3S6s2Vsx8n"
]
],
"delegate_info": {
"votes_for": 10361483474,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
I would like to be delegate.
-
roy (unlocked) >>> blockchain_get_blockcount
1473
roy (unlocked) >>> blockchain_get_block_by_number 1473
{
"previous": "594cb100e841b0ec850b28b5528ba35eed0137cf",
"block_num": 1473,
"fee_rate": 1000,
"delegate_pay_rate": 23007,
"timestamp": "20140613T155145",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "4e5a9bcdc3176c15677a9bb626ad1afebd2fb03d",
"previous_secret": "359c9980528d0256c421a7e7cbf0ba288f353a4c",
"delegate_signature": "1fa3ea891232bb8196c528e54f6b17782497a09cb63ca6b1f0785f9d93e529673eb0e99ef7a88dd9f3c09d3eb2488bc85d4fdf34a76e424e5d1ed8187b3bbb373f",
"user_transactions": []
}
I can not regester accounts now ,if I am in main chain
You are not in main chain. Looks like you are stalled (a known bug that we are working to solve).
-
I have registered as a delegate 10 hours ago, but remains inactive for a long time (don't know how to be active). Then I went to sleep (very late in my time zone). After wakeup, the connection lost (0 connection), and I can no longer find my account "ffwong-delegate-5" in the delegate list. I guess I was being kicked out and lost the status, right? (FYI, my machine is always connected to the internet, it is not my network connection problem.)
In what condition, I can maintain the connection? I am running on the node on a virtualbox virtual machine, and I have port-forwarded the randomly selected port by bitshares_client to my host machine. But the connection still lost from time to time. Is there a list of nodes that I can add? Anything I should do to make it right?
BTW, I wanted to re-register as delegate, but I am stupid to list multiple accounts when I asked people for sending me fund. The fund is separated on two accounts (1 with 10 XTS, 1 with 1XTS). The registration command does not support funding from multiple accounts. Shall I use "wallet_transfer" to transfer fund one to another? I did that last night before I slept. It seems very weird. The balance seems not right. It would be great if someone can send me 1 or 2 XTS to
ffwong-delegate-5 XTS819hyNrhVFkjEDrqM5sJmaTCS9qbUuTeFJkh81wogQFQWbRxQm
-
On recent builds I'm only getting 1 active connection. Anyone else having this issue?
-
In my experience the network code is completely botched right now. I am working with Eric to track down the cause. Very frustrating.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Np, good to know it's not just me.
-
My logs got 95 GB in 1 day which filled up the space I've assigned to the VM running the node resulting in crash of the client.
I'll increase its size and update to latest version and restart.
-
Maybe 30sec is too short for a delegate to produce a block and to be synchronized by the whole network(or 100 delegates) . How about 2 or 5 min?
In my experience the network code is completely botched right now. I am working with Eric to track down the cause. Very frustrating.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
init-delegate-118 XTS7X933vLMhkPiv3tFACokWfVhkBJwkTbrgiworsvNnWaiKdXYxZ 2014-06-14T05:22:30 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
I hire a VPS and it can runing 7*24, voting me
-
Am I still on the right one?
default (unlocked) >>> getinfo
{
"blockchain_head_block_num": 2867,
"blockchain_head_block_time": "20140614T054200",
"blockchain_confirmation_requirement": 290,
"blockchain_average_delegate_participation": 36.248131539611357,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140614T054300",
"blockchain_random_seed": "12ee3a21875e68c1aaf52fdf265e7d8a310d8cfb",
"blockchain_shares": 9999977325770,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19700101T000000",
"wallet_version": 100
}
nothing produce yet
default (unlocked) >>> wallet_get_account betax
{
"index": 8,
"id": 307,
"name": "betax",
"public_data": {},
"owner_key": "XTS8E7T1qxvfWKVZtq9HBZ8Nmv8RUSxwksukhCx3gcGEKenZN3bfh",
"active_key_history": [[
"20140613T145130",
"XTS8E7T1qxvfWKVZtq9HBZ8Nmv8RUSxwksukhCx3gcGEKenZN3bfh"
]
],
"delegate_info": {
"votes_for": 9980000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 0,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140613T145130",
"last_update": "20140613T214145",
"meta_data": null,
"account_address": "XTStm6ysCymEG9m6QR9sQVV9DRPQpfjsTQr",
"trust_level": 1,
"private_data": null
}
-
Just syncrhonized (took less than a minute with clean data dir).
Am I on the right chain?
"blockchain_head_block_num": 2870,
"blockchain_head_block_time": "20140614T054445",
-
Just syncrhonized (took less than a minute with clean data dir).
Am I on the right chain?
"blockchain_head_block_num": 2870,
"blockchain_head_block_time": "20140614T054445",
may be right. I on here:
"blockchain_head_block_num": 2879,
"blockchain_head_block_time": "20140614T055045",
-
init-delegate-1 is now out, you are in :)
Great! Thanks.
Still, delegate bitcoiners is not producing any blocks yet..
get_info
{
"blockchain_head_block_num": 2898,
"blockchain_head_block_time": "20140614T060430",
default (unlocked) >>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83010000000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 11,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
-
I can't produce even 1 block after rebuild about 8hours ago.
the network and block sync seems no problem.
attention that "wallet_seconds_until_next_block_production" is -5,
delegate (unlocked) >>> info
{
"blockchain_head_block_num": 2929,
"blockchain_head_block_time": "20140614T062800",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 35.780154924382146,
"network_num_connections": 2,
"wallet_unlocked_seconds_remaining": 99999835,
"wallet_next_block_production_time": "20140614T062815",
"wallet_seconds_until_next_block_production": -5,
"wallet_local_time": "20140614T062820",
"blockchain_random_seed": "8bb94b1e583370db1d9ed0e3e1c0ba8986812a78",
"blockchain_shares": 9999979815269,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170814T161215",
"wallet_version": 100
}
delegate (unlocked) >>> about
{
"bitshares_toolkit_revision": "2079bad65120f1a3a04ee8abc0a0e7baa345b896",
"bitshares_toolkit_revision_age": "8 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "32 hours ago",
"compile_date": "compiled on Jun 14 2014 at 07:48:30"
}
my account is 17,18,19,20.
before this upgrade, I miss only 3 blocks.
-
Oh, I know why from the source code.
delegate will not producing block when connection less than 5.
But why the connection is always 1 or 2? I have a public IP.
I can't produce even 1 block after rebuild about 8hours ago.
the network and block sync seems no problem.
attention that "wallet_seconds_until_next_block_production" is -5,
delegate (unlocked) >>> info
{
"blockchain_head_block_num": 2929,
"blockchain_head_block_time": "20140614T062800",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 35.780154924382146,
"network_num_connections": 2,
"wallet_unlocked_seconds_remaining": 99999835,
"wallet_next_block_production_time": "20140614T062815",
"wallet_seconds_until_next_block_production": -5,
"wallet_local_time": "20140614T062820",
"blockchain_random_seed": "8bb94b1e583370db1d9ed0e3e1c0ba8986812a78",
"blockchain_shares": 9999979815269,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170814T161215",
"wallet_version": 100
}
delegate (unlocked) >>> about
{
"bitshares_toolkit_revision": "2079bad65120f1a3a04ee8abc0a0e7baa345b896",
"bitshares_toolkit_revision_age": "8 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "32 hours ago",
"compile_date": "compiled on Jun 14 2014 at 07:48:30"
}
my account is 17,18,19,20.
before this upgrade, I miss only 3 blocks.
-
Oh, I know why from the source code.
delegate will not producing block when connection less than 5.
But why the connection is always 1 or 2? I have a public IP.
I can't produce even 1 block after rebuild about 8hours ago.
the network and block sync seems no problem.
attention that "wallet_seconds_until_next_block_production" is -5,
delegate (unlocked) >>> info
{
"blockchain_head_block_num": 2929,
"blockchain_head_block_time": "20140614T062800",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 35.780154924382146,
"network_num_connections": 2,
"wallet_unlocked_seconds_remaining": 99999835,
"wallet_next_block_production_time": "20140614T062815",
"wallet_seconds_until_next_block_production": -5,
"wallet_local_time": "20140614T062820",
"blockchain_random_seed": "8bb94b1e583370db1d9ed0e3e1c0ba8986812a78",
"blockchain_shares": 9999979815269,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170814T161215",
"wallet_version": 100
}
delegate (unlocked) >>> about
{
"bitshares_toolkit_revision": "2079bad65120f1a3a04ee8abc0a0e7baa345b896",
"bitshares_toolkit_revision_age": "8 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "32 hours ago",
"compile_date": "compiled on Jun 14 2014 at 07:48:30"
}
my account is 17,18,19,20.
before this upgrade, I miss only 3 blocks.
There are issues with the latest network code, but Eric and Dan are working on it.
-
roy (unlocked) >>> info
{
"blockchain_head_block_num": 2998,
"blockchain_head_block_time": "20140614T071330",
"blockchain_confirmation_requirement": 290,
"blockchain_average_delegate_participation": 35.247093023255815,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 9177,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140614T071522",
"blockchain_random_seed": "3e943fdcd182592c4d12e3d70e52e09789cad8ee",
"blockchain_shares": 9999982626684,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140614T094819",
"wallet_version": 100
}
I think I am in the main chain now , my Ip is 107.170.172.14
-
I've managed to compile and run the toolkit on an Amazon free tier micro vps, it's slooooow but it works :)
I like the new syncing messages, nice to have some running updates on the network status:
...
Listening for P2P connections on port 48362
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 361 blocks left to fetch
--- syncing with p2p network, our last block was created 2 hours ago
--- syncing with p2p network, our last block was created 37 minutes ago
Close and then reopen:
...
Attempting to connect to peer 84.238.140.192:8764
--- there are now 1 active connections to the p2p network
--- in sync with p2p network
Anyone able to send me some test XTS pls?
XTS53h8pTjQGW2QMUvNvZyWF5oU3hvNtpMFaPWCPEMvEjKeeSzCY1
-
Anyone able to send me some test XTS pls?
XTS53h8pTjQGW2QMUvNvZyWF5oU3hvNtpMFaPWCPEMvEjKeeSzCY1
3314.0 2014-06-14T10:15:30 spartako svk some xts 10.000000 XTS 0.010000 XTS 5d6e1484
-
My delegates init-delegate-21,init-delegate-22,init-delegate-23,init-delegate-24 are missing a lot of blocks because I think I have few connections.
It started with only one connection, then I added manually other 2 nodes:
network_add_node "95.85.33.16:8764" "add"
network_add_node "79.173.81.171:8764" "add"
Then I reached 3 connection in this way and after a while an other node arrived, so I have now 4 connection but I have this log:
1498558ms th_a display_current_conn ] Currently have 8 of 8 connections node.cpp:997
1498558ms th_a display_current_conn ] my id is 2ba2f63411e6677639b479d9f773bdcf913f2e22 node.cpp:998
1498558ms th_a display_current_conn ] active: 79.173.81.171:8764 with d684db4e2021b2392d85077cc5c23d72553dcb5f [outbound] node.cpp:1002
1498558ms th_a display_current_conn ] active: 84.238.140.192:50546 with 5df36814ac2ab624dee3b3f1d08d3a5af69b6b31 [inbound] node.cpp:1002
1498559ms th_a display_current_conn ] active: 95.85.33.16:8764 with 97ed6395a813c0426686056f7a4defd63e920447 [outbound] node.cpp:1002
1498559ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
1498559ms th_a display_current_conn ] handshaking: 107.170.211.129:33729 with 0000000000000000000000000000000000000000 [unknown] node.cpp:1006
1498559ms th_a display_current_conn ] handshaking: 107.170.211.129:37010 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
1498559ms th_a display_current_conn ] handshaking: 114.215.104.153:49600 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
1498559ms th_a display_current_conn ] handshaking: 119.9.78.202:43745 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
1498559ms th_a p2p_network_connect_ ] I don't need any more connections, waiting forever until something changes node.cpp:696
1498559ms th_a bind ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use tcp_socket.cpp:105
1498559ms th_a connect_to ] Failed to bind to desired local endpoint 0.0.0.0:51496, will connect using an OS-selected endpoint: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"tcp_socket.cpp","line":106,"method":"bind","hostname":"","thread_name":"th_a","timestamp":"20140614T102458.559409"},"format":"error binding to ${endpoint}: ${what}","data":{"endpoint":"0.0.0.0:51496","what":"bind: Address already in use"}}]} node.cpp:494
And in and other log part, I get this error but my wallet is UNLOCKED:
1663327ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
1663327ms th_a delegate_loop ] next block time: 20140614T102800 interval: 15 seconds now: 20140614T102743 client.cpp:436
1665327ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
1665328ms th_a delegate_loop ] next block time: 20140614T102800 interval: 15 seconds now: 20140614T102745 client.cpp:436
1665328ms th_a delegate_loop ] unable to produce block because wallet is locked client.cpp:463
1666328ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
1666328ms th_a delegate_loop ] next block time: 20140614T102800 interval: 15 seconds now: 20140614T102746 client.cpp:436
1666344ms th_a delegate_loop ] unable to produce block because wallet is locked client.cpp:463
1667344ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
1667344ms th_a delegate_loop ] next block time: 20140614T102800 interval: 15 seconds now: 20140614T102747 client.cpp:436
1667344ms th_a delegate_loop ] unable to produce block because wallet is locked client.cpp:463
1668344ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
1668345ms th_a delegate_loop ] next block time: 20140614T102800 interval: 15 seconds now: 20140614T102748 client.cpp:436
1668345ms th_a delegate_loop ] unable to produce block because wallet is locked client.cpp:463
-
I would be very thankful if anyone sends me some funds for testing.
XTS8c3oGHR9XNSRPV9yYZspcPC2HMowrp6pyadyywpRMFeCSw94E8
-
I would be very thankful if anyone sends me some funds for testing.
XTS8c3oGHR9XNSRPV9yYZspcPC2HMowrp6pyadyywpRMFeCSw94E8
3373.0 2014-06-14T10:45:30 spartako kenof 10.000000 XTS 0.010000 XTS 8541b057
-
I would be very thankful if anyone sends me some funds for testing.
XTS8c3oGHR9XNSRPV9yYZspcPC2HMowrp6pyadyywpRMFeCSw94E8
3373.0 2014-06-14T10:45:30 spartako kenof 10.000000 XTS 0.010000 XTS 8541b057
Thank you very much, I will vote for you ;)
-
Thank you very much, I will vote for you ;)
3510.0 2014-06-14T11:56:30 spartako kenof some love :) 100.000000 LOVE 0.010000 XTS d1a4285c
-
In my experience the network code is completely botched right now. I am working with Eric to track down the cause. Very frustrating.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
bytemaster, plz take it easy. Take a good sleep, forget all the f**king things.
I believe what should come will come, and what deserves be resolved will be resolved. By now, it's probably you. But no one should rush.
In the long run of DAC career, we really don't need to rush.
May the best DACs win. May all of us enjoy.
-
In my experience the network code is completely botched right now. I am working with Eric to track down the cause. Very frustrating.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
bytemaster, plz take it easy. Take a good sleep, forget all the f**king things.
I believe what should come will come, and what deserves be resolved will be resolved. By now, it's probably you. But no one should rush.
In the long run of DAC career, we really don't need to rush.
May the best DACs win. May all of us enjoy.
+5%
来自我的 HUAWEI P7-L00 上的 Tapatalk
-
Dan, be patient. what shall I do to help?
来自我的 HUAWEI P7-L00 上的 Tapatalk
-
I wish i had more IT skills and understand what you guys are talking about and be able to help... :( :(
-
Anyone able to send me some test XTS pls?
XTS53h8pTjQGW2QMUvNvZyWF5oU3hvNtpMFaPWCPEMvEjKeeSzCY1
3314.0 2014-06-14T10:15:30 spartako svk some xts 10.000000 XTS 0.010000 XTS 5d6e1484
Thanks but didn't receive anything yet, maybe you're on a different fork than me? Will leave it running but I guess we'll have to wait for the network code to be fixed.
Luckily it's the weekend and the world cup is on, so grab a beer and chill out :)
-
Luckily it's the weekend and the world cup is on, so grab a beer and chill out :)
Hope that at the end of the World Cup bitshares will be the Champion ;)
-
I'm seeing more than one connection now, alternating from 2 to occasionally 4 active connections.
Could someone send some testfunds to XTS8dQUhrQt45ovDRkXU18dag5Mpktu83N58sGfxpUKRjJcYp5W2V?
-
@spartako will you be able to send some funds to me too (enough to register as a delegate would be awesome)? Thanks in advance.
XTS6sWfWBPSxbYKuxaL7isG87w1YSdvJg6dj1J5qhzzPvYmyVTAFg
How did you get funds? I tried some ways to import my keys, but failed, haven't tried since. If you imported your keys, can you please describe how?
-
@spartako will you be able to send some funds to me too (enough to register as a delegate would be awesome)? Thanks in advance.
XTS6sWfWBPSxbYKuxaL7isG87w1YSdvJg6dj1J5qhzzPvYmyVTAFg
How did you get funds? I tried some ways to import my keys, but failed, haven't tried since. If you imported your keys, can you please describe how?
I sent you 10 XTS, I think it is enough to become delegate
3802.0 2014-06-14T14:10:00 spartako mauritso 10.000000 XTS 0.010000 XTS f9a2195e
I imported my private keys with the command :
wallet_import_private_key <BITCOIN_PRIVATEKEY> spartako
What error do you get?
-
Thanks but didn't receive anything yet, maybe you're on a different fork than me? Will leave it running but I guess we'll have to wait for the network code to be fixed.
This is my chain conf:
default (unlocked) >>> blockchain_get_config
{
"blockchain_id": "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843",
"block_interval": 15,
"max_block_size": 104857,
"target_block_size": 52428,
"block_reward": "0.104857 XTS",
"inactivity_fee_apr": 10,
"max_blockchain_size": 107374182400,
"symbol": "XTS",
"name": "BitShares XTS",
"version": 101,
"address_prefix": "XTS",
"min_block_fee": 1,
"delegate_num": 97,
"delegate_reg_fee": 10485700,
"delegate_reward_min": 104857,
"name_size_max": 63,
"symbol_size_max": 5,
"symbol_size_min": 3,
"data_size_max": 65536,
"asset_reg_fee": 10485700,
"asset_shares_max": 1000000000000000
}
default (unlocked) >>> getinfo
{
"blockchain_head_block_num": 3815,
"blockchain_head_block_time": "20140614T141530",
"blockchain_confirmation_requirement": 290,
"blockchain_average_delegate_participation": 45.07434944237918,
"network_num_connections": 5,
"wallet_unlocked_seconds_remaining": 993510,
"wallet_next_block_production_time": "20140614T141730",
"wallet_seconds_until_next_block_production": 103,
"wallet_local_time": "20140614T141547",
"blockchain_random_seed": "fccfc78074cbe32fe8d72a367fb0b60676b6b0d2",
"blockchain_shares": 10000009233720,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140626T021417",
"wallet_version": 100
}
Luckily it's the weekend and the world cup is on, so grab a beer and chill out :)
Yes a good beer and "Forza Italia" this night ;)
-
I'm seeing more than one connection now, alternating from 2 to occasionally 4 active connections.
Could someone send some testfunds to XTS8dQUhrQt45ovDRkXU18dag5Mpktu83N58sGfxpUKRjJcYp5W2V?
3821.0 2014-06-14T14:18:00 spartako joeyd 10.000000 XTS 0.010000 XTS f9982017
-
I just pushed an update that will provide better logging and querying of transaction / block validation exceptions. Updating to the latest source will help us gain greater insight into the kinds of errors that are occurring.
It seems that after I close down and re-open my client the number of connections is stuck at around 1 even though it use to have 3-4.
Updates we have coming (hopefully today)...
1) better reporting of why a node disconnects us (and/or why we disconnect the node)
2) better reporting on the status of our peer database (peers we know about but are not connected to.
There are currently 28 connections to my seed node, many of which are not behind a fire wall, and yet my own local node only has 1 connection.
--- there are now 28 active connections to the p2p network
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 3898,
"blockchain_head_block_time": "20140614T145145",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 48.019801980198018,
"network_num_connections": 28,
"wallet_unlocked_seconds_remaining": 2892209773,
"wallet_next_block_production_time": "20140614T150215",
"wallet_seconds_until_next_block_production": 613,
"wallet_local_time": "20140614T145202",
"blockchain_random_seed": "cfd4e110d8db2115d0d771cf568f47ac7cfda7e4",
"blockchain_shares": 10000013351559,
"network_num_connections_max": 100,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19691231T235959",
"wallet_version": 100
}
default (unlocked) >>> network_get_peer_info
[{
"addr": "58.62.197.41:19706",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757525,
"lastrecv": 1402757525,
"bytessent": 127280,
"bytesrecv": 8896,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "24.127.42.17:51579",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 16640,
"bytesrecv": 2336,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "053c20c062473e4a0f04701fbea17be1943ada2d (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T144535",
"bitshares_git_revision_age": "7 minutes ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "osx"
},{
"addr": "70.114.143.108:53499",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757507,
"lastrecv": 1402757507,
"bytessent": 988832,
"bytesrecv": 188256,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "4b1f9a837e96b4ae467dc86db8d53191c7908664 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T125642",
"bitshares_git_revision_age": "2 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "82.75.19.219:58018",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 776592,
"bytesrecv": 150816,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "4b1f9a837e96b4ae467dc86db8d53191c7908664 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T125642",
"bitshares_git_revision_age": "2 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "osx"
},{
"addr": "128.199.180.112:56438",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757471,
"bytessent": 271488,
"bytesrecv": 69504,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "8160735f2e1d157621db1d28ad365a9c7e7195c2 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T204717",
"bitshares_git_revision_age": "18 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "116.249.255.187:50992",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 981360,
"bytesrecv": 186240,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "209.141.177.195:37957",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 180944,
"bytesrecv": 45504,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "a095342f655c39279bc381b8dd86ed9ac34e030e (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T041808",
"bitshares_git_revision_age": "35 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "107.170.211.129:48199",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 692928,
"bytesrecv": 235584,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "137.189.91.69:62591",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 576880,
"bytesrecv": 112464,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "37f48f649735660bc89355f8d1f91c3a059b0243 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T140711",
"bitshares_git_revision_age": "25 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "137.117.246.253:1024",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 94096,
"bytesrecv": 24256,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "529290cb19b9b9f3172f46612021452c1ab2a1e4 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T072258",
"bitshares_git_revision_age": "7 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "win32"
},{
"addr": "23.239.5.30:57466",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757430,
"bytessent": 155792,
"bytesrecv": 33264,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "207.12.89.119:37918",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757470,
"lastrecv": 1402757506,
"bytessent": 138128,
"bytesrecv": 53488,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "a095342f655c39279bc381b8dd86ed9ac34e030e (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T041808",
"bitshares_git_revision_age": "35 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "188.138.107.159:37306",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757431,
"lastrecv": 1402757506,
"bytessent": 11712,
"bytesrecv": 1776,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "529290cb19b9b9f3172f46612021452c1ab2a1e4 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T072258",
"bitshares_git_revision_age": "7 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "84.238.140.192:50546",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757431,
"lastrecv": 1402757506,
"bytessent": 507072,
"bytesrecv": 201680,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "106.185.26.162:54061",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757431,
"bytessent": 113008,
"bytesrecv": 35728,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "107.170.172.14:60662",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402756466,
"lastrecv": 1402757506,
"bytessent": 74688,
"bytesrecv": 24208,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "50.174.230.86:57712",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 875600,
"bytesrecv": 173856,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "168.63.59.67:1177",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 254624,
"bytesrecv": 44784,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "5517b4ca8d1b2383bbe3cc0b66d8ef7ee9480d5c (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T204157",
"bitshares_git_revision_age": "18 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "54.76.159.139:41180",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 222720,
"bytesrecv": 39168,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "529290cb19b9b9f3172f46612021452c1ab2a1e4 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T072258",
"bitshares_git_revision_age": "7 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "107.170.170.214:45848",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 881136,
"bytesrecv": 187712,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "46.252.21.49:48681",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757470,
"bytessent": 981632,
"bytesrecv": 183488,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "8160735f2e1d157621db1d28ad365a9c7e7195c2 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T204717",
"bitshares_git_revision_age": "18 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "72.194.213.59:53851",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 901792,
"bytesrecv": 171472,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "a095342f655c39279bc381b8dd86ed9ac34e030e (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T041808",
"bitshares_git_revision_age": "35 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "95.85.33.16:8764",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757431,
"lastrecv": 1402757506,
"bytessent": 458384,
"bytesrecv": 109216,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "4f008f9abfe382a224d28d419cbdf311cb50afeb (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140612T235516",
"bitshares_git_revision_age": "39 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "180.153.142.120:8764",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757431,
"bytessent": 452480,
"bytesrecv": 79712,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "529290cb19b9b9f3172f46612021452c1ab2a1e4 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T072258",
"bitshares_git_revision_age": "7 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "176.9.234.167:51469",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757431,
"lastrecv": 1402757506,
"bytessent": 558464,
"bytesrecv": 122272,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "529290cb19b9b9f3172f46612021452c1ab2a1e4 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T072258",
"bitshares_git_revision_age": "7 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "88.204.169.242:2682",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757465,
"bytessent": 697104,
"bytesrecv": 125600,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "529290cb19b9b9f3172f46612021452c1ab2a1e4 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T072258",
"bitshares_git_revision_age": "7 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "win32"
},{
"addr": "79.173.81.171:8764",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 61216,
"bytesrecv": 92144,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "12 hours ago (newer than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
},{
"addr": "209.141.177.195:37754",
"addrlocal": "107.170.30.182:8764",
"services": "00000001",
"lastsend": 1402757506,
"lastrecv": 1402757506,
"bytessent": 317728,
"bytesrecv": 62288,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "a095342f655c39279bc381b8dd86ed9ac34e030e (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T041808",
"bitshares_git_revision_age": "35 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "40 hours ago (newer than ours)",
"platform": "linux"
}
]
-
Are there still testing?
I rebuild from the latest code and delete old data.
After sync, i got this, it stuck in block num 173:
(wallet closed) >>> getinfo
{
"blockchain_head_block_num": 173,
"blockchain_head_block_time": "20140613T031030",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 1.7747230201066886,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140614T155522",
"blockchain_random_seed": "2187e6da7507eac2aaa58bd07b8df924b548ed11",
"blockchain_shares": 10000000219072,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": false,
"wallet_unlocked_until": "",
"wallet_version": 100
}
(wallet closed) >>> blockchain_get_config
{
"blockchain_id": "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843",
"block_interval": 15,
"max_block_size": 104857,
"target_block_size": 52428,
(wallet closed) >>> network_get_peer_info
[{
"addr": "107.170.30.182:8764",
"addrlocal": "192.168.1.132:32243",
"services": "00000001",
"lastsend": 1402761483,
"lastrecv": 1402761484,
"bytessent": 50000,
"bytesrecv": 313728,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "834272898d260eb54335196fb1009332c2789785 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T223721",
"bitshares_git_revision_age": "17 hours ago (older than ours)",
"fc_git_revision_sha": "b02210a3617f86d09a2898bab17c727c73aae6f0 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T213658",
"fc_git_revision_age": "42 hours ago (older than ours)",
"platform": "linux"
}
]
-
Are there still testing?
I rebuild from the latest code and delete old data.
After sync, i got this, it stuck in block num 173:
(wallet closed) >>> getinfo
{
"blockchain_head_block_num": 173,
"blockchain_head_block_time": "20140613T031030",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 1.7747230201066886,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140614T155522",
"blockchain_random_seed": "2187e6da7507eac2aaa58bd07b8df924b548ed11",
"blockchain_shares": 10000000219072,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": false,
"wallet_unlocked_until": "",
"wallet_version": 100
}
(wallet closed) >>> blockchain_get_config
{
"blockchain_id": "ba0309904a7b0a2fb4c4c0f5796ca97eb8366726b491204434f918dc3349f843",
"block_interval": 15,
"max_block_size": 104857,
"target_block_size": 52428,
(wallet closed) >>> network_get_peer_info
[{
"addr": "107.170.30.182:8764",
"addrlocal": "192.168.1.132:32243",
"services": "00000001",
"lastsend": 1402761483,
"lastrecv": 1402761484,
"bytessent": 50000,
"bytesrecv": 313728,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "834272898d260eb54335196fb1009332c2789785 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T223721",
"bitshares_git_revision_age": "17 hours ago (older than ours)",
"fc_git_revision_sha": "b02210a3617f86d09a2898bab17c727c73aae6f0 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T213658",
"fc_git_revision_age": "42 hours ago (older than ours)",
"platform": "linux"
}
]
This is a known bug on windows builds that currently causes a predictable crash due to stack corruption, we did not reset the chain but apparently there is a bug in block 174 processing.
-
This is my state after recompiled and removed chain/ and peers.leveldb/ directory:
default (unlocked) >>> getinfo
{
"blockchain_head_block_num": 4089,
"blockchain_head_block_time": "20140614T161115",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 52.2347872913301,
"network_num_connections": 3,
"wallet_unlocked_seconds_remaining": 99999621,
"wallet_next_block_production_time": "20140614T161345",
"wallet_seconds_until_next_block_production": 143,
"wallet_local_time": "20140614T161122",
"blockchain_random_seed": "8b4428401691a199b4f1490efa22d2414c9d5087",
"blockchain_shares": 10000023086065,
"network_num_connections_max": 32,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170815T015143",
"wallet_version": 100
}
default (unlocked) >>> network_get_peer_info
[{
"addr": "84.238.140.192:50546",
"addrlocal": "188.138.107.159:8764",
"services": "00000001",
"lastsend": 1402762350,
"lastrecv": 1402762335,
"bytessent": 77344,
"bytesrecv": 305408,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "13 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (same as ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "42 hours ago (same as ours)",
"platform": "linux"
},{
"addr": "79.173.81.171:8764",
"addrlocal": "188.138.107.159:8764",
"services": "00000001",
"lastsend": 1402762350,
"lastrecv": 1402762335,
"bytessent": 10544,
"bytesrecv": 1392,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": true,
"firewall_status": "not behind a firewall",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "13 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (same as ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "42 hours ago (same as ours)",
"platform": "linux"
},{
"addr": "107.170.30.182:8764",
"addrlocal": "188.138.107.159:43596",
"services": "00000001",
"lastsend": 1402762350,
"lastrecv": 1402762350,
"bytessent": 141520,
"bytesrecv": 766064,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "834272898d260eb54335196fb1009332c2789785 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T223721",
"bitshares_git_revision_age": "18 hours ago (older than ours)",
"fc_git_revision_sha": "b02210a3617f86d09a2898bab17c727c73aae6f0 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T213658",
"fc_git_revision_age": "43 hours ago (older than ours)",
"platform": "linux"
}
]
And this is the log file regarding the network:
627501ms th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:622
627501ms th_a display_current_conn ] Currently have 7 of 8 connections node.cpp:997
627502ms th_a display_current_conn ] my id is bbe4c57e11695071622df6452d3193175a06354c node.cpp:998
627502ms th_a display_current_conn ] active: 84.238.140.192:50546 with 5df36814ac2ab624dee3b3f1d08d3a5af69b6b31 [inbound] node.cpp:1002
627502ms th_a display_current_conn ] active: 79.173.81.171:8764 with d684db4e2021b2392d85077cc5c23d72553dcb5f [inbound] node.cpp:1002
627502ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
627502ms th_a display_current_conn ] handshaking: 79.173.81.171:52096 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
627502ms th_a display_current_conn ] handshaking: 14.20.219.73:55042 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
627502ms th_a display_current_conn ] handshaking: 184.189.254.217:56448 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
627502ms th_a display_current_conn ] handshaking: 180.153.142.115:59434 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
627502ms th_a connect_to ] node_impl::connect_to(23.253.232.116:55727) node.cpp:2371
627502ms th_a display_current_conn ] Currently have 8 of 8 connections node.cpp:997
627502ms th_a display_current_conn ] my id is bbe4c57e11695071622df6452d3193175a06354c node.cpp:998
627502ms th_a display_current_conn ] active: 84.238.140.192:50546 with 5df36814ac2ab624dee3b3f1d08d3a5af69b6b31 [inbound] node.cpp:1002
627502ms th_a display_current_conn ] active: 79.173.81.171:8764 with d684db4e2021b2392d85077cc5c23d72553dcb5f [inbound] node.cpp:1002
627502ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
627502ms th_a display_current_conn ] handshaking: 23.253.232.116:55727 with 0000000000000000000000000000000000000000 [unknown] node.cpp:1006
627502ms th_a display_current_conn ] handshaking: 79.173.81.171:52096 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
627502ms th_a display_current_conn ] handshaking: 14.20.219.73:55042 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
627502ms th_a display_current_conn ] handshaking: 184.189.254.217:56448 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
627502ms th_a display_current_conn ] handshaking: 180.153.142.115:59434 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
627502ms th_a p2p_network_connect_ ] I don't need any more connections, waiting forever until something changes node.cpp:696
627502ms th_a bind ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use tcp_socket.cpp:105
627502ms th_a connect_to ] Failed to bind to desired local endpoint 0.0.0.0:8764, will connect using an OS-selected endpoint: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"tcp_socket.cpp","line":106,"method":"bind","hostname":"","thread_name":"th_a","timestamp":"20140614T161027.502647"},"format":"error binding to ${endpoint}: ${what}","data":{"endpoint":"0.0.0.0:8764","what":"bind: Address already in use"}}]} node.cpp:494
-
@spartako will you be able to send some funds to me too (enough to register as a delegate would be awesome)? Thanks in advance.
XTS6sWfWBPSxbYKuxaL7isG87w1YSdvJg6dj1J5qhzzPvYmyVTAFg
How did you get funds? I tried some ways to import my keys, but failed, haven't tried since. If you imported your keys, can you please describe how?
I sent you 10 XTS, I think it is enough to become delegate
3802.0 2014-06-14T14:10:00 spartako mauritso 10.000000 XTS 0.010000 XTS f9a2195e
I imported my private keys with the command :
wallet_import_private_key <BITCOIN_PRIVATEKEY> spartako
What error do you get?
Thank you, I will vote for you if it helps (smart way of buying votes ;)
I will try to import my private keys once again, I will post here if it works or not in a moment.
EDIT: It worked, tried the same thing a few days back, it didn't work that time.
-
@bytemaster: maybe i'am wrong, but i observed the issue due to limited p2p connections the first time after
commit f9d175e8ddb2391e2dbee74449cd3c10f307b553 in vendors submodule where upnpc.c gets removed.
Before that commit i had 8 connections in no time. Hope it helps.
-
Thank you, I will vote for you if it helps (smart way of buying votes ;)
Thanks you deserve some love ;)
4257.0 2014-06-14T17:28:30 spartako mauritso some love 100.000000 LOVE 0.010000 XTS 7067702c
I will try to import my private keys once again, I will post here if it works or not in a moment.
EDIT: It worked, tried the same thing a few days back, it didn't work that time.
There was a bug in the import command and it was fixed.
-
We are making progress here... once we get this up to 100% we will know we have a solid network :)
"blockchain_average_delegate_participation": 54.463784390791687,
-
@bytemaster: maybe i'am wrong, but i observed the issue due to limited p2p connections the first time after
commit f9d175e8ddb2391e2dbee74449cd3c10f307b553 in vendors submodule where upnpc.c gets removed.
Before that commit i had 8 connections in no time. Hope it helps.
Thanks for the tip, we will look into it.
-
We are making progress here... once we get this up to 100% we will know we have a solid network :)
"blockchain_average_delegate_participation": 54.463784390791687,
+5% +5% +5%
My three nodes:
"blocks_produced": 76,
"blocks_missed": 31,
"blocks_produced": 80,
"blocks_missed": 29,
"blocks_produced": 76,
"blocks_missed": 30,
-
We are making progress here... once we get this up to 100% we will know we have a solid network :)
"blockchain_average_delegate_participation": 54.463784390791687,
strangely my delegate (bitcoiners) is still not producing any blocks..
get_info
{
"blockchain_head_block_num": 4298,
"blockchain_head_block_time": "20140614T174845",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 54.18994413407821,
"network_num_connections": 3,
"wallet_unlocked_seconds_remaining": 999994911,
"wallet_next_block_production_time": "20140614T180415",
"wallet_seconds_until_next_block_production": 921,
"wallet_local_time": "20140614T174854",
"blockchain_random_seed": "fe9131fe0b860cb38cc45efaf16a9490601333f2",
"blockchain_shares": 10000023565531,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19100115T114229",
"wallet_version": 100
}
default (unlocked) >>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83118870000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 39,
"pay_balance": 0,
-
Now that my machine produces blocks successfully I'd like to reoffer my pub-keys for the discared delegates:
public key: XTS6DTmCuhUgGyN3sE2qxe7x21Fon9yqYrn9nErGLVqpiRJg9MvAH
public key: XTS8Y443qpsYp5hpmczg7NvDtqumZvzP8Az88n2EDrKECzYJKwMDP
public key: XTS5dLdpSdVZEcT7JNFL6Q7CJ8kxxj2geX7xCNJRhAK543gULNoK2
public key: XTS5oSzGcPetswPJSQ9s9qoXRdfax1oVVWCZsaKnBS5Q8u7gawZ6B (this one is active in the current testnet)
public key: XTS7e4pNDgLy7C7T6haye45PLrTRvH9FfAKpj8BAS3fbXNd6EtYEM
-
We are making progress here... once we get this up to 100% we will know we have a solid network :)
"blockchain_average_delegate_participation": 54.463784390791687,
strangely my delegate (bitcoiners) is still not producing any blocks..
get_info
{
"blockchain_head_block_num": 4298,
"blockchain_head_block_time": "20140614T174845",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 54.18994413407821,
"network_num_connections": 3,
"wallet_unlocked_seconds_remaining": 999994911,
"wallet_next_block_production_time": "20140614T180415",
"wallet_seconds_until_next_block_production": 921,
"wallet_local_time": "20140614T174854",
"blockchain_random_seed": "fe9131fe0b860cb38cc45efaf16a9490601333f2",
"blockchain_shares": 10000023565531,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19100115T114229",
"wallet_version": 100
}
default (unlocked) >>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83118870000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 39,
"pay_balance": 0,
"blockchain_head_block_num": 4330,
"blockchain_head_block_time": "20140614T180115",
Can you print out your peers?
Can you restart your peer and see if that allows it to produce blocks.
This is a very curious case.
-
We are making progress here... once we get this up to 100% we will know we have a solid network :)
"blockchain_average_delegate_participation": 54.463784390791687,
strangely my delegate (bitcoiners) is still not producing any blocks..
get_info
{
"blockchain_head_block_num": 4298,
"blockchain_head_block_time": "20140614T174845",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 54.18994413407821,
"network_num_connections": 3,
"wallet_unlocked_seconds_remaining": 999994911,
"wallet_next_block_production_time": "20140614T180415",
"wallet_seconds_until_next_block_production": 921,
"wallet_local_time": "20140614T174854",
"blockchain_random_seed": "fe9131fe0b860cb38cc45efaf16a9490601333f2",
"blockchain_shares": 10000023565531,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19100115T114229",
"wallet_version": 100
}
default (unlocked) >>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83118870000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 39,
"pay_balance": 0,
When did you build your client ? BM updated /libraries/client/client.cpp earlier today, you can only produce blocks when you have more than 5 connections if you built your client with this update.
https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/client/client.cpp line 450.
-
We are making progress here... once we get this up to 100% we will know we have a solid network :)
"blockchain_average_delegate_participation": 54.463784390791687,
strangely my delegate (bitcoiners) is still not producing any blocks..
get_info
{
"blockchain_head_block_num": 4298,
"blockchain_head_block_time": "20140614T174845",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 54.18994413407821,
"network_num_connections": 3,
"wallet_unlocked_seconds_remaining": 999994911,
"wallet_next_block_production_time": "20140614T180415",
"wallet_seconds_until_next_block_production": 921,
"wallet_local_time": "20140614T174854",
"blockchain_random_seed": "fe9131fe0b860cb38cc45efaf16a9490601333f2",
"blockchain_shares": 10000023565531,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19100115T114229",
"wallet_version": 100
}
default (unlocked) >>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83118870000,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 39,
"pay_balance": 0,
Install NTP and sync your local time .. that fixed it for me!
-
When did you build your client ? BM updated /libraries/client/client.cpp earlier today, you can only produce blocks when you have more than 5 connections if you built your client with this update.
https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/client/client.cpp line 450.
Modify message
Good catch!
-
Install NTP and sync your local time .. that fixed it for me!
The client now has a built in NTP service... I suppose I could add checks to make sure it actually worked properly. It doesn't change your system clock, but does update the offset it the client uses for blockchain validation.
-
Can you print out your peers?
Can you restart your peer and see if that allows it to produce blocks.
This is a very curious case.
network_get_peer_info
[{
"addr": "107.170.30.182:8764",
"addrlocal": "207.12.89.119:36129",
"services": "00000001",
"lastsend": 1402770137,
"lastrecv": 1402770137,
"bytessent": 1024,
"bytesrecv": 12400,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "834272898d260eb54335196fb1009332c2789785 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T223721",
"bitshares_git_revision_age": "20 hours ago (older than ours)",
"fc_git_revision_sha": "b02210a3617f86d09a2898bab17c727c73aae6f0 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T213658",
"fc_git_revision_age": "45 hours ago (older than ours)",
"platform": "linux"
}
]
Node restarted. Will update with results.
-
When did you build your client ? BM updated /libraries/client/client.cpp earlier today, you can only produce blocks when you have more than 5 connections if you built your client with this update.
https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/client/client.cpp line 450.
client built from code pulled in the last hour.
get_info
{
"blockchain_head_block_num": 4369,
"blockchain_head_block_time": "20140614T182045",
"blockchain_confirmation_requirement": 284,
"blockchain_average_delegate_participation": 54.957507082152972,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 999999991,
"wallet_next_block_production_time": "20140614T183700",
"wallet_seconds_until_next_block_production": 832,
"wallet_local_time": "20140614T182308",
"blockchain_random_seed": "9aaecbe4f4974f5231326f3eb1f37b064a6b405b",
"blockchain_shares": 10000027393425,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19100115T134123",
"wallet_version": 100
}
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "5d2f9a71c69fd8eb5aebf33ead1d1f3fb2090121",
"bitshares_toolkit_revision_age": "78 minutes ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "44 hours ago",
"compile_date": "compiled on Jun 14 2014 at 17:16:08"
}
-
It appears that the P2P connectivity issues are the problem for you. Right now we are adding extra code to give us greater visibility into the state of the connections and help diagnose these kinds of issues.
I just added code to catch and report the reason why your block didn't get produced. There is a new RPC command 'list_errors' that will dump major exceptions:
1) why you didn't produce a block when it was your turn
2) why a block or transaction was rejected
3) ... coming soon ... why a peer was intentionally disconnected
4) ... coming soon ... why you were intentionally disconnected from a peer.
-
When did you build your client ? BM updated /libraries/client/client.cpp earlier today, you can only produce blocks when you have more than 5 connections if you built your client with this update.
https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/client/client.cpp line 450.
client built from code pulled in the last hour.
get_info
{
"blockchain_head_block_num": 4369,
"blockchain_head_block_time": "20140614T182045",
"blockchain_confirmation_requirement": 284,
"blockchain_average_delegate_participation": 54.957507082152972,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 999999991,
"wallet_next_block_production_time": "20140614T183700",
"wallet_seconds_until_next_block_production": 832,
"wallet_local_time": "20140614T182308",
"blockchain_random_seed": "9aaecbe4f4974f5231326f3eb1f37b064a6b405b",
"blockchain_shares": 10000027393425,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19100115T134123",
"wallet_version": 100
}
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "5d2f9a71c69fd8eb5aebf33ead1d1f3fb2090121",
"bitshares_toolkit_revision_age": "78 minutes ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "44 hours ago",
"compile_date": "compiled on Jun 14 2014 at 17:16:08"
}
So you have to wait till you get 5 or more connections. Now you only have one.
-
When did you build your client ? BM updated /libraries/client/client.cpp earlier today, you can only produce blocks when you have more than 5 connections if you built your client with this update.
https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/client/client.cpp line 450.
client built from code pulled in the last hour.
get_info
{
"blockchain_head_block_num": 4369,
"blockchain_head_block_time": "20140614T182045",
"blockchain_confirmation_requirement": 284,
"blockchain_average_delegate_participation": 54.957507082152972,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 999999991,
"wallet_next_block_production_time": "20140614T183700",
"wallet_seconds_until_next_block_production": 832,
"wallet_local_time": "20140614T182308",
"blockchain_random_seed": "9aaecbe4f4974f5231326f3eb1f37b064a6b405b",
"blockchain_shares": 10000027393425,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19100115T134123",
"wallet_version": 100
}
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "5d2f9a71c69fd8eb5aebf33ead1d1f3fb2090121",
"bitshares_toolkit_revision_age": "78 minutes ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "44 hours ago",
"compile_date": "compiled on Jun 14 2014 at 17:16:08"
}
Considering I used my shares to get you voted a delegate, I am interested in getting you producing blocks :)
-
probably not intentional behavior:
default (unlocked) >>> info
{
"blockchain_head_block_num": 4401,
"blockchain_head_block_time": "20140614T183615",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 55.207740466704607,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 119092,
"wallet_next_block_production_time": "20140614T183630",
"wallet_seconds_until_next_block_production": -14,
"wallet_local_time": "20140614T183644",
"blockchain_random_seed": "041233f34649b2b845dc6108235be7d49ca93a9c",
"blockchain_shares": 10000029131857,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140616T034136",
"wallet_version": 100
}
-
I have some positiv feedback .. all fine here :-) .. Yehaa!
default (unlocked) >>> list_errors
[]
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 4420,
"blockchain_head_block_time": "20140614T184415",
"blockchain_confirmation_requirement": 285,
"blockchain_average_delegate_participation": 55.396916047972589,
"network_num_connections": 9,
"wallet_unlocked_seconds_remaining": 2892195830,
"wallet_next_block_production_time": "20140614T190645",
"wallet_seconds_until_next_block_production": 1340,
"wallet_local_time": "20140614T184425",
"blockchain_random_seed": "36860d7c6b2cc507d28f7b6ac4116db770765157",
"blockchain_shares": 10000030167927,
"network_num_connections_max": 64,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19691231T235959",
"wallet_version": 100
}
-
I tried to run delegate 96 with unlocked status in two clients again. Client A is in Japan while B is in China. I had them connected to each other.
So far these two clients are running well (at least they are on the same chain) . 'They' have produced three blocks 4399 & 4452 & 4511 and not got fired. Is it normal ? How can I tell which block was produced by which node ?
-
I should be up and running. Please remember to add my seed node with
network_add_node "95.85.33.16:8764" add
You can even write it into your config.json so it will attempt to connect at startup.
Thats what I had to do for the qt wallet since I can't enter commands in it. Also I figured out how to get it to open the default wallet. Right click on the wallet and hit reload. Wow do I feel stupid. I still can't get it to accept arguments when launching though. Is that a known issue?
I know the qt wallet has rightfully taken a back burner to the network code. I am just playing with it because I am not knowledgable enough about C++ or networking to help out in those areas.
-
I tried to run delegate 96 with unlocked status in two clients again. Client A is in Japan while B is in China. I had them connected to each other.
So far these two clients are running well (at least they are on the same chain) . 'They' have produced three blocks 4399 & 4452 & 4511 and not got fired. Is it normal ? How can I tell which block was produced by which node ?
You don't get auto-fired yet, in fact this "auto" fire will happen on the client side and it is not guaranteed unless enough stake is online and enough people want to enable auto-firing.
There is no easy way to map delegate signature to IP, this is by design.
-
I should be up and running. Please remember to add my seed node with
network_add_node "95.85.33.16:8764 add
You can even write it into your config.json so it will attempt to connect at startup.
Thats what I had to do for the qt wallet since I can't enter commands in it. Also I figured out how to get it to open the default wallet. Right click on the wallet and hit reload. Wow do I feel stupid. I still can't get it to accept arguments when launching though. Is that a known issue?
I know the qt wallet has rightfully taken a back burner to the network code. I am just playing with it because I am not knowledgable enough about C++ or networking to help out in those areas.
This helped immediately. Thanks. you forgot a " in your example
should be
network_add_node "95.85.33.16:8764" add
-
I should be up and running. Please remember to add my seed node with
network_add_node "95.85.33.16:8764 add
You can even write it into your config.json so it will attempt to connect at startup.
Thats what I had to do for the qt wallet since I can't enter commands in it. Also I figured out how to get it to open the default wallet. Right click on the wallet and hit reload. Wow do I feel stupid. I still can't get it to accept arguments when launching though. Is that a known issue?
I know the qt wallet has rightfully taken a back burner to the network code. I am just playing with it because I am not knowledgable enough about C++ or networking to help out in those areas.
This helped immediately. Thanks. you forgot a " in your example
should be
network_add_node "95.85.33.16:8764" add
Thanks. I fixed my original post.
-
Ha .. my first pull request to the bitshares_toolkit repo :-)
https://github.com/BitShares/bitshares_toolkit/pull/284
BTW: I am no coder :) took me like 20 minutes to figure this out :)
EDIT: you can now vote for my keyhotee-ID as delegate
wallet_set_delegate_trust_level xeroc 10
-
Rebuilt delegate node from latest. Deleted data dir and recreated wallet, imported delegate private key.
Restarted.
Still have only one connection
get_info
{
"blockchain_head_block_num": 4584,
"blockchain_head_block_time": "20140614T195900",
"blockchain_confirmation_requirement": 285,
"blockchain_average_delegate_participation": 55.843408175014396,
"network_num_connections": 1,
about
{
"bitshares_toolkit_revision": "096d7a830d80c7911e845eb9c3e5f05656444e24",
"bitshares_toolkit_revision_age": "2 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "45 hours ago",
"compile_date": "compiled on Jun 14 2014 at 20:25:16"
list_errors
[]
network_get_peer_info
[{
"addr": "107.170.30.182:8764",
"addrlocal": "207.12.89.119:47892",
"services": "00000001",
"lastsend": 1402775836,
"lastrecv": 1402775836,
"bytessent": 221792,
"bytesrecv": 1160032,
"conntime": "",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "834272898d260eb54335196fb1009332c2789785 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T223721",
"bitshares_git_revision_age": "21 hours ago (older than ours)",
"fc_git_revision_sha": "b02210a3617f86d09a2898bab17c727c73aae6f0 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T213658",
"fc_git_revision_age": "46 hours ago (older than ours)",
"platform": "linux"
}
from ~/.BitsharesXTS/default.log
node_impl::connect_to(106.185.26.48:54601) node.cpp:2371
470698ms th_a display_current_conn ] Currently have 8 of 8 connections node.cpp:997
470698ms th_a display_current_conn ] my id is 13c8b9e2d6df5b15bef116666c0d8a9f513b7913 node.cpp:998
470698ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
470698ms th_a display_current_conn ] handshaking: 106.185.26.48:54601 with 0000000000000000000000000000000000000000 [unknown] node.cpp:1006
470699ms th_a display_current_conn ] handshaking: 106.185.26.48:49342 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
470699ms th_a display_current_conn ] handshaking: 106.185.26.48:39322 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
470699ms th_a display_current_conn ] handshaking: 106.185.26.48:41107 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
470699ms th_a display_current_conn ] handshaking: 180.153.142.115:59434 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
470699ms th_a display_current_conn ] handshaking: 180.153.142.115:34896 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
470699ms th_a display_current_conn ] handshaking: 180.153.142.115:44341 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
470699ms th_a p2p_network_connect_ ] I don't need any more connections, waiting forever until something changes node.cpp:696
471410ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
473412ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
475415ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
477417ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
479420ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
481423ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
481982ms th_a on_item_ids_inventor ] received inventory of 1 items from peer 107.170.30.182:8764 node.cpp:1739
481982ms th_a on_item_ids_inventor ] addinged item 08337d57a48e09ef3d68c3f87fa9cad1c28c57df from inventory message to our list of items to fetch node.cpp:1766
481982ms th_a fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:794
481983ms th_a fetch_items_loop ] requesting item 08337d57a48e09ef3d68c3f87fa9cad1c28c57df from peer 107.170.30.182:8764 node.cpp:804
481984ms th_a dump_node_status ] ----------------- PEER STATUS UPDATE -------------------- node.cpp:2406
481984ms th_a dump_node_status ] number of peers: 1 active, 7, 124 closing. attempting to maintain 8 - 12 peers node.cpp:2409
481985ms th_a dump_node_status ] active peer 107.170.30.182:8764 peer_is_in_sync_with_us:true we_are_in_sync_with_peer:true node.cpp:2414
481985ms th_a dump_node_status ] handshaking peer 106.185.26.48:54601 in state disconnected node.cpp:2421
481985ms th_a dump_node_status ] handshaking peer 106.185.26.48:49342 in state disconnected node.cpp:2421
481985ms th_a dump_node_status ] handshaking peer 106.185.26.48:39322 in state disconnected node.cpp:2421
481985ms th_a dump_node_status ] handshaking peer 106.185.26.48:41107 in state disconnected node.cpp:2421
481985ms th_a dump_node_status ] handshaking peer 180.153.142.115:59434 in state disconnected node.cpp:2421
481985ms th_a dump_node_status ] handshaking peer 180.153.142.115:34896 in state disconnected node.cpp:2421
481985ms th_a dump_node_status ] handshaking peer 180.153.142.115:44341 in state disconnected node.cpp:2421
481985ms th_a dump_node_status ] --------- MEMORY USAGE ------------ node.cpp:2424
481985ms th_a dump_node_status ] node._active_sync_requests size: 4568 (this is known to be broken) node.cpp:2425
-
3257792ms th_a display_current_conn ] handshaking: 92.243.18.20:52599 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a display_current_conn ] handshaking: 107.170.30.182:58490 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a display_current_conn ] handshaking: 188.138.107.159:47379 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a display_current_conn ] handshaking: 188.138.107.159:47223 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a trigger_p2p_network_ ] Triggering connect loop now node.cpp:710
3257793ms th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:622
3257793ms th_a display_current_conn ] Currently have 7 of 8 connections node.cpp:997
3257793ms th_a display_current_conn ] my id is 51194ea22bd49766f3b20ea7b3f0ecf1ec62030e node.cpp:998
3257793ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
3257793ms th_a display_current_conn ] handshaking: 176.9.234.167:44912 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a display_current_conn ] handshaking: 107.170.30.182:34344 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a display_current_conn ] handshaking: 92.243.18.20:52599 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a display_current_conn ] handshaking: 107.170.30.182:58490 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a display_current_conn ] handshaking: 188.138.107.159:47379 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257793ms th_a display_current_conn ] handshaking: 188.138.107.159:47223 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a connect_to ] node_impl::connect_to(176.9.234.167:46785) node.cpp:2371
3257794ms th_a display_current_conn ] Currently have 8 of 8 connections node.cpp:997
3257794ms th_a display_current_conn ] my id is 51194ea22bd49766f3b20ea7b3f0ecf1ec62030e node.cpp:998
3257794ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
3257794ms th_a display_current_conn ] handshaking: 176.9.234.167:44912 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 107.170.30.182:34344 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 176.9.234.167:46785 with 0000000000000000000000000000000000000000 [unknown] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 92.243.18.20:52599 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 107.170.30.182:58490 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 188.138.107.159:47379 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 188.138.107.159:47223 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a p2p_network_connect_ ] I don't need any more connections, waiting forever until something changes node.cpp:696
3257794ms th_a connect_to ] fatal: error connecting to peer 107.170.30.182:58490: 0 exception: unspecified
Broken pipe
{"message":"Broken pipe"}
asio asio.cpp:28 read_write_handler node.cpp:503
3257794ms th_a display_current_conn ] Currently have 7 of 8 connections node.cpp:997
3257794ms th_a display_current_conn ] my id is 51194ea22bd49766f3b20ea7b3f0ecf1ec62030e node.cpp:998
3257794ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
3257794ms th_a display_current_conn ] handshaking: 176.9.234.167:44912 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 107.170.30.182:34344 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 176.9.234.167:46785 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 92.243.18.20:52599 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 188.138.107.159:47379 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a display_current_conn ] handshaking: 188.138.107.159:47223 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257794ms th_a trigger_p2p_network_ ] Triggering connect loop now node.cpp:710
3257794ms th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:622
3257795ms th_a display_current_conn ] Currently have 7 of 8 connections node.cpp:997
3257795ms th_a display_current_conn ] my id is 51194ea22bd49766f3b20ea7b3f0ecf1ec62030e node.cpp:998
3257795ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
3257795ms th_a display_current_conn ] handshaking: 176.9.234.167:44912 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 107.170.30.182:34344 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 176.9.234.167:46785 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 92.243.18.20:52599 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 188.138.107.159:47379 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 188.138.107.159:47223 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a connect_to ] node_impl::connect_to(188.138.107.159:50070) node.cpp:2371
3257795ms th_a display_current_conn ] Currently have 8 of 8 connections node.cpp:997
3257795ms th_a display_current_conn ] my id is 51194ea22bd49766f3b20ea7b3f0ecf1ec62030e node.cpp:998
3257795ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
3257795ms th_a display_current_conn ] handshaking: 176.9.234.167:44912 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 107.170.30.182:34344 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 176.9.234.167:46785 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 92.243.18.20:52599 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 188.138.107.159:50070 with 0000000000000000000000000000000000000000 [unknown] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 188.138.107.159:47379 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a display_current_conn ] handshaking: 188.138.107.159:47223 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257795ms th_a p2p_network_connect_ ] I don't need any more connections, waiting forever until something changes node.cpp:696
3257809ms th_a connect_to ] fatal: error connecting to peer 107.170.30.182:34344: 0 exception: unspecified
Broken pipe
{"message":"Broken pipe"}
asio asio.cpp:28 read_write_handler node.cpp:503
3257809ms th_a display_current_conn ] Currently have 7 of 8 connections node.cpp:997
3257809ms th_a display_current_conn ] my id is 51194ea22bd49766f3b20ea7b3f0ecf1ec62030e node.cpp:998
3257809ms th_a display_current_conn ] active: 107.170.30.182:8764 with 42e86a6e5638c95a4b3fdfde811de33a6d9ecedd [outbound] node.cpp:1002
3257809ms th_a display_current_conn ] handshaking: 176.9.234.167:44912 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257809ms th_a display_current_conn ] handshaking: 176.9.234.167:46785 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257809ms th_a display_current_conn ] handshaking: 92.243.18.20:52599 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257809ms th_a display_current_conn ] handshaking: 188.138.107.159:50070 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257809ms th_a display_current_conn ] handshaking: 188.138.107.159:47379 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257809ms th_a display_current_conn ] handshaking: 188.138.107.159:47223 with 0000000000000000000000000000000000000000 [outbound] node.cpp:1006
3257809ms th_a trigger_p2p_network_ ] Triggering connect loop now node.cpp:710
3257809ms th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:622
I'm getting a bunch of repeated attempts to handshake the same apparently dead nodes. If I manually network_add_node a live node, my active connection count increases, but manually adding the nodes to which it repeatedly attempts to connect does nothing.
-
@bitcoinerS @Trog Eric is working on this exact issue right now. If you want a list of nodes to connect to for now you can use "network_list_potential_peers"
-
@bitcoinerS @Trog Eric is working on this exact issue right now. If you want a list of nodes to connect to for now you can use "network_list_potential_peers"
>>> network_list_potential_peers
Error: invalid command "network_list_potential_peers"
-
@bitcoinerS @Trog Eric is working on this exact issue right now. If you want a list of nodes to connect to for now you can use "network_list_potential_peers"
>>> network_list_potential_peers
Error: invalid command "network_list_potential_peers"
Are you up to date?
-
@bitcoinerS @Trog Eric is working on this exact issue right now. If you want a list of nodes to connect to for now you can use "network_list_potential_peers"
>>> network_list_potential_peers
Error: invalid command "network_list_potential_peers"
Are you up to date?
>>> about
{
"bitshares_toolkit_revision": "096d7a830d80c7911e845eb9c3e5f05656444e24",
"bitshares_toolkit_revision_age": "2 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "46 hours ago",
"compile_date": "compiled on Jun 14 2014 at 20:25:16"
}
-
@bitcoinerS @Trog Eric is working on this exact issue right now. If you want a list of nodes to connect to for now you can use "network_list_potential_peers"
>>> network_list_potential_peers
Error: invalid command "network_list_potential_peers"
Are you up to date?
>>> about
{
"bitshares_toolkit_revision": "096d7a830d80c7911e845eb9c3e5f05656444e24",
"bitshares_toolkit_revision_age": "2 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "46 hours ago",
"compile_date": "compiled on Jun 14 2014 at 20:25:16"
}
You're not up to date. You can also check using github or just by trying to pull.
-
Are there any way to import keyhotee id? I always get thet account already registered with different key. I'm sure that brainkey is valid however are there possibility to check it?
-
Are there any way to import keyhotee id? I always get thet account already registered with different key. I'm sure that brainkey is valid however are there possibility to check it?
Was your KID not all lowercase? If so this might have fixed the issue, try now.
https://github.com/BitShares/bitshares_toolkit/pull/284
-
Are there any way to import keyhotee id? I always get thet account already registered with different key. I'm sure that brainkey is valid however are there possibility to check it?
Was your KID not all lowercase? If so this might have fixed the issue, try now.
https://github.com/BitShares/bitshares_toolkit/pull/284
It was in lower case. So it shouldnt be issue. However i cannot import it. So any possibiliti to check if i use right brainwallet?
-
So I started adding nodes by hand and it would connect.... don't add the same node twice or it will disconnect (known bug)... we are working out why the peer database isn't doing the right thing, but for now this gets me better connected.
(wallet closed) >>> network_add_node "180.153.142.120:8764" add
OK
--- there are now 2 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "162.243.127.243:33933" add
OK
--- there are now 3 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "84.238.140.192:50546" add
OK
--- there are now 4 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "107.170.30.182:48499" add
OK
(wallet closed) >>> network_add_node "107.170.170.214:40767" add
OK
--- there are now 5 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "107.170.211.129:48199" add
OK
--- there are now 6 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "176.9.234.167:39251" add
OK
(wallet closed) >>> network_add_node "107.170.30.182:8764" add
OK
--- there are now 7 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "106.185.24.234:48807" add
OK
--- there are now 8 active connections to the p2p network
--- in sync with p2p network
-
@bytemaster my public node now has 23 connections from peer db
-
Latest build fails to start.
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Starting JSON RPC server on port 44428 (localhost only)
Starting HTTP JSON RPC server on port 9989 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
{"method":"read","len":23,"over":1}
th_a datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
{"type":"uint8_t"}
th_a raw.hpp:440 unpack
optional<fc::exception>
{"type":"fc::exception"}
th_a raw.hpp:164 unpack
Error unpacking field last_error
{"field":"last_error"}
th_a raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
{"type":"bts::net::potential_peer_record"}
-
Same here:
Logging to file "/Users/maurits/Library/Application Support/BitSharesXTS/default.log"
Logging RPC to file "/Users/maurits/Library/Application Support/BitSharesXTS/rpc.log"
Loading config "/Users/maurits/Library/Application Support/BitSharesXTS/config.json"
{
"rpc": {
"rpc_user": "user",
"rpc_password": "pass",
"rpc_endpoint": "127.0.0.1:5681",
"httpd_endpoint": "127.0.0.1:5680",
"htdocs": "/Users/maurits/bitsharesxts/web_wallet/generated"
},
"default_peers": [
"107.170.30.182:8764",
"114.215.104.153:8764",
"84.238.140.192:8764"
],
"ignore_console": false,
"logging": {
"includes": [],
"appenders": [],
"loggers": []
}
}
Loading blockchain from "/Users/maurits/Library/Application Support/BitSharesXTS/chain"
Starting JSON RPC server on port 5681 (localhost only)
Starting HTTP JSON RPC server on port 5680 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
{"method":"read","len":23,"over":1}
th_a datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
{"type":"uint8_t"}
th_a raw.hpp:440 unpack
optional<fc::exception>
{"type":"fc::exception"}
th_a raw.hpp:164 unpack
Error unpacking field last_error
{"field":"last_error"}
th_a raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
{"type":"bts::net::potential_peer_record"}
th_a raw.hpp:440 unpack
-
Resync your blockchain
-
I recompiled and removed chain/ and peers.leveldb/ and relunched but I get segfault after a while.
This is the log file
463053ms th_a get_property ] property last_random_seed_id chain_database.cpp:1711
463057ms th_a on_new_block ] After push_block, current head block is 3072 client.cpp:534
463057ms th_a process_backlog_of_s ] sync: client accpted the block, we now have only 1798 items left to fetch before we're in sync node.cpp:1924
463057ms th_a process_backlog_of_s ] Popped item from front of 107.170.30.182:8764's sync list, new list length is 1798 node.cpp:1954
463058ms th_a process_backlog_of_s ] Currently backlog is 0 blocks node.cpp:2000
463058ms th_a trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:794
463058ms th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:748
463058ms th_a request_sync_item_fr ] requesting item 22718b464eaa3d76d330ea6bf1dd847b072af4cf from peer 107.170.30.182:8764 node.cpp:735
463058ms th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:784
463152ms th_a process_block_during ] received a sync block from peer 107.170.30.182:8764 node.cpp:2023
463152ms th_a process_backlog_of_s ] sync: this block is a potential first block, passing it to the client node.cpp:1895
463152ms th_a handle_message ] CLIENT: just received block 22718b464eaa3d76d330ea6bf1dd847b072af4cf client.cpp:599
463152ms th_a on_new_block ] Received a new block from the p2p network, current head block is 3072, new block is {"previous":"664e6900488c7fc11e445666fcb0abfdb3aefae4","block_num":3073,"fee_rate":1000,"delegate_pay_rate":42168,"timestamp":"20140614T075900","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"21ac19c3861e30e51a5a18df3b21d0338bda7193","previous_secret":"b869a10fd0309834887795b225e9fd8da03cdc77","delegate_signature":"1fda702f83eeab2f9de5ff38fe5fdff5c0ce519305d8838a0cad86cde78326618f9dac8d6cfbd7f9be0ccba9bdf3e507998d0498a680b8fa28a195cdf0e0a3017e","user_transactions":[]}, current head block is 3072 client.cpp:518
463152ms th_a get_property ] property last_random_seed_id chain_database.cpp:1711
463152ms th_a store_and_index ] we already know about its previous: 664e6900488c7fc11e445666fcb0abfdb3aefae4 chain_database.cpp:350
463152ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463152ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property confirmation_requirement chain_database.cpp:1711
463154ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
463154ms th_a get_property ] property last_random_seed_id chain_database.cpp:1711
463154ms th_a get_property ] property last_random_seed_id chain_database.cpp:1711
463154ms th_a get_property ] property confirmation_requirement chain_database.cpp:1711
463155ms th_a get_property ] property last_random_seed_id chain_database.cpp:1711
463159ms th_a on_new_block ] After push_block, current head block is 3073 client.cpp:534
463159ms th_a process_backlog_of_s ] sync: client accpted the block, we now have only 1797 items left to fetch before we're in sync node.cpp:1924
463159ms th_a process_backlog_of_s ] Popped item from front of 107.170.30.182:8764's sync list, new list length is 1797 node.cpp:1954
463159ms th_a process_backlog_of_s ] Currently backlog is 0 blocks node.cpp:2000
463159ms th_a trigger_fetch_sync_i ] Triggering fetch sync items loop now node.cpp:794
463159ms th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:748
463159ms th_a request_sync_item_fr ] requesting item 6a9d99709e1b2fa7ef4f607c7d086ecb3b9f69fc from peer 107.170.30.182:8764 node.cpp:735
463159ms th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:784
463173ms th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:44341 due to inactivity of at least 45 seconds node.cpp:931
463173ms th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:34353 due to inactivity of at least 45 seconds node.cpp:931
463174ms th_a terminate_inactive_c ] Disconnecting from handshaking peer 106.185.26.48:35830 due to inactivity of at least 45 seconds node.cpp:931
463174ms th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:34255 due to inactivity of at least 45 seconds node.cpp:931
463174ms th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:33142 due to inactivity of at least 45 seconds node.cpp:931
463174ms th_a terminate_inactive_c ] Disconnecting from handshaking peer 202.96.137.243:42975 due to inactivity of at least 45 seconds node.cpp:931
463174ms th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:46048 due to inactivity of at least 45 seconds node.cpp:931
(END)
And this is the gdb output
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab2c88 in EVP_EncryptUpdate ()
(gdb)
-
Resync your blockchain
Thanks, normally I remove the datadir, but this time I had a wallet in which I imported all my keys and stuff. Need to adapt my rebuild script to leave the config.json and the wallet dir.
after a while:
Current executable set to './bitshares_client' (x86_64).
(lldb) run
Process 59989 launched: './bitshares_client' (x86_64)
Logging to file "/Users/maurits/Library/Application Support/BitSharesXTS/default.log"
Logging RPC to file "/Users/maurits/Library/Application Support/BitSharesXTS/rpc.log"
Loading config "/Users/maurits/Library/Application Support/BitSharesXTS/config.json"
{
"rpc": {
"rpc_user": "user",
"rpc_password": "pass",
"rpc_endpoint": "127.0.0.1:5681",
"httpd_endpoint": "127.0.0.1:5680",
"htdocs": "/Users/maurits/bitsharesxts/web_wallet/generated"
},
"default_peers": [
"107.170.30.182:8764",
"114.215.104.153:8764",
"84.238.140.192:8764"
],
"ignore_console": false,
"logging": {
"includes": [],
"appenders": [],
"loggers": []
}
}
Loading blockchain from "/Users/maurits/Library/Application Support/BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
Listening for P2P connections on port 58343
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
Process 59989 stopped
* thread #1: tid = 0x26f60e, 0x000000010056a97d bitshares_client`EVP_EncryptUpdate + 29, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
frame #0: 0x000000010056a97d bitshares_client`EVP_EncryptUpdate + 29
bitshares_client`EVP_EncryptUpdate + 29:
-> 0x10056a97d: movq (%r12), %rbx
0x10056a981: testb $0x10, 0x12(%rbx)
0x10056a985: je 0x10056a9ad ; EVP_EncryptUpdate + 77
0x10056a987: movq %rdx, %r14
-
after starting gdb and then process with > run
When creating a new wallet etc.. after 1-2 min i get this message
Clean installed system so no old data dir... Ubuntu 14.04
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab142a in EVP_EncryptUpdate ()
Then i have to restart and then same error message again!
Don't know if it was discussed here before...just joined yet
-
problems on latest build
Loading blockchain from "/root/.BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7ffff58ae700 (LWP 27247)]
Listening for P2P connections on port 53893
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
[New Thread 0x7ffff4ead700 (LWP 27248)]
[New Thread 0x7fffeffff700 (LWP 27249)]
--- there are now 1 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
(wallet closed) >>> wallet_open default
OK
default (locked) >>> wallet_unlock 99999999
passphrase:
OK
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 5141,
"blockchain_head_block_time": "20140614T235030",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 279,
"blockchain_average_delegate_participation": 57.396449704142015,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 99999993,
"wallet_next_block_production_time": "20140614T235700",
"wallet_seconds_until_next_block_production": 297,
"wallet_local_time": "20140614T235203",
"blockchain_random_seed": "fb039b4dd5ec0bef959de04a02fd0192f3caad69",
"blockchain_shares": 10000061092614,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170815T093836",
"wallet_version": 100
}
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab14aa in EVP_EncryptUpdate ()
(gdb)
-
problems on latest build
Loading blockchain from "/root/.BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7ffff58ae700 (LWP 27247)]
Listening for P2P connections on port 53893
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
[New Thread 0x7ffff4ead700 (LWP 27248)]
[New Thread 0x7fffeffff700 (LWP 27249)]
--- there are now 1 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
(wallet closed) >>> wallet_open default
OK
default (locked) >>> wallet_unlock 99999999
passphrase:
OK
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 5141,
"blockchain_head_block_time": "20140614T235030",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 279,
"blockchain_average_delegate_participation": 57.396449704142015,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 99999993,
"wallet_next_block_production_time": "20140614T235700",
"wallet_seconds_until_next_block_production": 297,
"wallet_local_time": "20140614T235203",
"blockchain_random_seed": "fb039b4dd5ec0bef959de04a02fd0192f3caad69",
"blockchain_shares": 10000061092614,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170815T093836",
"wallet_version": 100
}
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab14aa in EVP_EncryptUpdate ()
(gdb)
That problem has been fixed and we now know the problem for the peer connection issues as well and should have that fixed tonight.
-
problems on latest build
Loading blockchain from "/root/.BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7ffff58ae700 (LWP 27247)]
Listening for P2P connections on port 53893
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
[New Thread 0x7ffff4ead700 (LWP 27248)]
[New Thread 0x7fffeffff700 (LWP 27249)]
--- there are now 1 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
(wallet closed) >>> wallet_open default
OK
default (locked) >>> wallet_unlock 99999999
passphrase:
OK
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 5141,
"blockchain_head_block_time": "20140614T235030",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 279,
"blockchain_average_delegate_participation": 57.396449704142015,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 99999993,
"wallet_next_block_production_time": "20140614T235700",
"wallet_seconds_until_next_block_production": 297,
"wallet_local_time": "20140614T235203",
"blockchain_random_seed": "fb039b4dd5ec0bef959de04a02fd0192f3caad69",
"blockchain_shares": 10000061092614,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170815T093836",
"wallet_version": 100
}
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab14aa in EVP_EncryptUpdate ()
(gdb)
That problem has been fixed and we now know the problem for the peer connection issues as well and should have that fixed tonight.
Excellent!
-
Please update your node, if you updated recently there is a bug that can cause problems for other nodes.
-
crazybit (unlocked) >>> get_info
get_info
{
"blockchain_head_block_num": 5569,
"blockchain_head_block_time": "20140615T024715",
"blockchain_head_block_time_rel": "10 minutes ago",
"blockchain_confirmation_requirement": 289,
"blockchain_average_delegate_participation": 58.823529411764703,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 998702,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140615T025744",
"blockchain_random_seed": "5595be7ce679bdb82557f88929972129d46ed9c1",
"blockchain_shares": 10000087488444,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140626T162246",
"wallet_version": 100
}
am i on the main chain now?
btw, i use command "wallet_account_rename" to change the account name with positive result , but when i wanna change it back, the following error encountered, is the result expected?
wallet_account_rename james crazybit
10 assert_exception: Assert Exception
!new_account.valid():
{}
th_a wallet.cpp:896 rename_account
{"old_account_name":"james","new_account_name":"crazybit"}
th_a wallet.cpp:901 rename_account
{}
th_a common_api_client.cpp:542 wallet_account_rename
{"command":"wallet_account_rename"}
th_a cli.cpp:547 execute_command
-
I'm on 5618 right now. The "blockchain_head_block_time_rel": "10 minutes ago" is suspicious... Are you on the latest?
btw, i use command "wallet_account_rename" to change the account name with positive result , but when i wanna change it back, the following error encountered, is the result expected?
Definitely no, filing an issue now
-
I rebuild from the latest code.
There only 1 connections on windows and 5 connections on ubuntu.
Are the windows version can't get node?
-
Wipe your old data-dir
Ubuntu: rm -r ~/.BitShares\ XTS
This command has never done anything for me. I feel I'm missing some implied instruction. Anyone care to clue me in.
I've just been either completely rebuilding the server from scratch or using the following
rm -r bitshares*
and then cloneing etc.
Does this have the same effect?
I notice i still have my wallet and imported keys, where as, when building from scratch I have to re create wallet and import keys again.
# about
tells me im on the latest revision but was i supposed to remove something that "# rm -r bits*" misses?
-
It is working well now ?
--- there are now 4 active connections to the p2p network
welk1n (unlocked) >>> info
{
"blockchain_head_block_num": 5654,
"blockchain_head_block_time": "20140615T032230",
"blockchain_head_block_time_rel": "32 seconds ago",
"blockchain_confirmation_requirement": 285,
"blockchain_average_delegate_participation": 61.237373737373737,
"network_num_connections": 4,
"wallet_unlocked_seconds_remaining": 9996219,
"wallet_next_block_production_time": "20140615T032915",
"wallet_seconds_until_next_block_production": 373,
"wallet_local_time": "20140615T032302",
"blockchain_random_seed": "ca281b06e58c7f9f52d211baf7911bf38691525d",
"blockchain_shares": 10000092853224,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141008T200641",
"wallet_version": 100
}
-
It is working well now ?
--- there are now 4 active connections to the p2p network
welk1n (unlocked) >>> info
{
"blockchain_head_block_num": 5654,
"blockchain_head_block_time": "20140615T032230",
"blockchain_head_block_time_rel": "32 seconds ago",
"blockchain_confirmation_requirement": 285,
"blockchain_average_delegate_participation": 61.237373737373737,
"network_num_connections": 4,
"wallet_unlocked_seconds_remaining": 9996219,
"wallet_next_block_production_time": "20140615T032915",
"wallet_seconds_until_next_block_production": 373,
"wallet_local_time": "20140615T032302",
"blockchain_random_seed": "ca281b06e58c7f9f52d211baf7911bf38691525d",
"blockchain_shares": 10000092853224,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141008T200641",
"wallet_version": 100
}
Lookin' good!
-
It is working well now ?
--- there are now 4 active connections to the p2p network
welk1n (unlocked) >>> info
{
"blockchain_head_block_num": 5654,
"blockchain_head_block_time": "20140615T032230",
"blockchain_head_block_time_rel": "32 seconds ago",
"blockchain_confirmation_requirement": 285,
"blockchain_average_delegate_participation": 61.237373737373737,
"network_num_connections": 4,
"wallet_unlocked_seconds_remaining": 9996219,
"wallet_next_block_production_time": "20140615T032915",
"wallet_seconds_until_next_block_production": 373,
"wallet_local_time": "20140615T032302",
"blockchain_random_seed": "ca281b06e58c7f9f52d211baf7911bf38691525d",
"blockchain_shares": 10000092853224,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141008T200641",
"wallet_version": 100
}
Lookin' good!
:),Thanks!
The four delegates of mine (30,31,32,33)
I use the blockchain_list_delegates commands .
It seems that they produced blocks well.
Please vote them , thank you !
-
problems on latest build
Loading blockchain from "/root/.BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7ffff58ae700 (LWP 27247)]
Listening for P2P connections on port 53893
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
[New Thread 0x7ffff4ead700 (LWP 27248)]
[New Thread 0x7fffeffff700 (LWP 27249)]
--- there are now 1 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
(wallet closed) >>> wallet_open default
OK
default (locked) >>> wallet_unlock 99999999
passphrase:
OK
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 5141,
"blockchain_head_block_time": "20140614T235030",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 279,
"blockchain_average_delegate_participation": 57.396449704142015,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 99999993,
"wallet_next_block_production_time": "20140614T235700",
"wallet_seconds_until_next_block_production": 297,
"wallet_local_time": "20140614T235203",
"blockchain_random_seed": "fb039b4dd5ec0bef959de04a02fd0192f3caad69",
"blockchain_shares": 10000061092614,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170815T093836",
"wallet_version": 100
}
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab14aa in EVP_EncryptUpdate ()
(gdb)
That problem has been fixed and we now know the problem for the peer connection issues as well and should have that fixed tonight.
HI BM. you did a good job!
I have some suggestions, i think there are not enough programme developers for 3I. because 3I has got a lot of money due to AGS, so i suggest that all the staff's (not programmers' ) first priority should be to find more talents to join the team to promote the progress of programming.
we do not lack of money, we have so many things to do, and i thinkg the other employees(not programmers) should really try their every effort to find more talented programmers to join 3I. and that's even equally imporant than the development of BTS X.
I do not know if i am right because i know little about softwares, IT or programming. this is just some advices. But I am once in charge of a team of about 100 people, and this is just some of my experience. we should really really pay attention to recruiting more talents to your team and give more time on this job.
At last, hope you guys be successful one day and become heros.
-
btw, i use command "wallet_account_rename" to change the account name with positive result , but when i wanna change it back, the following error encountered, is the result expected?
I'm on 5618 right now. The "blockchain_head_block_time_rel": "10 minutes ago" is suspicious... Are you on the latest?
i think i am on the lastest
crazybit (unlocked) >>> about
{
"bitshares_toolkit_revision": "e9582b7fbca06c7dc53f19bc75c0402c7870afa1",
"bitshares_toolkit_revision_age": "3 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "53 hours ago",
"compile_date": "compiled on Jun 14 2014 at 19:04:15"
}
crazybit (unlocked) >>> get_info
{
"blockchain_head_block_num": 5730,
"blockchain_head_block_time": "20140615T035415",
"blockchain_head_block_time_rel": "27 seconds ago",
"blockchain_confirmation_requirement": 287,
"blockchain_average_delegate_participation": 61.587301587301589,
"network_num_connections": 7,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140615T035442",
"blockchain_random_seed": "88b0c83dc6fcfa7e2ced9cbfd8be42e8fe6c44dd",
"blockchain_shares": 10000076678208,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19700101T000000",
"wallet_version": 100
}
btw,i upgrade myself to be a delegate, please vote "crazybit" , thanks
-
I got a backup chain file from ubuntu and run on windows because windows version always stuck on block 173.
And the backup chain is on block 5563.
It works well on windows at the begin.
After get the block 5666, the client is crash every time on windows, but it work well on ubuntu.
The last log on windows:
3473443ms th_a on_new_block ] Received a new block from the p2p network, current head block is 5666, new block is {"previous":"f0b54dea22b16d33ab319ff31b21514a9dc0893a","block_num":5667,"fee_rate":1000,"delegate_pay_rate":63853,"timestamp":"20140615T032800","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"81e526a9e2871b33164d3f09ad3311deb6191fd4","previous_secret":"bb8dc9dce058218a2f39b3a358ea2b78179bf906","delegate_signature":"1fdfc08bf36daad0a7ec31ccaedd25ad2e89fd082a6814f36b7aac25f70059355aabc9da9fb2570c7fa5bfed9eb6e6cbb00d9f8a29631de7c3dbe297e58a141e6a","user_transactions":[{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS4UTfbDwf5TvoYpMbqcviYpPFSpEFbwuwt","amount":10495702,"claim_input_data":""}},{"type":"update_account_op_type","data":{"account_id":315,"public_data":null,"active_key":null,"is_delegate":true}}],"signatures":["1f80dd5137f742b842da2dbf6bcfb4c23d94e62bafac751b4ea22da8cb918ce318ff739104db8c51f7a9da8320b17441dbfb7be57f717199fa26d50780e9bf805d","1f5742fb4e069b8b18496b7879fd00608d598f66aa13635060f0f215b884f5788a042107c1ccd28d5b059e0e090470130531b13396bb1b51a18ec6fa7caabf363d"]}]}, current head block is 5666 client.cpp:518
3473444ms th_a get_property ] property last_random_seed_id chain_database.cpp:1711
3473445ms th_a store_and_index ] we already know about its previous: f0b54dea22b16d33ab319ff31b21514a9dc0893a chain_database.cpp:350
3473446ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
3473446ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
3473450ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
3473451ms th_a get_property ] property confirmation_requirement chain_database.cpp:1711
3473451ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
3473452ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
3473453ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
3473453ms th_a get_property ] property active_delegate_list_id chain_database.cpp:1711
-
Our team of developers:
Eric Frias - responsible for most of the P2P network code, RPC code gen, and other items.
Toast - helping everywhere , currently web wallet / C++ integration
Nikita - helping with web wallet
HackFisher - helping everywhere, currently web wallet (Just in from China last week)
Dan N - working toward robust test suites
Nathan - Starting Monday (C++)
Vikram - Starting Monday (C++ / everywhere)
Myself - everywhere
Valentine - C++ / Web (part time, hopefully full time)
3 polish devs - Keyhotee / BitShares integration / Nightly Support
1 Indian - tester
James - part time (currently busy, but will return in 2 weeks) JS support for signing transactions
Most of this team only started working effectively this month.. so I think we have enough people to do the job now.
-
I got a backup chain file from ubuntu and run on windows because windows version always stuck on block 173.
We are well aware of the Windows client getting stuck on 173. It is the result of a stack corruption exception that has us truly baffled. Tomorrow that is Eric's top priority to track down as the bug likely effects other platforms but expresses itself differently.
-
Most of this team only started working effectively this month.. so I think we have enough people to do the job now.
you guys make a great progress this month. well done!
-
btw,i upgrade myself to be a delegate, please vote "crazybit" , thanks
to vote me, you just need to issue the follow command before you perform transfer. thanks :D
wallet_set_delegate_trust_level crazybit 1
-
Sorry but I could not resist posting a joke… fully understanding that I will be the only one to lough at it.
----
TK: “Dan, we all know that connecting with people and knowing the people you work with is very important to you. Can you describe your team?”
BM:“Yes, I really know all of them well, even though most of them started working effectively only this month. They are all pretty good, you know…[just needed a little bit of time worming up (from Feb till now)]. We are – Eric, Toast , Nikita, HackFisher, Dan N….
3 polish devs and 1 Indian tester”
----
PS
To vote me out, you just need to issue the follow command before you perform postinthisforum
tonyk_go_fuck_youself = [true]
‘
-
Ok. With latest build my connection count is up to 8. Still delegate is not producing any blocks..
>>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 2109074296,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 63,
"pay_balance": 0,
get_info
{
"blockchain_head_block_num": 5928,
"blockchain_head_block_time": "20140615T051545",
"blockchain_head_block_time_rel": "55 seconds ago",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 61.12161310649023,
"network_num_connections": 8,
>>> blockchain_list_delegates
..
** Inactive:
.. 299 bitcoiners 2109074296 0 0.0210906 % 0 63
-
(from Feb till now)
Me & hackfisher & nikita started full-time in May. Vikram and Nathan still haven't officially started. Eric started in March. So I believe your "since february" applies to the two Dans and the polish team who have been on keyhotee this whole time. The rest are still part-time.
https://github.com/BitShares/bitshares_toolkit/graphs/contributors
Did I misunderstand your joke?
-
Ok. With latest build my connection count is up to 8. Still delegate is not producing any blocks..
>>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 2109074296,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 63,
"pay_balance": 0,
get_info
{
"blockchain_head_block_num": 5928,
"blockchain_head_block_time": "20140615T051545",
"blockchain_head_block_time_rel": "55 seconds ago",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 61.12161310649023,
"network_num_connections": 8,
>>> blockchain_list_delegates
..
** Inactive:
.. 299 bitcoiners 2109074296 0 0.0210906 % 0 63
It looks like you got voted out, probably when BM moved his votes to get someone else in since he is the only one voting ATM
-
It looks like you got voted out, probably when BM moved his votes to get someone else in since he is the only one voting ATM
>:(
Please vote me back in!
-
Wipe your old data-dir
Ubuntu: rm -r ~/.BitShares\ XTS
This command has never done anything for me. I feel I'm missing some implied instruction. Anyone care to clue me in.
I've just been either completely rebuilding the server from scratch or using the following
rm -r bitshares*
and then cloneing etc.
Does this have the same effect?
I notice i still have my wallet and imported keys, where as, when building from scratch I have to re create wallet and import keys again.
# about
tells me im on the latest revision but was i supposed to remove something that "# rm -r bits*" misses?
~/.BitShares\ XTS may be referring to an old data directory (I have noticed that the different versions I have downloaded and compiled have had slightly different data directories. The current data dir is ~/.BitSharesXTS so the command would be
rm -r ~/.BitSharesXTS
This will wipe your wallet though. You will need to either re-import keys or copy your wallet over to the new directory. How I've done it is
cp -r ~/.BitSharesXTS/wallets ~
rm -r ~/.BitSharesXTS
mkdir ~/.BitSharesXTS
cp -r ~/wallets ~/.BitSharesXTS
there may be a better way of doing this.
I also currently just wipe out the bitshares_toolkit directory and git clone another one. that is what your rm -r ~/bitshares* command was doing. I am sure there is a better way than that to resync to git, but I don't know it.
-
Just an update:
emski (unlocked) >>> get_info
{
"blockchain_head_block_num": 6002,
"blockchain_head_block_time": "20140615T054600",
"blockchain_confirmation_requirement": 286,
"blockchain_average_delegate_participation": 60.89139987445072,
"network_num_connections": 26,
"wallet_unlocked_seconds_remaining": 99913328,
"wallet_next_block_production_time": "20140615T054700",
"wallet_seconds_until_next_block_production": 61,
"wallet_local_time": "20140615T054559",
"blockchain_random_seed": "c1286419a26cc7b0402fb40d3537f30a53c0837d",
"blockchain_shares": 10000094357869,
"network_num_connections_max": 50,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170814T152807",
"wallet_version": 100
}
--- there are now 27 active connections to the p2p network
--- in sync with p2p network
I've increased network_num_connections_max and desired_number_of_connections just to see what happens.
-
download the latest code from github and fresh run but still only getting one connection
myhometalk (locked) >>> info
{
"blockchain_head_block_num": 5995,
"blockchain_head_block_time": "20140615T054400",
"blockchain_head_block_time_rel": "8 seconds ago",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 60.7008760951189,
"network_num_connections": 1,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140615T054408",
"blockchain_random_seed": "d79467e267d6234b43a043c9037a2998fe58e95b",
"blockchain_shares": 10000093896268,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "",
"wallet_version": 100
}
-
Did I misunderstand your joke?
Yes you did..
Sam, Tom, Me and... 1 Indian tester....
...If you still do not get it - it is more of beginning of a racy joke then presentation of your core team (But as I said it is probably funny/sad to me only)
-
On my end whatever you did has solved connection issues on all three nodes I'm running.
-
Solved connection issue on ubuntu, I have now 6 active connections and my delegates ( init-delegate-21, init-delegate-22, init-delegate-23, init-delegate-24) are working.
-
Looks Good!
welk1n (unlocked) >>> info
{
"blockchain_head_block_num": 6097,
"blockchain_head_block_time": "20140615T095400",
"blockchain_head_block_time_rel": "61 seconds ago",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 39.786710418375719,
"network_num_connections": 8,
"wallet_unlocked_seconds_remaining": 9972700,
"wallet_next_block_production_time": "20140615T095945",
"wallet_seconds_until_next_block_production": 284,
"wallet_local_time": "20140615T095501",
"blockchain_random_seed": "5ed94b17a1f657851194360dd760251c35c065af",
"blockchain_shares": 10000100611524,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141008T200641",
"wallet_version": 100
}
-
I'm running test node with large allowed number of connections
can someone try to add me as peer?
79.173.81.171:8764
-
Loading blockchain from "/root/.BitSharesXTS/chain"
Starting JSON RPC server on port 57466 (localhost only)
Starting HTTP JSON RPC server on port 9989 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
{"method":"read","len":23,"over":1}
th_a datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
{"type":"uint8_t"}
th_a raw.hpp:440 unpack
optional<fc::exception>
{"type":"fc::exception"}
th_a raw.hpp:164 unpack
Error unpacking field last_error
{"field":"last_error"}
th_a raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
{"type":"bts::net::potential_peer_record"}
th_a raw.hpp:440 unpack
what is wrong
-
Loading blockchain from "/root/.BitSharesXTS/chain"
Starting JSON RPC server on port 57466 (localhost only)
Starting HTTP JSON RPC server on port 9989 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
{"method":"read","len":23,"over":1}
th_a datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
{"type":"uint8_t"}
th_a raw.hpp:440 unpack
optional<fc::exception>
{"type":"fc::exception"}
th_a raw.hpp:164 unpack
Error unpacking field last_error
{"field":"last_error"}
th_a raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
{"type":"bts::net::potential_peer_record"}
th_a raw.hpp:440 unpack
what is wrong
unpack data failed, looks like your blockchain data structure does not syn with the code.
-
Loading blockchain from "/root/.BitSharesXTS/chain"
Starting JSON RPC server on port 57466 (localhost only)
Starting HTTP JSON RPC server on port 9989 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
{"method":"read","len":23,"over":1}
th_a datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
{"type":"uint8_t"}
th_a raw.hpp:440 unpack
optional<fc::exception>
{"type":"fc::exception"}
th_a raw.hpp:164 unpack
Error unpacking field last_error
{"field":"last_error"}
th_a raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
{"type":"bts::net::potential_peer_record"}
th_a raw.hpp:440 unpack
what is wrong
I solved this by deleting ~/.BitsharesXT dir. But remember to backup your wallet. Or maybe you can try run ./bitshare_client --clear-peer-database --resync-blockchain
-
The Indian bitsharesX (wallet) tester
for anybody wanted to see them in action...
(https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSBDj-6ojyfZIuc2ddimcurJd_BtnuoSCOgZCjE4RaCFS_2qO9W)
-
I would like to get voted in, I would appreciate it if someone votes for me:
wallet_set_delegate_trust_level mauritso 1
If I am a delegate at the start of the XTS network I will launch a Amazon EC2 instance (m1.small/m3.medium/m3.large depending on the requirements in a location of your choosing) and keep it running for at least a month. After my amazon credit is gone, I am still a delegate and it got enough money in transaction fees I will probably switch to a dedicated host.
-
The Indian bitsharesX (wallet) tester
for anybody wanted to see them in action...
(https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSBDj-6ojyfZIuc2ddimcurJd_BtnuoSCOgZCjE4RaCFS_2qO9W)
IMO you should deal with a bit more respect to devs! Just said...
-
IMO you should deal with a bit more respect to devs! Just said...
I was certain everybody has a sense of humour, especialy on forums like this where people in most cases have high IQs (me excluded) :)
PS I am tired to say sorry guys but if I have insulted some of you... sorry!
-
@Devs: Now that I can import my keyhotee ID (lower-letter case issue resolved)
I wonder if I made sth wrong as I cannot see and funds tied to that account ('xeroc') .. I thought we get a stake on XTS as beeing a keyhotee founder?!
-
When I launched the command "wallet_list_unspent_balances" I obtained a segfault:
default (unlocked) >>> wallet_list_unspent_balances
BALANCE OWNER VOTE
--------------------------------------------------------------------------------------------------------------------------
10000000 XTSBq9D8nqMyn192B6Dt8HF62k9U7nwqJcv6 +mauritso
8989970000 XTSMFChKHFVFjZfSNZt8nAibo1bDvBouEwJM +bts101
990000 XTSLuMuRnXiAYh4jiT64isaK6VWaM6KRLYKu +bts101
265343474 XTSFCEgUceUsCjgHybTsYgJ7JJkUDc8cTYUm +cgafeng
1970000 XTS63HYCB2AUNKKn5e6pPCGATeJy6LxQSBxR +bts101
Program received signal SIGSEGV, Segmentation fault.
0x00000000006659f9 in bts::cli::detail::cli_impl::format_and_print_result(std::string const&, std::vector<fc::variant, std::allocator<fc::variant> >, fc::variant const&) ()
at /home/fabiux/ssd/bitshares_toolkit/libraries/cli/cli.cpp:791
791 if (delegate_rec->name.size() > 21)
(gdb)
-
I'm running test node with large allowed number of connections
can someone try to add me as peer?
79.173.81.171:8764
Added successfully.
-
I solved this by deleting ~/.BitsharesXT dir. But remember to backup your wallet. Or maybe you can try run ./bitshare_client --clear-peer-database --resync-blockchain
which one is my wallet file, is it included in folder ./bitshare XTS/ wallet?
-
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1. I manually added nodes until I was up to about 9, and left it for the night. This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain. My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.
-
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1. I manually added nodes until I was up to about 9, and left it for the night. This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain. My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.
I am running with old version (built more than 30 hours ago) and now has 12 connections.
Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>
-
I solved this by deleting ~/.BitsharesXT dir. But remember to backup your wallet. Or maybe you can try run ./bitshare_client --clear-peer-database --resync-blockchain
which one is my wallet file, is it included in folder ./bitshare XTS/ wallet?
XTS wallet use level db, it does not like bitcoin wallet which has only one wallet.dat file, you need to back the whole "wallets" folder.
-
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1. I manually added nodes until I was up to about 9, and left it for the night. This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain. My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.
I am running with old version (built more than 30 hours ago) and now has 12 connections.
Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>
Maybe you can use the wallet_get_account commands
welk1n (unlocked) >>> wallet_get_account init-delegate-33
{
"index": 10,
"id": 33,
"name": "init-delegate-33",
"public_data": null,
"owner_key": "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA",
"active_key_history": [[
"20140615T021914",
"XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA"
]
],
"delegate_info": {
"votes_for": 99732150532,
"votes_against": 0,
"blocks_produced": 137,
"blocks_missed": 18,
"pay_balance": 5988191,
"next_secret_hash": "419c0a4c97a2ea0847778747fdb7c5470ac6a1e6",
"last_block_num_produced": 6140
},
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"meta_data": null,
"account_address": "XTSG6FH3Q32yVgoafyJLnPS5JTo9juK5rWY4",
"trust_level": 0,
"private_data": null
}
-
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1. I manually added nodes until I was up to about 9, and left it for the night. This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain. My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.
I am running with old version (built more than 30 hours ago) and now has 12 connections.
Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>
+5%
-
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1. I manually added nodes until I was up to about 9, and left it for the night. This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain. My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.
I am running with old version (built more than 30 hours ago) and now has 12 connections.
Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>
Maybe you can use the wallet_get_account commands
welk1n (unlocked) >>> wallet_get_account init-delegate-33
{
"index": 10,
"id": 33,
"name": "init-delegate-33",
"public_data": null,
"owner_key": "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA",
"active_key_history": [[
"20140615T021914",
"XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA"
]
],
"delegate_info": {
"votes_for": 99732150532,
"votes_against": 0,
"blocks_produced": 137,
"blocks_missed": 18,
"pay_balance": 5988191,
"next_secret_hash": "419c0a4c97a2ea0847778747fdb7c5470ac6a1e6",
"last_block_num_produced": 6140
},
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"meta_data": null,
"account_address": "XTSG6FH3Q32yVgoafyJLnPS5JTo9juK5rWY4",
"trust_level": 0,
"private_data": null
}
I meant the the head numbers of all the blocks produced by the given delegate.
Like : init-delegate-33 has produced following blocks: 1, 1000, 2332,3344 ............ 6140
-
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1. I manually added nodes until I was up to about 9, and left it for the night. This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain. My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.
I am running with old version (built more than 30 hours ago) and now has 12 connections.
Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>
Maybe you can use the wallet_get_account commands
welk1n (unlocked) >>> wallet_get_account init-delegate-33
{
"index": 10,
"id": 33,
"name": "init-delegate-33",
"public_data": null,
"owner_key": "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA",
"active_key_history": [[
"20140615T021914",
"XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA"
]
],
"delegate_info": {
"votes_for": 99732150532,
"votes_against": 0,
"blocks_produced": 137,
"blocks_missed": 18,
"pay_balance": 5988191,
"next_secret_hash": "419c0a4c97a2ea0847778747fdb7c5470ac6a1e6",
"last_block_num_produced": 6140
},
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"meta_data": null,
"account_address": "XTSG6FH3Q32yVgoafyJLnPS5JTo9juK5rWY4",
"trust_level": 0,
"private_data": null
}
I meant the the head numbers of all the blocks produced by the given delegate.
Like : init-delegate-33 has produced following blocks: 1, 1000, 2332,3344 ............ 6140
Sorry,
Good idea. +5%
-
Are there some estimated number of nodes for current testnet?
-
this the imformation I posted last time
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
init-delegate-118 XTS7X933vLMhkPiv3tFACokWfVhkBJwkTbrgiworsvNnWaiKdXYxZ 2014-06-14T05:22:30 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
I hire a VPS and it can runing 7*24, voting me
this the accounts I open wallet after rebuild clients
NAME (* delegate) KEY REGISTERED TRUST LEVEL
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
who help me change the name of
init-delegate-118 XTS7X933vLMhkPiv3tFACokWfVhkBJwkTbrgiworsvNnWaiKdXYxZ
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 I have three account , you can see the name and key of second account both was changed
-
NAME (* delegate) KEY REGISTERED TRUST LEVEL
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
who help me change the name of "testz-test *" I have three account ,but the name was changed not by me
That sounds like a wallet sync bug
Are there some estimated number of nodes for current testnet?
30-50
-
NAME (* delegate) KEY REGISTERED TRUST LEVEL
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
who help me change the name of "testz-test *" I have three account ,but the name was changed not by me
When was your last update? I thought we fixed this one
-
NAME (* delegate) KEY REGISTERED TRUST LEVEL
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
who help me change the name of "testz-test *" I have three account ,but the name was changed not by me
When was your last update? I thought we fixed this one
I just updated the code ,rebuilt code , deleted all files / subfolder in the folder of ".BitSharesXTS" except "wallets" folder, and run the clients , open my wallet,
and I find the name and key of my secends account was changed
-
My delegate (bitcoiners) is still not producing any blocks. BM, please re-enable it.
blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 2109074296,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 63,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 7436,
"blockchain_head_block_time": "20140615T151845",
-
NAME (* delegate) KEY REGISTERED TRUST LEVEL
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
who help me change the name of "testz-test *" I have three account ,but the name was changed not by me
When was your last update? I thought we fixed this one
I just updated the code ,rebuilt code , deleted all files / subfolder in the folder of ".BitSharesXTS" except "wallets" folder, and run the clients , open my wallet,
and I find the name and key of my secends account was changed
Maybe it's still cached in your wallet, try dumping your private keys, making a new wallet, importing and rescanning
-
Are there some estimated number of nodes for current testnet?
30-50
Heh, I have 32-34 connections =D
-
All problems sorted importing PTS and BTS private keys. Wallets syncing and transferring between imported BitShare keys between VPS (Europe) and VMs
I need more votes to be a delegate, please :) "betax" nearly there.
-
My delegate (bitcoiners) is still not producing any blocks. BM, please re-enable it.
blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 2109074296,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 63,
"pay_balance": 0,
"next_secret_hash": "0000000000000000000000000000000000000000",
"last_block_num_produced": 4294967295
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 7436,
"blockchain_head_block_time": "20140615T151845",
Your delegate has been voted back in along with some others. I am all out of funds for voting.
-
i tried to create asset with transaction broadcasted, and the fee was also deducted from my account, but when i issue"wallet_account_transaction_history" command, no transaction record was found,and the command "blockchain_get_asset_record " was issued to check on blockchain without record found either, is it an issue?
-
"You offered us a block that we reject as invalid"
Is this message ok?
--- there are now 26 active connections to the p2p network
--- in sync with p2p network
Peer 128.199.180.19:51811 disconnected us: You offered us a block that we reject as invalid
--- there are now 25 active connections to the p2p network
delegate (unlocked) >>> about
{
"bitshares_toolkit_revision": "458342c24ad06f44dc46d0de0f64566f1bc8da5e",
"bitshares_toolkit_revision_age": "13 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "65 hours ago",
"compile_date": "compiled on Jun 15 2014 at 06:47:07"
}
-
"You offered us a block that we reject as invalid"
Is this message ok?
--- there are now 26 active connections to the p2p network
--- in sync with p2p network
Peer 128.199.180.19:51811 disconnected us: You offered us a block that we reject as invalid
--- there are now 25 active connections to the p2p network
delegate (unlocked) >>> about
{
"bitshares_toolkit_revision": "458342c24ad06f44dc46d0de0f64566f1bc8da5e",
"bitshares_toolkit_revision_age": "13 hours ago",
"fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
"fc_revision_age": "65 hours ago",
"compile_date": "compiled on Jun 15 2014 at 06:47:07"
}
I got the same error of my delegate node. I also got a disconnect with the message "You sent me a syunc block that I didn't ask for"
The node still appears to be synced with the main chain, and producing blocks though.
-
Your delegate has been voted back in along with some others. I am all out of funds for voting.
Thanks. It looks like this delegate has more votes now, but still has not produced any blocks..
>>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83109074296,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 63,
My desktop client and VPS server nodes are showing different block counts. Seems delegate node is falling behind.
delegate node
>>> get_info
{
"blockchain_head_block_num": 7489,
"blockchain_head_block_time": "20140615T153815",
"blockchain_head_block_time_rel": "53 minutes ago",
"blockchain_confirmation_requirement": 278,
"blockchain_average_delegate_participation": 56.362579895409645,
"network_num_connections": 12,
desktop
get_info
{
"blockchain_head_block_num": 7635,
"blockchain_head_block_time": "20140615T163430",
"blockchain_head_block_time_rel": "12 seconds ago",
"blockchain_confirmation_requirement": 282,
"blockchain_average_delegate_participation": 64.666666666666671,
"network_num_connections": 8,
-
Ha .. my first pull request to the bitshares_toolkit repo :-)
https://github.com/BitShares/bitshares_toolkit/pull/284
BTW: I am no coder :) took me like 20 minutes to figure this out :)
EDIT: you can now vote for my keyhotee-ID as delegate
wallet_set_delegate_trust_level xeroc 10
Thanks for voting me up .. now producing blocks ..
BTW:
--- there are now 25 active connections to the p2p network
-
try command below and find out both clients are on the same chain
blockchain_get_block_by_number 7489
Your delegate has been voted back in along with some others. I am all out of funds for voting.
Thanks. It looks like this delegate has more votes now, but still has not produced any blocks..
>>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83109074296,
"votes_against": 0,
"blocks_produced": 0,
"blocks_missed": 63,
My desktop client and VPS server nodes are showing different block counts. Seems delegate node is falling behind.
delegate node
>>> get_info
{
"blockchain_head_block_num": 7489,
"blockchain_head_block_time": "20140615T153815",
"blockchain_head_block_time_rel": "53 minutes ago",
"blockchain_confirmation_requirement": 278,
"blockchain_average_delegate_participation": 56.362579895409645,
"network_num_connections": 12,
desktop
get_info
{
"blockchain_head_block_num": 7635,
"blockchain_head_block_time": "20140615T163430",
"blockchain_head_block_time_rel": "12 seconds ago",
"blockchain_confirmation_requirement": 282,
"blockchain_average_delegate_participation": 64.666666666666671,
"network_num_connections": 8,
-
What's the output of command 'wallet_account_balance' in your clients ?
I have four accounts but get nothing by this command .
walletdelegate (unlocked) >>> wallet_account_balance
walletdelegate (unlocked) >>>
help info:
Usage:
wallet_account_balance [account_name] Lists the total balances of all accounts sorted by account and asset
Lists the total balances of all accounts sorted by account and asset
Parameters:
account_name (account_name, optional, defaults to "*"): the account to get a balance for, '*' or ''. If '*' or '' then all accounts will be returned
Returns:
map< account_name, map< asset_symbol, share_type> >
aliases: balance
So I guess the right output should be the balance of each account instead of nothing, right ?
walletdelegate (unlocked) >>> wallet_account_balance *
walletdelegate (unlocked) >>>
walletdelegate (unlocked) >>> wallet_account_balance heyd
heyd:
0.000000 XTS
-
yea my delegate is up for now! plz vote for me
wallet_set_delegate_trust_level denkhaus 10
as an cloud it pro i will keep my european node up, scalable and reliable!
btw: whoever wants to checkout bitshares in a docker container: take mine @
https://github.com/denkhaus/dockerfiles/tree/master/bitshares (https://github.com/denkhaus/dockerfiles/tree/master/bitshares)
-
try command below and find out both clients are on the same chain
blockchain_get_block_by_number 7489
desktop
blockchain_get_block_by_number 7489
{
"previous": "a1d2a69bfc8e2ad421972be43230f64551ce0c76",
"block_num": 7489,
"fee_rate": 1000,
"delegate_pay_rate": 74119,
"timestamp": "20140615T153815",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "a8b7d4cb492d5a53d43e055d77ba0be9445e9e1d",
"previous_secret": "fc8f207fd0d1c53da6fd2bb3c674c9e1a0c2d407",
"delegate_signature": "200bd9114e5e932760e0f64dcdd74df79c9b7dbd98ed4f0f0ea4957ca0df00c7fab5cd8186c2434111a9dfb2c470b1428c1432483fcf687a672e27a4936916f277",
"user_transaction_ids": []
}
get_info
{
"blockchain_head_block_num": 8037,
"blockchain_head_block_time": "20140615T185145",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 174,
"blockchain_average_delegate_participation": 67.454798331015297,
"network_num_connections": 8,
server
blockchain_get_block_by_number 7489
{
"previous": "a1d2a69bfc8e2ad421972be43230f64551ce0c76",
"block_num": 7489,
"fee_rate": 1000,
"delegate_pay_rate": 74119,
"timestamp": "20140615T153815",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "a8b7d4cb492d5a53d43e055d77ba0be9445e9e1d",
"previous_secret": "fc8f207fd0d1c53da6fd2bb3c674c9e1a0c2d407",
"delegate_signature": "200bd9114e5e932760e0f64dcdd74df79c9b7dbd98ed4f0f0ea4957ca0df00c7fab5cd8186c2434111a9dfb2c470b1428c1432483fcf687a672e27a4936916f277",
"user_transaction_ids": []
}
get_info
{
"blockchain_head_block_num": 7489,
"blockchain_head_block_time": "20140615T153815",
"blockchain_head_block_time_rel": "3 hours ago",
"blockchain_confirmation_requirement": 278,
"blockchain_average_delegate_participation": 42.863455589924875,
"network_num_connections": 11,
looks like my delegate node is stuck on block 7489
-
try command below and find out both clients are on the same chain
blockchain_get_block_by_number 7489
desktop
blockchain_get_block_by_number 7489
{
"previous": "a1d2a69bfc8e2ad421972be43230f64551ce0c76",
"block_num": 7489,
"fee_rate": 1000,
"delegate_pay_rate": 74119,
"timestamp": "20140615T153815",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "a8b7d4cb492d5a53d43e055d77ba0be9445e9e1d",
"previous_secret": "fc8f207fd0d1c53da6fd2bb3c674c9e1a0c2d407",
"delegate_signature": "200bd9114e5e932760e0f64dcdd74df79c9b7dbd98ed4f0f0ea4957ca0df00c7fab5cd8186c2434111a9dfb2c470b1428c1432483fcf687a672e27a4936916f277",
"user_transaction_ids": []
}
get_info
{
"blockchain_head_block_num": 8037,
"blockchain_head_block_time": "20140615T185145",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 174,
"blockchain_average_delegate_participation": 67.454798331015297,
"network_num_connections": 8,
server
blockchain_get_block_by_number 7489
{
"previous": "a1d2a69bfc8e2ad421972be43230f64551ce0c76",
"block_num": 7489,
"fee_rate": 1000,
"delegate_pay_rate": 74119,
"timestamp": "20140615T153815",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "a8b7d4cb492d5a53d43e055d77ba0be9445e9e1d",
"previous_secret": "fc8f207fd0d1c53da6fd2bb3c674c9e1a0c2d407",
"delegate_signature": "200bd9114e5e932760e0f64dcdd74df79c9b7dbd98ed4f0f0ea4957ca0df00c7fab5cd8186c2434111a9dfb2c470b1428c1432483fcf687a672e27a4936916f277",
"user_transaction_ids": []
}
get_info
{
"blockchain_head_block_num": 7489,
"blockchain_head_block_time": "20140615T153815",
"blockchain_head_block_time_rel": "3 hours ago",
"blockchain_confirmation_requirement": 278,
"blockchain_average_delegate_participation": 42.863455589924875,
"network_num_connections": 11,
looks like my delegate node is stuck on block 7489
Can you give me the result of 'list_errors' ?
-
Do you have your delegate key imported on two separate nodes?
That would partially explain why you keep getting onto a fork
-
Can you give me the result of 'list_errors' ?
Here is my latest.
>>> list_errors
[[
"20140615T202617.117015",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "chain_database.cpp",
"line": 502,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.116696"
},
"format": "block_data.timestamp <= (now + BTS_BLOCKCHAIN_BLOCK_INTERVAL_SEC/2): ${t} < ${now}",
"data": {
"t": "20140615T202700",
"now": "20140615T202617"
}
},{
"context": {
"level": "warn",
"file": "chain_database.cpp",
"line": 519,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.116735"
},
"format": "",
"data": {}
},{
"context": {
"level": "warn",
"file": "chain_database.cpp",
"line": 703,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.116872"
},
"format": "",
"data": {
"block": {
"previous": "a0746545259e47614589373baad67bd203c74eaa",
"block_num": 8311,
"fee_rate": 1000,
"delegate_pay_rate": 77795,
"timestamp": "20140615T202700",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "1e304010c539bd92b57be0579619d4bcf6430043",
"previous_secret": "7de7cf32ce93fed59c0a8655d70eb0420a6dd0ba",
"delegate_signature": "201c21399a7148a16ce8581bdf16e8b7a222ce202776f5937f36065e3beace8a09027493ede5dfb9fdec83aeb852df4ab9cb3da372ea64760d84c24526393e050b",
"user_transactions": []
}
}
},{
"context": {
"level": "warn",
"file": "chain_database.cpp",
"line": 1078,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.116928"
},
"format": "",
"data": {
"block_data": {
"previous": "a0746545259e47614589373baad67bd203c74eaa",
"block_num": 8311,
"fee_rate": 1000,
"delegate_pay_rate": 77795,
"timestamp": "20140615T202700",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "1e304010c539bd92b57be0579619d4bcf6430043",
"previous_secret": "7de7cf32ce93fed59c0a8655d70eb0420a6dd0ba",
"delegate_signature": "201c21399a7148a16ce8581bdf16e8b7a222ce202776f5937f36065e3beace8a09027493ede5dfb9fdec83aeb852df4ab9cb3da372ea64760d84c24526393e050b",
"user_transactions": []
}
}
},{
"context": {
"level": "warn",
"file": "client.cpp",
"line": 520,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.116999"
},
"format": "Error pushing block ${block_number} - ${block_id}",
"data": {
"block_id": "e9e03bdb20102b3a54705f6d00d61e188bac0577",
"block_number": 8311,
"block": {
"previous": "a0746545259e47614589373baad67bd203c74eaa",
"block_num": 8311,
"fee_rate": 1000,
"delegate_pay_rate": 77795,
"timestamp": "20140615T202700",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "1e304010c539bd92b57be0579619d4bcf6430043",
"previous_secret": "7de7cf32ce93fed59c0a8655d70eb0420a6dd0ba",
"delegate_signature": "201c21399a7148a16ce8581bdf16e8b7a222ce202776f5937f36065e3beace8a09027493ede5dfb9fdec83aeb852df4ab9cb3da372ea64760d84c24526393e050b",
"user_transactions": []
}
}
}
]
}
],[
"20140615T202617.118015",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.118014"
},
"format": "I am disconnecting peer 128.199.180.19:56891 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140615T202617.119228",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.119227"
},
"format": "I am disconnecting peer 180.153.142.120:8764 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140615T202617.121452",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.121450"
},
"format": "I am disconnecting peer 106.187.91.24:38866 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140615T202617.122178",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.122176"
},
"format": "I am disconnecting peer 106.185.24.234:39283 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140615T202617.124988",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.124986"
},
"format": "I am disconnecting peer 79.173.81.171:8764 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140615T202617.126778",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.126776"
},
"format": "I am disconnecting peer 80.240.133.79:55577 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140615T202617.135656",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.135654"
},
"format": "I am disconnecting peer 162.243.127.243:39878 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140615T202617.138049",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T202617.138048"
},
"format": "I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
]
]
Looks like I am two different forks.
desktop
>>> blockchain_get_block_by_number 8312
{
"previous": "e9e03bdb20102b3a54705f6d00d61e188bac0577",
"block_num": 8312,
"fee_rate": 1000,
"delegate_pay_rate": 77799,
"timestamp": "20140615T202715",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "5e35de2abda755a54cb771fa55fa12b54ce832d0",
"previous_secret": "343e7ff8cc86e25ecb4e8b2ad57cf1fb2681eefa",
"delegate_signature": "1fcec3efbb49f099c9c63444636a1300428b8af87fbd5a07043f761e7e88fa45d5494a5ed0187c94e680a91c9d6ea179ee75a0b39568b36380ab03774385990049",
"user_transaction_ids": []
delegate node
blockchain_get_block_by_number 8312
{
"previous": "12c95234b7fa8dfe12e0e2ae4a238e384953daf0",
"block_num": 8312,
"fee_rate": 1000,
"delegate_pay_rate": 77799,
"timestamp": "20140615T205800",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "41ebd8f0adc61466e4daa57b64c2736ff7dd4ed5",
"previous_secret": "62518597fa402d3cfdd670fe2effda4474e0d1ab",
"delegate_signature": "2042c68aad18bcf3698ca63fc29bbc6cd93ba86148a1b8dad5cf8087eba98fa554324f842d44435bc1793ac9824eab374a211b070c722e12b2c53ea5cdb7122568",
"user_transaction_ids": []
}
-
Would it be bad to automatically fire delegates if they fall below a certain ratio of blocks produced vs blocks missed?
-
Do you have your delegate key imported on two separate nodes?
That would partially explain why you keep getting onto a fork
No, delegate key is only loaded on server node.
-
"blockchain_average_delegate_participation": 70.69...........
Still working out some bugs that we have found, but it looks like forking has been greatly reduced.
-
I just recompiled the client. However i cannot get it to work. I get the error:
Initializing genesis state from built-in genesis file
Not starting RPC server, use --server to enable the RPC interface
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
{"method":"read","len":23,"over":1}
th_a datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
{"type":"uint8_t"}
th_a raw.hpp:440 unpack
optional<fc::exception>
{"type":"fc::exception"}
th_a raw.hpp:164 unpack
Error unpacking field last_error
{"field":"last_error"}
th_a raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
{"type":"bts::net::potential_peer_record"}
th_a raw.hpp:440 unpack
-
I just recompiled the client. However i cannot get it to work. I get the error:
Initializing genesis state from built-in genesis file
Not starting RPC server, use --server to enable the RPC interface
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
{"method":"read","len":23,"over":1}
th_a datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
{"type":"uint8_t"}
th_a raw.hpp:440 unpack
optional<fc::exception>
{"type":"fc::exception"}
th_a raw.hpp:164 unpack
Error unpacking field last_error
{"field":"last_error"}
th_a raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
{"type":"bts::net::potential_peer_record"}
th_a raw.hpp:440 unpack
delete your peer database "rm -r ~/.BitSharesXTS/peers.leveldb"
-
History of recent forks...
(http://bitshares.org/documentation/fork2.svg)
The bottom number in each circle is the time slice... it should be sequential. If it is not sequential then it means some blocks were missed.
These are the forks known by the main seed node.
-
i already deleted ~/.BitsharesXTS
-
i already deleted ~/.BitsharesXTS
that's the data dir you're using? Maybe you need a space: https://github.com/BitShares/bitshares_toolkit/issues/291
-
my init-delegate-42 had 1.0000000 XTS
I used "wallet_account_register xeldal init-delegate-42" to register a new account "xeldal"
This was successful.
I then tried to "wallet_account_update_registration xeldal init-delegate-42 null true"
obviously I had insufficient funds and it failed but now when i check the balance of init-delegate-42 it reads 0.0000 XTS
xeldal (unlocked) >>> wallet_account_balance
init-delegate-42:
0.000000 XTS
I didn't get a screen capture at the time but here is what i get when i try again
wallet_account_update_registration xeldal init-delegate-42 null true
20011 insufficient_funds: insufficient funds
{"required":"10.495702 XTS","available":"0.000000 XTS"}
where did the remaining 0.989999 XTS go.
Edit: Nevermind wallet_rescan_blockchain fixed it.
xeldal (unlocked) >>> wallet_account_balance
init-delegate-42:
0.989999 XTS
-
i already deleted ~/.BitsharesXTS
that's the data dir you're using? Maybe you need a space: https://github.com/BitShares/bitshares_toolkit/issues/291
yep that was it
-
Still having troubles with my delegate node. Rebuilt from latest source.
>>> about
{
"bitshares_toolkit_revision": "4c439dd2a81b970646252893c36716d38c5fccc7",
"bitshares_toolkit_revision_age": "47 minutes ago",
"fc_revision": "888a01881aa5aa1313509aa7044455cac02359dc",
"fc_revision_age": "3 hours ago",
"compile_date": "compiled on Jun 15 2014 at 22:33:47"
}
Deleted data dir, recreated wallet and imported delegate key. Now I am stuck on block 5685
>>> list_errors
[]
--- there are now 10 active connections to the p2p network
--- in sync with p2p network
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 5685,
"blockchain_head_block_time": "20140615T040245",
"blockchain_head_block_time_rel": "18 hours old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 16.387903362054402,
"network_num_connections": 10,
-
We're all stuck there ATM, working on it
-
just realized wallet need to be unlocked to produce blocks
],[
"20140615T223301.398618",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 453,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140615T223301.398297"
},
"format": "_wallet->is_unlocked(): Wallet must be unlocked to produce
blocks",
"data": {}
}
]
-
roy (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
roy (unlocked) >>> wallet_account_transaction_history init-delegate-101
BLK .TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
pending 2014-06-13T15:13:08 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS 10075a1e
pending 2014-06-13T15:22:40 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS d628823e
pending 2014-06-13T15:23:41 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS f8c2e9ba
pending 2014-06-13T15:26:45 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS f59d8204
pending 2014-06-13T15:31:54 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS e5d40c89
pending 2014-06-13T15:33:28 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS 11b6e455
1638.0 2014-06-13T15:39:15 init-delegate-101 init-delegate-101 register zf 0.000000 XTS 0.010001 XTS a63d3a1e
pending 2014-06-14T04:58:30 init-delegate-101 init-delegate-101 register init-delegate-118 as a... 0.000000 XTS 10.495701 XTS cfa13613
pending 2014-06-14T05:22:45 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS bc09a847
roy (unlocked) >>> wallet_account_transaction_history zf
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
roy (unlocked) >>> wallet_account_transaction_history testz-test
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
as up code show , I list all accouts in my wallet,and every translation of my accounts,
maybe I think there is some bug , why I have follow accounts, I never register it ,and more serious thing is I can get the private key of "testz-test" and there is no translation for regester fee. BM ,what is wrong?
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
-
roy (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
roy (unlocked) >>> wallet_account_transaction_history init-delegate-101
BLK .TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
pending 2014-06-13T15:13:08 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS 10075a1e
pending 2014-06-13T15:22:40 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS d628823e
pending 2014-06-13T15:23:41 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS f8c2e9ba
pending 2014-06-13T15:26:45 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS f59d8204
pending 2014-06-13T15:31:54 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS e5d40c89
pending 2014-06-13T15:33:28 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS 11b6e455
1638.0 2014-06-13T15:39:15 init-delegate-101 init-delegate-101 register zf 0.000000 XTS 0.010001 XTS a63d3a1e
pending 2014-06-14T04:58:30 init-delegate-101 init-delegate-101 register init-delegate-118 as a... 0.000000 XTS 10.495701 XTS cfa13613
pending 2014-06-14T05:22:45 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS bc09a847
roy (unlocked) >>> wallet_account_transaction_history zf
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
roy (unlocked) >>> wallet_account_transaction_history testz-test
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
as up code show , I list all accouts in my wallet,and every translation of my accounts,
maybe I think there is some bug , why I have follow accounts, I never register it ,and more serious thing is I can get the private key of "testz-test" and there is no translation for regester fee. BM ,what is wrong?
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
I think what happened was that the old wallet sync bug affected you, and it won't go away just from updating because it has to do with your wallet not clearing its indices.
What you should do is dump all your private keys, erase data dir, and re-import.
and more serious thing is I can get the private key of "testz-test"
Really? Are you sure you are able to wallet_dump_private_key for that address? If so, are you sure it's not actually one of yours?
I would be very very surprised if private keys were somehow shared, that is almost certainly not the case.
-
roy (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
zf XTS85r3BqawzUQF6fSy8PHGvH2QS9Q8Fk8VSgZGvdN6zvcPdUNE9V 2014-06-14T01:02:00 0
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
init-delegate-101 XTS6g8JzHR9WFixKjXTw3vwN54KE3Bf4kbLjBKUcw7i9yEzzD1aj4 2014-06-13T12:43:15 0
roy (unlocked) >>> wallet_account_transaction_history init-delegate-101
BLK .TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
pending 2014-06-13T15:13:08 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS 10075a1e
pending 2014-06-13T15:22:40 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS d628823e
pending 2014-06-13T15:23:41 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS f8c2e9ba
pending 2014-06-13T15:26:45 init-delegate-101 init-delegate-101 register init-delegate-110 0.000000 XTS 0.010001 XTS f59d8204
pending 2014-06-13T15:31:54 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS e5d40c89
pending 2014-06-13T15:33:28 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS 11b6e455
1638.0 2014-06-13T15:39:15 init-delegate-101 init-delegate-101 register zf 0.000000 XTS 0.010001 XTS a63d3a1e
pending 2014-06-14T04:58:30 init-delegate-101 init-delegate-101 register init-delegate-118 as a... 0.000000 XTS 10.495701 XTS cfa13613
pending 2014-06-14T05:22:45 init-delegate-101 init-delegate-101 register init-delegate-118 0.000000 XTS 0.010001 XTS bc09a847
roy (unlocked) >>> wallet_account_transaction_history zf
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
roy (unlocked) >>> wallet_account_transaction_history testz-test
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
as up code show , I list all accouts in my wallet,and every translation of my accounts,
maybe I think there is some bug , why I have follow accounts, I never register it ,and more serious thing is I can get the private key of "testz-test" and there is no translation for regester fee. BM ,what is wrong?
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
I think what happened was that the old wallet sync bug affected you, and it won't go away just from updating because it has to do with your wallet not clearing its indices.
What you should do is dump all your private keys, erase data dir, and re-import.
and more serious thing is I can get the private key of "testz-test"
Really? Are you sure you are able to wallet_dump_private_key for that address? If so, are you sure it's not actually one of yours?
I would be very very surprised if private keys were somehow shared, that is almost certainly not the case.
I will double check it after work ,
-
I'm typically getting about 8 connections immediately on startup, but they seem to gradually drop out as time goes on. I just came back and was down to 4, so I restarted the client and I'm at 8 again.
-
I'm typically getting about 8 connections immediately on startup, but they seem to gradually drop out as time goes on. I just came back and was down to 4, so I restarted the client and I'm at 8 again.
I'll just report - everything seems to work flawlessly. No crashes, no diminishing amount of connections. Log size is about 6.5GB since I restarted the client 32 hours ago. Restart was due to extremely large logfile filling up the assigned VM HDD size.
emski (unlocked) >>> get_info
{
"blockchain_head_block_num": 10037,
"blockchain_head_block_time": "20140616T065300",
"blockchain_confirmation_requirement": 288,
"blockchain_average_delegate_participation": 67.737430167597765,
"network_num_connections": 20,
"wallet_unlocked_seconds_remaining": 99822822,
"wallet_next_block_production_time": "20140616T070245",
"wallet_seconds_until_next_block_production": 500,
"wallet_local_time": "20140616T065425",
"blockchain_random_seed": "934cc04728e99de2cddd3f44c55cb26814628f33",
"blockchain_shares": 10000337282249,
"network_num_connections_max": 50,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170814T152807",
"wallet_version": 100
}
and delegate stats:
2 init-delegate-2 111301770268 0 1.11298 % 145 47
3 init-delegate-3 100343412064 0 1.0034 % 150 44
4 init-delegate-4 100943264829 0 1.0094 % 147 46
25 init-delegate-25 97173533229 0 0.971703 % 150 47
*inactive (this one was voted out):
1 init-delegate-1 70834712425 10000000 0.708223 % 32 38
High missed blocks are due to my timezone. When I woke up in the morning the test already had began.
-
updated the latest codes
but it shows
wang (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_time": "20140616T071527",
"blockchain_head_block_time_rel": "0 second old",
"blockchain_confirmation_requirement": 194,
"blockchain_average_delegate_participation": 0,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 9999891,
"wallet_next_block_production_time": "20140616T071615",
"wallet_seconds_until_next_block_production": 48,
"wallet_local_time": "20140616T071527",
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_shares": 9999999983936,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141010T010018",
"wallet_version": 100
}
wang (unlocked) >>> about
{
"bitshares_toolkit_revision": "bb16f2323fe66c31e6b8de8f5c774c7b35c877b5",
"bitshares_toolkit_revision_age": "10 hours ago",
"fc_revision": "888a01881aa5aa1313509aa7044455cac02359dc",
"fc_revision_age": "13 hours ago",
"compile_date": "compiled on Jun 16 2014 at 15:10:43"
}
-
I'll just report - everything seems to work flawlessly. No crashes, no diminishing amount of connections. Log size is about 6.5GB since I restarted the client 32 hours ago. Restart was due to extremely large logfile filling up the assigned VM HDD size.
In your data folder run:
$ rm default.log ; ln -s /dev/null default.logThen all log entries will be 'deleted' by default :) No log-bloating .. but also no log file-content :)
Further,
network_set_advanced_node_parameters {"desired_number_of_connections":25}
should increase you number of connections... however, there seems to be a bug currently, because I am stuck with 8 connections :(
-
updated the latest codes
but it shows
wang (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_time": "20140616T071527",
"blockchain_head_block_time_rel": "0 second old",
"blockchain_confirmation_requirement": 194,
"blockchain_average_delegate_participation": 0,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 9999891,
"wallet_next_block_production_time": "20140616T071615",
"wallet_seconds_until_next_block_production": 48,
"wallet_local_time": "20140616T071527",
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_shares": 9999999983936,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141010T010018",
"wallet_version": 100
}
wang (unlocked) >>> about
{
"bitshares_toolkit_revision": "bb16f2323fe66c31e6b8de8f5c774c7b35c877b5",
"bitshares_toolkit_revision_age": "10 hours ago",
"fc_revision": "888a01881aa5aa1313509aa7044455cac02359dc",
"fc_revision_age": "13 hours ago",
"compile_date": "compiled on Jun 16 2014 at 15:10:43"
}
You are not yet synced .. I run the same code. All fine here ..
"network_num_connections": 0,
[/b]
Seems to be a connection issue at your end :(
-
Can someone send me some test fund for applying delegate?
XTS8Eso3RfRDQviSKuQxhWL9hQCQ7siaZPbDzYULxcat1d1ncdhu1
My node is up and running with average 14 connections. You are welcome to connect to it.
180.153.142.120:8764
-
Can someone send me some test fund for applying delegate?
XTS8Eso3RfRDQviSKuQxhWL9hQCQ7siaZPbDzYULxcat1d1ncdhu1
My node is up and running with average 14 connections. You are welcome to connect to it.
180.153.142.120:8764
sent
-
thanks xeroc
Sent from my iPhone using Tapatalk
-
Can someone send me some test fund for applying delegate?
XTS8Eso3RfRDQviSKuQxhWL9hQCQ7siaZPbDzYULxcat1d1ncdhu1
My node is up and running with average 14 connections. You are welcome to connect to it.
180.153.142.120:8764
sent
How did you do that? wallet_transfer seems to only work with account names, or did you use his account name?
-
I'll just report - everything seems to work flawlessly. No crashes, no diminishing amount of connections. Log size is about 6.5GB since I restarted the client 32 hours ago. Restart was due to extremely large logfile filling up the assigned VM HDD size.
In your data folder run:
$ rm default.log ; ln -s /dev/null default.logThen all log entries will be 'deleted' by default :) No log-bloating .. but also no log file-content :)
Further,
network_set_advanced_node_parameters {"desired_number_of_connections":25}
should increase you number of connections... however, there seems to be a bug currently, because I am stuck with 8 connections :(
I just updated to recent revision that apparently fixes the large logs. And increased the size of VM HDD - we need the logs if something goes wrong after all. If the log file grows large again I'll archive it.
I've set desired_number_of_connections to 30 when I started the node and max connections to 50. Sometimes I get 30 connections but not always. I believe this is normal, isnt it ?
In order to increase your connections you should increase both desired_number_of_connections and max_number_of_connections (at least this makes sense to me).
-
who can send me some XTS or LOVE to test?
thanks
I have registe the wallet account alt.
-
updated the latest codes
but it shows
wang (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_time": "20140616T071527",
"blockchain_head_block_time_rel": "0 second old",
"blockchain_confirmation_requirement": 194,
"blockchain_average_delegate_participation": 0,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 9999891,
"wallet_next_block_production_time": "20140616T071615",
"wallet_seconds_until_next_block_production": 48,
"wallet_local_time": "20140616T071527",
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_shares": 9999999983936,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141010T010018",
"wallet_version": 100
}
wang (unlocked) >>> about
{
"bitshares_toolkit_revision": "bb16f2323fe66c31e6b8de8f5c774c7b35c877b5",
"bitshares_toolkit_revision_age": "10 hours ago",
"fc_revision": "888a01881aa5aa1313509aa7044455cac02359dc",
"fc_revision_age": "13 hours ago",
"compile_date": "compiled on Jun 16 2014 at 15:10:43"
}
You are not yet synced .. I run the same code. All fine here ..
"network_num_connections": 0,
[/b]
Seems to be a connection issue at your end :(
This is very strange.
Yesterday, the node is working good, there are almost 7 connections all the time.
I just compile the latest.
more info:
wang (unlocked) >>> network_list_potential_peers
ENDPOINT LAST SEEN LAST CONNECT ATTEMPT SUCCESSFUL CONNECT ATTEMPTS FAILED CONNECT ATTEMPTS LAST CONNECTION DISPOSITION LAST ERROR
114.215.104.153:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 0 exception: unspecified
Broken pipe
{"message":"Broken pipe"}
asio asio.cpp:28
84.238.140.192:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 0 exception: unspecified
Broken pipe
{"message":"Broken pipe"}
asio asio.cpp:28
107.170.30.182:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 9 canceled_exception: Canceled
Operation canceled
{"message":"Operation canceled"}
asio asio.cpp:45
wang (unlocked) >>>
wang (unlocked) >>>
wang (unlocked) >>> network_get_peer_info
[]
-
default (unlocked) >>> network_get_peer_info
[{
"addr": "80.240.133.79:55577",
"addrlocal": "10.10.40.72:52652",
"services": "00000001",
"lastsend": 1402905675,
"lastrecv": 1402905691,
"bytessent": 21936,
"bytesrecv": 119344,
"conntime": "20140616T013336.993163",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "aee32b7c276d08286085033384de88e8f692d9ae (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140615T165636",
"bitshares_git_revision_age": "15 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "81 hours ago (older than ours)",
"platform": "linux"
},{
"addr": "107.170.170.214:39219",
"addrlocal": "10.10.40.72:52652",
"services": "00000001",
"lastsend": 1402905661,
"lastrecv": 1402905690,
"bytessent": 14592,
"bytesrecv": 102416,
"conntime": "20140616T013337.053489",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "f8da55833029fb171b8bc86656f74bf916d9fa38 (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140615T023912",
"bitshares_git_revision_age": "29 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "81 hours ago (older than ours)",
"platform": "linux"
},{
"addr": "107.170.30.182:49076",
"addrlocal": "10.10.40.72:52652",
"services": "00000001",
"lastsend": 1402905675,
"lastrecv": 1402905691,
"bytessent": 31360,
"bytesrecv": 162752,
"conntime": "20140616T013335.204639",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "683ebc1cd0bc82087e35c6d1fe2835cf3210294f (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140615T204106",
"bitshares_git_revision_age": "11 hours ago (older than ours)",
"fc_git_revision_sha": "888a01881aa5aa1313509aa7044455cac02359dc (same as ours)",
"fc_git_revision_unix_timestamp": "20140615T181622",
"fc_git_revision_age": "14 hours ago (same as ours)",
"platform": "linux"
},{
"addr": "92.243.18.20:47771",
"addrlocal": "10.10.40.72:52652",
"services": "00000001",
"lastsend": 1402905691,
"lastrecv": 1402905693,
"bytessent": 117024,
"bytesrecv": 128384,
"conntime": "20140616T013331.828324",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "5517b4ca8d1b2383bbe3cc0b66d8ef7ee9480d5c (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140613T204157",
"bitshares_git_revision_age": "59 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "81 hours ago (older than ours)",
"platform": "linux"
},{
"addr": "106.185.24.234:39283",
"addrlocal": "10.10.40.72:52652",
"services": "00000001",
"lastsend": 1402905675,
"lastrecv": 1402905691,
"bytessent": 31600,
"bytesrecv": 80464,
"conntime": "20140616T013336.715732",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "458342c24ad06f44dc46d0de0f64566f1bc8da5e (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140615T032609",
"bitshares_git_revision_age": "29 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "81 hours ago (older than ours)",
"platform": "linux"
},{
"addr": "188.138.107.159:50013",
"addrlocal": "10.10.40.72:52652",
"services": "00000001",
"lastsend": 1402905691,
"lastrecv": 1402905691,
"bytessent": 25264,
"bytesrecv": 108112,
"conntime": "20140616T013331.850439",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "458342c24ad06f44dc46d0de0f64566f1bc8da5e (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140615T032609",
"bitshares_git_revision_age": "29 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "81 hours ago (older than ours)",
"platform": "linux"
},{
"addr": "84.238.140.192:50546",
"addrlocal": "10.10.40.72:52652",
"services": "00000001",
"lastsend": 1402905691,
"lastrecv": 1402905691,
"bytessent": 29824,
"bytesrecv": 86720,
"conntime": "20140616T013333.174146",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "dbeaf650cb56b92abc24954bfa8417a60c4b464b (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140614T025700",
"bitshares_git_revision_age": "53 hours ago (older than ours)",
"fc_git_revision_sha": "eab346121d1e6a2f52246e84b503907d8ec705f1 (different from ours)",
"fc_git_revision_unix_timestamp": "20140612T224012",
"fc_git_revision_age": "81 hours ago (older than ours)",
"platform": "linux"
},{
"addr": "107.170.30.182:8764",
"addrlocal": "10.10.40.72:52652",
"services": "00000001",
"lastsend": 1402905690,
"lastrecv": 1402905691,
"bytessent": 41168,
"bytesrecv": 209536,
"conntime": "20140616T013133.809657",
"pingtime": "",
"pingwait": "",
"version": "",
"subver": "bts::net::node",
"inbound": false,
"firewall_status": "unknown",
"startingheight": "",
"banscore": "",
"syncnode": "",
"bitshares_git_revision_sha": "683ebc1cd0bc82087e35c6d1fe2835cf3210294f (different from ours)",
"bitshares_git_revision_unix_timestamp": "20140615T204106",
"bitshares_git_revision_age": "11 hours ago (older than ours)",
"fc_git_revision_sha": "888a01881aa5aa1313509aa7044455cac02359dc (same as ours)",
"fc_git_revision_unix_timestamp": "20140615T181622",
"fc_git_revision_age": "14 hours ago (same as ours)",
"platform": "linux"
}
]
default (unlocked) >>>
-
updated the latest codes
but it shows
wang (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_time": "20140616T071527",
"blockchain_head_block_time_rel": "0 second old",
"blockchain_confirmation_requirement": 194,
"blockchain_average_delegate_participation": 0,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 9999891,
"wallet_next_block_production_time": "20140616T071615",
"wallet_seconds_until_next_block_production": 48,
"wallet_local_time": "20140616T071527",
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_shares": 9999999983936,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141010T010018",
"wallet_version": 100
}
wang (unlocked) >>> about
{
"bitshares_toolkit_revision": "bb16f2323fe66c31e6b8de8f5c774c7b35c877b5",
"bitshares_toolkit_revision_age": "10 hours ago",
"fc_revision": "888a01881aa5aa1313509aa7044455cac02359dc",
"fc_revision_age": "13 hours ago",
"compile_date": "compiled on Jun 16 2014 at 15:10:43"
}
You are not yet synced .. I run the same code. All fine here ..
"network_num_connections": 0,
[/b]
Seems to be a connection issue at your end :(
This is very strange.
Yesterday, the node is working good, there are almost 7 connections all the time.
I just compile the latest.
more info:
wang (unlocked) >>> network_list_potential_peers
ENDPOINT LAST SEEN LAST CONNECT ATTEMPT SUCCESSFUL CONNECT ATTEMPTS FAILED CONNECT ATTEMPTS LAST CONNECTION DISPOSITION LAST ERROR
114.215.104.153:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 0 exception: unspecified
Broken pipe
{"message":"Broken pipe"}
asio asio.cpp:28
84.238.140.192:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 0 exception: unspecified
Broken pipe
{"message":"Broken pipe"}
asio asio.cpp:28
107.170.30.182:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 9 canceled_exception: Canceled
Operation canceled
{"message":"Operation canceled"}
asio asio.cpp:45
wang (unlocked) >>>
wang (unlocked) >>>
wang (unlocked) >>> network_get_peer_info
[]
delete your peer database
-
updated the latest codes
but it shows
wang (unlocked) >>> info
{
"blockchain_head_block_num": 0,
"blockchain_head_block_time": "20140616T071527",
"blockchain_head_block_time_rel": "0 second old",
"blockchain_confirmation_requirement": 194,
"blockchain_average_delegate_participation": 0,
"network_num_connections": 0,
"wallet_unlocked_seconds_remaining": 9999891,
"wallet_next_block_production_time": "20140616T071615",
"wallet_seconds_until_next_block_production": 48,
"wallet_local_time": "20140616T071527",
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"blockchain_shares": 9999999983936,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141010T010018",
"wallet_version": 100
}
wang (unlocked) >>> about
{
"bitshares_toolkit_revision": "bb16f2323fe66c31e6b8de8f5c774c7b35c877b5",
"bitshares_toolkit_revision_age": "10 hours ago",
"fc_revision": "888a01881aa5aa1313509aa7044455cac02359dc",
"fc_revision_age": "13 hours ago",
"compile_date": "compiled on Jun 16 2014 at 15:10:43"
}
You are not yet synced .. I run the same code. All fine here ..
"network_num_connections": 0,
[/b]
Seems to be a connection issue at your end :(
This is very strange.
Yesterday, the node is working good, there are almost 7 connections all the time.
I just compile the latest.
more info:
wang (unlocked) >>> network_list_potential_peers
ENDPOINT LAST SEEN LAST CONNECT ATTEMPT SUCCESSFUL CONNECT ATTEMPTS FAILED CONNECT ATTEMPTS LAST CONNECTION DISPOSITION LAST ERROR
114.215.104.153:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 0 exception: unspecified
Broken pipe
{"message":"Broken pipe"}
asio asio.cpp:28
84.238.140.192:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 0 exception: unspecified
Broken pipe
{"message":"Broken pipe"}
asio asio.cpp:28
107.170.30.182:8764 1970-01-01T00:00:00 2014-06-16T07:52:50 0 12 last_connection_failed 9 canceled_exception: Canceled
Operation canceled
{"message":"Operation canceled"}
asio asio.cpp:45
wang (unlocked) >>>
wang (unlocked) >>>
wang (unlocked) >>> network_get_peer_info
[]
delete your peer database
I delete the .BitSharesXTS absolutely.
-
Can someone send me some test fund for applying delegate?
XTS8Eso3RfRDQviSKuQxhWL9hQCQ7siaZPbDzYULxcat1d1ncdhu1
My node is up and running with average 14 connections. You are welcome to connect to it.
180.153.142.120:8764
sent
How did you do that? wallet_transfer seems to only work with account names, or did you use his account name?
you need to wallet_add_contact .. to make a local contact name for an address
-
wang (unlocked) >>> list_errors
[]
wang (unlocked) >>> list_errors
[]
-
who can send me some XTS or LOVE to test?
thanks
I have registe the wallet account alt.
Sent.
-
who's got some LOVE to send my way?
-
alt, clout sent some XTS :)
got no LOVE send me some if we have created it
-
I manually add a nodes to fixed my problems.
network_add_node "80.240.133.79:55577" "add"
But how can I know the node is correctly on the main chain?
-
who's got some LOVE to send my way?
10367.0 2014-06-16T08:35:15 xeroc spartako For free! 100.000000 FREE 0.010000 XTS 76a82442
10368.1 2014-06-16T08:35:30 xeroc puppies For free! 100.000000 FREE 0.010000 XTS 87f60ee8
10369.0 2014-06-16T08:35:45 xeroc mauritso For free! 100.000000 FREE 0.010000 XTS 75eac050
10370.1 2014-06-16T08:36:00 xeroc crazybit For free! 100.000000 FREE 0.010000 XTS bfa3513e
10370.0 2014-06-16T08:36:00 xeroc coolspeed For free! 100.000000 FREE 0.010000 XTS 050e1d3d
10373.0 2014-06-16T08:37:00 xeroc blockchainer For free! 100.000000 FREE 0.010000 XTS 8a537930
pending 2014-06-16T08:37:00 xeroc bts101 For free! 100.000000 FREE 0.010000 XTS 7cdd5565
pending 2014-06-16T08:37:05 xeroc cgafeng For free! 100.000000 FREE 0.010000 XTS 3ac0a53f
pending 2014-06-16T08:37:10 xeroc clout For free! 100.000000 FREE 0.010000 XTS 480b54d4
-
Have some happiness :D
10382.1 2014-06-16T08:41:00 betax xeroc 100,000.000000 HAP 0.010000 XTS e2267cdf
10383.0 2014-06-16T08:41:30 betax clout 100,000.000000 HAP 0.010000 XTS 23586aee
10384.0 2014-06-16T08:42:15 betax alt 100,000.000000 HAP 0.010000 XTS 851d86be
10389.0 2014-06-16T08:44:15 betax boombastic 100,000.000000 HAP 0.010000 XTS 1cf5c729
10395.0 2014-06-16T08:46:15 betax spartako 100,000.000000 HAP 0.010000 XTS c0af7ff4
10397.0 2014-06-16T08:46:45 betax puppies 100,000.000000 HAP 0.010000 XTS 95e475fc
10400.0 2014-06-16T08:47:30 betax mauritso Happiness 100,000.000000 HAP 0.010000 XTS ad2c6d26
10401.0 2014-06-16T08:47:45 betax crazybit Happiness 100,000.000000 HAP 0.010000 XTS 07a00bcc
10403.0 2014-06-16T08:48:15 betax coolspeed Happiness 100,000.000000 HAP 0.010000 XTS 3ec7df9c
10404.0 2014-06-16T08:49:00 betax blockchainer Happiness 100,000.000000 HAP 0.010000 XTS bbadbcf6
10405.1 2014-06-16T08:49:30 betax bts101 Happiness 100,000.000000 HAP 0.010000 XTS c86fe6b8
10405.0 2014-06-16T08:49:30 betax cgafeng Happiness 100,000.000000 HAP 0.010000 XTS 268685ca
-
I have 10.0 XTS initially.
Had my account name registered (with remaining balance 9.969992 XTS) and tried to update the registration as delegate.
wallet_account_update_registration boombastic-ags boombastic-ags null true
It says
20011 insufficient_funds: insufficient funds
{"required":"10.495702 XTS","available":"9.969992 XTS"}
th_a wallet.cpp:206 withdraw_to_transaction
{"amount":10495702,"asset_id":0,"from_account_address":"XTSBwzbtZRFgLT3V7YxYkSk7VMH4v1r9cL41","trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSNJT7o8AbedmHM5JBvpXVxb45kNjRQegKr","amount":9969992,"claim_input_data":""}}],"signatures":[]},"required_signatures":["XTSFBCWGyFnXBAb9by6RMLzPwrtQB3Ah45RU"]}
th_a wallet.cpp:207 withdraw_to_transaction
How much does it require for registering delegate? Is this normal? After the error, wallet_account_balance shows 0. I need to do wallet_rescan_blockchain to have remaining 9.969992 XTS balance to show up correctly.
-
How much does it require for registering delegate? Is this normal? After the error, wallet_account_balance shows 0. I need to do wallet_rescan_blockchain to have remaining 9.969992 XTS balance to show up correctly.
"required":"10.495702 XTS"
Just sent some more ... have fun
-
I sent more LOVE :)
10511.0 2014-06-16T09:32:15 spartako alt some love 100.000000 LOVE 0.010000 XTS 870cd6e6
10513.0 2014-06-16T09:33:00 spartako clout some love 100.000000 LOVE 0.010000 XTS fa122e8d
10515.0 2014-06-16T09:34:00 spartako boombastic some love 100.000000 LOVE 0.010000 XTS 287aac38
10515.2 2014-06-16T09:34:00 spartako bts101 some love 100.000000 LOVE 0.010000 XTS a0f8227b
10515.3 2014-06-16T09:34:00 spartako crazybit some love 100.000000 LOVE 0.010000 XTS b3a82e4b
10515.1 2014-06-16T09:34:00 spartako blockchainer some love 100.000000 LOVE 0.010000 XTS 76d1df26
10515.4 2014-06-16T09:34:00 spartako coolspeed some love 100.000000 LOVE 0.010000 XTS c5ec73cb
10517.0 2014-06-16T09:35:00 spartako cgafeng some love 100.000000 LOVE 0.010000 XTS d006ba63
10518.0 2014-06-16T09:35:30 spartako xeroc some love 100.000000 LOVE 0.010000 XTS 9acda5ed
10519.1 2014-06-16T09:36:00 spartako mauritso some love 100.000000 LOVE 0.010000 XTS b898378d
10519.0 2014-06-16T09:36:00 spartako puppies some love 100.000000 LOVE 0.010000 XTS 862db875
I tried to buy XTS with LOVE but nobody want my love :(
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTS3NhNgEQjUSqLYKsZsjUMAhdDgoLfw5emE bid_order 10.000000 XTS 0.1 LOVE / XTS 1.000000 LOVE
XTS23zcpVE1MgRZZwEXKpbRZd6avmk32PvkR bid_order 1.000000 XTS 0.1 LOVE / XTS 0.100000 LOVE
XTSDp79gmqKyAEtDPK8Q3EubqY73PCZbVEfy bid_order 0.000000 XTS 0.1 LOVE / XTS 0.000000 LOVE
XTS8CwnoEZJAXX382WSfbvW9iAohQ9jpFs29 bid_order 100.000000 XTS 0.1 LOVE / XTS 10.000000 LOVE
-
How much does it require for registering delegate? Is this normal? After the error, wallet_account_balance shows 0. I need to do wallet_rescan_blockchain to have remaining 9.969992 XTS balance to show up correctly.
I have created a ticket / issue for that already in git hub.
I have sent you some more.
-
thanks
Sent from my iPhone using Tapatalk
-
I sent more LOVE :)
10511.0 2014-06-16T09:32:15 spartako alt some love 100.000000 LOVE 0.010000 XTS 870cd6e6
10513.0 2014-06-16T09:33:00 spartako clout some love 100.000000 LOVE 0.010000 XTS fa122e8d
10515.0 2014-06-16T09:34:00 spartako boombastic some love 100.000000 LOVE 0.010000 XTS 287aac38
10515.2 2014-06-16T09:34:00 spartako bts101 some love 100.000000 LOVE 0.010000 XTS a0f8227b
10515.3 2014-06-16T09:34:00 spartako crazybit some love 100.000000 LOVE 0.010000 XTS b3a82e4b
10515.1 2014-06-16T09:34:00 spartako blockchainer some love 100.000000 LOVE 0.010000 XTS 76d1df26
10515.4 2014-06-16T09:34:00 spartako coolspeed some love 100.000000 LOVE 0.010000 XTS c5ec73cb
10517.0 2014-06-16T09:35:00 spartako cgafeng some love 100.000000 LOVE 0.010000 XTS d006ba63
10518.0 2014-06-16T09:35:30 spartako xeroc some love 100.000000 LOVE 0.010000 XTS 9acda5ed
10519.1 2014-06-16T09:36:00 spartako mauritso some love 100.000000 LOVE 0.010000 XTS b898378d
10519.0 2014-06-16T09:36:00 spartako puppies some love 100.000000 LOVE 0.010000 XTS 862db875
I tried to buy XTS with LOVE but nobody want my love :(
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTS3NhNgEQjUSqLYKsZsjUMAhdDgoLfw5emE bid_order 10.000000 XTS 0.1 LOVE / XTS 1.000000 LOVE
XTS23zcpVE1MgRZZwEXKpbRZd6avmk32PvkR bid_order 1.000000 XTS 0.1 LOVE / XTS 0.100000 LOVE
XTSDp79gmqKyAEtDPK8Q3EubqY73PCZbVEfy bid_order 0.000000 XTS 0.1 LOVE / XTS 0.000000 LOVE
XTS8CwnoEZJAXX382WSfbvW9iAohQ9jpFs29 bid_order 100.000000 XTS 0.1 LOVE / XTS 10.000000 LOVE
All LOVE is gone
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
-
All LOVE is gone
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
I think there is a problem with "wallet_market_order_list" (or wallet_market_submit_bid) command because I can see the LOVE orders:
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTS3NhNgEQjUSqLYKsZsjUMAhdDgoLfw5emE bid_order 10.000000 XTS 0.1 LOVE / XTS 1.000000 LOVE
XTS23zcpVE1MgRZZwEXKpbRZd6avmk32PvkR bid_order 1.000000 XTS 0.1 LOVE / XTS 0.100000 LOVE
XTSDp79gmqKyAEtDPK8Q3EubqY73PCZbVEfy bid_order 0.000000 XTS 0.1 LOVE / XTS 0.000000 LOVE
XTS8CwnoEZJAXX382WSfbvW9iAohQ9jpFs29 bid_order 100.000000 XTS 0.1 LOVE / XTS 10.000000 LOVE
Can you try to buy some love with this command and we see what happen?
wallet_market_submit_bid betax 10 XTS 1 LOVE
-
All LOVE is gone
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
Not enough funds (I don't have any love ?)
I think there is a problem with "wallet_market_order_list" (or wallet_market_submit_bid) command because I can see the LOVE orders:
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTS3NhNgEQjUSqLYKsZsjUMAhdDgoLfw5emE bid_order 10.000000 XTS 0.1 LOVE / XTS 1.000000 LOVE
XTS23zcpVE1MgRZZwEXKpbRZd6avmk32PvkR bid_order 1.000000 XTS 0.1 LOVE / XTS 0.100000 LOVE
XTSDp79gmqKyAEtDPK8Q3EubqY73PCZbVEfy bid_order 0.000000 XTS 0.1 LOVE / XTS 0.000000 LOVE
XTS8CwnoEZJAXX382WSfbvW9iAohQ9jpFs29 bid_order 100.000000 XTS 0.1 LOVE / XTS 10.000000 LOVE
Can you try to buy some love with this command and we see what happen?
wallet_market_submit_bid betax 10 XTS 1 LOVE
-
Can you see this:
wallet_market_order_list HAP FREE
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTSG3opSXiRbRxuWZUv3kSVDZzrFq5SMAwkt bid_order 50.000000 FREE 1000. HAP / FREE 50,000.000000 HAP
or this
default (unlocked) >>> wallet_market_order_list HAP XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTS6kDM29yaoQTiSMetqaVJsFqkiHMp1wAWj bid_order 50.000000 XTS 50000. HAP / XTS 2,500,000.000000 HAP
-
Made the order
10586.0 2014-06-16T10:01:30 betax ORDER-G3opSXiR buy 50 FREE @ 1000 HAP 50,000.000000 HAP 0.010000 XTS fd732f64
10590.0 2014-06-16T10:03:15 betax ORDER-NJ3T2GiM buy 100 LOVE @ 1000 HAP 100,000.000000 HAP 0.010000 XTS fc3216a0
10591.0 2014-06-16T10:04:15 betax ORDER-6kDM29ya buy 50 XTS @ 50000 HAP 2,500,000.000000 HAP 0.010000 XTS ef8d5283
10617.0 2014-06-16T10:14:45 spartako betax 1,000.000000 LOVE 0.000000 XTS 4f9b3012
10622.0 2014-06-16T10:17:00 betax ORDER-5UrcvC7x buy 10 XTS @ 1 LOVE 10.000000 LOVE 0.010000 XTS d8c4501f
But look at this now:
default (unlocked) >>> wallet_market_order_list XTS LOVE
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTS5UrcvC7x65mTfgahtugtzjLYa89AWcNQv bid_order 10.000000 XTS 1. LOVE / XTS 10.000000 LOVE
-
But look at this now:
default (unlocked) >>> wallet_market_order_list XTS LOVE
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTS5UrcvC7x65mTfgahtugtzjLYa89AWcNQv bid_order 10.000000 XTS 1. LOVE / XTS 10.000000 LOVE
This is my "wallet_market_order_list":
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTSLvdkwYFrUpUA1bYa3DD9HxsvndmQD1kvV bid_order 10.000000 XTS 100. LOVE / XTS 1,000.000000 LOVE
XTS3NhNgEQjUSqLYKsZsjUMAhdDgoLfw5emE bid_order 10.000000 XTS 0.1 LOVE / XTS 1.000000 LOVE
XTS23zcpVE1MgRZZwEXKpbRZd6avmk32PvkR bid_order 1.000000 XTS 0.1 LOVE / XTS 0.100000 LOVE
XTSDp79gmqKyAEtDPK8Q3EubqY73PCZbVEfy bid_order 0.000000 XTS 0.1 LOVE / XTS 0.000000 LOVE
XTS8CwnoEZJAXX382WSfbvW9iAohQ9jpFs29 bid_order 100.000000 XTS 0.1 LOVE / XTS 10.000000 LOVE
default (unlocked) >>> wallet_market_order_list XTS LOVE
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
default (unlocked) >>> wallet_market_order_list HAP XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
default (unlocked) >>> wallet_market_order_list XTS HAP
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
-
Is it still possible to run as an (initial) delegate? A good friend of mine (excellent programmer) and I would partner up. The technical side he would support is at a totally professional level. Servers would be in Germany.
-
Sure .. just fetch enough votes in the current dry run and you will starf as an initial delegate .. afaik
-
But look at this now:
default (unlocked) >>> wallet_market_order_list XTS LOVE
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTS5UrcvC7x65mTfgahtugtzjLYa89AWcNQv bid_order 10.000000 XTS 1. LOVE / XTS 10.000000 LOVE
This is my "wallet_market_order_list":
default (unlocked) >>> wallet_market_order_list LOVE XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
XTSLvdkwYFrUpUA1bYa3DD9HxsvndmQD1kvV bid_order 10.000000 XTS 100. LOVE / XTS 1,000.000000 LOVE
XTS3NhNgEQjUSqLYKsZsjUMAhdDgoLfw5emE bid_order 10.000000 XTS 0.1 LOVE / XTS 1.000000 LOVE
XTS23zcpVE1MgRZZwEXKpbRZd6avmk32PvkR bid_order 1.000000 XTS 0.1 LOVE / XTS 0.100000 LOVE
XTSDp79gmqKyAEtDPK8Q3EubqY73PCZbVEfy bid_order 0.000000 XTS 0.1 LOVE / XTS 0.000000 LOVE
XTS8CwnoEZJAXX382WSfbvW9iAohQ9jpFs29 bid_order 100.000000 XTS 0.1 LOVE / XTS 10.000000 LOVE
default (unlocked) >>> wallet_market_order_list XTS LOVE
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
default (unlocked) >>> wallet_market_order_list HAP XTS
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
default (unlocked) >>> wallet_market_order_list XTS HAP
ID TYPE QUANTITY PRICE COST
-----------------------------------------------------------------------------------------------------------
I guess this is then partly implemented.
-
I guess this is then partly implemented.
Yes, I think we have to wait....thanks for your testing!
-
no bother i was doing a similar test myself
-
Can you vote me and send me some love :P
NAME BALANCE KEY REGISTERED TRUST LEVEL
networker 0.000000 XTS XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO 0
I sent you some XTS for register your name and some LOVE.
1400.0 2014-06-13T13:20:45 spartako networker 10.000000 XTS 0.010000 XTS 0865528f
1400.1 2014-06-13T13:20:45 spartako networker 100.000000 LOVE 0.010000 XTS 526193c9
When you will become delegate I am able to vote for you.
Why my balance still is zero?
networker (unlocked) >>> wallet_account_register
account_name: networker
pay_from_account: networker
10
!"Insufficient Funds": Requested 0.010001 XTS but only 0.000000 XTS available
{"required":"0.010001 XTS","available":"0.000000 XTS"}
th_a wallet.cpp:178 withdraw_to_transaction
networker (unlocked) >>> wallet_list_receive_accounts
NAME BALANCE KEY REGISTERED TRUST LEVEL
networker 0.000000 XTS XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO
Please help!
I think, I sent funds in an other chain fork.
I tried again:
1479.0 2014-06-13T15:48:45 spartako networker 10.000000 XTS 0.010000 XTS add543bb
Hi, Spartako, I didn't receive your XTS and think I'm on a fork chain so I reinstall bitshare_toolkit and creat account again. My XTS address has changed,
networker (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
networker XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m NO 0
Please send me some XTS aganin for registering as a delegate. Thanks a lot!
-
Hi, Spartako, I didn't receive your XTS and think I'm on a fork chain so I reinstall bitshare_toolkit and creat account again. My XTS address has changed,
networker (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
networker XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m NO 0
Please send me some XTS aganin for registering as a delegate. Thanks a lot!
Ok sent
10995.0 2014-06-16T12:42:45 spartako networker1 10.000000 XTS 0.010000 XTS 44c9bc93
-
Hi, Spartako, I didn't receive your XTS and think I'm on a fork chain so I reinstall bitshare_toolkit and creat account again. My XTS address has changed,
networker (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
networker XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m NO 0
Please send me some XTS aganin for registering as a delegate. Thanks a lot!
Ok sent
10995.0 2014-06-16T12:42:45 spartako networker1 10.000000 XTS 0.010000 XTS 44c9bc93
networker (unlocked) >>> wallet_account_balance networker
networker:
10.000000 XTS
Thank you very much!
BTW. Can I find my old account back if I reinstall bitshare_toolkit without backing up my wallet? and How to backup my wallet if next time same things happen?
-
networker (unlocked) >>> wallet_account_balance networker
networker:
10.000000 XTS
Thank you very much!
BTW. Can I find my old account back if I reinstall bitshare_toolkit without backing up my wallet? and How to backup my wallet if next time same things happen?
You can copy wallets directory in your data-dir (~/.BitShares XTS/) if you want create a backup.
You can also use the command "wallet_dump_private_key <ADDRESS_ACCOUNT>" for retrieving your private key and then import with "wallet_import_private_key" command.
-
Hi, Spartako, I didn't receive your XTS and think I'm on a fork chain so I reinstall bitshare_toolkit and creat account again. My XTS address has changed,
networker (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
networker XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m NO 0
Please send me some XTS aganin for registering as a delegate. Thanks a lot!
Ok sent
10995.0 2014-06-16T12:42:45 spartako networker1 10.000000 XTS 0.010000 XTS 44c9bc93
Now I found I register successfully.
networker (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
networker XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m 2014-06-16T12:49:00 0
Can someone trust me? I'll vote for you in the real run :)
-
I just sent some more .. try again
-
networker (unlocked) >>> wallet_account_register networker networker null true
20011 insufficient_funds: insufficient funds
{"required":"10.495701 XTS","available":"9.979998 XTS"}
th_a wallet.cpp:206 withdraw_to_transaction
Why now it need 10.49 XTS?
I don't know but I sent you an other XTS
11027.0 2014-06-16T12:56:15 spartako networker 1.000000 XTS 0.010000 XTS 4cf16afe
-
I just sent some more .. try again
Thank you, xeroc.
Just now I found myself register successfully.
Now I found I register successfully.
networker (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
networker XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m 2014-06-16T12:49:00 0
Can you give me some trust 8)
-
networker (unlocked) >>> wallet_account_balance networker
networker:
10.000000 XTS
Thank you very much!
BTW. Can I find my old account back if I reinstall bitshare_toolkit without backing up my wallet? and How to backup my wallet if next time same things happen?
You can copy wallets directory in your data-dir (~/.BitShares XTS/) if you want create a backup.
You can also use the command "wallet_dump_private_key <ADDRESS_ACCOUNT>" for retrieving your private key and then import with "wallet_import_private_key" command.
I see. Thank you, spartako!
-
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
-
I know I am a little late to the party, but I built the latest with a clean .BitsharesXTS dir and tried to import my wallet.dat from PTS using wallet_import_bitcoin and it seemed like it worked but I don't have any XTS. Am I doing something wrong? Could I get some XTS to try to register as a delegate with? :)
importing PrWXTV7BMNJikS36HTJZzdUXKDc4QKjRbz
importing Pkw41LBvT8BEhwiW7osiKtf5yHRah7w8n7
importing 1KakKQR3bGMexAEEuxeiqcEU4yBEd1QAxo
importing 1E1GsFVnh2EAufuekKDsAsR2j2zkrATCrj
OK
bdnoble (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
bdnoble (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
bdnoble XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ NO 0
bdnoble (unlocked) >>> wallet_get_info
{
"data_directory": "/home/ben/.BitSharesXTS/wallets",
"last_unlocked_scanned_block_number": 3829,
"last_locked_scanned_block_number": null,
"next_child_key_index": 2,
"default_transaction_priority_fee": {
"amount": 10000,
"asset_id": 0
},
"state": "open",
"locked": false,
"file": "/home/ben/.BitSharesXTS/wallets/bdnoble",
"scheduled_lock_time": "20140628T024833"
}
-
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
Wow! How to creat my own asset like you? that's awesome!
-
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
Wow! How to creat my own asset like you? that's awesome!
wallet_asset_create <symbol> <asset_name> <issuer_name> [description] [data] [maximum_share_supply] [precision]
-
I know I am a little late to the party, but I built the latest with a clean .BitsharesXTS dir and tried to import my wallet.dat from PTS using wallet_import_bitcoin and it seemed like it worked but I don't have any XTS. Am I doing something wrong? Could I get some XTS to try to register as a delegate with? :)
importing PrWXTV7BMNJikS36HTJZzdUXKDc4QKjRbz
importing Pkw41LBvT8BEhwiW7osiKtf5yHRah7w8n7
importing 1KakKQR3bGMexAEEuxeiqcEU4yBEd1QAxo
importing 1E1GsFVnh2EAufuekKDsAsR2j2zkrATCrj
OK
bdnoble (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
bdnoble (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
bdnoble XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ NO 0
bdnoble (unlocked) >>> wallet_get_info
{
"data_directory": "/home/ben/.BitSharesXTS/wallets",
"last_unlocked_scanned_block_number": 3829,
"last_locked_scanned_block_number": null,
"next_child_key_index": 2,
"default_transaction_priority_fee": {
"amount": 10000,
"asset_id": 0
},
"state": "open",
"locked": false,
"file": "/home/ben/.BitSharesXTS/wallets/bdnoble",
"scheduled_lock_time": "20140628T024833"
}
I imported mine using private keys.
Have you done wallet_account_balance <- to get the balance
or wallet_rescan_blockchain <- to "refresh"
-
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
Wow! How to creat my own asset like you? that's awesome!
wallet_asset_create <symbol> <asset_name> <issuer_name> [description] [data] [maximum_share_supply] [precision]
Can you explain [data] and [precision] or tell me where can I find description information? Thanks a lot
-
I know I am a little late to the party, but I built the latest with a clean .BitsharesXTS dir and tried to import my wallet.dat from PTS using wallet_import_bitcoin and it seemed like it worked but I don't have any XTS. Am I doing something wrong? Could I get some XTS to try to register as a delegate with? :)
importing PrWXTV7BMNJikS36HTJZzdUXKDc4QKjRbz
importing Pkw41LBvT8BEhwiW7osiKtf5yHRah7w8n7
importing 1KakKQR3bGMexAEEuxeiqcEU4yBEd1QAxo
importing 1E1GsFVnh2EAufuekKDsAsR2j2zkrATCrj
OK
bdnoble (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
bdnoble (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
bdnoble XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ NO 0
bdnoble (unlocked) >>> wallet_get_info
{
"data_directory": "/home/ben/.BitSharesXTS/wallets",
"last_unlocked_scanned_block_number": 3829,
"last_locked_scanned_block_number": null,
"next_child_key_index": 2,
"default_transaction_priority_fee": {
"amount": 10000,
"asset_id": 0
},
"state": "open",
"locked": false,
"file": "/home/ben/.BitSharesXTS/wallets/bdnoble",
"scheduled_lock_time": "20140628T024833"
}
I imported mine using private keys.
Have you done wallet_account_balance <- to get the balance
or wallet_rescan_blockchain <- to "refresh"
I did a rescan.
I actually couldn't figure out how to find my private keys from PTS. I did a dumpprivkey on my PTS qt wallet but it said it couldn't find my private key for my address or something like that. So that's why I tried to import the wallet.dat. Has anyone else tried that yet? Is it supposed to be working?
Sent from my iPhone using Tapatalk
-
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
Wow! How to creat my own asset like you? that's awesome!
wallet_asset_create <symbol> <asset_name> <issuer_name> [description] [data] [maximum_share_supply] [precision]
Can you explain [data] and [precision] or tell me where can I find description information? Thanks a lot
Creates a new user issued asset.
Parameters
symbol the ticker symbol for the new asset (asset_symbol, required)
asset_name the name of the asset (std::string, required)
issuer_name the name of the issuer of the asset (std::string, required)
description a description of the asset (std::string, optional, defaults to "")
data arbitrary data attached to the asset (json_variant, optional, defaults to null)
maximum_share_supply the maximum number of shares of the asset (int64_t, optional, defaults to 1000000000000000)
precision defines where the decimal should be displayed, must be a power of 10 (int64_t, optional, defaults to 1000000)
You can search any function in http://bitshares.org/resources/documentation/
-
I donot understand what you are doning, but I want to ask: Is there everythings is OK? Could we see the release in the summer?....lol
来自我的 M353 上的 Tapatalk
-
We are pleased with progress and release is imminent - as soon as all test results are acceptable.
im·mi·nent
ˈimənənt
adjective
1.
about to happen.
"they were in imminent danger of being swept away"
synonyms: impending, close (at hand), near, (fast) approaching, coming, forthcoming, on the way, in the offing, in the pipeline, on the horizon, in the air, just around the corner, coming down the pike, expected, anticipated, brewing, looming, ... :)
-
There are 5 pages of comments that I haven't caught up on, but I wanted to post an update on where we are:
1) Clock drift is causing some nodes to fail to validate blocks. Apparently it can drift by as much as 5 seconds or more per day and we only do NTP sync on launch. Blocks were failing because their time was 'in the future' and this would cause forks.
2) We found a bug where transactions on forks are not saved and thus we fail to switch to the fork. This would exasperate #1
3) If your client is the one with the bad clock then you can get stuck because once block is 'failed' it will never retry. This will leave you stuck until you re-sync.
We are preparing fixes for these issues now which should be relatively straight forward and should have it all resolved today.
-
We are pleased with progress and release is imminent - as soon as all test results are acceptable.
im·mi·nent
ˈimənənt
adjective
1.
about to happen.
"they were in imminent danger of being swept away"
synonyms: impending, close (at hand), near, (fast) approaching, coming, forthcoming, on the way, in the offing, in the pipeline, on the horizon, in the air, just around the corner, coming down the pike, expected, anticipated, brewing, looming, ... :)
+5%
haha ;)
and also the other products are coming soon as well ;D
-
+5%
-
thanks all, I have get many XTS/LOVE/HAP from you :)
10296.0 2014-06-16T08:05:00 clout alt 50.000000 XTS 0.000000 XTS e2c9cbc9
10339.0 2014-06-16T08:22:45 mauritso alt 10.000000 XTS 0.000000 XTS 37671f7e
10341.0 2014-06-16T08:23:15 mauritso alt 10.000000 LOVE 0.000000 XTS fe819ec6
10355.0 2014-06-16T08:30:45 betax alt 20.000000 XTS 0.000000 XTS 2ebd73be
10358.0 2014-06-16T08:32:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS d50ebe4c
10368.0 2014-06-16T08:35:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 136d44af
10384.0 2014-06-16T08:42:15 betax alt 100,000.000000 HAP 0.000000 XTS 851d86be
10511.0 2014-06-16T09:32:15 spartako alt some love 100.000000 LOVE 0.000000 XTS 870cd6e6
-
Can someone vote for my delegate?
alexxy
I'm running public node with ~30 connections (max connections set to 256) 79.173.81.171:8764
-
Can someone vote for my delegate?
alexxy
I'm running public node with ~30 connections (max connections set to 256) 79.173.81.171:8764
I tried but I think I finished my votes :(
-
There are 5 pages of comments that I haven't caught up on, but I wanted to post an update on where we are:
1) Clock drift is causing some nodes to fail to validate blocks. Apparently it can drift by as much as 5 seconds or more per day and we only do NTP sync on launch. Blocks were failing because their time was 'in the future' and this would cause forks.
2) We found a bug where transactions on forks are not saved and thus we fail to switch to the fork. This would exasperate #1
3) If your client is the one with the bad clock then you can get stuck because once block is 'failed' it will never retry. This will leave you stuck until you re-sync.
We are preparing fixes for these issues now which should be relatively straight forward and should have it all resolved today.
good to know.
-
There are 5 pages of comments that I haven't caught up on, but I wanted to post an update on where we are:
1) Clock drift is causing some nodes to fail to validate blocks. Apparently it can drift by as much as 5 seconds or more per day and we only do NTP sync on launch. Blocks were failing because their time was 'in the future' and this would cause forks.
2) We found a bug where transactions on forks are not saved and thus we fail to switch to the fork. This would exasperate #1
3) If your client is the one with the bad clock then you can get stuck because once block is 'failed' it will never retry. This will leave you stuck until you re-sync.
We are preparing fixes for these issues now which should be relatively straight forward and should have it all resolved today.
Looks promising! GJ & keep going.
-
Hi guys,
I am yet to be a delegate, need some votes "betax"
Thanks!
-
Can someone confirm the keyhotee import is working?
I can't get mine. I'm hoping its not because I've tried 100's of brain keys and no success. I may have just forgot :(
-
What does UNKNOWN mean
alexxy (unlocked) >>> wallet_account_transaction_history
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
pending 2014-06-11T07:49:15 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3d60360b
703.0 2014-06-13T08:12:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 231fcf83
10358.0 2014-06-16T08:32:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS d50ebe4c
10368.0 2014-06-16T08:35:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 136d44af
11281.0 2014-06-16T14:31:30 alexxy alexxy update alexxy 0.000000 XTS 0.010002 XTS 72976560
11282.0 2014-06-16T14:31:45 alexxy alexxy update alexxy as a delegate 0.000000 XTS 10.495702 XTS 2784c48b
11293.0 2014-06-16T14:35:45 spartako alexxy some votes :) 10.000000 XTS 0.000000 XTS ba8b2542
11294.0 2014-06-16T14:36:15 spartako alexxy and some love ;) 100.000000 LOVE 0.000000 XTS 11784510
-
Can someone confirm the keyhotee import is working?
I can't get mine. I'm hoping its not because I've tried 100's of brain keys and no success. I may have just forgot :(
Yes it works, at least i can import my keyhotee id
-
Can someone confirm the keyhotee import is working?
I can't get mine. I'm hoping its not because I've tried 100's of brain keys and no success. I may have just forgot :(
I also had some problems, didn't use middle name so put null in command but my brain id is very long with some special characters.
Seems that client can't read characters after "!" and returns error
Looking for some votes too ;)
wallet_set_delegate_trust_level dd-1 10
Can someone vote for my delegate?
alexxy
I'm running public node with ~30 connections (max connections set to 256) 79.173.81.171:8764
Hi guys,
I am yet to be a delegate, need some votes "betax"
Thanks!
you have mine
-
Can someone confirm the keyhotee import is working?
I can't get mine. I'm hoping its not because I've tried 100's of brain keys and no success. I may have just forgot :(
Yes it works, at least i can import my keyhotee id
How to import keyhotee id?
-
networker (unlocked) >>> wallet_account_register networker networker null true
20011 insufficient_funds: insufficient funds
{"required":"10.495701 XTS","available":"9.979998 XTS"}
th_a wallet.cpp:206 withdraw_to_transaction
Why now it need 10.49 XTS?
I don't know but I sent you an other XTS
11027.0 2014-06-16T12:56:15 spartako networker 1.000000 XTS 0.010000 XTS 4cf16afe
I can't get it and I think I am on a fork again.
networker (unlocked) >>> getinfo
{
"blockchain_head_block_num": 11007,
"blockchain_head_block_time": "20140616T124900",
"blockchain_head_block_time_rel": "2 hours old",
How to resync to the network and recover from this unnormal status?
-
networker (unlocked) >>> getinfo
{
"blockchain_head_block_num": 11007,
"blockchain_head_block_time": "20140616T124900",
"blockchain_head_block_time_rel": "2 hours old",
How to resync to the network and recover from this unnormal status?
Yes, I think you are in a fork, this is my state:
{
"blockchain_head_block_num": 11405,
"blockchain_head_block_time": "20140616T151645",
"blockchain_head_block_time_rel": "21 seconds old",
Stop the program, remove ~/.BitShares\ XTS/chain/ and restart
-
default (unlocked) >>> getinfo
{
"blockchain_head_block_num": 11407,
"blockchain_head_block_time": "20140616T151730",
"blockchain_head_block_time_rel": "8 seconds ago",
"blockchain_confirmation_requirement": 219,
"blockchain_average_delegate_participation": 64.796259185036746,
"network_num_connections": 8,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140616T151734",
"blockchain_random_seed": "028f7673a383773d410584af2841b95601970390",
"blockchain_shares": 10000391232056,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140616T054319",
"wallet_version": 100
-
We are pleased with progress and release is imminent - as soon as all test results are acceptable.
im·mi·nent
ˈimənənt
adjective
1.
about to happen.
"they were in imminent danger of being swept away"
synonyms: impending, close (at hand), near, (fast) approaching, coming, forthcoming, on the way, in the offing, in the pipeline, on the horizon, in the air, just around the corner, coming down the pike, expected, anticipated, brewing, looming, ... :)
good jobs for all! I think the team is really efficient and effective in this month.
it seems that the first version of BTSX could be released before August, though there are still a lot of important functions unrealized in this version.
And may I ask that before the end of this summer, will there be any other snapshots?
:)
-
We are pleased with progress and release is imminent - as soon as all test results are acceptable.
im·mi·nent
ˈimənənt
adjective
1.
about to happen.
"they were in imminent danger of being swept away"
synonyms: impending, close (at hand), near, (fast) approaching, coming, forthcoming, on the way, in the offing, in the pipeline, on the horizon, in the air, just around the corner, coming down the pike, expected, anticipated, brewing, looming, ... :)
good jobs for all! I think the team is really efficient and effective in this month.
it seems that the first version of BTSX could be released before August, though there are still a lot of important functions unrealized in this version.
And may I ask that before the end of this summer, will there be any other snapshots?
:)
Hopefully. :)
-
Have we tested delegate cheating part, like process a double spending? If this test run will decide the initial delegates, everyone will be honest and we miss the test about delegate cheating part.
Sent from my iPhone using Tapatalk
-
blockchain_market_list_bids LOVE XTS
I see people are playing with the bids...
[{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "0.1",
"quote_asset_id": 1,
"base_asset_id": 0
},
"owner": "XTS23zcpVE1MgRZZwEXKpbRZd6avmk32PvkR"
},
"state": {
"balance": 100000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "0.1",
"quote_asset_id": 1,
"base_asset_id": 0
},
"owner": "XTS3NhNgEQjUSqLYKsZsjUMAhdDgoLfw5emE"
},
"state": {
"balance": 1000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "0.1",
"quote_asset_id": 3,
"base_asset_id": 0
},
"owner": "XTS7UepfihWJHmX12x17w38wxodG3fyu9TBj"
},
"state": {
"balance": 100000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "0.1",
"quote_asset_id": 1,
"base_asset_id": 0
},
"owner": "XTS8CwnoEZJAXX382WSfbvW9iAohQ9jpFs29"
},
"state": {
"balance": 10000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "1.",
"quote_asset_id": 3,
"base_asset_id": 0
},
"owner": "XTSCo722mSgFUESujZKKk4tKEE9iRiA2ju2"
},
"state": {
"balance": 10000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "1.",
"quote_asset_id": 1,
"base_asset_id": 0
},
"owner": "XTS5UrcvC7x65mTfgahtugtzjLYa89AWcNQv"
},
"state": {
"balance": 10000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "1.",
"quote_asset_id": 1,
"base_asset_id": 0
},
"owner": "XTS6fZoXku4WrgMAg4bn9Wg1vYbvK7VJYrVQ"
},
"state": {
"balance": 10000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "1.",
"quote_asset_id": 2,
"base_asset_id": 0
},
"owner": "XTS8cuLFCXDuf2fUmPpH28e37paHg9yxRZyS"
},
"state": {
"balance": 10000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "100.",
"quote_asset_id": 3,
"base_asset_id": 0
},
"owner": "XTS6B31qfyap37GGecioTCUUbgj2vKH38zd4"
},
"state": {
"balance": 1000000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "100.",
"quote_asset_id": 1,
"base_asset_id": 0
},
"owner": "XTSLvdkwYFrUpUA1bYa3DD9HxsvndmQD1kvV"
},
"state": {
"balance": 1000000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "1000.",
"quote_asset_id": 3,
"base_asset_id": 2
},
"owner": "XTSG3opSXiRbRxuWZUv3kSVDZzrFq5SMAwkt"
},
"state": {
"balance": 50000000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "1000.",
"quote_asset_id": 3,
"base_asset_id": 1
},
"owner": "XTSNJ3T2GiMLkvfZ7d7i4E3XNAAyco2Vc5sB"
},
"state": {
"balance": 100000000000,
"delegate_id": 0
}
},{
"type": "bid_order",
"market_index": {
"order_price": {
"ratio": "50000.",
"quote_asset_id": 3,
"base_asset_id": 0
},
"owner": "XTS6kDM29yaoQTiSMetqaVJsFqkiHMp1wAWj"
},
"state": {
"balance": 2500000000000,
"delegate_id": 0
}
}
]
As you may have noticed all you can do is place bids / cancel bids. No asks or shorts right now.
-
having problems with latest git pull
~/bitshares_toolkit# git submodule update
fatal: reference is not a tree: 4b095728a9cf4cd696ba2d926268e3cbd77c5b4a
Unable to checkout '4b095728a9cf4cd696ba2d926268e3cbd77c5b4a' in submodule path 'vendor'
-
the latest code can't compile by vs2013.
bitshares_toolkit\libraries\fc\include\fc/network/ntp.hpp(23): error C2039: “unique_ptr”: not the member function of “std”
-
I am not sure if my node is tracking the main blockchain or a fork.
>>> get_info
{
"blockchain_head_block_num": 10209,
"blockchain_head_block_time": "20140616T153000",
"blockchain_head_block_time_rel": "24 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 28.877642155403393,
"network_num_connections": 8,
Is there a way to check?
-
I am not sure if my node is tracking the main blockchain or a fork.
>>> get_info
{
"blockchain_head_block_num": 10209,
"blockchain_head_block_time": "20140616T153000",
"blockchain_head_block_time_rel": "24 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 28.877642155403393,
"network_num_connections": 8,
Is there a way to check?
You can check: "blockchain_head_block_time_rel": "24 minutes old"
So you are on a fork.
Quite curious why you are so consistently forking. We will have more diagnostic info available soon. BM is fixing the last known forking causes now, after that we will examine your case more thoroughly.
Thanks for your help so far.
-
having problems with latest git pull
~/bitshares_toolkit# git submodule update
fatal: reference is not a tree: 4b095728a9cf4cd696ba2d926268e3cbd77c5b4a
Unable to checkout '4b095728a9cf4cd696ba2d926268e3cbd77c5b4a' in submodule path 'vendor'
Fixed in latest
the latest code can't compile by vs2013.
bitshares_toolkit\libraries\fc\include\fc/network/ntp.hpp(23): error C2039: “unique_ptr”: not the member function of “std”
git submodule update?
-
with "wallet_import_keyhotee"
is the <keyhoteeid> case sensitive?
I noticed that in "blockchain_list_registered_accounts" my keyhotee ID is all lowercase but that is not how i set it up.
Which should i use with the import or does it matter?
-
with "wallet_import_keyhotee"
is the <keyhoteeid> case sensitive?
I noticed that in "blockchain_list_registered_accounts" my keyhotee ID is all lowercase but that is not how i set it up.
Which should i use with the import or does it matter?
Enter it as you registered it
-
Whats wrong with current test networks in latest git build? It cannot sync after
{
"blockchain_head_block_num": 10252,
"blockchain_head_block_time": "20140616T161845",
"blockchain_head_block_time_rel": "2 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 28.429073856975382,
Seems we have 2 major forks =\
-
Whats wrong with current test networks in latest git build? It cannot sync after
{
"blockchain_head_block_num": 10252,
"blockchain_head_block_time": "20140616T161845",
"blockchain_head_block_time_rel": "2 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 28.429073856975382,
Seems we have 2 major forks =\
I am on the block 10256.
-
I know I am a little late to the party, but I built the latest with a clean .BitsharesXTS dir and tried to import my wallet.dat from PTS using wallet_import_bitcoin and it seemed like it worked but I don't have any XTS. Am I doing something wrong? Could I get some XTS to try to register as a delegate with? :)
importing PrWXTV7BMNJikS36HTJZzdUXKDc4QKjRbz
importing Pkw41LBvT8BEhwiW7osiKtf5yHRah7w8n7
importing 1KakKQR3bGMexAEEuxeiqcEU4yBEd1QAxo
importing 1E1GsFVnh2EAufuekKDsAsR2j2zkrATCrj
OK
bdnoble (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
bdnoble (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
bdnoble XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ NO 0
bdnoble (unlocked) >>> wallet_get_info
{
"data_directory": "/home/ben/.BitSharesXTS/wallets",
"last_unlocked_scanned_block_number": 3829,
"last_locked_scanned_block_number": null,
"next_child_key_index": 2,
"default_transaction_priority_fee": {
"amount": 10000,
"asset_id": 0
},
"state": "open",
"locked": false,
"file": "/home/ben/.BitSharesXTS/wallets/bdnoble",
"scheduled_lock_time": "20140628T024833"
}
I imported mine using private keys.
Have you done wallet_account_balance <- to get the balance
or wallet_rescan_blockchain <- to "refresh"
I did a rescan.
I actually couldn't figure out how to find my private keys from PTS. I did a dumpprivkey on my PTS qt wallet but it said it couldn't find my private key for my address or something like that. So that's why I tried to import the wallet.dat. Has anyone else tried that yet? Is it supposed to be working?
Sent from my iPhone using Tapatalk
Any word on this? Is there some special way to import from PTS wallet.dat that I haven't tried? Could anyone send me some XTS to play with until I figure this out?
XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ
Sent from my iPhone using Tapatalk
-
Whats wrong with current test networks in latest git build? It cannot sync after
{
"blockchain_head_block_num": 10252,
"blockchain_head_block_time": "20140616T161845",
"blockchain_head_block_time_rel": "2 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 28.429073856975382,
Seems we have 2 major forks =\
Looks fine with me:
"blockchain_head_block_num": 10263,
"blockchain_head_block_time": "20140616T171645",
-
Whats wrong with current test networks in latest git build? It cannot sync after
{
"blockchain_head_block_num": 10252,
"blockchain_head_block_time": "20140616T161845",
"blockchain_head_block_time_rel": "2 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 28.429073856975382,
Seems we have 2 major forks =\
Looks fine with me:
"blockchain_head_block_num": 10263,
"blockchain_head_block_time": "20140616T171645",
"blockchain_head_block_num": 11738,
"blockchain_head_block_time": "20140616T172045",
"blockchain_head_block_time_rel": "12 seconds old",
"blockchain_confirmation_requirement": 212,
"blockchain_average_delegate_participation": 66.076294277929151,
-
Looks like latest build, deletion of ~/.BitsharesXTS/chain and restart got me onto main blockchain again.
>>> get_info
{
"blockchain_head_block_num": 11740,
"blockchain_head_block_time": "20140616T172130",
"blockchain_head_block_time_rel": "7 seconds old",
"blockchain_confirmation_requirement": 212,
"blockchain_average_delegate_participation": 66.076294277929151,
"network_num_connections": 7,
-
Any word on this? Is there some special way to import from PTS wallet.dat that I haven't tried? Could anyone send me some XTS to play with until I figure this out?
XTS5UJbjAws1os3J8eX2H2HEp3iTs5a2CsqJwb2w23cZvxqjd6vjZ
Sent from my iPhone using Tapatalk
sent you some LOVE :)
-
what does this mean?
I am disconnecting peer 207.12.89.119:55968 for reason: You sent me a sync block that I didn't ask for
--- there are now 7 active connections to the p2p network
I am disconnecting peer 106.185.26.162:8764 for reason: You sent me a sync block that I didn't ask for
--- there are now 6 active connections to the p2p network
-
Are there any howto about running web wallet?
-
what does this mean?
I am disconnecting peer 207.12.89.119:55968 for reason: You sent me a sync block that I didn't ask for
--- there are now 7 active connections to the p2p network
I am disconnecting peer 106.185.26.162:8764 for reason: You sent me a sync block that I didn't ask for
--- there are now 6 active connections to the p2p network
The way the P2P code works is that no client should ever send a block that was not requested. If a client receives a block it did not request then it shuts down the peer (presumed flooding attempt). On some older builds we had a bug that has since been fixed where the client forgot that it had requested something.
-
Whats wrong with current test networks in latest git build? It cannot sync after
{
"blockchain_head_block_num": 10252,
"blockchain_head_block_time": "20140616T161845",
"blockchain_head_block_time_rel": "2 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 28.429073856975382,
Seems we have 2 major forks =\
I am on the block 10256.
"blockchain_head_block_num": 11958,
"blockchain_head_block_time": "20140616T184500",
If you haven't updated recently then your client will not be able to switch to the correct fork when it tries without deleting the chain (unless there were no transactions during the fork).
We have fixed several significant issues today so I encourage everyone to update.
-
Is there an alternative way to check the brainkey on keyhotee ID.
I'm convinced, of the 200 iterations of my brainkey at least one of them is correct but it has not imported into this wallet.
-
If you haven't updated recently then your client will not be able to switch to the correct fork when it tries without deleting the chain (unless there were no transactions during the fork).
We have fixed several significant issues today so I encourage everyone to update.
Why dont you create a separate thread where you state the recommended git revision(s).
This could avoid compile error(s) and will keep everyone on same version(s) (hopefully).
-
Seems my delegate node is not producing blocks.. It has been showing
"blocks_produced": 7,
for several hours
get_info
{
"blockchain_head_block_num": 12019,
"blockchain_head_block_time": "20140616T190730",
"blockchain_head_block_time_rel": "2 seconds old",
"blockchain_confirmation_requirement": 223,
"blockchain_average_delegate_participation": 66.529492455418378,
"network_num_connections": 11,
..
--- there are now 10 active connections to the p2p network
default (unlocked)
>>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83109630849,
"votes_against": 0,
"blocks_produced": 7,
"blocks_missed": 125,
"pay_balance": 576553,
"next_secret_hash": "a2d0bdf2ef998a9efb0821786b243d146c7a075b",
"last_block_num_produced": 9758
},
-
Are there any howto about running web wallet?
just follow the README.md on https://github.com/BitShares/web_wallet
-
Has anyone managed to get the client to compile on a different linux distribution?
On both OpenSuse and Gentoo I get stuck in the same place, apparently because of a problem in time.hpp/cpp. I've quoted the error message below. Any clues on how to get beyond this point would be appreciated, because I'm personally not a big fan of Ubuntu.
[ 95%] Building CXX object libraries/client/CMakeFiles/bts_client.dir/client.cpp.o
/home/joey/bitshares_toolkit/libraries/client/client.cpp: In member function 'virtual fc::variant_object bts::client::detail::client_impl::get_info() const':
/home/joey/bitshares_toolkit/libraries/client/client.cpp:1954:149: error: no matching function for call to 'get_approximate_relative_time_string(fc::time_point_sec, fc::time_point_sec, const char [5])'
info["blockchain_head_block_time_rel"] = fc::get_approximate_relative_time_string(_chain_db->now(), bts::blockchain::now(), " old");
^
/home/joey/bitshares_toolkit/libraries/client/client.cpp:1954:149: note: candidates are:
In file included from /home/joey/bitshares_toolkit/libraries/fc/include/fc/log/logger.hpp:3:0,
from /home/joey/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:6,
from /home/joey/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/types.hpp:6,
from /home/joey/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/chain_database.hpp:2,
from /home/joey/bitshares_toolkit/libraries/client/include/bts/client/client.hpp:2,
from /home/joey/bitshares_toolkit/libraries/client/client.cpp:1:
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:120:10: note: fc::string fc::get_approximate_relative_time_string(const fc::time_point_sec&)
string get_approximate_relative_time_string(const time_point_sec& event_time);
^
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:120:10: note: candidate expects 1 argument, 3 provided
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:121:10: note: fc::string fc::get_approximate_relative_time_string(const fc::time_point&)
string get_approximate_relative_time_string(const time_point& event_time);
^
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:121:10: note: candidate expects 1 argument, 3 provided
libraries/client/CMakeFiles/bts_client.dir/build.make:57: recipe for target 'libraries/client/CMakeFiles/bts_client.dir/client.cpp.o' failed
make[2]: *** [libraries/client/CMakeFiles/bts_client.dir/client.cpp.o] Error 1
CMakeFiles/Makefile2:685: recipe for target 'libraries/client/CMakeFiles/bts_client.dir/all' failed
make[1]: *** [libraries/client/CMakeFiles/bts_client.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2
-
Has anyone managed to get the client to compile on a different linux distribution?
On both OpenSuse and Gentoo I get stuck in the same place, apparently because of a problem in time.hpp/cpp. I've quoted the error message below. Any clues on how to get beyond this point would be appreciated, because I'm personally not a big fan of Ubuntu.
[ 95%] Building CXX object libraries/client/CMakeFiles/bts_client.dir/client.cpp.o
/home/joey/bitshares_toolkit/libraries/client/client.cpp: In member function 'virtual fc::variant_object bts::client::detail::client_impl::get_info() const':
/home/joey/bitshares_toolkit/libraries/client/client.cpp:1954:149: error: no matching function for call to 'get_approximate_relative_time_string(fc::time_point_sec, fc::time_point_sec, const char [5])'
info["blockchain_head_block_time_rel"] = fc::get_approximate_relative_time_string(_chain_db->now(), bts::blockchain::now(), " old");
^
/home/joey/bitshares_toolkit/libraries/client/client.cpp:1954:149: note: candidates are:
In file included from /home/joey/bitshares_toolkit/libraries/fc/include/fc/log/logger.hpp:3:0,
from /home/joey/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:6,
from /home/joey/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/types.hpp:6,
from /home/joey/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/chain_database.hpp:2,
from /home/joey/bitshares_toolkit/libraries/client/include/bts/client/client.hpp:2,
from /home/joey/bitshares_toolkit/libraries/client/client.cpp:1:
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:120:10: note: fc::string fc::get_approximate_relative_time_string(const fc::time_point_sec&)
string get_approximate_relative_time_string(const time_point_sec& event_time);
^
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:120:10: note: candidate expects 1 argument, 3 provided
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:121:10: note: fc::string fc::get_approximate_relative_time_string(const fc::time_point&)
string get_approximate_relative_time_string(const time_point& event_time);
^
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:121:10: note: candidate expects 1 argument, 3 provided
libraries/client/CMakeFiles/bts_client.dir/build.make:57: recipe for target 'libraries/client/CMakeFiles/bts_client.dir/client.cpp.o' failed
make[2]: *** [libraries/client/CMakeFiles/bts_client.dir/client.cpp.o] Error 1
CMakeFiles/Makefile2:685: recipe for target 'libraries/client/CMakeFiles/bts_client.dir/all' failed
make[1]: *** [libraries/client/CMakeFiles/bts_client.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2
git submodule update ... your fc branch is out of date.
-
Good news, we appear to have solved the hang on block 173 issue (stack overflow due to default stack size chosen by boost::context being too small).
Those of you who are lucky enough to experience this particular bug can checkout the latest (be sure to do submodule update) and you should be able to get past block 173.
-
Still no blocks produced by my delegate node.. It is stuck on
"blocks_produced": 7,
>>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83109630849,
"votes_against": 0,
"blocks_produced": 7,
"blocks_missed": 130,
"pay_balance": 576553,
"next_secret_hash": "a2d0bdf2ef998a9efb0821786b243d146c7a075b",
"last_block_num_produced": 9758
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 12387,
"blockchain_head_block_time": "20140616T212245",
"blockchain_head_block_time_rel": "2 seconds old",
"blockchain_confirmation_requirement": 201,
"blockchain_average_delegate_participation": 66.988950276243088,
"network_num_connections": 10,
>>> about
{
"bitshares_toolkit_revision": "cc3d866a984c0117932ed407a4183bab4e69cc10",
"bitshares_toolkit_revision_age": "5 hours ago",
"fc_revision": "689848432106a52c9c1656611727745ba8a5ac0d",
"fc_revision_age": "5 hours ago",
"compile_date": "compiled on Jun 16 2014 at 18:11:46"
-
There are 5 pages of comments that I haven't caught up on, but I wanted to post an update on where we are:
1) Clock drift is causing some nodes to fail to validate blocks. Apparently it can drift by as much as 5 seconds or more per day and we only do NTP sync on launch. Blocks were failing because their time was 'in the future' and this would cause forks.
2) We found a bug where transactions on forks are not saved and thus we fail to switch to the fork. This would exasperate #1
3) If your client is the one with the bad clock then you can get stuck because once block is 'failed' it will never retry. This will leave you stuck until you re-sync.
We are preparing fixes for these issues now which should be relatively straight forward and should have it all resolved today.
woderfull
来自我的 HUAWEI P7-L00 上的 Tapatalk
-
Still no blocks produced by my delegate node.. It is stuck on
"blocks_produced": 7,
>>> blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83109630849,
"votes_against": 0,
"blocks_produced": 7,
"blocks_missed": 130,
"pay_balance": 576553,
"next_secret_hash": "a2d0bdf2ef998a9efb0821786b243d146c7a075b",
"last_block_num_produced": 9758
},
"registration_date": "20140613T030845",
"last_update": "20140613T031130",
"meta_data": null
}
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 12387,
"blockchain_head_block_time": "20140616T212245",
"blockchain_head_block_time_rel": "2 seconds old",
"blockchain_confirmation_requirement": 201,
"blockchain_average_delegate_participation": 66.988950276243088,
"network_num_connections": 10,
>>> about
{
"bitshares_toolkit_revision": "cc3d866a984c0117932ed407a4183bab4e69cc10",
"bitshares_toolkit_revision_age": "5 hours ago",
"fc_revision": "689848432106a52c9c1656611727745ba8a5ac0d",
"fc_revision_age": "5 hours ago",
"compile_date": "compiled on Jun 16 2014 at 18:11:46"
list_errors?
-
Something stange.
I generated a list of 162 different brainkey combinations and pasted the whole thing into the client.
something like the following:
wallet_import_keyhotee John Middle Lastname "My secret brainkey challenge." EasyBTC
wallet_import_keyhotee John Middle Lastname "My secret 1brainkey challenge." EasyBTC
wallet_import_keyhotee John Middle Lastname "My secret 2brainkey challenge." EasyBTC
wallet_import_keyhotee John Middle Lastname "My secret 3brainkey challenge." EasyBTC
wallet_import_keyhotee John Middle Lastname "My secret 4brainkey challenge." EasyBTC
... etc.
When it was done i got this
xeldal-w (unlocked) >>> wallet_list_receive_accounts
--- there are now 12 active connections to the p2p network
NAME (* delegate) KEY REGISTERED TRUST LEVEL
xeldal-del XTS8YWXDVj8qGtyJvNYGXENqgVZEnrvFY7nUfegi1VrSyZCtgp5dD 2014-06-16T02:00:30 0
easybtcchallenge. XTS8WoPWWvktGEcHXBiSonjkupzBcv69ruQzWeiebcLVFQSgMM1Yf NO 0
init-delegate-45 * XTS5ttrjXKJPiWYm6EL7LAYRWV4GWnAaBPjGvkydy86yaKQdxTcHg 2014-06-01T00:00:00 0
init-delegate-44 * XTS8QLeHvaYQqFRdTP46EZq4GVdvj65Fp9wbKBGhBx5kvDnNFTDtM 2014-06-01T00:00:00 0
init-delegate-43 * XTS6whTVdWVb4KFvBDfKeawRjWPa6rsG5etsMvmg1MuybWhpVTf2u 2014-06-01T00:00:00 0
init-delegate-42 * XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit 2014-06-01T00:00:00 0
No idea where that came from. I certainly didn't create it.
At first I thought maybe I had found my Keyhotee Key and the name just got fuddled but unfortunately the key is different.
At any rate I'm sure its not supposed to do whatever it did.
-
Second issue is known.
Regarding keyhotee, I just wouldn't worry about it - the whole thing is really screwy and we need to figure out what we're doing about that
-
list_errors?
Unfortunately my terminal screen gets cut off
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140616T033824.967829"
},
"format": "I am disconnecting peer 107.170.170.214:39219 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140616T033824.971040",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140616T033824.971038"
},
"format": "I am disconnecting peer 128.199.180.112:58344 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140616T033824.972200",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 818,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140616T033824.972198"
},
"format": "I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
],[
"20140616T173520.297257",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "node.cpp",
"line": 2046,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140616T173839.826219"
},
"format": "You sent me a sync block that I didn't ask for, block_id: ${block_id}",
"data": {
"block_id": "b6bab87fac3fec2519020c0202c58abbdd2acdb4"
}
}
]
}
]
]
-
Oops, sorry about forgetting to update the submodules.
Still can't manage to compile a working binary outside of ubuntu however, I'm now stuck on a linking error with an undefined reference to 'main' with bitshares_client_tests and deterministic_signature_test.
Any steps I could take to figure out what's going wrong there?
-
I made a mistake when create my dream.
So I just lose my dreak :P
default (unlocked) >>> wallet_asset_create DREAM Dream alt "I have a dream" 100000000000 1000000
default (unlocked) >>> blockchain_list_registered_assets
ID SYMBOL NAME DESCRIPTION CURRENT_SUPPLY MAX_SUPPLY FEES COLLECTED REGISTERED
8 APPLE Dream I have a dream 0 0.0001 02014-06-17T00:24:45
5 DREAM Dream I have a dream 0 1 02014-06-17T00:20:30
2 FREE Freedom 100999999 1000000000 02014-06-16T08:32:00
3 HAP Happiness 100000000 1000000000 02014-06-16T08:35:15
6 HELLO Dream I have a dream 0 1 02014-06-17T00:23:00
1 LOVE LOVE 100000 1000000000 02014-06-13T08:12:15
9 ORA Dream I have a dream 999 1000 02014-06-17T00:26:15
4 PPL puppie_LOVE Right back at ya 170000000 1000000000 02014-06-16T19:03:00
0 XTS BitShares XTS Stake in future BitShares X ch... 10000454.92553 1000000000 339.9027932014-06-01T00:00:00
-
Can I buy you a drink? 8)
delegate (unlocked) >>> wallet_transfer 10000 DRINK delegate-alt 0dayzh "buy you a drink"
10 assert_exception: Assert Exception
is_valid_account_name( account_name ):
{}
th_a wallet.cpp:2594 is_valid_account
{"real_amount_to_transfer":10000,"amount_to_transfer_symbol":"DRINK","from_account_name":"delegate-alt","to_account_name":"0dayzh","memo_message":"buy you a drink"}
th_a wallet.cpp:1599 transfer_asset
{}
th_a common_api_client.cpp:482 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:570 execute_command
-
Can I buy you a drink? 8)
delegate (unlocked) >>> wallet_transfer 10000 DRINK delegate-alt 0dayzh "buy you a drink"
10 assert_exception: Assert Exception
is_valid_account_name( account_name ):
{}
th_a wallet.cpp:2594 is_valid_account
{"real_amount_to_transfer":10000,"amount_to_transfer_symbol":"DRINK","from_account_name":"delegate-alt","to_account_name":"0dayzh","memo_message":"buy you a drink"}
th_a wallet.cpp:1599 transfer_asset
{}
th_a common_api_client.cpp:482 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:570 execute_command
names cannot start with numbers, those shouldn't even be in genesis block
-
run list_errors and got following error log,not sure if it is just a warning or an exception
list_errors
[[
"20140617T001800.760239",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "wallet.cpp",
"line": 1043,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T001800.747660"
},
"format": "key.valid(): ",
"data": {}
},{
"context": {
"level": "warn",
"file": "wallet.cpp",
"line": 1046,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T001800.759609"
},
"format": "",
"data": {
"addr": "XTSJBUPebvzdAsmhxvzvqRdwKtTKg7Y9bvX5"
}
},{
"context": {
"level": "warn",
"file": "wallet.cpp",
"line": 1148,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T001800.760134"
},
"format": "",
"data": {
"header": {
"previous": "51ff0d6880749851c4c1ba3eb9a64d5e7d4e11e4",
"block_num": 12902,
"fee_rate": 1000,
"delegate_pay_rate": 90909,
"timestamp": "20140617T001800",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "0000000000000000000000000000000000000000",
"previous_secret": "0000000000000000000000000000000000000000",
"delegate_signature": "0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
}
}
}
]
}
]
]
-
Can I buy you a drink? 8)
delegate (unlocked) >>> wallet_transfer 10000 DRINK delegate-alt 0dayzh "buy you a drink"
10 assert_exception: Assert Exception
is_valid_account_name( account_name ):
{}
th_a wallet.cpp:2594 is_valid_account
{"real_amount_to_transfer":10000,"amount_to_transfer_symbol":"DRINK","from_account_name":"delegate-alt","to_account_name":"0dayzh","memo_message":"buy you a drink"}
th_a wallet.cpp:1599 transfer_asset
{}
th_a common_api_client.cpp:482 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:570 execute_command
names cannot start with numbers, those shouldn't even be in genesis block
I agree you.
-
Good news, we appear to have solved the hang on block 173 issue (stack overflow due to default stack size chosen by boost::context being too small).
Those of you who are lucky enough to experience this particular bug can checkout the latest (be sure to do submodule update) and you should be able to get past block 173.
Good job.
It work well now.
-
networker (unlocked) >>> getinfo
{
"blockchain_head_block_num": 11007,
"blockchain_head_block_time": "20140616T124900",
"blockchain_head_block_time_rel": "2 hours old",
How to resync to the network and recover from this unnormal status?
Yes, I think you are in a fork, this is my state:
{
"blockchain_head_block_num": 11405,
"blockchain_head_block_time": "20140616T151645",
"blockchain_head_block_time_rel": "21 seconds old",
Stop the program, remove ~/.BitShares\ XTS/chain/ and restart
It's ok now.
networker (unlocked) >>> blockchain_get_account_record networker
{
"id": 332,
"name": "networker",
"public_data": null,
"owner_key": "XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m",
"active_key_history": [[
"20140616T124900",
"XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m"
]
],
"delegate_info": null,
"registration_date": "20140616T124900",
"last_update": "20140616T124900",
"meta_data": null
}
Can I become a real delegate for testing block produce?
-
why some transactions from UNKNOWN?
delegate (unlocked) >>> wallet_account_transaction_history
.....
13288.0 2014-06-17T02:27:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 30ee8dad
delegate (unlocked) >>> blockchain_get_transaction 30ee8dad
{
"trx": {
"expiration": null,
"delegate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTSHswxSb1yoHgyoK3u7SqLUnHbkMRKBFgAk",
"amount": 10000000,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTS82KFS55P7RxQT2yGaHjhKNEqs9b8PuYSN",
"amount": 495709,
"claim_input_data": ""
}
},{
"type": "create_asset_op_type",
"data": {
"symbol": "POW",
"name": "power",
"description": "Power Coin",
"public_data": 100000000000,
"issuer_account_id": 332,
"maximum_share_supply": 1000000,
"precision": 1000000
}
}
],
"signatures": [
"20c92066273109a6c3c2b424f97cabd0e771b9dbd39db0d356a8f8796d201fdf9f8fd25fc6e83517bb4d43e24d38c19cf6e59404cd49edf85893df743cfec69ca9",
"1f2a2e085730d3cd6600b5cbd2a0e57816eed9a05e4903d7b1c7bade49c2d1e29bf1d9a11f2cc84cadc06360f7152446464ba0d09ae9c547295760ddbb0dc208e1",
"1f4a276262d8a90bc3d90bd5f6561474a1f2091a2facb46af698005073826b998b15e5d499fc7bf5c363d6ebb9369ca6d111161454ee01e959bf0b7a44bab2563e"
]
},
"signed_keys": [
"XTSKnJ3GsgVzcKnQUDUX3bZjFrR8cpz4Hgfp",
"XTSC3Rrm5HHMmjJJpvXf5owhUvchPZduDXJ1",
"XTSJ1uVkKwj6opxn1XpHtSH2Ku1B5gRRutbS",
"XTSPAdo1Fx1JTuo438oKJxKbDdJXGjQMCQdJ",
"XTSGfFUDNNT46A6v7uHU4nsrykAJpCtxo52M",
"XTS4Akzyo6tNUbgdemtrpYaLwSxjqNctxRaM",
"XTSCtGKAhg6pDbigyPf7EpapEkgBHXfeupDX",
"XTSDJizuC5nqRDGYi5j2vChi9mYeaV8kxPhw",
"XTSDbE5sTA2rGycqst17EXqUJ2nZswNnMY9M",
"XTS2X2aCdRJX1HTGJ3JTZi7iJfm8fcaqhb17",
"XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj",
"XTSEGJzmcJsCmbKw4Goi8VBy5xK9HRtUvtd1",
"XTS44N71Gpanrwm2ZAeBXJZ4S9p8nfYgzwAM",
"XTSCjRYC1frZKt2edjheESDvrKsiLkMHTCH3",
"XTS3mCdpG8RQ2uKRwAL36dfmE6UPynM4596f"
],
"validation_error": null,
"required_deposits": [],
"provided_deposits": [],
"deposits": [],
"withdraws": [[
0,{
"amount": 10495709,
"asset_id": 0
}
]
],
"balance": [[
0,
10495709
]
],
"net_delegate_votes": [[
304,{
"votes_for": -10000000,
"votes_against": 0
}
],[
314,{
"votes_for": -495709,
"votes_against": 0
}
]
],
"chain_location": {
"block_num": 13288,
"trx_num": 0
}
}
-
Second issue is known.
Regarding keyhotee, I just wouldn't worry about it - the whole thing is really screwy and we need to figure out what we're doing about that
What if my local account name is the same as Keyhotee id?
For example , I creat an account named 'networker' , and my Keyhotee id is 'networker' too.
-
Still not producing any blocks.. after 7
blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83109630849,
"votes_against": 0,
"blocks_produced": 7,
"blocks_missed": 145,
>>> get_info
{
"blockchain_head_block_num": 13427,
"blockchain_head_block_time": "20140617T031615",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 8,
"blockchain_average_delegate_participation": 73.652239939255878,
"network_num_connections": 9,
>>> about
{
"bitshares_toolkit_revision": "c345f294b5bdca77f1e6a45cc0b7ae86477e2e5b",
"bitshares_toolkit_revision_age": "4 hours ago",
"fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
"fc_revision_age": "4 hours ago",
"compile_date": "compiled on Jun 17 2014 at 02:16:5
list_errors
..
"level": "warn",
"file": "chain_database.cpp",
"line": 1069,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T024332.916702"
},
"format": "",
"data": {
"block_data": {
"previous": "4ade36992ec3209214b0fc91eb67ca0677186748",
"block_num": 13349,
"fee_rate": 1000,
"delegate_pay_rate": 91803,
"timestamp": "20140617T024645",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "447c7dfd98fbd471a93113ef6ce23b63ea2172f9",
"previous_secret": "31fee77caf17df77620ba7067cff2c652beb7b36",
"delegate_signature": "1fb0a852e7e463c3bea50eb8fc4e07cc1ad325db031a10b16a24f278e1e32b9ea1ad945d7a5bc6b950b5722e158aa88b511487e89bd91549e8790b1da39f806ea3",
"user_transactions": []
}
}
},{
"context": {
"level": "warn",
"file": "client.cpp",
"line": 550,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T024332.916777"
},
"format": "Error pushing block ${block_number} - ${block_id}",
"data": {
"block_id": "73142597a754b26aac370ff1ebffa9ea98351592",
"block_number": 13349,
"block": {
"previous": "4ade36992ec3209214b0fc91eb67ca0677186748",
"block_num": 13349,
"fee_rate": 1000,
"delegate_pay_rate": 91803,
"timestamp": "20140617T024645",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "447c7dfd98fbd471a93113ef6ce23b63ea2172f9",
"previous_secret": "31fee77caf17df77620ba7067cff2c652beb7b36",
"delegate_signature": "1fb0a852e7e463c3bea50eb8fc4e07cc1ad325db031a10b16a24f278e1e32b9ea1ad945d7a5bc6b950b5722e158aa88b511487e89bd91549e8790b1da39f806ea3",
"user_transactions": []
}
}
}
]
}
],[
"20140617T024332.917766",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 848,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T024332.917764"
},
"format": "I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
]
]
-
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
I created my own asset 'POWER'
,{
"id": 11,
"symbol": "POW",
"name": "power",
"description": "Power Coin",
"public_data": 100000000000,
"issuer_account_id": 332,
"precision": 1000000,
"current_share_supply": 0,
"maximum_share_supply": 1000000,
"collected_fees": 0,
"registration_date": "20140617T022715"
},{
How can I send some to you? I used
networker (unlocked) >>> wallet_transfer
amount_to_transfer: 10000
asset_symbol: POW
from_account_name: networker
to_account_name: betax
20011 insufficient_funds: insufficient funds
{"required":"10,000.000000 POW","available":"0.000000 POW"}
th_a wallet.cpp:206 withdraw_to_transaction
{"amount":10000000000,"asset_id":11,"from_account_address":"XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj","trx":{"expiration":null,"delegate_id":null,"operations":[],"signatures":[]},"required_signatures":[]}
th_a wallet.cpp:207 withdraw_to_transaction
{"real_amount_to_transfer":10000,"amount_to_transfer_symbol":"POW","from_account_name":"networker","to_account_name":"betax","memo_message":""}
th_a wallet.cpp:1599 transfer_asset
{}
th_a common_api_client.cpp:472 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:547 execute_command
What does this mean? Why the fund is insufficient?
-
Do not produce any block for 12 min or I am on the forked chain
info
{
"blockchain_head_block_num": 13112,
"blockchain_head_block_time": "20140617T034415",
"blockchain_head_block_time_rel": "12 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 50.259067357512954,
"network_num_connections": 7,
"ntp_time": "20140617T035550.088785",
"ntp_error_seconds": -0.010285000000000001,
"wallet_unlocked_seconds_remaining": 9988922,
"wallet_next_block_production_time": "20140617T040100",
"wallet_seconds_until_next_block_production": 310,
"wallet_local_time": "20140617T035550",
"blockchain_random_seed": "7e1a30ee30277f7cd7c090f8487b584bf5624f52",
"blockchain_shares": 10000458377029,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141010T183752",
"wallet_version": 100
}
-
Do not produce any block for 12 min or I am on the forked chain
info
{
"blockchain_head_block_num": 13112,
"blockchain_head_block_time": "20140617T034415",
"blockchain_head_block_time_rel": "12 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 50.259067357512954,
"network_num_connections": 7,
"ntp_time": "20140617T035550.088785",
"ntp_error_seconds": -0.010285000000000001,
"wallet_unlocked_seconds_remaining": 9988922,
"wallet_next_block_production_time": "20140617T040100",
"wallet_seconds_until_next_block_production": 310,
"wallet_local_time": "20140617T035550",
"blockchain_random_seed": "7e1a30ee30277f7cd7c090f8487b584bf5624f52",
"blockchain_shares": 10000458377029,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141010T183752",
"wallet_version": 100
}
Here is mine:
emski (unlocked) >>> get_info
{
"blockchain_head_block_num": 13543,
"blockchain_head_block_time": "20140617T035900",
"blockchain_head_block_time_rel": "10 seconds old",
"blockchain_confirmation_requirement": 7,
"blockchain_average_delegate_participation": 73.262839879154072,
"network_num_connections": 27,
"ntp_time": "20140617T035910.362611",
"ntp_error_seconds": 3.6413069999999998,
"wallet_unlocked_seconds_remaining": 2891989745,
"wallet_next_block_production_time": "20140617T040000",
"wallet_seconds_until_next_block_production": 50,
"wallet_local_time": "20140617T035910",
"blockchain_random_seed": "b3dc1e136fdabc070a7d8a141b0c6b6202c70c86",
"blockchain_shares": 10000487430311,
"network_num_connections_max": 60,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19691231T235959",
"wallet_version": 100
}
--- there are now 27 active connections to the p2p network
-
could you please do" blockchain_get_block_by_number 13112" and post the output below?
I am suspicious the network is forked into 2 chains.
following is mine output for 13112
blockchain_get_block_by_number 13112
{
"previous": "4212da499f7bbaee08101232023946dfb397e2e6",
"block_num": 13112,
"fee_rate": 1000,
"delegate_pay_rate": 91329,
"timestamp": "20140617T034415",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "42a008716f3f720b535c5dd47581fd32be2daf89",
"previous_secret": "104fc6c7297da0f15b6c97af5227562db8e7d0b2",
"delegate_signature": "20e5d0dd14fad51dbf40549c5706d58cbb34f7df04e23ddd6005b1639d807e286bd4bc766fc7427ee434dbff871a34138027f1a50540da9476d91eb1c6c2d99b0d",
"user_transaction_ids": []
}
pan2pa
-
(wallet closed) >>> wallet_open
wallet_name: roy
20005 no_such_wallet: wallet does not exist
No such wallet exists!
{"name":"roy"}
th_a wallet.cpp:563 open
{"wallet_name":"roy"}
th_a wallet.cpp:567 open
{}
th_a common_api_client.cpp:252 wallet_open
{"command":"wallet_open"}
th_a cli.cpp:570 execute_command
root@BTS002:~/.BitSharesXTS/wallets# dir
roy
I cannot open the wallet, after update code ,
-
Toast /BM , bad news , our network forked . following is info of block 13112 form 2 clients
btw, i am on the latest code form github
blockchain_get_block_by_number 13112
{
"previous": "4212da499f7bbaee08101232023946dfb397e2e6",
"block_num": 13112,
"fee_rate": 1000,
"delegate_pay_rate": 91329,
"timestamp": "20140617T034415",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "42a008716f3f720b535c5dd47581fd32be2daf89",
"previous_secret": "104fc6c7297da0f15b6c97af5227562db8e7d0b2",
"delegate_signature": "20e5d0dd14fad51dbf40549c5706d58cbb34f7df04e23ddd6005b1639d807e286bd4bc766fc7427ee434dbff871a34138027f1a50540da9476d91eb1c6c2d99b0d",
"user_transaction_ids": []
}
blockchain_get_block_by_number 13112
{
"previous": "4a0892eefaa2a8be974478bd9d054e2959508ab6",
"block_num": 13112,
"fee_rate": 1000,
"delegate_pay_rate": 91329,
"timestamp": "20140617T012845",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "a81c89804309b6f12f1ee332a1ca8efb180d2c37",
"previous_secret": "b1a33103e50925046ccfdb1b0651d4529dbcce15",
"delegate_signature": "203af87a488097790e643ea0ed8e5337d44a96e98bf40677b1f7bf4e27252e1d3f6e642df9c24f4a640820f0eb62c74bc987570417d443729ceaa031be283227ed",
"user_transaction_ids": []
}
-
Great. Something to take on in the am.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
could you please do" blockchain_get_block_by_number 13112" and post the output below?
I am suspicious the network is forked into 2 chains.
following is mine output for 13112
blockchain_get_block_by_number 13112
{
"previous": "4212da499f7bbaee08101232023946dfb397e2e6",
"block_num": 13112,
"fee_rate": 1000,
"delegate_pay_rate": 91329,
"timestamp": "20140617T034415",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "42a008716f3f720b535c5dd47581fd32be2daf89",
"previous_secret": "104fc6c7297da0f15b6c97af5227562db8e7d0b2",
"delegate_signature": "20e5d0dd14fad51dbf40549c5706d58cbb34f7df04e23ddd6005b1639d807e286bd4bc766fc7427ee434dbff871a34138027f1a50540da9476d91eb1c6c2d99b0d",
"user_transaction_ids": []
}
pan2pa
>>> blockchain_get_block_by_number 13112
{
"previous": "4a0892eefaa2a8be974478bd9d054e2959508ab6",
"block_num": 13112,
"fee_rate": 1000,
"delegate_pay_rate": 91329,
"timestamp": "20140617T012845",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "a81c89804309b6f12f1ee332a1ca8efb180d2c37",
"previous_secret": "b1a33103e50925046ccfdb1b0651d4529dbcce15",
"delegate_signature": "203af87a488097790e643ea0ed8e5337d44a96e98bf40677b1f7bf4e27252e1d3f6e642df9c24f4a640820f0eb62c74bc987570417d443729ceaa031be283227ed",
"user_transaction_ids": []
-
Great. Something to take on in the am.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
let me know if you need any log
-
1. you create power with max supply only 1, you should set it more
2. after create power, you need to issue your asset to yourself
delegate (unlocked) >>> wallet_asset_issue 0.1 POW networker "little power"
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
I created my own asset 'POWER'
,{
"id": 11,
"symbol": "POW",
"name": "power",
"description": "Power Coin",
"public_data": 100000000000,
"issuer_account_id": 332,
"precision": 1000000,
"current_share_supply": 0,
"maximum_share_supply": 1000000,
"collected_fees": 0,
"registration_date": "20140617T022715"
},{
How can I send some to you? I used
networker (unlocked) >>> wallet_transfer
amount_to_transfer: 10000
asset_symbol: POW
from_account_name: networker
to_account_name: betax
20011 insufficient_funds: insufficient funds
{"required":"10,000.000000 POW","available":"0.000000 POW"}
th_a wallet.cpp:206 withdraw_to_transaction
{"amount":10000000000,"asset_id":11,"from_account_address":"XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj","trx":{"expiration":null,"delegate_id":null,"operations":[],"signatures":[]},"required_signatures":[]}
th_a wallet.cpp:207 withdraw_to_transaction
{"real_amount_to_transfer":10000,"amount_to_transfer_symbol":"POW","from_account_name":"networker","to_account_name":"betax","memo_message":""}
th_a wallet.cpp:1599 transfer_asset
{}
th_a common_api_client.cpp:472 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:547 execute_command
What does this mean? Why the fund is insufficient?
-
seems your local time is wrong, you can't produc block if your tims is not correct.
Still not producing any blocks.. after 7
blockchain_get_account_record bitcoiners
{
"id": 299,
"name": "bitcoiners",
"public_data": null,
"owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
"active_key_history": [[
"20140613T030845",
"XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
]
],
"delegate_info": {
"votes_for": 83109630849,
"votes_against": 0,
"blocks_produced": 7,
"blocks_missed": 145,
>>> get_info
{
"blockchain_head_block_num": 13427,
"blockchain_head_block_time": "20140617T031615",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 8,
"blockchain_average_delegate_participation": 73.652239939255878,
"network_num_connections": 9,
>>> about
{
"bitshares_toolkit_revision": "c345f294b5bdca77f1e6a45cc0b7ae86477e2e5b",
"bitshares_toolkit_revision_age": "4 hours ago",
"fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
"fc_revision_age": "4 hours ago",
"compile_date": "compiled on Jun 17 2014 at 02:16:5
list_errors
..
"level": "warn",
"file": "chain_database.cpp",
"line": 1069,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T024332.916702"
},
"format": "",
"data": {
"block_data": {
"previous": "4ade36992ec3209214b0fc91eb67ca0677186748",
"block_num": 13349,
"fee_rate": 1000,
"delegate_pay_rate": 91803,
"timestamp": "20140617T024645",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "447c7dfd98fbd471a93113ef6ce23b63ea2172f9",
"previous_secret": "31fee77caf17df77620ba7067cff2c652beb7b36",
"delegate_signature": "1fb0a852e7e463c3bea50eb8fc4e07cc1ad325db031a10b16a24f278e1e32b9ea1ad945d7a5bc6b950b5722e158aa88b511487e89bd91549e8790b1da39f806ea3",
"user_transactions": []
}
}
},{
"context": {
"level": "warn",
"file": "client.cpp",
"line": 550,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T024332.916777"
},
"format": "Error pushing block ${block_number} - ${block_id}",
"data": {
"block_id": "73142597a754b26aac370ff1ebffa9ea98351592",
"block_number": 13349,
"block": {
"previous": "4ade36992ec3209214b0fc91eb67ca0677186748",
"block_num": 13349,
"fee_rate": 1000,
"delegate_pay_rate": 91803,
"timestamp": "20140617T024645",
"transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
"next_secret_hash": "447c7dfd98fbd471a93113ef6ce23b63ea2172f9",
"previous_secret": "31fee77caf17df77620ba7067cff2c652beb7b36",
"delegate_signature": "1fb0a852e7e463c3bea50eb8fc4e07cc1ad325db031a10b16a24f278e1e32b9ea1ad945d7a5bc6b950b5722e158aa88b511487e89bd91549e8790b1da39f806ea3",
"user_transactions": []
}
}
}
]
}
],[
"20140617T024332.917766",{
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 848,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T024332.917764"
},
"format": "I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid",
"data": {}
}
]
}
]
]
-
(wallet closed) >>> wallet_open
wallet_name: roy
20005 no_such_wallet: wallet does not exist
No such wallet exists!
{"name":"roy"}
th_a wallet.cpp:563 open
{"wallet_name":"roy"}
th_a wallet.cpp:567 open
{}
th_a common_api_client.cpp:252 wallet_open
{"command":"wallet_open"}
th_a cli.cpp:570 execute_command
root@BTS002:~/.BitSharesXTS/wallets# dir
roy
I cannot open the wallet, after update code ,
config dir had change to .BitShares\ XTS
mv your wallet file from old dir to new dir.
-
seems your local time is wrong, you can't produc block if your tims is not correct.
I am using a VPS server with OpenVZ, so can't set time manually.
-
seems your local time is wrong, you can't produc block if your tims is not correct.
Do you know how to correct it? Ubuntu 14.04 server.
install ntp, run it to sync with ntp server.
From what I know, latest bitshares_client have include a ntp client already.
-
1. you create power with max supply only 1, you should set it more
2. after create power, you need to issue your asset to yourself
delegate (unlocked) >>> wallet_asset_issue 0.1 POW networker "little power"
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
I created my own asset 'POWER'
,{
"id": 11,
"symbol": "POW",
"name": "power",
"description": "Power Coin",
"public_data": 100000000000,
"issuer_account_id": 332,
"precision": 1000000,
"current_share_supply": 0,
"maximum_share_supply": 1000000,
"collected_fees": 0,
"registration_date": "20140617T022715"
},{
How can I send some to you? I used
networker (unlocked) >>> wallet_transfer
amount_to_transfer: 10000
asset_symbol: POW
from_account_name: networker
to_account_name: betax
20011 insufficient_funds: insufficient funds
{"required":"10,000.000000 POW","available":"0.000000 POW"}
th_a wallet.cpp:206 withdraw_to_transaction
{"amount":10000000000,"asset_id":11,"from_account_address":"XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj","trx":{"expiration":null,"delegate_id":null,"operations":[],"signatures":[]},"required_signatures":[]}
th_a wallet.cpp:207 withdraw_to_transaction
{"real_amount_to_transfer":10000,"amount_to_transfer_symbol":"POW","from_account_name":"networker","to_account_name":"betax","memo_message":""}
th_a wallet.cpp:1599 transfer_asset
{}
th_a common_api_client.cpp:472 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:547 execute_command
What does this mean? Why the fund is insufficient?
What's the problem with following command?
networker (unlocked) >>> wallet_asset_create POW2 power2 networker "Power Coin" null 1000000000000000 1000000
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol_name( symbol ):
{}
th_a wallet.cpp:1692 create_asset
{"symbol":"POW2","name":"power2","description":"Power Coin","issuer_account":"networker"}
th_a wallet.cpp:1729 create_asset
{}
th_a common_api_client.cpp:562 wallet_asset_create
{"command":"wallet_asset_create"}
th_a cli.cpp:547 execute_command
-
After creating an asset you must issue it to yourself before you can transfer.
wallet_asset_issue....
-
try a new name without digital
1. you create power with max supply only 1, you should set it more
2. after create power, you need to issue your asset to yourself
delegate (unlocked) >>> wallet_asset_issue 0.1 POW networker "little power"
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
I created my own asset 'POWER'
,{
"id": 11,
"symbol": "POW",
"name": "power",
"description": "Power Coin",
"public_data": 100000000000,
"issuer_account_id": 332,
"precision": 1000000,
"current_share_supply": 0,
"maximum_share_supply": 1000000,
"collected_fees": 0,
"registration_date": "20140617T022715"
},{
How can I send some to you? I used
networker (unlocked) >>> wallet_transfer
amount_to_transfer: 10000
asset_symbol: POW
from_account_name: networker
to_account_name: betax
20011 insufficient_funds: insufficient funds
{"required":"10,000.000000 POW","available":"0.000000 POW"}
th_a wallet.cpp:206 withdraw_to_transaction
{"amount":10000000000,"asset_id":11,"from_account_address":"XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj","trx":{"expiration":null,"delegate_id":null,"operations":[],"signatures":[]},"required_signatures":[]}
th_a wallet.cpp:207 withdraw_to_transaction
{"real_amount_to_transfer":10000,"amount_to_transfer_symbol":"POW","from_account_name":"networker","to_account_name":"betax","memo_message":""}
th_a wallet.cpp:1599 transfer_asset
{}
th_a common_api_client.cpp:472 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:547 execute_command
What does this mean? Why the fund is insufficient?
What's the problem with following command?
networker (unlocked) >>> wallet_asset_create POW2 power2 networker "Power Coin" null 1000000000000000 1000000
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol_name( symbol ):
{}
th_a wallet.cpp:1692 create_asset
{"symbol":"POW2","name":"power2","description":"Power Coin","issuer_account":"networker"}
th_a wallet.cpp:1729 create_asset
{}
th_a common_api_client.cpp:562 wallet_asset_create
{"command":"wallet_asset_create"}
th_a cli.cpp:547 execute_command
-
You are right. Digital makes the problem.
Now:
networker (unlocked) >>> wallet_asset_create POR Power networker "Power Coin" null 1000000000000000 1000000
20011 insufficient_funds: insufficient funds
{"required":"10.495701 XTS","available":"10.464290 XTS"}
th_a wallet.cpp:206 withdraw_to_transaction
Can someone send me more XTS for the test?
try a new name without digital
Can someone send me more XTS for the test?
1. you create power with max supply only 1, you should set it more
2. after create power, you need to issue your asset to yourself
delegate (unlocked) >>> wallet_asset_issue 0.1 POW networker "little power"
Have some happiness :D
11060.0 2014-06-16T13:08:30 betax networker 100,000.000000 HAP 0.010000 XTS 532275d5
try creating your own assets
I created my own asset 'POWER'
,{
"id": 11,
"symbol": "POW",
"name": "power",
"description": "Power Coin",
"public_data": 100000000000,
"issuer_account_id": 332,
"precision": 1000000,
"current_share_supply": 0,
"maximum_share_supply": 1000000,
"collected_fees": 0,
"registration_date": "20140617T022715"
},{
How can I send some to you? I used
networker (unlocked) >>> wallet_transfer
amount_to_transfer: 10000
asset_symbol: POW
from_account_name: networker
to_account_name: betax
20011 insufficient_funds: insufficient funds
{"required":"10,000.000000 POW","available":"0.000000 POW"}
th_a wallet.cpp:206 withdraw_to_transaction
{"amount":10000000000,"asset_id":11,"from_account_address":"XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj","trx":{"expiration":null,"delegate_id":null,"operations":[],"signatures":[]},"required_signatures":[]}
th_a wallet.cpp:207 withdraw_to_transaction
{"real_amount_to_transfer":10000,"amount_to_transfer_symbol":"POW","from_account_name":"networker","to_account_name":"betax","memo_message":""}
th_a wallet.cpp:1599 transfer_asset
{}
th_a common_api_client.cpp:472 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:547 execute_command
What does this mean? Why the fund is insufficient?
What's the problem with following command?
networker (unlocked) >>> wallet_asset_create POW2 power2 networker "Power Coin" null 1000000000000000 1000000
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol_name( symbol ):
{}
th_a wallet.cpp:1692 create_asset
{"symbol":"POW2","name":"power2","description":"Power Coin","issuer_account":"networker"}
th_a wallet.cpp:1729 create_asset
{}
th_a common_api_client.cpp:562 wallet_asset_create
{"command":"wallet_asset_create"}
th_a cli.cpp:547 execute_command
-
Ok so I recently discovered that we failed to use the NTP time for the block generation loop, (only using it for validation). This would cause any nodes that fall out of sync with NTP by more than 30 seconds to end up on a fork. I have updated the code and it should hopefully resolve the remaining forks.
Just because we include NTP in our client does not mean we are using the most accurate form of NTP. We merely query the server without factoring in network latency. To get a proper NTP sync delegates should install NTP and set it to track as closely as possible to minimize drift.
Recent error logged by one of the seed servers...
"format": "block_data.timestamp <= (now + BTS_BLOCKCHAIN_BLOCK_INTERVAL_SEC*2): ${block_data.timestamp} < ${now}",
"data": {
"block_data.timestamp": "20140617T024645",
"now": "20140617T024332"
}
-
To get a proper NTP sync delegates should install NTP and set it to track as closely as possible to minimize drift.
I am running a VPS server on OpenVZ and manual time updates are not possible as this is a shared-kernel setup.
-
To get a proper NTP sync delegates should install NTP and set it to track as closely as possible to minimize drift.
I am running a VPS server on OpenVZ and manual time updates are not possible as this is a shared-kernel setup.
With the latest code it shouldn't matter too much. Real NTP is just improving things in the sub second range. You should be able to operate just fine now.
-
send you 2 XTS just now
You are right. Digital makes the problem.
Now:
networker (unlocked) >>> wallet_asset_create POR Power networker "Power Coin" null 1000000000000000 1000000
20011 insufficient_funds: insufficient funds
{"required":"10.495701 XTS","available":"10.464290 XTS"}
th_a wallet.cpp:206 withdraw_to_transaction
Can someone send me more XTS for the test?
-
As a protocol DPOS is very reliant on time synchronization to prevent forks. This shouldn't be a problem but is something that I would love to find a way to make more robust.
That said while the latest fix should prevent forks in the first place, there is apparently still a bug that is preventing the minority fork from rejoining the majority fork in a timely manner. I am going to investigate this further.
The good news is that delegate participation has stayed above 70% for a long time now and despite the problems and bug fixes we have managed to keep the chain going. I would say that we are on a solid trajectory toward a releasable DPOS baseline. Thanks again for everyone helping us test and debug this code. You are earning your spot as future delegates and leaders and it should pay you well.
-
BM , do you mean that i can keep all my four spots <grin> ?
BTW , do i need to set up NTP on my linux and how?
sudo apt-get install NTP
Reading package lists... Done
Building dependency tree
Reading state information... Done
ntp is already the newest version.
Thanks again for everyone helping us test and debug this code. You are earning your spot as future delegates and leaders and it should pay you well.
-
Here is the list of blocks known to the seed where forks occurred thus far:
[
6249, 10008, 12290, 12804, 13346, 13095, 13102, 10251, 12014
]
Based upon the latest graphvis rendering it appears we had a 3-way fork going on for a while. One reason the chains may not converge is because once a fork is marked invalid it doesn't matter how long it gets. In the event that the majority chain ends up 'in the future' (ie: your local clock is ahead) then you will never join. That said the server is reporting that the forks were in the future, and therefore they should consider our 'longer chain' the valid chain and switch over to it.
If you are a delegate on a minority fork then please provide me the result of 'list_errors', I am working on a version that is prettier than the current dump. You may have to open the image in a new tab to scroll right to see the whole fork tree.
(http://bitshares.org/documentation/fork13000.svg)
-
anyway to dump list_errors output to file.
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054339.859860"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054340.860556",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054340.860518"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054341.861192",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054341.861155"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054342.861835",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054342.861796"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054343.862502",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054343.862464"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054344.863197",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054344.863158"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054345.863795",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054345.863757"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054346.864391",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054346.864352"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054515.892444",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054515.892406"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054516.893131",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054516.893093"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054517.893783",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054517.893745"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054518.894431",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054518.894393"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054519.895103",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054519.895064"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054520.895757",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054520.895718"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054521.896418",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054521.896380"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054522.897074",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054522.897035"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054523.897730",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054523.897690"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054524.898392",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054524.898352"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054525.899062",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054525.899024"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054526.899880",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054526.899841"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054527.900685",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054527.900647"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054528.901329",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054528.901291"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054529.902077",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054529.902039"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054530.902672",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054530.902634"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
],[
"20140617T054531.903464",{
"code": 10,
"name": "assert_exception",
"message": "Assert Exception",
"stack": [{
"context": {
"level": "error",
"file": "client.cpp",
"line": 438,
"method": "",
"hostname": "",
"thread_name": "th_a",
"timestamp": "20140617T054531.903423"
},
"format": "network_get_connection_count() >= BTS_MIN_DELEGATE_CONNECTION_COUNT: Client must have ${count} connections before you may produce blocks",
"data": {
"count": 5
}
}
]
}
]
Here is the list of blocks known to the seed where forks occurred thus far:
[
6249, 10008, 12290, 12804, 13346, 13095, 13102, 10251, 12014
]
Based upon the latest graphvis rendering it appears we had a 3-way fork going on for a while. One reason the chains may not converge is because once a fork is marked invalid it doesn't matter how long it gets. In the event that the majority chain ends up 'in the future' (ie: your local clock is ahead) then you will never join. That said the server is reporting that the forks were in the future, and therefore they should consider our 'longer chain' the valid chain and switch over to it.
If you are a delegate on a minority fork then please provide me the result of 'list_errors', I am working on a version that is prettier than the current dump. You may have to open the image in a new tab to scroll right to see the whole fork tree.
(http://bitshares.org/documentation/fork13000.svg)
-
alt, puppy thanks for your puppylove and drinks :) Nice thing to wake up to.
networker let me know if you still having problems creating your assets, just catch up now with the thread.
-
Thanks for puppy love and drinks! :)
It is strange that I have also a lot of UNKNOW transactions:
12029.1 2014-06-16T19:12:00 puppies spartako puppy love 10,000,000.000000 PPL 0.000000 XTS 4d00acba
12911.0 2014-06-17T00:20:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS a7f1c1fe
12919.1 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 5bea9de8
12919.0 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 0dd5c404
12923.0 2014-06-17T00:25:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 4070120d
12927.0 2014-06-17T00:26:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3cb5c470
12962.0 2014-06-17T00:38:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3c4916b0
12977.1 2014-06-17T00:43:00 delegate-alt spartako buy you a drink 10,000.000000 DRINK 0.000000 XTS 605101ed
13009.6 2014-06-17T00:55:15 delegate-alt spartako buy you a drink 10,000.000000 DRINK 0.000000 XTS d0211a26
13288.0 2014-06-17T02:27:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 30ee8dad
-
Thanks for puppy love and drinks! :)
It is strange that I have also a lot of UNKNOW transactions:
12029.1 2014-06-16T19:12:00 puppies spartako puppy love 10,000,000.000000 PPL 0.000000 XTS 4d00acba
12911.0 2014-06-17T00:20:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS a7f1c1fe
12919.1 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 5bea9de8
12919.0 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 0dd5c404
12923.0 2014-06-17T00:25:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 4070120d
12927.0 2014-06-17T00:26:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3cb5c470
12962.0 2014-06-17T00:38:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3c4916b0
12977.1 2014-06-17T00:43:00 delegate-alt spartako buy you a drink 10,000.000000 DRINK 0.000000 XTS 605101ed
13009.6 2014-06-17T00:55:15 delegate-alt spartako buy you a drink 10,000.000000 DRINK 0.000000 XTS d0211a26
13288.0 2014-06-17T02:27:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 30ee8dad
dito
12911.0 2014-06-17T00:20:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS a7f1c1fe
12919.0 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 0dd5c404
12919.1 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 5bea9de8
12923.0 2014-06-17T00:25:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 4070120d
12927.0 2014-06-17T00:26:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3cb5c470
12962.0 2014-06-17T00:38:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3c4916b0
13288.0 2014-06-17T02:27:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 30ee8dad
//edit: a7f1c1fe seems to be a multipart tx with DREAMs:
{
"trx": {
"expiration": null,
"delegate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTSPF4tqwJcBofobTYvk1LTnS8mBhHL8PEdB",
"amount": 7940000,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTS23evqoPUn1gMuokexXW4o4EZbfJgf4gvb",
"amount": 2555709,
"claim_input_data": ""
}
},{
"type": "create_asset_op_type",
"data": {
"symbol": "DREAM",
"name": "Dream",
"description": "I have a dream",
"public_data": 1000000000000000,
"issuer_account_id": 301,
"maximum_share_supply": 1000000,
"precision": 1000000
}
}
],
"signatures": [
"206eaf4bd8a8528807e117753bc1f5b4aa923f887a0d636dc5f548d681bd8550186516465b5468eaa98a9c8b4f336b2a183e031fb91dda5429f026eaa4aa033b57",
"205eda2650f123b6026bd0858d1729ee16a79ff1b036d566f54fdcc5995be6d5738890675364f872fe4ec8854921f112fd1aa4e57214aedda7c501534af0b35a41",
"20450f00a0d4f3d4e2a873cc128ba221b8818ea2aa1d85687ce4d36903e86867ee11b17ccd42fc1ae930d4dc49e7c66e9987e754e4990d48a10a1df2c90378aac7"
]
},
"signed_keys": [
"XTSHb9T6vgwTVdHCZnpxAQsJhrfv6ZUaMibR",
"XTSAbYQ9EzqcyqUZVDcyi8NcmiXabREMSc9i",
"XTSGcMVUFwPodBeYqGcHyiBdPjdzfGvDXH8u",
"XTSAPRnTisVPnXqcchGBYHkvTi1R9oECG5mY",
"XTSPF4Kh1amQW1i8s37fcyFPrvkhhqQ4ufZr",
"XTS9Wc6HcsXdsp15yf68YtJRLNsPHuDEeCW3",
"XTSGGB7WWy5HHutJY8XdBrrUoCwL9V83Dtj4",
"XTS9XgtsQAAmJsz6uC5T7B1HUTC1Fipw4KV",
"XTSE4pN4RxYKssJ82Xiz3HhBjKEJ1mR5CYV2",
"XTSNp4uA8HF5wB2ErkZE4DmsBeLnnsqsPkre",
"XTSCHbgH3adAvPecgSp4LPqPC46hWfckfWBK",
"XTS3JNsHvPqg4X28h81dVsCdDwJSxyatKKw3",
"XTS4jPV6cGF97NueDDku334QeWrgNwnctqyV",
"XTSnBo4NdUn1PkiDpQGTvkmfgdYyaTxVWPs",
"XTS7ZiXFgXgQByRtvpX6wZxZMsktxZbAuRG3"
],
"validation_error": null,
"required_deposits": [],
"provided_deposits": [],
"deposits": [],
"withdraws": [[
0,{
"amount": 10495709,
"asset_id": 0
}
]
],
"balance": [[
0,
10495709
]
],
"net_delegate_votes": [[
307,{
"votes_for": -7940000,
"votes_against": 0
}
],[
302,{
"votes_for": -2555709,
"votes_against": 0
}
]
],
"chain_location": {
"block_num": 12911,
"trx_num": 0
}
}
-
//edit: a7f1c1fe seems to be a multipart tx with DREAMs:
The last one (30ee8dad) It seems similar but with POW
{
"trx": {
"expiration": null,
"delegate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTSHswxSb1yoHgyoK3u7SqLUnHbkMRKBFgAk",
"amount": 10000000,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTS82KFS55P7RxQT2yGaHjhKNEqs9b8PuYSN",
"amount": 495709,
"claim_input_data": ""
}
},{
"type": "create_asset_op_type",
"data": {
"symbol": "POW",
"name": "power",
"description": "Power Coin",
"public_data": 100000000000,
"issuer_account_id": 332,
"maximum_share_supply": 1000000,
"precision": 1000000
}
}
],
"signatures": [
"20c92066273109a6c3c2b424f97cabd0e771b9dbd39db0d356a8f8796d201fdf9f8fd25fc6e83517bb4d43e24d38c19cf6e59404cd49edf85893df743cfec69ca9",
"1f2a2e085730d3cd6600b5cbd2a0e57816eed9a05e4903d7b1c7bade49c2d1e29bf1d9a11f2cc84cadc06360f7152446464ba0d09ae9c547295760ddbb0dc208e1",
"1f4a276262d8a90bc3d90bd5f6561474a1f2091a2facb46af698005073826b998b15e5d499fc7bf5c363d6ebb9369ca6d111161454ee01e959bf0b7a44bab2563e"
]
},
"signed_keys": [
"XTSKnJ3GsgVzcKnQUDUX3bZjFrR8cpz4Hgfp",
"XTSC3Rrm5HHMmjJJpvXf5owhUvchPZduDXJ1",
"XTSJ1uVkKwj6opxn1XpHtSH2Ku1B5gRRutbS",
"XTSPAdo1Fx1JTuo438oKJxKbDdJXGjQMCQdJ",
"XTSGfFUDNNT46A6v7uHU4nsrykAJpCtxo52M",
"XTS4Akzyo6tNUbgdemtrpYaLwSxjqNctxRaM",
"XTSCtGKAhg6pDbigyPf7EpapEkgBHXfeupDX",
"XTSDJizuC5nqRDGYi5j2vChi9mYeaV8kxPhw",
"XTSDbE5sTA2rGycqst17EXqUJ2nZswNnMY9M",
"XTS2X2aCdRJX1HTGJ3JTZi7iJfm8fcaqhb17",
"XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj",
"XTSEGJzmcJsCmbKw4Goi8VBy5xK9HRtUvtd1",
"XTS44N71Gpanrwm2ZAeBXJZ4S9p8nfYgzwAM",
"XTSCjRYC1frZKt2edjheESDvrKsiLkMHTCH3",
"XTS3mCdpG8RQ2uKRwAL36dfmE6UPynM4596f"
],
"validation_error": null,
"required_deposits": [],
"provided_deposits": [],
"deposits": [],
"withdraws": [[
0,{
"amount": 10495709,
"asset_id": 0
}
]
],
"balance": [[
0,
10495709
]
],
"net_delegate_votes": [[
304,{
"votes_for": -10000000,
"votes_against": 0
}
],[
314,{
"votes_for": -495709,
"votes_against": 0
}
]
],
"chain_location": {
"block_num": 13288,
"trx_num": 0
}
}
-
Same here:
12029.0 2014-06-16T19:12:00 puppies betax puppy love 10,000,000.000000 PPL 0.000000 XTS 1cca930e
12911.0 2014-06-17T00:20:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS a7f1c1fe
12919.0 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 0dd5c404
12919.1 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 5bea9de8
12923.0 2014-06-17T00:25:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 4070120d
12927.0 2014-06-17T00:26:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3cb5c470
12962.0 2014-06-17T00:38:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3c4916b0
12977.0 2014-06-17T00:43:00 delegate-alt betax buy you a drink 10,000.000000 DRINK 0.000000 XTS 0c9c4190
12990.1 2014-06-17T00:47:45 delegate-alt betax buy you a drink 10,000.000000 DRINK 0.000000 XTS 6685757e
13000.0 2014-06-17T00:51:30 delegate-alt betax buy you a drink 10,000.000000 DRINK 0.000000 XTS a8923925
13288.0 2014-06-17T02:27:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 30ee8dad
-
alt, puppy thanks for your puppylove and drinks :) Nice thing to wake up to.
networker let me know if you still having problems creating your assets, just catch up now with the thread.
Just now alt sent me 2 XTS and I use following command. Strange things happened, My XTS balance decrease everytime even I didn't creat my own asset successfully. Why ?
networker (unlocked) >>> wallet_asset_create POR Power networker "Power Coin" null 1000000000000000 1000000 20011 insufficient_funds: insufficient funds
{"required":"10.495701 XTS","available":"2.000000 XTS"}
th_a wallet.cpp:206 withdraw_to_transaction
{"amount":10495701,"asset_id":0,"from_account_address":"XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj","trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSPghsfhR7GSSW9bfPALY2n8FKDCL73sy5B","amount":2000000,"claim_input_data":""}}],"signatures":[]},"required_signatures":["XTS7g45Ah8dtfjVdUptKCg23RFiXzMMbXiz6","XTSzeBJTaQEDcx6NffvuYW39qyt6gG91Rwj"]}
th_a wallet.cpp:207 withdraw_to_transaction
{"symbol":"POR","name":"Power","description":"Power Coin","issuer_account":"networker"}
th_a wallet.cpp:1729 create_asset
{}
th_a common_api_client.cpp:562 wallet_asset_create
{"command":"wallet_asset_create"}
th_a cli.cpp:547 execute_command
networker (unlocked) >>> wallet_asset_create POR Power networker "Power Coin" null 1000000000000000 1000000
20011 insufficient_funds: insufficient funds
{"required":"10.495701 XTS","available":"0.000000 XTS"}
th_a wallet.cpp:206 withdraw_to_transaction
It seems everytime I run wallet_asset_create command , my xts balance decrease no matter the asset is created successfully or not?
Can someone send me 11 XTS for the creating asset test?
-
insufficient_funds: insufficient funds
I sent you some more
edit: after running 'wallet_rescan_blockchain' your balance should be correct again!
-
What does pay balance mean in delegate account info?
blockchain_get_account_record_by_id 81
{
"id": 81,
"name": "init-delegate-81",
"public_data": null,
"owner_key": "XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc",
"active_key_history": [[
"20140616T183634",
"XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc"
]
],
"delegate_info": {
"votes_for": 87701418366,
"votes_against": 0,
"blocks_produced": 164,
"blocks_missed": 103,
"pay_balance": 12293597,
"next_secret_hash": "7efcf506ea6a5704f19827fa023a7d0e8fa783b2",
"last_block_num_produced": 14519
},
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"meta_data": null
}
-
Also seems like wallet_account_rename doesnt work =D
-
What does pay balance mean in delegate account info?
blockchain_get_account_record_by_id 81
{
"id": 81,
"name": "init-delegate-81",
"public_data": null,
"owner_key": "XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc",
"active_key_history": [[
"20140616T183634",
"XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc"
]
],
"delegate_info": {
"votes_for": 87701418366,
"votes_against": 0,
"blocks_produced": 164,
"blocks_missed": 103,
"pay_balance": 12293597,
"next_secret_hash": "7efcf506ea6a5704f19827fa023a7d0e8fa783b2",
"last_block_num_produced": 14519
},
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"meta_data": null
}
afaik theres an extra command to move these funds to an account
-
What does pay balance mean in delegate account info?
blockchain_get_account_record_by_id 81
{
"id": 81,
"name": "init-delegate-81",
"public_data": null,
"owner_key": "XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc",
"active_key_history": [[
"20140616T183634",
"XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc"
]
],
"delegate_info": {
"votes_for": 87701418366,
"votes_against": 0,
"blocks_produced": 164,
"blocks_missed": 103,
"pay_balance": 12293597,
"next_secret_hash": "7efcf506ea6a5704f19827fa023a7d0e8fa783b2",
"last_block_num_produced": 14519
},
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"meta_data": null
}
afaik theres an extra command to move these funds to an account
Realy!? What command?
-
Realy!? What command?
Should be "wallet_withdraw_delegate_pay" but doesn't work for me:
"id": 22,
"name": "init-delegate-22",
"public_data": null,
"owner_key": "XTS8LLDp6tZzh4bt5mBJXrigaff76xJCHzU1uqJrEryJpiZFcW3Ac",
"active_key_history": [[
"20140616T234722",
"XTS8LLDp6tZzh4bt5mBJXrigaff76xJCHzU1uqJrEryJpiZFcW3Ac"
]
],
"delegate_info": {
"votes_for": 93511847643,
"votes_against": 0,
"blocks_produced": 177,
"blocks_missed": 89,
"pay_balance": 12309790,
"next_secret_hash": "c6aa50eb9c8f6a6691692fdc5e88637fddad67e2",
"last_block_num_produced": 14735
},
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"meta_data": null
}
default (unlocked) >>> wallet_withdraw_delegate_pay init-delegate-22 spartako 10000 "some pay"
31005 insufficient_funds: insufficient funds
{"pay_to_account":{"id":22,"name":"init-delegate-22","public_data":null,"owner_key":"XTS8LLDp6tZzh4bt5mBJXrigaff76xJCHzU1uqJrEryJpiZFcW3Ac","active_key_history":[["20140616T234722","XTS8LLDp6tZzh4bt5mBJXrigaff76xJCHzU1uqJrEryJpiZFcW3Ac"]],"delegate_info":{"votes_for":93511847643,"votes_against":0,"blocks_produced":177,"blocks_missed":89,"pay_balance":12309790,"next_secret_hash":"c6aa50eb9c8f6a6691692fdc5e88637fddad67e2","last_block_num_produced":14735},"registration_date":"20140601T000000","last_update":"20140601T000000","meta_data":null},"amount":20000}
th_a account_operations.cpp:93 evaluate
{"*this":{"amount":20000,"account_id":22}}
th_a account_operations.cpp:100 evaluate
{"op":{"type":"withdraw_pay_op_type","data":{"amount":20000,"account_id":22}}}
th_a operation_factory.hpp:51 evaluate
{"trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_pay_op_type","data":{"amount":20000,"account_id":22}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_id":22,"type":"withdraw_signature_type","data":{"owner":"XTSPFC8WEyGDxShfCZuKGhovtCT6toUZP7n4","memo":{"one_time_key":"XTS7Jfw28NZiaHfHu3F29DwQGvfeLPiNFQb3DE3yKqrf3LhjFy8xr","encrypted_memo_data":"878a7af38043f1793349316b9dc636b69f9ea3abcc9fee4287caf7a3d1aba246446a2b241d1a15c56e86eb601f89d68b86b1fa20c1bd1c089ebcd914db63194b"}}}}}],"signatures":["1f5056222be336d661d8b4180482fcf4723784d6fd73809d9a360295ce48ecba206cba7f01d1608e11e1b6e06b15459dbbc13516015f14904e29c8c323b669a981"]}}
th_a transaction_evaluation_state.cpp:149 evaluate
{"trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_pay_op_type","data":{"amount":20000,"account_id":22}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_id":22,"type":"withdraw_signature_type","data":{"owner":"XTSPFC8WEyGDxShfCZuKGhovtCT6toUZP7n4","memo":{"one_time_key":"XTS7Jfw28NZiaHfHu3F29DwQGvfeLPiNFQb3DE3yKqrf3LhjFy8xr","encrypted_memo_data":"878a7af38043f1793349316b9dc636b69f9ea3abcc9fee4287caf7a3d1aba246446a2b241d1a15c56e86eb601f89d68b86b1fa20c1bd1c089ebcd914db63194b"}}}}}],"signatures":["1f5056222be336d661d8b4180482fcf4723784d6fd73809d9a360295ce48ecba206cba7f01d1608e11e1b6e06b15459dbbc13516015f14904e29c8c323b669a981"]}}
th_a chain_database.cpp:966 evaluate_transaction
{"trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_pay_op_type","data":{"amount":20000,"account_id":22}},{"type":"deposit_op_type","data":{"amount":10000,"condition":{"asset_id":0,"delegate_id":22,"type":"withdraw_signature_type","data":{"owner":"XTSPFC8WEyGDxShfCZuKGhovtCT6toUZP7n4","memo":{"one_time_key":"XTS7Jfw28NZiaHfHu3F29DwQGvfeLPiNFQb3DE3yKqrf3LhjFy8xr","encrypted_memo_data":"878a7af38043f1793349316b9dc636b69f9ea3abcc9fee4287caf7a3d1aba246446a2b241d1a15c56e86eb601f89d68b86b1fa20c1bd1c089ebcd914db63194b"}}}}}],"signatures":["1f5056222be336d661d8b4180482fcf4723784d6fd73809d9a360295ce48ecba206cba7f01d1608e11e1b6e06b15459dbbc13516015f14904e29c8c323b669a981"]}}
th_a chain_database.cpp:1305 store_pending_transaction
{}
th_a common_api_client.cpp:642 wallet_withdraw_delegate_pay
{"command":"wallet_withdraw_delegate_pay"}
th_a cli.cpp:570 execute_command
-
What does pay balance mean in delegate account info?
blockchain_get_account_record_by_id 81
{
"id": 81,
"name": "init-delegate-81",
"public_data": null,
"owner_key": "XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc",
"active_key_history": [[
"20140616T183634",
"XTS6ATqGY8ynvL7cqHsxCJYuNYRLX7Nyv9X51qT6MivTADt6dPMRc"
]
],
"delegate_info": {
"votes_for": 87701418366,
"votes_against": 0,
"blocks_produced": 164,
"blocks_missed": 103,
"pay_balance": 12293597,
"next_secret_hash": "7efcf506ea6a5704f19827fa023a7d0e8fa783b2",
"last_block_num_produced": 14519
},
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"meta_data": null
}
afaik theres an extra command to move these funds to an account
Realy!? What command?
wallet_withdraw_delegate_pay <delegate_name> <to_account_name> <amount_to_withdraw> <memo>
-
insufficient_funds: insufficient funds
I sent you some more
edit: after running 'wallet_rescan_blockchain' your balance should be correct again!
I'm on a fork again :'(
networker (unlocked) >>> getinfo
{
"blockchain_head_block_num": 14373,
"blockchain_head_block_time": "20140617T085745",
"blockchain_head_block_time_rel": "3 hours old",
I install NTP and sync with China NTP Server using Hongkong Time.
Tue Jun 17 20:27:17 HKT 2014
-
Funny command walllet_list_unspent_balances causes segfault
-
Funny command walllet_list_unspent_balances causes segfault
same here .. but it used to work yesterday
-
Thanks for puppy love and drinks! :)
It is strange that I have also a lot of UNKNOW transactions:
12029.1 2014-06-16T19:12:00 puppies spartako puppy love 10,000,000.000000 PPL 0.000000 XTS 4d00acba
12911.0 2014-06-17T00:20:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS a7f1c1fe
12919.1 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 5bea9de8
12919.0 2014-06-17T00:23:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 0dd5c404
12923.0 2014-06-17T00:25:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 4070120d
12927.0 2014-06-17T00:26:45 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3cb5c470
12962.0 2014-06-17T00:38:00 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3c4916b0
12977.1 2014-06-17T00:43:00 delegate-alt spartako buy you a drink 10,000.000000 DRINK 0.000000 XTS 605101ed
13009.6 2014-06-17T00:55:15 delegate-alt spartako buy you a drink 10,000.000000 DRINK 0.000000 XTS d0211a26
13288.0 2014-06-17T02:27:30 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 30ee8dad
All of the UNKNOWN transactions are other people issuing assets which the wallet is including in everyones wallet. Known bug.
-
Seems like wallet_withdraw_delegate_pay doesnt work =\
-
What have you done? My number of connections has finally increased to 25.
-
"blockchain_average_delegate_participation": 73.876618431073879,
good to see the participation is increase.
-
roy (unlocked) >>> wallet_list_unspent_balances
BALANCE OWNER VOTE
--------------------------------------------------------------------------------------------------------------------------
10000000000 XTSPZ7uJuawoRhhzmrY6XpTFiKwTSr18Cy9b +init-delegate-60
10000000000 XTS9TQhSUydf6WucD2CrsYMKquoGmM56qhdG +init-delegate-28
10000000000 XTSLBVU1KzA7hKUXf74tHmYRv1WtM3uFawNn +init-delegate-93
10000000000 XTSCEfgwvJV4YWxA6pzdPy7SQTGGvFsEJTmX +init-delegate-55
I have so many BTS ? is it belong to me ,or What is the units
roy (unlocked) >>> wallet_account_balance roy
roy:
10,000.000000 DRINK
0.000000 XTS
what is DRINK?
-
So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
Sent from my iPhone using Tapatalk
-
So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
You got trust from me ..
+ You should give yourself some trust and move your XTS from your wallet back to your own wallet so that your vote is broadcasted!
-
So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
You got trust from me ..
+ You should give yourself some trust and move your XTS from your wallet back to your own wallet so that your vote is broadcasted!
Right, of course! I'll go do that on my lunch break. :)
Sent from my iPhone using Tapatalk
-
"blockchain_head_block_num": 15371,
"blockchain_head_block_time": "20140617T143000",
"blockchain_head_block_time_rel": "8 seconds old",
"blockchain_average_delegate_participation": 75.369075369075375,
We are making progress... thanks everyone for keeping your nodes built with the latest code and frequent updates.
-
"blockchain_head_block_num": 15371,
"blockchain_head_block_time": "20140617T143000",
"blockchain_head_block_time_rel": "8 seconds old",
"blockchain_average_delegate_participation": 75.369075369075375,
We are making progress... thanks everyone for keeping your nodes built with the latest code and frequent updates.
Its easy actualy =D
Btw are there some estimation about number of active nodes and/or node connectivity graph?
-
So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
You got trust from me ..
+ You should give yourself some trust and move your XTS from your wallet back to your own wallet so that your vote is broadcasted!
Hi I trusted everyone here, moving XTS around but the problem is:
+ When I vote for someone else my votes decreased.
+ When I vote back myself (transfer XTS back) I believe their votes go down
So we are back to square 1.
Bytemaster any way to get all the delegates in the queue (named) as delegates. I would like and (everyone else I guess) to test my VPS.
-
default (unlocked) >>> wallet_set_delegate_trust_level crazybit 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level cgafeng 1
OK
--- there are now 22 active connections to the p2p network
default (unlocked) >>> wallet_set_delegate_trust_level puppies 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level boombastic-ags 1
OK
--- there are now 23 active connections to the p2p network
--- in sync with p2p network
default (unlocked) >>> wallet_set_delegate_trust_level mauritso 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level delegate-alt 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level alexxy 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level coolspeed 1
OK
--- there are now 24 active connections to the p2p network
--- in sync with p2p network
default (unlocked) >>> wallet_set_delegate_trust_level testz-test 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level bitshares 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level dd-1 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level spartako 1
OK
--- there are now 23 active connections to the p2p network
default (unlocked) >>> wallet_set_delegate_trust_level xeroc 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level betax 1
-
I have a subfolder "gui_settings" showing up in my wallet/ directory. I suspect it has something to do with this commit https://github.com/BitShares/bitshares_toolkit/commit/fdff2fa2d726bb97fcddca4ecab2c31f607f1fd3.
Anyone else see this too?
-
So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
You got trust from me ..
+ You should give yourself some trust and move your XTS from your wallet back to your own wallet so that your vote is broadcasted!
Hi I trusted everyone here, moving XTS around but the problem is:
+ When I vote for someone else my votes decreased.
+ When I vote back myself (transfer XTS back) I believe their votes go down
So we are back to square 1.
Bytemaster any way to get all the delegates in the queue (named) as delegates. I would like and (everyone else I guess) to test my VPS.
The challenge we have is that our 'test stake' isn't enough to fully elect all the delegates (meaning things are working). I used my stake to vote out some of the non-performing initial delegate keys in an attempt to make room for everyone else.
-
Build failed:
1 warning generated.
Linking CXX executable bitshares_client
Undefined symbols for architecture x86_64:
"_rl_copy_text", referenced from:
bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
"_rl_getc", referenced from:
fc::detail::functor_run<bts::cli::detail::get_character::$_0>::run(void*, void*) in libbts_cli.a(cli.cpp.o)
"_rl_replace_line", referenced from:
bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2
-
So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
You got trust from me ..
+ You should give yourself some trust and move your XTS from your wallet back to your own wallet so that your vote is broadcasted!
Hi I trusted everyone here, moving XTS around but the problem is:
+ When I vote for someone else my votes decreased.
+ When I vote back myself (transfer XTS back) I believe their votes go down
So we are back to square 1.
Bytemaster any way to get all the delegates in the queue (named) as delegates. I would like and (everyone else I guess) to test my VPS.
The challenge we have is that our 'test stake' isn't enough to fully elect all the delegates (meaning things are working). I used my stake to vote out some of the non-performing initial delegate keys in an attempt to make room for everyone else.
So are we going to have to vote down all the init delegates again when the official release hits? Or is there going to be some kind of snapshot from this test net? Would it be more effective to vote down init delegates than to vote up everyone else?
Sent from my iPhone using Tapatalk
-
The challenge we have is that our 'test stake' isn't enough to fully elect all the delegates (meaning things are working). I used my stake to vote out some of the non-performing initial delegate keys in an attempt to make room for everyone else.
Does it mean the XTS we have can only vote for OR against a delegate? Can't both?
-
So I finally was able to import my PTS wallet.dat. Apparently I just had to wait long enough for the blockchain to sync. And now I am registered as a delegate on the waiting list! Anyone want to vote for me?! :D "bdnoble-1" I can send some votes back too. We gotta replace some more of these init-delegates. :)
You got trust from me ..
+ You should give yourself some trust and move your XTS from your wallet back to your own wallet so that your vote is broadcasted!
Hi I trusted everyone here, moving XTS around but the problem is:
+ When I vote for someone else my votes decreased.
+ When I vote back myself (transfer XTS back) I believe their votes go down
So we are back to square 1.
Bytemaster any way to get all the delegates in the queue (named) as delegates. I would like and (everyone else I guess) to test my VPS.
The challenge we have is that our 'test stake' isn't enough to fully elect all the delegates (meaning things are working). I used my stake to vote out some of the non-performing initial delegate keys in an attempt to make room for everyone else.
Very good point. I remember now you use all your stake to vote a couple of guys / gals in.
-
The challenge we have is that our 'test stake' isn't enough to fully elect all the delegates (meaning things are working). I used my stake to vote out some of the non-performing initial delegate keys in an attempt to make room for everyone else.
Does it mean the XTS we have can only vote for OR against a delegate? Can't both?
That's another good question.
-
The challenge we have is that our 'test stake' isn't enough to fully elect all the delegates (meaning things are working). I used my stake to vote out some of the non-performing initial delegate keys in an attempt to make room for everyone else.
Does it mean the XTS we have can only vote for OR against a delegate? Can't both?
That's another good question.
Answer is yes
-
Funny command walllet_list_unspent_balances causes segfault
I think I fixed this...
-
We will be launching a new Dry Run 3 chain and it will have the following changes:
1) all active delegates that produced 0 blocks will be removed
2) everyone that registered as a delegate will take their place prioritized by vote.
3) we have fixed the wallet_withdraw_delegate_pay operation which would introduce a hard fork
4) we will increase the block interval to 30 seconds
5) we will be updating the on-the-wire protocol to communicate extra information such as:
a) latency between nodes
b) additional information about node connectivity.
c) persistent node IDs derived from a public key
With these network updates we should be able to map out the full network of connected nodes (nothing the NSA cannot do anyway). Using this information delegates can optimize their network connections and users can verify geographic diversity.
The new test net will launch once we finalize the on-the-wire protocol updates so probably tonight or tomorrow.
A new GUI wallet is also close to release.
-
good job.
-
last block produced 5 minutes ago, i think i am on fork :-\
@bytemaster +5%
-
Repost:
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/level_map.hpp:14:
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/upgrade_leveldb.hpp:9:
In file included from /opt/local/include/boost/regex.hpp:31:
In file included from /opt/local/include/boost/regex/v4/regex.hpp:48:
/opt/local/include/boost/regex/v4/regex_raw_buffer.hpp:132:7: warning: 'register' storage class specifier is deprecated [-Wdeprecated-register]
register pointer result = end;
^~~~~~~~~
1 warning generated.
Linking CXX executable bitshares_client
Undefined symbols for architecture x86_64:
"_rl_copy_text", referenced from:
bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
"_rl_getc", referenced from:
fc::detail::functor_run<bts::cli::detail::get_character::$_0>::run(void*, void*) in libbts_cli.a(cli.cpp.o)
"_rl_replace_line", referenced from:
bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2
Is there a configuration error on my part? (Mac OS X 10.9)
-
Repost:
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/level_map.hpp:14:
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/upgrade_leveldb.hpp:9:
In file included from /opt/local/include/boost/regex.hpp:31:
In file included from /opt/local/include/boost/regex/v4/regex.hpp:48:
/opt/local/include/boost/regex/v4/regex_raw_buffer.hpp:132:7: warning: 'register' storage class specifier is deprecated [-Wdeprecated-register]
register pointer result = end;
^~~~~~~~~
1 warning generated.
Linking CXX executable bitshares_client
Undefined symbols for architecture x86_64:
"_rl_copy_text", referenced from:
bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
"_rl_getc", referenced from:
fc::detail::functor_run<bts::cli::detail::get_character::$_0>::run(void*, void*) in libbts_cli.a(cli.cpp.o)
"_rl_replace_line", referenced from:
bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2
Is there a configuration error on my part? (Mac OS X 10.9)
Remove your cmake cache... it looks like you compiled / installed the latest readline but cmake is still linking to the old one.
rm CMakeCache.txt
-
last block produced 5 minutes ago, i think i am on fork :-\
@bytemaster +5%
?? what happened?
-
default (unlocked) >>> info
{
"blockchain_head_block_num": 15775,
"blockchain_head_block_time": "20140617T164030",
"blockchain_head_block_time_rel": "8 seconds old",
"blockchain_confirmation_requirement": 1,
"blockchain_average_delegate_participation": 78.099838969404189,
"network_num_connections": 34,
"ntp_time": "20140617T164038.675214",
"ntp_error_seconds": -0.023547999999999999,
"wallet_unlocked_seconds_remaining": 99960516,
"wallet_next_block_production_time": "20140617T164215",
"wallet_seconds_until_next_block_production": 97,
"wallet_local_time": "20140617T164038",
"blockchain_random_seed": "3493c71eac43d555d8d8aec75ba5b7005990c5d6",
"blockchain_shares": 10000633285155,
"network_num_connections_max": 100,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170817T152914",
"wallet_version": 100
}
default (unlocked) >>> blockchain_list_forks
[
14683,
15636,
]
The most recent fork was for a single block between times 15473 15474 and 15475 and appears to be a 'naturally occurring' well behaved/expected fork where delegate at time 15475 didn't get the block from 15474 in time and the other delegates agreed. Increasing the block interval to 30 seconds should reduce the probability of this. Also I suspect that the delegate that produced block 88383 (time slot 15474) may be running older code (ie: didn't update in the past 12 hours)
-
last block produced 5 minutes ago, i think i am on fork :-\
@bytemaster +5%
?? what happened?
last block produced is 15742 but it is irrelevant now when dry run 3 is coming
"blockchain_head_block_num": 15742,
"blockchain_head_block_time": "20140617T163030",
"blockchain_head_block_time_rel": "15 minutes ago",
"blockchain_confirmation_requirement": 7,
"blockchain_average_delegate_participation": 74.329501915708818,
"network_num_connections": 8,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140617T164542",
"blockchain_random_seed": "a22b0a9cd8f31b4a85a5a6b1b2a73e7a3cb5c396",
"blockchain_shares": 10000630530782,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140617T164023",
"wallet_version": 100
-
We will be launching a new Dry Run 3 chain and it will have the following changes:
1) all active delegates that produced 0 blocks will be removed
2) everyone that registered as a delegate will take their place prioritized by vote.
3) we have fixed the wallet_withdraw_delegate_pay operation which would introduce a hard fork
4) we will increase the block interval to 30 seconds
5) we will be updating the on-the-wire protocol to communicate extra information such as:
a) latency between nodes
b) additional information about node connectivity.
c) persistent node IDs derived from a public key
With these network updates we should be able to map out the full network of connected nodes (nothing the NSA cannot do anyway). Using this information delegates can optimize their network connections and users can verify geographic diversity.
The new test net will launch once we finalize the on-the-wire protocol updates so probably tonight or tomorrow.
A new GUI wallet is also close to release.
Is there any way we could get the wiki updated with the recently added debug commands? Like list_errors and max_connections and all that? That way those of us who came a little late can be more helpful.
Sent from my iPhone using Tapatalk
-
Repost:
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/level_map.hpp:14:
In file included from /Users/maurits/bitsharesxts/bitshares_toolkit/libraries/db/include/bts/db/upgrade_leveldb.hpp:9:
In file included from /opt/local/include/boost/regex.hpp:31:
In file included from /opt/local/include/boost/regex/v4/regex.hpp:48:
/opt/local/include/boost/regex/v4/regex_raw_buffer.hpp:132:7: warning: 'register' storage class specifier is deprecated [-Wdeprecated-register]
register pointer result = end;
^~~~~~~~~
1 warning generated.
Linking CXX executable bitshares_client
Undefined symbols for architecture x86_64:
"_rl_copy_text", referenced from:
bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
"_rl_getc", referenced from:
fc::detail::functor_run<bts::cli::detail::get_character::$_0>::run(void*, void*) in libbts_cli.a(cli.cpp.o)
"_rl_replace_line", referenced from:
bts::cli::detail::cli_impl::display_status_message(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in libbts_cli.a(cli.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2
Is there a configuration error on my part? (Mac OS X 10.9)
Remove your cmake cache... it looks like you compiled / installed the latest readline but cmake is still linking to the old one.
rm CMakeCache.txt
I do rm -rf bitshares_toolkit every time when I want to update/rebuild bitshares_toolkit.
ran:
rm CMakeCache.txtcmake -DCMAKE_PREFIX_PATH=/usr/local/ssl .make
And I got the same error.
-
>>> blockchain_list_forks
[
10427,
13346,
15830,
5624,
14994,
14973,
7832,
2299,
6388
]
>>> info
{
"blockchain_head_block_num": 15833,
"blockchain_head_block_time": "20140617T170145",
"blockchain_head_block_time_rel": "14 seconds old",
"blockchain_confirmation_requirement": 15,
"blockchain_average_delegate_participation": 77.537969624300558,
"network_num_connections": 12,
"ntp_time": "20140617T170159.909973",
"ntp_error_seconds": 202.32990100000001,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": "20140617T171300",
"wallet_seconds_until_next_block_production": 661,
"wallet_local_time": "20140617T170159",
"blockchain_random_seed": "abeedd4f3c753dea11ea026f9ff5345f1d76665a",
"blockchain_shares": 10000628300985,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19700101T000000",
"wallet_version": 100
}
>>> about
{
"bitshares_toolkit_revision": "b851eb7cadfb79df07d5512ee9de1217479962b4",
"bitshares_toolkit_revision_age": "49 minutes ago",
"fc_revision": "653fd2ca8b54c64c0e2e217456bd9ee355d32ced",
"fc_revision_age": "83 minutes ago",
"compile_date": "compiled on Jun 17 2014 at 17:23:16"
}
-
Funny command walllet_list_unspent_balances causes segfault
I think I fixed this...
Not completely:
default (unlocked) >>> wallet_list_unspent_balances
BALANCE OWNER VOTE
--------------------------------------------------------------------------------------------------------------------------
[...]
10000000000000 XTSDZMTUtwj6FQHC6JsaevZ8usNHRqfW61fK none10 assert_exception: Assert Exception
!"unimplemented condition type":
{}
th_a cli.cpp:843 format_and_print_result
-
Another single-block natural fork occurred at 15830 (likely the same delegate)...
-
Switched to a manually compiled/installed version of readline (coming from macports readline @6.3.003_0) and it built successfully.
Also discovered why the JSON RPC API didn't work at first, there is another difference between the bitcoin RPC and bitshares RPC.
Bitcoin RPC doesn't require to be passed an "id", bitshares RPC does.
http://<user>:<pass>@localhost:<httprpcport>/rpc and send an "id" and it should work (like so: "id" : uniqueidentifier)
-
Another single-block natural fork occurred at 15830 (likely the same delegate)...
I saw more forks on my end......???
>>> blockchain_list_forks
[
1460,
14683,
10427,
6158,
12826,
15830,
6690,
14994,
2124,
14973,
7832,
12852,
2299,
6388
]
pan2pan (unlocked) >>> info
{
"blockchain_head_block_num": 16332,
"blockchain_head_block_time": "20140617T194045",
"blockchain_head_block_time_rel": "18 seconds old",
"blockchain_confirmation_requirement": 3,
"blockchain_average_delegate_participation": 77.414205905826023,
"network_num_connections": 6,
"ntp_time": "20140617T194103.348120",
"ntp_error_seconds": 3.5663130000000001,
"wallet_unlocked_seconds_remaining": 977746,
"wallet_next_block_production_time": "20140617T194415",
"wallet_seconds_until_next_block_production": 192,
"wallet_local_time": "20140617T194103",
"blockchain_random_seed": "28560defc69aa22ca1442fcfb45e7e4d087eb353",
"blockchain_shares": 10000633395121,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140629T031649",
"wallet_version": 100
}
-
Here is the actual console output:
--- in sync with p2p network
--- there are now 29 active connections to the p2p network
--- syncing with p2p network, 246 blocks left to fetch
--- there are now 29 active connections to the p2p network
--- there are now 29 active connections to the p2p network
emski (unlocked) >>> get_info
{
"blockchain_head_block_num": 16429,
"blockchain_head_block_time": "20140617T201115",
"blockchain_head_block_time_rel": "24 seconds old",
"blockchain_confirmation_requirement": 1,
"blockchain_average_delegate_participation": 77.106518282988873,
"network_num_connections": 29,
"ntp_time": "20140617T201139.063736",
"ntp_error_seconds": 4.4679169999999999,
"wallet_unlocked_seconds_remaining": 2891931396,
"wallet_next_block_production_time": "20140617T201530",
"wallet_seconds_until_next_block_production": 231,
"wallet_local_time": "20140617T201139",
"blockchain_random_seed": "e2436f9c12cce0ef0198c92e2ae5458d2f9c56e0",
"blockchain_shares": 10000642668612,
"network_num_connections_max": 60,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19691231T235959",
"wallet_version": 100
}
--- in sync with p2p network
Was I on a fork just before the message:
"--- syncing with p2p network, 246 blocks left to fetch"
And then synchronized ?
-
Another single-block natural fork occurred at 15830 (likely the same delegate)...
I like 15 seconds more as it's quicker and fork is fine as you always have to face it and we have TaPOS to discard a fork anyway.
-
Today the delegates are incentive to produce blocks by getting reward and punished only by votes.
I guess people are lazy to vote and I think we can further punish the delegate for missing blocks like this:
The reward for each block will be (normal reward)*(blocks produced in last 10000 blocks)/(blocks should have produced in last 10000 blocks). This means the more you miss, the less you can get the reward. Of course, you can be recovered if you continuously produce blocks for 10000 blocks (100 turns).
-
Here is the actual console output:
--- in sync with p2p network
--- there are now 29 active connections to the p2p network
--- syncing with p2p network, 246 blocks left to fetch
--- there are now 29 active connections to the p2p network
--- there are now 29 active connections to the p2p network
emski (unlocked) >>> get_info
{
"blockchain_head_block_num": 16429,
"blockchain_head_block_time": "20140617T201115",
"blockchain_head_block_time_rel": "24 seconds old",
"blockchain_confirmation_requirement": 1,
"blockchain_average_delegate_participation": 77.106518282988873,
"network_num_connections": 29,
"ntp_time": "20140617T201139.063736",
"ntp_error_seconds": 4.4679169999999999,
"wallet_unlocked_seconds_remaining": 2891931396,
"wallet_next_block_production_time": "20140617T201530",
"wallet_seconds_until_next_block_production": 231,
"wallet_local_time": "20140617T201139",
"blockchain_random_seed": "e2436f9c12cce0ef0198c92e2ae5458d2f9c56e0",
"blockchain_shares": 10000642668612,
"network_num_connections_max": 60,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "19691231T235959",
"wallet_version": 100
}
--- in sync with p2p network
Was I on a fork just before the message:
"--- syncing with p2p network, 246 blocks left to fetch"
And then synchronized ?
Yes that is a confusing message, but Eric says it is ok (just misleading)
-
my delegate "crazybit " still in the inactive list ,could anyone pls give me some trust, would like to test the block generation.
-
blockchain_list_forks not work
(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
{"key":"f54461de391b568340f93083999858a32613a438"}
th_a level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
{"key":"f54461de391b568340f93083999858a32613a438"}
th_a level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
{"block_id":"f54461de391b568340f93083999858a32613a438"}
th_a chain_database.cpp:1574 get_block_num
{}
th_a common_api_client.cpp:222 blockchain_list_forks
{"command":"blockchain_list_forks"}
th_a cli.cpp:570 execute_command
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
"bitshares_toolkit_revision_age": "18 hours ago",
"fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
"fc_revision_age": "25 hours ago",
"compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>
-
my delegate "crazybit " still in the inactive list ,could anyone pls give me some trust, would like to test the block generation.
putting you in dry run 3
-
load config from .BitSharesXTS or .BitShares\ XTS ?
this is the output from latest version .
Creating default config file "/home/alt/.BitSharesXTS/config.json"
-
load config from .BitSharesXTS or .BitShares\ XTS ?
this is the output from latest version .
Creating default config file "/home/alt/.BitSharesXTS/config.json"
Default directory was restored to the ~/.BitSharesXTS on Linux per: https://github.com/BitShares/bitshares_toolkit/issues/291
Linux users will want to move their wallets from ~/.BitShares\ XTS to ~/.BitSharesXTS.
-
load config from .BitSharesXTS or .BitShares\ XTS ?
this is the output from latest version .
Creating default config file "/home/alt/.BitSharesXTS/config.json"
Default directory was restored to the ~/.BitSharesXTS on Linux per: https://github.com/BitShares/bitshares_toolkit/issues/291
Linux users will want to move their wallets from ~/.BitShares\ XTS to ~/.BitSharesXTS.
thx
for user who run in linux, pay attention, rename the dir name when you update client.
-
blockchain_list_forks not work
(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
{"key":"f54461de391b568340f93083999858a32613a438"}
th_a level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
{"key":"f54461de391b568340f93083999858a32613a438"}
th_a level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
{"block_id":"f54461de391b568340f93083999858a32613a438"}
th_a chain_database.cpp:1574 get_block_num
{}
th_a common_api_client.cpp:222 blockchain_list_forks
{"command":"blockchain_list_forks"}
th_a cli.cpp:570 execute_command
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
"bitshares_toolkit_revision_age": "18 hours ago",
"fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
"fc_revision_age": "25 hours ago",
"compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>
Should be fixed for now: https://github.com/BitShares/bitshares_toolkit/commit/909323ea5e1ed6287f6ca5900d135771e2fa7564
-
Great!
But I can't test this, because the chain database is clear and redownload after upgrade.
blockchain_list_forks not work
(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
{"key":"f54461de391b568340f93083999858a32613a438"}
th_a level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
{"key":"f54461de391b568340f93083999858a32613a438"}
th_a level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
{"block_id":"f54461de391b568340f93083999858a32613a438"}
th_a chain_database.cpp:1574 get_block_num
{}
th_a common_api_client.cpp:222 blockchain_list_forks
{"command":"blockchain_list_forks"}
th_a cli.cpp:570 execute_command
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
"bitshares_toolkit_revision_age": "18 hours ago",
"fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
"fc_revision_age": "25 hours ago",
"compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>
Should be fixed for now: https://github.com/BitShares/bitshares_toolkit/commit/909323ea5e1ed6287f6ca5900d135771e2fa7564
-
blockchain_list_forks not work
(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
{"key":"f54461de391b568340f93083999858a32613a438"}
th_a level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
{"key":"f54461de391b568340f93083999858a32613a438"}
th_a level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
{"block_id":"f54461de391b568340f93083999858a32613a438"}
th_a chain_database.cpp:1574 get_block_num
{}
th_a common_api_client.cpp:222 blockchain_list_forks
{"command":"blockchain_list_forks"}
th_a cli.cpp:570 execute_command
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
"bitshares_toolkit_revision_age": "18 hours ago",
"fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
"fc_revision_age": "25 hours ago",
"compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>
Should be fixed for now: https://github.com/BitShares/bitshares_toolkit/commit/909323ea5e1ed6287f6ca5900d135771e2fa7564
It works on windows.
-
I'm eagerly awaiting dry run 3. The new chain hasn't launched yet has it?
-
I'm eagerly awaiting dry run 3. The new chain hasn't launched yet has it?
Waiting for updates from Eric.
-
I'm eagerly awaiting dry run 3. The new chain hasn't launched yet has it?
Waiting for updates from Eric.
Will the next dry run go with GUI?
-
Fresh rebuild with latest in ubuntu 14.04
"bitshares_toolkit_revision": "b81f9ac56623a4ae8bbc608b8a1f819e48938ac1",
"bitshares_toolkit_revision_age": "70 minutes ago",
"fc_revision": "9002b024693a8ac749a4d5f0b64821b2a1e8eab9",
"fc_revision_age": "6 hours ago",
"compile_date": "compiled on Jun 17 2014 at 21:08:07"
I've got connections droping and joining back and forth, very actively
}
--- 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 5 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 4 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
--- syncing with p2p network, 11207 blocks left to fetch
--- there are now 5 active connections to the p2p network
--- there are now 5 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
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- syncing with p2p network, 11210 blocks left to fetch
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- syncing with p2p network, 11212 blocks left to fetch
--- syncing with p2p network, 11213 blocks left to fetch
--- 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 6 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- syncing with p2p network, 11214 blocks left to fetch
--- there are now 5 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 5 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
--- there are now 6 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
--- there are now 7 active connections to the p2p network
and a "block count left to fetch" that just keeps increasing
--- syncing with p2p network, 11212 blocks left to fetch
--- syncing with p2p network, 11213 blocks left to fetch
stuck on block 6410
"blockchain_head_block_num": 6410,
"blockchain_head_block_time": "20140618T010915",
"blockchain_head_block_time_rel": "28 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 5.6297156123041203,
"network_num_connections": 9,
"ntp_time": "20140618T013657.384359",
"ntp_error_seconds": -0.082447000000000006,
"wallet_unlocked_seconds_remaining": 998505,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140618T013657",
"blockchain_random_seed": "a2de675ff3e5ae6032860b538e21793d78960fb0",
"blockchain_shares": 10000142881983,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140629T145842",
"wallet_version": 100
-
New build again, now stuck on 6923
"blockchain_head_block_num": 6923,
"blockchain_head_block_time": "20140615T115615",
"blockchain_head_block_time_rel": "62 hours old",
"blockchain_confirmation_requirement": 278,
"blockchain_average_delegate_participation": 5.8606730711135278,
"network_num_connections": 10,
"ntp_time": null,
"wallet_unlocked_seconds_remaining": 999305,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140618T022308",
"blockchain_random_seed": "c752c956ef242f8f17f174f81650dd8dce9a7694",
"blockchain_shares": 10000147000033,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140629T155813",
"wallet_version": 100
-
here is a script for automation test,
hope you like it
https://bitsharestalk.org/index.php?topic=5102.0
-
when I first run the automation test script, without sleep before wallet_transfer.
all transfer is pending and seems will never resolve.
17412.6 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS e579167b
17412.3 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS 95cb9277
17412.0 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS 00115a80
17413.0 2014-06-18T01:25:00 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS b0dbee8b
pending 2014-06-18T01:34:23 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS f4a242fd
pending 2014-06-18T01:34:23 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 2229adc8
pending 2014-06-18T01:34:23 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS d5d36e58
pending 2014-06-18T01:34:23 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS ca027b09
pending 2014-06-18T01:41:03 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS 0dd41950
pending 2014-06-18T01:41:03 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 87dfe5d1
pending 2014-06-18T01:41:03 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS 7cfe74d6
pending 2014-06-18T01:41:03 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS 3a3df2f1
17469.0 2014-06-18T01:41:30 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS 9034b4a1
17471.0 2014-06-18T01:42:15 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS c40c4f10
17486.0 2014-06-18T01:46:15 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 72c8f31a
17487.0 2014-06-18T01:46:30 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS b92a168c
-
and some times transfer failed
default (unlocked) >>> wallet_transfer 13 DRINK alt delegate-alt "test flood..."
31005 insufficient_funds: insufficient funds
{"current_balance_record":{"balance":0,"condition":{"asset_id":10,"delegate_id":17,"type":"withdraw_signature_type","data":{"owner":"XTSLWeDvytxWHxe4QVzKKxGFqy8woas
xJm1K","memo":{"one_time_key":"XTS5cvkcg9fdYqARpHz8p2CQrK7SWzypnp9eoNshXm5gSRqgftJij","encrypted_memo_data":"dbdf5de38b227851e360ae2bb02d83b60249e88cd33cd54eb13bc6b8be8
07f60f61a3be5d30aba8f24208e09c53d4f46a8387b2dd545a42ce4f3dd4737451ea3"}}},"last_update":"20140618T025300"},"amount":1000000,"current_balance_record->balance - amount":-
1000000}
th_a balance_operations.cpp:80 evaluate
{"op":{"balance_id":"XTSBrJnZLZ8cLRMTU6gwJ8SjyTH7GBHgkBzp","amount":1000000,"claim_input_data":""}}
th_a balance_operations.cpp:164 evaluate
{"op":{"type":"withdraw_op_type","data":{"balance_id":"XTSBrJnZLZ8cLRMTU6gwJ8SjyTH7GBHgkBzp","amount":1000000,"claim_input_data":""}}}
th_a operation_factory.hpp:51 evaluate
{"trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSBrJnZLZ8cLRMTU6gwJ8SjyTH7GBHgkBzp","amount":1000000,"
claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSKu4YBFNwCjUhSkTkqyZEPLYWqVL7VwFbB","amount":12000000,"claim_input_data":""}},{"type":"withdra
w_op_type","data":{"balance_id":"XTSFWtxkbLEdHs4fSzVqwVwgbg8Do5RrFLMR","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":13000000,"condi
tion":{"asset_id":10,"delegate_id":333,"type":"withdraw_signature_type","data":{"owner":"XTSDYicNZHx6bvLgb644STFGnhHZo622WCyr","memo":{"one_time_key":"XTS73P5XDcjRrhnJS
2G4douZV1e7LvcWDjiztbo2iC4U3NxeaNo9H","encrypted_memo_data":"d58dd6d7751b8a8e515e523837e03d95f14c1f1be9890c5bd4d02e98a94e177d673ffa272c6715a52f3a4dba50572151d0bd88e3f28
59176cffbb34f159746c5"}}}}}],"signatures":["2000bcece222f0bc535b06318906ced4ca930bb67226a872903ee1c5fc4ff6421c82baacee46d25f250eabc071a2065e5fac0c0ac200a15ad78c5c9bfea8
94c109","1f22ff50d7939b719baa5258918a31b99c0041bc89c361699f1919f2f288c4b6514d7a3a1d142972d8e74efe5ed1c3c63084acd45149f85d797ace16f7ce758960","1f0b65410ac4def2346893c352
2782c21a16dca0696b6ef677ba603d9a22656c6772e0930a50f473854ba730c3513e6bf198baaa71aa66df54acdba1e7d2fc846e"]}}
th_a transaction_evaluation_state.cpp:149 evaluate
{"trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSBrJnZLZ8cLRMTU6gwJ8SjyTH7GBHgkBzp","amount":1000000,"
claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSKu4YBFNwCjUhSkTkqyZEPLYWqVL7VwFbB","amount":12000000,"claim_input_data":""}},{"type":"withdra
w_op_type","data":{"balance_id":"XTSFWtxkbLEdHs4fSzVqwVwgbg8Do5RrFLMR","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":13000000,"condi
tion":{"asset_id":10,"delegate_id":333,"type":"withdraw_signature_type","data":{"owner":"XTSDYicNZHx6bvLgb644STFGnhHZo622WCyr","memo":{"one_time_key":"XTS73P5XDcjRrhnJS
2G4douZV1e7LvcWDjiztbo2iC4U3NxeaNo9H","encrypted_memo_data":"d58dd6d7751b8a8e515e523837e03d95f14c1f1be9890c5bd4d02e98a94e177d673ffa272c6715a52f3a4dba50572151d0bd88e3f28
59176cffbb34f159746c5"}}}}}],"signatures":["2000bcece222f0bc535b06318906ced4ca930bb67226a872903ee1c5fc4ff6421c82baacee46d25f250eabc071a2065e5fac0c0ac200a15ad78c5c9bfea8
94c109","1f22ff50d7939b719baa5258918a31b99c0041bc89c361699f1919f2f288c4b6514d7a3a1d142972d8e74efe5ed1c3c63084acd45149f85d797ace16f7ce758960","1f0b65410ac4def2346893c352
2782c21a16dca0696b6ef677ba603d9a22656c6772e0930a50f473854ba730c3513e6bf198baaa71aa66df54acdba1e7d2fc846e"]}}
th_a chain_database.cpp:996 evaluate_transaction
{"trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSBrJnZLZ8cLRMTU6gwJ8SjyTH7GBHgkBzp","amount":1000000,"
claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSKu4YBFNwCjUhSkTkqyZEPLYWqVL7VwFbB","amount":12000000,"claim_input_data":""}},{"type":"withdra
w_op_type","data":{"balance_id":"XTSFWtxkbLEdHs4fSzVqwVwgbg8Do5RrFLMR","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":13000000,"condi
tion":{"asset_id":10,"delegate_id":333,"type":"withdraw_signature_type","data":{"owner":"XTSDYicNZHx6bvLgb644STFGnhHZo622WCyr","memo":{"one_time_key":"XTS73P5XDcjRrhnJS
2G4douZV1e7LvcWDjiztbo2iC4U3NxeaNo9H","encrypted_memo_data":"d58dd6d7751b8a8e515e523837e03d95f14c1f1be9890c5bd4d02e98a94e177d673ffa272c6715a52f3a4dba50572151d0bd88e3f28
59176cffbb34f159746c5"}}}}}],"signatures":["2000bcece222f0bc535b06318906ced4ca930bb67226a872903ee1c5fc4ff6421c82baacee46d25f250eabc071a2065e5fac0c0ac200a15ad78c5c9bfea8
94c109","1f22ff50d7939b719baa5258918a31b99c0041bc89c361699f1919f2f288c4b6514d7a3a1d142972d8e74efe5ed1c3c63084acd45149f85d797ace16f7ce758960","1f0b65410ac4def2346893c352
2782c21a16dca0696b6ef677ba603d9a22656c6772e0930a50f473854ba730c3513e6bf198baaa71aa66df54acdba1e7d2fc846e"]}}
th_a chain_database.cpp:1335 store_pending_transaction
{}
th_a common_api_client.cpp:492 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:570 execute_command
default (unlocked) >>> wallet_account_balance
alt:
999,790.000000 DRINK
98,989.000000 HAP
79.000000 LOVE
999.000000 ORA
2.999740 XTS
-
3rd times the charm i guess
another fresh rebuild this time back to normal.
"blockchain_head_block_num": 17907,
"blockchain_head_block_time": "20140618T040600",
"blockchain_head_block_time_rel": "14 seconds old",
"blockchain_confirmation_requirement": 2,
"blockchain_average_delegate_participation": 77.662129703763014,
"network_num_connections": 10,
"ntp_time": "20140618T040614.894843",
"ntp_error_seconds": 0.42322100000000001,
"wallet_unlocked_seconds_remaining": 0,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140618T040614",
"blockchain_random_seed": "f31780c5622f1c8a161f467f1767bb6688cbf8aa",
"blockchain_shares": 10000753196660,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": false,
"wallet_unlocked_until": "",
"wallet_version": 100
same revision
(wallet closed) >>> about
{
"bitshares_toolkit_revision": "b81f9ac56623a4ae8bbc608b8a1f819e48938ac1",
"bitshares_toolkit_revision_age": "4 hours ago",
"fc_revision": "9002b024693a8ac749a4d5f0b64821b2a1e8eab9",
"fc_revision_age": "8 hours ago",
"compile_date": "compiled on Jun 17 2014 at 23:13:14"
}
-
Has anyone tried to run a delegate through Tor yet? I've noticed that nodes broadcast their local IP. If I am running behind a router through tor, and I broadcast 192.168.1.2 would that be enough to prevent someone from finding my IP? Is there a better way to broadcast through tor, without giving up your IP?
-
Is this an error?
I've set wallet_toggle_delegate_block_production init-delegate-42 true
and wallet_get_account init-delegate-42 says "block_production_enabled": false,
xeldal-w (unlocked) >>> wallet_toggle_delegate_block_production init-delegate-42 true
OK
xeldal-w (unlocked) >>> wallet_get_account init-delegate-42
{
"index": 4,
"id": 42,
"name": "init-delegate-42",
"public_data": null,
"owner_key": "XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit",
"active_key_history": [[
"20140618T035618",
"XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit"
]
],
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"delegate_info": {
"votes_for": 85012306379,
"votes_against": 0,
"blocks_produced": 193,
"blocks_missed": 113,
"pay_balance": 13562297,
"next_secret_hash": "677e403d0b6c7341cca966ce584a630b5a317e30",
"last_block_num_produced": 17209
},
"meta_data": null,
"account_address": "XTSJBUPebvzdAsmhxvzvqRdwKtTKg7Y9bvX5",
"trust_level": 0,
"block_production_enabled": false,
"private_data": null
}
-
can't understand the balance.
this is my transaction history
default (unlocked) >>> wallet_account_transaction_history alt
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----
pending 2014-06-11T07:49:15 UNKNOWN UNKNOWN 0.000000 XTS 0.000000 XTS 3d60360b
370.0 2014-06-13T05:17:15 alt alt register alt 0.000000 XTS 0.010044 XTS 2e486166
396.0 2014-06-13T05:35:45 alt init-delegate-18 test 0.100000 XTS 0.010000 XTS 09dd2374
399.0 2014-06-13T05:37:45 alt init-delegate-18 idle 1.000000 XTS 0.010000 XTS 4594491e
10092.1 2014-06-16T06:41:45 alt dorian hello 0.100000 XTS 0.010000 XTS f65a6b4d
10296.0 2014-06-16T08:05:00 clout alt 50.000000 XTS 0.000000 XTS e2c9cbc9
10339.0 2014-06-16T08:22:45 mauritso alt 10.000000 XTS 0.000000 XTS 37671f7e
10341.0 2014-06-16T08:23:15 mauritso alt 10.000000 LOVE 0.000000 XTS fe819ec6
10355.0 2014-06-16T08:30:45 betax alt 20.000000 XTS 0.000000 XTS 2ebd73be
10384.0 2014-06-16T08:42:15 betax alt 100,000.000000 HAP 0.000000 XTS 851d86be
10511.0 2014-06-16T09:32:15 spartako alt some love 100.000000 LOVE 0.000000 XTS 870cd6e6
11421.0 2014-06-16T15:23:45 alt ORDER-6B31qfya buy 10 XTS @ 100 HAP 1,000.000000 HAP 0.010000 XTS d50281b3
12754.0 2014-06-16T23:31:45 alt delegate-alt register delegate 11.000000 HAP 0.010000 XTS 898b13ea
12764.0 2014-06-16T23:34:15 alt delegate-alt register delegate 11.000000 XTS 0.010000 XTS 890fcb45
12772.0 2014-06-16T23:37:15 alt dorian send LOVE 20.000000 LOVE 0.010000 XTS 35e018a8
12776.0 2014-06-16T23:38:15 alt delegate-alt register delegate 11.000000 LOVE 0.010000 XTS c7e40cb1
12777.0 2014-06-16T23:38:30 alt delegate-alt register delegate 1.000000 XTS 0.010000 XTS 35aa0c54
12911.0 2014-06-17T00:20:45 alt alt create DREAM (Dream) 0.000000 XTS 0.000000 XTS a7f1c1fe
12919.0 2014-06-17T00:23:30 alt alt create HELLO (Dream) 0.000000 XTS 0.000000 XTS 0dd5c404
12919.1 2014-06-17T00:23:30 alt alt create HELLO (Dream) 0.000000 XTS 0.000000 XTS 5bea9de8
12923.0 2014-06-17T00:25:00 alt alt create APPLE (Dream) 0.000000 XTS 0.000000 XTS 4070120d
12927.0 2014-06-17T00:26:45 alt alt create ORA (Dream) 0.000000 XTS 0.000000 XTS 3cb5c470
12936.0 2014-06-17T00:29:45 alt alt hello 100.000000 ORA 0.000000 XTS 691dc61f
12936.1 2014-06-17T00:29:45 alt alt hello 10.000000 ORA 0.000000 XTS cb830aea
12939.0 2014-06-17T00:30:30 alt alt hello 889.000000 ORA 0.000000 XTS f6b7b739
12962.0 2014-06-17T00:38:00 alt alt create DRINK (drink) 0.000000 XTS 0.000000 XTS 3c4916b0
12966.0 2014-06-17T00:39:30 alt alt buy you a drink 9,999,999.000000 DRINK 0.000000 XTS 32a95de5
12969.0 2014-06-17T00:40:15 alt delegate-alt drink 9,000,000.000000 DRINK 0.010000 XTS d79413a4
13791.0 2014-06-17T05:28:30 alt networker 2.000000 XTS 0.010000 XTS da389b2e
17412.4 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS a815759a
17412.6 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS e579167b
17412.0 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS 00115a80
17412.5 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS cd87c4b9
17412.2 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS 9192aa1f
17412.1 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS 78f1d803
17412.3 2014-06-18T01:24:45 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS 95cb9277
17413.0 2014-06-18T01:25:00 alt delegate-alt test flood ... 10.000000 DRINK 0.010000 XTS b0dbee8b
pending 2014-06-18T01:34:23 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS d5d36e58
pending 2014-06-18T01:34:23 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS f4a242fd
pending 2014-06-18T01:34:23 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS ca027b09
pending 2014-06-18T01:34:23 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 2229adc8
pending 2014-06-18T01:41:03 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 87dfe5d1
pending 2014-06-18T01:41:03 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS 3a3df2f1
pending 2014-06-18T01:41:03 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS 0dd41950
pending 2014-06-18T01:41:03 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS 7cfe74d6
17469.0 2014-06-18T01:41:30 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS 9034b4a1
17471.0 2014-06-18T01:42:15 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS c40c4f10
17486.0 2014-06-18T01:46:15 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 72c8f31a
17487.1 2014-06-18T01:46:30 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS cb6c22c5
17487.0 2014-06-18T01:46:30 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS b92a168c
17487.2 2014-06-18T01:46:30 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS dd75389f
17493.0 2014-06-18T01:48:15 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 034b26a5
17493.1 2014-06-18T01:48:15 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS f7827952
17494.1 2014-06-18T01:48:30 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS 963b033f
17494.0 2014-06-18T01:48:30 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS 67f4dd77
pending 2014-06-18T02:04:25 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS e15cd926
pending 2014-06-18T02:04:26 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS ab18779f
pending 2014-06-18T02:04:27 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS a88ae121
pending 2014-06-18T02:04:28 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS 992ca441
pending 2014-06-18T02:06:45 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 12fe004e
pending 2014-06-18T02:06:46 alt delegate-alt test flood... 11.000000 DRINK 0.010000 XTS 3883ee08
pending 2014-06-18T02:06:47 alt delegate-alt test flood... 12.000000 DRINK 0.010000 XTS 679f5b60
pending 2014-06-18T02:06:48 alt delegate-alt test flood... 13.000000 DRINK 0.010000 XTS a9bbfa5b
pending 2014-06-18T02:08:19 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS b9c5e39e
pending 2014-06-18T02:08:21 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS 1fa8a494
...............
pending 2014-06-18T03:42:12 alt delegate-alt test flood... 10.000000 DRINK 0.010000 XTS ceba9be8
from this, I get about 80 XTS from clout,mauritso,betax. send about 12 XTS to delegate-alt
but the balance is only 3 XTS.
default (unlocked) >>> wallet_account_balance alt
alt:
999,803.000000 DRINK
98,989.000000 HAP
79.000000 LOVE
999.000000 ORA
3.009740 XTS
I have rescan before get balance.
Maybe create asset have spent much XTS, but not show on the history list?
-
Is this an error?
I've set wallet_toggle_delegate_block_production init-delegate-42 true
and wallet_get_account init-delegate-42 says "block_production_enabled": false,
xeldal-w (unlocked) >>> wallet_toggle_delegate_block_production init-delegate-42 true
OK
xeldal-w (unlocked) >>> wallet_get_account init-delegate-42
{
"index": 4,
"id": 42,
"name": "init-delegate-42",
"public_data": null,
"owner_key": "XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit",
"active_key_history": [[
"20140618T035618",
"XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit"
]
],
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"delegate_info": {
"votes_for": 85012306379,
"votes_against": 0,
"blocks_produced": 193,
"blocks_missed": 113,
"pay_balance": 13562297,
"next_secret_hash": "677e403d0b6c7341cca966ce584a630b5a317e30",
"last_block_num_produced": 17209
},
"meta_data": null,
"account_address": "XTSJBUPebvzdAsmhxvzvqRdwKtTKg7Y9bvX5",
"trust_level": 0,
"block_production_enabled": false,
"private_data": null
}
The same to me. Built with the latest codes.
-
heh my init delegates work like a charm, hovever my keyhotee id delegate alexxy didnt have a chance to produce block
-
my delegate "crazybit " still in the inactive list ,could anyone pls give me some trust, would like to test the block generation.
putting you in dry run 3
Would you mind putting me in dry run 3 too ?
my delegate "networker"
-
Same as what Xeldal met, my delegates have stopped working. I built with the latest codes.
"block_production_enabled": false,
heyd (unlocked) >>> info
{
"blockchain_head_block_num": 18346,
"blockchain_head_block_time": "20140618T063845",
"blockchain_head_block_time_rel": "1 second old",
"blockchain_confirmation_requirement": 1,
"blockchain_average_delegate_participation": 74.102368220015279,
"network_num_connections": 20,
"ntp_time": "20140618T063846.274894",
"ntp_error_seconds": -0.0015269999999999999,
"wallet_unlocked_seconds_remaining": 9986809,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140618T063846",
"blockchain_random_seed": "5ae3cf375a3d49771c448271f9c7a24f6f376e48",
"blockchain_shares": 10000752930064,
"network_num_connections_max": 999,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20141011T204535",
"wallet_version": 100
}
heyd (unlocked) >>> about
{
"bitshares_toolkit_revision": "b81f9ac56623a4ae8bbc608b8a1f819e48938ac1",
"bitshares_toolkit_revision_age": "6 hours ago",
"fc_revision": "9002b024693a8ac749a4d5f0b64821b2a1e8eab9",
"fc_revision_age": "11 hours ago",
"compile_date": "compiled on Jun 18 2014 at 02:54:02"
}
heyd (unlocked) >>> wallet_toggle_delegate_block_production init-delegate-96 true
OK
heyd (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK
heyd (unlocked) >>> wallet_get_account init-delegate-96
{
"index": 8,
"id": 96,
"name": "init-delegate-96",
"public_data": null,
"owner_key": "XTS5HHx85ASdW3b4UmyV8g2rLyYRfHeTj8aH6E1DTE11jFUBr96as",
"active_key_history": [[
"20140618T025823",
"XTS5HHx85ASdW3b4UmyV8g2rLyYRfHeTj8aH6E1DTE11jFUBr96as"
]
],
"registration_date": "20140601T000000",
"last_update": "20140601T000000",
"delegate_info": {
"votes_for": 93576540633,
"votes_against": 0,
"blocks_produced": 272,
"blocks_missed": 42,
"pay_balance": 18372613,
"next_secret_hash": "0a67f9d19499c8e3e8952c6d2c95e122f6d8bed2",
"last_block_num_produced": 17608
},
"meta_data": null,
"account_address": "XTSNdngzms5KBFqgpFF7dTJNZnJXT3xAXzZG",
"trust_level": 0,
"block_production_enabled": false,
"private_data": null
}
-
They missed to tell us about a recent commit:
https://github.com/BitShares/bitshares_toolkit/commit/55053c244f3057841b86a5b46fad654d7e1ce636
You need to run:
wallet_toggle_delegate_block_production <delegate> true
In order for delegates to produce blocks!
EDIT: doesn't seem to work .. i reverted to the previous commit to keep my delegate online AND producing blocks
-
sent some HSBC shares to the following guys, just for fun, not real HSBC shares. :D
18350.0 2014-06-18T06:40:15 crazybit xeroc Shares of HSBC 10,000.000000 HSBC 0.010000 XTS 9fcb4e7f
18351.0 2014-06-18T06:40:30 crazybit spartako Shares of HSBC 10,000.000000 HSBC 0.010000 XTS b9debac2
18352.0 2014-06-18T06:41:00 crazybit betax Shares of HSBC 10,000.000000 HSBC 0.010000 XTS 311db446
18352.1 2014-06-18T06:41:00 crazybit cgafeng Shares of HSBC 10,000.000000 HSBC 0.010000 XTS a6d0be23
18353.0 2014-06-18T06:41:30 crazybit mauritso Shares of HSBC 10,000.000000 HSBC 0.010000 XTS 32489b64
18353.1 2014-06-18T06:41:30 crazybit puppies Shares of HSBC 10,000.000000 HSBC 0.010000 XTS fd042d38
18355.0 2014-06-18T06:43:15 crazybit ags Shares of HSBC 10,000.000000 HSBC 0.010000 XTS 06c0dad5
18355.1 2014-06-18T06:43:15 crazybit delegate-alt Shares of HSBC 10,000.000000 HSBC 0.010000 XTS 3d4f84ff
18356.0 2014-06-18T06:43:30 crazybit alexxy Shares of HSBC 10,000.000000 HSBC 0.010000 XTS 8d7d321c
18357.0 2014-06-18T06:43:45 crazybit testz Shares of HSBC 10,000.000000 HSBC 0.010000 XTS a5a8a40d
18358.0 2014-06-18T06:44:15 crazybit bitsuperlab Shares of HSBC 10,000.000000 HSBC 0.010000 XTS bd08
-
sent some HSBC shares to the following guys, just for fun, not real HSBC shares. :D
Get it, thanks! :)
-
Having troubles issuing assets.
Usage:
wallet_asset_issue <amount> <symbol> <to_account_name> <memo_message>
>>> wallet_asset_issue 1000000 BEE default "Bees are people too"
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol( symbol ):
{}
th_a wallet.cpp:1772 issue_asset
-
Having troubles issuing assets.
Usage:
wallet_asset_issue <amount> <symbol> <to_account_name> <memo_message>
>>> wallet_asset_issue 1000000 BEE default "Bees are people too"
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol( symbol ):
{}
th_a wallet.cpp:1772 issue_asset
Is your account-name really 'default' .. not wallet name... it's accountname .. list your account names via wallet_list_receive_accounts
-
Is there any way we could get the wiki updated with the recently added debug commands? Like list_errors and max_connections and all that? That way those of us who came a little late can be more helpful.
Sent from my iPhone using Tapatalk
https://github.com/BitShares/bitshares_toolkit/wiki should be done. Generated with the api json documents.
Created a pull request: https://github.com/BitShares/bitshares_toolkit/pull/332
Manually fixed the JSON.
-
Can someone vote for my delegate?
-
Can someone vote for my delegate?
I just voted for you ;)
-
I missed the entire dry run 2, because it became impossible to install on a server with only 1GB RAM.
2GB seems enough. It's more expensive though.
I've got it up and running on a 512mb Amazon free tier micro server so that's not quite true. First compile failed, then I setup a 1gb swap and it worked.
It takes forever to compile though so by the time it's done, lots of new changes have alreade been pushed, lol.
-
It worked for me on dry run 1 with 1GB RAM, but on dry run 2 server just crashed when installing. After setting instance with 2GB RAM it now works like charm. OS is Ubuntu 14.04.
Hope to get elected to be active delegate in the next dry run. It could take very large marketing campaign in the future to stay a delegate.
-
Is there any way we could get the wiki updated with the recently added debug commands? Like list_errors and max_connections and all that? That way those of us who came a little late can be more helpful.
Sent from my iPhone using Tapatalk
https://github.com/BitShares/bitshares_toolkit/wiki should be done. Generated with the api json documents.
Created a pull request: https://github.com/BitShares/bitshares_toolkit/pull/332
Manually fixed the JSON.
Thanks
-
I missed the entire dry run 2, because it became impossible to install on a server with only 1GB RAM.
2GB seems enough. It's more expensive though.
This is a g++ limitation as our code does not require that much to run.
-
Im wondering, if we're manually adding a bunch of delegates for Dry Run 3. Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable? rather than making an additional one.
-
Im wondering, if we're manually adding a bunch of delegates for Dry Run 3. Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable? rather than making an additional one.
Good point!
I like it.
-
Im wondering, if we're manually adding a bunch of delegates for Dry Run 3. Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable? rather than making an additional one.
Good point!
I like it.
I get toast on it.
-
They missed to tell us about a recent commit:
https://github.com/BitShares/bitshares_toolkit/commit/55053c244f3057841b86a5b46fad654d7e1ce636
You need to run:
wallet_toggle_delegate_block_production <delegate> true
In order for delegates to produce blocks!
EDIT: doesn't seem to work .. i reverted to the previous commit to keep my delegate online AND producing blocks
Bytemaster fixed an issue with that feature:
It's now called
wallet_enable_delegate_block_production <delegate> true
-
I missed the entire dry run 2, because it became impossible to install on a server with only 1GB RAM.
2GB seems enough. It's more expensive though.
I'm running a VPS with 1GB, you might need this to compile toolkit with only 1GB RAM:
https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04 (https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04)
-
Can someone vote for my delegate?
I just voted for you ;)
Can you vote me for the delegate?
I have been testing for ten days, just solve the forking problem and need to test block produce.
Thank you in advance
my account is networker. You sent me XTS before.
-
Can you vote me for the delegate?
I have been testing for ten days, just solve the forking problem and need to test block produce.
Thank you in advance
my account is networker. You sent me XTS before.
I tried to vote for you but when I make the transaction I have this exception (if I set the trust to 0 the command works):
default (unlocked) >>> wallet_set_delegate_trust_level networker 1
OK
default (unlocked) >>> wallet_transfer 1 XTS spartako spartako
10 assert_exception: Assert Exception
!"WARNING - delegate id 0 bug @ 2":
{}
th_a wallet.cpp:2732 select_delegate_vote
{"real_amount_to_transfer":1,"amount_to_transfer_symbol":"XTS","from_account_name":"spartako","to_account_name":"spartako","memo_message":""}
th_a wallet.cpp:1605 transfer_asset
{}
th_a common_api_client.cpp:492 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:570 execute_command
This is the last row of last_errors command:
{"trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS5KoeF1bUEnvimnP6ydz2adhMXsHvjDrP8","amount":10000000000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSGVteQzFr4naiGCZbGqSGb81HvLVeUSn4D","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000000000,"condition":{"asset_id":13,"delegate_id":318,"type":"withdraw_signature_type","data":{"owner":"XTS6xzWaEaVyZnFb45Z6GoHH5nt2JXaYWwzL","memo":{"one_time_key":"XTS5dtpSJUiseqJUzBa9RqPbhy4S1yfL3VRBn2GEbTaaAYfsqhNrP","encrypted_memo_data":"55957764a0d660de6f059da65750d973a26018a98d9f1d86af7db2dafb8efe78c6b0e6514dea2e125197691e4460d0cbb817b14e4d7edf3332ec44c70adf05a6"}}}}}],"signatures":["2067a9e792f16b5087f9e69784c884de8421d7df5498058ea223cb5690c9cd4831870697b3d97f44191e78c49d12ac2264113b72f91a128c3ed4c1085d588fb8a2","208492d77b7918db73f292708a8ddb6fdc129a865c3294de475f527a8b9ce59b87edf819d3ad31e42ee2b6ab891b5b2db266c4a550eaed31a1cfd1947c60fd9566"]}}
EDIT: I found your name in wallet_list_contact_accounts is showed as NOT registered (because you changed your key)
default (unlocked) >>> wallet_list_contact_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
networker XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO 1
But in blockchain_list_registered_accounts command is registered:
default (unlocked) >>> blockchain_list_registered_accounts networker
NAME (* delegate) KEY REGISTERED VOTES FOR VOTES AGAINST TRUST LEVEL
networker * XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m 2014-06-16T12:49:00 0 0 1
-
They missed to tell us about a recent commit:
https://github.com/BitShares/bitshares_toolkit/commit/55053c244f3057841b86a5b46fad654d7e1ce636
You need to run:
wallet_toggle_delegate_block_production <delegate> true
In order for delegates to produce blocks!
EDIT: doesn't seem to work .. i reverted to the previous commit to keep my delegate online AND producing blocks
Bytemaster fixed an issue with that feature:
It's now called
wallet_enable_delegate_block_production <delegate> true
In my system. there is only wallet_toggle_delegate_block_production command. How to update the command to wallet_enable_delegate_block_production with git command?
I'm not very familiar with git. Please help me!
-
git pull; git submodule update;Then you need to recompile with make
-
Ok so we have some issues today as we are breaking things left and right in preparation for the next dry run.
I renamed wallet_toggle_delegate_block_production to wallet_enable_deleagte_block_product and fixed the bug.
-
I created network account twice. XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV is the first and XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m is the second. You sent my first account xts before, maybe that's the reason first account in your wallet_list_contact_accounts. Can you delete the first one and using the second one? I don't know why I can create account twice. I delete all data for the first account because I was on a fork that time and didn't backup my account. So I reinstall bitshares_toolkit and create my account second time.
Can you vote me for the delegate?
I have been testing for ten days, just solve the forking problem and need to test block produce.
Thank you in advance
my account is networker. You sent me XTS before.
I tried to vote for you but when I make the transaction I have this exception (if I set the trust to 0 the command works):
default (unlocked) >>> wallet_set_delegate_trust_level networker 1
OK
default (unlocked) >>> wallet_transfer 1 XTS spartako spartako
10 assert_exception: Assert Exception
!"WARNING - delegate id 0 bug @ 2":
{}
th_a wallet.cpp:2732 select_delegate_vote
{"real_amount_to_transfer":1,"amount_to_transfer_symbol":"XTS","from_account_name":"spartako","to_account_name":"spartako","memo_message":""}
th_a wallet.cpp:1605 transfer_asset
{}
th_a common_api_client.cpp:492 wallet_transfer
{"command":"wallet_transfer"}
th_a cli.cpp:570 execute_command
This is the last row of last_errors command:
{"trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTS5KoeF1bUEnvimnP6ydz2adhMXsHvjDrP8","amount":10000000000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"XTSGVteQzFr4naiGCZbGqSGb81HvLVeUSn4D","amount":10000,"claim_input_data":""}},{"type":"deposit_op_type","data":{"amount":10000000000,"condition":{"asset_id":13,"delegate_id":318,"type":"withdraw_signature_type","data":{"owner":"XTS6xzWaEaVyZnFb45Z6GoHH5nt2JXaYWwzL","memo":{"one_time_key":"XTS5dtpSJUiseqJUzBa9RqPbhy4S1yfL3VRBn2GEbTaaAYfsqhNrP","encrypted_memo_data":"55957764a0d660de6f059da65750d973a26018a98d9f1d86af7db2dafb8efe78c6b0e6514dea2e125197691e4460d0cbb817b14e4d7edf3332ec44c70adf05a6"}}}}}],"signatures":["2067a9e792f16b5087f9e69784c884de8421d7df5498058ea223cb5690c9cd4831870697b3d97f44191e78c49d12ac2264113b72f91a128c3ed4c1085d588fb8a2","208492d77b7918db73f292708a8ddb6fdc129a865c3294de475f527a8b9ce59b87edf819d3ad31e42ee2b6ab891b5b2db266c4a550eaed31a1cfd1947c60fd9566"]}}
EDIT: I found your name in wallet_list_contact_accounts is showed as NOT registered
default (unlocked) >>> wallet_list_contact_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
networker XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV NO 1
But in blockchain_list_registered_accounts command is registered:
default (unlocked) >>> blockchain_list_registered_accounts networker
NAME (* delegate) KEY REGISTERED VOTES FOR VOTES AGAINST TRUST LEVEL
networker * XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m 2014-06-16T12:49:00 0 0 1
-
I created network account twice. XTS5ebwAWhckHqACuZjxTUFP6oXmrAUXhcZLaGwAssBTVrmMx3sKV is the first and XTS7ridJBN8aG7rGNqdtqwc8Twp8krpx9Qq4dqqRmh8gVnFHJEs5m is the second. You sent my first account xts before, maybe that's the reason first account in your wallet_list_contact_accounts. Can you delete the first one and using the second one? I don't know why I can create account twice. I delete all data for the first account because I was on a fork that time and didn't backup my account. So I reinstall bitshares_toolkit and create my account second time.
Ok solved, I removed your previous account and now the command worked:
default (unlocked) >>> blockchain_list_delegates
ID NAME VOTES FOR VOTES AGAINST NET VOTES BLOCKS PRODUCED BLOCKS MISSED
---------------------------------------------------------
332 networker 1000000 0 9.999192116e-06 % 0 0
-
Ok so we have some issues today as we are breaking things left and right in preparation for the next dry run.
I renamed wallet_toggle_delegate_block_production to wallet_enable_deleagte_block_product and fixed the bug.
+5% It works
-
Can someone vote for my delegate?
default (unlocked) >>> wallet_account_vote_summary alexxy
Delegate For Against
--------------------------------------------------------------
betax 1195164299 0
bts101 709740 0
There is a bug on this.. as I am getting the same results over and over again
[code] wallet_account_vote_summary
account_name: fjlkjflkafjladfk
Delegate For Against
--------------------------------------------------------------
betax 1195164299 0
bts101 709740 0
-
Just voted for
networker
spartako
alexxy
xeroc
testz
bdnoble-1
puppies
betax
Please vote for my delegates too.
wallet_set_delegate_trust_level bitcoiners 10
wallet_set_delegate_trust_level bitcoiners-1 10
wallet_set_delegate_trust_level bitcoiners-2 10
-
What's meaning of wallet_set_delegate_trust_level number ? For example , what does 1and 5 and 10 stands for?
Is there any rule or guide about trust_level when we want to give someone trust? I see somebody give others trust_level 5 or 10 or 1. What's the difference?
After using this command, why we need to transfer XTS to our account?
-
What's meaning of wallet_set_delegate_trust_level number ? For example , what does 1and 5 and 10 stands for?
Is there any rule or guide about trust_level when we want to give someone trust? I see somebody give others trust_level 5 or 10 or 1. What's the difference?
After using this command, why we need to transfer XTS to our account?
xeldal-w (unlocked) >>> help wallet_set_delegate_trust_level
Usage:
wallet_set_delegate_trust_level <delegate_name> [trust_level] Updates the trust placed in a given delegate
Updates the trust placed in a given delegate
Parameters:
delegate_name (account_name, required): the name of the delegate to set trust level on
trust_level (int32_t, optional, defaults to 0): Positive for Trust, Negative for Distrust, 0 for Neutral
Returns:
void
aliases: trust, set_trust
Im not sure 10 is any different that 1, perhaps someone can clarify that.
-
Please vote for my delegates too.
wallet_set_delegate_trust_level bitcoiners 10
wallet_set_delegate_trust_level bitcoiners-1 10
wallet_set_delegate_trust_level bitcoiners-2 10
wallet_set_delegate_trust_level blockchainer 10
Actually I have found this procedure for being sure that I vote for you:
* Set trust to 0 for all your contacts
wallet_set_delegate_trust_level bitcoiners-1 1
wallet_transfer 0.1 XTS spartako spartako
wallet_set_delegate_trust_level bitcoiners-1 0
wallet_set_delegate_trust_level bitcoiners-2 1
wallet_transfer 0.05 XTS spartako spartako
Now you can see some votes for yours delegates that had 0 votes:
354 bitcoiners-2 50000 0 4.999590146e-07 % 0 0
353 bitcoiners-1 40000 0 3.99967206e-07 % 0 0
-
default (unlocked) >>> wallet_set_delegate_trust_level crazybit 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level cgafeng 1
OK
--- there are now 22 active connections to the p2p network
default (unlocked) >>> wallet_set_delegate_trust_level puppies 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level boombastic-ags 1
OK
--- there are now 23 active connections to the p2p network
--- in sync with p2p network
default (unlocked) >>> wallet_set_delegate_trust_level mauritso 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level delegate-alt 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level alexxy 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level coolspeed 1
OK
--- there are now 24 active connections to the p2p network
--- in sync with p2p network
default (unlocked) >>> wallet_set_delegate_trust_level testz-test 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level bitshares 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level dd-1 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level spartako 1
OK
--- there are now 23 active connections to the p2p network
default (unlocked) >>> wallet_set_delegate_trust_level xeroc 1
OK
default (unlocked) >>> wallet_set_delegate_trust_level betax 1
These are my votes from yesterday, who am I missing ?? I believe the to vote against is -1 and in favour is + 1
-
git pull; git submodule update;Then you need to recompile with make
It works. Now I can use new command 8)
-
What's meaning of wallet_set_delegate_trust_level number ? For example , what does 1and 5 and 10 stands for?
Is there any rule or guide about trust_level when we want to give someone trust? I see somebody give others trust_level 5 or 10 or 1. What's the difference?
After using this command, why we need to transfer XTS to our account?
xeldal-w (unlocked) >>> help wallet_set_delegate_trust_level
Usage:
wallet_set_delegate_trust_level <delegate_name> [trust_level] Updates the trust placed in a given delegate
Updates the trust placed in a given delegate
Parameters:
delegate_name (account_name, required): the name of the delegate to set trust level on
trust_level (int32_t, optional, defaults to 0): Positive for Trust, Negative for Distrust, 0 for Neutral
Returns:
void
aliases: trust, set_trust
Im not sure 10 is any different that 1, perhaps someone can clarify that.
Currently, all positive integers are treated the same, and all negative integers are treated the same. See: https://github.com/BitShares/bitshares_toolkit/blob/63798df7ca63f18e1face9ae87b42a9ee00a1383/libraries/wallet/wallet.cpp#L2717-L2723
We should probably restrict the input to only {-1,0,1}.
-
Why we need this command 'wallet_transfer 0.1 XTS spartako spartako'?
How many XTS should we send to ourselves after vote someone?
Please vote for my delegates too.
wallet_set_delegate_trust_level bitcoiners 10
wallet_set_delegate_trust_level bitcoiners-1 10
wallet_set_delegate_trust_level bitcoiners-2 10
wallet_set_delegate_trust_level blockchainer 10
Actually I have found this procedure for being sure that I vote for you:
* Set trust to 0 for all your contacts
wallet_set_delegate_trust_level bitcoiners-1 1
wallet_transfer 0.1 XTS spartako spartako
wallet_set_delegate_trust_level bitcoiners-1 0
wallet_set_delegate_trust_level bitcoiners-2 1
wallet_transfer 0.05 XTS spartako spartako
Now you can see some votes for yours delegates that had 0 votes:
354 bitcoiners-2 50000 0 4.999590146e-07 % 0 0
353 bitcoiners-1 40000 0 3.99967206e-07 % 0 0
-
Toast , I never created following 2 accounts but both showing in my wallet now. not sure what happened ????
wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
mauritso * XTS6sWfWBPSxbYKuxaL7isG87w1YSdvJg6dj1J5qhzzPvYmyVTAFg 2014-06-14T17:34:15 0
-
Why we need this command 'wallet_transfer 0.1 XTS spartako spartako'?
How many XTS should we send to ourselves after vote someone?
Please vote for my delegates too.
wallet_set_delegate_trust_level bitcoiners 10
wallet_set_delegate_trust_level bitcoiners-1 10
wallet_set_delegate_trust_level bitcoiners-2 10
wallet_set_delegate_trust_level blockchainer 10
Actually I have found this procedure for being sure that I vote for you:
* Set trust to 0 for all your contacts
wallet_set_delegate_trust_level bitcoiners-1 1
wallet_transfer 0.1 XTS spartako spartako
wallet_set_delegate_trust_level bitcoiners-1 0
wallet_set_delegate_trust_level bitcoiners-2 1
wallet_transfer 0.05 XTS spartako spartako
Now you can see some votes for yours delegates that had 0 votes:
354 bitcoiners-2 50000 0 4.999590146e-07 % 0 0
353 bitcoiners-1 40000 0 3.99967206e-07 % 0 0
However much vote you want to change. "Vote" is stake-vote
-
Toast , I never created following 2 accounts but both showing in my wallet now. not sure what happened ????
wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
mauritso * XTS6sWfWBPSxbYKuxaL7isG87w1YSdvJg6dj1J5qhzzPvYmyVTAFg 2014-06-14T17:34:15 0
I think this is a known issue. What revision are you on?
default (locked) >>> about
{
"bitshares_toolkit_revision": "eb11334b15a5fcf73754ce582fd4334f38911f65",
"bitshares_toolkit_revision_age": "22 hours ago",
"fc_revision": "1fe26a989b75722b2f6a47c3ae0c2cca1c9e0504",
"fc_revision_age": "24 hours ago",
"compile_date": "compiled on Jun 17 2014 at 13:24:53"
}
-
Why we need this command 'wallet_transfer 0.1 XTS spartako spartako'?
How many XTS should we send to ourselves after vote someone?
Actually I don't understand very well the heuristics used in the wallet but the command wallet_set_delegate_trust_level set only a priority list in your delegate but it doesn't make any vote.
The vote is given only when you make a transaction and it is proportional to the number of coins used in the transaction.
-
Seems we have forks
"blockchain_head_block_num": 19739,
"blockchain_head_block_time": "20140618T154645",
"blockchain_head_block_time_rel": "13 seconds old",
"blockchain_confirmation_requirement": 240,
"blockchain_average_delegate_participation": 62.179487179487182,
"network_num_connections": 20,
"ntp_time": "20140618T154658.561180",
"ntp_error_seconds": -0.0046610000000000002,
"wallet_unlocked_seconds_remaining": 599834,
"wallet_next_block_production_time": "20140618T154815",
"wallet_seconds_until_next_block_production": 77,
"wallet_local_time": "20140618T154658",
"blockchain_random_seed": "dd0a7e13cdc121efbf03cc31a30246124507fc6c",
"blockchain_shares": 10000825938984,
"network_num_connections_max": 128,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140625T142412",
"wallet_version": 100
-
Recent commits have caused database changes that are producing forks. Also the delegates are not enabled by default in the latest build so it requires manual intervention.
We are working in a lot of updates before the next dry run that are taking a tad longer than I thought, but overall things are proceeding steadily.
-
"bitshares_toolkit_revision": "59d5d6abf7c824ab316d725ebe5bdee2ddeb42f4",
"bitshares_toolkit_revision_age": "21 hours ago",
"fc_revision": "1fe26a989b75722b2f6a47c3ae0c2cca1c9e0504",
"fc_revision_age": "25 hours ago",
"compile_date": "compiled on Jun 17 2014 at 16:22:30"
Toast , I never created following 2 accounts but both showing in my wallet now. not sure what happened ????
wallet_list_receive_accounts
NAME (* delegate) KEY REGISTERED TRUST LEVEL
testz-test * XTS8TR6PDqB1kpThaMHXMcJisUbRXWtNGv6ru4njQnGGaLSqsKRV9 2014-06-14T10:18:15 0
mauritso * XTS6sWfWBPSxbYKuxaL7isG87w1YSdvJg6dj1J5qhzzPvYmyVTAFg 2014-06-14T17:34:15 0
I think this is a known issue. What revision are you on?
default (locked) >>> about
{
"bitshares_toolkit_revision": "eb11334b15a5fcf73754ce582fd4334f38911f65",
"bitshares_toolkit_revision_age": "22 hours ago",
"fc_revision": "1fe26a989b75722b2f6a47c3ae0c2cca1c9e0504",
"fc_revision_age": "24 hours ago",
"compile_date": "compiled on Jun 17 2014 at 13:24:53"
}
-
We will look into it.. For now the only thing you can do is export whatever keys you have (wallet_account_list_public_keys -> wallet_account_export_private_key) then make a new wallet and rescan
-
XTS please:
XTS8VwZrdRhvFLf8nGfHfiyScSnmQZEm5dimzBhEezmt7Mujw9g91
-
XTS please:
XTS8VwZrdRhvFLf8nGfHfiyScSnmQZEm5dimzBhEezmt7Mujw9g91
Sent you some.
-
"blockchain_head_block_num": 20171,
"blockchain_head_block_time": "20140618T181715",
"blockchain_head_block_time_rel": "in the future",
"blockchain_confirmation_requirement": 148,
:P
-
A few things:
>>> wallet_withdraw_delegate_pay init-delegate-82 wackou 100000 "test withdraw"
10 assert_exception: Assert Exception
delegate_account_record->delegate_info->pay_balance >= (amount_to_withdraw + required_fees.amount):
{"delegate_account_record":{"id":82,"name":"init-delegate-82","public_data":null,"owner_key":"XTS8Nycs16hWgGQTykcZ8n581scfBePSvyrxAWtfoLYBp4m6VqcCg","active_key_history":[["20140618T180300","XTS8Nycs16hWgGQTykcZ8n581scfBePSvyrxAWtfoLYBp4m6VqcCg"]],"registration_date":"20140601T000000","last_update":"20140601T000000","delegate_info":{"votes_for":83832250149,"votes_against":0,"blocks_produced":177,"blocks_missed":183,"pay_balance":10980294,"next_secret_hash":"f0cebbf2a660d2ecd7c3b8483e9928b504e2e212","last_block_num_produced":20893},"meta_data":null}}
th_a wallet.cpp:1363 withdraw_delegate_pay
{"delegate_name":"init-delegate-82","amount_to_withdraw":100000}
th_a wallet.cpp:1404 withdraw_delegate_pay
{}
th_a common_api_client.cpp:652 wallet_withdraw_delegate_pay
{"command":"wallet_withdraw_delegate_pay"}
th_a cli.cpp:572 execute_command
In particular:
delegate_account_record->delegate_info->pay_balance = 10980294
amount_to_withdraw = 100000
required_fees.amount = not sure exactly how much, thought it was 10000
which means that this should be able to go through, no? Or is there a certain period of time during which the delegates cannot withdraw the xts on their account?
In any case, can someone send me some XTS to register a new delegate? Thanks!
wackou XTS8SCY7ZFAK72uL1jQjWtchDRvf3nz1m7rkDeEn818WRdZiqEo5f
And 2 more questions to end:
- do you have the armory wallet import planned for soon? If not, I imagine there should be a way for me to export the private keys from Armory and import them as bitcoin(?) keys
- how do I import my PTS wallet?
-
And 2 more questions to end:
- do you have the armory wallet import planned for soon? If not, I imagine there should be a way for me to export the private keys from Armory and import them as bitcoin(?) keys
- how do I import my PTS wallet?
Armory import support is planned: https://github.com/BitShares/bitshares_toolkit/issues/90
In the meantime, you can manually import private keys using wallet_import_private_key.
For importing PTS wallet, you can use wallet_import_bitcoin.
-
wallet_import_armory should work now. (actually Issue #90 says it needs testing, care to help test?)
blockchain_get_account_record is now pretty-print for better understanding:
default (unlocked) >>> blockchain_get_account_record init-delegate-82
Record for 'init-delegate-82' (ID 82)
Registered on 2014-Jun-01 00:00:00
Last update was 18 days ago
Owner's key: XTS8Nycs16hWgGQTykcZ8n581scfBePSvyrxAWtfoLYBp4m6VqcCg
History of active keys:
Key XTS8Nycs16hWgGQTykcZ8n581scfBePSvyrxAWtfoLYBp4m6VqcCg last used 17 minutes ago
This account is a delegate.
Votes for: 0.8382%
against: 0.0000%
Blocks produced: 178
missed: 183
Last block produced was Block #21004
Total pay: 11.079392 XTS
Hash of next secret number: 3c5a53a5348842ec013af4b31267ad9c2e01e4b5
No meta data.
Your balance is 11.079 XTS and so you can do:
sage:
wallet_withdraw_delegate_pay <delegate_name> <to_account_name> <amount_to_withdraw> [memo] Used to transfer some of the delegates pay from their balance
Used to transfer some of the delegates pay from their balance
Parameters:
delegate_name (account_name, required): the delegate who's pay is being cashed out
to_account_name (account_name, required): the account that should receive the funds
amount_to_withdraw (real_amount, required): the amount to withdraw
memo (string, optional, defaults to "payday"): memo to add to transaction
Returns:
signed_transaction
Used like this:
wallet_withdraw_delegate_pay init-delegate-82 init-delegate-82 11.0 and it should work.
-
When is the "ntp_error_seconds" calculated?
I've been running the client for some time and I noticed this: "ntp_error_seconds": 5.8529650000000002 .
I've setup an ntp daemon and synchronized my time.
However the ntp_error_seconds remained the same for at least 10 minutes.
Does this mean I'm a cheater now ?
-
wallet_import_armory should work now. (actually Issue #90 says it needs testing, care to help test?)
blockchain_get_account_record is now pretty-print for better understanding:
[...]
wallet_withdraw_delegate_pay init-delegate-82 init-delegate-82 11.0 and it should work.
Thanks! Gotta get some sleep now, but I'll test the armory import first thing tomorrow. Cheers!
-
When is the "ntp_error_seconds" calculated?
I've been running the client for some time and I noticed this: "ntp_error_seconds": 5.8529650000000002 .
I've setup an ntp daemon and synchronized my time.
However the ntp_error_seconds remained the same for at least 10 minutes.
Does this mean I'm a cheater now ?
Every 30 minutes. If you changed your time then that could be an issue for about 30 minutes.
-
Every 30 minutes. If you changed your time then that could be an issue for about 30 minutes.
Yes, it synchronized now. Thanks.
-
crash with wallet_clear_pending_transactions
default (unlocked) >>> wallet_clear_pending_transactions
Program received signal SIGSEGV, Segmentation fault.
0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520) at /usr/include/c++/4.8/bits/stl_construct.h:75
75 { ::new(static_cast<void*>(__p)) _T1(std::forward<_Args>(__args)...); }
(gdb) bt
#0 0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520)
at /usr/include/c++/4.8/bits/stl_construct.h:75
#1 __uninit_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*>
(__result=0x174f520, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:75
#2 uninitialized_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*> (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:117
#3 __uninitialized_copy_a<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*, fc::array<unsigned char, 65ul> > (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:258
#4 vector (__x=..., this=0x7ffff50fff58) at /usr/include/c++/4.8/bits/stl_vector.h:316
#5 signed_transaction (this=0x7ffff50ffeb0, this@entry=0x0) at /home/alt/workspace/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/transaction.hpp:142
#6 bts::wallet::transaction_data::transaction_data (this=this@entry=0x7ffff50ffeb0)
at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:145
#7 0x0000000000876025 in wallet_record (this=0x7ffff50ffea8) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:109
#8 pair (this=0x7ffff50ffe90) at /usr/include/c++/4.8/bits/stl_pair.h:127
#9 bts::wallet::wallet_db::clear_pending_transactions (this=0x15d1070) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/wallet_db.cpp:332
#10 0x000000000079d2cb in bts::rpc_stubs::common_api_client::wallet_clear_pending_transactions (this=0x1546978)
at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_client.cpp:390
#11 0x00000000006f2d55 in bts::rpc_stubs::common_api_rpc_server::wallet_clear_pending_transactions_positional (this=this@entry=0x1548290, json_connection=...,
parameters=...) at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:1231
#12 0x000000000076a231 in bts::rpc_stubs::common_api_rpc_server::direct_invoke_positional_method (this=0x1548290, method_name=..., parameters=...)
at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:6681
#13 0x00000000006530b0 in bts::rpc::detail::rpc_server_impl::dispatch_authenticated_method (this=this@entry=0x1548290, method_data=..., arguments_from_caller=...)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:393
#14 0x000000000064d413 in direct_invoke_method (arguments=..., method_name=..., this=0x1548290)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:465
#15 bts::rpc::rpc_server::direct_invoke_method (this=<optimized out>, method_name=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:677
#16 0x000000000067e7b0 in bts::cli::detail::cli_impl::execute_command (this=this@entry=0x16053e0, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:568
#17 0x0000000000680998 in bts::cli::detail::cli_impl::execute_interactive_command (this=0x16053e0, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:556
#18 0x000000000065de0d in bts::cli::cli::execute_interactive_command (this=<optimized out>, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1685
#19 0x000000000067cc5a in bts::cli::detail::cli_impl::parse_and_execute_interactive_command (this=this@entry=0x16053e0, command=..., argument_stream=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:163
#20 0x000000000067d6bb in bts::cli::detail::cli_impl::execute_command_line (this=this@entry=0x16053e0, line=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:208
#21 0x000000000065d44d in bts::cli::detail::cli_impl::process_commands (this=this@entry=0x16053e0, input_stream=<optimized out>)
---Type <return> to continue, or q <return> to quit---
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1589
#22 0x000000000065daad in start (this=0x16053e0) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:82
#23 bts::cli::cli::start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1636
#24 0x0000000000589524 in start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:308
#25 operator() (__closure=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:1809
#26 fc::detail::void_functor_run<bts::client::client::start()::__lambda0>::run(void *, void *) (functor=<optimized out>, prom=0x15f1ca0)
at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:54
#27 0x00000000005f9a6d in fc::task_base::run_impl (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:38
#28 0x00000000005f9e15 in fc::task_base::run (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:29
#29 0x00000000005f83b7 in run_next_task (this=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:347
#30 fc::thread_d::process_tasks (this=this@entry=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:370
#31 0x00000000005f86b1 in fc::thread_d::start_process_tasks (my=22316000) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:328
#32 0x0000000000ab5cee in make_fcontext ()
#33 0x00000000015483e0 in ?? ()
#34 0x0000000000000000 in ?? ()
-
why not recruit alt into the team, this dude is remarkable :D
-
why not recruit alt into the team, this dude is remarkable :D
+1
Sent from my SCH-I535 using Tapatalk
-
thands for your believe, so happy :)
-
wallet_withdraw_delegate_pay seems still generate a fork.
delegate (unlocked) >>> blockchain_list_forks
[
5624,
11312,
11338,
21322,
21325,
21340,
21449
]
delegate (unlocked) >>> info
{
"blockchain_head_block_num": 21589,
"blockchain_head_block_time": "20140619T021600",
"blockchain_head_block_time_rel": "10 seconds old",
"blockchain_confirmation_requirement": 1,
"blockchain_average_delegate_participation": 73.596358118361152,
"network_num_connections": 1,
"ntp_time": "20140619T021610.662404",
"ntp_error_seconds": -0.0084840000000000002,
"wallet_unlocked_seconds_remaining": 99999960,
"wallet_next_block_production_time": "20140619T021615",
"wallet_seconds_until_next_block_production": 5,
"wallet_local_time": "20140619T021610",
"blockchain_random_seed": "2c8b569da33e1990d77d46dfdfcfc43a17d8106f",
"blockchain_shares": 10001009030968,
"network_num_connections_max": 999,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170819T120210",
"wallet_version": 100
}
delegate (unlocked) >>> wallet_withdraw_delegate_pay init-delegate-17 delegate-alt 23 "withdraw"
10 assert_exception: Assert Exception
delegate_account_record->delegate_info->pay_balance >= (amount_to_withdraw + required_fees.amount):
{"delegate_account_record":{"id":17,"name":"init-delegate-17","public_data":null,"owner_key":"XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM","active_key_his
tory":[["20140618T234015","XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM"]],"registration_date":"20140601T000000","last_update":"20140601T000000","delegate_info
":{"votes_for":87931672469,"votes_against":0,"blocks_produced":335,"blocks_missed":24,"pay_balance":971565,"next_secret_hash":"ffed3e1abe7f8aa03abb6a8c67de1b3eae31433d"
,"last_block_num_produced":21408},"meta_data":null}}
th_a wallet.cpp:1364 withdraw_delegate_pay
{"delegate_name":"init-delegate-17","amount_to_withdraw":23}
th_a wallet.cpp:1405 withdraw_delegate_pay
{}
th_a common_api_client.cpp:652 wallet_withdraw_delegate_pay
{"command":"wallet_withdraw_delegate_pay"}
th_a cli.cpp:580 execute_command
delegate (unlocked) >>> blockchain_list_forks
[
5624,
11312,
11338,
21322,
21325,
21340,
21449,
21589
]
client will choose to the main chain automatic.
another problem is the balance is add 23 XTS, and this block will list in the history with blk is 0.0
delegate (unlocked) >>> wallet_account_balance
delegate-alt:
...
25.774298 XTS
delegate (unlocked) >>> wallet_account_transaction_history
...
21385.0 2014-06-19T01:07:00 dorian delegate-alt ... 9,923.000000 DRINK 0.000000 XTS 038cc1cb
21386.0 2014-06-19T01:07:15 dorian delegate-alt ... 20.000000 LOVE 0.000000 XTS 2b7c117a
0.0 2014-06-19T02:16:15 init-delegate-17 delegate-alt withdraw 23.000000 XTS 0.000000 XTS 44a7d36c
-
wallet_withdraw_delegate_pay seems still generate a fork.
delegate (unlocked) >>> blockchain_list_forks
[
5624,
11312,
11338,
21322,
21325,
21340,
21449
]
delegate (unlocked) >>> info
{
"blockchain_head_block_num": 21589,
"blockchain_head_block_time": "20140619T021600",
"blockchain_head_block_time_rel": "10 seconds old",
"blockchain_confirmation_requirement": 1,
"blockchain_average_delegate_participation": 73.596358118361152,
"network_num_connections": 1,
"ntp_time": "20140619T021610.662404",
"ntp_error_seconds": -0.0084840000000000002,
"wallet_unlocked_seconds_remaining": 99999960,
"wallet_next_block_production_time": "20140619T021615",
"wallet_seconds_until_next_block_production": 5,
"wallet_local_time": "20140619T021610",
"blockchain_random_seed": "2c8b569da33e1990d77d46dfdfcfc43a17d8106f",
"blockchain_shares": 10001009030968,
"network_num_connections_max": 999,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170819T120210",
"wallet_version": 100
}
delegate (unlocked) >>> wallet_withdraw_delegate_pay init-delegate-17 delegate-alt 23 "withdraw"
10 assert_exception: Assert Exception
delegate_account_record->delegate_info->pay_balance >= (amount_to_withdraw + required_fees.amount):
{"delegate_account_record":{"id":17,"name":"init-delegate-17","public_data":null,"owner_key":"XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM","active_key_his
tory":[["20140618T234015","XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM"]],"registration_date":"20140601T000000","last_update":"20140601T000000","delegate_info
":{"votes_for":87931672469,"votes_against":0,"blocks_produced":335,"blocks_missed":24,"pay_balance":971565,"next_secret_hash":"ffed3e1abe7f8aa03abb6a8c67de1b3eae31433d"
,"last_block_num_produced":21408},"meta_data":null}}
th_a wallet.cpp:1364 withdraw_delegate_pay
{"delegate_name":"init-delegate-17","amount_to_withdraw":23}
th_a wallet.cpp:1405 withdraw_delegate_pay
{}
th_a common_api_client.cpp:652 wallet_withdraw_delegate_pay
{"command":"wallet_withdraw_delegate_pay"}
th_a cli.cpp:580 execute_command
delegate (unlocked) >>> blockchain_list_forks
[
5624,
11312,
11338,
21322,
21325,
21340,
21449,
21589
]
client will choose to the main chain automatic.
another problem is the balance is add 23 XTS, and this block will list in the history with blk is 0.0
delegate (unlocked) >>> wallet_account_balance
delegate-alt:
...
25.774298 XTS
delegate (unlocked) >>> wallet_account_transaction_history
...
21385.0 2014-06-19T01:07:00 dorian delegate-alt ... 9,923.000000 DRINK 0.000000 XTS 038cc1cb
21386.0 2014-06-19T01:07:15 dorian delegate-alt ... 20.000000 LOVE 0.000000 XTS 2b7c117a
0.0 2014-06-19T02:16:15 init-delegate-17 delegate-alt withdraw 23.000000 XTS 0.000000 XTS 44a7d36c
I've done the following and I see no issues (except one pending transaction):
emski (unlocked) >>> wallet_account_transaction_history
BLK.TRX TIMESTAMP FROM TO MEMO AMOUNT FEE ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
22245.0 2014-06-19T06:11:15 init-delegate-4 emski payday 1.000000 XTS 0.010000 XTS 74a7399a
22251.0 2014-06-19T06:14:30 init-delegate-1 emski payday 0.100000 XTS 0.010000 XTS 25058cfd
pending 2014-06-19T06:14:42 init-delegate-1 emski payday 0.500000 XTS 0.010000 XTS 923bb6ee
22252.0 2014-06-19T06:14:45 init-delegate-1 emski payday 0.500000 XTS 0.010000 XTS e1e666c8
22257.0 2014-06-19T06:17:45 init-delegate-1 emski payday 0.040000 XTS 0.010000 XTS ccd77580
22259.0 2014-06-19T06:18:45 init-delegate-2 emski payday 22.000000 XTS 0.010000 XTS 5aa7bbba
22262.1 2014-06-19T06:20:00 init-delegate-3 emski payday 21.000000 XTS 0.010000 XTS 1dcd873f
22262.0 2014-06-19T06:20:00 init-delegate-2 emski payday 0.011000 XTS 0.010000 XTS 09e69e5b
22263.0 2014-06-19T06:20:45 init-delegate-4 emski payday 21.000000 XTS 0.010000 XTS 6b59416f
22263.1 2014-06-19T06:20:45 init-delegate-25 emski payday 22.000000 XTS 0.010000 XTS ccba5442
22276.0 2014-06-19T06:27:45 emski emski register emski 0.000000 XTS 0.010001 XTS 99f63e17
22279.1 2014-06-19T06:30:00 emski emski update emski 0.000000 XTS 0.010002 XTS 7aaa97e4
22279.0 2014-06-19T06:30:00 emski emski update emski as a delegate 0.000000 XTS 10.495714 XTS 9988b6dd
emski (unlocked) >>> wallet_account_balance
emski:
77.135283 XTS
emski (unlocked) >>> blockchain_list_forks
[
5624,
11312,
11338,
20506,
21322,
21325,
21340,
21449,
21788,
21934,
22011,
22139,
22160,
22171,
22236
]
--- there are now 23 active connections to the p2p network
--- in sync with p2p network
emski (unlocked) >>> get_info
{
"blockchain_head_block_num": 22296,
"blockchain_head_block_time": "20140619T063945",
"blockchain_head_block_time_rel": "14 seconds old",
"blockchain_confirmation_requirement": 254,
"blockchain_average_delegate_participation": 68.648266100495405,
"network_num_connections": 23,
"ntp_time": "20140619T063959.374775",
"ntp_error_seconds": -0.002032,
"wallet_unlocked_seconds_remaining": 99959227,
"wallet_next_block_production_time": "20140619T064345",
"wallet_seconds_until_next_block_production": 226,
"wallet_local_time": "20140619T063959",
"blockchain_random_seed": "1773c2f0abffa39c3cf82c296076c6270a4d9126",
"blockchain_shares": 10001026424724,
"network_num_connections_max": 60,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20170819T050706",
"wallet_version": 100
}
emski (unlocked) >>> about
{
"bitshares_toolkit_revision": "c21fdf60ab39798102662080ff896da73443d6f2",
"bitshares_toolkit_revision_age": "13 hours ago",
"fc_revision": "9002b024693a8ac749a4d5f0b64821b2a1e8eab9",
"fc_revision_age": "35 hours ago",
"compile_date": "compiled on Jun 18 2014 at 22:17:43"
}
-
I have test again just now.
yes it can works without issue this time.
I think I did not change anything.
If it's possible that the fork reason is some delegate node didn't update and refuse my block ?
-
I have do a press test, make 200 transfers in several seconds.
seems very good, all transactions is confirmed in 1 minute.
you can see block_num 22398 && 22399
blockchain_get_block_by_number 22399
-
Is it normal for me to see that much difference on this message:
--- syncing with p2p network, XXX blocks left to fetch
--- syncing with p2p network, 4523 blocks left to fetch
--- there are now 23 active connections to the p2p network
--- syncing with p2p network, 3762 blocks left to fetch
--- syncing with p2p network, 387 blocks left to fetch
--- there are now 22 active connections to the p2p network
--- in sync with p2p network
--- there are now 23 active connections to the p2p network
--- in sync with p2p network
--- there are now 24 active connections to the p2p network
--- syncing with p2p network, 4527 blocks left to fetch
--- there are now 25 active connections to the p2p network
--- there are now 24 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 24 active connections to the p2p network
--- syncing with p2p network, 4528 blocks left to fetch
--- there are now 23 active connections to the p2p network
emski (unlocked) >>> get_info
{
"blockchain_head_block_num": 22474,
"blockchain_head_block_time": "20140619T083400",
-
wallet_import_armory should work now. (actually Issue #90 says it needs testing, care to help test?)
Armory import seems not implemented at all yet... Tried it with actual values, as well as random values, gives OK all the time
>>> wallet_import_armory
wallet_filename: /this/file/does/not/exist
passphrase:
account_name: well, this is not an account
OK
-
I'm on:
>>> about
{
"bitshares_toolkit_revision": "cfcfcb24935067458c221cfc382d3843bf4f5d68",
"bitshares_toolkit_revision_age": "7 hours ago",
"fc_revision": "9002b024693a8ac749a4d5f0b64821b2a1e8eab9",
"fc_revision_age": "38 hours ago",
"compile_date": "compiled on Jun 19 2014 at 10:46:58"
}
-
try 2000 failed, the pending number is 1762, maybe not broadcast out by client.
always pending there.
start from block 22635
I have do a press test, make 200 transfers in several seconds.
seems very good, all transactions is confirmed in 1 minute.
you can see block_num 22398 && 22399
blockchain_get_block_by_number 22399
-
fork happen now .......
can't see all these transaction now
22398 or 22635
before I test press 2000, 22398 is there.
now, change to another chain?
237 confirms is not safe?
try 2000 failed, the pending number is 1762, maybe not broadcast out by client.
always pending there.
start from block 22635
I have do a press test, make 200 transfers in several seconds.
seems very good, all transactions is confirmed in 1 minute.
you can see block_num 22398 && 22399
blockchain_get_block_by_number 22399
-
@toast: Is rpc yet fully implemented?
When i try to create a rpc-connection to my client at normal rpc-port i get timed out. It seems, some infinite loop freezes my computer fore some minutes until client crash.
try for yourself:
curl --user 'your_username' --data-binary '{"jsonrpc":"1.0","id":"my_id","method":"wallet_open","params":["default"]}' -H 'content-type:text/plain;' http://127.0.0.1:5679
When connecting over rpc-http port and adapt the path to /rpc, all is fine, though some void returning methods as
"wallet_open, wallet_create ..." sometimes return empty responses with Content-Length: 31.
Related to further processing this seems some unevaluable. Could you change that to standard rpc response?
-
@toast: Is rpc yet fully implemented?
When i try to create a rpc-connection to my client at normal rpc-port i get timed out. It seems, some infinite loop freezes my computer fore some minutes until client crash.
try for yourself:
curl --user 'your_username' --data-binary '{"jsonrpc":"1.0","id":"my_id","method":"wallet_open","params":["default"]}' -H 'content-type:text/plain;' http://127.0.0.1:5679
When connecting over rpc-http port and adapt the path to /rpc, all is fine, though some void returning methods as
"wallet_open, wallet_create ..." sometimes return empty responses with Content-Length: 31.
Related to further processing this seems some unevaluable. Could you change that to standard rpc response?
Works for me.
-
crash with wallet_clear_pending_transactions
default (unlocked) >>> wallet_clear_pending_transactions
Program received signal SIGSEGV, Segmentation fault.
0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520) at /usr/include/c++/4.8/bits/stl_construct.h:75
75 { ::new(static_cast<void*>(__p)) _T1(std::forward<_Args>(__args)...); }
(gdb) bt
#0 0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520)
at /usr/include/c++/4.8/bits/stl_construct.h:75
#1 __uninit_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*>
(__result=0x174f520, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:75
#2 uninitialized_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*> (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:117
#3 __uninitialized_copy_a<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*, fc::array<unsigned char, 65ul> > (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:258
#4 vector (__x=..., this=0x7ffff50fff58) at /usr/include/c++/4.8/bits/stl_vector.h:316
#5 signed_transaction (this=0x7ffff50ffeb0, this@entry=0x0) at /home/alt/workspace/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/transaction.hpp:142
#6 bts::wallet::transaction_data::transaction_data (this=this@entry=0x7ffff50ffeb0)
at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:145
#7 0x0000000000876025 in wallet_record (this=0x7ffff50ffea8) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:109
#8 pair (this=0x7ffff50ffe90) at /usr/include/c++/4.8/bits/stl_pair.h:127
#9 bts::wallet::wallet_db::clear_pending_transactions (this=0x15d1070) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/wallet_db.cpp:332
#10 0x000000000079d2cb in bts::rpc_stubs::common_api_client::wallet_clear_pending_transactions (this=0x1546978)
at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_client.cpp:390
#11 0x00000000006f2d55 in bts::rpc_stubs::common_api_rpc_server::wallet_clear_pending_transactions_positional (this=this@entry=0x1548290, json_connection=...,
parameters=...) at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:1231
#12 0x000000000076a231 in bts::rpc_stubs::common_api_rpc_server::direct_invoke_positional_method (this=0x1548290, method_name=..., parameters=...)
at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:6681
#13 0x00000000006530b0 in bts::rpc::detail::rpc_server_impl::dispatch_authenticated_method (this=this@entry=0x1548290, method_data=..., arguments_from_caller=...)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:393
#14 0x000000000064d413 in direct_invoke_method (arguments=..., method_name=..., this=0x1548290)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:465
#15 bts::rpc::rpc_server::direct_invoke_method (this=<optimized out>, method_name=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:677
#16 0x000000000067e7b0 in bts::cli::detail::cli_impl::execute_command (this=this@entry=0x16053e0, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:568
#17 0x0000000000680998 in bts::cli::detail::cli_impl::execute_interactive_command (this=0x16053e0, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:556
#18 0x000000000065de0d in bts::cli::cli::execute_interactive_command (this=<optimized out>, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1685
#19 0x000000000067cc5a in bts::cli::detail::cli_impl::parse_and_execute_interactive_command (this=this@entry=0x16053e0, command=..., argument_stream=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:163
#20 0x000000000067d6bb in bts::cli::detail::cli_impl::execute_command_line (this=this@entry=0x16053e0, line=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:208
#21 0x000000000065d44d in bts::cli::detail::cli_impl::process_commands (this=this@entry=0x16053e0, input_stream=<optimized out>)
---Type <return> to continue, or q <return> to quit---
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1589
#22 0x000000000065daad in start (this=0x16053e0) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:82
#23 bts::cli::cli::start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1636
#24 0x0000000000589524 in start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:308
#25 operator() (__closure=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:1809
#26 fc::detail::void_functor_run<bts::client::client::start()::__lambda0>::run(void *, void *) (functor=<optimized out>, prom=0x15f1ca0)
at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:54
#27 0x00000000005f9a6d in fc::task_base::run_impl (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:38
#28 0x00000000005f9e15 in fc::task_base::run (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:29
#29 0x00000000005f83b7 in run_next_task (this=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:347
#30 fc::thread_d::process_tasks (this=this@entry=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:370
#31 0x00000000005f86b1 in fc::thread_d::start_process_tasks (my=22316000) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:328
#32 0x0000000000ab5cee in make_fcontext ()
#33 0x00000000015483e0 in ?? ()
#34 0x0000000000000000 in ?? ()
This has been fixed.
-
Thanks, it works.
another issue.
some transmit from alt to delegate-alt are pending in both two node.
clear_pengding_transactions can clear these transmit in node alt, but not clear in node delegate-alt.
delegate (unlocked) >>> wallet_clear_pending_transactions
OK
delegate (unlocked) >>> wallet_account_transaction_history
.....
pending 2014-06-19T10:28:45 alt delegate-alt test flood... 10.000000 DRINK 0.000000 XTS 01e5be55
pending 2014-06-19T10:28:45 alt delegate-alt test flood... 11.000000 DRINK 0.000000 XTS 026b787c
pending 2014-06-19T10:28:45 alt delegate-alt test flood... 10.000000 DRINK 0.000000 XTS 17a8965b
pending 2014-06-19T10:28:45 alt delegate-alt test flood... 11.000000 DRINK 0.000000 XTS 58d8f9be
pending 2014-06-19T10:30:15 alt delegate-alt test flood... 11.000000 DRINK 0.000000 XTS 83c3757e
pending 2014-06-19T10:30:15 alt delegate-alt test flood... 11.000000 DRINK 0.000000 XTS af8ba6db
pending 2014-06-19T10:30:15 alt delegate-alt test flood... 10.000000 DRINK 0.000000 XTS 1abf5dfe
crash with wallet_clear_pending_transactions
default (unlocked) >>> wallet_clear_pending_transactions
Program received signal SIGSEGV, Segmentation fault.
0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520) at /usr/include/c++/4.8/bits/stl_construct.h:75
75 { ::new(static_cast<void*>(__p)) _T1(std::forward<_Args>(__args)...); }
(gdb) bt
#0 0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520)
at /usr/include/c++/4.8/bits/stl_construct.h:75
#1 __uninit_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*>
(__result=0x174f520, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:75
#2 uninitialized_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*> (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:117
#3 __uninitialized_copy_a<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*, fc::array<unsigned char, 65ul> > (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:258
#4 vector (__x=..., this=0x7ffff50fff58) at /usr/include/c++/4.8/bits/stl_vector.h:316
#5 signed_transaction (this=0x7ffff50ffeb0, this@entry=0x0) at /home/alt/workspace/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/transaction.hpp:142
#6 bts::wallet::transaction_data::transaction_data (this=this@entry=0x7ffff50ffeb0)
at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:145
#7 0x0000000000876025 in wallet_record (this=0x7ffff50ffea8) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:109
#8 pair (this=0x7ffff50ffe90) at /usr/include/c++/4.8/bits/stl_pair.h:127
#9 bts::wallet::wallet_db::clear_pending_transactions (this=0x15d1070) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/wallet_db.cpp:332
#10 0x000000000079d2cb in bts::rpc_stubs::common_api_client::wallet_clear_pending_transactions (this=0x1546978)
at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_client.cpp:390
#11 0x00000000006f2d55 in bts::rpc_stubs::common_api_rpc_server::wallet_clear_pending_transactions_positional (this=this@entry=0x1548290, json_connection=...,
parameters=...) at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:1231
#12 0x000000000076a231 in bts::rpc_stubs::common_api_rpc_server::direct_invoke_positional_method (this=0x1548290, method_name=..., parameters=...)
at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:6681
#13 0x00000000006530b0 in bts::rpc::detail::rpc_server_impl::dispatch_authenticated_method (this=this@entry=0x1548290, method_data=..., arguments_from_caller=...)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:393
#14 0x000000000064d413 in direct_invoke_method (arguments=..., method_name=..., this=0x1548290)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:465
#15 bts::rpc::rpc_server::direct_invoke_method (this=<optimized out>, method_name=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:677
#16 0x000000000067e7b0 in bts::cli::detail::cli_impl::execute_command (this=this@entry=0x16053e0, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:568
#17 0x0000000000680998 in bts::cli::detail::cli_impl::execute_interactive_command (this=0x16053e0, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:556
#18 0x000000000065de0d in bts::cli::cli::execute_interactive_command (this=<optimized out>, command=..., arguments=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1685
#19 0x000000000067cc5a in bts::cli::detail::cli_impl::parse_and_execute_interactive_command (this=this@entry=0x16053e0, command=..., argument_stream=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:163
#20 0x000000000067d6bb in bts::cli::detail::cli_impl::execute_command_line (this=this@entry=0x16053e0, line=...)
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:208
#21 0x000000000065d44d in bts::cli::detail::cli_impl::process_commands (this=this@entry=0x16053e0, input_stream=<optimized out>)
---Type <return> to continue, or q <return> to quit---
at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1589
#22 0x000000000065daad in start (this=0x16053e0) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:82
#23 bts::cli::cli::start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1636
#24 0x0000000000589524 in start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:308
#25 operator() (__closure=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:1809
#26 fc::detail::void_functor_run<bts::client::client::start()::__lambda0>::run(void *, void *) (functor=<optimized out>, prom=0x15f1ca0)
at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:54
#27 0x00000000005f9a6d in fc::task_base::run_impl (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:38
#28 0x00000000005f9e15 in fc::task_base::run (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:29
#29 0x00000000005f83b7 in run_next_task (this=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:347
#30 fc::thread_d::process_tasks (this=this@entry=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:370
#31 0x00000000005f86b1 in fc::thread_d::start_process_tasks (my=22316000) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:328
#32 0x0000000000ab5cee in make_fcontext ()
#33 0x00000000015483e0 in ?? ()
#34 0x0000000000000000 in ?? ()
This has been fixed.
-
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?
-
same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?
-
same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?
suppose there is something wrong , how can a name map to 2 different private keys?
-
same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?
suppose there is something wrong , how can a name map to 2 different private keys?
Every account has the 'account key' and under the account key are any number of 'balance keys' that are generated when someone sends you a titan transaction or you import keys into the account from an external source.
In theory no funds should be sent directly to an 'account key', but only to a key derived from the account key.
Importing the key into two places will probably confuse the wallet right now.
-
More confused now. Could you please tell the diff among
1)Public key which we used as wallet address
2)what is account key? Is it the same as public key
3) what is balance key?
Is there any command that i can use to discover these keys
same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?
suppose there is something wrong , how can a name map to 2 different private keys?
Every account has the 'account key' and under the account key are any number of 'balance keys' that are generated when someone sends you a titan transaction or you import keys into the account from an external source.
In theory no funds should be sent directly to an 'account key', but only to a key derived from the account key.
Importing the key into two places will probably confuse the wallet right now.
-
More confused now. Could you please tell the diff among
1)Public key which we used as wallet address
2)what is account key? Is it the same as public key
3) what is balance key?
Is there any command that i can use to discover these keys
same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?
suppose there is something wrong , how can a name map to 2 different private keys?
Every account has the 'account key' and under the account key are any number of 'balance keys' that are generated when someone sends you a titan transaction or you import keys into the account from an external source.
In theory no funds should be sent directly to an 'account key', but only to a key derived from the account key.
Importing the key into two places will probably confuse the wallet right now.
In an attempt to simplify concepts we have decided to NOT overload the term 'address' as used in bitcoin.
Accounts have Public Keys which we are calling your Account Key and contain automatically generated addresses from TITAN or from imported bitcoin wallets.
An address is the hash of a public key used to control a balance (spendable entry in the blockchain).
Our goal is that users never have to think much about their Account Keys and NEVER about their addresses.
-
+5% for that brief description .. we should add that to the techtalk about titan
-
+5% for that brief description .. we should add that to the techtalk about titan
+1
-
How to import PTS wallet?
I see the bitcoin, electrum, multibit, armory, and keyhotee import commands.
Is there no command for PTS yet?
-
would you mind to describe a little bit more about the wallet data structure, i can not sort out the data structure diagram base on the program,since there are many table mapping there, know you are quite busy on the development, just let go if it need too much time to make it clear :D, don't want to spend too much of your time.
fc::optional<wallet_master_key_record> wallet_master_key;
unordered_map< address, wallet_key_record > keys;
unordered_map< address, address > btc_to_bts_address;
unordered_map< address, int32_t > address_to_account_wallet_record_index;
unordered_map< account_id_type, int32_t > account_id_to_wallet_record_index;
map< string, int32_t > name_to_account_wallet_record_index;
unordered_map<address,wallet_market_order_status_record> market_orders;
/** maps wallet_record_index to accounts */
unordered_map< int32_t,wallet_account_record > accounts;
unordered_map< transaction_id_type, wallet_transaction_record > transactions;
unordered_map< balance_id_type,wallet_balance_record > balances;
map<string,wallet_asset_record> assets;
map<property_enum, wallet_property_record> properties;
map< string, wallet_setting_record > settings;
i found there are many mapping in the wallet db,would you please describe a bit more about the wallet data structure?
same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?
suppose there is something wrong , how can a name map to 2 different private keys?
Every account has the 'account key' and under the account key are any number of 'balance keys' that are generated when someone sends you a titan transaction or you import keys into the account from an external source.
In theory no funds should be sent directly to an 'account key', but only to a key derived from the account key.
Importing the key into two places will probably confuse the wallet right now.
-
How to import PTS wallet?
I see the bitcoin, electrum, multibit, armory, and keyhotee import commands.
Is there no command for PTS yet?
You can either import the private key directly or you can import the PTS wallet.dat using the bitcoin import.
Sent from my iPhone using Tapatalk
-
if my understanding is not wrong, the command wallet_import_bitcoin can be used for pts wallet import, since pts is clone from bitcoin qt,
How to import PTS wallet?
I see the bitcoin, electrum, multibit, armory, and keyhotee import commands.
Is there no command for PTS yet?
-
I did a dumpprivkey <ptsAddress> in the Bitshares-PTS wallet console
I took this private key and tryed both
bitcoin_importprivkey and wallet_import_private_key
neither worked
I also uploaded the wallet.dat to my server and used " wallet_import_bitcoin "~/imports/wallet.dat" "
it didn't like that either. says it can't find wallet.dat
I tried moving the dat file to various places but it doesn't want to find it.
Is there a particular place it needs to be or a particular way i need to reference it?
-
How to import PTS wallet?
I see the bitcoin, electrum, multibit, armory, and keyhotee import commands.
Is there no command for PTS yet?
Use import bitcoin.
-
I did a dumpprivkey <ptsAddress> in the Bitshares-PTS wallet console
I took this private key and tryed both
bitcoin_importprivkey and wallet_import_private_key
neither worked
I also uploaded the wallet.dat to my server and used " wallet_import_bitcoin "~/imports/wallet.dat" "
it didn't like that either. says it can't find wallet.dat
I tried moving the dat file to various places but it doesn't want to find it.
Is there a particular place it needs to be or a particular way i need to reference it?
I imported my PTS wallet with wallet_import_bitcoin <full path to wallet.dat>
-
In an attempt to simplify concepts we have decided to NOT overload the term 'address' as used in bitcoin.
Accounts have Public Keys which we are calling your Account Key and contain automatically generated addresses from TITAN or from imported bitcoin wallets.
An address is the hash of a public key used to control a balance (spendable entry in the blockchain).
Our goal is that users never have to think much about their Account Keys and NEVER about their addresses.
https://github.com/BitShares/bitshares_toolkit/wiki/Wallets,-accounts,-owner-&-active-keys,-addresses---The-differences-between-Bitcoin-and-Bitshares
-
I got at least a little further.
Looks i was referencing the location incorrectly
instead of ~/Imports/wallet.dat
should be /root/Imports/wallet.dat
It seems to have found it this way but when it asks for "imported wallet passphrase" (it doesn't have one)
I just hit enter, leaving blank and i get aborted
xeldal-w (unlocked) >>> wallet_import_bitcoin "/root/Imports/wallet.dat"
passphrase:
account_name: PTS-jmob
imported wallet passphrase:
Command aborted
-
I got at least a little further.
Looks i was referencing the location incorrectly
instead of ~/Imports/wallet.dat
should be /root/Imports/wallet.dat
It seems to have found it this way but when it asks for "imported wallet passphrase" (it doesn't have one)
I just hit enter, leaving blank and i get aborted
xeldal-w (unlocked) >>> wallet_import_bitcoin "/root/Imports/wallet.dat"
passphrase:
account_name: PTS-jmob
imported wallet passphrase:
Command aborted
It expects your PTS wallet to have a password. How about setting it up?
-
Ok i figured it out. 2 things.
1 you need to wallet_account_create before you import, it won't automatically create the account
2 wallet_account_create doesn't like uppercase :-\
I got it to import provided these 2 things.
-
Ok i figured it out. 2 things.
1 you need to wallet_account_create before you import, it won't automatically create the account
2 wallet_account_create doesn't like uppercase :-\
I got it to import provided these 2 things.
I feel like this process should be documented better. I went through the exact same process and it took me a while before I was able to get my PTS imported as well.
Sent from my iPhone using Tapatalk
-
I got at least a little further.
Looks i was referencing the location incorrectly
instead of ~/Imports/wallet.dat
should be /root/Imports/wallet.dat
It seems to have found it this way but when it asks for "imported wallet passphrase" (it doesn't have one)
I just hit enter, leaving blank and i get aborted
xeldal-w (unlocked) >>> wallet_import_bitcoin "/root/Imports/wallet.dat"
passphrase:
account_name: PTS-jmob
imported wallet passphrase:
Command aborted
It expects your PTS wallet to have a password. How about setting it up?
This has been fixed.
-
wallet_import_armory should work now. (actually Issue #90 says it needs testing, care to help test?)
Armory import seems not implemented at all yet... Tried it with actual values, as well as random values, gives OK all the time
>>> wallet_import_armory
wallet_filename: /this/file/does/not/exist
passphrase:
account_name: well, this is not an account
OK
This was a mistake; Armory has not been implemented yet.
-
2 of my clients are in different chain. network forked :-\
info
{
"blockchain_head_block_num": 23968,
"blockchain_head_block_time": "20140619T190830",
"blockchain_head_block_time_rel": "3 seconds old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 61.12161310649023,
"network_num_connections": 8,
"ntp_time": "20140619T190833.573876",
"ntp_error_seconds": -0.0051879999999999999,
"wallet_unlocked_seconds_remaining": 947714,
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
"wallet_local_time": "20140619T190833",
"blockchain_random_seed": "7eb8264deb04d0e8318364360af0722c4550fe23",
"blockchain_shares": 10001234079409,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140630T182347",
"wallet_version": 100
}
blockchain_list_forks
[
189,
3594,
8562,
10370,
11312,
11338,
14776,
14793,
14921,
18376,
18472,
18718,
20218,
20506,
21322,
21325,
21340,
21449,
21788,
22139,
22160,
22171,
22236,
22281,
22311,
22324,
22331,
22342,
22351,
22504,
22612,
23579,
23640,
23817,
23837,
23912
]
info
{
"blockchain_head_block_num": 23865,
"blockchain_head_block_time": "20140619T190330",
"blockchain_head_block_time_rel": "2 minutes old",
"blockchain_confirmation_requirement": 291,
"blockchain_average_delegate_participation": 56.89149560117302,
"network_num_connections": 8,
"ntp_time": "20140619T190550.862606",
"ntp_error_seconds": 0.47598600000000002,
"wallet_unlocked_seconds_remaining": 999924,
"wallet_next_block_production_time": "20140619T190900",
"wallet_seconds_until_next_block_production": 190,
"wallet_local_time": "20140619T190550",
"blockchain_random_seed": "bbbc529f2ec7ed04c5f3650dc79115cefc1704a8",
"blockchain_shares": 10001224082315,
"network_num_connections_max": 12,
"network_protocol_version": 101,
"wallet_open": true,
"wallet_unlocked_until": "20140701T085114",
"wallet_version": 100
}
blockchain_list_forks
[
11312,
22160,
22281,
23817,
11338,
23912,
14793,
21788,
23837,
189,
22342,
22171,
23640,
21449,
22504,
22331,
10370,
22351,
22139,
14776,
21340,
20506,
8562,
23579,
22236,
18472,
22612,
21325,
21322,
22324,
22311,
14921
]
-
Thanks all! Dry run 3 starting soon!