bs58 | Base58 encoding/decoding for Bitcoin | Cryptography library

You need your keys in a format that Node.js recognizes. KeyObject create*Key APIs recognize and the key is supported in - for Ed25519 keys that is, assuming Node.js >= 16.0.0:

• PEM/DER in SPKI for public keys
• PEM/DER in PKCS8 for private keys
• JWK for both public and private keys

Here's a snippet that uses DER.

Remove the line

As per React's documentation:

Don’t call Hooks inside loops, conditions, or nested functions. Instead, always use Hooks at the top level of your React function, before any early returns.

Currently, you're attempting to call a hook inside the onClick handler - AddUser is a custom hook since it also uses hooks and the better name for it should be useAddUser.

I suggest to make some improvements by returning a function from your custom hook that you can call to add a new user, e.g.:

Retrying is not a bad thing! In some situations, it's actually the preferred way to handle dropped transactions.

You may like to read through this cookbook entry about retrying transactions: https://solanacookbook.com/guides/retrying-transactions.html

Specifically, it explains how to implement some retry logic: https://solanacookbook.com/guides/retrying-transactions.html#customizing-rebroadcast-logic

And what retrying means specifically: https://solanacookbook.com/guides/retrying-transactions.html#when-to-re-sign-transactions

Thanks for providing a concrete example on this, you're very close! The encoding is absolutely the issue here -- the pubkey is correctly encoded in Python as bytes. That first byte of \x90, encoded as two hex values, is 144 in JS, and you can check that in Python with: int('90', 16) = 144.

So to verify your key, you can instead use the base58 package https://github.com/keis/base58 and do:

If you look in the API documentation for bs58::encode, you see that it returns a EncodeBuilder.

Looking at the documentation for that, you see that there is a with_check method but it has a note attached to it:

This is supported on crate feature check only.

Rust supports crates defining optional features - these features typically have extra dependancies that are not needed in all cases, so they are off by default.

You can enable the extra features in your Cargo.toml file, like this: