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

Hi
They are waiting for a updated wallet, should be soon.

Would you like to help out? We have a open skype chat were everybody are contributing their work and experience. It is a awesome group 

We are now syncing with the option "connect", it's a little bit slower but it's syncing.
Using the option "addnode" resulted in a 400 +/- block difference with the last block found.

We will have the block explorer online by tomorrow.

1) there is/was no hidden block
2) there can only be 1000 blocks @ 10K each - hence 10 million coins, hence any "hidden block" would be nullified as again - there can only be 1000 mined blocks PoW
3) main.h is correct - 10,000,000 * COIN is the max money
4) your taling about things that you don't understand - util.h is telling us the value for display of the coin - hence instead of doing something like 100 * 1000000 to convert an int64 as 100 instead you multiply 100 * COIN (which has a value of 1000000) hence max QTM IS SUPPOSED TO BE 10000000000000 expressed as int64 DUMBASS

You started all this BS based on stupidity and non-understanding of the code - you actually had them abandon QTM and move to QTM2???

Also you are reading the transactions wrong and you don't understand how POS transactions are formatted, and you obviously have no idea how to read as the block you are saying had 10,010,000 QTM in it has 10K in it an likely a test of 10 QTM while I was mining it.

WTF would be the point of mining all these coins? The market could never sustain it.

And finally - if one runs getinfo in the old QTM client - there is LESS THAN 10 million coins because of transaction fees that needed to be paid to ensure large transactions I sent to the QTM team were not delayed - I had many issues with this client and blew the original wallet up and likely lost a modest ammount of coins in the process (thousands)

This though speaks volumes as to the QTM team if you guys didn't see this was incorrect what this guy was saying.

DO NOT make accusations based on stupidy - PLEASE.

You are likely the cause of the FLT threats etc sent to me so likely you are also responsible for me quiting FLT.

Job well done Sherlock!

Yes, please proceed, we are using https://github.com/ofeefee/fluttercoin for the new build, our current explorer updated to this last night, and many of teamFLT are running it for their personal wallets to test everything out.  Code is a direct fork from thekidcoin, with minimal changes, new checkpoint/alert keys.

Use the following for syncing up.  network is still a bit flaky because of all the previous forks.  If it doesn't sync up to http://chainz.cryptoid.info/flt/, sync with connect instead of addnode, and change it back after sync.

I could have forced the new client not to talk to the old clients, but trying to make this as friendly as possible on the network.  So we have to do a little more work.

rpcuser=x
rpcpassword=x
rpcallowip=127.0.0.1
noirc=1
listen=1
dnsseed=1
server=1
seednode=54.84.46.196
seednode=87.98.188.77
seednode=54.215.241.255
seednode=50.147.45.28
addnode=54.84.46.196
addnode=87.98.188.77
addnode=54.215.241.255
addnode=50.147.45.28