Mac Wallet v1.9.2
Download
Topic: FLY COIN ANN.Swapping to "Las Vegas"coin,+Masternodes,Darksend,Stealth, instantX - page 103. (Read 186194 times)
March 10, 2016, 10:07:49 AM
March 09, 2016, 10:11:08 PM
Is there anything in the pipeline that would make me want to buy this coin? I have flicked through the pages and it seemed like a great coin, then i looked at trading history on yobit and cryptopia and there is no volume at all. Please, i am not trying to fud the coin, i just want info so i can decide if it is worth investing a little btc into it. Many thanks..
Thanks for your question - no offense taken. It is a good question.
Current volume is low due to a current wallet problem which makes now a good time to buy. Like you see in many coins, when a wallet problem gets fixed it moves up. Another reason for the low volume is Fly has been holding off on marketing efforts until the wallet synch problem is solved. This solution should be very quick as the problem is identified and, the code is being corrected Previous wallet versions have been incompatible with Yobit's system (for a long time) - it was announced to move coins from there to avoid them becoming stuck on the exchange. Cryptopia is the official exchange. Should you decide to buy, that is where you should go.
March 09, 2016, 10:07:23 PM
Is there anything in the pipeline that would make me want to buy this coin? I have flicked through the pages and it seemed like a great coin, then i looked at trading history on yobit and cryptopia and there is no volume at all. Please, i am not trying to fud the coin, i just want info so i can decide if it is worth investing a little btc into it. Many thanks..
Well, to be very honest with you, this is crypto, so nobody really knows if it will be a good investment or not; only time can tell.
The only thing you can be sure is that vegasguy is very persistent, and that needs to mean something. Other than that, it is like any other cryptocoin: risky.
March 09, 2016, 09:18:56 PM
Is there anything in the pipeline that would make me want to buy this coin? I have flicked through the pages and it seemed like a great coin, then i looked at trading history on yobit and cryptopia and there is no volume at all. Please, i am not trying to fud the coin, i just want info so i can decide if it is worth investing a little btc into it. Many thanks..
March 09, 2016, 09:03:30 PM
There is a sync issue with the wallets because of the way someone coded the comparison to a fork to check for the key structure. the wrong variable was used and it causes it to work sometimes but after a certain block in the 55,000's it stops working because the variable changes. I am working to fix it. it is just hard to test against the correct chain now because a lot of people got reverted back blocks. 1.9.2 will have this fixed though. it looks like the bug was in the wallet since the 1.8 versions.
And nobody knew this before because... ?
its like a time bomb, before getting to a height it didnt go off. once we passed a certain block height it started to cause problems. much like you dont notice a time bomb before the clock its zero.
@woody, i was talking about sync issues not crash on startup
March 09, 2016, 08:54:51 PM
There is a sync issue with the wallets because of the way someone coded the comparison to a fork to check for the key structure. the wrong variable was used and it causes it to work sometimes but after a certain block in the 55,000's it stops working because the variable changes. I am working to fix it. it is just hard to test against the correct chain now because a lot of people got reverted back blocks. 1.9.2 will have this fixed though. it looks like the bug was in the wallet since the 1.8 versions.
And nobody knew this before because... ?
in the old FLY thread - page 48. Unfortunately, it only happened to some users and seemed random.
those that have had this problem (myself included) were only able to fix it by doing a dump private key and
synching a clean, new wallet and then, importing private key.
The previous developer wrote "It is possible that there is a difference in Berkeley database versions
(the db system wallet.dat uses) between the 32 bit and 64 bit builds."
This aggravating problem has been highest on the priority list since then with 3 developers working to
find the problem in the millions lines of of code. Griffith (one of the developers working on the code)
feels the problem has been identified and the solution is being implemented along with the synching
problem.
I feel your pain and frustration but, am the most confident I have been that a lasting solution is near.
March 09, 2016, 06:20:13 PM
There is a sync issue with the wallets because of the way someone coded the comparison to a fork to check for the key structure. the wrong variable was used and it causes it to work sometimes but after a certain block in the 55,000's it stops working because the variable changes. I am working to fix it. it is just hard to test against the correct chain now because a lot of people got reverted back blocks. 1.9.2 will have this fixed though. it looks like the bug was in the wallet since the 1.8 versions.
And nobody knew this before because... ?
March 09, 2016, 06:11:32 PM
There is a sync issue with the wallets because of the way someone coded the comparison to a fork to check for the key structure. the wrong variable was used and it causes it to work sometimes but after a certain block in the 55,000's it stops working because the variable changes. I am working to fix it. it is just hard to test against the correct chain now because a lot of people got reverted back blocks. 1.9.2 will have this fixed though. it looks like the bug was in the wallet since the 1.8 versions.
March 09, 2016, 04:51:02 PM
I can confirm the same for myself.
The new (v1.9.1) wallet ALWAYS stucks on the following blocks while syncing from scratch:
21596, 23096, 55756, 57708, 58227.
Same crash bug, and same block numbers.
Debug file complaining the addnode IPs added are the wrong Protocol version.
The new (v1.9.1) wallet ALWAYS stucks on the following blocks while syncing from scratch:
21596, 23096, 55756, 57708, 58227.
Same crash bug, and same block numbers.
Debug file complaining the addnode IPs added are the wrong Protocol version.
March 09, 2016, 04:38:16 PM
We know there are sync issues and working on them now. There was an old bug where the wallet would attempt to start and then disappear. Have any of you experienced this in 1.91 or is it just sync issues. We will fix the sync issues, but we need to know if that "crash bug on startup" still exists or not.
Vegas
Vegas
no such issue here, (with v1.9.1). wallet started right up, had some connections, refused to sync.
i concur that 'fly has always been a PITA to upgrade', but i bear in mind that we're all beta testers here, whether we like it or not, anyway
March 09, 2016, 04:21:05 PM
"crash bug on startup" still exists or not
It exists. Here are steps to reproduce such bug:
1. Delete FlyCoin directory in AppData.
2. Install v1.7.8 (or earlier) wallet, launch and sync (only first blocks are ok too), close the wallet.
3. Install a wallet of the newer version, try to launch it.
4. Crash after the loading screen.
In my opinion, wallet.dat's versions are incompatible. It was always pain to upgrade FLY wallet.
The new (v1.9.1) wallet ALWAYS stucks on the following blocks while syncing from scratch:
21596, 23096, 55756, 57708, 58227.
March 09, 2016, 02:25:04 PM
We know there are sync issues and working on them now. There was an old bug where the wallet would attempt to start and then disappear. Have any of you experienced this in 1.91 or is it just sync issues. We will fix the sync issues, but we need to know if that "crash bug on startup" still exists or not.
Vegas
Vegas
Yes Vegas. It does.
March 09, 2016, 02:22:46 PM
We know there are sync issues and working on them now. There was an old bug where the wallet would attempt to start and then disappear. Have any of you experienced this in 1.91 or is it just sync issues. We will fix the sync issues, but we need to know if that "crash bug on startup" still exists or not.
Vegas
Vegas
March 09, 2016, 01:43:11 PM
Guys we are fully aware of the syncing issues. I just finished speaking with Griffith and he has class for the next few hours, then he will return and fix it. He already knows what the problem is. So hang in there.
Vegas
Vegas
March 09, 2016, 12:58:46 PM
Not fixed yet. Still cannot sync.
Same here, stuck at block 55756
March 09, 2016, 12:38:55 PM
Are your seed nodes running the right version of the wallet???
Code:
connected 167.114.224.79:41568
send version message: version 60080, blocks=55756, us=68.235.184.68:41568, them=167.114.224.79:41568, peer=167.114.224.79:41568
partner 167.114.224.79:41568 using obsolete version 60070; disconnecting
ProcessMessage(version, 108 bytes) FAILED
getblocks 51855 to 00000000000000000000 limit 1500
getblocks stopping at limit 53354 a4b6a9013bc3f8579a6c
disconnecting node 167.114.224.79:41568
trying connection 72.74.62.254:41568 lastseen=16.1hrs
trying connection 167.114.224.82:41568 lastseen=377095.8hrs
connected 167.114.224.82:41568
send version message: version 60080, blocks=55756, us=68.235.184.68:41568, them=167.114.224.82:41568, peer=167.114.224.82:41568
partner 167.114.224.82:41568 using obsolete version 60070; disconnecting
ProcessMessage(version, 108 bytes) FAILED
disconnecting node 167.114.224.82:41568
trying connection 167.114.224.79:41568 lastseen=377095.8hrs
connected 167.114.224.79:41568
send version message: version 60080, blocks=55756, us=68.235.184.68:41568, them=167.114.224.79:41568, peer=167.114.224.79:41568
partner 167.114.224.79:41568 using obsolete version 60070; disconnecting
ProcessMessage(version, 108 bytes) FAILED
getblocks 51855 to 00000000000000000000 limit 1500
getblocks stopping at limit 53354 a4b6a9013bc3f8579a6c
disconnecting node 167.114.224.79:41568
trying connection 167.114.224.82:41568 lastseen=377095.8hrs
connected 167.114.224.82:41568
send version message: version 60080, blocks=55756, us=68.235.184.68:41568, them=167.114.224.82:41568, peer=167.114.224.82:41568
partner 167.114.224.82:41568 using obsolete version 60070; disconnecting
ProcessMessage(version, 108 bytes) FAILED
getblocks 51855 to 00000000000000000000 limit 1500
getblocks stopping at limit 53354 a4b6a9013bc3f8579a6c
disconnecting node 167.114.224.82:41568
March 09, 2016, 08:16:06 AM
Not fixed yet. Still cannot sync.
I report the same problem. Even with deleted wallet.dat and FlyCoin folder in AppData. I resync, import my privkey and then moving back to the block 57708.
Update: now bootstrap do not help. Now on block 55756.
March 09, 2016, 03:02:44 AM
Not fixed yet. Still cannot sync.
March 08, 2016, 10:07:09 PM
Is there anything preventing the exchanges from running on "normal" addresses and exempting their users from Super Fly fees?
March 08, 2016, 06:18:57 PM
Important
If you are on the right block height 59000+ then do not clear your data folder. Just replace the exe and enjoy.
If you are on the right block height 59000+ then do not clear your data folder. Just replace the exe and enjoy.
Jump to: