Pages:
Author

Topic: ►►►[XBC] BitcoinPlus ►Official Thread◄官方公告◄◄◄ - page 59. (Read 408040 times)

newbie
Activity: 39
Merit: 0
You guys have very good support response. Keep up the good work!
member
Activity: 89
Merit: 10
Where I can get the minting profitability?
I mean like a clculator that tells me approx due to the current situation how much I can mint per day due to my coins

https://www.bitcoinplus.org/blog/proof-stake-explained

Unrealistic to calculate per day as the algorithm is based on 1 year. Theoretical amount - divide yearly stake by 365.
sr. member
Activity: 595
Merit: 251
Where I can get the minting profitability?
I mean like a clculator that tells me approx due to the current situation how much I can mint per day due to my coins
legendary
Activity: 1484
Merit: 1032
2017-10-18 10:47 UTC

Difficulty
POW: 0.01442156
POS: 0.00028575
Coin Supply (XBC)
101770.03748919
432976 blocks
31 connections

XBC/BTC
Last Price
0.00865037
24hr Change
-18.24%
24hr High
0.01071694
24hr Low
0.00820000
24hr Volume:
44.47967261 BTC / 4889.84033537 XBC
legendary
Activity: 1484
Merit: 1032
I got 51 connections believe it or not!

Nice.I managed to get 38 myself yesterday which wasn't too shabby. Smiley
legendary
Activity: 1484
Merit: 1032
2017-10-17 10:35

Difficulty
POW: 0.01442156
POS: 0.0003351
Coin Supply (XBC)
101745.97009536
432295 blocks
32 connections

XBC/BTC
Last Price
0.01018651
24hr Change
+42.24%
24hr High
0.01145000
24hr Low
0.00710000
24hr Volume:
50.92568620 BTC / 5297.28683508 XBC
member
Activity: 157
Merit: 10
2017-10-16 10:18

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
101716.3027019
431510 blocks
31 connections

XBC/BTC
Last Price
0.00732221
24hr Change
+1.11%
24hr High
0.00761223
24hr Low
0.00710000
24hr Volume:
5.88236507 BTC / 804.61017746 XBC
I got 51 connections believe it or not!
legendary
Activity: 1484
Merit: 1032
2017-10-16 10:18

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
101716.3027019
431510 blocks
31 connections

XBC/BTC
Last Price
0.00732221
24hr Change
+1.11%
24hr High
0.00761223
24hr Low
0.00710000
24hr Volume:
5.88236507 BTC / 804.61017746 XBC
legendary
Activity: 1484
Merit: 1032
2017-10-15 14:25 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
101694.41448582
430881 blocks
26 connections

XBC/BTC
Last Price
0.00739069
24hr Change
-9.87%
24hr High
0.00826904
24hr Low
0.00705868
24hr Volume:
5.00413659 BTC / 649.49009317 XBC
legendary
Activity: 1484
Merit: 1032
2017-10-14 19:49 UTC

Difficulty
POW: 0.01442156
POS: 0.00024523
Coin Supply (XBC)
101670.08407766
430321 blocks
29 connections


XBC/BTC
Last Price
0.00801153
24hr Change
-2.76%
24hr High
0.00865499
24hr Low
0.00801000
24hr Volume:
3.63077658 BTC / 438.18335997 XBC
legendary
Activity: 1484
Merit: 1032
2017-10-13 11:11

Difficulty
POS: 0.00029022
Coin Supply (XBC)
101631.68079493
429323 blocks
30 connections

XBC/BTC
Last Price
0.00863310
24hr Change
-7.87%
24hr High
0.00952785
24hr Low
0.00855650
24hr Volume:
13.04028591 BTC / 1433.05927469 XBC
member
Activity: 98
Merit: 10


Waiting for an answer
Previously, I had no problems when I updated the node list, there used to be local IPs, only TORs and everything on new ports 80003
Your developer made the updates, these updates work for linux but for windows they are not working


