Pages:
Author

Topic: Bitcoin3 - page 4. (Read 6571 times)

newbie
Activity: 78
Merit: 0
April 13, 2021, 03:32:28 AM
Someone did ask if there is a block explorer already.
cryptohamstr.com offers a very basic explorer, you can look up transactions and general infos about the blocks.
You can find the BTC3 explorere here: https://cryptohamstr.com/explorer/BTC3


Diffuculty looking quite funny  Grin
https://i.imgur.com/tDMcbiU.png
is it possible to mine on this pool on cpu or only asic? which miner can mine on the pool on cpu?
newbie
Activity: 298
Merit: 0
April 11, 2021, 12:48:58 PM
newbie
Activity: 6
Merit: 0
April 11, 2021, 12:28:16 AM
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!
newbie
Activity: 83
Merit: 0
April 10, 2021, 07:36:45 PM
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
newbie
Activity: 14
Merit: 0
April 10, 2021, 06:53:04 PM
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
hero member
Activity: 883
Merit: 556
cryptohamstr.com - Pool OP
April 10, 2021, 09:13:47 AM
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
As far as i know antminers (and other asics) cant solo mine, only solomine on a pool. This is related to the difference in block generation für solo directly to your wallet and with a pools software.
newbie
Activity: 12
Merit: 0
April 10, 2021, 03:08:21 AM
qualcuno a preso qualche blocco
newbie
Activity: 83
Merit: 0
April 10, 2021, 02:46:35 AM
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
newbie
Activity: 78
Merit: 0
April 09, 2021, 01:13:31 PM
the wallet was synced everyone thanks for the help
hero member
Activity: 883
Merit: 556
cryptohamstr.com - Pool OP
April 09, 2021, 08:31:26 AM
Someone did ask if there is a block explorer already.
cryptohamstr.com offers a very basic explorer, you can look up transactions and general infos about the blocks.
You can find the BTC3 explorere here: https://cryptohamstr.com/explorer/BTC3


Diffuculty looking quite funny  Grin
newbie
Activity: 49
Merit: 0
April 09, 2021, 12:19:43 AM
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.

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.
newbie
Activity: 49
Merit: 0
April 09, 2021, 12:08:39 AM

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
newbie
Activity: 78
Merit: 0
April 08, 2021, 11:52:32 PM
Dev download the working bitcoin3.conf
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.
2021-04-09T03: 51: 01Z Socket recovery error Remote forcibly terminated an existing connection. (10054)
newbie
Activity: 83
Merit: 0
April 08, 2021, 04:27:37 PM
I just loaded wallet to see if it would start and it went to block 6405
newbie
Activity: 49
Merit: 0
April 08, 2021, 04:20:58 PM
Dev download the working bitcoin3.conf
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.
newbie
Activity: 78
Merit: 0
April 08, 2021, 12:58:12 PM
Dev download the working bitcoin3.conf
0 blocks and 0 connections, 6 weeks behind.
wallet 1.0.2
newbie
Activity: 12
Merit: 0
April 08, 2021, 12:45:49 PM
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
hero member
Activity: 883
Merit: 556
cryptohamstr.com - Pool OP
April 08, 2021, 12:38:04 PM
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?

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.
connect= it did not help, 0 connections

Did you allready try to delete everything except for your wallet.dat? If your wallet is already synced to a wrong chain it might never get synced.
What does a "-getinfo" put for block number?
newbie
Activity: 78
Merit: 0
April 08, 2021, 12:36:52 PM
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?

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.
connect= it did not help, 0 connections
hero member
Activity: 883
Merit: 556
cryptohamstr.com - Pool OP
April 08, 2021, 12:00:34 PM
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?

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.
Pages:
Jump to: