Quote from: TheStuhlman on April 16, 2017, 12:16:07 AM

Quote from: SwedishBitMiner on April 15, 2017, 08:40:25 PM

Quote from: adorid on April 15, 2017, 05:35:01 PM

So we are back on invalid transaction problem. I think not only my pool stopped to accept transactions but notepool too. So i just can say, dev plz fix this annoying problem.

20:33:20.341922 INFO Block <2736a36a32b7181d3be099850aa00401292b85ed8e7dd39340184cafb85ca349> has at least one invalid transaction:
20:33:32.731710 INFO Block <9886572d03d030b6321e744394bbb117fbf5097483da5e31458e5188dd3dbc4b> can't contain transaction because it has invalid version
20:33:32.760333 INFO Block <9886572d03d030b6321e744394bbb117fbf5097483da5e31458e5188dd3dbc4b> has at least one invalid transaction:

at moment i stopped pool and hope that miners have configured the alternative pool to not waste hash power.
I will try to resync wallet...

Yes please fix this problem dev... It is the exactly same problem on notepool.pw.

I spoke with the dev on slack and explained the problem. He is working on a solution.
This problem is a real turn off. Seems someone is sending a TX from another cryptonote wallet,
or running another cryptonote wallet on the same port causing cross chain spam.

not solved yet?

It seems still stuck.