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

[ofeefee]

Using ofeefee .conf file, I was finally able to reload my wallet all the way after it locking up 2 times. Current block the wallet shows is block 87489.
Offical block crawler is on 86944.

I have 79,000 FLT all orphaned PoS, wtf.

You need to have connect statements, and you need to delete your blockchain and redownload the chain.

Need to still check my peers, will get a new list of what I have that matches explorer.

Kid must be going to release the cloak wallet with the fix all at once.

To those with problems, when its corrected you can re download and it will restore missing items and pos can happen again.

[1714669433]

1714669433

[1714669433]

1714669433

[1714669433]

1714669433

[chris20131111]

Using ofeefee .conf file, I was finally able to reload my wallet all the way after it locking up 2 times. Current block the wallet shows is block 87489.
Offical block crawler is on 86944.

I have 79,000 FLT all orphaned PoS, wtf.

You need to have connect statements, and you need to delete your blockchain and redownload the chain.

Need to still check my peers, will get a new list of what I have that matches explorer.

Kid must be going to release the cloak wallet with the fix all at once.

To those with problems, when its corrected you can re download and it will restore missing items and pos can happen again.

What you mean connect statements? I have deleted all files and reloaded the whole chain like 3 times now, this is my .conf file.

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
noirc=1
listen=1
dnsseed=1
server=1
addnode=54.203.244.170
addnode=54.203.244.27
addnode=54.199.237.235
addnode=98.220.203.77
addnode=76.177.91.53
addnode=91.123.91.65
addnode=95.221.16.69
addnode=71.61.60.138
addnode=188.165.3.223
addnode=89.190.253.27
addnode=83.86.92.116
addnode=192.99.159.64
addnode=69.59.38.87
addnode=173.175.130.35
addnode=71.200.192.224
addnode=209.124.227.24
addnode=78.20.226.228
addnode=101.78.254.170
addnode=173.175.130.35
addnode=209.124.227.24
addnode=70.70.239.50
addnode=107.170.172.93
addnode=66.11.162.228
addnode=192.99.13.127
addnode=192.3.177.246
addnode=122.108.198.199
addnode=65.6.105.7



This is what I had before in my .conf
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
noirc=1
listen=1
dnsseed=1
server=1
addnode=54.203.244.170
addnode=54.203.244.27
addnode=54.199.237.235
connect=54.203.244.170
connect=54.203.244.27
connect=54.199.237.235
connect=98.220.203.77
connect=76.177.91.53
connect=91.123.91.65
connect=95.221.16.69
connect=71.61.60.138
connect=188.165.3.223
connect=89.190.253.27
connect=83.86.92.116
connect=192.99.159.64
connect=69.59.38.87
connect=173.175.130.35
connect=71.200.192.224
connect=209.124.227.24
connect=70.113.15.89
connect=78.20.226.228
connect=101.78.254.170
connect=173.175.130.35
connect=209.124.227.24


I couldn't load the whole chain at all like that b/c it keeps locking up my wallet when it gets to around last weekend time frame.

[Kryon]

why wallet not responding?

[ofeefee]

In %appdata%\fluttercoin
Delete everything but wallet.dat
Create fluttercoin.conf

connect=54.203.244.170
connect=54.203.244.27
connect=54.199.237.235
connect=98.220.203.77
connect=76.177.91.53
connect=91.123.91.65
connect=95.221.16.69
connect=71.61.60.138
connect=188.165.3.223
connect=89.190.253.27
connect=83.86.92.116
connect=192.99.159.64
connect=69.59.38.87
connect=173.175.130.35
connect=71.200.192.224
connect=209.124.227.24
connect=78.20.226.228
connect=101.78.254.170
connect=173.175.130.35
connect=209.124.227.24
connect=70.70.239.50
connect=107.170.172.93
connect=66.11.162.228
connect=192.3.177.246
connect=122.108.198.199
connect=65.6.105.7

Please please post your public IP so people can add connect=yourip so we can have more synced node that are correct...well if explorer is correct. ONLY IF YOU ARE IN SYNC WITH EXPLORER BLOCK HEIGHT

Would be nice to be able to ban nodes in client so you could self prune so you don't talk to other peers on forks, like delnode=IP and I won't use that peer.

Once we get most nodes synced back up we could go back to addnode, but there are lots of peers on wrong chains

[ofeefee]

So does no one know how to contact kid?  Someone has to be able to ask him for an update?

And can I just zip up the directory under appdata/fluttercoin if I want to backup the blockchain and provide if someone wants, not sure I have the space...or the bandwidth.

Wish we had more official nodes.  I've debated on putting some wallets in aws, to play around with.

Only 1 official node was working yesterday, and I am not connected to it anymore so maybe it died too.

[Stedy]

thanks ofeefee, that last conf got things going again. However i'm now less 200k coins than what i know i have. Gah!

[ofeefee]

thanks ofeefee, that last conf got things going again. However i'm now less 200k coins than what i know i have. Gah!

Wow, did you move any recently?  Hope oncenit finishes on syncing you will be whole.

[Stedy]

i did do transfer's recently, and yes, i hope they reappear also. I've put a lot of time and energy and money into this coin. This would be a huge kick in the face if they were to disappear.

Would be really cool to hear from thekidcoin on this issue. I know he's probably busy however some sort of an update would probably be a smart move.

[JustBetweenUs]

Would be really cool to hear from thekidcoin on this issue. I know he's probably busy however some sort of an update would probably be a smart move.

Indeed.

[LastUpdateDate]

does it fly away?

[ofeefee]

In %appdata%\fluttercoin
Delete everything but wallet.dat
Create fluttercoin.conf

connect=54.203.244.170
connect=54.203.244.27
connect=54.199.237.235
connect=98.220.203.77
connect=76.177.91.53
connect=91.123.91.65
connect=95.221.16.69
connect=71.61.60.138
connect=188.165.3.223
connect=89.190.253.27
connect=83.86.92.116
connect=192.99.159.64
connect=69.59.38.87
connect=173.175.130.35
connect=71.200.192.224
connect=209.124.227.24
connect=78.20.226.228
connect=101.78.254.170
connect=173.175.130.35
connect=209.124.227.24
connect=70.70.239.50
connect=107.170.172.93
connect=66.11.162.228
connect=192.3.177.246
connect=122.108.198.199

Please please post your public IP so people can add connect=yourip so we can have more synced node that are correct...well if explorer is correct. ONLY IF YOU ARE IN SYNC WITH EXPLORER BLOCK HEIGHT

Would be nice to be able to ban nodes in client so you could self prune so you don't talk to other peers on forks, like delnode=IP and I won't use that peer.

Once we get most nodes synced back up we could go back to addnode, but there are lots of peers on wrong chains

I'm done, if you want a list of valid nodes that match explorer, you can PM me for my list.  Some asshole is on the wrong chain and keeps sending me bogus blocks, client is all fucked up now.  THANKS!

Here's the culprit...right out of debug.log. If you know who you are, follow the directions!
accepted connection 193.136.98.184:34679
send version message: version 70009, blocks=87085, us=65.6.105.7:7408, them=193.136.98.184:34679, peer=193.136.98.184:34679
Added time data, samples 12, offset +4 (+0 minutes)
receive version message: version 70009, blocks=87858, us=65.6.105.7:7408, them=193.136.98.184:7408, peer=193.136.98.184:34679

[bqxpd]

transferred 250k flt from bittrex and it's nowhere to be seen. 

I'm seeing the same thing. I've sent three transactions in the last few hours, each about 30 minutes apart. Only the first made it to its destination. The other two look like they've sent, but have generated zero confirmations, and their transaction IDs do not appear in the blockchain. Fortunately these were just small test transactions of 5 FLT each; I was planning to send a much larger amount, but after skimming this thread decided I to send a few tests first since so many people were reporting sync issues.

[ofeefee]

always nice when the main OP nodes are down...this just keeps getting better...
trying connection 54.203.244.170 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.27 lastseen=0.0hrs
connection timeout
trying connection 54.199.237.235 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.170 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.27 lastseen=0.0hrs
connection timeout
trying connection 54.199.237.235 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.170 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.27 lastseen=0.0hrs
connection timeout
trying connection 54.199.237.235 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.170 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.27 lastseen=0.0hrs
connection timeout
trying connection 54.199.237.235 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.170 lastseen=0.0hrs
connection timeout
trying connection 54.203.244.27 lastseen=0.0hrs

[mjgraham]

I think were going to need a fix at another level, if I use the list and turn off listen=1 in the .conf it works good but as soon as I turn it back on here comes a few nodes outta wack.

[coinlighter]

Using ofeefee .conf file, I was finally able to reload my wallet all the way after it locking up 2 times. Current block the wallet shows is block 87489.
Offical block crawler is on 86944.

