Memo: Rescue Function
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the issue body and review the linked Discord and Twitter discussions. The issue is explicitly a draft DIP memo with insufficient information, so first determine the intended rescue function and proposal requirements. Done means producing a sufficiently complete DIP for later use.
Written by the indexing model from the issue text.
Description
This issue is a draft DIP memo and will be used to create a DIP later, although it is not accompanied by sufficient information.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 dev-protocol/DIPs
-
priority - high tokenomics
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#76 · 4 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
dev-protocol/DIPs#61 · 2 reactions ·
-
layers
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#52 · 2 comments · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
dev-protocol/DIPs#48 · 13 comments ·
-
core layers usability
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#47 · 3 comments ·
All issues in dev-protocol/DIPs
Similar issues
-
feature
Difficulty 1/5 Under an hour Newbie friendliness 72/100
vercel-labs/skills#2370 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 3 days
-
bug developer portal
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
discord/discord-api-docs#8645 ·
Maintainers usually reply within 1 day
-
Перевод устарел
Difficulty 1/5 1-3 hours Newbie friendliness 88/100