Add additional partial headers

[felixbrucker]

Purpose:

Expose farmer peer id, full harvester version, harvester capacity (raw/effective) and plot count when submitting a partial.

Current Behavior:

Currently only the full farmer version and harvester peer id are exposed

New Behavior:

Farmer and harvester peer id and full version, as well as harvester capacity and plot count are exposed.

Testing Notes:

Limitation: capacity and plot count are not scoped by plotnft yet, as those are not tracked separately right now in plot_sync_receivers. The current lookups are fast as its just a direct variable access, scoping per launcher id/contract address would require additional compute resources without a refactor of how plot_sync_receivers works right now.

• Depends on Pass full version in Handshake #15679

[emlowe]

Interestingly, RFC 6648 (https://www.rfc-editor.org/rfc/rfc6648) deprecates using X- as the beginning nomenclature for new parameters. Perhaps chia should be in the name somewhere - maybe chia-farmer-peer-id

[emlowe]

Some Internal discussion indicates that some of these would be contentious to send by default - I suggest creating a new CHIP to discuss those and they may need to be optional to send

The harvester version itself is likely not controversial - but some of the others eliciting some internal feedback

[felixbrucker]

some of these would be contentious to send by default - I suggest creating a new CHIP to discuss those and they may need to be optional to send

which ones exactly?

[danieljperry]

some of these would be contentious to send by default - I suggest creating a new CHIP to discuss those and they may need to be optional to send

which ones exactly?

Farmer peer ID. This might work well as an informational CHIP if there are other clients that could use it. I'm not familiar enough with the pooling protocols to say for sure, though.

[felixbrucker]

I don't see how that is contentious in any way, but sure i can create a chip for it

[felixbrucker]

The CHIP PR is available here: Chia-Network/chips#114

[github-actions]

This PR has been flagged as stale due to no activity for over 60 days. It will not be automatically closed, but it has been given a stale-pr label and should be manually reviewed by the relevant parties.

[almogdepaz]

lgtm

[BrandtH22]

Per the conversation in the chip, the inherent security issues with defaulting the additional headers to not be obfuscated, and the reduced version of the pr already adoption; this pr is being closed and not adopted into the chia codebase.