Minor issue: Fingerprint of new user's key sent to inviter before verification

I have recently invited another user to Keybase, he had uploaded his existing public key while registering, but he did not verify it (by self-signing Keybase request).
As a result I received e-mail about registration of my invitee that contained firgerprint of his public key (and no notice that the key has not yet been verified).

The public key might have also been displayed on the website for some time (prior to verification), but it is possible that the key was displayed only to the user himself for the purpose of verification.

Several hours later Keybase.io website displayed that the new user has no key published. The public key was re-uploaded and successfully verified afterwards.

Start by tracing the invitee registration email and public-key verification flow described in the report, then reproduce the sequence with an uploaded but unsigned key. Check both the invitation email and the website state before verification; done means unverified keys are not presented as verified and the user receives an accurate status notice.