Allow peers to update their own public key

[aquarat]

A bit like Keybase, would it be reasonable for peers to update their own public keys on remote peers?

This carries potential risks, but also, if the private key has been compromised you can't trust it anyway.

[bbenligiray]

I don't see a security issue with it necessarily, but having to run an instance with the old key in parallel until every one of your peers receive your update request may get annoying in practice.

The way I envision this being implemented is you would send a report that would land in incoming/aaron/.requests/public-key-update.json that reads

{ "newPublicKey": "0x1234abcd..." }

Your peers would run (manually or periodically) a helper-like tool that fulfills un-ACK'ed requests and write ACK responses in outgoing/aaron/.responses/ (the original request JSON + additional data generated by the fulfillment of the request). hinter-core already handles peer public key updates by restarting, so no hinter-core change would be needed.

The general idea is that a P2P file sharing protocol can be used to implement arbitrary protocols on top (see #18 for example) in an "everything is a file" manner, and this allows the hinter-core to remain minimal.

[bbenligiray]

I think this feature doesn't justify the implementation of that entire new workflow of detecting requests and sending responses, but if we can come up with a few other useful features that depend on the same pattern, this may be worth bundling with them.