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?
Topic: Bitcoin3 - page 5. (Read 6571 times)
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"
cryptohamstr.com has 4 connections so far and blockchain is moving forward.
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"
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.
cryptohamstr.com
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"
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
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
Apologies to everyone. Been on vacation for several days during the holy week season.
Testbug= yes already sent you a pm
sdnz= yes old wallet version 1 is still connected to the hardcoded node.
Will be killing the node for the old version 1 wallet, so miners using old version 1 wallet won't be able to connect to the old node anymore.
wallet 1.0.2 connects to these nodes
addnode=136.144.171.201:30268
addnode= 158.101.29.12:30268
addnode=95.11.228.167:30268
initially but then gets disconnected after a few minutes. Still trouble shooting, might have to into the source code and delete the hard coded nodes.
As for exchanges, Graviex would be happy to list BTC3 for a 0.1BTC listing fee. Still evaluating if this amount would justify for the listing or just crowdsource/crowfund the listing fee just to get it on the exchange. Feel free to weigh in everyone.
Block explorer page is on hold at the moment until we get the new wallet back online.
Thanks everyone for your continued patience
BTC3
Testbug= yes already sent you a pm
sdnz= yes old wallet version 1 is still connected to the hardcoded node.
Will be killing the node for the old version 1 wallet, so miners using old version 1 wallet won't be able to connect to the old node anymore.
wallet 1.0.2 connects to these nodes
addnode=136.144.171.201:30268
addnode= 158.101.29.12:30268
addnode=95.11.228.167:30268
initially but then gets disconnected after a few minutes. Still trouble shooting, might have to into the source code and delete the hard coded nodes.
As for exchanges, Graviex would be happy to list BTC3 for a 0.1BTC listing fee. Still evaluating if this amount would justify for the listing or just crowdsource/crowfund the listing fee just to get it on the exchange. Feel free to weigh in everyone.
Block explorer page is on hold at the moment until we get the new wallet back online.
Thanks everyone for your continued patience
BTC3
I'm connected to those nodes but wallet is still behind. Gonna be honest it's a little late to be giving this info out, most people have already given up on the coin, but maybe you can rekindle some interest by fixing the bugs and getting a pool online.
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)
Apologies to everyone. Been on vacation for several days during the holy week season.
Testbug= yes already sent you a pm
sdnz= yes old wallet version 1 is still connected to the hardcoded node.
Will be killing the node for the old version 1 wallet, so miners using old version 1 wallet won't be able to connect to the old node anymore.
wallet 1.0.2 connects to these nodes
addnode=136.144.171.201:30268
addnode= 158.101.29.12:30268
addnode=95.11.228.167:30268
initially but then gets disconnected after a few minutes. Still trouble shooting, might have to into the source code and delete the hard coded nodes.
As for exchanges, Graviex would be happy to list BTC3 for a 0.1BTC listing fee. Still evaluating if this amount would justify for the listing or just crowdsource/crowfund the listing fee just to get it on the exchange. Feel free to weigh in everyone.
Block explorer page is on hold at the moment until we get the new wallet back online.
Thanks everyone for your continued patience
BTC3
Testbug= yes already sent you a pm
sdnz= yes old wallet version 1 is still connected to the hardcoded node.
Will be killing the node for the old version 1 wallet, so miners using old version 1 wallet won't be able to connect to the old node anymore.
wallet 1.0.2 connects to these nodes
addnode=136.144.171.201:30268
addnode= 158.101.29.12:30268
addnode=95.11.228.167:30268
initially but then gets disconnected after a few minutes. Still trouble shooting, might have to into the source code and delete the hard coded nodes.
As for exchanges, Graviex would be happy to list BTC3 for a 0.1BTC listing fee. Still evaluating if this amount would justify for the listing or just crowdsource/crowfund the listing fee just to get it on the exchange. Feel free to weigh in everyone.
Block explorer page is on hold at the moment until we get the new wallet back online.
Thanks everyone for your continued patience
BTC3
Thank you for the message.
I suggest that in future you would let the community know in advance if you are taking days off.
If you just stay silent, it will only develope FUD.
Hopefully this will get some wind under the wings.
Apologies to everyone. Been on vacation for several days during the holy week season.
Testbug= yes already sent you a pm
sdnz= yes old wallet version 1 is still connected to the hardcoded node.
Will be killing the node for the old version 1 wallet, so miners using old version 1 wallet won't be able to connect to the old node anymore.
wallet 1.0.2 connects to these nodes
addnode=136.144.171.201:30268
addnode= 158.101.29.12:30268
addnode=95.11.228.167:30268
initially but then gets disconnected after a few minutes. Still trouble shooting, might have to into the source code and delete the hard coded nodes.
As for exchanges, Graviex would be happy to list BTC3 for a 0.1BTC listing fee. Still evaluating if this amount would justify for the listing or just crowdsource/crowfund the listing fee just to get it on the exchange. Feel free to weigh in everyone.
Block explorer page is on hold at the moment until we get the new wallet back online.
Thanks everyone for your continued patience
BTC3
Testbug= yes already sent you a pm
sdnz= yes old wallet version 1 is still connected to the hardcoded node.
Will be killing the node for the old version 1 wallet, so miners using old version 1 wallet won't be able to connect to the old node anymore.
wallet 1.0.2 connects to these nodes
addnode=136.144.171.201:30268
addnode= 158.101.29.12:30268
addnode=95.11.228.167:30268
initially but then gets disconnected after a few minutes. Still trouble shooting, might have to into the source code and delete the hard coded nodes.
As for exchanges, Graviex would be happy to list BTC3 for a 0.1BTC listing fee. Still evaluating if this amount would justify for the listing or just crowdsource/crowfund the listing fee just to get it on the exchange. Feel free to weigh in everyone.
Block explorer page is on hold at the moment until we get the new wallet back online.
Thanks everyone for your continued patience
BTC3
Man that sucks I was looking forward to this. Anyone else know of new and promising altcoins?
Looks dead to me
dev was last seen on March 31st. I think the project is dead.Seems like, yes. Pretty sad, project did start/sound promising but after all the problems with the blockchain and the DEV not being online to say what's going on
Looks dead to me
dev was last seen on March 31st. I think the project is dead.
Looks dead to me
Still no update on the nodes?
As suggestes by "sndz" the seednode, being built in to the source code of the coin, MUSST to be updated in order to allow the network to get available again.
Currently it seems like only the dev has a working connection to the network. cryptohamstr.com pool could serve as a node, allowing in and outgoing connections. This would only work is i get a connected node on the pools server, sadly no connections.
Dev if you need some help on updateing your non working seed node feel free to send me a PM. If i can assist you i will assist in order to kick this project back online!
As suggestes by "sndz" the seednode, being built in to the source code of the coin, MUSST to be updated in order to allow the network to get available again.
Currently it seems like only the dev has a working connection to the network. cryptohamstr.com pool could serve as a node, allowing in and outgoing connections. This would only work is i get a connected node on the pools server, sadly no connections.
Dev if you need some help on updateing your non working seed node feel free to send me a PM. If i can assist you i will assist in order to kick this project back online!
Few suggestions to the dev/team from someone who have been in this forum for over 8 years, IF you want to have any future for the project:
First of all, don't stay quiet and only reply every now and then. You should have few members of the team to be ready to answer at least 10hrs/day to communitys questions and messages in the forum.
Be active.
Second, if there is a reason you can't be active, tell the community about the reasons and possible time you can be active.
Third, let community help you with the project. There are thousands of top tier devs and people with knowledge that can take the project to another level. Do not hesitate to ask help.
Be open about your goals and why you have made the project in the first place.
Last but not least, do not drive the project with $ signs in your eyes. That never gets you anywhere.
These ar the most important things in my opinion.
I also suggest that you make a non-selfmoderated topic and take all the critisism that comes and deal with it.
Otherwise you can dig a hole and dump whole project there and forget it.
First of all, don't stay quiet and only reply every now and then. You should have few members of the team to be ready to answer at least 10hrs/day to communitys questions and messages in the forum.
Be active.
Second, if there is a reason you can't be active, tell the community about the reasons and possible time you can be active.
Third, let community help you with the project. There are thousands of top tier devs and people with knowledge that can take the project to another level. Do not hesitate to ask help.
Be open about your goals and why you have made the project in the first place.
Last but not least, do not drive the project with $ signs in your eyes. That never gets you anywhere.
These ar the most important things in my opinion.
I also suggest that you make a non-selfmoderated topic and take all the critisism that comes and deal with it.
Otherwise you can dig a hole and dump whole project there and forget it.
THX for your kind words!
[/size] Jump to: