Topic: [ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving - page 231. (Read 368067 times)

Everyone should have known, an alert was sent out, and there was ample 1 weeks notice.  The nodes are on the right fork also.

No nodes are needed all actually as long as dnsseed=1 and noirc=1 is enabled as per the recommendation

Name:    dnsseed.fluttercoin.us
Addresses:  81.152.199.1
          54.199.237.235
          54.244.220.101
          82.247.88.92
          134.249.161.21
          71.254.142.160
          76.183.161.20
          192.99.35.62
          54.201.183.106
          54.203.244.170
          108.6.129.72
          107.170.6.172
          162.243.208.243
          95.223.54.204
          192.99.13.127
          218.87.111.74
          82.231.120.170
          106.186.121.158
          86.9.102.73
          188.226.191.238
          74.91.20.250
          78.72.45.32
          192.99.44.159
          128.73.104.246
          171.98.87.1
          82.138.34.183
          148.251.12.124

According to the OP the coin forked at block 22,000.

Someone needs to figure out which of the nodes are on the correct fork so that we can have the correct nodes in the conf file.

edit:  There are only 3 nodes in the conf file, that is bad form.

addnode=54.203.244.170
addnode=54.203.244.27
addnode=54.199.237.235

Whenever a dev forks a coin it is a serious event.  It can seriously hurt a coin if not done correctly.  Some things I noticed:

The mandatory wallet update is not mentioned in the title of this thread.  The title should be edited and the mandatory wallet info should be in all caps.
It is mentioned in the OP but not at the top of the page and not in near as big a font as it should be.

Devs think they are not responsible for letting everyone know about the new fork.  That is fine as long as you don't mind killing your own coin.

The nodes that are listed in the OP for the conf file must be updated if you fork a coin.  If the nodes are on the wrong fork you are going to have problems.

It was a great idea to switch to fixed rewards, that is a definite plus.

edit:  When the block number that the fork will occur on is reached the dev should be at the ready to fix problems.

Getting this message in wallet..

"WARNING! Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."

My wallet is latest version and re-installing it didn't help.

Might be a fork.

I would backup my wallet.dat, delete the blockchain and let it re-sync.

Did this coin recently fork?

which ban? i thought that was just rumour?

fluttercoin has died for me, the daemon it got to about block 21650 (can't remember exact number) and then went off on it's own fork, with 15MHash. I've tried changing addnode to connect, deleting everyhting but wallet and conf and now it is stuck on 0, with no connections, sometimes it blips 1 connection, then loses it, it's been a few days now. I've read through a zillion posts looking for a fix and changed the dnsseed, but that hasn't helped.  "ip" : "0.0.0.0" is somewhat suspicious, has my client stopped talking to the world?
My other coin wallets seem fine. I like the look of this coin, but if it's going to wander off on a  fork and lose the ability to keep the wallet up to date, I think I'm out.

 "version" : "v0.4.5.3-ga-beta",
    "protocolversion" : 70005,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 0,
    "timeoffset" : 0,
    "moneysupply" : 0.00000000,
    "connections" : 0,
    "proxy" : "",
    "ip" : "0.0.0.0",
    "difficulty" : {
        "proof-of-work" : 0.00024414,
        "proof-of-stake" : 0.00024414
    },
    "testnet" : false,
    "keypoololdest" : 1395858196,
    "keypoolsize" : 102,
    "paytxfee" : 0.01000000,
    "mininput" : 0.01000000,
    "errors" : ""

rpcuser=pictsidhe
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.2.11*
rpcallowip=192.168.2.100
connect=54.203.244.170
connect=54.203.244.27
connect=54.199.237.235
noirc=1
listen=1
dnsseed=0
server=1

looks like the ban in china is going into effect. i wonder if we will see a lot more fluttercoin volume on mintpal instead of bter

Getting this message in wallet..

"WARNING! Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."

My wallet is latest version and re-installing it didn't help.

Yeah, he solved it extremely quickly after another block was found.

hey moonpool did you see block 22300 solved by mr undestroyable? 0.00% and 2 actual shares. holy shit lol

well obviously it needs to be focused on proof of transaction feature

If they want to dump, let em. Its just inexpensive coin to pick up.

Flutter has a small market cap. Until people start hearing about it and get interested in it, it doesn't matter if multipools hold or dump.

Flutter just needs to spread its wings and fly. With a little marketing 

I like the idea of a sliding reward value based on hashrate. When wafflepool hits us with 30GH like they have at times, it would be great if the reward dropped to 500 or 1000 coins, this would kill profitability for them.

I agree with Jesse Livermore, if we stop buying the dumps they will have to stop mining it. But that's not realistic, they would just stop mining it till people started buying again then they would jump back on. We need to look at real long term solutions here.

+1 its really hard to maintain a coins growth if there's a multipool constantly converting flt/btc considering multipools already own around 50-60% of the network hash everyday and those coins will eventually get dumped in a short amount of time. Kid wouldn't want to change the algo, but i hope he will come up with something to prevent multipools.

100% accurate.

Very true, good point.