Topic: [ANN] Fastcoin - FST - The Fastest coin so far in the market - is launched!! - page 15. (Read 238167 times)

In April of 2016, the block reward for Fastcoin was about 8.  Your transaction would have 1,250 inputs and perhaps less depending what was in the pools wallet.  Most likely these transactions were too large in size (KB) and were never mined into any blocks.  We have seen this problem several times before.  When I had this problem, I had to do a restart my Fastcoin client with -zapwallettxes which took 4 days to reprocess the blockchain.  This is what fst.thecoin.pw will need to do (but this may cause them other problems and they won't want to do it).  After restarting my client, I was table to retrieve my Fastcoins to send them again to Cryptopia in smaller amounts (5000 FST or 2000 FST or 500 FST).  I had to repeat the restart process several times.

Fastcoin has a problem that Bitcoin doesn't have.  The Block rewards are rather small in terms of local currency.  Basically at this point, the miners are mining dust.  And sending dust requires a lot of space on the blockchain.  In my experience, a transaction should be less than 10KB to be safe to be confirmed.  Unfortunately, the big pools and exchanges don't know about that so they sometimes make transactions that will never be confirmed.  This 10KB limit in size requires many transactions to be sent.  Good Luck!

If the coins were mined on the wrong fork, then that would be another reason why the transactions never confirmed.

If a pool mined on the wrong fork then those coins are effectively lost. The blocks on the wrong fork will be orphans when compared to the main/preferred chain. You cannot send coins across two different chains.

I have the same problem
FST txid: 07b65e29fcbd1d82df543c4f65919275547505b933f893e7afce7d2302223e29    Timestamp    31st Dec 1969 18:00:00

FST   8820.71070926   UnConfirmed   Normal   07b65e29fcbd1d82df543c4f65919275547505b933f893e7afce7d2302223e29   0/200   3/03/2016 10:08:00 AM

But the coins never reached Cryptopia, there is no single confirmation.
And before that, as well, 6 transactions of 10,000 FST have no confirmations

 FST   10000.00000000   UnConfirmed   Normal   f5e903dfb0fa7a10b1aa70543a19881a2ccc2ce64b5381b9ae07fcd141b3e5b3   0/200   3/03/2016 10:03:00 AM
 FST   10000.00000000   UnConfirmed   Normal   3d96e554dfb2e34bbe72144b86e7e71c3cfc525a261405f2c3616d2a47776cc3   0/200   3/03/2016 10:04:00 AM
FST   10000.00000000   UnConfirmed   Normal   d66034b0ea4c6b6ceab54d3f424b46db2cbeffdffc908f455557b3462ad8c303   0/200   3/03/2016 10:05:00 AM
 FST   10000.00000000   UnConfirmed   Normal   aa60f7640f1c1f5838051c4cafd411aa9063aa6985e9197e2c16f315551b23fc   0/200   3/03/2016 10:05:00 AM
FST   10000.00000000   UnConfirmed   Normal   9fe772a4cf67dd412b35ddfbff5a589174a228845ab15db7e729c39bd947699d   0/200   3/03/2016 10:07:00 AM
 FST   10000.00000000   UnConfirmed   Normal   555b6e1517d0cd6dabc33c11d701319a66de68198487a401bff18fb8fbc6b182   0/200   4/03/2016 12:32:00 AM

 and there is no record in the blocker http://fst.blockexp.info, only the TX ID tags on the Cryptopia exchange about incoming transactions, but without confirmation.
DEV can you still get these coins? they were mined at the mine fst.thecoin.pw, but the owner of the shoal says that he had the wrong fork and he never received any coins.
ATP for attention, I'm waiting for help ...   my e-mail [email protected]

Hello all FastCoin community members and Cryptocurrency fans,



I wanted to take the time to thank Livecoin and Cryptopia for working with our Development team on this most recent issue.  

We do want to inform the community that our investigation is ongoing and we are still waiting for some additional data back from Cryptopia on this matter.  It is recognized that the users directly involved with this issue may have experienced unnecessary inconvenience.  Its important to point out that we have outlined in the past our recommended best practices to holders of FastCoin and Crypto's in general in that the best way to hold your Cryptocurrency is within your own personal wallet.  Exchanges certainly do serve a purpose, however without a properly regulated framework this case in point, clearly points out some of the challenges that exists in this space as we work to resolve the reported issue.  Without going into further detail, we continue to encourage best practices moving forward and users wishing to purchase FastCoin and withdraw their coins can continue to do so from Cryptopia without issue.

If you have any further questions or concerns of what our position is with respects to "Best Practices" and how to hold your coins, please feel free to email us at [email protected].

Our team has been working diligently on additional upgrades and enhancements to FastCoin, with that, we would ask any community members that are currently hosting mining pools and either have supported or continue to support mining of FastCoin to please forward us their mining pool details.  We would like to make this information available to all community members moving forward with an up to date list of available FastCoin miners.  Also, with the potential upcoming changes to FastCoin we may require some changes to take place on the mining side of the equation and before we release this information we want to make sure FastCoin mining pool operators have all of the latest information available to them before we make our release public.

Again, all mining pool operators, please email us at [email protected] and in your email please give us the name of your mining pool, URL address etc as well as what standard you are currently mining on, IE 8.7.2 or 10.2.2 etc.

Thank you all again for your continued support as we look forward for a very exciting year ahead.

Sincerely

/C

Thank you Yaremi,

Please note we have also reached out to Cryptopia on this issue and are awaiting their reply.  

Once we receive VALID txid's from them on this issue we would be happy to share them with you.

Best

Fast

Hello.


Livecoin don't need to rescan because them didn't sent this invalid transaction. Only Cryptopia need to do that.

About this transaction.

http://fst.blockexp.info/tx/7bc9e159868a057cb5cd3cdfddcf78bf76aeb4b41450d24c9db8831c076bac51



1. Time not correct. 31st Dec 1969 18:00:00 LOL
2. Confirmations. We see that this transaction have 10475685 confirmations but this coin mined only 10475692 blocks.. So this transaction sent 3 year old?
3. Block, what block number of this transaction? Where Block Hash?


Dev.. What you want from livecoin? This exchange can't receive invalid transaction without valid txid.. Where is working block explorer that don't lie? How i see the problem not with livecoin.

The problem with you (devs) or sender (cryptopia). So if you or cryptopia don't have problems, please send me VALID txid for this transaction with link to correct working block explorer. I will check this txid in my node and block explorer.

Thanks.

sir livecoin FST treading problam?

Hello Saman02,

Please note, there is NO FST scam occurring here.  What seems to be the problem is what was mentioned above.  These types of problems are also indicative to Bitcoin and many Cryptocurrencies.  We have a case open with Livecoin on this and are waiting for them to get back to us with additional information.  Sending and receiving from Cryptopia to our personal FST wallets continue without issue.

Best

Fast

Thank you Stouse49,

Yes we believe you are also correct here, the exchange should -rescan or turn off and turn back on again their fastcoin clients/daemons to flush this out of their mempools.

We have a case open with Livecoin on this issue and we are waiting for them to get back to us and to also confirm that they have taken this action on their end.

Best

Fast

bump

Thank you Almightruler,

You are correct, we also feel it is a reporting error on the block explorer.  We have reached out to the owner of this Block Explorer and asked him/her to assist us in verifying this with us.

Best

Fast

FST scammmm?

Cryptopia and Livecoin, both of which might be using 0.8.7.2 software, need to -rescan or perhaps turn off and turn back on again their fastcoin clients/daemons.  This should wipe their mempools of this unconfirmed transaction.  They might need to adjust their database system to remove records that the transaction was sent or do something to return the balance back to the customer.

Unix time is expressed as the number of seconds since midnight UTC on January 1st 1970. So 1st Jan 1970 00:00 UTC is 0.

31st Dec 1969 18:00 would be 'unix 0', adjusted for timezone (UTC-6)

It's most likely a reporting error on the block explorer. I doubt any coin client would accept a transaction (or block) with a calculated timestamp from nearly 50 years ago. Or a timestamp value of 0.

Others have mentioned that this block explorer is unreliable.

for me too ... only I do not understand who wants to deceive me ...?

Timestamp: 31st Dec 1969?
To me it looks a cheat attempt.
 

http://fst.blockexp.info/tx/7bc9e159868a057cb5cd3cdfddcf78bf76aeb4b41450d24c9db8831c076bac51   
 is my FST how can I get it back?

Hello! already one year has passed, how my transaction can not up to me to walk. what do I do? there 85821.94807831 FST

Ok, thanks. I downloaded this version of the wallet. At me all was synchronized.

I agree.  Why is Livecoin.net using a block explorer to validate transactions?  The "gettransaction" RPC command will tell you or the exchange software how many confirmations that a transaction has.  Tracking confirmations is very important for exchanges as they all have different requirements for how many are needed before you can sell or transfer those coins.

The transaction in question is interesting, assuming anything about it is real.  It has 1165 inputs to add up to 134781 FST.  The size of the transaction from this block explorer is about 176,000 bytes.  This reminds me of the stuck transactions from Cryptsy which had rather large transaction sizes.  Transactions themselves do not have timestamps, but the date on the block explorer is Dec 1969 which is 0 in unix time.  This might be because this was in the mempool of the blockexplorer and it was never confirmed.  This transaction never would get into my mempool on 10.2.2 for reasons below.

We know from previous messages on this board that the different versions of fastcoin circulating have different rules for transaction sizes.  Cryptopia is using 0.8.7.2 (https://www.cryptopia.co.nz/CoinInfo/?coin=FST).  And from the source code:  https://github.com/fastcoinproject/fastcoin/blob/fastcoin-8.7.2/src/main.h

200,000 byte transaction sizes are valid, so the above transaction is valid on that basis.  The comment says 100KB, but that is incorrect (1 million divided by 2 and then by 2.5 is 200,000).

https://github.com/fastcoinproject/fastcoin/blob/10.2.2/src/main.h

And version 10.2.2 has 100,000 size limits.

In my experience, anything over 10,000 bytes took a long time to confirm and some were never confirmed.  From this I suspect the miners are using 10.2.2 or very large transaction sizes cannot be handled for other reasons.

This particular transaction getting stuck is not new, but it is rare as most people don't have thousands of small transactions in their wallets.