navidr-2026-q2-480h-c++

layout: fr
title: "navidr 480h monerod C++ development"
author: navidR
date: April 13, 2026
amount: 96
milestones:
  - name: 160 hours
    funds: 32
    done:
    status: unfinished
  - name: 160 hours
    funds: 32
    done:
    status: unfinished
  - name: 160 hours
    funds: 32
    done:
    status: unfinished
payouts:
  - date:
    amount:
  - date:
    amount:
  - date:
    amount:

What

I propose to work on Monero for 3 months, with the primary goal of strengthening Monero’s C++ / monerod development capacity during the FCMP++ transition period. My focus will be on the parts of the project where experienced C++ review and testing are currently most needed: reviewing and testing pull requests, helping with monerod-side integration work, assisting with stressnet testing, and helping with core issues and code which need careful analysis. This CCS is intentionally structured around high-priority project needs rather than one narrowly-scoped feature. There is a large amount of important C++ work, review work, testing work, and integration work that needs attention in parallel. My goal is to help move that work forward in a practical way. Planned areas of work include:

• Review and testing of Monero core PRs, especially consensus-sensitive, wallet, daemon, P2P, and performance-related changes
• FCMP++ / monerod integration support on the C++ side, helping review, test, debug, and improve the existing integration path needed to move from stressnet toward later deployment stages
• Stressnet-related testing and support work, including helping test, reproduce issues, and analyze failures or regressions as they come up
• General monerod / C++ maintenance work, including backlog review, issue investigation, bug fixing, and simplification work where appropriate
• Code quality work, including targeted testing, benchmarking where useful, documentation improvements, and cleanup when it helps ongoing development
• Coordination with active contributors so effort is spent on what is most needed rather than on work which is interesting but not currently on the critical path A few important clarifications:
• This CCS is not primarily about rewriting FCMP++ from Rust to C++
• My understanding is that the highest-priority need is helping Monero move FCMP++ forward by strengthening the existing monerod / C++ side, review capacity, testing, and integration work
• If implementation work arises during the CCS, I will do it, but I do not want to over-promise a single large deliverable whose exact scope depends on upstream progress and coordination with other contributors

Expected deliverables

During this CCS, I expect to provide:

• Ongoing review and testing of PRs in monero-project/monero
• Public milestone reports describing:
  • what I worked on
  • how much time I spent
  • what was completed
  • what remains in progress
  • priorities for the next period
• Concrete technical output in the form of reviews, tested feedback, issue investigation, patches, bug fixes, and testing / benchmarking results where applicable
• Help with stressnet testing and related debugging as needed
• The CCS is expected to be completed within a maximum period of four (4) months. In the event that the CCS is not completed within this timeframe, any remaining funds shall be returned to the Monero General Fund. The commencement date of the CCS shall be no later than thirty (30) days from the merge date of this CCS.

Milestones

Milestone 1

• Begin active review and testing of Monero core PRs
• Help with stressnet-related testing and issue analysis where useful
• Identify the highest-priority monerod / FCMP++ integration areas where I can contribute immediately

Milestone 2

• Continue review and testing work on high-priority or blocked PRs
• Continue helping with stressnet testing, debugging, and follow-up work
• Contribute implementation or investigation work where needed on monerod-side integration or other core C++ issues

Milestone 3

• Continue review, testing, debugging, and implementation support on the highest-priority Monero C++ work
• Focus on helping unblock remaining review / integration issues and improving confidence in ongoing work

Who

I am Navid Rahimi. Previous compiler engineer, switched to career on blockchains. Previous CCSs: !429 (merged) !438 (merged) !487 (merged) !526 (merged)

Funding

32 XMR per month x 3 months = 96 XMR

Schedule

40 hours per week x 12 weeks = 480 hours