Who decides when a project moves from ‘Ideas’ to ‘Funding Required’?
Which ‘Completed Task’ had the highest budget? What was the USD value (at the time, hint: read the proposal) and how many contributors were there?
RandomX Audits - $118,000 – 40 Contributors
- What’s the current USD value of all ‘Work in Progress’?
3082 Monero = $170,781.94015
- Choose one project from ‘Work in Progress’ and write a short summary of the work being done and how it supports the Monero ecosystem.
Broadcast Transactions over Tor Hidden Service – Add support to Monero daemon for broadcasting new transactions received over RPC to privacy preserving p2p connections to conceal origin IP. This proposal will use Tor hidden services, but the implementation will be written such that additional anonymity networks (Kovri?) can be added in the future.
Milestone 1 – Socks v4a - Provide a sock 4a client implementation. A standard library is less desirable - Tor has some extensions for DNS lookup that will be useful in the future. The delivery for this milestone will not be the ability to force all connections to a specific proxy (that is possibly left for a future FFS).
Milestone 2 – Timing Analysis Mitigations - A well-known weakness of Tor is the lack of delay in data transmits. This has the side effect of leaking the timing of data transmits through the Tor network, and sometimes the size of a message being sent (if the link is often idle). This timing issue can result in the leaking of transaction origin purely by watching the timing and volume of traffic being sent over Tor. This is particularly problematic with Monero having a lower transaction volume than Bitcoin.
Milestone 3 – Tor Hidden Service Seed Nodes - This will be similar to the hard-coded seed/bootstrap nodes used for connecting to the Monero network for this first time. These will most likely not be operated by me. This will allow --anonymizing-proxy to work without specifying a Tor --add-peer.