Topic: FLY COIN ANN.Swapping to "Las Vegas"coin,+Masternodes,Darksend,Stealth, instantX - page 71. (Read 186171 times)

Thank you  Presstab

Hi FLY-community,

I am happy, to be a huge part here, and its my duty, to bring in a lot of stuff here too.

Here is a short hint, whats happened in the background:



http://www.federatedblockchains.eu.org/


Yes. You see it right. Thanks Vegas and his awesome community, TEAM FLY is also a proud member of the "Federated Blockchain"-Mission.

This project is very young and I will fill in from time to time, great news and some developments there. So,

the mission began already!

Greetz
Steve

@Cryptonit, I always enjoy your posts. They are always contain very wise and useful information. I would agree that dropping the base to 20% would encourage more locking. My biggest concern has always been inflation as it has been proven over and over again in Crypto that it is the Achilles heal of coins. I still need to make our table , so it can be discussed and tweaked on the thread before our code goes final.

@GoldTiger: Your post tells me that you truly care about this project. Thank you, you have been an amazing supporter of this project. You also see that over time fly will be the greatest crypto ever. No one is more determined to get that title and keep it than team fly. I wanted to clear up some confusion now that things have settled down. I have said in my past few posts that our changes will be one update then perhaps in a month when we know all is well another update. I think this is not too fast, but I could be wrong. I think you might be referring to our past. Let me be clear on what happened. When I started trying to integrate antidump, upon each release we thought we had it working correct, and it was always one problem or another. So after a problem was discovered, I HAD to force a quick release to get that fixed. Thats all it was. I agree with you, that constant non stop updates cause a train wreck, and its not what I want. It made everything very unstable. So we are now in a place were I want to calm the waters, and release updates at a nice pace. I think 4-6 weeks apart seems reasonable. Anyway, I didnt want you to think that I was pumping out updates because I thought it was just a good idea. I had to learn a hard lesson, and I have. We will now be using code from sources that are tested and proven, and release them many weeks apart.

Vegas

to avoid hyperinflation i would consider reduce the base stakerate and the hold  bonus

something like base 20%
and each month hold add a factor of 0.1 (1+ the factor)

so lock 12 months give
20*2.2=44%

1 month give
20*1.1 =22%

u can combine this systemn with a constant decreasing base stakerate and still the boost for hold fit to it

example if u say base stakerate decrease each year by 5% down to minimum stakerate 5%

then in 4th year base stakerate would be 5%

and each month hold add a factor of 0.1 (1+ the factor)

so lock 12 months give
5*2.2=11%

1 month give
5*1.1 =5.4%

a ROI of 11% is outside of crypto great
and even 5.5% u wont get as a normal investor only banks can ask for so much interest on their loans

I really don't know why to hurry the releases of the new wallets. This coin is a 'long term' coin, so it should be treated like that. In other words, the next release of the coin should be in like next month, after weeks of testing, because it's dumb to release now and then, after one week, release the 'fix' for the rushed released wallet.

Honestly, I thought you guys had learned the lesson of NOT rushing the wallets, just to figure latter that the Exchange needs to fix the bugs on it.

Vegas, I love your "locked coins"-model! I am in talks with a good guy around me, and will present him to you as soon as possible...more yesterday than tomorrow. I love it, that we dont wanna create an "early adopter bonus". This is fair for all, because a fixed rewardsystem for each timeframe would be awesome and urgent needed in cryptoworld!

So I am sure, he can tell you some thoughts about it very soon!

Greetz
Steve

So to update everyone on our roadmap, the next update which will be released before the end of the week is the addition of POSP. We will allow about a month to make sure everything is running as it should. During this time we will be coding for the addition of HODL. Our version of the HODL code will differ in a few ways. First , the current HODL code benefits those the most that "lock" as early as possible (closest to Genesis). Our system will not function this way. It will not matter when you lock. There will be options to lock from 1-12 months. 12 months having the most rewards and 1 month having the least. It will be on a much smaller scale to avoid inflation. Probably 120% a year being the max. So these are some rough guidelines we are creating while we are studying HODL. There will still be the regular POS reward of 35% for those that participate only in POSP. HODL will be completely optional.

Vegas

Mac Wallet v2.1

Download

This version has an experimental patch, that fixes crushes caused by broken wallet.dat
Before it goes upstream, it needs to be tested



Try this one


If you have mac, try this build with your broken wallet.dat


Current fix happend thanks to EBK1000 (who gave me his file).

Do you still have broken wallet.dat?

Thanks, Presstab!

Looks to be on the correct block now. In sync with the other 2 BE's

Peace, Dennis

Yup, Im sure Cryptonit will confirm that when he moved his coins from an address created in 2015, he never had a problem again.

Vegas

How do I do that? I need to have 2 separate wallets?

fly.presstab.pw explorer is updated and I believe on the correct chain.

make sure the new address is in another new wallet.dat

else u still have the troublemaker address in ur wallet.dat .....

In the past, when I have trouble upgrading wallet and the usual does not work.  I backup everything, and move it out of APPDATA so that the new EXE creates a new wallet and grabs the blockchain (or imports the bootstrap).  Once all is in sync, I then switch to my old wallet.  After a few crash starts, it works.

But, like you said, hopefully the last time it happens... ;-)

Thank you Ivan. Many people kept on saying that the "startup bug" was in the code. In an attempt to put this problem away for good, I spent a few days non stop discovering what was really causing it. It turned out that if you have transactions from 2015 then something early in the code wrote "dirty transactions" into your wallet.dat. ALL early adopters from fly suffered from this, and thats why it took so long to solve, is because everyone was looking at the wallet code. The ONLY permanent cure that has worked 100% is to move your coins to a new address, thus eliminating any of your transactions from 2015. No one that has moved their coins to a new addy has had a problem since

Vegas

Imported priv keys and everything works fine. Hope this is the last time.

Will send coins to a new address.

Thx Vegas.

The answer to this is you MUST dump and reimport the priv key to V2.1 . Then you MUST trasfer your coins to a new addy. If you still cannot get this working PM me, and as I did for Dennis Levy, Ill teamviewer in and get you fixed up if you will allow that. Also check that V2.1 launches without a wallet.dat file. Just renamed your wallet.dat to wallet.tmp
Vegas

yes, that is going to be your best bet. The good news is this will be the last time as V2.1 is flawless. Also if your still using your original address from 6 months ago or more. THIS is the reason for the crashes. You MUST send the coins to a new addy to stop this from ever happening again. The only people still having crashes on startup have very old Fly addresses that have transactions near the beginning of the chain. By transferring your coins, your transactions begin near the end of our current chain.

Vegas

Nope, now it crashes with every single version of the wallet I have. 2.0, 2.01.

Only 1 wallet.dat file available. I do have a really old backup in cold storage. Any other option?

Edit. 2.1 starts with fresh wallet.dat file. Crashes with the one from. 2.01

Edit. It seems 1.4 version starts with the old 2.01 wallet.dat. Dump keys again?