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

Man, my only two PoS for today are orphaned again. Is your PoS working ofeefee

Edit,

Nevemind my PoS is working now. Computer must have shutdown during the rain and the time was stuck a couple of hours ago. After restarting the wallet it synced up fine and my PoS are all good.

Same here, my test 300 FLT also went through. Lets just hope that this is the right chain lol.

i have verified that my 100 and 19.99 are in my balance now.  I have not run further tests at the moment.

You must have a very sheltered life !

Would also appreciate this info

Our main wallet is now in sync with the official explorer and we've processed all pending deposits but we'll be leaving automatic processing off for a little while until we're 100% confident we're not going to get stuck on an invalid chain again.

I've also put up another temporary block explorer on a personal machine based on the above list of known-good nodes incase it helps. http://199.48.164.89/fluttercoin/

has anyone compiled the code from source, please send me a PM.

need to spin up a VM so I can test some things on linux, if you have a howto, download wallet src, download xx packages, and compile using this, would be appreciated.

Got an email from Mintpal saying they have suspended FLT deposits until they have someone check it out. Would be nice to get some kind of official word / fix from Thekidcoin so we can start to get this fixed asap.

fluttercoin.conf with above added nodes that match explorer chain
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=178.203.9.140
connect=65.6.105.7
connect=54.200.138.226
connect=24.20.116.148
connect=66.11.162.228
connect=69.59.38.87
connect=178.203.9.140
server=1
rpcuser=ofeefee
rpcpassword=x
listen=0
noirc=1
rpcallowip=192.168.1.*


Use this to sync only, after you have synced up, you have some options.

• change listen=0 to listen=1
• change connect to addnode

