[MAGIC] vtnerd Monero dev work for Q1/Q2 has been fully funded!

Thank you to all donors!

The MAGIC Monero Fund's campaign to raise 226 XMR (28,800 USD) for three months of vtnerd (Lee Clagett) development work has succeeded.

vtnerd will work on Monero and Monero Light Wallet Server (LWS). The LWS increases Monero's capacity for more users and transactions. LWS will be even more important when Seraphis (next generation Monero transactions) is implemented because Seraphis will improve the user privacy and speed of light wallet servers.

Here are the full details of vtnerd's proposed work:

vtnerd is the author of Monero-LWS, and has been a contributor to the Monero codebase since 2016. He is a veteran of four CCS proposals; [1], [2], [3], [4]

This proposal funds 480 hours of work, ~3 months. The milestones will be hour based; 160 (1 month), 320 (2 months), 480 (3 months). At the completion of hours, he will provide the Monero Fund committee references to the work that was completed during that timeframe.

Some features that are being targeted in monero-project/monero :

• Get new serialization routine merged (work on piecemeal PRs for reviewers sake) (already in-progress)
• Complete work necessary to merge DANE/TLSA in wallet2/epee.
• Adding trust-on-first-use support to wallet2

Work targeted towards vtnerd/monero-lws :

• Optional full chain verification for malicious daemon attack (already-in progress)
• Webhooks/ZMQ-PUB support for tx sending (watch for unexpected sends)
• ZMQ-pub support for incoming transactions and blocks (notifies of any new transaction or block)
• Implement "horizontal" scaling of account scanning (transfer account info via zmq to another process for scanning)
• Make account creation more "enterprise grade" (currently scanning engine re-starts on every new account creation, and uses non-cacheable memory) * Unit tests for REST-API
• Create frontend LWS C/C++ library
• Provide official LWS docker-image
• Provide official snap/flatpak/appimge (tbd one or all of those)
• Provide pre-built binaries
• (Unlikely) - reproducible builds so community members can verify+sign the binary hashes
• It is unlikely that all features will be implemented, at which point the unfinished features will roll into the next quarter.