-
Notifications
You must be signed in to change notification settings - Fork 300
feat(lazer): add utils for adding and checking ed25519 signers to solana contract #2788
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 8 Skipped Deployments
|
import yargs from "yargs/yargs"; | ||
import { readFileSync } from "fs"; | ||
import NodeWallet from "@coral-xyz/anchor/dist/cjs/nodewallet"; | ||
import { createEd25519Instruction } from "@pythnetwork/pyth-lazer-sdk"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually can you move this function to @pythnetwork/pyth-lazer-solana-contract
. It makes sense to be here and we want to remove it from js-sdk to remove the solana dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well that's a bigger lift that we need to work on sometime later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed solana deps from @pythnetwork/pyth-lazer-sdk
and moved the code to ``@pythnetwork/pyth-lazer-solana-contract. Preparing
@pythnetwork/pyth-lazer-solana-contract` for publishing is tricky, so I'll leave it for later.
a26104a
to
3b50457
Compare
673a756
to
fc0550b
Compare
Summary
Add utils for dealing with ed25519 signers
Rationale
I wrote this to update signers on solana devnet and testnet.
How has this been tested?