Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with anchor-client
Search options not deleted
user 529
2
votes
2
answers
192
views
What is the commonly accepted way to test using multiple users (signers) when testing anchor... [closed]
I was following along in this tutorial and found this user's approach. Is there a better way to do this?
- 438
2
votes
What is the commonly accepted way to test using multiple users (signers) when testing anchor...
So it looks like @anon.sol was correct. I think the original difficulty was in dealing with passing in PDA accounts to transactions before they were created. Regardless, using anchor.web3.Keypair.gene …
- 438
1
vote
1
answer
126
views
What is the more up to date way of waiting for a transaction?
When the following code is used during testing, I get the following warning:
[tsserver 6387] [I] The signature '(strategy: string, commitment?: Commitment): Promise<RpcResponseAndContext<SignatureResu …
- 438