Topic: deleted - page 36. (Read 68074 times)
On walletversion 3000000, that is.
Why do I get the feeling I am the only one mining, hoping I haven't got my own fork. Can I get a confirm we on block 130007 please
I know the feeling. My wallet just now went bust. Restarted it and its rescanning the blockchain.
Why do I get the feeling I am the only one mining, hoping I haven't got my own fork. Can I get a confirm we on block 130007 please
"version" : 4000000,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 2844.00000000,
"blocks" : 130007,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.95580836,
"testnet" : false,
"keypoololdest" : 1411580371,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
A lot of users are still using Version 3.x.
Please note, this wallet won't work beyond block 130000, so it's recommended you upgrade.
Please note, this wallet won't work beyond block 130000, so it's recommended you upgrade.
Why do I get the feeling I am the only one mining, hoping I haven't got my own fork. Can I get a confirm we on block 130007 please
Version 4 of the wallet has been released. This's yet another automated hard fork from block 130001 which improves on the difficulty retarget algo.
I think we need a pool?
Not yet in my opinion, a standard GPU can still hit blocks fairly frequently. When difficulty crosses the 500 mark then I think it will be time. However that is just my thoughts.
I think we need a pool?
Version 4 of the wallet will be coming soon which'll sync till block 140000.
This difficulty retarget algo needs more tweaking, so this'll be an automated hard fork.
Currently there's ongoing testing of the version 4 wallet.
This difficulty retarget algo needs more tweaking, so this'll be an automated hard fork.
Currently there's ongoing testing of the version 4 wallet.
Could someone clarify this part:
"Instead of deploying complicated, CPU-friendly algorithms, we use use simple GPU and ASIC friendly algorithms. And as soon as an ASIC is on the verge of being made, we simply change the algorithm by automated hard forking"
If you want to be asic resistant, why choose an asic friendly algo ? And to what will you change it if asics are going to be used.
"Instead of deploying complicated, CPU-friendly algorithms, we use use simple GPU and ASIC friendly algorithms. And as soon as an ASIC is on the verge of being made, we simply change the algorithm by automated hard forking"
If you want to be asic resistant, why choose an asic friendly algo ? And to what will you change it if asics are going to be used.
ASIC friendly algos are also GPU friendly, so are very fast on the GPU and have negligible speeds on CPU, which has it's advantage.
Quote
Blake is a GPU friendly algorithm which provides maximum protection, cause GPU power is the most expensive to lend.
The disadvantage is that it's simple so ASICs can be made for it without much R&D.
Since we can always hard fork before a reputed company claims to be able to produce such an ASIC, we'll change the algorithm (in the next hard forking schedule) to something which does not have an ASIC like Ink, SHA-3, X13, Quark etc... depending on what's available at that time when an ASIC is on the verge of being made.
Could someone clarify this part:
"Instead of deploying complicated, CPU-friendly algorithms, we use use simple GPU and ASIC friendly algorithms. And as soon as an ASIC is on the verge of being made, we simply change the algorithm by automated hard forking"
If you want to be asic resistant, why choose an asic friendly algo ? And to what will you change it if asics are going to be used.
"Instead of deploying complicated, CPU-friendly algorithms, we use use simple GPU and ASIC friendly algorithms. And as soon as an ASIC is on the verge of being made, we simply change the algorithm by automated hard forking"
If you want to be asic resistant, why choose an asic friendly algo ? And to what will you change it if asics are going to be used.
Version 3 of the wallet has been released. If you're using version 2, it's suggested to upgrade, cause Version 2 doesn't sync beyond block 122000. From 122001 onwards, new difficulty algorithm will trigger (which's still in Beta and incompatible with previous algo).
As promised, a hard fork will never be announced as an emergency in big bold red letters. Cause it's not an emergency at all.
As promised, a hard fork will never be announced as an emergency in big bold red letters. Cause it's not an emergency at all.
Blockchain is around 120.000 now, right? I now only have one connection.
Yes.
You may add more nodes.
59.89.16.23
79.114.108.172
83.85.139.25
178.214.184.201
105.184.27.160
121.237.21.245
Version 3 of the wallet has been released. If you're using version 2, it's suggested to upgrade, cause Version 2 doesn't sync beyond block 122000. From 122001 onwards, new difficulty algorithm will trigger (which's still in Beta and incompatible with previous algo).
As promised, a hard fork will never be announced as an emergency in big bold red letters. Cause it's not an emergency at all.
As promised, a hard fork will never be announced as an emergency in big bold red letters. Cause it's not an emergency at all.
Blockchain is around 120.000 now, right? I now only have one connection.
I have 3 connections and seem to be finding most of the blocks. So it already forked, I guess...
No, that's not the criteria for a fork.
I have 3 connections and seem to be finding most of the blocks. So it already forked, I guess...
I was going to review this, but I can't even figure out how to extract an xz file, much less it being hosted on onedrive.
Get it on github if you want to be taken seriously
Get it on github if you want to be taken seriously
New wallet don't sync. Any nodes?
It should automatically. seed.hardforkcoin.org
Still don't sync.
You do have connections right (see the connection bar at the lower bottom, is that crossed)? It'll take some time to sync.
I don't have any connections. Tried windows and compiled linux wallet.
21:25:08

getpeerinfo
21:25:08

[
]
Then only the firewall's left out. It's blocking connections on your end.
You may try these --
117.201.89.0
207.172.224.81
89.12.123.94
It seems to be ok now. Thanks
New wallet don't sync. Any nodes?
It should automatically. seed.hardforkcoin.org
Still don't sync.
You do have connections right (see the connection bar at the lower bottom, is that crossed)? It'll take some time to sync.
I don't have any connections. Tried windows and compiled linux wallet.
21:25:08

getpeerinfo
21:25:08

[
]
New wallet don't sync. Any nodes?
It should automatically. seed.hardforkcoin.org
Still don't sync.
You do have connections right (see the connection bar at the lower bottom, is that crossed)? It'll take some time to sync.
New wallet don't sync. Any nodes?
It should automatically. seed.hardforkcoin.org
Still don't sync.
Jump to: