All of a sudden log is full of nothing but the following errors. System was running fine up till now. Was happily forging. Can someone help please!

2017-08-27 16:24:16 [pool-4-thread-4] DEBUG c.heatledger.BlockchainProcessorImpl - Downloaded block from 163.172.182.157 not accepted
com.heatledger.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
        at com.heatledger.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:757)
        at com.heatledger.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:400)
        at com.heatledger.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:237)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
2017-08-27 16:24:16 [pool-4-thread-4] DEBUG com.heatledger.peer.PeerImpl - Blacklisting 163.172.182.157 because of: com.heatledger.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
com.heatledger.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
        at com.heatledger.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:757)
        at com.heatledger.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:400)
        at com.heatledger.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:237)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Missing all of my balances and outstanding orders (BTC, HEAT) 😮 in C-CEX. Any idea, what what might have happened? Anybody know, does their support actually respond to created tickets, or are they currently fleeing to the Caribbean waters?

In the node list at https://heatwallet.com/nodes.cgi what does "State: 0" imply?  Is there an incoming port that needs to be forwarded to the server?

Ok no, it wouldn't work if the buy order can't be filled in the first place and someone could spam the chain with unfillable orders with a dummy token.

I am adapting my FIMK pool code so that I am ready once the HEAT leasing goes active.  In updating my code, I found a FIMK API call that was not recreated in the HEAT API.  I have looked for similar functions that accomplish the same goal, but haven't found a new set of function calls that accomplish the same thing as the FIMK API does.

FIMK API Function:  getAccountLessors

This function returns that list of lessors to an account at a specific block height.  This is useful for determining how to divide up the block reward. 

As the leasing functionality is yet to be active, this function may still be added to the API.  Can anyone confirm this is being added?