FlapXcoin Back on the move Listings, Pools, Games, More. Flappycoin, FLAP FLAPX

[wailord284]

ok so where did you change it its hard codded i may need to make another backup and sort all this out
I was very sure it was all working before i compiled the last time i was getting paouts from the pool ect
but if im going to have to re re re release i should do it now so were not oprpaining

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

[Flapmin]

ok so where did you change it its hard codded i may need to make another backup and sort all this out
I was very sure it was all working before i compiled the last time i was getting paouts from the pool ect
but if im going to have to re re re release i should do it now so were not oprpaining

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

are you getting your payouts ... and by that are you getting a payout to any other address
OTHER THEN to the pool hot address and the reward/fee addresses  if you are very cool
if not then its not working . you dont have anyone to confirm the blokes and i
have to go back and debug and hard code a few nodes in ..
 

[Flapmin]

im going to pull my pool wallet down into a gui and see whats what

[Flapmin]

ok so where did you change it its hard codded i may need to make another backup and sort all this out
I was very sure it was all working before i compiled the last time i was getting paouts from the pool ect
but if im going to have to re re re release i should do it now so were not oprpaining

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

ok one more question did you announce yourself as a syncnode in any changes

[wailord284]

ok so where did you change it its hard codded i may need to make another backup and sort all this out
I was very sure it was all working before i compiled the last time i was getting paouts from the pool ect
but if im going to have to re re re release i should do it now so were not oprpaining

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

ok one more question did you announce yourself as a syncnode in any changes

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

[Flapmin]

ok so where did you change it its hard codded i may need to make another backup and sort all this out
I was very sure it was all working before i compiled the last time i was getting paouts from the pool ect
but if im going to have to re re re release i should do it now so were not oprpaining

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

ok one more question did you announce yourself as a syncnode in any changes

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

yea thats where my head is at im pulling the .flappycoin down now off the server to run in gui ill let you know what i find out

[Flapmin]

im going to go ahead and rebuild from source too i want to make sure
this is not some stupid qt file in the cashe shill from when i was working

[Flapmin]

IM going to have to fork again with a windows wallet already in place ... anyone mining id go ahead and back off im going to leave the deamon running for the moment ill grab as much of the current chain as i can and ill set up a few extra nodes hard codded .... give me a few hrs

[Flapmin]

Ill be making a checkpoint from block 779500
any blocks found after that will be orphaned
submitting wallet for windows build
Please recompile for pool and daemon operators and enthusiasts
the issue is a protocol one atm ill be putting up 3 nodes at launch
hopefully this is all the maintenance to get us threw to 900k+ blocks

[n00bminer]

Ill be making a checkpoint from block 779500
any blocks found after that will be orphaned
submitting wallet for windows build
Please recompile for pool and daemon operators and enthusiasts
the issue is a protocol one atm ill be putting up 3 nodes at launch
hopefully this is all the maintenance to get us threw to 900k+ blocks

Is it safe to pull down and recompile?

[Flapmin]

Ill be making a checkpoint from block 779500
any blocks found after that will be orphaned
submitting wallet for windows build
Please recompile for pool and daemon operators and enthusiasts
the issue is a protocol one atm ill be putting up 3 nodes at launch
hopefully this is all the maintenance to get us threw to 900k+ blocks

Is it safe to pull down and recompile?

no ill pull it down
its not going to hurt just waist your time
there is an error in the proto version listed
and what is being used just waiting for the p2p pool to hit block
779500 about 40 min and ill grab the checkpoint and recompile and upload

[Flapmin]

see we stopped on the chain a few blocks early thanks everyone ill get on the checkpoint now

[hanzou]

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.

I have the pool pretty much good and can change things as time goes on but, I just started getting this message on the p2pool site:
Warning: (from bitcoind) Warning: This version is obsolete, upgrade required!

However, I am still able to mine and am receiving rewards. Thoughts?

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.

chance you will claim the bounty for win wallet??

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?

[Flapmin]

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.

I have the pool pretty much good and can change things as time goes on but, I just started getting this message on the p2pool site:
Warning: (from bitcoind) Warning: This version is obsolete, upgrade required!

However, I am still able to mine and am receiving rewards. Thoughts?

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.

chance you will claim the bounty for win wallet??

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?

The bounty is 50 million ATM

[Flapmin]

im about to test the nodes window wallet guy says he will have time in about 30 min

[Blurb]

...FlappyCoin 2014 developers may have haphazardly set it to 70003, most other coins keep it at 70002.

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

[Flapmin]

...FlappyCoin 2014 developers may have haphazardly set it to 70003, most other coins keep it at 70002.

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 . 

[Flapmin]

So jet this shit ... i just spent 5 hrs fighting with rpc password issues and nodes .....
it would not connect until i took the numbers out of my password and user name in the .conf

is this a know node js issue ?



anyway immediately nodes fired up and connected after i found that bug

finishing setting up waiting on the win wallet guy

[Flapmin]

anyone up i have the win wallet gonna work on the ann and links before i crash out

[Flapmin]

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

give me a bit ive not had a chance to look at it pm me the link you would like me to use for ann