45 $XMR Sought for Tor and I2P Work
Developer jpk68 has asked the Monero ($XMR) community to fund three months of full-time work on the project’s wallet software and anonymity networks, posting the plan to its Community Crowdfunding System (CCS) page on 2026-07-23. The CCS is Monero’s donation-funded development model: a developer publishes a work plan and a budget, and users decide with their contributions. The proposal sets a target of 45 $XMR and commits jpk68 to 40 hours of work per week across the period. At the time of our check, the page showed 42 contributors and 31.04 $XMR pledged, which the CCS displays as roughly 69% of the goal. The Monero ($XMR) price slipped about 3.4% over the past 24 hours, although the pledge is counted in $XMR, so the remaining shortfall of roughly 14 $XMR is measured in the coin itself. The proposed work centers on privacy plumbing. jpk68 plans to begin Tor control protocol support in monerod, the node daemon that runs the network, and to automate the setup of onion services, the Tor-based endpoints that accept connections without exposing a server’s location. A second track would examine folding an I2P SAM implementation into the core wallet code, so users of remote nodes, third-party servers that light clients query instead of running a full node locally and that can reveal which wallet address is being served, get a native route through that anonymity network. Interface work is on the agenda as well: usability and feature improvements to the Monero ($XMR) GUI that reach everyday holders, including those who keep coins in a cold wallet, plus continuous maintenance and testing of the anonymous network code, review of code changes submitted by other developers, and general bug fixes. jpk68 frames the Tor and I2P SAM items as planning-stage tasks, not scheduled feature releases. Both extend an anonymity line the project has pursued across efforts from the Kovri project onward.
Behind the pledge sits a defined delivery structure. The total request of 45 $XMR divides into three monthly milestones of 15 $XMR each, giving the core team fixed checkpoints before any payment moves. Each milestone payment is set at 15 $XMR, so the payout schedule is fixed even if the donation total moves. The proposal also asks that leftover donations from a closed I2P SAM bounty be applied to this work where possible, which would reduce the fresh Monero ($XMR) the community needs to provide. Tasks left incomplete under existing proposals are excluded from these hours, the developer writes, and will be finished separately, so the new budget funds new scope only. The supporting record offered in the proposal is jpk68’s own: about eight months of involvement in Monero development and roughly 50 merged pull requests, figures presented without third-party verification. The CCS model that would carry the plan forward works in stages. A developer first publishes the work plan and the required funding, and the community debates the proposal’s strengths and weaknesses; fundraising opens once the core team judges that loose consensus has been reached. From that point the core team acts as escrow, releasing funds as milestones are completed rather than up front. That structure caps a donor’s exposure: a contribution sits with the escrow until work is delivered, and each milestone payment follows completed output. The CCS guidance carries one more caveat for anyone reading the current page: the contributor count and the pledged amount measure donation participation, not the community’s approval rating, and the displayed totals are point-in-time values that change as new contributions arrive. The page has been open since late July, and the pledge has accumulated over roughly three months, leaving the final third of the 45 $XMR target still open.
