Reference implementation of the Filecoin protocol, written in Go
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 67%
Response Time: 10h
First Timer Success: 55%
filecoin-project/lotus has a recorded first-timer success rate of 54.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in filecoin-project/lotus respond to incoming external pull requests in approximately 10.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 62.5 places filecoin-project/lotus in the A tier.
The external contributor pull request merge rate for filecoin-project/lotus is 67.0%, based on public PR activity from non-core contributors.
filecoin-project/lotus currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in filecoin-project/lotus. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/filecoin-project/lotus?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (84% approval). Large PRs (>500 lines) take ~50 hours (30% approval). Keep your diff compact for rapid review.
Write the skeleton for nv30. This is part of a series of tickets across multiple repos, as building up a network upgrade skeleton requires changes across: filecoin-project/ref-fvm#2347 filecoin-project/filecoin-ffi#590 filecoin-project/go-state-types#472 lotus (this ticket) How to create a network skeleton in Lotus is documented here: https://github.com/filecoin-project/lotus/blob/master/documentation/misc/Building_a_network_skeleton.md#lotus-checklist Done Criteria There is a network skeleton in Lotus, which bubbles up all the other dependencies, and allows one to run a 2k-network and see that it switches network version from nv29 to nv30. User/Customer Implementers
Checklist This is not a security-related bug/issue. If it is, please follow please follow the security policy. I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion. I am running the Latest release, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these. I did not make any code changes to lotus. Lotus component lotus daemon - chain sync lotus fvm/fevm - Lotus FVM and FEVM interactions lotus miner/worker - sealing lotus miner - proving(WindowPoSt/WinningPoSt) lotus JSON-RPC API lotus message management (mpool) Other Lotus Version lotus 1.36.2+mainnet+git.ce2a17c Repro Steps Run eth_call against various gas caps for a txn, some should be failing but are not Describe the Bug Lotus seems to ignore the gas cap in eth_call Context: It just took me 5 tries to swap axlUSDC from Filecoin to Base on Squid Router, and I had to 6x the gas limit manua
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to filecoin-project/lotus, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of filecoin-project/lotus acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.0% were successfully merged into the primary branch.
filecoin-project/lotus has a recorded first-timer success rate of 54.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 62.5 places filecoin-project/lotus in the Welcoming tier.
The external pull request merge rate is 67.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, filecoin-project/lotus currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for filecoin-project/lotus are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.