Remove gen_vault_signer_key for test #176
Open
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.
Is there any reason for default
Pubkey
ingen_vault_signer_key
?My use case:
I'm trying to process instructions in Rust code with real data from the network (1. accounts data received from validators, so they are real 2.
fuzz
is used because only this feature processspl_token
instructions instead of cross program invocations). Becausegen_vault_signer_key
produce defaultPubkey
I have a problem withSettleFunds
instruction, I need to pass vault signer as defaultPubkey
for successful validation from serum dex and at the same time need to pass correct vault signer with realPubkey
for successful validation from spl_token. Currently, I changedowner
pubkey for vault addresses but looks like a real in the key returned bygen_vault_signer_key
.