EVM Pubkey derivation script #1
Open
+61,024
−34,244
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix: bump echogarden to fix case sensitive issue
Improved Twitter Documentation
fix: sql command
fix: remove db adapters depencies from core and remove plugin-node from telegram
fix: remove postinstall script from plugin-coinbase
fix: postgres
fix: Token provider getHighestLiquidityPair
Add community stream notes for WDYGDTW 2
feat: add new pages
add codecov integration to CI workflow
Update ci.yaml
…nilpat/eliza into realitySpiral/coinbaseTrading
…nilpat/eliza into realitySpiral/coinbaseTrading
feat: improve browser service
added support for LlamaLocal's path outside plugin-node/dist
CS - adding better errors and readme.
feat: implement coinbase trading
fix: pnpm-lock.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A quick easy way to derive your EVM pubkey from the EVM_PRIVATE_KEY set in your .env file without needing to access the key generation system in the new TEE feature.
Relates to:
This is simply a super easy convenience PR to help devs move their agents into EVM testing much more quickly.
Risks
There's basically no risk to the PR. It's a super simple helper script that operates outside of the existing codebase and framework.
Background
As I went to setup the EVM integration for the Gods - I realized there wasn't an easy way to derive EVM public keys from the EVM private key. This also paves the way to simplifying the .env file requirements and thus simplifying the setup process.
Documentation changes needed?
It would be great to mention this in any "get started" content relating to EVM agents.
Set your private key in the .env
EVM_PRIVATE_KEYand runnode scripts/derive-keys.jsSet your public key
EVM_PUBLIC_KEYfrom the public key output in your consoleTesting
Can test by simply importing an
EVM_PRIVATE_KEYinto the .env file and bashingnode scripts/derive-keys.js