[PLACEHOLDER] Define an API to do various chain-specific validation
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- api, backend-api-design
Research direction
Start by reading the new multichain send flow and the temporary API exposed through onClientRequest. Determine the chain-specific validations the client must request from the snap and define the stable API boundary; done means the API supports those validation requests without relying on the temporary experiment.
Written by the indexing model from the issue text.
Description
The new multichain send flow will need to do request validation of various things chain-specific to the snap. Create an API that allows the client to request these validations from the snap.
(The new networks team is experimenting a temporary API through onClientRequest in the interest of time. They will come back with a SIP once they have something "stable" enough).
- Dominant language
- TypeScript
- Stars
- 853
- Forks
- 662
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 8
Contributor guide
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.
More from MetaMask/snaps
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
snaps-refined-backlog
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
snaps-refined-backlog
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
snaps-refined-backlog
Difficulty 4/5 3-5 days Newbie friendliness 15/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·