You don't need to update any node list.2.6 wallet connects over Tor straight away.Wallet just finds what is available.You don't need to do anything except run the wallet in whatever mode you want it to run.Everything else is automated except setting up wallet messaging for security reasons.Btw port 80003 doesn't exist unless you are talking about the PROTOCOL_VERSION = 80003.

Run on a new computer
I downloaded a client from the site and launched
Same problem

Problem in ports or PROTOCOL_VERSION  if you look at debug.log

Quote
bitcoinplus version v2.6.0.0: satoshi (Apr 28 2017, 13:40:11)
Using OpenSSL version OpenSSL 1.0.2g  1 Mar 2016
Startup time: 10/12/17 16:29:03
Default data directory C:\Users\Ion\AppData\Roaming\bitcoinplus
Used data directory C:\Users\Ion\AppData\Roaming\bitcoinplus
dbenv.open LogDir=C:\Users\Ion\AppData\Roaming\bitcoinplus\database ErrorFile=C:\Users\Ion\AppData\Roaming\bitcoinplus\db.log
Initialising Tor Network...
Bound to 127.0.0.1:8884
Initialising Tor Network...
AddLocal(2vvo4d2bs4esaokm.onion:8884,6)
Loading block index...
Opening LevelDB in C:\Users\Ion\AppData\Roaming\bitcoinplus\txleveldb
Opened LevelDB successfully
CBlock(hash=0000005f6a28e686f641c616e56182d1b43afbe08a223f23bda23cdf9d55b882, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=81d205aec871e7998b1313f195603159a2e6388ced896536dce76bf1410fc039, nTime=1427729379, nBits=1e0fffff, nNonce=1698442, vtx=1, vchBlockSig=)
  Coinbase(hash=81d205aec8, nTime=1427729379, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, 4294967295), coinbase 00012a2d424243204e6577733a2043616d65726f6e206c61756e6368657320656c656374696f6e2 063616d706169676e2e)
    CTxOut(empty)
  vMerkleTree: 81d205aec8
block.GetHash() == 0000005f6a28e686f641c616e56182d1b43afbe08a223f23bda23cdf9d55b882
block.hashMerkleRoot == 81d205aec871e7998b1313f195603159a2e6388ced896536dce76bf1410fc039
block.nTime = 1427729379
block.nNonce = 1698442
CBlock(hash=0000005f6a28e686f641c616e56182d1b43afbe08a223f23bda23cdf9d55b882, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=81d205aec871e7998b1313f195603159a2e6388ced896536dce76bf1410fc039, nTime=1427729379, nBits=1e0fffff, nNonce=1698442, vtx=1, vchBlockSig=)
  Coinbase(hash=81d205aec8, nTime=1427729379, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, 4294967295), coinbase 00012a2d424243204e6577733a2043616d65726f6e206c61756e6368657320656c656374696f6e2 063616d706169676e2e)
    CTxOut(empty)
  vMerkleTree: 81d205aec8
SetBestChain: new best=0000005f6a28e686f641  height=0  trust=1048577  blocktrust=1048577  date=03/30/15 15:29:39
ResetSyncCheckpoint: pending for sync-checkpoint 00000019ca43d5a4dbae504ca25971b59e6f8662027c905423f9c0dd92a37c7c
ResetSyncCheckpoint: sync-checkpoint reset to 0000005f6a28e686f641c616e56182d1b43afbe08a223f23bda23cdf9d55b882
 block index             719ms
Loading wallet...
nFileVersion = 2060000
Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total
Performing wallet upgrade to 60000
Flushing wallet.dat
Flushed wallet.dat 390ms
RandAddSeed() 224656 bytes
keypool added key 1, size=1
keypool added key 2, size=2
keypool added key 3, size=3
keypool added key 4, size=4
keypool added key 5, size=5
keypool added key 6, size=6
keypool added key 7, size=7
keypool added key 8, size=8
keypool added key 9, size=9
keypool added key 10, size=10
keypool added key 11, size=11
keypool added key 12, size=12
keypool added key 13, size=13
keypool added key 14, size=14
keypool added key 15, size=15
keypool added key 16, size=16
keypool added key 17, size=17
keypool added key 18, size=18
keypool added key 19, size=19
keypool added key 20, size=20
keypool added key 21, size=21
keypool added key 22, size=22
keypool added key 23, size=23
keypool added key 24, size=24
keypool added key 25, size=25
keypool added key 26, size=26
keypool added key 27, size=27
keypool added key 28, size=28
keypool added key 29, size=29
keypool added key 30, size=30
keypool added key 31, size=31
keypool added key 32, size=32
keypool added key 33, size=33
keypool added key 34, size=34
keypool added key 35, size=35
keypool added key 36, size=36
keypool added key 37, size=37
keypool added key 38, size=38
keypool added key 39, size=39
keypool added key 40, size=40
keypool added key 41, size=41
keypool added key 42, size=42
keypool added key 43, size=43
keypool added key 44, size=44
keypool added key 45, size=45
keypool added key 46, size=46
keypool added key 47, size=47
keypool added key 48, size=48
keypool added key 49, size=49
keypool added key 50, size=50
keypool added key 51, size=51
keypool added key 52, size=52
keypool added key 53, size=53
keypool added key 54, size=54
keypool added key 55, size=55
keypool added key 56, size=56
keypool added key 57, size=57
keypool added key 58, size=58
keypool added key 59, size=59
keypool added key 60, size=60
keypool added key 61, size=61
keypool added key 62, size=62
keypool added key 63, size=63
keypool added key 64, size=64
keypool added key 65, size=65
keypool added key 66, size=66
keypool added key 67, size=67
keypool added key 68, size=68
keypool added key 69, size=69
keypool added key 70, size=70
keypool added key 71, size=71
keypool added key 72, size=72
keypool added key 73, size=73
keypool added key 74, size=74
keypool added key 75, size=75
keypool added key 76, size=76
keypool added key 77, size=77
keypool added key 78, size=78
keypool added key 79, size=79
keypool added key 80, size=80
keypool added key 81, size=81
keypool added key 82, size=82
keypool added key 83, size=83
keypool added key 84, size=84
keypool added key 85, size=85
keypool added key 86, size=86
keypool added key 87, size=87
keypool added key 88, size=88
keypool added key 89, size=89
keypool added key 90, size=90
keypool added key 91, size=91
keypool added key 92, size=92
keypool added key 93, size=93
keypool added key 94, size=94
keypool added key 95, size=95
keypool added key 96, size=96
keypool added key 97, size=97
keypool added key 98, size=98
keypool added key 99, size=99
keypool added key 100, size=100
keypool added key 101, size=101
 wallet                19027ms
Loading addresses...
ERROR: CAddrman::Read() : open failed
Invalid or missing peers.dat; recreating
Loaded 0 addresses from peers.dat  0ms
Secure messaging starting.
Error opening file: No such file or directory
Failed to read smsg.ini
No address keys loaded.
Message store directory does not exist.
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
ThreadDNSAddressSeed started
ThreadOnionSeed started
Loading addresses from .onion seeds
ThreadSocketHandler started
Loading addresses from DNS seeds (could take a while)
ThreadOpenAddedConnections started
ThreadOpenAddedConnections exited
ThreadIRCSeed exited
ThreadMapPort started
ThreadMessageHandler started
ThreadStakeMiner started
Added vqr4nghlcpdipdpj.onion:8884 from vqr4nghlcpdipdpj.onion: 0 tried, 1 new
ThreadOpenConnections started
Added yvjofqv4wox4ywwm.onion:8884 from yvjofqv4wox4ywwm.onion: 0 tried, 2 new
Added dtc6mm23aexkkjtl.onion:8884 from dtc6mm23aexkkjtl.onion: 0 tried, 3 new
Added 7xcm543jtkje4mkv.onion:8884 from 7xcm543jtkje4mkv.onion: 0 tried, 4 new
Added r2bqmq2uun4ojk45.onion:8884 from r2bqmq2uun4ojk45.onion: 0 tried, 5 new
Added jo43ypvfj6me63ph.onion:8884 from jo43ypvfj6me63ph.onion: 0 tried, 6 new
Added 7bzf57aacrsmvokz.onion:8884 from 7bzf57aacrsmvokz.onion: 0 tried, 7 new
Added adkzksf6pfevieus.onion:8884 from adkzksf6pfevieus.onion: 0 tried, 8 new
8 addresses found from .onion seeds
ThreadOnionSeed exited
Added 1 addresses from 138.68.191.241: 0 tried, 9 new
Added 1 addresses from 188.226.146.79: 0 tried, 10 new
Flushed 10 addresses to peers.dat  265ms
Added 1 addresses from 138.68.88.179: 0 tried, 11 new
Added 1 addresses from 162.243.14.4: 0 tried, 12 new
trying connection jo43ypvfj6me63ph.onion:8884 lastseen=134.5hrs
SOCKS5 connecting jo43ypvfj6me63ph.onion
ERROR: Proxy error: host unreachable
4 addresses found from DNS seeds
ThreadDNSAddressSeed exited
refreshWallet
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
ipcThread started
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
UPnP: ExternalIPAddress = 192.168.225.100
Flushing wallet.dat
trying connection jo43ypvfj6me63ph.onion:8884 lastseen=134.5hrs
SOCKS5 connecting jo43ypvfj6me63ph.onion
ERROR: Proxy error: host unreachable
UPnP Port Mapping successful.
Flushed wallet.dat 359ms
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection adkzksf6pfevieus.onion:8884 lastseen=157.3hrs
SOCKS5 connecting adkzksf6pfevieus.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection 7xcm543jtkje4mkv.onion:8884 lastseen=112.7hrs
SOCKS5 connecting 7xcm543jtkje4mkv.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection adkzksf6pfevieus.onion:8884 lastseen=157.3hrs
SOCKS5 connecting adkzksf6pfevieus.onion
ERROR: Proxy error: host unreachable
trying connection 7xcm543jtkje4mkv.onion:8884 lastseen=112.7hrs
SOCKS5 connecting 7xcm543jtkje4mkv.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
trying connection 7bzf57aacrsmvokz.onion:8884 lastseen=129.6hrs
SOCKS5 connecting 7bzf57aacrsmvokz.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
trying connection 7xcm543jtkje4mkv.onion:8884 lastseen=112.7hrs
SOCKS5 connecting 7xcm543jtkje4mkv.onion
ERROR: Proxy error: host unreachable
trying connection adkzksf6pfevieus.onion:8884 lastseen=157.3hrs
SOCKS5 connecting adkzksf6pfevieus.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
trying connection jo43ypvfj6me63ph.onion:8884 lastseen=134.5hrs
SOCKS5 connecting jo43ypvfj6me63ph.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection 7xcm543jtkje4mkv.onion:8884 lastseen=112.7hrs
SOCKS5 connecting 7xcm543jtkje4mkv.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection jo43ypvfj6me63ph.onion:8884 lastseen=134.5hrs
SOCKS5 connecting jo43ypvfj6me63ph.onion
ERROR: Proxy error: host unreachable
trying connection adkzksf6pfevieus.onion:8884 lastseen=157.3hrs
SOCKS5 connecting adkzksf6pfevieus.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection adkzksf6pfevieus.onion:8884 lastseen=157.3hrs
SOCKS5 connecting adkzksf6pfevieus.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection jo43ypvfj6me63ph.onion:8884 lastseen=134.5hrs
SOCKS5 connecting jo43ypvfj6me63ph.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection 7xcm543jtkje4mkv.onion:8884 lastseen=112.7hrs
SOCKS5 connecting 7xcm543jtkje4mkv.onion
ERROR: Proxy error: host unreachable
trying connection jo43ypvfj6me63ph.onion:8884 lastseen=134.5hrs
SOCKS5 connecting jo43ypvfj6me63ph.onion
ERROR: Proxy error: host unreachable
trying connection 7bzf57aacrsmvokz.onion:8884 lastseen=129.6hrs
SOCKS5 connecting 7bzf57aacrsmvokz.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection adkzksf6pfevieus.onion:8884 lastseen=157.3hrs
SOCKS5 connecting adkzksf6pfevieus.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
trying connection jo43ypvfj6me63ph.onion:8884 lastseen=134.5hrs
SOCKS5 connecting jo43ypvfj6me63ph.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection vqr4nghlcpdipdpj.onion:8884 lastseen=107.8hrs
SOCKS5 connecting vqr4nghlcpdipdpj.onion
ERROR: Proxy error: host unreachable
trying connection r2bqmq2uun4ojk45.onion:8884 lastseen=129.0hrs
SOCKS5 connecting r2bqmq2uun4ojk45.onion
ERROR: Proxy error: host unreachable
trying connection dtc6mm23aexkkjtl.onion:8884 lastseen=151.9hrs
SOCKS5 connecting dtc6mm23aexkkjtl.onion
ERROR: Proxy error: host unreachable
trying connection adkzksf6pfevieus.onion:8884 lastseen=157.3hrs
SOCKS5 connecting adkzksf6pfevieus.onion
ERROR: Proxy error: host unreachable
trying connection adkzksf6pfevieus.onion:8884 lastseen=157.3hrs
SOCKS5 connecting adkzksf6pfevieus.onion
ERROR: Proxy error: host unreachable
trying connection yvjofqv4wox4ywwm.onion:8884 lastseen=155.3hrs
SOCKS5 connecting yvjofqv4wox4ywwm.onion
ERROR: Proxy error: host unreachable
legendary
Activity: 1330
Merit: 1000
Good afternoon, I tried to take my coins out to the exchange but your wallet shows 0 conecction?
How can I solve the problem?
please give a list of Node
10 days ago worked everything ok

My BitcoinPlus 2.6




I have 26 connections.You are on the latest client 2.6.0.0 so there should be no issue but try connecting without Tor in case one of the seed nodes you are connecting through are down.If that doesnt work contact mammix2 or bushstar here on the forum.



I have a windows client
And it used to work fine, you have changed all the ports on the network and all TOR clients
You must release a new windows client
Why should I solve the problem when you and your developer have changed the entire network and are not compatible with win client 2.6

Update
I asked my friend to try win client
The same problem the same 0 conection

You do not have not one open IP http://block.bitcoinplus.org/network, all IP TORs


Like I already said.Just use the standard connection until the issue is resolved.On the latest client you can switch off the TOR and use basic I2P and you will get an immeadiate connection through hard wired nodes.I have already contacted mammix to see if his seed TOR nodes are down or what the problem is if any.

I could start giving you advice on flushing peers from the executables etc but like I said either contact mammix directly or wait until I have further advice.Nothing more I can do here. http://block.bitcoinplus.org/api/getconnectioncount


Note:After using standard I2P and if having issues using TOR you can try to restart the wallet on TOR from the settings check box.Then shut it down.If you use windows just search %appdata% and go into bitcoinplus executable files.You can just delete the peers.dat and tor peers.dat Restart the wallet and after flushing the peers files manually it will refind available peers.
legendary
Activity: 1330
Merit: 1000


Waiting for an answer
Previously, I had no problems when I updated the node list, there used to be local IPs, only TORs and everything on new ports 80003
Your developer made the updates, these updates work for linux but for windows they are not working


You don't need to update any node list.2.6 wallet connects over Tor straight away.Wallet just finds what is available.You don't need to do anything except run the wallet in whatever mode you want it to run.Everything else is automated except setting up wallet messaging for security reasons.Btw port 80003 doesn't exist unless you are talking about the PROTOCOL_VERSION = 80003.
hero member
Activity: 777
Merit: 777
Altbone inc.Burial service for altcoins


I checked on linux. really works 27 connections
Then I copied the .bitcoinplus folder and run 2.6 win
Problem also 0 connections. TOR I disabled
Your developer has updated dns seeds and they do not work with client 2.6

When the release of new windows  versions is planned?



I am still witing for confirmation from mammix but everything works fine with my client so its probably an issue your end.Just download a new client and put in your wallet.dat or import your private keys.

Quote
Your developer has updated dns seeds and they do not work with client 2.6


https://github.com/bitcoinplusorg/xbcwalletsource/blob/origin/src/net.cpp#L1184


They are the current seeders.

    {"seednode1.bitcoinplus.net", "seednode1.bitcoinplus.net"},
    {"seednode2.bitcoinplus.net", "seednode2.bitcoinplus.net"},
    {"seednode3.bitcoinplus.net", "seednode3.bitcoinplus.net"},
    {"seednode4.bitcoinplus.net", "seednode4.bitcoinplus.net"},
    {"seednode5.bitcoinplus.net", "seednode5.bitcoinplus.net"},


Looking back 2.1 they were so nothing was replaced just added to which should not cause any issue.

    {"seednode1.bitcoinplus.net", "seednode1.bitcoinplus.net"},
    {"seednode2.bitcoinplus.net", "seednode2.bitcoinplus.net"},


Quote
When the release of new windows  versions is planned?


When we are updated to a higher bitcoin version after more BIPs and refactoring so I don't have a time or date.Current version works fine for now.

Waiting for an answer
Previously, I had no problems when I updated the node list, there used to be local IPs, only TORs and everything on new ports 80003
Your developer made the updates, these updates work for linux but for windows they are not working



Stop your repetitive fud nonsense and just download a new wallet from the website.You don't need to update any node list or even have .conf due to latest client finding nodes itself automatically.You have been given more than one answer already.The wallet works without any problems.If tor seed node is down just use I2P until resolved.
member
Activity: 98
Merit: 10


I checked on linux. really works 27 connections
Then I copied the .bitcoinplus folder and run 2.6 win
Problem also 0 connections. TOR I disabled
Your developer has updated dns seeds and they do not work with client 2.6

When the release of new windows  versions is planned?



I am still witing for confirmation from mammix but everything works fine with my client so its probably an issue your end.Just download a new client and put in your wallet.dat or import your private keys.

Quote
Your developer has updated dns seeds and they do not work with client 2.6


https://github.com/bitcoinplusorg/xbcwalletsource/blob/origin/src/net.cpp#L1184


They are the current seeders.

    {"seednode1.bitcoinplus.net", "seednode1.bitcoinplus.net"},
    {"seednode2.bitcoinplus.net", "seednode2.bitcoinplus.net"},
    {"seednode3.bitcoinplus.net", "seednode3.bitcoinplus.net"},
    {"seednode4.bitcoinplus.net", "seednode4.bitcoinplus.net"},
    {"seednode5.bitcoinplus.net", "seednode5.bitcoinplus.net"},


Looking back 2.1 they were so nothing was replaced just added to which should not cause any issue.

    {"seednode1.bitcoinplus.net", "seednode1.bitcoinplus.net"},
    {"seednode2.bitcoinplus.net", "seednode2.bitcoinplus.net"},


Quote
When the release of new windows  versions is planned?


When we are updated to a higher bitcoin version after more BIPs and refactoring so I don't have a time or date.Current version works fine for now.

Waiting for an answer
Previously, I had no problems when I updated the node list, there used to be local IPs, only TORs and everything on new ports 80003
Your developer made the updates, these updates work for linux but for windows they are not working
legendary
Activity: 1484
Merit: 1032
2017-10-12 09:10 UTC

Current Block
428562
Difficulty
0.00024414
Money Supply
101598.37394926
32 connections

XBC/BTC
Last Price
0.00930000
24hr Change
-5.43%
24hr High
0.01034000
24hr Low
0.00930000
24hr Volume:
8.74116290 BTC / 886.80502863 XBC
legendary
Activity: 1484
Merit: 1032


I checked on linux. really works 27 connections
Then I copied the .bitcoinplus folder and run 2.6 win
Problem also 0 connections. TOR I disabled
Your developer has updated dns seeds and they do not work with client 2.6

When the release of new windows  versions is planned?



I am still witing for confirmation from mammix but everything works fine with my client so its probably an issue your end.Just download a new client and put in your wallet.dat or import your private keys.

Quote
Your developer has updated dns seeds and they do not work with client 2.6


https://github.com/bitcoinplusorg/xbcwalletsource/blob/origin/src/net.cpp#L1184


They are the current seeders.

    {"seednode1.bitcoinplus.net", "seednode1.bitcoinplus.net"},
    {"seednode2.bitcoinplus.net", "seednode2.bitcoinplus.net"},
    {"seednode3.bitcoinplus.net", "seednode3.bitcoinplus.net"},
    {"seednode4.bitcoinplus.net", "seednode4.bitcoinplus.net"},
    {"seednode5.bitcoinplus.net", "seednode5.bitcoinplus.net"},


Looking back 2.1 they were so nothing was replaced just added to which should not cause any issue.

    {"seednode1.bitcoinplus.net", "seednode1.bitcoinplus.net"},
    {"seednode2.bitcoinplus.net", "seednode2.bitcoinplus.net"},


Quote
When the release of new windows  versions is planned?


When we are updated to a higher bitcoin version after more BIPs and refactoring so I don't have a time or date.Current version works fine for now.
member
Activity: 98
Merit: 10
Good afternoon, I tried to take my coins out to the exchange but your wallet shows 0 conecction?
How can I solve the problem?
please give a list of Node
10 days ago worked everything ok

My BitcoinPlus 2.6




I have 26 connections.You are on the latest client 2.6.0.0 so there should be no issue but try connecting without Tor in case one of the seed nodes you are connecting through are down.If that doesnt work contact mammix2 or bushstar here on the forum.



I have a windows client
And it used to work fine, you have changed all the ports on the network and all TOR clients
You must release a new windows client
Why should I solve the problem when you and your developer have changed the entire network and are not compatible with win client 2.6

Update
I asked my friend to try win client
The same problem the same 0 conection

You do not have not one open IP http://block.bitcoinplus.org/network, all IP TORs


Like I already said.Just use the standard connection until the issue is resolved.On the latest client you can switch off the TOR and use basic I2P and you will get an immeadiate connection through hard wired nodes.I have already contacted mammix to see if his seed TOR nodes are down or what the problem is if any.

I could start giving you advice on flushing peers from the executables etc but like I said either contact mammix directly or wait until I have further advice.Nothing more I can do here. http://block.bitcoinplus.org/api/getconnectioncount

I checked on linux. really works 27 connections
Then I copied the .bitcoinplus folder and run 2.6 win
Problem also 0 connections. TOR I disabled
Your developer has updated dns seeds and they do not work with client 2.6

When the release of new windows  versions is planned?
legendary
Activity: 1484
Merit: 1032
Good afternoon, I tried to take my coins out to the exchange but your wallet shows 0 conecction?
How can I solve the problem?
please give a list of Node
10 days ago worked everything ok

My BitcoinPlus 2.6




I have 26 connections.You are on the latest client 2.6.0.0 so there should be no issue but try connecting without Tor in case one of the seed nodes you are connecting through are down.If that doesnt work contact mammix2 or bushstar here on the forum.



I have a windows client
And it used to work fine, you have changed all the ports on the network and all TOR clients
You must release a new windows client
Why should I solve the problem when you and your developer have changed the entire network and are not compatible with win client 2.6

Update
I asked my friend to try win client
The same problem the same 0 conection

You do not have not one open IP http://block.bitcoinplus.org/network, all IP TORs


Like I already said.Just use the standard connection until the issue is resolved.On the latest client you can switch off the TOR and use basic I2P and you will get an immeadiate connection through hard wired nodes.I have already contacted mammix to see if his seed TOR nodes are down or what the problem is if any.

I could start giving you advice on flushing peers from the executables etc but like I said either contact mammix directly or wait until I have further advice.Nothing more I can do here. http://block.bitcoinplus.org/api/getconnectioncount
Pages:
Jump to: