Showing people how to verify a proof

The proofs are very nice. I appreciate the claim language and also the careful avoidance of any assertion other than exactly what the demonstration of the claim represents, and no more.

What I think is missing, is any explanation for how others can verify the demonstration.

Of course, at the moment, that means being able to verify the ASCII-armored signed version of the JSON claim data. I would think that, no matter how keybase.io evolves, such geek-level verification would remain an option.

In the meantime, it would be nice to have the CLI/GnuPG means of verification explained, along with a way to make the ASCII-armored messages viewable. There might even be something about that in the boilerplate of the proof statements themselves.

I think this is important for putting teeth into the idea that the keybase.io profiles are publicly auditable.

Start with the issue's description of the ASCII-armored signed JSON claim data and the requested CLI/GnuPG verification flow. Document how users can verify the signed claims and make the armored messages viewable; the work is done when these steps are understandable to someone auditing a proof.

Written by the indexing model from the issue text.