Feathercoin 0.8.6
-
Coin control lets you choose exactly which address the fund are coming from and where the and where the “change” should go.
-
Oh ok. Cheers for that.
-
Nice! Will you be tagging it 0.8.6 once you’re through with test?
I’ll roll this up into a FreeBSD Port - though still no movement on the original Port getting into their repo, though. I’m pretty disappointed with their process atm.
-
Nice! I am compilying it . How many lines of code 0.8.6 ?
-
Nice! Will you be tagging it 0.8.6 once you’re through with test?
I’ll roll this up into a FreeBSD Port - though still no movement on the original Port getting into their repo, though. I’m pretty disappointed with their process atm.
This will be tagged as 0.8.6. So far no problems have been reported.
Nice! I am [background=#ffffff]compilying it . [/background][background=#ffffff]How many lines of code [/background][background=#ffffff]0.8.6 ?[/background]
To see the code changes please go to GitHub and look at the commits on Feb 26.
https://github.com/FeatherCoin/Feathercoin/commits/master-0.8.6?page=1
-
I agree, looking at the changes, it is a good move forward.
Cheers Peter! more Rep ++
-
Is it just me, or is there a buzz around this place since the forum changed? Top work. ;D
-
I’ll get a version down later, stuff it in a VM and have a play with it. Will try and get back to you over the weekend…
UM
-
Coin Control : Correct !. I choice some ftc ,then pay to bter.com, Correct !
-
I noticed the compile error
/home/tony/Feathercoin/src/main.cpp:2323: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 2 has type ‘int64 {aka long long int}’ [-Wformat=]
return error(“ProcessBlock() : block has a time stamp of %u before the last checkpoint of %u”, pblock->GetBlockTime(), pcheckpoint->nTime);
1. As this is Checking / checkpointing, and has the error integer missmatch. Just checking it is absolutley not a problem?
2. What is our position on moving to Qt5 compile?
-
No, that is no problem.
as the message says, it is a warning and means, that you give parameter of format in64 to a function that expects format unsigned int.
As both types are integer, there should be no problem.
-
I compile it success with win7 32bit system.
-
Up and running!
Thanks for the heads up
