|
hardforkcoin (OP)
|
 |
October 06, 2014, 05:34:59 PM |
|
Version 5 of the wallet has been released.
The difficulty retarget algo has been improved. It'll trigger after block 170000 which'll also expire all version 4.x wallets.
Will the Github issues be resolved? I'm on linux, thanks. I've uploaded the source to Google docs. |
|
|
|
samspaces
Legendary
 Offline
Activity: 1453
Merit: 1030
|
|
October 06, 2014, 05:53:03 PM |
|
Version 5 of the wallet has been released.
The difficulty retarget algo has been improved. It'll trigger after block 170000 which'll also expire all version 4.x wallets.
Will the Github issues be resolved? I'm on linux, thanks. I've uploaded the source to Google docs. Thanks! |
|
|
|
|
|
hardforkcoin (OP)
|
|
October 06, 2014, 05:57:52 PM |
|
4.x wallets are offline.
|
|
|
|
|
hardforkcoin (OP)
|
|
October 09, 2014, 05:37:55 PM |
|
5.0.1.0 has been released. This syncs 30000 more blocks.
|
|
|
|
DsD
Newbie
Offline
Activity: 9
Merit: 0
|
|
October 09, 2014, 08:12:51 PM
Last edit: October 10, 2014, 06:03:21 AM by DsD |
|
Just made a pool!!!!!! Join at http://mine. hardforkpool .tk Low 0.5% fee! |
|
|
|
|
samspaces
Legendary
Offline
Activity: 1453
Merit: 1030
|
|
October 09, 2014, 10:57:04 PM |
|
Just made a pool!!!!!! Join at http://mine. hardforkpool .tk:22500/ !!!! Low 0.5% fee! Nice work. I tried it as a pet project, but failed miserably... |
|
|
|
|
DsD
Newbie
Offline
Activity: 9
Merit: 0
|
|
October 10, 2014, 04:28:26 AM |
|
Nice work. I tried it as a pet project, but failed miserably...
I would see for some days. If no one will need it then I'll close the pool. |
|
|
|
|
DsD
Newbie
Offline
Activity: 9
Merit: 0
|
|
October 10, 2014, 04:55:23 AM |
|
I think we have to add this coin to some exchanges, maybe Poloniex...
It will be great boost for hardforkcoin.
|
|
|
|
|
|
hardforkcoin (OP)
|
|
October 10, 2014, 06:04:02 PM |
|
Thanks for the pool.
It appears nowadays these ICO/IPO things are pretty hot and standard. So we're planning to start "Trusted public to public offering" where you don't need to trust the dev with your BTC.
But before that, we're working on the diff retarget algo.
|
|
|
|
samspaces
Legendary
Offline
Activity: 1453
Merit: 1030
|
|
October 10, 2014, 07:14:30 PM |
|
Thanks for the pool.
It appears nowadays these ICO/IPO things are pretty hot and standard. So we're planning to start "Trusted public to public offering" where you don't need to trust the dev with your BTC.
But before that, we're working on the diff retarget algo.
Being standard doesn't mean being ok. I like the way coins like hardforkcoin are handled, released and no apparent money grabbing. In the long run, these coins will make it, I think. The IPO's are just there to avoid mining and get rich quick. |
|
|
|
|
|
muchoman
|
|
October 18, 2014, 04:53:24 AM |
|
Exchange coming any time soon?
|
|
|
|
|
|
hardforkcoin (OP)
|
|
October 19, 2014, 04:55:47 PM |
|
Exchange coming any time soon?
Not sure. You want to buy or sell? If you want to buy, I'll set up a "Trusted public to public offering". HFC 6.0.0.0 is up next with a new difficulty retarget algo called "Exception Detection and Rectification". |
|
|
|
|
The_Prof
|
|
October 19, 2014, 05:36:20 PM |
|
OK, well 5 mill of the coins are now out the running. Did a format and the qt keeps crashing when I load the wallet. Managed one transfer of 100 k, it crashed again and sadly now cannot be salvaged.
|
Look over there...
|
|
|
|
hardforkcoin (OP)
|
|
October 19, 2014, 05:46:50 PM |
|
OK, well 5 mill of the coins are now out the running. Did a format and the qt keeps crashing when I load the wallet. Managed one transfer of 100 k, it crashed again and sadly now cannot be salvaged.
What do you mean by 'format'? |
|
|
|
|
The_Prof
|
|
October 19, 2014, 05:49:46 PM |
|
OK, well 5 mill of the coins are now out the running. Did a format and the qt keeps crashing when I load the wallet. Managed one transfer of 100 k, it crashed again and sadly now cannot be salvaged.
What do you mean by 'format'? PC format - I reload my PC every 3 months or so. Do it with a hardware change/upgrade. But I back-up the wallet.dat on all the coins and re-load them. |
Look over there...
|
|
|
|
hardforkcoin (OP)
|
|
October 19, 2014, 05:53:01 PM |
|
OK, well 5 mill of the coins are now out the running. Did a format and the qt keeps crashing when I load the wallet. Managed one transfer of 100 k, it crashed again and sadly now cannot be salvaged.
What do you mean by 'format'? PC format - I reload my PC every 3 months or so. Do it with a hardware change/upgrade. But I back-up the wallet.dat on all the coins and re-load them. So you have the old (untouched) wallet. You tried using that? |
|
|
|
|
hardforkcoin (OP)
|
|
October 19, 2014, 06:09:13 PM |
|
Ok, I'll try and contact an exchange. Till then I'll list this in bynergy
But without votes it wont be good, that's why I'm not trying. Cause 1st we need A LOT of support to get into a good exchange.
|
|
|
|
|
The_Prof
|
|
October 19, 2014, 06:19:28 PM |
|
OK, well 5 mill of the coins are now out the running. Did a format and the qt keeps crashing when I load the wallet. Managed one transfer of 100 k, it crashed again and sadly now cannot be salvaged.
What do you mean by 'format'? PC format - I reload my PC every 3 months or so. Do it with a hardware change/upgrade. But I back-up the wallet.dat on all the coins and re-load them. So you have the old (untouched) wallet. You tried using that? Yes, with that the QT keeps crashing while trying to load the blockchain. So I loaded the blockchain with a new wallet and swapped from there. After some time the QT eventually loaded and from there I slowly tried to make a transfer to a wallet on my second PC. Moving slowly down in value from said 5M, every failed transfer crashed the QT. I finally made a transfer of 100k and then the QT has crashed along with the wallet. Whichever PC I load it on it comes up as a zero balance. I'm left with the original wallet.dat and a file called: wallet.1413731410.bak Salavage wallet while loading the QT does not work and I have come to the conclusion that I will have to mine them again, which is annoying but doable. I just would like to inform everyone that if you have a large amount from solo mining it is a wise plan to send them to a secondary wallet in larger amount transfers as the wallet seems to overload with hundreds of small transaction. This is not the only coin I have suffered it on. Giving everyone a heads up. |
Look over there...
|
|
|
|
hardforkcoin (OP)
|
|
October 19, 2014, 06:36:09 PM |
|
OK, well 5 mill of the coins are now out the running. Did a format and the qt keeps crashing when I load the wallet. Managed one transfer of 100 k, it crashed again and sadly now cannot be salvaged.
What do you mean by 'format'? PC format - I reload my PC every 3 months or so. Do it with a hardware change/upgrade. But I back-up the wallet.dat on all the coins and re-load them. So you have the old (untouched) wallet. You tried using that? Yes, with that the QT keeps crashing while trying to load the blockchain. So I loaded the blockchain with a new wallet and swapped from there. After some time the QT eventually loaded and from there I slowly tried to make a transfer to a wallet on my second PC. Moving slowly down in value from said 5M, every failed transfer crashed the QT. I finally made a transfer of 100k and then the QT has crashed along with the wallet. Whichever PC I load it on it comes up as a zero balance. I'm left with the original wallet.dat and a file called: wallet.1413731410.bak Salavage wallet while loading the QT does not work and I have come to the conclusion that I will have to mine them again, which is annoying but doable. I just would like to inform everyone that if you have a large amount from solo mining it is a wise plan to send them to a secondary wallet in larger amount transfers as the wallet seems to overload with hundreds of small transaction. This is not the only coin I have suffered it on. Giving everyone a heads up. So don't sync the blockchain. Keep your network down, and dumpprivkey for all your addresses. Import those private keys to your new wallet (or multiple wallets) and then transfer them to another address. Another alternative is to sync completely with a new empty wallet, and then copy the backed up wallet.dat. Our devs are aware of this problem in many wallets. They're seeing to it why this happens. We had these problems while testing KGW against the new difficulty retarget algo (we're benchmarking against KGW to see it's performance). |
|
|
|
|
hardforkcoin (OP)
|
|
October 20, 2014, 05:30:29 PM |
|
Version 6 of the wallet has been released. This'll sync 20,000 blocks.
New algo will trigger after block 210000.
We present 'Exception Detection and Rectification' (eDR) difficulty retarget algo which's the most responsive difficulty retarget till date. Currently there is no coin which provides better protection against both an instamine and a stuck block chain at an incredibly high difficulty.
'Exception Detection and Rectification' difficulty retarget algo is 37.68 times more effective in preventing an instamine and has 35.44 times faster recovery from an instamine (stuck block chain) as compared to KGW. Similar statistics follow for KGW siblings digishield and DGW. Further improvements are in progress to make it more effective against an instamine (maybe 60 times faster than KGW).
Paper:
To test how good eDR is compared to KGW we conducted benchmarks where regular mining was done at around 5.1 MH/s and an instamine was done at 1.15 GH/s (1150 MH/s) or around 225.5 times the regular mining power.
Configuration used for KGW is the same as in Megacoin.
Although one may expect an instamine with at best 10 times the hashing power, but we're testing on 225.5 time the hashing power.
The result of the benchmark is summarized in the links below as CSV documents. The source code of HFC which was used for the benchmark (these are not designed to run on a connected network) is also available on request. We'll provide both the HardForkcoin with KGW and eDR source, the current implementation (after block 210000) being based on eDR.
The CSV documents have 8 columns:
Block -- block no.
Diff -- Difficulty at this block.
Time -- Timestamp of the block.
Average (cumulative) -- Please ignore this.
Moving average (50 blocks) -- Moving average block interval of the last 50 blocks.
Relative to previous diff -- Difficulty up/down relative to the previous difficulty.
Relative to current diff -- Difficulty up/down relative to the current difficulty.
KGW stats interpretation --
With regular mining, the difficulty remains between 0.03 and 0.05, under mining by the instaminer, the difficulty peaks at 3.6 and then subsides to 3.5 and remains that way.
After we started an instamine at block 6410, it took 2826 blocks (and a total of 45722 seconds or a total of 12.29 hours) for KGW to reach to a difficulty 3.6 in order to prevent the instamine; at block 9236 this was finally done.
Instaming ended at block 9909 where the difficulty was left at 3.58. To reach the normal difficulty again, it took KGW 387 blocks; i.e. by block 10296 the difficulty was back between 0.03 and 0.05 range. Recovery phase took a total of 135333 seconds or 37.5925 hours.
eDR stats interpretation --
With regular mining, the difficulty remains between 0.02 and 0.05, under mining by the instaminer, the difficulty remains between 2 and 8 with an average of 4.4.
After we started an instamine at block 197, it took 75 blocks (965 seconds or 16.08 minutes) for eDR to reach to difficulty 4.x in order to prevent the instamine; at block 254 this was finally done.
Instaming ended at block 476 where the difficulty was left at 4.73. To reach the normal difficulty again, it took eDR 13 blocks; i.e. by block 489 the difficulty was back between 0.02 and 0.05 range. Recovery phase took a total of 3819 seconds or around 1 hour.
CSV data link --
KGW stats:https://drive.google.com/file/d/0B7gVckd84oOMSk0tY2ZlV1lCbk0/view?usp=sharing
eDR stats:https://drive.google.com/file/d/0B7gVckd84oOMRmZMOHhsRUFScFE/view?usp=sharing
|
|
|
|
|
