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

I haven't heard back from bitember.

I told them to jump on this thread.

Quote from: chris20131111 on June 25, 2014, 04:19:30 PM

How many coins can they be getting with block rewards only at 20 ? If they have to split that between everyone, it can't be that much total for each person for one day. You would get way more mining through the multipool than with block rewards at 20. I was getting about 3500-5500 coins a day mining with x11 on the multipool. I stopped mining though last friday whenever the fork and all this started though so not sure if the multipool is still going or what

just resceived a huge transaction of flutters from the fluttercoinpool.
+/- 5 days worth of flutter mining on fluttercoinpool.com

so that should be ok.

flutter was scam, its over. go to other scam coin.

So are the exchanges on the same chain as us?

Maybe I should cash out so I can buy back when this gets fixed. I have 2k on this chain and probably 1k on the other.

Mintpal I believe is on the right chain. I sent / withdrew earlier this morning. Not sure about the others since i've never used any.

This is all assuming the block explorer is on the right chain in the first place

Quote from: MobileWill on June 25, 2014, 07:46:28 PM

So are the exchanges on the same chain as us?

Maybe I should cash out so I can buy back when this gets fixed. I have 2k on this chain and probably 1k on the other.

bittrex is like 2 blocks off, and it's enabled again, i sent some to cryptsy and mintpal, checking.

cryptsy confirmed my coins arrived, mintpal shows the coins, but says 0/10 confirmations. I expect they are still running things manually to process things, until we know we are in the clear, Mintpal_Jason posted this previously.

Same here on MP. I sent 1.2 and its shows up but no confirms.

Ya mintpal is doing it manually so it will take a little bit longer than normal

There is 7mh being reported on explorer chain. I have 600khs solo and can add another 1.8mh to the cause, prefer to add it to an pool. Can we start ramping back up hashrate?

What's the consensus on PoW?

Can we get a statement of bitembers current reason on continuing on a fork?

Any other pools up?

Someone should take this coin over from that dumbass dev. It has a great potential with these features if we leave this idiot behind.

Quote from: coldbound on June 25, 2014, 10:54:33 PM

Someone should take this coin over from that dumbass dev. It has a great potential with these features if we leave this idiot behind.

Lot of people have this sentiment.

Can we get the other explorer setup? I remember it being delayed, but we need this going forward.

Explorer is the only current way to check things, look up blocks, etc. All pools and clients need to verify they arent on a wrong chain, and make it asap to sync properly. We have tried to provide peers to make this easier. We are on day 4 or 5 and other chains appear to continue to grow. If you are mining on a pool that have blocks that do not match explorer, please consider going solo or a different pool, it is likely that your rewards for mining will be loss. Also mining at fluttercoinpool.com is going to produce more FLT and helps price stability.

And again, kid if you are out there, what options do you see. I expect all this can be fix and rolled into the cloak wallet, but a hey I'm not dead would be good.

Wow, look at Bitember stats

Network Info
Difficulty   83.41351365
Est Next Difficulty   39.35238540 (Change in 1 Blocks)
Est. Avg. Time per Block   2 minutes 3 seconds
Current Block   44788

Block number is weird

Net hash
2908.95MH/s

Pool hash
25.21MH/s

Edit: They are down now.

Hey ofeefee, thanks for all your efforts on the sync issues, you've solved it for me (and probably many others), my missing coins have returned and sync is being maintained. Glad you're on board.

Don't worry about compensating bitember miners for their loss. They are on the wrong fork, that's how it goes. I also lost 250,000 FLT while I was solo mining in the first few days due to multiple forks at launch. I didn't cry and/or ask for compensation. This stuff happens and you must be paying attention when it does. Bitember has also caused forks in the past because of their huge hashrate.

ofeefee thanks for all the help I was on the wrong chain until your info, you have put a lot of effort in. I have been with this coin a long while, one thing I don't like is when both sides get into a put down contest of sorts. I do wish the kid would add something I am sure he can fix this or even redirect things. Something i find strange is all these pools running at 100's of M/hs. I might be wrong but I haven't see that rate on there even long before the fork.

For now, some kind of fix needs to happen so we can all be on the block explorers chain and get things back to normal. If that means PoW has to go, I don't mind. Would that do anything to mess up PoT / PoS ?
As for Kidcoin. He did tweet saying something about releasing the anon update on July 3rd or 4th. That is next thurs/fri. I think if by then he hasn't responded here, or anywhere where really, it would be safe to say he isn't coming back. We could then start to move forward with whatever else needs to be done. I am still holding out hope that Kid comes back and isn't injured in some hospital or something worse. He may not have had the best attitude at times, but he knows his stuff and PoT is a great idea and what defines this coin from everything else out there.

This is a beautiful thing! My main wallet, open wide, with listen=1 and addnodes set, oh yeah!

21:43:23

getpeerinfo

21:43:23

