[ANN][FLT] Fluttercoin Ƹ̵̡Ӝ̵̨̄Ʒ | Proof of Transaction 3.0 | Update v0.7.5.22

[groggin]

I just received 5,000 coins out of the blue 

They weren't mined, and I didn't send them... Anyone have an explanation for this mystery?

You are one of the 50 winners here. 

http://fluttercointalk.com/showthread.php?222-500-members-250-000-FLT-in-prizes&p=2308&viewfull=1#post2308

WooHoo! I'm a winner! Thanks, I signed up for that so long ago I nearly forgot 

  w00t! me too. thanks   

[1714006350]

1714006350

[1714006350]

1714006350

[1714006350]

1714006350

[12345mm]

Yes you should, That's what I always do when I'm stuck with a coin it works 95% of the time if its not a hardfork problem or a very specific one. Once you cleaned the roaming folder you only need to launch the QT(exe) again no need to delet/reinstall. You can let the wallet.dat in the folder too(in fact you must otherwise it will create a new wallet.dat with a new address).Don't forget to make a copy of it anyway ! I dont know if there is a bootstrap for ftl but flutter speed make the blockchain up to date fast enough.
Too bad I had no orders sub 60

thanks much for the assist - this method of deleting everything but the wallet.dat and then restarting worked for me (will remember this if I need to do similar on other coins) - had to synchronize from the very first block , and was interrupted with a brief power outage from lightning and had to do it a 2nd time from the start (doh!  *shakes fist at sky*) , but nonetheless , it did eventually work perfect and my old flutter balance is now available in my synchronized wallet , now staking nice rewards as well and having picked up a bunch of rewards from back in time yay!

[oddwh]

Hello,

I bought some FLT this morning, tried to withdraw them, it was impossible. So I contacted cryptsy, and now the wallet is under maintenance. They answered very quickly.

I hope it will be fixed soon !

[johnbrainless]

Proof of Transaction 3.0 | Update v0.7.5.17 looks awesome

[ofeefee]

yeah, there is a bug in the latest code that is causing the client to crash periodically.  I don't have my build environment up at the moment, so if someone who can debug it and look let me know, or submit the pull request to github with the fix.  Soomster, yes some of the original members I expect exited.  I am just holding and enjoying things lately, this coin makes that easy.  We have settled to around 20% interest with the latest diff. 

--o

[blockexperts]

I see the block explorer hosting period expired.

Please contact our support to renew the hosting period.
You can contact us by sending an email to support@blockexperts.com

[djhomeschool]

My QT wallet is crashing multiple times per week on Win8x64 - any word on when an update is coming to fix this?

[fairglu]

yeah, there is a bug in the latest code that is causing the client to crash periodically. 

Can't debug it, but I have had to restart the explorer wallet a few times in the last weeks, there was nothing special in the debug.log, but if something comes up next time I'll let you know!

[ofeefee]

yeah, there is a bug in the latest code that is causing the client to crash periodically. 

Can't debug it, but I have had to restart the explorer wallet a few times in the last weeks, there was nothing special in the debug.log, but if something comes up next time I'll let you know!

We have identified an issue with a piece of code that checks if an address is valid or not far as we can tell.  I don't have tools necessary to find it at the moment, but we are looking into it, my dev environment is back online so hoping we can isolate it, other than that one issue, things are running well with the new PoTv3 changes!

--o

[ofeefee]

yeah, there is a bug in the latest code that is causing the client to crash periodically. 

Can't debug it, but I have had to restart the explorer wallet a few times in the last weeks, there was nothing special in the debug.log, but if something comes up next time I'll let you know!

We have identified an issue with a piece of code that checks if an address is valid or not far as we can tell.  I don't have tools necessary to find it at the moment, but we are looking into it, my dev environment is back online so hoping we can isolate it, other than that one issue, things are running well with the new PoTv3 changes!

--o

Looking through the code...wow I did some major changes.  Anyway, my dev system is building out my linux dependencies and then will compile with debugs and gdb and bt it to find the line of code...hopefully later tomorrow maybe...or not, who knows.

[slax0r]

yeah, there is a bug in the latest code that is causing the client to crash periodically.

Can't debug it, but I have had to restart the explorer wallet a few times in the last weeks, there was nothing special in the debug.log, but if something comes up next time I'll let you know!

We have identified an issue with a piece of code that checks if an address is valid or not far as we can tell.  I don't have tools necessary to find it at the moment, but we are looking into it, my dev environment is back online so hoping we can isolate it, other than that one issue, things are running well with the new PoTv3 changes!

--o

Looking through the code...wow I did some major changes.  Anyway, my dev system is building out my linux dependencies and then will compile with debugs and gdb and bt it to find the line of code...hopefully later tomorrow maybe...or not, who knows.

Just built out a brand new linux box.  Give me some pointers on what to look for and Im all over it. Incidentally, I can verify that it is occurring on Linux and the Mac.

slax0r

[ofeefee]

Only thing my debugger sees is an issue in pthread crashing the stack, and I cannot go back any further in gdb to see what function called this...linux library.  I expect something is trying to spawn a new thread.  I did make an update to the thread handling for P2P, but that conflicts with what Kz is seeing.

Just let it sync, around 362k, and then off an on after this it will crash, leaving you a trail of breadcrumbs.  If we need to add some things to the src to make debugging easier in the future, I can clone a dev branch to add these.

Regards,
--o

[anotherlateminer]

FLT Cryptsy wallet is still in maintenance mode. Any information about this?

[anotherlateminer]

Thanks. I've been waiting for more than a week to withdraw my coins.

[ofeefee]

i have asked cryptsy to fallback their version to .16 which doesn't have the fault issue.  I am actively trying to find a solution as this aggravates me as well since I do trade my stake rewards and well that doesn't work well at the moment.

FYI, web wallet/android app is coming back online, syncing it up now.

best regards,
--o

edit...looking further, seems it may be back farther than .16, because i am syncing web wallet up on .15 and it's faulting too.

i have narrowed it down to the .14 release where this starts having issues syncing and crashing on certain blocks for whatever reason.  .12 syncs up without any issues (no crash).  So i have narrowed it down further that it exists at least as of 11/23/2014 commit, now trying a commit prior to when we put in secure messaging (testing from commit 40ce1d2) see what we get...

--o

[ofeefee]

i have asked cryptsy to fallback their version to .16 which doesn't have the fault issue.  I am actively trying to find a solution as this aggravates me as well since I do trade my stake rewards and well that doesn't work well at the moment.

FYI, web wallet/android app is coming back online, syncing it up now.

best regards,
--o

edit...looking further, seems it may be back farther than .16, because i am syncing web wallet up on .15 and it's faulting too.

i have narrowed it down to the .14 release where this starts having issues syncing and crashing on certain blocks for whatever reason.  .12 syncs up without any issues (no crash).  So i have narrowed it down further that it exists at least as of 11/23/2014 commit, now trying a commit prior to when we put in secure messaging (testing from commit 40ce1d2) see what we get...

--o

Found the module having the issue...secure messaging.  If you wish to create a shortcut and start the client with -nosmsg or enter smsgdisable in the console it will prevent the crashes from occurring.

Looking through the code now, but that will alleviate the issue temporarily.  I have emailed cryptsy the solution, will send over to Poloniex shortly.

--o

[mmfiore]

I found that it will crash more readily if you attempt unlock the wallet to start staking before the wallet is synced up. Wait till the wallet syncs before staking.

[ofeefee]

cryptsy is back up if anyone noticed, had them start daemon with the -nosmsg.  I have found the function or narrowed it down to the functions related.  Have not had time to see why those functions are causing the issue yet...

--o

[ofeefee]

cryptsy is back up if anyone noticed, had them start daemon with the -nosmsg.  I have found the function or narrowed it down to the functions related.  Have not had time to see why those functions are causing the issue yet...

--o

if you use a fluttercoin.conf file, adding nosmsg=1 to it will disable the messaging component until we get it fixed. 

--o

[ofeefee]

New test client (still says .17), BACKUP your wallets first...

I have it running on my main wallet.  Tested all the main things, syncs, sending, receiving, staking, fluttershare, etc.  I have not tested mining, but that should be unaffected, but someone test if they can.

github for this version...
https://github.com/ofeefee/fluttercoin/tree/dev

64bit windows
https://dl.dropboxusercontent.com/u/107300/fluttercoin-64-windows-v0.7.5.17.zip

Regards,
--o