Topic: deleted - page 33. (Read 68074 times)
NICE!!! Thanks @AllCrypt !!
HFC has just been added to AllCrypt.com! The coin is live and available right now, although the blockchain might still be downloading - if so, deposits and deposit address generation will not be available until the blockchain is complete.
We have (or will very soon) post an announcement on Twitter as well. Follow us on twitter (@all_crypt or https://twitter.com/All_Crypt) to help spread the word and keep abreast of site news and updates.
We'd appreciate being listed as an active exchange in the OP of the this thread. If you'd like a high quality PNG logo to use, a zip is available at: http://www.allcrypt.com/aclogopack.zip
Important note: It sucks for everyone when there is a fork, or a version upgrade, and we don't get notified. Sometimes developers just tweet that there is an upgrade. We're busy running the site - very often we miss tweets - we get a lot every day! If there is an emergency upgrade, a hard fork coming in less than a week, a major issue that requires an immediate upgrade, if it's tweeted at us we may not see it. The only truly RELIABLE way to ensure we know about a mandatory upgrade is to submit a support ticket. Just have someone hop by http://support.allcrypt.com and let us know. We see those all the time, including on the dev staff's mobile devices.
If for some reason your github source changes (community takeover for example) PLEASE let us know that in the ticket. Our system is highly automated, and if you issue a new source code under a new git address, we won't know unless thats provided - our system will check the old address for the new version. Since we save it, you only need to worry about it if the github location changes. In all other cases, just letting us know we need to upgrade is enough!
I think that covers it! Thanks for your support of AllCrypt and we're proud to support you in return!
We have (or will very soon) post an announcement on Twitter as well. Follow us on twitter (@all_crypt or https://twitter.com/All_Crypt) to help spread the word and keep abreast of site news and updates.
We'd appreciate being listed as an active exchange in the OP of the this thread. If you'd like a high quality PNG logo to use, a zip is available at: http://www.allcrypt.com/aclogopack.zip
Important note: It sucks for everyone when there is a fork, or a version upgrade, and we don't get notified. Sometimes developers just tweet that there is an upgrade. We're busy running the site - very often we miss tweets - we get a lot every day! If there is an emergency upgrade, a hard fork coming in less than a week, a major issue that requires an immediate upgrade, if it's tweeted at us we may not see it. The only truly RELIABLE way to ensure we know about a mandatory upgrade is to submit a support ticket. Just have someone hop by http://support.allcrypt.com and let us know. We see those all the time, including on the dev staff's mobile devices.
If for some reason your github source changes (community takeover for example) PLEASE let us know that in the ticket. Our system is highly automated, and if you issue a new source code under a new git address, we won't know unless thats provided - our system will check the old address for the new version. Since we save it, you only need to worry about it if the github location changes. In all other cases, just letting us know we need to upgrade is enough!
I think that covers it! Thanks for your support of AllCrypt and we're proud to support you in return!
I'm thinking about renaming this coin.
We'll have a poll soon about this.
We'll have a poll soon about this.
The websites are now secure with https.
7819, are those unique views? Anyway, I will twitter about HFC again. Dev, keep up the good work!
No, those are just page views.
7819, are those unique views? Anyway, I will twitter about HFC again. Dev, keep up the good work!
Any decent exchange coming, bittrex, c-cex?
Where are we going to get the volume and votes from? This coin must be popular to come in those exchanges. Currently there are only 7819 page views.
Sorry, I forgot to upload the blockchain data from the benchmarks.
Now it's there.
Now it's there.
So the only pool from the op has 0kh. Where do I mine this?
At home with either the wallet or a gpu.
No kidding? So solo mining only?
There is a pool, you can use that. If there is no one mining in the pool, that doesn't mean you cant mine on it.
Sorry, I forgot to upload the blockchain data from the benchmarks.
Now it's there.
Now it's there.
So the only pool from the op has 0kh. Where do I mine this?
At home with either the wallet or a gpu.
No kidding? So solo mining only?
Any decent exchange coming, bittrex, c-cex?
Sorry, I forgot to upload the blockchain data from the benchmarks.
Now it's there.
Now it's there.
So the only pool from the op has 0kh. Where do I mine this?
At home with either the wallet or a gpu.
Sorry, I forgot to upload the blockchain data from the benchmarks.
Now it's there.
Now it's there.
So the only pool from the op has 0kh. Where do I mine this?
Sorry, I forgot to upload the blockchain data from the benchmarks.
Now it's there.
Now it's there.
Miners must notice the more stable difficulty compared to the previous algo.
That explains why --
Code:
"startingheight" : 210000
Someone in the network has modified the 5.0.1.0 wallet to work beyond 210,000 blocks.
5.0.1.0 is incompatible with 6.0.0.0, your wallet has probably stopped syncing cause it rejected mined blocks by the genuine 6.0.0.0 wallet.
Any mining done using this wallet will be rejected by other nodes, including the seed node.
Don't complaint if you loose your balance.
5.0.1.0 is incompatible with 6.0.0.0, your wallet has probably stopped syncing cause it rejected mined blocks by the genuine 6.0.0.0 wallet.
Any mining done using this wallet will be rejected by other nodes, including the seed node.
Don't complaint if you loose your balance.
[/quote]
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.
[/quote]
Something similar happened to me once, wrote this post about it:
"For those interested: I had a 'corrupt wallet' after a reboot without shutting down vertcoind. Balance was gone, new wallet.dat and another file named wallet.dat.rewrite. After some tinkering, renaming the 'wallet.dat.rewrite' to 'wallet.dat' recovered the original wallet. "
Perhaps it's of help.
Impressive work on the difficulty retarget. This coin should be getting more attention. It's listed at bynergy.com.
A request has been sent to bynergy.com
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
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
Jump to: