[ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving

[zhouhuiyan520]

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.

[1715547825]

1715547825

[1715547825]

1715547825

[1715547825]

1715547825

[1715547825]

1715547825

[Invisible Hands]

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.

[Invisible Hands]

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

[Invisible Hands]

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

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

[thekidcoin]

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

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

[thekidcoin]

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.

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

[thekidcoin]

ALL: if you want to find nodes to use, this page will list all nodes connected to a know good node:

http://explorer.fluttercoin.us/peers.php

As you can see, it will list the version and the starting height - the starting height does not mean that's the height that the client is on FYI.  that's just what block they were on when the client started...

[thekidcoin]

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

Your IP was likely banned because you were on a fork FYI

Get some nodes here: http://explorer.fluttercoin.us/peers.php

[thekidcoin]

When the hell those wallet problems will end?

When:

1) pools especially the locust muti-pools are responsible with hashrate distribution
2) people upgrade their clients pre-fork
3) people actually pay attention to their wallet, instead of leaving it on a forked chain for days
4) people understand how to setup and maintain a conf file

All of these issues are node related issues because of one of the above.

[thekidcoin]

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.

http://explorer.fluttercoin.us/peers.php

get some peers from this list and add to your conf file - make sure they are on the same version

[thekidcoin]

So, does someone have a marketing plan? Or at least some interesting marketing ideas?

Sure market away... as long as it doesn't cost me anything LOL (you should see how many emails I get from people trying to make money) it has to be a community effort

BTW we should setup some sort of a donation bucket, to pay for some things that would help the coin out marketing wise

[thekidcoin]

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

Fastest block, ever LOL

[thekidcoin]

So, does someone have a marketing plan? Or at least some interesting marketing ideas?

Sure market away... as long as it doesn't cost me anything LOL (you should see how many emails I get from people trying to make money) it has to be a community effort

BTW we should setup some sort of a donation bucket, to pay for some things that would help the coin out marketing wise

I think it would be a good idea to offer some bounties for professional logo, high quality YouTube videos presenting and advertising Fluttercoin, articles on popular websites and blogs (with at least 100 visitors per day), etc.

All fine, so who is donating to the bounty?

[thekidcoin]

So, does someone have a marketing plan? Or at least some interesting marketing ideas?

Sure market away... as long as it doesn't cost me anything LOL (you should see how many emails I get from people trying to make money) it has to be a community effort

BTW we should setup some sort of a donation bucket, to pay for some things that would help the coin out marketing wise

I think it would be a good idea to offer some bounties for professional logo, high quality YouTube videos presenting and advertising Fluttercoin, articles on popular websites and blogs (with at least 100 visitors per day), etc.

All fine, so who is donating to the bounty?

Everyone who wants this coin to succeed.

Sounds good to me I'm sure a lot of people will donate something... myself included.

Let me figure out some things with regard to taking donations for marketing, bounties etc.  That way then when something comes down the pipe we can release funds.  Still actually need to get a donation for some sort together for the person who made the website for us.

[axo]

You would left the rewards as they are now, maximum 5K, 2.5K, etc, but adopted a system of adjusting the rewards down/up based on difficulty/hashrate, with the current reward levels being the maximums, possibly it could alleviate some dumping.

Say a multipool wanted to mine because it was profitable at 5000, but then their hashrate hit the coin and the reward dropped to say 4000, the coin may not be as profitable and they would switch to a new coin (maybe)

If you throw 20gH at it, say with ASIC's, maybe the reward will drop to 500 or something, and they would stop mining.

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.

The idea of drop reward when big multipool hits the coin is not as good as it looks because the network can react only after the multipool mined some blocks. There is a time shift between the time a multipool starts mining the coin and the time of reward drop. Doing an intermittent mining, this timeshift can be exploited by the multipool to lower the average reward generating fluctuating block reward, and mine only higher reward blocks.

I thought many days about a way to discourage multipools but my conclusion is that the only way is the opposite: encourage the multipool (and other miners) to continue mining the coin, leaving the stabilization to the market.
I think that if the block reward would grow with the difficulty, the coin would be more stable. This cause an offer increase in the market, the price will adjust accordingly and the mining profit change, so miners and multipools can join or leave the coin accordingly. This is a longer cycle that can generate a smoother fluctuation. With actual fixed block reward we have a mining profit drop immediately after network power increase, without waiting for a price adjustment in the market, it is too fast, in my opinion this generate instability.

There are many possibility for incresing the block reward, but if the reward is proportional to difficulty we have a coin with predictable mining costs because the reward for a single rig becomes indipendent from the network power.

[seattletu]

Logo looks fine to me, no need for a new one IMO

[seattletu]

We need an article on coindesk to tell people about fluttercoin and its proof of transaction feature

[seattletu]

You can email them at news@coindesk.com I'm gonna send them an email right now

[seattletu]

Donated coins could be put to better use I think

[thekidcoin]

Donated coins could be put to better use I think

Yep, Logos don't make a coin a success