Bitcoin: Getting “Public key is neither compressed or uncompressed” after trying to send with imported key

Troubleshooting Issue: “Public Key is Neither Compressed nor Uncompressed” after Importing Key

As a Bitcoin enthusiast, it is not uncommon to encounter issues when trying to import your old Bitcoin wallet keys into the bitWallet app. One such issue that has been reported by users is encountering issues with the “public key” being neither compressed nor uncompressed after import. This article aims to provide a step-by-step guide on how to resolve this issue and get your public key working properly.

Understanding Public Keys

In Bitcoin, the public key is used for signing and verifying transactions. When you create a new wallet, you generate a private key and an associated public key. The private key is used to sign transactions, while the public key can be shared publicly or used to receive payments from others.

Importing Old Keys into BitWallet

When importing your old keys into the bitWallet app for iOS, you should initially not have any issues. However, in some cases, you may encounter issues with the “public key” being neither compressed nor uncompressed after import.

Troubleshooting Steps

To resolve this issue, follow these steps:

  • Check your private key: Make sure your old private key is entered correctly in the bitWallet app. You can do this by going to Settings > Wallets & Keys and selecting the “Import” tab for the wallet containing your old keys.
  • Check compression status: Check whether your public key has been compressed or uncompressed. To do this, you can use tools like the openssl command line tool (e.g. openssl pkcs12 -in -out -nokeys, then openssl rsa -pubin -out ) to check the compression status of both the old private key and the imported public key.
  • Reimport key

    : Reimport your old keys into the bitWallet app, ensuring that all necessary options are selected for compression (if necessary). If you are still experiencing issues after reimporting, try removing and reimporting all keys from the bitWallet app.

  • Clear app cache and data: Clear the app cache and data for bitWallet to ensure it starts with a clean slate. This can help resolve any cache issues that may be causing the issue.

What to do next

If none of these troubleshooting steps resolve the issue, there may be other factors at play that need to be addressed. Some possible causes include:

  • Data corruption or loss during import
  • Incorrect key configuration in the bitWallet app
  • Network connectivity issues

To further diagnose the issue, you can try creating a new wallet with your old keys and importing it into the bitWallet app. If this resolves the issue, it is likely a matter of corrupt data or incorrect key configuration.

Conclusion

In conclusion, experiencing issues with the “public key” being neither compressed nor uncompressed after import is a common issue when using the bitWallet app for iOS. By following these troubleshooting steps and addressing the potential causes, you should be able to resolve this issue and get your public key working properly.

bridge pump dump