I see this message, a problem?
Try adding addnode=seed.bc.crypto-daio.co.uk to your conf file then restart your client.
The seed.bc.crypto-daio.co.uk domain has multiple A records, each pointing to an IP address that should have an active BC node. The records get updated every hour or so by the block explorer.
Currently the A records look like this:
ANSWER SECTION:
seed.bc.crypto-daio.co.uk. 1 IN A 178.17.171.102
seed.bc.crypto-daio.co.uk. 1 IN A 138.68.184.193
seed.bc.crypto-daio.co.uk. 1 IN A 73.171.28.236
seed.bc.crypto-daio.co.uk. 1 IN A 77.247.181.162
seed.bc.crypto-daio.co.uk. 1 IN A 185.220.101.13
seed.bc.crypto-daio.co.uk. 1 IN A 218.1.18.78
seed.bc.crypto-daio.co.uk. 1 IN A 128.199.40.99
seed.bc.crypto-daio.co.uk. 1 IN A 185.220.101.46
seed.bc.crypto-daio.co.uk. 1 IN A 185.220.101.27
seed.bc.crypto-daio.co.uk. 1 IN A 121.98.52.216
Using addnode=seed.bc.crypto-daio.co.uk is a shortcut instead of adding each on the IPs separately.
2 Likes
Which port is used for B&C? TCP 2239 ? I have to port forward it in my router, is it correct?
what’s the height now? 1367938? My 6.1.0 version is stuck at 1367938.
The B&C block height is 1872740. The network is functioning normally, but at low difficulty.
Most users are with V6.1.0? I’ll join the minting.
After more than 20 days sync, my height is stuck at 1077XXX block with only one connected node.
Still here, with block height 1900xxx. Although also only 1 connected node at the moment.
Where is the node download and source code?
@smooth here are the client downloads:
https://bitbucket.org/JordanLeePeershares/bcexchange/downloads/
Here is the source code:
https://bitbucket.org/JordanLeePeershares/bcexchange/src/master/
1 Like
Sorry to hear this. Has anyone posted a blockchain he can download? Otherwise, I suggest you re-sync the blockchain by deleting it.
1 Like
I re-sync several days ago, but I find a ping issue.
PING 138.68.184.193 (138.68.184.193) 56(84) bytes of data.
64 bytes from 138.68.184.193: icmp_seq=2 ttl=49 time=437 ms
64 bytes from 138.68.184.193: icmp_seq=4 ttl=49 time=437 ms
64 bytes from 138.68.184.193: icmp_seq=7 ttl=49 time=426 ms
64 bytes from 138.68.184.193: icmp_seq=8 ttl=49 time=426 ms
64 bytes from 138.68.184.193: icmp_seq=9 ttl=49 time=426 ms
64 bytes from 138.68.184.193: icmp_seq=10 ttl=49 time=425 ms
^C
— 138.68.184.193 ping statistics —
11 packets transmitted, 6 received, 45% packet loss, time 10076ms
Hi, Is this domain available now?
I just ran dig seed.bc.crypto-daio.co.uk and it returned the expected list of IP addresses. I’ll have to double check the script that updates the list later on but at first look, it does seem to be available.
1 Like
It appears the block explorer isn’t syncing. The network block height is currently 1968270, while the block explorer only has 1962064. Can you please fix this @woolly_sammoth ?
1 Like
I’ve been trying to start the explorer Daemon in. A variety of different ways (connecting to different nodes) but it doesn’t want to advance the blocks. Looking at the peer list it seems that there are lots of nodes at the same block and only one at a higher. My guess is that the consensus is that the older block is correct and the higher block is a fork. We could try updating the blkindex on the explorer Daemon with the one from the higher node as that may start things off again. Ideally though, we need more minters.
There was a fork with multiple minters. The main minter on the fork used a backup of his BlockShare wallet to mint on a different client (that synced to 1962064) than he had been using in recent days. The result was that the backup of the wallet began minting where most clients were stuck: block 1962064. The explorer and the SouthXchange client are both accepting these new blocks. The network is currently synced at a block height of 1962123.
1 Like
This post was flagged by the community and is temporarily hidden.
It seems the network forked again.