OLD FLY THREAD

[Griffith]

have no fear, i am here

[Woody20285]

have no fear, i am here

I feel better already!

[Argon18]

Cryptopia's Flycoin Wallets are back in maintenance mode.
Looks like Another Bug in flycoin code causing problems.

AG18

By the way , Called it on Nov 22nd

That's not a bug , but Pure Genius.
By the Wallets not working no one can dump.
Genius, Pure Genius.    

AG18

Time to Suit up Vegas & Keesdewit,  Ya got a coin to Fixx!!!



@Griffith,
CryptoJohn could use some help in the other forum, if ya still working there.

[cryptonit]

have no fear, i am here

nice nice

i did see ur work longterm and dedicated for ECC
its good u support FLY development

what a amanzing sign of strenght and activity when a coin have so much work that one dev isnt enought

and in fact its a bit unfair we have two devs working for us while so many coins have no active dev at all

good who choose to invest in a active coin like FLY

and even better that after this difficult weeks the price is very attractive to join in

at least up to the 100 FLY barrier so u can qualify urself for superFLY payouts

(in case u wana go into FLY deeper i suggest get in touch with vegas he still seek and redistribute coins to core investors following the TEAM FLY stabilisation pact)

[xProphet]

so now my wallet is stuck at block 35771

I had the same issue, but solved it in 5 minutes.
Just update to the v1.73 instead of 1.72.
If it will stuck again, just resync.

[xProphet]

And here is my tweet on this week:
https://twitter.com/OneMoreBtcNoob/status/671993590550298624

[vegasguy]

Yes, there are still some little bugs to squash . We now have 2 very highly skilled devs on board. The very well known Griffith (From Trusted Cryptos) is now on our team.

Vegas

[Crypto_Towelie]

Exchange again not working. Another bugged code. Another code without good testing. You don't test these kind of things in 2-3 days time. You spend weeks on testnet.

ETA for fix please?? so I can finally dump my little bag of this clowncoin

[vegasguy]

Ok. First I apologize. Ive hired another skilled dev, Griffith from Supercoin, and ECcoin as our code is incredibly complex. Please hang in there. I PROMISE you, it will all be soooo worth it. We have had our troubles. I knew this would be an incredibly difficult project, but I didnt want just another silly clone coin that looked like all the rest. please hang in there, we are working non stop and are very close on this.

https://bitcointalk.org/index.php?topic=1006830.0

Here is the test logs: https://github.com/CoinProjects/Fly-coin/releases/download/v1.7.3/Test.results.release.1.7.3.pdf

Vegas

[Crypto_Towelie]

Ok. First I apologize. Ive hired another skilled dev, Griffith from Supercoin, and ECcoin as our code is incredibly complex. Please hang in there. I PROMISE you, it will all be soooo worth it. We have had our troubles. I knew this would be an incredibly difficult project, but I didnt want just another silly clone coin that looked like all the rest. please hang in there, we are working non stop and are very close on this.

https://bitcointalk.org/index.php?topic=1006830.0

Here is the test logs: https://github.com/CoinProjects/Fly-coin/releases/download/v1.7.3/Test.results.release.1.7.3.pdf

Vegas

Is that meant to be a serious test vegasguy? This pdf only shows us a few test transactions on mainnet. They are not even confirmed in the screenshots.


Please, I would like to hear the explanation about this:
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.h#L69 - No testnet guys?


2 important forks happend after presstab left. There is nothing in version.h to block older versions from connecting. This is highly recommended after such dramatic changes.
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L38
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L48


I can't believe none of your developers noticed this error. Is this is a joke?
https://github.com/CoinProjects/Fly-coin/blob/master/src/qt/guiutil.cpp#L130-L132


You either remove this, or turn it back to false after you mined a new genesis block. Leave it in for now until you mined a genesis for testnet (details guys, cmon!)
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.cpp#L2765-L2784

And what is the reason behind this? Where is the nonce?
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.cpp#L2760
http://fly.dnsalias.com/block/0000045d787a26f5d4850d7d1125f8be9a677bab5d1605ad86b191901e574e57

[vegasguy]

