Kaspa full-node reference implementation and related libraries in the Rust programming language
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 62%
Response Time: 7d
First Timer Success: 54%
kaspanet/rusty-kaspa has a recorded first-timer success rate of 53.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kaspanet/rusty-kaspa respond to incoming external pull requests in approximately 165.7 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 60.0 places kaspanet/rusty-kaspa in the A tier.
The external contributor pull request merge rate for kaspanet/rusty-kaspa is 62.2%, based on public PR activity from non-core contributors.
kaspanet/rusty-kaspa currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in kaspanet/rusty-kaspa.
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/kaspanet/rusty-kaspa?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~108 hours (78% approval). Large PRs (>500 lines) take ~795 hours (28% approval). Keep your diff compact for rapid review.
Post-Toccata, VirtualState::accepted_id_digests always holds exactly one element: the seq_commit hash (KIP-21). The Vec<Hash> shape is a leftover from pre-KIP-21, when it carried the tx digests for accepted_id_merkle_root computation. Proposed in the TODO left by #1083: Introduce a dedicated single-hash type for the field Its Serialize/Deserialize impl encodes as a one-element vector, so the on-disk and wire format stay byte-identical (pre-Toccata rows still decode through PreToccataVirtualState) The type makes the single-element invariant explicit and drops the Vec from the API Call sites that would simplify: consensus/src/model/stores/virtual_state.rs: the field, new, from_genesis consensus/src/pipeline/virtual_processor/processor.rs: construction via vec![compute_seq_commit(..)] (companion TODO there) and the accepted_id_digests[0] read when building the header
TRANSIENT_BYTE_TO_MASS_FACTOR has outlived it's purpose. Transient mass should be directly set and treated as a byte limit (1:1). This can be applied post hardfork as a non-consensus change. Effectively: Transient mass will change from 1,000,000 to 250,000 in the limit The TRANSIENT_BYTE_TO_MASS_FACTOR (current value is 4) is removed from the calculation
Is your feature request related to a problem? Please describe. When passing hostnames in --addpeer, the program stops with "invalid IP address syntax", this is an issue especially in cloud native environments. Describe the solution you'd like I'd like the program to resolves IP at runtime Describe alternatives you've considered Resolve IP as part of a pre-start step: peer_ip="$(getent ahostsv4 devnet-kaspad-0.devnet-kaspad.kaspa.svc.cluster.local | awk 'NR==1 { print $1 }')"
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 kaspanet/rusty-kaspa, 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 kaspanet/rusty-kaspa acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.2% were successfully merged into the primary branch.
kaspanet/rusty-kaspa has a recorded first-timer success rate of 53.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 days+. 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 60.0 places kaspanet/rusty-kaspa in the Welcoming tier.
The external pull request merge rate is 62.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kaspanet/rusty-kaspa currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kaspanet/rusty-kaspa 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.