|
yes, sorry if that wasn't clear. What I'm saying is that we'll have them documented very shortly. It's a priority for us, which I believe will address the OP's issue. We'll have documentation on: - what needs to be in the signed statement - how to hash the statement for safety on the platform you're posting, if necessary (twitter: yes, github: no, DNS TXT: yes, web domains: no, etc.) - how to tell Keybase about the statement (API call) - how to post the statement on Keybase (API call; this is needed in the scenario where it's hashed, twitter style) These will all be proof specific, which is necessary for reasons you can imagine. Character encodings allowed, where proofs go, what length they can be, etc., what goes into a proof (username?), etc., are all platform specific. But the goal is that someone can do this with software of their choice. |