Maybe one day...

thekidcoin  --  Че за хрень - у меня в кошельке 110000 тысяч  - после установки нового кошеля остается только

 14000 тысяч. В чем дело ??

My wallet refuse to sync above 15553, 1447 Blk remaining, on XP & seven

I dled from the thread and from website.

kidcoin what do you think about tweaking the code so that the potr hits 4 times as often, but 4 times less amount of reward? is it even possible to code it that way?it will be more fun if it's like a casino machine, winning more often  

I'll just bounce this back to you once it's confirmed.

Does anyone know how to find/create a list of the previous PoT rewards? Or what the probability is that you'll hit one? I know it's tied to the block hash etc etc but was just wondering if anyone knew?

After re-reading the pdf on PoT again, I guess pot size doesn't matter as long as it's 501FLT. Payout is still 2500FLT, 50% of the block reward. Again, correct me if I'm wrong, I am getting tired.

So.... Instead of it costing just myself 501 (actual 500.01) for everyone to be able to play, you want all players to pay 501. I am ok with that, but I don't know if it will expand our player-base. It's still an unlimited chance to win 2500 for just 501.
If you guys really want this game to be a members only thing, since you want your existing FLT secured, I'll do the buy-in for 501, but that means running pot will be reduced by me to 501, to stay at 501. The extra in the current pot, which would need to be sent to me, will be turned into cold storage. I'll hold all the buy-ins for replenishment in case of emergency in cold storage wallet. I'll keep a running list of who paid and provide addresses. I'd also write up a revised game description to accommodate.

What do you think? Will this just secure our funds, or will this prevent people from playing? I mean, it's not entirely bad to have a buy-in. Kinda like the lottery. Keep in mind this game was meant for anyone to pay for free, and any FLT invested up to this point other than the original 500.01 of mine was based on a misinterpretation, but can go towards the buy-in or can even be refunded as it gets passed to the investor or I can issue refunds if game coins come to me. Should we push the reset button? You guys tell me. I downloaded the wallet on my cold storage computer awaiting input from you guys. If we go with buy-ins, DO NOT send me buy-ins to my game address, I will provide the cold storage address. Any PoS will go toward our funds.

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.

Little game called ''pass the flutter''. Requires nuthin' but honesty to play. seattletu, post your address, ill send ya 250 FLT, if you're game.

Keep a log going, the person who receives the FLT should cut and paste where it came from rather than quoting for message space reasoning. Don't want entire thread space taken up because of the game

So, like this:

Halofire to seattletu 250 FLT (then write) BONUS or NO BONUS.
seattletu to (whoever) 250 FLT BONUS or NO BONUS.


Best part is it won't cost anybody anything except tiny transaction fee for a chance to receive 500 FLT = 2x the amount of FLT sent. People could add to it as well if they want a chance to get even more FLT back! How you drum up the next person is up to you. You can send to a person who has had the flutters before, too! I just ask, seattletu, that you'd send them forward and not back to me. I could write something up better for the game when it's 'go' time, directions and such.

So... you game?

Donated coins could be put to better use I think

Everyone who wants this coin to succeed.

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.

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

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

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.

When the hell those wallet problems will end?

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

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.

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