|
ALL: if you are having trouble connecting and downloading the blockchain, ensure your not using peerblock or some other address blocking list.
If you are, make sure you at least allow permanently the node IP's listed in the conf, and any node if you dig or nslookup dnsseed.fluttercoin.us
|
|
|
|
where is the .conf file? I don't see it in the %appdata% folder anywhere
If you don't see it in your %appdata% directory, then you don't need to save it. It's a file that you can use to configure your wallet in the case you encrypted your wallet. It's used to get around the limitations of Proof of Stake minting with an encrypted wallet. For more details, you can watch this video showing how to create a .conf file with PeerCoin (but it should be similar for all coins). https://www.youtube.com/watch?v=WnLvE_Vnojc&list=PLBt4zAxcWonnA8-InWGUEw-UZofHdUIeT&index=14Yeah on windows you don't need to have it, but its best to use it to set things like disable IRC, enable DNS seeding etc |
|
|
|
I am a big fan of litecoin. I also had a lot of potcoin but got rid of it for flutter. There really aren't that many alts that I support. I think vert has potential too.
This is the new POTcoin LOL |
|
|
|
i just realized bter has 47 million fluttercoins, yet only about 1 million are on orders to sell. so that basically means a lot of people are using bter as their flutter wallet. unless bter themselves are just buying up all the coins. which is possible, they were the first exchange to add flutter, seemingly out of nowhere.
I have like 50k in there I bought or sent for testing... A lot of people seemed to buy it |
|
|
|
Can the dev please contact me?
I've updated to the latest source but i'm still stuck at 15553.
Thanks
Richie@bittrex
This is for anyone "stuck" because of a bad node somewhere (yet to figure out who it is) Delete all files in %appdata% except for your conf and wallet.dat Download the newest binary https://github.com/thekidcoin/fluttercoin/releases/tag/v0.4.5.3-fltMake your conf file look like this: rpcuser=username rpcpassword=password rpcallowip=127.0.0.1 connect=54.203.244.170 connect=54.203.244.27 connect=54.199.237.235 noirc=1 dnsseed=0 Its not possible to download the wrong fork using this method. All those nodes are operating on the correct blockchain. Then, shutdown the wallet, and change the conf back to look like: rpcuser=username rpcpassword=password rpcallowip=127.0.0.1 addnode=54.203.244.170 addnode=54.203.244.27 addnode=54.199.237.235 noirc=1 listen=1 dnsseed=1 server=1 I can confirm this indeed works. I backed up my wallet.dat and deleted all fluttercoin files. Downloaded the new wallet and then ran the wallet and it did get stuck at block 15553. I then deleted everything again and tried exactly what thekidcoin just described for the .conf and now my wallet is up to date and works fine. CONFIRMED! This works perfectly. Thanks! This worked for me as well, just a warning, those IP addresses were blocked by Peerblock for me, which took a while to figure out why it wouldn't work. You might need to unblock them as they are Amazon, Inc. and my P2P list was filtering them. They are my addresses... I despise peerblock for reasons like this. How would one go about unblocking IP's??? |
|
|
|
Wallet is not synching past 15553! ...maybe this will get your attention. Tried different approaches, one of which was using only the block explorer links as nodes. In this last attempt i got a beautiful " WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers." message instead of the normal green "Synchronizing with network..." bar. ...and noooobody gives a flying fuck. and PM Any plans on fixing the fucking 15553 fork? Or are you too busy not giving a fuck?
What do you think? I think you don't give a fuck. There are not enough people experiencing this issue to make you want to fix it, although I could see at least 5 wile searching for a solution in this thread earlier. But hey, not enough to endanger the health of the chain. Fuck the minority! What you are most interested in is profiting from your little creation before it dies. Who gives a fuck about the people who mine it? Not you, for sure. By the way, for your next crappy coin you might want to introduce a new concept... Proof-of-not-giving-a-fuck. I bet that will work too... To respond to the users who eventually answered my my cry for help, thank you all for trying. At the point when I wrote my first message, I had already tried all possible solutions mentioned by you, as well as some I picked up from my own experience. Using only the block explorer IPs as nodes with "banscore=1" should supposedly force the client to connect only to those nodes. And since the issue repeated itself under those circumstances, I assume that there is a problem at bock 15553. If you want to test it yourselves, backup your wallet.dat, delete the coin subfolder from the appdata/peers location, and try to reconstruct the blockchain. I bet you'll find yourselves in the same situation. I indeed gave up this piece of shit coin, and will never change my mind about it. The dev obviously is more interested in making the near future as shinny as possible, to keep you all blinded with promises of greatness and make the price of the coin go up until a certain level when he will dump all his coins and turn his back on the coin and all of you. If you want to look for a coin that really has a future, go ask for help on it's forum, and see how fast someone from the coin's staff (be it the owner, a dev, or a simple forum moderator) responds to your question with at least a "We are looking into the matter and will come back with an answer in due time.". Sorry pal. I've tested it many times in the last 2 days - and if there is an issue, it will be dealt with. Just to amuse myself with your rant, I simultaneously deleted all files in %appdata%/fluttercoin on a windows box, and ~/.fluttercoin on a linux box. Then I started the wallet and daemon up respectively, and to my surprise guess what? Windows BEAT Linux in syncing all blocks from 0 - 17071 15553 as i said before was where an offending pool with a lot of hashrate forked - nodes on the wrong fork get stuck by checkpoints, and they all need to re-download the blockchain. Eventually they will all be banned, and also eventually all versions using the current protocol will be dropped as bad. |
|
|
|
ALL: latest binaries uploaded to the release page: https://github.com/thekidcoin/fluttercoin/releases/tag/v0.4.5.3-fltWill be throwing a checkpoint in there and issuing new binaries in a few days, not mandatory, but will help with some of the issues maybe with the forked nodes - also as of 4/1/2014 00:00:00 GMT all version 0.4.5.2 clients will cease communication with the current blockchain (could be a little before or after the fork) |
|
|
|
We also were just added to Bittrex yesterday! I recommend everyone give the exchange a try as I have had a very positive experience with them so far. I've also heard they are planning to geolocate servers in various locations around the world such as China and India to improve user experience. Quite an interesting and innovative move in my opinion.
wow thats great news! |
|
|
|
Can the dev please contact me?
I've updated to the latest source but i'm still stuck at 15553.
Thanks
Richie@bittrex
PM sent... one of the pools forked it seems and some nodes went with it |
|
|
|
Can the dev please contact me?
I've updated to the latest source but i'm still stuck at 15553.
Thanks
Richie@bittrex
This is for anyone "stuck" because of a bad node somewhere (yet to figure out who it is) Delete all files in %appdata% except for your conf and wallet.dat Download the newest binary https://github.com/thekidcoin/fluttercoin/releases/tag/v0.4.5.3-fltMake your conf file look like this: rpcuser=username rpcpassword=password rpcallowip=127.0.0.1 connect=54.203.244.170 connect=54.203.244.27 connect=54.199.237.235 noirc=1 dnsseed=0 Its not possible to download the wrong fork using this method. All those nodes are operating on the correct blockchain. Then, shutdown the wallet, and change the conf back to look like: rpcuser=username rpcpassword=password rpcallowip=127.0.0.1 addnode=54.203.244.170 addnode=54.203.244.27 addnode=54.199.237.235 noirc=1 listen=1 dnsseed=1 server=1 |
|
|
|
Don't forget to update the stratum-mining code  Yeah, done so, didn't feel the need to mention that. Just checking LOL thanks! |
|
|
|
Don't forget to update the stratum-mining code |
|
|
|
so the first link is the new wallet, and we all need to download and run it, and the second link is only for pools to update? or do i have that incorrect? Binaries later today... Stratum just for pools |
|
|
|
Will contact every pool and exchange, but here is info on the latest MANDATORY update:We are forking at block 22000 (approximately 7 days) - this update below is mandatory (you man take the HEAD commit if you wish)https://github.com/thekidcoin/fluttercoin/releases/tag/v0.4.5.3-fltIn addition below is a mandatory stratum-mining update - this is the only version that will work with POT blocks, and this must be in place by the fork (it can be installed now - it will begin working immediately). Note you will need to first upgrade to Fluttercoin v0.4.5.3 above.https://github.com/thekidcoin/stratum-miningIt is the latest version, only mods are a few lines to support POT. This is mandatory for all pools to use this version for Fluttercoin.Binaries will be released Tuesday.
|
|
|
|
Will contact every pool and exchange (but pass this along if you could anyways), but here is info on the latest MANDATORY update: We are forking at block 22000 (approximately 7 days) - this update below is mandatory (you man take the HEAD commit if you wish)https://github.com/thekidcoin/fluttercoin/releases/tag/v0.4.5.3-fltIn addition below is a mandatory stratum-mining update - this is the only version that will work with POT blocks, and this must be in place by the fork (it can be installed now - it will begin working immediately). Note you will need to first upgrade to Fluttercoin v0.4.5.3 above.https://github.com/thekidcoin/stratum-miningIt is the latest version, only mods are a few lines to support POT. This is mandatory for all pools to use this version for Fluttercoin.Binaries will be released Tuesday. |
|
|
|
|
If your getting stuck, change the conf from addnode to connect - then download the blockchain. Shutdown the wallet. Change the conf back to addnode. Restart the wallet.
There could be a bad node out there forked - there is no fix except for it to be banned. There is no fork to fix etc.
Just blew away everything and re-downloaded the blockchain with no issue using the standard conf.
|
|
|
|
Wallet is not synching past 15553! ...maybe this will get your attention. Tried different approaches, one of which was using only the block explorer links as nodes. In this last attempt i got a beautiful " WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers." message instead of the normal green "Synchronizing with network..." bar. ...and noooobody gives a flying fuck. and PM Any plans on fixing the fucking 15553 fork? Or are you too busy not giving a fuck?
What do you think? |
|
|
|
Flutter is not asic resistant?
Never... |
|
|
|
|
Show Posts
