NV29 Tracking
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- rust
- Domain
- blockchain
Research direction
Start by locating the NV29 sub-issues represented in the preparation, testing, and upgrade dependency graph. Read the skeleton, fil-actor-states, ref-fvm, network-testing, and upgrade issues first; done means coordinating their dependencies, completing the calibration and mainnet upgrades, and publishing both announcement posts.
Written by the indexing model from the issue text.
Description
Tracking issue for the NV29 network upgrade
Tasks
(in the sub-issues)
Communication
- [NV29] Announcement discussion post (calibnet)
- [NV29] Announcement discussion post (mainnet)
After each post, link it to the #fil-forest-announcements channel in the Filecoin Slack and re-share with critical stakeholders, e.g., ChainSafe Infra team.
Dependency graph
Some work can be parallelized, some not.
graph TD
subgraph Prep["Preparation"]
A["[NV29] Skeleton with migration"]
B["[NV29] fil-actor-states update & release"]
C["[NV29] ref-fvm Update"]
end
subgraph Testing["Testing"]
G["[NV29] 2k network testing"]
J["[NV29] Butterflynet testing"]
end
subgraph Upgrades["Upgrades"]
H["[NV29] Calibration network upgrade"]
I["[NV29] Mainnet upgrade"]
end
%% Dependencies
B --> G
A --> G
G --> H
H --> I
classDef done fill:#008000
- Dominant language
- Rust
- Stars
- 700
- Forks
- 201
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 65
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 ChainSafe/forest
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Bug
Difficulty 3/5 1-2 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
[automated] `cargo deny check advisories` failure @ 20/11/26 00:01Possibly taken @akaladarshi claimed this today. OpenBug
Difficulty 1/5 Under an hour Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
FIP-0119 implementation in `builtin-actors`Possibly taken @LesnyRumcajs claimed this 2 days ago. OpenType: Task
ChainSafe/forest#7886 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in ChainSafe/forest
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
app-request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
flatpark/flatpark#1423 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
area:image documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day