earl

Let me add a few use cases where this would greatly help the pool operator day-to-day: 1. `chia-harvester-version`: Very recently, a third-party harvester software was discovered to be not forming...

> Don't you get the IP address of the farmer when it contacts the pool - either in the originating source address or maybe X-Forwarded-For? We do, but that's usually...

> X-Forwarded-For should have the original internal IP address in most cases - it does for me (although in my case it is an IPv6 addy). At least this is...

> My concern here is that providing the farmer peer id, this proposal makes it harder for me as a farmer to protect my privacy. Not all farmers want to...

Thanks for clarifying, @fizpawiz. So a suggested way forward: - Send a "masked" farmer ID calculated as hash(launcher id | farmer peer id) instead of the plain farmer peer ID....

> I'm still confused why anyone wants the stats. The stats can be extremely useful in assisting farmers to analyze their farms. As a matter of fact, besides the obvious...

> I'd like to note that with [CHIP-0026](https://github.com/Chia-Network/chips/pull/100) once adopted, hitting the subscription limit will result in a rejection instead of silently failing. Thanks for bringing that up, that'll be...

@emlowe Thanks. I just force-pushed a signed version of my original commit to #174, just in case you need that: https://github.com/Chia-Network/chiavdf/pull/174/commits/5b9ee7b9c3dc7d02017bc77e6fc575591869a53d

> Are the FullBlock JSON you produce compatible with what chia-blockchain produces? Nope, not yet, at least not intentionally or verified. If there's interest in merging this, I'll look into...

Ok, I'll have a quick look into establishing structural compatibility with the Python JSON to get an idea how much work that'll be. I don't think a serde fork is...