Funding
Monero Community Backs 45 XMR Proposal for Three Months of Core Development
By News Desk ·
Key takeaways
- Monero developer jpk68 requested 45 XMR for three months of full-time work on privacy infrastructure, wallet software and core improvements.
- The Community Crowdfunding System proposal raised 31.04 XMR from 42 contributors as of October 26, leaving 13.96 XMR to reach its target.
- Planned work includes adding Tor Control protocol support to monerod and investigating whether the existing I2P SAM implementation can be integrated into Monero's core wallet code.
Monero developer jpk68 has requested 45 XMR for three months of full-time work on the network's privacy infrastructure, wallet software and core improvements, with the Community Crowdfunding System proposal raising 31.04 XMR from 42 contributors as of October 26. crypto.news reported that the developer is seeking support for 40 hours of work per week over three months, leaving 13.96 XMR to reach the funding target.
Monero's 45 XMR Proposal and Planned Work
Monero's official X account highlighted the proposal on October 26, directing community members to the funding page after jpk68 publicly requested support on October 23. The developer intends to continue improving Monero's compatibility with anonymity networks, particularly Tor and I2P, while working on wallet usability, software maintenance and code reviews.
One planned change involves adding support for the Tor Control protocol to monerod, Monero's core daemon software, allowing the software to configure onion services automatically and reducing manual setup. Another priority is investigating whether the existing I2P SAM implementation can be integrated into Monero's core wallet code to support connections through remote nodes.
Jpk68 has previously worked on bringing I2P support to P2Pool and adding I2P SAM functionality to monerod and the Monero graphical wallet, which the developer said had remained unfinished for seven years before contributing to its implementation. Previous contributions include helping move the Monero GUI to Qt6, fixing software correctness issues, improving build performance and updating documentation, with approximately 50 merged pull requests during the first eight months of contributing to Monero.
The new proposal includes continued GUI improvements, anonymity network testing, reviewing other developers' code and fixing bugs discovered during routine development. Jpk68 specified that unfinished obligations from an existing crowdfunding proposal would be completed separately and would not count toward the working hours requested in the new funding round.
Monero's Crowdfunding Records and Prior Funding
According to akta.pro company records, Monero has one funding round on record, a 2015-09 secondary market. The same records list a 2026-04 partnership with THORChain, which completed Monero integration in early April 2026, enabling native cross-chain liquidity for XMR through decentralized swaps.
| Record | Date | Detail |
|---|---|---|
| Funding round | 2015-09 | Secondary market |
| Partnership | 2026-04 | THORChain completed Monero integration |
| Product launch | 2026-05 | FCMP++ beta upgrade launched May 6, 2026 |
Monero's Development Timeline Before the Proposal
Monero released a new beta stressnet version ahead of FCMP++ and CARROT upgrades scheduled for October 5, with the team urging community testing and issue reporting, U.Today reported in September 2026. FCMP++ expands privacy by allowing inputs to prove spending from the entire eligible output set rather than a small ring.
AInvest reported in September 2026 that Monero enforces mandatory privacy via ring signatures and stealth addresses, leading to delistings from major exchanges including Binance and Kraken, while community crowdfunding sustains development. CoinMarketCap reported in September 2026 that Monero traded around $512 to $524, with market cap near $9.4 billion to $9.9 billion, as privacy-coin demand gained momentum.
Monero's Next Steps on the Proposal
The official CCS dashboard continues to classify jpk68's proposal as requiring funding, with the developer requesting community contributions before the full 45 XMR target is met. Jpk68 has requested that any remaining donations from a completed I2P SAM bounty be considered for the new proposal, arguing that the planned work involves similar development responsibilities, though the request does not establish whether those funds will be transferred.