Quote from: miningfield on May 09, 2017, 10:53:24 AM

Quote from: psionin on May 09, 2017, 05:38:37 AM

Quote from: miningfield on May 08, 2017, 11:16:21 PM

Is everything OK with the blockchain?

Block Explorer shows the last found block has a TimeStamp of "Thu, 01 Jan 1970 00:00:00 GMT"

Blocks are not beeing found.

Anyway, the wallet was acting strange on the server so i put the Pool Offline.

As soon as this issue is fixed i'll put the Pool back online

Hey, thanks for writing here. I've also noticed this odd transaction, perhaps it's some type of exploit - http://smartchain.cc/tx/a6d85e1ec17873f90dfe5e8270cfe90a2f5f70cb493e7161b82f415aad8c39bb

Nothing has changed in a while as far as the source code is concerned, and I have seen this before too, about a year ago, so there shouldn't be anything of critical concern. If there was a way to spend such malformed output, it must have been done already, but I don't think there is, because the tx is not part of a block. It's just a kind of spam. I have put this on my list of issues to investigate further.

I have also noticed other mining issues, however. For example, the pool at smc.e-pool.net:8960/static has been generating shares that were 97% "dead on arrival", but this seems to be a pool issue because at the same time (2 days ago) the Miningfield pool was working fine.

The main issue with SMC mining has been that a large amount of hash rate switches into high gear and then disappears once the difficulty has been raised. (Blocks were probably not being found as usual because of the increased difficulty.) This is a well known type of vulnerability, but one that should not be occurring with a sufficient amount of dedicated hash power always available to the network. I have been looking for a Baikal miner in order to resolve this, while renting X11 rigs to mitigate the sync delays that have been happening in the meantime.

I think it should be okay to ignore the invalid tx and bring the pool back online.

Pool is back Online

http://smc.miningfield.com

yesterday the wallet was generating a lot more load on the server, and a simple "getinfo" would take 15sec to get the output, a wallet restart would not solve the problem.

I don't know if it was some kind of attack, i've been having the wallet running for 2 hour now, and had no performance issue so far, so i'm putting the Pool Online.

Block explorer still shows that strange block as the last one, so i don't know if there's a bigger issue behind this.

Also Network Speed seems to be stuck.

Let's wait for another block.

New Blocks have been found.

Everything OK on the Pool, and block explorer is following blocks.

I would say it's back to normal.