[
{
"addr" : "24.20.116.148:7408",
"services" : "00000001",
"lastsend" : 1403750556,
"lastrecv" : 1403750559,
"conntime" : 1403750453,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88366,
"banscore" : 0
},
{
"addr" : "54.72.71.185:7408",
"services" : "00000001",
"lastsend" : 1403750603,
"lastrecv" : 1403750603,
"conntime" : 1403750453,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88141,
"banscore" : 0
},
{
"addr" : "209.124.227.24:7408",
"services" : "00000001",
"lastsend" : 1403750455,
"lastrecv" : 1403750550,
"conntime" : 1403750454,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88955,
"banscore" : 0
},
{
"addr" : "98.220.203.77:7408",
"services" : "00000001",
"lastsend" : 1403750556,
"lastrecv" : 1403750556,
"conntime" : 1403750469,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88955,
"banscore" : 0
},
{
"addr" : "192.99.159.64:7408",
"services" : "00000001",
"lastsend" : 1403750556,
"lastrecv" : 1403750556,
"conntime" : 1403750475,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88955,
"banscore" : 0
},
{
"addr" : "66.11.162.228:7408",
"services" : "00000001",
"lastsend" : 1403750556,
"lastrecv" : 1403750565,
"conntime" : 1403750483,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88955,
"banscore" : 0
},
{
"addr" : "192.3.177.246:7408",
"services" : "00000001",
"lastsend" : 1403750556,
"lastrecv" : 1403750556,
"conntime" : 1403750483,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88955,
"banscore" : 0
},
{
"addr" : "69.59.38.87:7408",
"services" : "00000001",
"lastsend" : 1403750556,
"lastrecv" : 1403750556,
"conntime" : 1403750489,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88955,
"banscore" : 0
},
{
"addr" : "173.192.30.91:7408",
"services" : "00000001",
"lastsend" : 1403750603,
"lastrecv" : 1403750603,
"conntime" : 1403750496,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 87143,
"banscore" : 0
},
{
"addr" : "54.200.138.226:7408",
"services" : "00000001",
"lastsend" : 1403750556,
"lastrecv" : 1403750594,
"conntime" : 1403750505,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88955,
"banscore" : 0
},
{
"addr" : "189.110.136.147:7408",
"services" : "00000001",
"lastsend" : 1403750557,
"lastrecv" : 1403750558,
"conntime" : 1403750543,
"version" : 70009,
"subver" : "/Satoshi:0.7.5.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 88955,
"banscore" : 0
}
]

explorer.fluttercoin.com
Block Count:
88955

It's time to open the throttle a little bit.

if you are in sync with explorer.fluttercoin.com please consider modifying your fluttercoin.conf to change connect to addnode, and changing listen to 1

Edit: I did sync twice today using this fluttercoin.conf, but there is a possibility of bad peers still in the network, which is why I suggest using the one with connect in them.

First part is from OP post for fluttercoin.conf, other addnodes are the same as connect, but this allows you to start joining other nodes, and syncing them.

fluttercoin.conf

rpcuser=ofeefee
rpcpassword=x
rpcallowip=192.168.1.*
addnode=54.203.244.170
addnode=54.203.244.27
addnode=54.199.237.235
noirc=1
listen=1
dnsseed=1
server=1

addnode=98.220.203.77
addnode=76.177.91.53
addnode=71.61.60.138
addnode=192.99.159.64
addnode=209.124.227.24
addnode=70.70.239.50
addnode=107.170.172.93
addnode=66.11.162.228
addnode=192.3.177.246
addnode=98.193.106.107
addnode=69.59.38.87
addnode=86.212.55.167
addnode=173.192.30.91
addnode=178.203.9.140
addnode=213.214.63.127
addnode=65.6.105.7
addnode=54.200.138.226
addnode=24.20.116.148
addnode=66.11.162.228
addnode=69.59.38.87
addnode=178.130.36.81
addnode=178.203.9.140

Hi,
is this coin dead? i have coins that got lost on the way from my wallet to cryptsy. (no answer from Dev team).
dont see the transaction in the block explorer.
any idea what can i do.

thanks

Quote from: hashpower on June 26, 2014, 03:35:53 AM

Hi,
is this coin dead? i have coins that got lost on the way from my wallet to cryptsy. (no answer from Dev team).
dont see the transaction in the block explorer.
any idea what can i do.

thanks

if you don't see the coins in the explorer, then you were on a fork at the time. Not usually a reason to worry, when send from your wallet to cryptsy and you are on the fork, the coins are safe on the existing chain.

Look back a page or so in the thread and find the fluttercoin.conf with the connect= in them.

go to %appdata%\fluttercoin if on windows
make a backup of your wallet.dat file
delete everything but wallet.dat
create fluttercoin.conf and copy paste what I posted.

Then startup fluttercoin-qt, it should sync back up, once you sync, it should be same height as explorer, you can hover over the green arrow, or run getinfo in debug console.

All your coins should be there, if not, what you got should be what the chain sees if you are in sync, then resend your coins to cryptsy.

Good Luck!

And the coin is far from dead, network is rebuilding, i have 28 peers on my main wallet now, no lockup issues like it was doing a few days ago. Thanks to all who has been resyncing and validating things! Now if Kid can get our new wallet and cloaksend along with some new sync points to lock and load!