I have 79,000 FLT all orphaned PoS, wtf.

Sorry to go off topic, but how many coins do you need to have 70000 POS reward?

[ofeefee]

pruned some of the nodes that were no longer responding, clients shut down.  And we got some new friends synced up.

NOTE - do not use these if you are on the other chains, you will have issues with your client, as will these that you are connecting to.  You need to delete all that is in your %appdata%\fluttercoin (except wallet.dat).
Create fluttercoin.conf and start qt, I'm testing it from scratch at the moment, I synced earlier just looking for nodes, and got the wrong chain, yeah! BOO HISS!

I modified this so I could solo mine to add some additional hashrate, and some block traffic...also I changed listen=0 so it doesn't accept outside connections while you sync.  I just had an issue where I saw a bad chain in my peer list.  monitoring it...

connect=54.203.244.170
connect=54.203.244.27
connect=54.199.237.235
connect=98.220.203.77
connect=76.177.91.53
connect=71.61.60.138
connect=192.99.159.64
connect=209.124.227.24
connect=70.70.239.50
connect=107.170.172.93
connect=66.11.162.228
connect=192.3.177.246
connect=98.193.106.107
connect=69.59.38.87
connect=86.212.55.167
connect=173.192.30.91
connect=178.203.9.140
connect=213.214.63.127
connect=65.6.105.7
server=1
rpcuser=ofeefee
rpcpassword=x
listen=0
noirc=1
rpcallowip=192.168.1.*

oh and it's not fluttercoin, but this wiki is nice, has descriptions of what different things do in your conf file.
https://en.bitcoin.it/wiki/Running_Bitcoin

[ofeefee]

I think were going to need a fix at another level, if I use the list and turn off listen=1 in the .conf it works good but as soon as I turn it back on here comes a few nodes outta wack.

yeah i just noticed that in my conf...i set listen=0 for now.  I was blocking a few bad chains in my router, but they keep getting showing up.

[ofeefee]

Using ofeefee .conf file, I was finally able to reload my wallet all the way after it locking up 2 times. Current block the wallet shows is block 87489.
Offical block crawler is on 86944.

I have 79,000 FLT all orphaned PoS, wtf.

Sorry to go off topic, but how many coins do you need to have 70000 POS reward?

about 800k or so, that's real nice! My PoS is usually around 8-10% per stake.

[ofeefee]

pruned some of the nodes that were no longer responding, clients shut down.  And we got some new friends synced up.

NOTE - do not use these if you are on the other chains, you will have issues with your client, as will these that you are connecting to.  You need to delete all that is in your %appdata%\fluttercoin (except wallet.dat).
Create fluttercoin.conf and start qt, I'm testing it from scratch at the moment, I synced earlier just looking for nodes, and got the wrong chain, yeah! BOO HISS!

I modified this so I could solo mine to add some additional hashrate, and some block traffic...also I changed listen=0 so it doesn't accept outside connections while you sync.  I just had an issue where I saw a bad chain in my peer list.  monitoring it...

connect=54.203.244.170
connect=54.203.244.27
connect=54.199.237.235
connect=98.220.203.77
connect=76.177.91.53
connect=71.61.60.138
connect=192.99.159.64
connect=209.124.227.24
connect=70.70.239.50
connect=107.170.172.93
connect=66.11.162.228
connect=192.3.177.246
connect=98.193.106.107
connect=69.59.38.87
connect=86.212.55.167
connect=173.192.30.91
connect=178.203.9.140
connect=213.214.63.127
connect=65.6.105.7
server=1
rpcuser=ofeefee
rpcpassword=x
listen=0
noirc=1
rpcallowip=192.168.1.*

oh and it's not fluttercoin, but this wiki is nice, has descriptions of what different things do in your conf file.
https://en.bitcoin.it/wiki/Running_Bitcoin

**confirmed** full sync without any other nodes jumping in to mess it up.  

After you do sync up you want to close the client and modify listen=0 to listen=1  It is going to cause your client to lock up if a bad peer connects, but if you aren't doing anything but letting it run, at least someone can connect to you to download.  Can always kill it, set listen=0 to do whatever, then switch it back on as needed.

[MobileWill]

I am trying to figure out if I can on the "right" chain. My block count matches http://explorer.fluttercoin.us/ but diff doesn't match. And my friend has a way higher block count and diff. His diff is closer to http://flt.bitember.com.

What is right? Should I stop solo mining till this is figured out? I am finding a lot of blocks.