You can have performance issues as other bad nodes connect into you.  This is normal until the majority of nodes resync (everyone needs to check this, if they haven't!).  You can move back and forth as needed if you are trying to do something.  I wouldn't try to do anything else at the moment, just hold...

based on the ones you gave me.  I'll see if anymore connected, but this it their status.  Current chain is around 87700 at the time I ran this, if they are off by a good bit, most likely they are on a bad chain. I struck through the bad ones.

blocks=87138,peer=107.150.6.17:7408
blocks=87138,peer=66.11.162.228:7408
blocks=87138,peer=70.70.239.50:7408
blocks=87138,peer=64.90.187.229:7408
blocks=87138,peer=178.203.9.140:7408
blocks=87138,peer=178.63.168.46:7408
blocks=87131,peer=64.90.187.229:7408
blocks=87138,peer=54.201.183.106:7408
blocks=87138,peer=54.200.138.226:7408
blocks=87700,peer=70.70.239.50:7408
blocks=87138,peer=162.243.167.235:7408
blocks=87138,peer=50.180.178.143:7408
blocks=87138,peer=192.3.177.246:7408
blocks=87920,peer=54.201.183.106:7408
blocks=87138,peer=50.149.31.242:7408
blocks=87920,peer=50.180.178.143:7408
blocks=87138,peer=192.99.159.64:7408
blocks=87138,peer=24.20.35.80:7408
blocks=87920,peer=50.149.31.242:7408
blocks=87700,peer=192.99.159.64:7408
blocks=87138,peer=212.129.12.103:7408
blocks=87138,peer=98.220.203.77:7408
blocks=87131,peer=162.243.167.235:7408
blocks=87131,peer=24.20.35.80:7408
blocks=87138,peer=71.61.60.138:7408
blocks=88102,peer=212.129.12.103:7408
blocks=87700,peer=54.200.138.226:7408
blocks=87700,peer=192.3.177.246:7408
blocks=87138,peer=70.74.161.2:7408
blocks=87700,peer=178.63.168.46:7408
blocks=87928,peer=107.150.6.17:7408
blocks=87920,peer=70.74.161.2:7408
blocks=87700,peer=98.220.203.77:7408
blocks=87138,peer=24.20.116.148:7408
blocks=87138,peer=69.59.38.87:7408
blocks=87700,peer=24.20.116.148:7408
blocks=87700,peer=66.11.162.228:7408
blocks=87700,peer=69.59.38.87:7408
blocks=87138,peer=178.130.36.81:7408
blocks=87489,peer=178.203.9.140:7408
blocks=87602,peer=71.61.60.138:7408
blocks=87703,peer=178.130.36.81:7408

i expect since there's like 3 or 4 chains going on here, that you are getting bombarded with different blocks, and your CPU is suffering.  I suggest, using the list above, add the additional peers that are good, and see if that resolves it in the interim.  You can always remove this config later.

Just for clarification, explorer is at 87714 now, if your getinfo doesn't match this, you need to delete chain and sync with fluttercoin.conf previously mentioned.  I will edit to add these new nodes listed above that appear correct.

i suspect some of those nodes are on the wrong chain, block is found on wrong chain, it gets sent around, you mark it invalid, but for whatever reason the client does not like this at all.  I expect that as of last night, the other chain was longer which maybe the cause.

Your chain is shorter, and they have a longer one, and the client is trying to figure out if it wants to move to this chain.  I don't know how that works, just speculation.

Based on explorer.flutterchain.us, I would say you are on the correct chain, get me a FLT address, I'll send a test across.

And, I keep hoping that if we can surpass the bad chain in length the performance problems will cease to be an issue, but i haven't checked to see where the other chain/peers is.  I do know that some pools were on the bad chain, which was causing it to increase in size.  Hopefully that has stopped, and people are syncing back to this chain, and hashrate stays steady we can get it resolved.

this can be solved quickly by Dev releasing a checkpoint, but no word.

Let me load your peers, I'll see what their heights are...give me a few.

That being said - why is the wallet running at 80% CPU?

Here is our nodelog. We have 16 connections. No idea if we are "legit" or not. I don't own any fluttercoin to test sent to cryptsy, and I cant send a users coin on the off chance it disappears.

As of writing, we have 87679 blocks. Ignore the first column thats just a database ID key for the node. The last column was the timestamp of the last update/IE the newest nodes we've connected to.

6776509   FLT   107.150.6.17:7408   70009   /Satoshi:0.7.5.7/   2014-06-22 15:25:27   2014-06-24 13:45:02
6246294   FLT   66.11.162.228:7408   70009   /Satoshi:0.7.5.7/   2014-06-18 13:34:24   2014-06-24 13:45:02
6776520   FLT   70.70.239.50:7408   70009   /Satoshi:0.7.5.7/   2014-06-22 15:25:27   2014-06-24 13:45:02
1130   FLT   64.90.187.229:7408   70007   /Satoshi:0.7.5.7/   2014-05-07 11:55:30   2014-06-24 13:45:02
4848922   FLT   178.203.9.140:7408   70009   /Satoshi:0.7.5.7/   2014-06-09 01:01:01   2014-06-24 13:45:02
7063865   FLT   178.63.168.46:7408   0      2014-06-24 10:09:58   2014-06-24 13:45:02
588896   FLT   54.201.183.106:7408   70007   /Satoshi:0.7.5.7/   2014-05-11 12:25:25   2014-06-24 13:45:02
1129   FLT   54.200.138.226:7408   70007   /Satoshi:0.7.5.7/   2014-05-07 11:55:30   2014-06-24 13:45:02
2442616   FLT   162.243.167.235:7408   70009   /Satoshi:0.7.5.7/   2014-05-24 23:07:37   2014-06-24 13:45:02
4280606   FLT   50.180.178.143:7408   70009   /Satoshi:0.7.5.7/   2014-06-05 12:54:48   2014-06-24 13:45:02
6776514   FLT   192.3.177.246:7408   70009   /Satoshi:0.7.5.7/   2014-06-22 15:25:27   2014-06-24 13:45:02
4277646   FLT   50.149.31.242:7408   70009   /Satoshi:0.7.5.7/   2014-06-05 12:27:50   2014-06-24 13:45:02
6794112   FLT   192.99.159.64:7408   70009   /Satoshi:0.7.5.7/   2014-06-22 18:07:04   2014-06-24 13:45:02
4181970   FLT   24.20.35.80:7408   70009   /Satoshi:0.7.5.7/   2014-06-04 21:55:55   2014-06-24 13:45:02
3659673   FLT   212.129.12.103:7408   70009   /Satoshi:0.7.5.7/   2014-06-01 18:04:10   2014-06-24 13:45:02
2610929   FLT   98.220.203.77:7408   70009   /Satoshi:0.7.5.7/   2014-05-26 02:35:29   2014-06-24 13:45:02
6776512   FLT   71.61.60.138:7408   70009   /Satoshi:0.7.5.7/   2014-06-22 15:25:27   2014-06-24 09:56:33
7009699   FLT   72.133.225.98:7408   70009   /Satoshi:0.7.5.7/   2014-06-24 02:05:59   2014-06-24 05:27:50
4122721   FLT   70.74.161.2:7408   70009   /Satoshi:0.7.5.7/   2014-06-04 12:32:41   2014-06-24 01:52:30
7000635   FLT   203.100.215.90:7408   70009   /Satoshi:0.7.5.7/   2014-06-24 00:45:13   2014-06-24 01:25:39
6926035   FLT   92.222.19.210:7408   70009   /Satoshi:0.7.5.7/   2014-06-23 13:47:18   2014-06-24 01:25:39
198531   FLT   24.20.116.148:7408   70008   /Satoshi:0.7.5.7/   2014-05-08 20:48:20   2014-06-24 00:31:49
344546   FLT   69.59.38.87:7408   70008   /Satoshi:0.7.5.7/   2014-05-09 17:50:04   2014-06-23 17:08:39
1131   FLT   54.203.244.27:7408   70008   /Satoshi:0.7.5.7/   2014-05-07 11:55:30   2014-06-23 16:28:19
6919981   FLT   86.212.55.167:7408   70009   /Satoshi:0.7.5.7/   2014-06-23 12:53:38   2014-06-23 15:34:42
6938108   FLT   81.249.242.170:7408   0      2014-06-23 15:34:42   2014-06-23 15:34:42
6900821   FLT   178.130.36.81:7408   70009   /Satoshi:0.7.5.7/   2014-06-23 09:59:09   2014-06-23 15:21:16
2532796   FLT   69.122.150.85:7408   70009   /Satoshi:0.7.5.7/   2014-05-25 13:27:43   2014-06-23 13:33:50

coin forked, some clients are on a different chain, official chain is "supposed" to be matching explorer.fluttercoin.us. Nodes listed above are on the explorer chain, as is cryptsy and bittrex last check, i have asked for additional nodes to add, but it appears no one gives a damn to share their peer IP.  There are 3 official nodes in the OP, none are accepting connections.

It forked back on friday I believe. We may have fixed it but we are all waiting on Thekidcoin to come here and confirm that the block explorer is indeed on the correct chain. Without knowing exactly what chain is correct, we can't really do much more.

Ok - so whats going on? I actually came here to ask why our fluttercoind is pretty much sitting at 80% CPU usage, with gen=0 and 87662 blocks - but then I see that it may be forked on a lot of different chains?

Is the CPU usage related? I'm tempted to kill the wallet, it's using about 25% of the entire CPU power for the wallet server it's on, making all the other coins slow as heck.

Can someone link to a summary of what exactly the issue is? A quick scroll through of the last 2 pages, I didnt see anything with more details than "boke".

my 2mhs is scaling back up, accidentally closed my client looking at something, all my rigs went offline for a bit, they are back up now,  I would expect that you technically "are" the network so not sure if you can fork if you are the only one hashing, but yes, we need more hashing if others have a gpu or so to add a solo mine config, you can my post, it's configured to allow solo mining, and in your miner -o yourwalletmachineip

The network needs more hashrate!!! I can't scale back hash right now.

mintpal is having issues.  cryptsy and bittrex confirmed my transfers

Update - 6/24 11:38cst
opened a ticket with Mintpal to ask they check their wallet, transids I sent, confirmed by official explorer.flutterchain.us
my transids that were sent to mintpal
bittrex -> mintpal -> 100.00
e2ed845b8ddda07830899e2a1f808227eafc633ee8c8557eaba7fc2c6d6e0556
wallet -> mintpal -> 19.99
42ce231b22b496e23de3c8423c5f893b6f62c41bf4be38eddecf8de17ea0af4d

Alright guys, my cloak just sold on bittrex, time for some trading, will check back later this afternoon, but babysitting my wallet doesn't pay well.

Finally synced to the official block explorer thanks to ofeefee . I have sent a test 300 FLT to mintpal a few mins ago but still not showing anything. I think they may be on the wrong fork which would suck. I was doing a little trading on there the past couple of days.