cowprotocol / cowprotocol/solana-programs
What to do for extra accounts in instructions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 1
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 32
Description
(From this comment.)
For consistency and debugging reason, we want all instructions to enforce the exact number of accounts they take and reject instructions that have more, unused accounts.
On the other hand, there might be cases where it makes sense to add extra accounts to the instruction, for example if some specific token operation needed to specify some other account. We want to investigate if this is something that's actually needed in practice.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked discussion in pull request #38 and trace the instruction account handling it refers to. Determine whether real token operations require extra accounts, then document a clear decision and the account-count behavior that should apply to all instructions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100