Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: 0.5.3 Wallet won't connect  (Read 420 times)

0 Members and 1 Guest are viewing this topic.

Offline emailtooaj

0.5.3 Wallet won't connect
« on: January 30, 2015, 12:41:28 AM »

Hey everyone,
I've tried it all, and still can't get this dang wallet to get connections.
-Tried deleting BitShare folder and reinstall
-cleared cache
-deleted app roaming folder
-checked firewall
-tried to install 5.0, 5.1 and 5.3 (all same results)

I was told to try re indexing, but don't know what and can't find the correct way to enter it into console
Any suggestions please
Winblowz 8.1

here is my get_info

Code: [Select]
>> get_info

{
  "blockchain_head_block_num": 62039,
  "blockchain_head_block_age": "27 weeks old",
  "blockchain_head_block_timestamp": "2014-07-26T16:23:30",
  "blockchain_average_delegate_participation": "0.01 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": "2,498,988,716.40653 BTS",
  "blockchain_blocks_left_in_round": 76,
  "blockchain_next_round_time": "at least 13 minutes in the future",
  "blockchain_next_round_timestamp": "2015-01-30T00:47:20",
  "blockchain_random_seed": "a5ca15a2efbaca4cc39ac083126fe751b3123795",
  "client_data_dir": ":/Users/A/AppData/Roaming/BitShares",
  "client_version": "v0.5.3",
  "network_num_connections": 0,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-01-30T00:34:41",
  "ntp_time_error": -15.145448,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2015-02-10T14:06:00",
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

*edit
I now have 17 connections but sync time is going UP instead of down???
I'm perplexed, any suggestions or ideas.
« Last Edit: January 30, 2015, 01:55:56 AM by emailtooaj »
Sound Editor of Beyondbitcoin Hangouts. Listen to latest here - https://beyondbitcoin.org support the Hangouts! BTS Tri-Fold Brochure https://bitsharestalk.org/index.php/topic,15169.0.html
Tip BROWNIE.PTS to EMAILTOOAJ

Offline abit

Re: 0.5.3 Wallet won't connect
« Reply #1 on: January 30, 2015, 02:56:28 AM »
Quit the client,
delete peers.leveldb folder,
start bitshares_client.exe instead of bitshares.exe,
type 'info' in the console periodically.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline emailtooaj

Re: 0.5.3 Wallet won't connect
« Reply #2 on: January 30, 2015, 03:00:03 AM »
Thank you abit!
I'll give a go and report back.
Sound Editor of Beyondbitcoin Hangouts. Listen to latest here - https://beyondbitcoin.org support the Hangouts! BTS Tri-Fold Brochure https://bitsharestalk.org/index.php/topic,15169.0.html
Tip BROWNIE.PTS to EMAILTOOAJ

Offline emailtooaj

Re: 0.5.3 Wallet won't connect
« Reply #3 on: February 01, 2015, 06:08:30 PM »
Well, I've tried just about everything I know to do.
Abit, even doing what you suggested hasn't help.
Could someone help me and tell me what folders BitShares uses so I can do a COMPLETE uninstall/delete.
I'm running Win. 8.1 w/8GB RAM and 120GB Samsung SSD Pro along w/ AMD A-10 processor, just in case anyone asks if I'm having troubles do to hardware limitations.

In Windows, I've already ran the native UNINSTALL  through Control Panel.
I've checked Program Files to verify BitShares folder was gone, and also verified the app/roaming folder was deleted.
Are there any other folder locations to delete (outside of the 2 i mentioned)?
And do I need to get into Registry and delete anything there?

Again thank you for any help/suggestions!!!
Sound Editor of Beyondbitcoin Hangouts. Listen to latest here - https://beyondbitcoin.org support the Hangouts! BTS Tri-Fold Brochure https://bitsharestalk.org/index.php/topic,15169.0.html
Tip BROWNIE.PTS to EMAILTOOAJ

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12241
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: 0.5.3 Wallet won't connect
« Reply #4 on: February 01, 2015, 09:10:46 PM »
do you have a firewall running that prevents opening up connections?
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline vikram

Re: 0.5.3 Wallet won't connect
« Reply #5 on: February 01, 2015, 10:40:21 PM »
Yesterday I discovered a bug that could cause syncing to get stuck forever like what is maybe happening here, and I've fixed it for 0.6.x.

If you use the latest version and sync from scratch, but then get stuck--can you look in your logs/p2p/p2p.log file and let us know if you see any messages like "fork permanently rejected"?

Offline bitmarley

  • Full Member
  • ***
  • Posts: 135
    • View Profile
Re: 0.5.3 Wallet won't connect
« Reply #6 on: February 02, 2015, 12:33:55 AM »
I had the exact same problem and I fixed it by resetting the database. I think there is a command line to reset the database but I forced quit my client, restarted and then a dialog appeared asking if I wanted to reset and I said Yes. Once I reset the database everything works perfect.

Offline emailtooaj

Re: 0.5.3 Wallet won't connect
« Reply #7 on: February 02, 2015, 04:48:29 AM »
do you have a firewall running that prevents opening up connections?
Thank you for the question Xeroc. I confirmed there isn't any firewall issues.

So I got it to work somewhat, but still not 100% up and running. Here's what I've done so far...

I uninstalled BitShares via Windows Uninstall through Control Panel,
Went to the C:/ Program Files to verify uninstall,
Went to app/roaming and delete BitShares folder (as uninstall didn't do it?),
Went into the Registry under HKEY_CURRENT_USER>SOFTWARE>BitShares and deleted that folder,
Did a disk clean up and trimmed SSD to rid any remnants,
Restarted Windows,
Re-installed BitShares 0.5.3,

Now... this latest install started to download the chain and was ticking along (unlike my previous attempts) and GUI was showing the sync count down correctly.
But now it's stuck at 664328 and has been stuck for the past 6hrs.
I've  shut the client down and restarted it but still remains on 664328 for the past hour now.
Task Manager is showing 53-60% CPU usage and 581'ish RAM usage. So it's doing something, not sure what though lol?

Yesterday I discovered a bug that could cause syncing to get stuck forever like what is maybe happening here, and I've fixed it for 0.6.x.

If you use the latest version and sync from scratch, but then get stuck--can you look in your logs/p2p/p2p.log file and let us know if you see any messages like "fork permanently rejected"?

Vikram, I looked into the p2p.log file and did a text search for "Fork" and nothing showed up. The file size is nearly 10MB's and has A LOT of txt LOL, but glancing through the text I notice there's a huge amount of timeout errors... Here are some examples...

fatal: error connecting to peer 85.214.53.224:1776: 0 exception: unspecified
No connection could be made because the target machine actively refused it
    {"message":"No connection could be made because the target machine actively refused it"}
    asio  asio.cpp:59 fc::asio::detail::error_handler


2015-02-02T04:20:18 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_synopsis took 1310667us, longer than our target maximum of 500ms         node.cpp:329
2015-02-02T04:20:18 p2p:message read_loop ~call_statistics_col ] Actual execution took 433055us, with a 877612us delay before the delegate thread started executing the method, and a 0us delay after it finished before the p2p thread started processing the response         node.cpp:334
2015-02-02T04:20:18 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_synopsis took 1768728us, longer than our target maximum of 500ms         node.cpp:329
2015-02-02T04:20:18 p2p:message read_loop ~call_statistics_col ] Actual execution took 458061us, with a 1310667us delay before the delegate thread started executing the method, and a 0us delay after it finished before the p2p thread started processing the response         node.cpp:334
2015-02-02T04:20:19 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_synopsis took 2223786us, longer than our target maximum of 500ms         node.cpp:329
2015-02-02T04:20:19 p2p:message read_loop ~call_statistics_col ] Actual execution took 455058us, with a 1768728us delay


