Topic: Bitcoin3 - page 4. (Read 6617 times)
I have an S9 mining and will keep my wallet up indefinite except for any internet or power issues to try and help push project along!
I got my wallet working.
What I did is as follows:
-I backed everything from AppData/Roaming/Bitcoin3
-then deleted everything from that folder except wallet.dat, bitcoin3.conf and folder named wallets
-then i edited bitcoin3.conf and removed all addnodes and added only these four:
addnode=158.101.29.12:30268
addnode=195.238.117.169:4226
addnode=203.211.106.86:22571
addnode=46.138.178.248:58506
-Saved the file and started the wallet again.
It synced from block 1 to current block 6793 in about minute.
I'm currently connected to only one node tho, 158.101.29.12:30268
Same here thats the node I have running on my wallet as well, must be the only pool running What I did is as follows:
-I backed everything from AppData/Roaming/Bitcoin3
-then deleted everything from that folder except wallet.dat, bitcoin3.conf and folder named wallets
-then i edited bitcoin3.conf and removed all addnodes and added only these four:
addnode=158.101.29.12:30268
addnode=195.238.117.169:4226
addnode=203.211.106.86:22571
addnode=46.138.178.248:58506
-Saved the file and started the wallet again.
It synced from block 1 to current block 6793 in about minute.
I'm currently connected to only one node tho, 158.101.29.12:30268
I got my wallet working.
What I did is as follows:
-I backed everything from AppData/Roaming/Bitcoin3
-then deleted everything from that folder except wallet.dat, bitcoin3.conf and folder named wallets
-then i edited bitcoin3.conf and removed all addnodes and added only these four:
addnode=158.101.29.12:30268
addnode=195.238.117.169:4226
addnode=203.211.106.86:22571
addnode=46.138.178.248:58506
-Saved the file and started the wallet again.
It synced from block 1 to current block 6793 in about minute.
I'm currently connected to only one node tho, 158.101.29.12:30268
What I did is as follows:
-I backed everything from AppData/Roaming/Bitcoin3
-then deleted everything from that folder except wallet.dat, bitcoin3.conf and folder named wallets
-then i edited bitcoin3.conf and removed all addnodes and added only these four:
addnode=158.101.29.12:30268
addnode=195.238.117.169:4226
addnode=203.211.106.86:22571
addnode=46.138.178.248:58506
-Saved the file and started the wallet again.
It synced from block 1 to current block 6793 in about minute.
I'm currently connected to only one node tho, 158.101.29.12:30268
qualcuno a preso qualche blocco
Is the Dev going to work on his nomp pool?, when my new desktop gets here I need to learn more about this pool stuff, Im a dummy when it comes to that sort of thing, got antminer and cant solo a wallet lol
the wallet was synced everyone thanks for the help
I found those nodes connecting to my node are in "banned" list automatically. I think it's because they are still in the wrong chain.
If you are running a node from one of these, please run v1.0.2 and make sure to delete old chain info before restart.
Also be careful not to delete your wallets.
I will keep cleaning banned list so they can connect to the network.
If you are running a node from one of these, please run v1.0.2 and make sure to delete old chain info before restart.
Also be careful not to delete your wallets.
Code:
"address": "73.31.181.117/32",
"address": "91.152.210.102/32",
"address": "94.247.63.177/32",
"address": "95.84.178.175/32",
"address": "95.111.228.167/32",
"address": "195.238.117.169/32",
"address": "203.220.21.37/32",
"address": "206.116.249.47/32",
I will keep cleaning banned list so they can connect to the network.
2021-04-09T03: 51: 01Z Socket recovery error Remote forcibly terminated an existing connection. (10054)
You could be more supportive to get help ;-) I don't think there are many people can help with that just the last line from your debug output.
Could you copy more lines from the debug output?
And please make sure old blockchain info is removed before restarting. Sorry if you have done so but there was no mention in your question.
I think the directory is like:
C:\Users\YourUserName\Appdata\Roaming\Bitcoin3
Dev download the working bitcoin3.conf
0 blocks and 0 connections, 6 weeks behind.
wallet 1.0.2
0 blocks and 0 connections, 6 weeks behind.
wallet 1.0.2
You need to make sure all directories/files to be removed except wallets from bitcoin3 directory.
And add the available seed nodes and start bitcoin3-qt.
For example my bitcoin3.conf is as following for your reference.
Code:
addresstype=legacy
server=1
daemon=1
#gen=1
#genproclimit=-1
rpcbind=0.0.0.0
rpcuser=username-here
rpcpassword=pass-here
rpcallowip=127.0.0.1
listen=1
rest=1
onlynet=ipv4
dbcache=30
addnode=161.97.187.181
addnode=158.101.29.12
If nothing happens for several minutes after restarting bitcoin3-qt, then goto Help/Debug window/Information window, and click "Open" under "Debug log file" and show the last part of the output will be helpful to identify the problem.
I just loaded wallet to see if it would start and it went to block 6405
Dev download the working bitcoin3.conf
0 blocks and 0 connections, 6 weeks behind.
wallet 1.0.2
0 blocks and 0 connections, 6 weeks behind.
wallet 1.0.2
You need to make sure all directories/files to be removed except wallets from bitcoin3 directory.
And add the available seed nodes and start bitcoin3-qt.
For example my bitcoin3.conf is as following for your reference.
Code:
addresstype=legacy
server=1
daemon=1
#gen=1
#genproclimit=-1
rpcbind=0.0.0.0
rpcuser=username-here
rpcpassword=pass-here
rpcallowip=127.0.0.1
listen=1
rest=1
onlynet=ipv4
dbcache=30
addnode=161.97.187.181
addnode=158.101.29.12
If nothing happens for several minutes after restarting bitcoin3-qt, then goto Help/Debug window/Information window, and click "Open" under "Debug log file" and show the last part of the output will be helpful to identify the problem.
Dev download the working bitcoin3.conf
0 blocks and 0 connections, 6 weeks behind.
wallet 1.0.2
0 blocks and 0 connections, 6 weeks behind.
wallet 1.0.2
ha minato 6000 blocchi in solitaria, cancellato i nostri,e difficolta paurosa,minimo un rimborso per chi puo dimostrare di aver lavorato con il computer dal 15 marzo a oggi
addnode=158.101.29.12:30268
addnode=194.50.15.119:3009
addnode=203.211.106.86:31426
addnode=37.161.27.94:24513
wallet 1.0.2 shows 0 connections! What to do?
addnode=194.50.15.119:3009
addnode=203.211.106.86:31426
addnode=37.161.27.94:24513
wallet 1.0.2 shows 0 connections! What to do?
If it is not syncing try:
connect= instead of addnode= on your bitcoin3.conf
With connect your node will only connect to the nodes you entered. As soon as you are synced you can change "connect=" again to "addnode=" in order to let your node connect to other nodes.
The blockchain is very tiny right now, so it should sync within a few minutes.
Hashrate is already increasing.
addnode=158.101.29.12:30268
addnode=194.50.15.119:3009
addnode=203.211.106.86:31426
addnode=37.161.27.94:24513
wallet 1.0.2 shows 0 connections! What to do?
addnode=194.50.15.119:3009
addnode=203.211.106.86:31426
addnode=37.161.27.94:24513
wallet 1.0.2 shows 0 connections! What to do?
Man that sucks I was looking forward to this. Anyone else know of new and promising altcoins?
There is Piece Classic and Piece I had to restart my chain but it will be something. I will keep a I out for this one. Pieceofpi.world but no node or blockexplorer yet
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:
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"
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:
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"
perfetto questa mattina mi sono stati cancellati tremila btc3 maturati dopo che sono giorni che ho lasciato il computer accesso,poca serieta nei miei confronti?
Duecentoquaranta ore di corrente buttati
Duecentoquaranta ore di corrente buttati
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:
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
Jump to: