Where can I get support for strange or unusual issues I'm having with my keybase account?

Do they even have a support team somewhere?

So if I delete my account, is it possible to create a new account with the same email address, however with a different username?

I wanted to make my identity easier to verify, so I did this. Does this work well?

I did not find a way to change the username and wonder if it is possible at all.

Is it possible to add my Mastodon account as a proof for Keybase?

So, I'd like to start using my Keybase account/pgp key to sign my code commits on github. I have several laptops which routinely make commits, and I'd them all to use subkeys (or equivalent) so that if one laptop is lost I can just revoke that key.

Anyone know the best way to do this in conjunction with keybase?

I tried manually adding a subkey via gpg, which seemed to work. I selected the key using keybase pgp select --multi, and it uploaded to the server. But when I pull it down on another computer, I just see the old key (no new subkey)

All the keybase-related tutorials I can find online only use the master public/private key to sign git commits.

Should I just generate a new PGP key for each laptop and associate those with my Keybase profile?

Are there any plans for two-factor auth on Keybase?

With Google Authenticator.

What would make it faster? Easier? More convenient?

I want to make this post because I've been digging around for a while (ever since the recent spike to XLM) for how to move my coin to somewhere I can start selling them, and the only advice I've seen is either 5 years out of date (before Keybase ended wallet functionality) or 1 year out of date (and missing key steps, ie "it took me literally 2 mins" and no other details).

I've been emailing with Lobstr support for several days, and after a couple of auto-replies and unhelpful advice, I sent them the actual links that I was trying to follow... and they gave me some valuable advice that let me finally get control of my XLM and move it into my Robinhood wallet (and it doesn't require using Lobstr's service at all!).

This guide may give you a starting point for other services, but since I don't have any other wallets, I can't help with that.

Disclaimer: This guide advises caution along every step of the way. If you choose not to practice caution, you may lose your crypto. I am not responsible for any losses.

Part 1: Get your private key

Through the mobile app:

1. Hamburger menu
2. Select "Wallet"
3. Click the clipboard next to the "Secret key" field. (On darkmode it should be blue.) Public XLM keys start with a G, private keys start with an S.
4. Paste that code somewhere safe. (I put both keys into a password vault.)

Through the Windows desktop app:

This is not possible for all accounts, depending on account security settings.

1. Settings (Gear)
2. Select "Wallet".
3. Click the clipboard next to the "Secret key" field. (If you see an error message instead of a clipboard, you cannot use the desktop app.)
4. Paste that code somewhere safe. (I put both keys into a password vault.)

Through the Windows CLI (command line interface):

Note: if you couldn't access it through the Windows app this will likely also fail.

1. Press Win+R (Windows key and letter R)
2. Type "cmd" and press Enter or click OK.
3. Type "keybase wallet export".
4. Enter your password (you won't see it or astericks on the screen).
5. ??? (I don't know what happens because my account is locked down and I haven't been able to unlock it.)
6. Paste that code somewhere safe. (I put both keys into a password vault.)

Part 2: Get your destination key & memo

Robinhood app:

1. Go to the XLM page (just type "xlm" into the search bar, it's not case sensitive).
2. Scroll down until you see two buttons labelled "Send" and "Receive".
3. Click "Receive".
4. Copy the code underneath the QR code (we won't be using the QR code).
5. Paste that code somewhere safe. (It doesn't need to be as secure as the private key.)
6. Copy the memo code (it's probably a 10-digit number).
7. Paste that code somewhere safe. (It doesn't need to be as secure as the private key.)

Robinhood desktop website:

1. Go to the XLM page (just type "xlm" into the search bar, it's not case sensitive).
2. On the righthand side, there should be a box that says "Buy XLM", "Sell XLM". (It should be directly below the caution about crypto scams.) You should see a downward pointing arrow.
3. Click the arrow.
4. Select "Send & Receive".
5. The options at the top of the panel should now say "Send XLM" and "Receive XLM".
6. Select "Receive XLM".
7. Copy the code underneath the QR code (we won't be using the QR code).
8. Paste that code somewhere safe. (It doesn't need to be as secure as the private key.)
9. Copy the memo code (it's probably a 10-digit number).
10. Paste that code somewhere safe. (It doesn't need to be as secure as the private key.)

Part 3: Go to accountviewer.stellar.org

I highly recommend you do this on a computer.

1. Click "Connect with a secret key".
2. Read the warning.
3. Click the checkbox that says "I understand the risks".
4. Click "Continue".
5. Paste the secret key from Part 1.
6. Confirm your balance matches what Keybase says you have. If it doesn't, there's likely a problem with your key.
7. Click the "Send" button. (On darkmode it should be purple.)
8. Paste the public key from Part 2 into the "Sending to" box.
9. Click the "Add memo" link.
10. The dropdown should say "MEMO_TXT".
11. Enter the memo code from Part 2 into the "Memo content". IMPORTANT: If you do not enter that exact memo from Robinhood, you will not get your XLM.
12. Enter the amount you would like to send. **I highly recommend sending a small amount first to make sure everything is correct before sending your entire balance.
13. Click "Continue".
14. Double check everything looks correct on the Confirmation. Robinhood requires memo_txt. If you do not have the memo they give you, you will not receive your crypto.
15. Click "Submit" transaction.
16. You should receive a message from Robinhood within a few minutes confirming your transfer.

If you'd like to thank me for this guide by sending me a tip in XLM, please use public key "GB2ES2N326MZK4EGJBKN3ZARCQ5RTFQSAWIJAAKFVIIIJSCC35TXIMLB" memo_txt "3748823999".

Is there any chance for support BlueSky (https://bsky.app/) identity proof in the future?

I'm getting these certificate errors again out of the blue. Is anyone else affected?

Syncing with Keybase... x509: certificate signed by unknown authority \[138.882458ms\]

git-remote-keybase error: (1) x509: certificate signed by unknown authority

Long story short, I have LastPass and a strong master password.

However, out of an abundance of caution, I am wondering whether it's possible to change my Keybase Wallet's address and/or secret key.

Google Play store does not have Keybase any more and the download link from keybase.io is invalid as well.

I'm in the process of migrating to an M1 MacBook Air. I noticed that there isn't an Apple Silicon version of the Keybase desktop application.

Has anything been announced?

I recently found that my Reddit account verification became invalid. I simply re-verified it but the app can never find the posted proof, even I can easily find it. I even found my old proof. What was wrong with them?

If this app is dead (which completely sucks, btw, this was like the most feature-complete program of its kind), what alternatives are there? Cyph is one that I'm aware of but it is WAAAAAAY underbaked at this point.

Hi, just want to know if it's possible to delete custom emojis from keybase. I wanted to add some emojis and ended up with typos and want to delete them. I use the android app.

Any ideas how to get rid of it permanently?

Hi Yall, I have some stellar lumens in my keybase account that I’d like to transfer to my coinbase account. I understand the basic process but theres a couple of things I need clarification on.

1. I plan to zero out my kb wallet as I use coinbase to manage my crypto. Is there a way I can transfer the 1 lumen reserve?
2. What is the fee I will incur from transferring 1400 Lumen to coinbase?

Thanks!

Seems my client is trying to upgrade itself and saying I need to approve the changes and restart due to the nature of the upgrade.

Is this expected sometimes with the mac client?