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 sign
Search options answers only
not deleted
user 1202
1
vote
Cross-program invocation with unauthorized signer or writable account when using PDA with seeds
As far as I know, this is how PDAs are specified in the Rust program and derived in the client.
Rust:
..
seeds = [authority.key().as_ref(), "instructor".as_bytes().as_ref()]
..
Js/Ts:
const instructo …
- 3,944