@ghostlander Agreed. Its the biggest issue I have with P2Pool. Ive tried to change the difficulty to increase the size of payouts but that seems to only help so much.
Its the same way with the P2Pool fee for running the pool, Ive got ~500FTC in fees but like 1500 transactions.

@lizhi
That is good :)

It is the expected behaviour.The next step is to keep mining with both versions, but slowly move more and more miners to 0.11.x. As far as I understood, the 'old clients should be obsoleted, as soon as more than 95% of the hash rate is on the new version.
The question is, if this woks smooth, or if we get a fork in the testnet during this step.

good job , I think testnet is running.

http://ftc11.testnet.ftc-c.com:19327/static/
http://testnet.ftc-c.com:19327/static/

I think that don’t caused a hardfork , it compatible old protocol.

I can take a look, maybe just bootstrapping it would make it look pretty

oret…thanx…
just wait d ‘solution’ is ready for android wallet then…
without worried d wallet ‘balance’ gone, rit…? :o)

Another thing…

-results of mining activity is acceptable during this ‘period’ or it will be reset after this matter solved…?

-better to stop mining or just keep mining…?

-from 2 two different pool, why both pool shows different total-network-hashrate…? GMC : 0.05 Gh\s @ 50 Mh\s , BFP-FTC : 128.27 Mh\s

@wrapper said:

I note the Invalid checkpoint found!, ppcoin fork has occurred again.

There a couple of points from FTC experience, the first is the confusion about which is the correct fork and no help from Sunny King?

Hopefully there will be a more complete update, plus it would be worth following in case it is due to auto check pointing, and may effect FTC …

https://github.com/ppcoin/ppcoin/issues/100#issuecomment-181826754

That is why I like Vericoin. They are 100POS and managed to remove synchronization checkpointing.

I didn’t understand this paragraph from BIP 113, that might effect pools. I assume p2pool head will have included a fix…

Implication for users:
GetMedianTimePast() always trails behind the current time, so a transaction locktime set to the present time will be rejected by nodes running this release until the median time moves forward. To compensate, subtract one hour (3,600 seconds) from your locktimes to allow those transactions to be included in mempools at approximately the expected time.

Yes I agree with @Wellenreiter, pchMessageStart additional Genesis message - is important and worth doing.

It has effected running multipools, and was also “the” major criticism of FTC, and also Ghostlander did a fix for us, which we should be able to push easy enough?.

I think it was pressure of doing other changes and the hard fork that prevented @Bushstar from pushing the change from Pheonixcoin, as @Ghostlander did the fix after Neoscrypt.

Perhaps a bounty for Ghostlander to push a patch to FTC? (As he created it? and @Lizhi is already doing a very lot :))

@Guest be aware of shapeshift phishing:

https://shapeshift.io/site/blog/2016/01/18/please-read-note-scam-social-media-accounts-and-website

Yes, all versions can connect to each other.
But pool daemon should run 0.11.1 ,it make block 2 or block 3. but 0.8.7 only make block 2 and don’t accept blocks 3.

main.cpp ,line 2249.
/* Don’t accept blocks with bogus nVersion numbers after this point */
if((nHeight >= nForkFour) || (fTestNet && (nHeight >= nTestnetFork))) {
if(nVersion != 2)
return(state.DoS(100, error(“AcceptBlock() : incorrect block version”)));
}

@wrapper said:

http://forum.feathercoin.com/topic/7597/help-feathercoin-create-a-full-node-on-a-raspberry-pi

Thank you wrapper

@thebobinater
We didn’t follow up on this.

We had a similar idea to separate the block chain and it’s tools/services from the wallets, but other tasks took preference.

If you are willing to follow up on this and re-code it for feathercoin, It’s highly appreciated. May be @kris_davison also can find some time to code some parts.
kris was very quiet lately due to familiy affairs :dancer:

By the way, there is a comparable solution offered by a worldcoin guy here which seems to be interesting, but also a bit complex.

https://github.com/feathercoin2/Feathercoin2

Still watching your hard work Lizhi, thanks again…

@shadowhh32 said:
…
…
As of now, all we have is the daemon, not the wallet client for Linux-es. WE WANT the WALLET. The WALLET is what were after.We need to repack and rebuild everything now.
…
…

The wallet will come soon for Linux. Compilation works, packaging is in progress, but if a Package for Fedora can be built is open.

The hardening option is default for Core 0.9.3 and uses PIE.
You need to actively disable it with the --disable-hardening parameter passed to the configure script.