So it seems I'm having connection issues on the back end???
I'll try to delete the peers.lvldb file again and restart the client and add nodes that was posted is another related thread (I think Riverhead had posted it?).

We'll see what happens!
 
Sound Editor of Beyondbitcoin Hangouts. Listen to latest here - https://beyondbitcoin.org support the Hangouts! BTS Tri-Fold Brochure https://bitsharestalk.org/index.php/topic,15169.0.html
Tip BROWNIE.PTS to EMAILTOOAJ

Offline Akado

  • Hero Member
  • *****
  • Posts: 2760
    • View Profile
  • BTS: akado
Re: 0.5.3 Wallet won't connect
« Reply #8 on: February 03, 2015, 12:30:52 AM »
mine just keeps crashing. also didn't connect last time it didnt crash
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline emailtooaj

Re: 0.5.3 Wallet won't connect
« Reply #9 on: February 03, 2015, 03:43:11 AM »
ok so now I started all over again and am now getting this...
Any ideas or suggestions?

Code: [Select]
I am disconnecting peer 99.242.226.87:64415 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 123.203.69.194:37912 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 99.242.226.87:64415 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 176.9.234.167:1700 for reason: You offered us a block th
at we reject as invalid
--- in sync with p2p network
I am disconnecting peer 50.116.4.37:1877 for reason: You offered us a block that
 we reject as invalid
I am disconnecting peer 67.0.179.48:52772 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 176.9.234.167:1700 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 213.136.87.34:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 123.203.69.194:37912 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 50.116.4.37:1877 for reason: You offered us a block that
 we reject as invalid
I am disconnecting peer 123.203.69.194:37912 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 213.136.87.34:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 176.9.234.167:1700 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 67.0.179.48:52772 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 50.116.4.37:1877 for reason: You offered us a block that
 we reject as invalid
I am disconnecting peer 213.136.87.34:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 50.116.4.37:1877 for reason: You offered us a block that
 we reject as invalid
I am disconnecting peer 67.0.179.48:52772 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 176.9.234.167:1700 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 213.136.87.34:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 67.0.179.48:52772 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 218.17.161.66:5966 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 176.9.234.167:1700 for reason: You offered us a block th
at we reject as invalid
--- there are now 3 active connections to the p2p network
I am disconnecting peer 67.0.179.48:52772 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 176.9.234.167:1700 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 213.136.87.34:1776 for reason: You offered us a block th
at we reject as invalid
--- there are now 2 active connections to the p2p network
I am disconnecting peer 176.9.234.167:1700 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 67.0.179.48:52772 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 176.9.234.167:1700 for reason: You offered us a block th
at we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
I am disconnecting peer 99.242.226.87:64474 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 75.148.117.228:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 23.239.5.30:1776 for reason: You offered us a block that
 we reject as invalid
I am disconnecting peer 106.185.26.162:1676 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 69.90.132.209:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 104.131.133.241:1776 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 75.148.117.228:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 23.239.5.30:1776 for reason: You offered us a block that
 we reject as invalid
I am disconnecting peer 106.185.26.162:1676 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 69.90.132.209:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 104.131.133.241:1776 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 92.107.4.67:49150 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 23.239.5.30:1776 for reason: You offered us a block that
 we reject as invalid
I am disconnecting peer 106.185.26.162:1676 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 69.90.132.209:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 104.131.133.241:1776 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 92.107.4.67:49150 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 108.61.167.133:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 46.226.109.66:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 106.185.26.162:1676 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 69.90.132.209:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 104.131.133.241:1776 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 92.107.4.67:49150 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 108.61.167.133:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 46.226.109.66:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 69.90.132.209:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 104.131.133.241:1776 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 92.107.4.67:49150 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 108.61.167.133:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 46.226.109.66:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 104.131.133.241:1776 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 92.107.4.67:49150 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 108.61.167.133:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 46.226.109.66:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 92.107.4.67:49150 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 108.61.167.133:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 46.226.109.66:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 108.61.167.133:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 46.226.109.66:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 46.226.109.66:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 128.199.139.242:51288 for reason: You offered us a block
 that we reject as invalid
I am disconnecting peer 96.248.12.174:64260 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 96.248.12.174:64260 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 54.77.51.177:1776 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 188.226.195.137:60696 for reason: You offered us a block
 that we reject as invalid
I am disconnecting peer 66.172.10.30:1776 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 178.62.50.61:1779 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 99.242.226.87:64494 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 14.147.84.121:14534 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 188.226.195.137:60696 for reason: You offered us a block
 that we reject as invalid
I am disconnecting peer 66.172.10.30:1776 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 178.62.50.61:1779 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 99.242.226.87:64494 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 14.147.84.121:14534 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 66.172.10.30:1776 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 178.62.50.61:1779 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 99.242.226.87:64494 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 14.147.84.121:14534 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 178.62.50.61:1779 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 99.242.226.87:64494 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 14.147.84.121:14534 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 99.242.226.87:64494 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 14.147.84.121:14534 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 14.147.84.121:14534 for reason: You offered us a block t
hat we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
I am disconnecting peer 178.62.30.171:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 192.169.201.30:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 192.169.201.30:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 116.34.174.21:2654 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 116.34.174.21:2654 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 72.177.1.136:53868 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 99.242.226.87:64515 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 5.189.131.201:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 37.187.103.184:1776 for reason: You offered us a block t
hat we reject as invalid
--- there are now 3 active connections to the p2p network
I am disconnecting peer 116.34.174.21:2654 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 72.177.1.136:53868 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 72.177.1.136:53868 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 99.242.226.87:64515 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 5.189.131.201:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 37.187.103.184:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 72.177.1.136:53868 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 99.242.226.87:64515 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 99.242.226.87:64515 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 5.189.131.201:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 37.187.103.184:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 99.242.226.87:64515 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 5.189.131.201:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 5.189.131.201:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 37.187.103.184:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 5.189.131.201:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 37.187.103.184:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 37.187.103.184:1776 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 37.187.103.184:1776 for reason: You offered us a block t
hat we reject as invalid
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- syncing with p2p network, 1383173 blocks left to fetch
I am disconnecting peer 95.215.47.201:1776 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 128.199.139.242:36292 for reason: You offered us a block
 that we reject as invalid
I am disconnecting peer 73.162.63.60:13737 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 104.131.185.84:39398 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 73.162.63.60:13737 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 104.200.28.117:33108 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 104.200.28.117:33108 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 104.131.185.84:39398 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 99.242.226.87:64536 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 38.108.54.4:10359 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 99.242.226.87:64536 for reason: You offered us a block t
hat we reject as invalid
--- in sync with p2p network
I am disconnecting peer 104.200.28.117:33108 for reason: You offered us a block
that we reject as invalid
I am disconnecting peer 38.108.54.4:10359 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 38.108.54.4:10359 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 99.242.226.87:64536 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 38.108.54.4:10359 for reason: You offered us a block tha
t we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
I am disconnecting peer 67.0.179.48:52791 for reason: You offered us a block tha
t we reject as invalid
I am disconnecting peer 83.87.59.133:54315 for reason: You offered us a block th
at we reject as invalid
I am disconnecting peer 99.242.226.87:64558 for reason: You offered us a block t
hat we reject as invalid
I am disconnecting peer 104.131.134.181:55906 for reason: You offered us a block
 that we reject as invalid
I am disconnecting peer 72.231.3.30:55193 for reason: You offered us a block tha
t we reject as invalid
(wallet closed) >>>
Sound Editor of Beyondbitcoin Hangouts. Listen to latest here - https://beyondbitcoin.org support the Hangouts! BTS Tri-Fold Brochure https://bitsharestalk.org/index.php/topic,15169.0.html
Tip BROWNIE.PTS to EMAILTOOAJ

 

Google+