Quote from: testbug on Today at 10:29:29 AM

Quote from: sdnz on Today at 10:26:04 AM

Quote from: testbug on Today at 10:10:34 AM

Quote from: sdnz on Today at 09:59:22 AM

Quote from: testbug on Today at 09:52:23 AM

Quote from: SonOfSatosh1 on Today at 05:06:17 AM

Quote from: testbug on April 07, 2021, 09:22:39 AM

Sadly i am still not able to connect to the blockchain.
I can offer the following: Dev can upload his blockchain (blocks, chainstate,...) as zip file to the Bitcoin3 website. After that i can download it and let the pool act as a node. The pool will most likely be there for a while so this would help to get all new people a working connection to the network. I can not allow unlimited nodes to connect to the pool, but there can be more than 15 connections at once. So the other nodes can sync and if someone is hosting a Bitcoin3 node in a datacentre, he could also allow in and outgoing traffic on the Bitcoin3 p2p port (not the RPC port, this port should ALWAYS be closed).

The main error for not being connected is, as far as i can say, this error on the debug.log:

Quote

ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000004130bdf143da15ee11d6d2f44e9c5d0b7f5624eb10c63b607c, bad-diffbits, incorrect proof of work (code 16)

Blockchain and chainstate have been uploaded to btc3 website. Hope we can have the pool act as a node for people to connect.

Thanks

Is this the right chain? "blocks": 6298

My node at 158.101.29.12 seems also running correctly now.

Connected peers:
'37.161.27.94:24517' '/Satoshi:1.0.2/' headers=6305/6307/6307"
'194.50.15.119:2963' '/Satoshi:1.0.2/' headers=6305/6307/6307"
'203.211.106.86:30904' '/Satoshi:1.0.2/' headers=6298/-1/-1"
'46.138.178.248:36806' '/Satoshi:1.0.2/' headers=6306/6307/6307"
'212.171.130.83:62569' '/Satoshi:1.0.2/' headers=6298/-1/-1"

just to confirm: Block 6 308 ? Currently three connections on the pool, node is configured to allow inbound transaction, meaning new people can connect to the pools node and sync the blockchain.

It seems the chain is moving now. I have 6 connections on my node and all nodes are from v1.0.2:

Connected peers:
"0: '212.171.130.83:62990' '/Satoshi:1.0.2/' headers=6313/6313/6313"
"1: '161.97.187.181:49844' '/Satoshi:1.0.2/' headers=6313/6313/6313"
"2: '194.50.15.119:2972' '/Satoshi:1.0.2/' headers=6313/6313/6313"
"3: '37.161.27.94:24514' '/Satoshi:1.0.2/' headers=6313/6313/6313"
"5: '203.211.106.86:22822' '/Satoshi:1.0.2/' headers=6313/6313/6313"
"7: '46.138.178.248:36612' '/Satoshi:1.0.2/' headers=6313/6313/6313"

cryptohamstr.com has 4 connections so far and blockchain is moving forward.

wallet shows 0 connections! What to do?