Ok. First I apologize. Ive hired another skilled dev, Griffith from Supercoin, and ECcoin as our code is incredibly complex. Please hang in there. I PROMISE you, it will all be soooo worth it. We have had our troubles. I knew this would be an incredibly difficult project, but I didnt want just another silly clone coin that looked like all the rest. please hang in there, we are working non stop and are very close on this.

https://bitcointalk.org/index.php?topic=1006830.0

Here is the test logs: https://github.com/CoinProjects/Fly-coin/releases/download/v1.7.3/Test.results.release.1.7.3.pdf

Vegas

Is that meant to be a serious test vegasguy? This pdf only shows us a few test transactions on mainnet. They are not even confirmed in the screenshots.


Please, I would like to hear the explanation about this:
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.h#L69 - No testnet guys?


2 important forks happend after presstab left. There is nothing in version.h to block older versions from connecting. This is highly recommended after such dramatic changes.
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L38
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L48


I can't believe none of your developers noticed this error. Is this is a joke?
https://github.com/CoinProjects/Fly-coin/blob/master/src/qt/guiutil.cpp#L130-L132


You either remove this, or turn it back to false after you mined a new genesis block. Leave it in for now until you mined a genesis for testnet (details guys, cmon!)
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.cpp#L2765-L2784

And what is the reason behind this? Where is the nonce?
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.cpp#L2760
http://fly.dnsalias.com/block/0000045d787a26f5d4850d7d1125f8be9a677bab5d1605ad86b191901e574e57

Yes PLEASE help. Im NOT being sarcastic when I say THANK YOU!!!  Ill even reward you if you can help clean up some bugs too. By all means help us, and PM me your FLY address.

Really, thank you.

Vegas

[vegasguy]

I dont mind if you critique our code. Finally!! Someone thats willing to help , other than telling us we have bugs, and complaining. We know that and are working on it, and I thank you. I get the feeling thats not your main account. You certainly seem to be highly skilled. Yes, we need all the help we can get. PM me your fly address please.

Vegas

[Crypto_Towelie]

Oh no, don't get me wrong. I'm not here to help. And never will be either. Thank a few "team fly" members for that who decided all my posts we're rubbish a few pages back. The only one with a normal response was you and the guy with the woody woodpecker avatar.


Sorry, but I just want to get out now. A few members in this community are blinded and really cocky when it gets to critics about the code. I don't want to be part of such ignorance.

[presstab]

Good critiques. Do have some questions about them though. (and don't worry I am not part of 'team fly')

Please, I would like to hear the explanation about this:
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.h#L69 - No testnet guys?

It is pretty normal for coins not to use a testnet. What is not normal is having 5 forks in one month and 'changing crypto' without a testnet. (edit - or without a proper testing fork or similar method)

2 important forks happend after presstab left. There is nothing in version.h to block older versions from connecting. This is highly recommended after such dramatic changes.
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L38
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L48

Totally agree with this one. If you aren't blocking old peers it will cause high resource consumption of the valid peers trying to fill continual requests from outdated peers.

I can't believe none of your developers noticed this error. Is this is a joke?
https://github.com/CoinProjects/Fly-coin/blob/master/src/qt/guiutil.cpp#L130-L132

This actually was noticed when I was still working on fly, i think banzaibtc pointed it out. My decision was that nobody uses URI for small altcoins, so don't fuss with it. Am I wrong? Is there a 3rd party block explorer or something that is using this?

You either remove this, or turn it back to false after you mined a new genesis block. Leave it in for now until you mined a genesis for testnet (details guys, cmon!)
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.cpp#L2765-L2784

Doesn't need to be removed, as you see a few lines above, this part of the code is only triggered if mapBlockIndex is empty. You could remove these things if you wanted to clean up the code. But who cares?

And what is the reason behind this? Where is the nonce?
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.cpp#L2760
http://fly.dnsalias.com/block/0000045d787a26f5d4850d7d1125f8be9a677bab5d1605ad86b191901e574e57

Looks like the nonce didn't make it into the commit for some reason. Although it seems to be no fowl since the chain syncs fine as is. The genesis block is checkpointed, it is all secure. This really only matters for someone that is curious about the code and sees no nonce, so maybe about 1 in every 10,000+ people.

Honestly, in my opinion at least, the things you pointed out are trivial things that don't really have anything to do with the functioning of the coin. The testnet and protocol bumps I do believe to be important, the rest is more about code organization rather than the functioning of the coin network.

Edit - I hope my tone doesn't sound hostile, I am just wondering if most of the fuss is about formatting rather than the security and functionality of the coin?

[midnight_miner]

Good critiques. Do have some questions about them though. (and don't worry I am not part of 'team fly')

Please, I would like to hear the explanation about this:
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.h#L69 - No testnet guys?

It is pretty normal for coins not to use a testnet. What is not normal is having 5 forks in one month and 'changing crypto' without a testnet.

I disagree, there a quality altcoins that use the testnet.  It's the fly-by-the-seat-of-your-pants testing that creates problems from not taking the time to set up testnets.  For myself that is a big minus in my books for not taking the time to set up the test net and using it for testing.

2 important forks happend after presstab left. There is nothing in version.h to block older versions from connecting. This is highly recommended after such dramatic changes.
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L38
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L48

Totally agree with this one. If you aren't blocking old peers it will cause high resource consumption of the valid peers trying to fill continual requests from outdated peers.

[/quote]

The easy fix for this is:

banscore=5 or 10

Would take care of the resource problem, would it not?

[keesdewit]

Good critiques. Do have some questions about them though. (and don't worry I am not part of 'team fly')

Please, I would like to hear the explanation about this:
https://github.com/CoinProjects/Fly-coin/blob/master/src/main.h#L69 - No testnet guys?

It is pretty normal for coins not to use a testnet. What is not normal is having 5 forks in one month and 'changing crypto' without a testnet.

I disagree, there a quality altcoins that use the testnet.  It's the fly-by-the-seat-of-your-pants testing that creates problems from not taking the time to set up testnets.  For myself that is a big minus in my books for not taking the time to set up the test net and using it for testing.

2 important forks happend after presstab left. There is nothing in version.h to block older versions from connecting. This is highly recommended after such dramatic changes.
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L38
https://github.com/CoinProjects/Fly-coin/blob/master/src/version.h#L48

Totally agree with this one. If you aren't blocking old peers it will cause high resource consumption of the valid peers trying to fill continual requests from outdated peers.

Thanks for you critiques. I would like to reply:

There are other ways to test a coin besides from the testnet. One could setup a closed environment based on the current block chain or just start the blockchain from zero. For blocking older versions with version.h my answer would be "it depends". My opinion is that you cannot say in general that it would cause high resource consumption. It depends on what you change. For the other things you say I share presstabs thoughts.

[hashmaster1]

I am glad to a holder of this unique coin thanks to Vegasguy  I have no intention on selling any coins I have .....my goal is to get 5000 coin I'm in it  for a long hall keep up great work dev's ...

[gregofdoom]

I am glad to a holder of this unique coin thanks to Vegasguy  I have no intention on selling any coins I have .....my goal is to get 5000 coin I'm in it  for a long hall keep up great work dev's ...

I also try to collect more FLY
As I said earlier, vegas + community + keesdewit = Great Bright Future !

[Woody20285]

I am glad to a holder of this unique coin thanks to Vegasguy  I have no intention on selling any coins I have .....my goal is to get 5000 coin I'm in it  for a long hall keep up great work dev's ...

I also try to collect more FLY
As I said earlier, vegas + community + keesdewit = Great Bright Future !

Thank you all for the criticisms, the suggestions and the support.
All of these will help us to get better.

[Woody20285]

Oh no, don't get me wrong. I'm not here to help. And never will be either. Thank a few "team fly" members for that who decided all my posts we're rubbish a few pages back. The only one with a normal response was you and the guy with the woody woodpecker avatar.

Sorry, but I just want to get out now. A few members in this community are blinded and really cocky when it gets to critics about the code. I don't want to be part of such ignorance.

My apologies for the negative responses you received. In written commmunication, it is easy to read the tone of comments wrong and react negatively. I appreciate your positive suggestions to the code.

For any interested, I had the pleasure to know Walter Lantz, the creator of Woody Woodpecker, who was a wonderful and truely funny person. My avatar is a photo of an original oil painting Walter Lantz painted which hangs in my office. Walter was not just a legendary cartoonist buta highly skilled artist.