sorry if the pool is going up and down im about to resize to a lager unit it may take 15 min at the most not sure when but in the next few hrs
System load: 0.88 Processes: 86 Usage of /: 54.3% of 19.65GB Users logged in: 1 Memory usage: 96% <<< may go back down after updating netcoin blockchain
|
|
|
I've made a source repo: https://github.com/hanzou-x/Flappy5 and invited you both for write access. By basing it off the old Flappy5 you can easily see the Sp2 differences in terms of the block reward, default transaction fees, and images. I even notice a bug where one image seems to have been mis-copied. I'll be posting a macOS client binary from this source later tonight. hey so do you guys have a p2p pool up and going or are you mining over here . if you have a working pool id like to throw some hash on in and perhaps use it as a failover , if you dont mind people mining ill add it to the first page also i have all the weekly builds from the last 6 months or so if you want to look at some more changes i guess better yet would be if we put up the source i first compiled from next to the current ?
|
|
|
looking at this bcc split thing not sure what to think about it
|
|
|
I just dont know how i feel about a fork of bitcoin that allows anyone who has the majority of the btc to have the majority of bcc... why did you not clone bitcoin make your changes and start mining over . seems your killing the price immediately with a premine in a way . lets say im a new user day zero . why would i invest when there are already millions of coins
|
|
|
I've made a source repo: https://github.com/hanzou-x/Flappy5 and invited you both for write access. By basing it off the old Flappy5 you can easily see the Sp2 differences in terms of the block reward, default transaction fees, and images. I even notice a bug where one image seems to have been mis-copied. I'll be posting a macOS client binary from this source later tonight. I see your notes and you are correct the info withing the coin pertaining to the coin has not been kept up with at all and in fact there are several 100 lines that have just been commented out we have a final release planed in about 10 weeks with a bunch of build updates that were never upgraded I suggest as soon as it goes to debug we will get a git copy up there so we can take several weeks to clean it up prior to release
|
|
|
morning guys looking at your posts now . ill work on my relationship with git in this round ive got a few build issues with beaveroin i need to work out and then ill see what i can see ...other then that wallet working stable for everyone ?
|
|
|
@flapmin, n00bminer: Got the source now on correct level. flapmin : you have write access, and ofc you can have ownnership. We really need to have the repo on github, version branches changes can be made there very easy, and with pull and push, etc .. you can get everything nice to your workstation and backup to github again. https://github.com/derubm/Flapsversion.h : (nothing changed) PROTOCOL_VERSION = 1111337;
clientversion.h: (updated to predicted Version Number 3.2.1), added Copyright 2014-2017. #define CLIENT_VERSION_MAJOR 3 #define CLIENT_VERSION_MINOR 2 #define CLIENT_VERSION_REVISION 1 #define CLIENT_VERSION_BUILD 0
can you think of why im only getting the readme in the push it would seem to me i need to push from one directory higher or im not cataloging the files proporly
|
|
|
Hasn't Flappycoin been dead some time ago?
Yeah. For better or worse a dead coin is easier to keep forking in an attempt to revive it... Okay, as for getting the proto-111137 chain moving, I guess the problem was nobody was mining for the past two hours. As soon as I turned it on http://blockcrawler.rf.gd/index.php?i=1 shows my blocks and I'm reaping these ridiculous 12500 block rewards every few seconds. that is correct. been mining with 330 kh the entire time ill make sure im on the same block as crawler
|
|
|
@flapmin, n00bminer: Got the source now on correct level. flapmin : you have write access, and ofc you can have ownnership. We really need to have the repo on github, version branches changes can be made there very easy, and with pull and push, etc .. you can get everything nice to your workstation and backup to github again. https://github.com/derubm/Flapsversion.h : (nothing changed) PROTOCOL_VERSION = 1111337;
clientversion.h: (updated to predicted Version Number 3.2.1), added Copyright 2014-2017. #define CLIENT_VERSION_MAJOR 3 #define CLIENT_VERSION_MINOR 2 #define CLIENT_VERSION_REVISION 1 #define CLIENT_VERSION_BUILD 0
yes git hub and i had a falling out but were in counseling
|
|
|
well the node is sync'd to "version" : 3020000, "protocolversion" : 92845, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 779459, "timeoffset" : 0, "connections" : 0, "proxy" : "", "difficulty" : 0.00024414, "testnet" : false, "keypoololdest" : 1500573464, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.01000000, "errors" : ""
but no connections. addnode'd all the uBm listed... This was rolled up with the same bootstrap the desktop used, and worked.... this node was connected before so I know iptables is open. I may delete the blockchain again, and see what's up
"protocolversion" : 92845, <<<you need to rebuild flappysp2 you are still running old flappy sp1the new wallets will not allow you to handshake with them recompiled from the zip and it is the right version now all good?
|
|
|
[2017-07-28 06:52:16.395] [FATAL] [default] - Pool flappycoin Thread 1 Share rejected: {"job":"8d","ip":"146.185.151.11","worker":"FPgUwTD1c9WQ91CSQUfposuAbAaRMo3GYq","difficulty":512,"error":"low difficulty share of 0.00001560141472673674"} [2017-07-28 06:52:16.983] [FATAL] [default] - Pool flappycoin Thread 1 Share rejected: {"job":"8d","ip":"146.185.151.11","worker":"FPgUwTD1c9WQ91CSQUfposuAbAaRMo3GYq","difficulty":512,"error":"low difficulty share of 0.000032508198158847866"}
Usually that error means the share your miner submitted was garbage, and didn't actually verify on the pool. Sometimes it means the share was submitted too late, and the pool has already moved on to the next block. But if you keep getting it over and over, then your miner code is broken (or you're using the wrong algorithm).
if thats your address you not hitting any shares
|
|
|
SPOTS uNOMP POOL -o stratum+tcp://http://138.68.234.216:3009 -u yourspotscoinaddress -p x Fixed 128 Diff. -o stratum+tcp://http://138.68.234.216:3033 -u yourspotscoinaddress -p x Vardiff 32/256. -o stratum+tcp://http://138.68.234.216:3257 -u yourspotscoinaddress -p x Fixed 512 Diff. min payout of 10 coins
|
|
|
POOL BACK UP i needed to make a snapshot
|
|
|
well the node is sync'd to "version" : 3020000, "protocolversion" : 92845, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 779459, "timeoffset" : 0, "connections" : 0, "proxy" : "", "difficulty" : 0.00024414, "testnet" : false, "keypoololdest" : 1500573464, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.01000000, "errors" : ""
but no connections. addnode'd all the uBm listed... This was rolled up with the same bootstrap the desktop used, and worked.... this node was connected before so I know iptables is open. I may delete the blockchain again, and see what's up
"protocolversion" : 92845, <<<you need to rebuild flappysp2 you are still running old flappy sp1the new wallets will not allow you to handshake with them
|
|
|
What is the use of the coin ?
the coin is from 2013 abandoned I think about two years ago when it started to break. So the purpose of the coin as far as my part now was to return the coin to the community. However it has a gaming background one of our member posted this information on word press https://flappycoins.wordpress.com/
|
|
|
Ill be restarting the pool at 11PM
|
|
|
compiling my node now. Will have to resync.
Will be 198.98.48.192:11556
what will be
|
|
|
Yes, that list is unhelpful because the only active nodes in it are on the 91337 chain.
As I mentioned above the only proto-1111337 peer I am getting is 94.61.193.156:11556. It's probably the blockcrawler node itself, so you can add that to your flappycoin.conf if you really want to get in on this.
94.61.193.156:11556.... This IP is mine. not from the blockcrawler node... the node are running fine i paid for them and set them up myself .
Seriously. What are you doing? Let it die already.
bump our thread bitch
First question: 10000 blocks for for this large block reward makes for about three hours of mining. Is it already over at the time of writing? The bounty is 50 million ATM Looks like the Windows wallet is now available at https://github.com/Flapmin/FLAPsp2WinQt so no more bounty. It would be nice to get my build environment set up regardless. Can you send me the MinGW builds for boost, db4.8, etc. or connect me with the person who has these? 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 Thanks Blurb. This is helpful. 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. From what I can tell, although the latest litecoin source broadcasts protocol version 70015, its MIN_PEER_PROTO_VERSION is still 70002 so it doesn't mess up p2pool and other standard tools like we're seeing with flappycoin. version.h:static const int GETHEADERS_VERSION = 70002; version.h:static const int MIN_PEER_PROTO_VERSION = GETHEADERS_VERSION;
strattum connection refused on the pool all ports. Isn't stratum for pooling only? Seems like we need to get our solo wallets (Mac, Linux, and required source code) working first after this large change. edit: The protocol version now says 1111337. Remember that protocol versions increase sequentially, so if we go to that one now every future protocol version has to have at least 7 digits. We still have 3 digits to go before hitting maxint, but this seems a bit reckless. As for running the wallet, it says two hours behind and I'm stuck at block 779980, I have only one proto version 1111337 peer at: getpeerinfo [ { "addr" : "94.61.193.156:11556", ... "version" : 1111337, .. } ] and http://blockcrawler.rf.gd/index.php?i=1 says it's also still downloading the blockchain. Hope this doesn't sound crazy, but given the situation (what Blurb said regarding disconnects, having more protocol 91137 nodes at the moment, the fact that somehow we got convinced to download a wallet without source code, and general bugs which would be easier to troubleshoot on a single chain), could I get the room to consider not forking? If the only intent of this is to resolve the transaction fees we already know we can do that without a fork. Checkpointing and building a cleaner Windows wallet can also be done regardless. no 10k blocks is a week and if you look at the rewards to come up its one of the smaller bumps
I had 2 very good reasons to hold source for a few hrs now the network seems to be all good . im gonna get someone to push it for me git hub and i are not on speaking terms ...
uploading taking a bit
First question: 10000 blocks for for this large block reward makes for about three hours of mining. Is it already over at the time of writing? The bounty is 50 million ATM Looks like the Windows wallet is now available at https://github.com/Flapmin/FLAPsp2WinQt so no more bounty. It would be nice to get my build environment set up regardless. Can you send me the MinGW builds for boost, db4.8, etc. or connect me with the person who has these? 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 Thanks Blurb. This is helpful. 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. From what I can tell, although the latest litecoin source broadcasts protocol version 70015, its MIN_PEER_PROTO_VERSION is still 70002 so it doesn't mess up p2pool and other standard tools like we're seeing with flappycoin. version.h:static const int GETHEADERS_VERSION = 70002; version.h:static const int MIN_PEER_PROTO_VERSION = GETHEADERS_VERSION;
strattum connection refused on the pool all ports. Isn't stratum for pooling only? Seems like we need to get our solo wallets (Mac, Linux, and required source code) working first after this large change. edit: The protocol version now says 1111337. Remember that protocol versions increase sequentially, so if we go to that one now every future protocol version has to have at least 7 digits. We still have 3 digits to go before hitting maxint, but this seems a bit reckless. As for running the wallet, it says two hours behind and I'm stuck at block 779980, I have only one proto version 1111337 peer at: getpeerinfo [ { "addr" : "94.61.193.156:11556", ... "version" : 1111337, .. } ] and http://blockcrawler.rf.gd/index.php?i=1 says it's also still downloading the blockchain. Hope this doesn't sound crazy, but given the situation (what Blurb said regarding disconnects, having more protocol 91137 nodes at the moment, the fact that somehow we got convinced to download a wallet without source code, and general bugs which would be easier to troubleshoot on a single chain), could I get the room to consider not forking? If the only intent of this is to resolve the transaction fees we already know we can do that without a fork. Checkpointing and building a cleaner Windows wallet can also be done regardless. no 10k blocks is a week and if you look at the rewards to come up its one of the smaller bumps
First question: 10000 blocks for for this large block reward makes for about three hours of mining. Is it already over at the time of writing? The bounty is 50 million ATM Looks like the Windows wallet is now available at https://github.com/Flapmin/FLAPsp2WinQt so no more bounty. It would be nice to get my build environment set up regardless. Can you send me the MinGW builds for boost, db4.8, etc. or connect me with the person who has these? 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 Thanks Blurb. This is helpful. 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. From what I can tell, although the latest litecoin source broadcasts protocol version 70015, its MIN_PEER_PROTO_VERSION is still 70002 so it doesn't mess up p2pool and other standard tools like we're seeing with flappycoin. version.h:static const int GETHEADERS_VERSION = 70002; version.h:static const int MIN_PEER_PROTO_VERSION = GETHEADERS_VERSION;
strattum connection refused on the pool all ports. Isn't stratum for pooling only? Seems like we need to get our solo wallets (Mac, Linux, and required source code) working first after this large change. edit: The protocol version now says 1111337. Remember that protocol versions increase sequentially, so if we go to that one now every future protocol version has to have at least 7 digits. We still have 3 digits to go before hitting maxint, but this seems a bit reckless. As for running the wallet, it says two hours behind and I'm stuck at block 779980, I have only one proto version 1111337 peer at: getpeerinfo [ { "addr" : "94.61.193.156:11556", ... "version" : 1111337, .. } ] and http://blockcrawler.rf.gd/index.php?i=1 says it's also still downloading the blockchain. Hope this doesn't sound crazy, but given the situation (what Blurb said regarding disconnects, having more protocol 91137 nodes at the moment, the fact that somehow we got convinced to download a wallet without source code, and general bugs which would be easier to troubleshoot on a single chain), could I get the room to consider not forking? If the only intent of this is to resolve the transaction fees we already know we can do that without a fork. Checkpointing and building a cleaner Windows wallet can also be done regardless. changing to such a high pro vr is necessary not reckless you need to take into account all the forked flappy chains from the past still on the same network.. thats one of the 4 ways the coin broke . there are protvrs on nodes still running all the way up to 900000 that wont hand out blocks So when we catch to those chains here around and about 820000 we wont start to download there blocks thats why there is a high reward at that point in case we have to fight for our chain .. We did over a year or research to see what exactly happened and how was the best way to preserve everyones coins including test mining threw the forks . then we rolled back to the checkpoints https://github.com/Flapmin/FlappySp2Sourcesource zipped config is in there to my pool will be up and down for updates the p2p book will help alot [moderator's note: consecutive posts merged]
|
|
|
|