-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use plugin-evm #3380
Comments
Same problem here: Used the Metamask generated private key for my Ethereum account. Seems there needs to be conversion to happen. |
So, here is info from Gemini AI:
Hexadecimal (Private Key): This is the most common and fundamental format. It's a 64-character hexadecimal string representing the private key. Each character represents 4 bits of data, so 64 hex characters represent 256 bits (the size of an EVM private key). Example: 0x0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef (This is just a random example; never use this key). Example (Uncompressed): Kwb9JzM9mXjLg869p8cVeSnc9k4t9xUj2gYt9529999999999999 (This is a fictional example). Example: abandon ability able about above absent absorb abstract absurd abuse access accident ... (This is just a partial example; a real seed phrase would have 12, 15, 18, or 24 words). |
So what worked from me: I just added a 0x at the beginning of my private key, as I checked if was all hexa (from 0 to f). Bingo! worked! |
Describe the bug
I installed
plugin-evm
withpnpm install @elizaos/plugin-evm
,added values for these attributes in the
.env
file:EVM_PRIVATE_KEY=my-private-key
EVM_PROVIDER_URL=rpc-url
Added also in my character json file:
When I run
pnpm start --character="path/to/my/character.json
I get this error:invalid private key, expected hex or 32 bytes, got string
When I inspected the logs, I saw that only one part of my private key I pasted was used, not the whole value.
To Reproduce
Explained above
Expected behavior
I can run
plugin-evm
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: