John Doering

By merging the NeoScrypt code and scheduling a hard fork with difficulty reset.

No address for generate transactions is a known issue for v0.6 wallets. It will be solved by a scheduled code base upgrade.

phoenixcoind listtransactions

Have you provided a specific coin base to the miner? If so, look there. The daemon only monitors its wallet.dat addresses including reserved.

It works for me. If the miner shows a block solving share, it must be because the daemon has told so. Look at the daemon's logs.

If there was a valid PoW found and sent to the daemon through RPC submitblock, a text "GBT proof-of-work found" with the coin base details had to be present in...

I cannot tell why their wallet has been unable to generate a new address without additional information. Maybe that's an overload issue. Try again later.

I'm not surprised. The wallet may use CPUminer which they have blacklisted for years.

How am I supposed to fight those false positives? They flag whatever they like for no real reason.

Might not be false? The binaries are hosted by GitHub. No one except me has upload rights. I don't do trojans. By the way, most of those ignorant AVs report...