Open the-fool opened 1 month ago
The underlying solana-banks-server code doesn't check the signatures. But how are you serializing the transaction without the signatures being checked on the client side? Related: https://github.com/kevinheavey/solana-bankrun/pull/15
That answers that :)
I am just using @solana/web3.js
, like so:
const msg = new web3.TransactionMessage({
payerKey,
recentBlockhash,
instructions,
}).compileToV0Message()
const tx = new web3.VersionedTransaction(msg)
banksClient.processTransaction(tx)
It seems like
processTransaction
works when an account is supposed to be a signer, but there is no signature in the transaction. Is this the expected behavior? And is there any way to enforce signature checks?For example, say there is an Anchor accounts declaration:
If I submit a transaction with these two accounts, but no signature for the
other_signer
account, the transaction still executes successfully.