Dry Run 2: The Real Deal

[bytemaster]

what does this mean?

Code: [Select]

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.

[alexxy]

Are there any howto about running web wallet?

[clout]

what does this mean?

Code: [Select]

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


[bitcoinerS]

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

[bitcoinerS]

Looks like latest build, deletion of  ~/.BitsharesXTS/chain and restart got me onto main blockchain again.

Code: [Select]

>>> 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,


[Xeldal]

Whats wrong with current test networks in latest git build? It cannot sync after

Code: [Select]

{
  "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",

 

Code: [Select]

"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,


[emski]

Whats wrong with current test networks in latest git build? It cannot sync after

Code: [Select]

{
  "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",

[bdnoble]

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?

Code: [Select]

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

[Harvey]

Whats wrong with current test networks in latest git build? It cannot sync after

Code: [Select]

{
  "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.

[alexxy]

Whats wrong with current test networks in latest git build? It cannot sync after

Code: [Select]

{
  "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 =\

[toast]

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

[Xeldal]

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?

[toast]

having problems with latest git pull

Code: [Select]

~/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.

Code: [Select]

bitshares_toolkit\libraries\fc\include\fc/network/ntp.hpp(23): error C2039: “unique_ptr”: not the member function of “std”


git submodule update?

[toast]

I am not sure if my node is tracking the main blockchain or a fork.

Code: [Select]

>>> 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.

[bitcoinerS]

I am not sure if my node is tracking the main blockchain or a fork.

Code: [Select]

>>> 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?