Go spam on your own thread

Simple Blockcrawler
http://blockcrawler.rf.gd/index.php

Would need a "always on Node" temporary i am using my one

Donation/Bounty:
Flap FHt6NQ57seYkRMFDp75w27UNU4m42Wh4SR
ETH 0x61ecb00f1042a6f92aea4b0740d31a7aba270762
Doge D6PRqCegz3tAebZtEqBv3cyyJVFTyDuU4T

It followed the update to litecoin core which went from 70002 to 70003 , many coins out there didn't use the newer litecoin code, thus the many 70002 versions.

Based on a year old reddit post, flappy also at one time had a 70005 protocol version (staking fix?) , , tho, there are probably not all that many old wallets around now..

66coin killed itself when the dev added code to disconnect nodes with blocks that new nodes didn't like, don't do that, it splits the network into 2 sets of nodes, one each on each rule set, because nodes can't get the correct blocks because other nodes disconnect them before they can get any new block data, so there is no hope of the orphaned half of the network ever getting the right chain back. just make consensus rules reject the blocks, that is all you needed here really...(it still forks, but the new clients would accept blocks mined under the old rules, so it would tend to keep bridging the chains, so you don't get a massive split, just lots of random orphan chains until everyone upgrades)

Likely doesn't matter so much with flappy right at the moment, since all the nodes are in the room so to speak, just wanted to point out the disconnect thing is potentially hairy


the first fork i did took place before the pos addition this coin will not pos
....trust me the tea and i mined ahead 20k blocks to see what was going to happen , we had help from
several devs looking over the code over months  . the second was to fix an issue that was caused buy low paying blocks and high fees
the reason we had a problem ...im pretty sure is i listed the proto number incorrectly .. someone changed in there local wallet becoming the sync node since their proto number was the highest on the network.... however since they were blocking the lower end they were not handing out any blocks thus taking off with the chain ... ive made the corrections. also ive added two seednodes and most of you are on windows that causes issues when no win wallet was available yet  its seriously on me i was in error .. however its not the hardest time ive had with this coin it took 3 months to get it cleaned up enough in the first place .. i save the chain often its unlikely the coin will ever break break again after we get started and if it does we will simply make the fix ... sorry guys my bad im just glad it happend now i want is to have a good 200-300k blocks without having to make any changes hopefully were good as gold now . im updating chains on the nodes now and then ill just bee making sure we have connection . 

Looks like there was a ton of chaos here in the last day.

I'm sure this coin can survive another hard fork... as it's done it enough times in the past with more hash power. However, was this necessary? Reducing the default transaction fee is not even a soft-fork change. Blocks accepted at a lower transaction fee are still valid in the blockchain for the old clients. You can just introduce the lower fees by adding more hashpower with the new clients (basically what we started doing last week with command-line options), then the whole network retains its hash power and low-fee transactions eventually make it through, even more so as time goes on and users migrate.

Hard forks are required for changing the block reward, so maybe that's at hand here too? (edit: ok, now I see the title that says "payouts" are fixed, so sounds like it.) If so, it would be nice to see the specific changes to the code. At https://github.com/Flapmin I only see the old repo.

edit: Found and earlier post with the link https://github.com/Flapmin/FLAPsp1 but that is 404 now.

Cool. There were a couple places with VERSION in the p2pool code that initially seemed to have no effect. I was probably supposed to be set to 91337 there as well, although apparently you guys are changing it again.

In the future I think we should be cautious about changing this number. Although the FlappyCoin 2014 developers may have haphazardly set it to 70003, most other coins keep it at 70002. p2pool probably isn't the only codebase that doesn't play nice with such changes.

I'd be interested in getting my MinGW environment back into shape. How much is the bounty for?

As I mentioned I could use some prebuilt static binaries for boost, db4.8, openssl, miniupnpc. So perhaps you could get me in touch with your super-busy friend so he could send those over?

Is it safe to pull down and recompile?

No I dont believe I did but I did port forward so people can add my node and use it. Also about the payouts... unfortunately I dont know as I have no wallet to verify the coins being moved. If you get a GUI up I can mine using your address and we can verify

I didnt have to change anything with flappycoind. I just ran make -f makefile.unix nothing else. I'm finding blocks no problem. I just had to change a config file in p2pool to update the protocol version

I didnt have to change anything with flappycoind. I just ran make -f makefile.unix nothing else. I'm finding blocks no problem. I just had to change a config file in p2pool to update the protocol version

No I just compiled. However my pool wouldnt connect until I changed the version to 92845. Now things are good. I had that error outdated message but I restarted the node and it went away.

Are those with port 11556 ?
You can add my node addnode=172.91.203.163:11557