[solana] Solana tests 2 #1255
[solana] Solana tests 2 #1255
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
| .iter() | ||
| .map(|x| libsecp256k1::sign(&digest, &x)) | ||
| .collect(); | ||
| let wormhole_signatures: Vec<wormhole_sdk::vaa::Signature> = signatures |
There was a problem hiding this comment.
Adding actual signatures to the common sdk
|
|
||
| let digest = libsecp256k1Message::parse_slice(&body.digest().unwrap().secp256k_hash).unwrap(); | ||
|
|
||
| let signatures: Vec<(Signature, RecoveryId)> = guardians[0..NUM_SIGNATURES] |
There was a problem hiding this comment.
maybe the number of signatures should be an argument to the function
There was a problem hiding this comment.
also do you want it to be the case that it's always the first N guardians who signed? are there possible tests where you want a random subset of guardians or something?
I would think about the range of configurability you need downstream and then try to build that in to the test methods here.
Another similar question would be whether you need the ability to define & work with different guardian sets in the tests. In that case, you may want to make the signing guardian keys an argument to this function.
There was a problem hiding this comment.
Ok so I switched to having random subsets of guardians. I don't think I need more configurability for now.
target_chains/solana/programs/pyth-solana-receiver/tests/common/mod.rs
Outdated
Show resolved
Hide resolved
The goal of this PR is to expand the testing coverage to
post_updates_atomicFor this we add a way to created signed VAAs to
pythnet_sdk/test-utils. We also simulate the guardian set account insetup_pyth_receiver.