Feathercoin 0.8.6.2 Released - Hard fork on block 204,639
-
There seems to be a problem with the links on the homepage.
Until this is fixed you can find the pre-compiled Linux binaries here:
http://software.opensuse.org/package/feathercoin
There are binaries for several Linux distributions, not just Opensuse ones on this server
-
Only binaries available for Linux?
I was pulling from the git repo but I’m getting the 0.8.6.0-beta. Where are the sources for the 0.8.6.2?
Thx
-
Only binaries available for Linux?
I was pulling from the git repo but I’m getting the 0.8.6.0-beta. Where are the sources for the 0.8.6.2?Thx
Running the follow is all that is required to get the 0.8.6.2 release.
git clone https://github.com/FeatherCoin/Feathercoin.gitIf you are not deleting the old folder try running for the daemon.
make -f makefile.unix clean -
-
Bushstar,
perfect I now have the newest version running. I was keeping pulling wrom the prev version. My bad!
Thx for the help.
-
There seams to be some problems with the download links on the front page under certain browser conditions!
So until they are resolved if your looking for the downloads they can be obtained from the following locations:
All download issues have been moved to this support thread
UM
-
Can someone post the download link to the direct feathercoin-qt.exe?
I don’t want to install it, would like to just run it.
-
Just checked and we have 355 blocks to go…
-
That looks about 12 o’clock tonight then. That means I can nip out to the shop, I thought I had to wait in for the fireworks! :)
-
Can someone post the download link to the direct feathercoin-qt.exe?
I don’t want to install it, would like to just run it.
If you follow the guide in Technical Development, you can compile your own version, directly from the source, in a VirtualBox.
As this is Linux it’ll run fine under windows, but is isolated from your “real” system. It also explains how you can read through the source code, by using Qt Creator to compile he source code. Now 0.8.6.2 has been released you just compile the standard version.
-
I thought that the time had shifted a little :)
Glad about that as I have to go to the office for meetings today, and wanted to be here when it happened to see what was going on.
Ahh just remembered another wallet that needs upgrading…
-
Here’s a direct link for the Zipped Feathercoin.
https://www.feathercoin.com/dl/feathercoin-0.8.6.2.zip
So 173 blocks to go, that should be about 7.2 hours at 02:30 UTC. Alerts are still ticking on 0.6.4.4 to the 0.8.6 releases and I have sent one last round of messages on social media. I can still see quite a lot of old clients connecting to the network. We’ve even spotted some 0.6.3 clients that stopped being compatible months ago so no idea what those guys are doing on the network. We can expect a fair few support requests tomorrow.
Clients not updated will still subscribe to the autocheckpointing node so they will get told to connect to blocks that are incompatible with the client. There is a chance that after updating they will have database errors. This is the problem we experienced last time with BDB. If this is what gets reported the solution is to stop the client, go to the data directory and delete the blk0001.dat, blkindex.dat, blocks folder and chainstate folder and then start the client again. The blockchain will have to download but the client should work fine at the end.
-
We’re currently at 6:39 per block, but we’re close to a difficulty adjustment. Block time’s are going to drop soon.
http://www.cryptocoinstats.com/hashratetrackerdetail.php?ac=FTC
-
Looking at the block explorer, someone has got a plenty of easy blocks when the difficulty has dropped from 199 to 1.4 in less than half an hour.
http://explorer.feathercoin.com/chain/Feathercoin?count=500&hi=204860
-
Looking at the block explorer, someone has got a plenty of easy blocks when the difficulty has dropped from 199 to 1.4 in less than half an hour.
http://explorer.feathercoin.com/chain/Feathercoin?count=500&hi=204860
There was no special case to take care of the 2.5 minute blocks calculated into the average after the change so were regarded by the new algo as being too hard. We now have enough history under the new algo for things to behave like expected. We have been tested only a little so far, some fast blocks were seen, the difficulty went up, the blocks got a little long and then the difficulty came swiftly down. It will not be long before some of the larger players try to abuse our new solution. This is very interesting to watch.
As long as everything is good with our new solution then we should look toward our new solution post haste.
For those who do not know, Ghostlander is working on his idea called NeoScrypt, the fastest and most efficient version of Scrypt so far that will not be broken by differential analysis for at least a decade it is imagined. I think it is a genius idea like the light bulb, something that seems obvious now but before it took a genius to figure it out :)
-
I am truly excited in every sense of the word.
This is partially what crypto’s are about.
It’s the grand social experiment of the 21st century. -
Looking at the block explorer, someone has got a plenty of easy blocks when the difficulty has dropped from 199 to 1.4 in less than half an hour.
http://explorer.feathercoin.com/chain/Feathercoin?count=500&hi=204860
I have analysed the preliminary results from the hard fork change over in greater detail.
Handling the change over to one minute transaction blocks took about 130 blocks. Between 13:18am and 13:35am or about 15 mins. 25th/04/2014. By 02:00 the block transaction time had settled to 1 minute for 60 block average. The block times are still settling down as it come fully in.
If any other coins attempt such a change over I would recommend including a period where both cases apply. In this case, for say the first 200 blocks, the data for calculating the new difficulty should have been based on a special case of old look back times (2.30min) divided by the 2.5 to convert old data look back times to 1min equivalents.
This would mean the Block time would have moved gradually move from one value to another. Our change over was a bit sudden.
That’s also a lot of extra software programming and testing for a once only event, so more to go wrong and all miners at the time benefited from the lower difficulty so it wasn’t “unfair” to any one particular interest.
Considering the severity of the swerve, I’m very relieved to see we’re still on the road.
Well done team!
-
Unless the two profitability calculators I tried are wrong, I am slated to get less FTC per day mining than I was before the hard fork :-/
-
The statistics calculations are probably are wrong, and will need a slight tweak, due to the block transaction time change.
Wellenreiter did some updates for p2pool. Even so the graphs on that pool are per block, so they show the proportional value of a block.
The transaction time as gone down so you will be paid smaller amounts but more often.
You should get the same payment per 2.5 mins, if not more, as the dust settles from the hard fork…
-
Posted here …
