Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • monero-project/ccs-proposals
  • rehrar/ccs-proposals
  • DSal/ccs-proposals
  • el00ruobuob/ccs-proposals
  • TONGZHENGSHIJIE/ccs-proposals
  • SarangNoether/ccs-proposals
  • pwrcycle/ccs-proposals
  • onosendai/ccs-proposals
  • xeagu/ccs-proposals
  • b-g-goodell/ccs-proposals
  • xmrhaelan/ccs-proposals
  • moneromooo-monero/ccs-proposals
  • AcceptThisYouCensors/ccs-proposals
  • Needmoney90/ccs-proposals
  • erciccione/ccs-proposals
  • knueffelbund/ccs-proposals
  • xiphon/ccs-proposals
  • dsc/ccs-proposals
  • Codivorous/ccs-proposals
  • serhack/ccs-proposals
  • sgp/ccs-proposals
  • Kukks/ccs-proposals
  • gingeropolous/ccs-proposals
  • hyc/ccs-proposals
  • saumyabratadutt/ccs-proposals
  • kayront/ccs-proposals
  • rellis/ccs-proposals
  • Avantpay19/ccs-proposals
  • lazaridiscom/ccs-proposals
  • omani/ccs-proposals
  • JackBlack/ccs-proposals
  • Kyoto/ccs-proposals
  • Endogen/ccs-proposals
  • sri346/ccs-proposals
  • asymptotically/ccs-proposals
  • Avis/ccs-proposals
  • Monero/ccs-proposals
  • jtgrassie/ccs-proposals
  • Fudin/ccs-proposals
  • helloworld9998/ccs-proposals
  • lalanza808/ccs-proposals
  • TheCharlatan/ccs-proposals
  • atoc/ccs-proposals
  • randybrito/ccs-proposals
  • Ministo/ccs-proposals
  • objectorange/ccs-proposals
  • adrelanos/ccs-proposals
  • mj/ccs-proposals
  • MoneroAddict/ccs-proposals
  • h4sh3d/ccs-proposals
  • paulshapiro/ccs-proposals
  • pricode/ccs-proposals
  • naijaminer/ccs-proposals
  • niyiajayi/ccs-proposals
  • cryptosourov/ccs-proposals
  • Drowxes/ccs-proposals
  • Mon_icp/ccs-proposals
  • Madbu221b/ccs-proposals
  • suyash67/ccs-proposals
  • kdavid2008/ccs-proposals
  • xmrLovera/ccs-proposals
  • lh1008/ccs-proposals
  • jatinajwani/ccs-proposals
  • normoes/ccs-proposals
  • Wobole/ccs-proposals
  • lederstrumpf/ccs-proposals
  • AlexAnarcho/ccs-proposals
  • readifugly/ccs-proposals
  • binaryFate/ccs-proposals
  • oeAdgK01/ccs-proposals
  • nio21/ccs-proposals
  • michaelizer/ccs-proposals
  • janowitz/ccs-proposals
  • fleaw/ccs-proposals
  • gusan/ccs-proposals
  • Leo27/ccs-proposals
  • tobtoht/ccs-proposals
  • anon/ccs-proposals
  • panagot12/ccs-proposals
  • kysn/ccs-proposals
  • monerotesla/ccs-proposals
  • sahil07/ccs-proposals
  • xmronadaily/ccs-proposals
  • ClaytonBHooverIII/ccs-proposals
  • txstreet/ccs-proposals
  • Aron/ccs-proposals
  • jklein/ccs-proposals
  • wtii/ccs-proposals
  • alynoe/ccs-proposals
  • selsta/ccs-proposals
  • johnfoss67/ccs-proposals
  • benevanoff/ccs-proposals
  • op/ccs-proposals
  • cirocosta/ccs-proposals
  • ragazzo/ccs-proposals
  • 888/ccs-proposals
  • elibroftw/ccs-proposals
  • amr-monero/ccs-proposals
  • behash/ccs-proposals
  • AnonDev/ccs-proposals
  • Rucknium/ccs-proposals
  • rating89us/ccs-proposals
  • AdorableTanuki/ccs-proposals
  • neat/ccs-proposals
  • plowsoff/ccs-proposals
  • xmr_sale/ccs-proposals
  • escapethe3RA/ccs-proposals
  • DouglasTuman/ccs-proposals
  • Bl5ckj5ck/ccs-proposals
  • j-berman/ccs-proposals
  • CrypticEntertainments/ccs-proposals
  • Geroser/ccs-proposals
  • ava_haidang/ccs-proposals
  • pluja/ccs-proposals
  • msvblab/ccs-proposals
  • monerokage/ccs-proposals
  • noot/ccs-proposals
  • RogueMaven/ccs-proposals
  • xmrman/ccs-proposals
  • moneronews/ccs-proposals
  • spirobel/ccs-proposals
  • winstonsthiccbooty/ccs-proposals
  • help.ukraine/help-ukraine-to-use-monero
  • dangerousfreedom/ccs-proposals
  • moneroist/ccs-proposals
  • anon_/ccs-proposals
  • agustincruz/3-d-metal-printer-project
  • savandra/ccs-proposals
  • willk/ccs-proposals
  • max.zab/ccs-proposals
  • rimuru/ccs-proposals
  • CryptoMorpheus_/ccs-proposals
  • jeffro256_/ccs-proposals
  • m0n3r0d1c3/ccs-proposals
  • leonerone/ccs-proposals
  • marjorie69/ccs-proposals
  • monero_archive/monero-archive
  • forgotsudo/ccs-proposals
  • mikigrey321/ccs-proposals
  • anhdres/ccs-proposals
  • thelefterisjp/ccs-proposals
  • lescuer971/ccs-proposals
  • MoneroBro/ccs-proposals
  • rayatina/ccs-proposals
  • HoudiniSwap/ccs-proposals
  • nightwolf361/ccs-proposals
  • z00t/ccs-proposals
  • markofdistinction_/ccs-proposals
  • busyboredom/ccs-proposals
  • Mitchellpkt/ccs-proposals
  • Fierfek/p-2-p-publisher-monerotopia-mexico-city
  • BigmenPixel/ccs-proposals
  • cmiv/ccs-proposals
  • VOSTOEMISIO/ccs-proposals
  • valldrac/ccs-proposals
  • Titus/ccs-proposals
  • C0mradeBlin/ccs-proposals
  • kayabaNerve/ccs-proposals
  • Boog9001/ccs-proposals
  • 4rkal/ccs-proposals
  • binarybaron2/ccs-proposals-bb
  • ajs/ccs-proposals
  • sacatunquetun/ccs-proposals
  • vtnerd/ccs-proposals
  • 0xFFFC0000/ccs-proposals
  • Clodagh/ccs-proposals
  • mrcyjanek/ccs-proposals
  • detheforxmr/ccs-proposals
  • r4v3r23/ccs-proposals
  • janaka303/ccs-proposals
  • eyedeekay/ccs-proposals
  • Secrecy1337/ccs-proposals
  • rohanrhu/ccs-proposals
  • baldeagle/ccs-proposals
  • fengzie_mbz/mobazha-with-monero-in-privacy-ecommerce
  • freeross/ccs-proposals
  • DiosDelRayo/ccs-proposals
  • omnedeus/ccs-proposals
  • geonic/ccs-proposals
  • untraceable/ccs-proposals
  • ki9/ccs-proposals
  • monerobullgitlab/ccs-proposals
  • sybann/ccs-proposals-bb
  • hinto/ccs-proposals
  • HardenedSteel/ccs-proposals
  • Kewbit/ccs-proposals
  • plowsofff/ccs-proposals
  • mainnet-pat/ccs-proposals
  • SimplifiedPrivacy/ccs-proposal-carrot-animated-video
  • SimplifiedPrivacy/ccs-proposal-carrot-animated-video-b
  • SNeedlewoods/ccs-proposals
  • midipoet/ccs-proposals
  • soufiane/ccs-proposals
  • geonic1/ccs-proposals
  • v1docq47/ccs-proposals
  • fullmetalScience/ccs-proposals
  • FiatDemise/xmrchat
  • dadybayo/ccs-proposals
  • rottenwheel/ccs-proposals
  • napoly/ccs-proposals
  • techpopulus/marketplace-monero-techdaddi
  • hbs/ccs-proposals
  • acx/ccs-proposals
  • wallet-verse/ccs-proposals
  • N1co1asB1ancon1/monero-contract-system
  • SyntheticBird/ccs-proposals
206 results
Show changes
Showing
with 1143 additions and 42 deletions
---
layout: cp
title: v1docq47 - monerotopia 2023 (part 3) and monerokon 2023 (part 2) voiceovers and working on xmr.ru
author: v1docq47
date: November 30, 2024
amount: 57.6
milestones:
- name: June
funds: 16.66% (9.6 XMR)
done: June 30, 2024
status: finished
- name: July
funds: 16.66% (9.6 XMR)
done: July 31, 2024
status: finished
- name: August
funds: 16.66% (9.6 XMR)
done: August 31, 2024
status: finished
- name: September
funds: 16.66% (9.6 XMR)
done: September 30, 2024
status: finished
- name: October
funds: 16.66% (9.6 XMR)
done: October 31, 2024
status: finished
- name: November
funds: 16.66% (9.6 XMR)
done: November 30, 2024
status: finished
payouts:
- date: 4 July 2024
amount: 9.6
- date: 12 August 2024
amount: 9.6
- date: 4 September 2024
amount: 9.6
- date: 15 October 2024
amount: 9.6
- date: 15 November 2024
amount: 9.6
- date: 9 December 2024
amount: 9.6
---
_Note: Overfunding of 0.10696243161 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
# Introduction
Hi, everyone!
[v1docq47](https://t.me/v1docq47) is here!
This is our next CCS proposal for the new period for voiceover of [Monerotopia 2023](https://www.youtube.com/watch?v=GcJiaPmldhQ&list=PLfJ_JjSwYaa810CWboNcPX7cY-JYEWo-4) and [Konferenco 2023](https://www.youtube.com/playlist?list=PLsSYUeVwrHBm1m7IaU3JiDVb5EC7cn0KG) videos into Russian, creating other content for [Monero Russian Community Youtube channel](https://www.youtube.com/@MoneroRussianCommunity) and supporting [Russian Monero website XMR.RU](https://xmr.ru/).
# Who I Am?
[Since 2017](https://github.com/pulls?q=is%3Apr+author%3Av1docq47+archived%3Afalse+is%3Aclosed+sort%3Acreated-asc) we've been working on translations, transcriptions, voiceover videos and writing various articles and manuals about Monero in Russian.
We also create news [weekly](https://www.youtube.com/watch?v=ixUamqRd3nc&list=PLQyX7h187qnQWtCN6brBXsB9QLEuaJWQO) and [quarterly](https://www.youtube.com/watch?v=rhWi3a3gZXw&list=PLQyX7h187qnTrEQo1n1_-lxR5tk0qlRKo) / [informational](https://www.youtube.com/watch?v=FOsHxWG5jNs&list=PLQyX7h187qnTqq4_-EAnp4HZk9eJpMvZK) / [tutorial](https://www.youtube.com/watch?v=bug2_NvHeNs&list=PLQyX7h187qnTGFHdrdZL7VRxQINEQZ2xJ) videos.
Besides we are publishing text translations of all the Monero speeches both in Russian and English in a separate repository (similar to previous events like [Monero Konferenco 2022](https://github.com/v1docq47/monerokon-2022-transcriptions), [Critical Decentralisation Cluster (36c3)](https://github.com/v1docq47/monero-cdc-36c3-transcriptions), [Monerotopia 2022](https://github.com/v1docq47/monerotopia-2022-transcriptions)) so that everyone could not only watch, but also read the text versions of the speeches.
That is, we are doing localization of Monero project on Russian.
## Shortlist of my previous Monero localization works
- [Mastering Monero](https://github.com/monerobook/monerobook/pull/81)
- [Zero to Monero - Second Edition](https://github.com/UkoeHB/Monero-RCT-report/pull/9)
- [Monero Reserch Lab bulletins and pappers](https://github.com/v1docq47/monero-research-lab-translations/tree/main/publications/bulletins)
- [Critical Decentralisation Cluster (36c3) transcriptions (RUS + ENG)](https://github.com/v1docq47/monero-cdc-36c3-transcriptions)
- [Monerotopia 2022 transcriptions (RUS + ENG)](https://github.com/v1docq47/monerotopia-2022-transcriptions)
- [Monerotopia 2023 transcriptions (RUS + ENG)](https://github.com/v1docq47/monerotopia-2023-transcriptions)
- [Monero Konferenco 2022 transcriptions (RUS + ENG)](https://github.com/v1docq47/monerokon-2022-transcriptions)
- [Monero Konferenco 2023 transcriptions (RUS + ENG)](https://github.com/v1docq47/monerokon-2022-transcriptions)
- [Monero Cheatsheet (The Salmon Series)](https://www.bybaro.it/Moh3po/)
- [Breaking Monero](https://github.com/monero-ecosystem/outreach-docs/tree/master/monero-outreach-docs/translations/ru/transcriptions/breaking_monero)
## Shortlist of my previous videos / voiceover for Monero Russian Community YouTube channel
- [Monero News (Weekly) playlist](https://www.youtube.com/watch?v=ixUamqRd3nc&list=PLQyX7h187qnQWtCN6brBXsB9QLEuaJWQO)
- [Monero News (Quarterly) playlist](https://www.youtube.com/watch?v=rhWi3a3gZXw&list=PLQyX7h187qnTrEQo1n1_-lxR5tk0qlRKo)
- [What is Monero playlist](https://www.youtube.com/watch?v=FOsHxWG5jNs&list=PLQyX7h187qnTqq4_-EAnp4HZk9eJpMvZK)
- [Monero Konferenco 2019 playlist](https://www.youtube.com/watch?v=56Tr03HzGJ8&list=PLQyX7h187qnSZG_PTYtO57_z_nFOlWWEM)
- [Monero Konferenco 2022 playlist](https://www.youtube.com/watch?v=69Vszlx5PQ0&list=PLQyX7h187qnR3doOALJAmHv1mAVPNzNV9)
- [Monero Konferenco 2023 playlist](https://www.youtube.com/watch?v=f3Yrc_Agg84&list=PLQyX7h187qnTLBvm-nu4RsRymKsOJa-jj)
- [Monerotopia 2022 playlist](https://www.youtube.com/watch?v=c6Zu_sqO0pQ&list=PLQyX7h187qnT3F0H-jkINsNR9jG_-3SUU)
- [Monerotopia 2023 playlist](https://www.youtube.com/watch?v=DyQ7B2w_KcI&list=PLQyX7h187qnROrs1c_opKzyeNRu30thuD)
## My other projects
- [Unofficial technical documentation for Monero](https://wiki.xmr.ru/)
- [XMR.RU on Hugo](https://github.com/xmr-ru/xmr_ru)
# What?
During the upcoming period we plan to accomplish the following milestones:
- finish voiceover and transcript of the remaining [Monerotopia 2023](https://www.youtube.com/watch?v=GcJiaPmldhQ&list=PLfJ_JjSwYaa810CWboNcPX7cY-JYEWo-4) videos ([10 speeches](https://trello.com/c/6a8Dfi9C/4-monerotopia-2023-on-russian-voiceover))
- continue voiceover and transcript [Konferenco 2023](https://www.youtube.com/playlist?list=PLsSYUeVwrHBm1m7IaU3JiDVb5EC7cn0KG) videos ([~7 speeches](https://trello.com/c/hW0HdVu4/5-konferenco-2023-on-russian-voiceover))
- re-voiceover old [informational](https://www.youtube.com/watch?v=FOsHxWG5jNs&list=PLQyX7h187qnTqq4_-EAnp4HZk9eJpMvZK) and [tutorial](https://www.youtube.com/watch?v=bug2_NvHeNs&list=PLQyX7h187qnTGFHdrdZL7VRxQINEQZ2xJ) videos (~10 videos)
- creating new videos on working with Monero tools such as Gupax, Blockchain explorer, etc.
- we will continue to publish weekly ([22 videos](https://trello.com/c/feQdy8p0/2-monero-news-weekly)) and quarterly ([2 videos](https://trello.com/c/ZYmjmEbU/3-monero-news-quarterly)) news, [translate](https://trello.com/c/8Pe2secC/1-monero-on-xmrru) articles and all kind of materials related to Monero for XMR.RU and Moneropedia
As always, the whole process and progress will be displayed in our [Trello board](https://trello.com/b/9dB370Bx/june-2024-november-2024).
# How much and Payouts
10$ per hour, \~30 hours per week or \~120 hours per month (\~3-5 hours а day)
30-day average Monero price on Kraken \~125$ (on 10.05.2024)
## In total
120 (hours per month) * 6 (month) * 10 ($ per hour) / 125 (30-day average Monero price) = 7200 / 125 = 57.6 XMR for 6 months work
9.6 XMR per month starting from June
\ No newline at end of file
---
layout: wip
title: v1docq47 - monerokon 2024 voiceovers and working on xmr.ru
author: v1docq47
date: December 31, 2024
amount: 42.64
milestones:
- name: December
funds: 16.66% (7.6 XMR)
done: December 31, 2024
status: done
- name: January
funds: 16.66% (7.6 XMR)
done: January 31, 2025
status: done
- name: February
funds: 16.66% (7.6 XMR)
done:
status: unfinished
- name: March
funds: 16.66% (7.6 XMR)
done:
status: unfinished
- name: April
funds: 16.66% (7.6 XMR)
done:
status: unfinished
- name: May
funds: 4.64 XMR
done:
status: unfinished
payouts:
- date: 23 March 2025
amount: 15.2
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
---
_Note: 15XMR has been awarded to v1docq47 after closure of [Netriks translation coordinator proposal](https://ccs.getmonero.org/proposals/netrik-translation-coordination-2.html)_
_Note: 15.371159810053XMR from v1docq47s' [historical overfunding](https://ccs.getmonero.org/index.php/projects#:~:text=data) has been awarded to this proposal_
# Introduction
Hi, everyone!
[v1docq47](https://t.me/v1docq47) is here!
This is our new CCS proposal for voiceover of [Konferenco 2024](https://www.youtube.com/playlist?list=PLsSYUeVwrHBk-C3zImaDAQLx453PL7dR-) videos into Russian, creating other content for [Monero Russian Community Youtube channel](https://www.youtube.com/@MoneroRussianCommunity) and continue supporting [XMR.RU](https://xmr.ru/).
# Who I Am?
[Since 2017](https://github.com/pulls?q=is%3Apr+author%3Av1docq47+archived%3Afalse+is%3Aclosed+sort%3Acreated-asc) we've been working on translations, transcriptions, voiceover videos and writing various articles and manuals about Monero in Russian.
We also create news [weekly](https://www.youtube.com/watch?v=ixUamqRd3nc&list=PLQyX7h187qnQWtCN6brBXsB9QLEuaJWQO) and [quarterly](https://www.youtube.com/watch?v=rhWi3a3gZXw&list=PLQyX7h187qnTrEQo1n1_-lxR5tk0qlRKo) / [informational](https://www.youtube.com/watch?v=FOsHxWG5jNs&list=PLQyX7h187qnTqq4_-EAnp4HZk9eJpMvZK) / [tutorial](https://www.youtube.com/watch?v=bug2_NvHeNs&list=PLQyX7h187qnTGFHdrdZL7VRxQINEQZ2xJ) videos.
Besides we are publishing text translations of all the Monero speeches both in Russian and English in a separate repository (similar to previous events like [Monero Konferenco 2023](https://github.com/v1docq47/monerokon-2023-transcriptions), [Monerotopia 2023](https://github.com/v1docq47/monerotopia-2023-transcriptions), [Critical Decentralisation Cluster (36c3)](https://github.com/v1docq47/monero-cdc-36c3-transcriptions) so that everyone could not only watch, but also read the text versions of the speeches.
That is, we are localizing the Monero project into Russian.
## Shortlist of my previous Monero localization works
- [Breaking Monero](https://github.com/monero-ecosystem/outreach-docs/tree/master/monero-outreach-docs/translations/ru/transcriptions/breaking_monero)
- [Mastering Monero](https://github.com/monerobook/monerobook/pull/81)
- [Zero to Monero - Second Edition](https://github.com/UkoeHB/Monero-RCT-report/pull/9)
- [Monero Cheatsheet (The Salmon Series)](https://www.bybaro.it/Moh3po/)
- [Monero Reserch Lab bulletins and pappers](https://github.com/v1docq47/monero-research-lab-translations/tree/main/publications/bulletins)
- [Monerotopia 2022 transcriptions (RUS + ENG)](https://github.com/v1docq47/monerotopia-2022-transcriptions)
- [Monerotopia 2023 transcriptions (RUS + ENG)](https://github.com/v1docq47/monerotopia-2023-transcriptions)
- [Monero Konferenco 2022 transcriptions (RUS + ENG)](https://github.com/v1docq47/monerokon-2022-transcriptions)
- [Monero Konferenco 2023 transcriptions (RUS + ENG)](https://github.com/v1docq47/monerokon-2022-transcriptions)
- [Critical Decentralisation Cluster (36c3) transcriptions (RUS + ENG)](https://github.com/v1docq47/monero-cdc-36c3-transcriptions)
## Shortlist of my previous videos / voiceover for Monero Russian Community YouTube channel
- [What is Monero playlist](https://www.youtube.com/watch?v=FOsHxWG5jNs&list=PLQyX7h187qnTqq4_-EAnp4HZk9eJpMvZK)
- [Monero News (Weekly) playlist](https://www.youtube.com/watch?v=ixUamqRd3nc&list=PLQyX7h187qnQWtCN6brBXsB9QLEuaJWQO)
- [Monero News (Quarterly) playlist](https://www.youtube.com/watch?v=rhWi3a3gZXw&list=PLQyX7h187qnTrEQo1n1_-lxR5tk0qlRKo)
- [Monerotopia 2022 playlist](https://www.youtube.com/watch?v=c6Zu_sqO0pQ&list=PLQyX7h187qnT3F0H-jkINsNR9jG_-3SUU)
- [Monerotopia 2023 playlist](https://www.youtube.com/watch?v=DyQ7B2w_KcI&list=PLQyX7h187qnROrs1c_opKzyeNRu30thuD)
- [Monero Konferenco 2019 playlist](https://www.youtube.com/watch?v=56Tr03HzGJ8&list=PLQyX7h187qnSZG_PTYtO57_z_nFOlWWEM)
- [Monero Konferenco 2022 playlist](https://www.youtube.com/watch?v=69Vszlx5PQ0&list=PLQyX7h187qnR3doOALJAmHv1mAVPNzNV9)
- [Monero Konferenco 2023 playlist](https://www.youtube.com/watch?v=f3Yrc_Agg84&list=PLQyX7h187qnTLBvm-nu4RsRymKsOJa-jj)
## My other projects
- [Unofficial technical documentation for Monero](https://wiki.xmr.ru/)
- [XMR.RU on Hugo](https://github.com/xmr-ru/xmr_ru)
# What?
During the upcoming period we plan to accomplish the following milestones:
* [start work on voiceover and transcription of Konferenco 2024](https://trello.com/c/jUt3uC8c)
* [creating videos on working with Monero tools such as Gupax, p2pool, blockchain explorer, etc.](https://trello.com/c/P3tcSWAF/5-tools-in-monero)
* continue to publish [weekly (20 videos)](https://trello.com/c/bPY8povA/2-monero-news-weekly) and [quarterly (2 videos)](https://trello.com/c/PVgWV6HO/4-monero-news-quarterly) news
* translate articles and news for [XMR.RU](https://xmr.ru/) and [wiki.xmr.ru](https://wiki.xmr.ru/)
As always, the whole process and progress will be displayed in our [Trello board](https://trello.com/b/MFPsQkbx/december-2024-may-2025).
# How much and Payouts
10$ per hour, \~30 hours per week or \~120 hours per month (\~3-5 hours a day)
30-day average Monero price on Kraken \~158$ (on 14.11.2024)
## In total
120 (hours per month) * 6 (month) * 10 ($ per hour) = 7200 / 158 (30-day average Monero price) = ~45.6 XMR for 6 months work
7.6 XMR per month starting from December
---
layout: fr
layout: cp
title: v1docq47 - video creation and translations into russian (february - july 2022)
author: v1docq47
date: July 31, 2022
......@@ -8,42 +8,44 @@ milestones:
- name: February
funds: 16.66% (10.3 XMR)
done: February 28, 2022
status: unfinished
status: finished
- name: March
funds: 16.66% (10.3 XMR)
done: March 31, 2022
status: unfinished
status: finished
- name: April
funds: 16.66% (10.3 XMR)
done: April 30, 2022
status: unfinished
status: finished
- name: May
funds: 16.66% (10.3 XMR)
done: May 31, 2022
status: unfinished
status: finished
- name: June
funds: 16.66% (10.3 XMR)
done: June 30, 2022
status: unfinished
status: finished
- name: July
funds: 16.66% (10.3 XMR)
funds: 16.66% (10.5 XMR)
done: July 31, 2022
status: unfinished
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 4 March 2022
amount: 10.3
- date: 2 April 2022
amount: 10.3
- date: 2 May 2022
amount: 10.3
- date: 9 June 2022
amount: 10.3
- date: 6 July 2022
amount: 10.3
- date: 4 August 2022
amount: 10.5
---
_Note: Overfunding of 5.296349910952 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
# Introduction
Hello, my dear followers, colleagues, and friends!
......
......@@ -42,6 +42,8 @@ payouts:
amount: 16.3
---
_Note: Overfunding of 9.775398688381 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
Hello, my dear followers, colleagues, and friends!
v1docq47 is here!
And this is my new funding request for my work.
......
......@@ -44,6 +44,9 @@ payouts:
amount: 8
---
_Note: Overfunding of 0.102272626261 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
# Introduction
Hello, my dear followers, colleagues, and friends.
[v1docq47](https://t.me/v1docq47) is here!
......
......@@ -40,6 +40,8 @@ payouts:
amount: 9
---
_Note: Overfunding of 0.031000000001 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
# Introduction
Hello, my dear followers, colleagues, and friends.
[v1docq47](https://t.me/v1docq47) is here.
......
---
layout: wip
title: Offline Signing Library for XmrSigner to Production
date: August 31, 2024
author: Thor a.k.a. vThor a.k.a DiosDelRayo
amount: 196
milestones:
- name: Upfront
funds: 20 XMR
done: 11 November 2024
status: finished
- name: First month, minus upfront
funds: 46 XMR
done: 5 December 2024
status: finished
- name: Second month
funds: 65 XMR
done: 30 January 2025
status: finished
- name: Third month
funds: 65 XMR
done:
status: unfinished
payouts:
- date: 15 November 2024
amount: 20
- date: 13 December 2024
amount: 46
- date: 10 February 2025
amount: 65
- date:
amount:
- date:
amount:
---
# Offline Signing Library for XmrSigner Production
## About
This proposal aims to create a minimal library for offline signing on
air-gapped devices, and make XmrSigner production ready to actual use secure, focusing on essential features:
- Seed phrase generation (including polyseed)
- Address and key generation
- Account and sub-address management
- Address verification
- Output importing and Key Image exporting (raw and encrypted)*
- Unsigned transaction handling (description, sanity checks, signing)
- Block height and date estimation
The library will be implemented in C++ with a C ABI, allowing use in
multiple languages. It will be based on the current Monero source but
without relying on wallet2, aiming for minimal external dependencies,
not inventing the wheel again, nor rolling own crypto.
Key objectives:
- Comprehensive documentation (OTS library, OTS Python library, buildroot packages desired integrated into monero docs for a easy and quick start to build something)
- Quick start guide for offline and hardware wallet developers
- Documentation of challenges in stripping down and cross-compiling
- Buildroot package for easy target system integration
- Python module for library usage
- Test code
- Modification of XmrSigner to use this new library
## Who
Thor (vThor/DiosDelRayo), completed the [XmrSigner (MoneroSigner Resurrection) proposal](https://ccs.getmonero.org/proposals/%20MoneroSignerResurrection.html).
## Why
[XmrSigner](https://github.com/XmrSigner/xmrsigner), while functional, is currently more of a proof of concept than a
production-ready tool. This library addresses several key issues:
1. Performance: The current implementation using wallet RPC is slow,
especially on resource-constrained devices.
2. Security: Minimizing dependencies and code base improves auditability
and reduces attack surface.
3. Flexibility: A dedicated library allows for easier integration into
various offline signing solutions.
4. Resource efficiency: Stripping down to essential features enables use on
lower-power devices.
By creating this library, we will:
- Bring XmrSigner to production readiness
- Provide a foundation for future hardware wallet development
- Explore the viability of using even more resource-constrained devices (e.g., MCUs) for offline signing
- Build the basis for a lib which could also serve for quick payment way (seems there exists something like it called pocket change, was not aware of before) even if the customer is offline. Talked about that in [#monero-community](https://libera.monerologs.net/monero-community/20241018#c446995)
A proof of concept has been developed to validate this approach:
[c_abi_for_cpp_code_PoC](https://github.com/DiosDelRayo/c_abi_for_cpp_code_PoC)
This library will significantly improve XmrSigner's performance, security,
and usability while opening doors for more diverse Monero hardware wallet
solutions in the future.
## Milestones and Timeline
# Offline Signing Library for XmrSigner Production
## Milestones and Timeline
### 1. Setting up documentation site (4 hours)
All OTS library related will go into a fork of docs.get-monero.org and should take me no more than a blink of an eye to get going.
For the XmrSigner related part I will setup the same mkdocs via github pages.
This is apart from the Doxygen and Sphinx documentation, which I need to see how to make it best available on the way.
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Set up initial documentation structure | 2 | 1 |
| Configure documentation site | 2 | 1 |
| Use existing Monero documentation through PR's | 0 | 0 |
</details>
### 2. MVP library with C ABI (164 hours)
The main task of this proposal, creating an ots folder in monero/src and nit pick the parts the lib needs together
to create and compile a actual library. On top add the C ABI and make the build script as easy and robust as possible.
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Initial ABI design | 16 | 8 |
| Seed phrase generation | 8 | 4 |
| Address and key generation | 10 | 5 |
| Account and sub-address management | 10 | 5 |
| Address verification | 10 | 5 |
| Output importing and Key Image exporting | 30 | 15 |
| Unsigned transaction handling | 30 | 15 |
| Write Doxygen documentation | 14 | 7 |
| Create detailed documentation of the ABI and library internals | 14 | 7 |
| Develop unit tests with Check | 14 | 7 |
| PR process revisions and merge | 8 | 4 |
</details>
### 3. Python cffi classes (44 hours)
Building the clue code between the C ABI and Python in a pythonic way.
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Design Python class structure | 10 | 5 |
| Implement Python wrapper classes | 20 | 10 |
| Write rich inline documentation | 8 | 4 |
| Create Sphinx documentation | 2 | 1 |
| Develop unit tests for Python classes | 4 | 2 |
</details>
### 4. Building library in buildroot (44 hours)
buildroot is a build kit to create an embedded linux with the help of
packages which get cross compiled for the target platform. Here the dependencies
to build the OTS library from the monero sources need to be fulfilled.
<details>
<summery>Show more...</summary>
A very critical part to use the library on the pi zero (or other target device - maybe modifications will be needed here fore).
I build for XmrSigner before buildroot packages, but struggled to get monero-wallet-rpc as binary running on
the pi via Buildroot (how I was building on the Pi itself and there are so many dependencies that finally I pulled
the plug on that version, becauseit was clear that monero-wallet-rpc was only a temporary solution to finish the CCS
in a running state)
</details>
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Adapt CMakeLists.txt for the library and its dependencies | 20 | 10 |
| Create buildroot package for downloading and compiling | 12 | 6 |
| Write documentation for builders/developers | 12 | 6 |
</details>
### 5. Buildroot package for Python library (12 hours)
The same but a lot easier then for the OTS library, here the Python OTS
library will get compiled via CPython, how there are only two dependencies (the OTS library and
cffi) it should be much easier even with a deterministic build.
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Create buildroot package for the Python library | 8 | 4 |
| Write documentation for builders/developers | 4 | 2 |
</details>
### 6. XmrSigner integration (34 hours)
Here the XmrSigner code get's the upgrade, monero-wallet-rpc, python-monero, python-polyseed will
be replaced by the Python OTS library.
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Remove existing dependencies and integrate new Python library | 26 | 13 |
| Update XmrSigner documentation | 8 | 4 |
</details>
### 7. XmrSigner on XmrSigner OS (buildroot2) (42 hours)
Here all gets assembled together to create the actual XmrSigner production image.
<details>
<summery>Show more...</summary>
How I did that already outside of the last CSS, I need only to make some modifications,
get the dependencies right, the biggest part will be testing and debugging if something
goes wrong - I had this issue already, but hope that this time is minimal to use the calculated
time for Milestone 9 because I really like to improve there. But 30 hours can vanish quick debugging
issues there because it took like 30min to build on a 4c ore i7 with 16GB (lack at the moment something more powerful)
and then flashing to microSD and test. But how from the buildroot image was forked from SeedSignerOS which stripped handy
everything unnecessary away - good for security and speed - but terrible to debug.
</details>
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Create buildroot package for XmrSigner | 8 | 4 |
| Test and debug XmrSigner in buildroot environment | 30 | 15 |
| Write documentation for XmrSigner OS integration | 4 | 2 |
</details>
### 8. Unify XmrSigner-related components (48 hours)
Getting all the XmrSigner stuff on one place together and the OTS library stuff on docs.get-monero.org, or
at least in close reach.
<details>
<summery>Show more...</summary>
Through the excessive amount of time the last CCS took the rebranding to XmrSigner and
putting documentation and linking nice together suffered a bit. So here everything will
get separated what is actual XmrSigner and what is needed to build a different Offline Signer
from the OTS library and BCUR. So that XmrSigner is XmrSigner, and the building blocks a close to get-monrero.org
as possible. All development resources should be on monero docs after the PR got merged, so there is a quickstart
and all documents to create an offline signer pretty quick.
</details>
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Reorganize and consolidate XmrSigner-related content on GitHub | 8 | 4 |
| Create separate documentation for UR codes | 20 | 10 |
| Register UR types used | 6 | 3 |
| Final review and organization of all documentation | 14 | 7 |
</details>
### 9. (Optional/Stretch) Clean-up and Optimization (82 hours)
Here is where my heart is, but after carefully calculating through the time, and catching myself,
arguing on almost each point it could be done faster, and almost halving most points... I still with 138h more
then the original 240 hours estimated. And instead of doubling or triple the time to have more air for unforeseen
challenges I'm now even tighter, so that I probably will end up again working a lot of hours for free to get all done.
But I still hope to safe enough time to get this milestone done, too.
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Analyze Monero source dependencies | 20 | 10 |
| Remove unnecessary dependencies | 20 | 10 |
| Optimize remaining code | 10 | 5 |
| Document changes and rationale | 16 | 8 |
| Analyze minimal resources needed for OTS library on restricted devices | 8 | 4 |
| PR process revisions and merge | 8 | 4 |
</details>
### 10. (Stretch) Xmr Signer Pure (Rewrite in C++) (98 hours)
If I have the mega flow, I will continue here to move substitute the Python code
to C++. Why C++ and not Go or not Rust? First I'm still learning daily in C++, but
the more important reason, I think there is a benefit in thinking on a bare metal
XmrSigner NG in future. [circle](https://github.com/rsta2/circle) and [libcamera](https://github.com/rsta2/libcamera)
would make it possible to run XmrSigner on bare metal what is a C++ environment...
So done this here well, most of the work would be already done for the next step.
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Build environment | 6 | 3 |
| Screen | 8 | 4 |
| UI | 12 | 6 |
| Logic | 20 | 10 |
| OTS | 4 | 2 |
| CBOR | 8 | 4 |
| BCUR | 8 | 4 |
| Zxing | 12 | 6 |
| Cam | 20 | 10 |
</details>
### 11. (Stretch) JNI classes (44 hours)
This is another thing I wanted to include but the time constraints will probably not allow it.
One to have a second language using the C ABI with documentation, and second to be used
for Android apps.
<details>
<summary>View tasks</summary>
| Task | Hours | Sessions |
|------|-------|----------|
| Design Java class structure | 10 | - |
| Implement Java wrapper classes | 20 | - |
| Create Java documentation | 10 | - |
| Develop unit tests for Java classes | 4 | 44 |
</details>
## Total Estimated Time
Core Milestones (1-8): 392 hours
Optional/Stretch Milestones (9-11): 224 hours
Grand Total: 616 hours
*Note: This timeline is an estimate and may be subject to adjustments as the project progresses. The sessions are based on the Pomodoro technique to maintain high focus and productivity throughout the project.*
Given the significant time investment and potential challenges ahead, I
propose a shift from my usual value-based pricing to an monthly rate for
this project.
Proposed terms:
- 65 Promodoro Sessions (130 hours) per month for three months (196 sessions in total, first month one extra session)
- Compensation: 1 XMR per session, making 66 XMR first and 65 XMR second and 65 third month. (196 in total)
- I would kindly request a 20 xmr upfront on start from the first month.
- Total compensation: 196 XMR
Hours worked beyond in the running month shall roll over to the next month. If I can work some time out I will work
on the optional/strech goals. If time is missing to get milestone 1-8 done in the calculated hours, I will work hours for free to get it done - I always do.
I will commit every day my work, on starting each repository I will advertise them here in a comment an push my commits every day.
And I will create a repository/blog or something as a daily logbook to document the work done and the daily progress.
<details><summary>I set up a [website](https://diosdelrayo.github.io) which syncronizes my actual pomodoro sessions, and the last 48 hours the work done</summary> on which tasks and how many sessions, even each unit time, so it is more transparent. On the way I plan to render also all tasks with the total time and a calendar. But the raw data is available in the issues of the [github repository](https://github.com/DiosDelRayo/DiosDelRayo.github.io) of the site. The time worked on each task can be calculated by the label and unlabeling of `WIP` label is start to work and unlabel end of work on it.
</details>
---
layout: wip
title: Wallet SDK for Android
author: valldrac
date: May 17, 2023
amount: 295
milestones:
- name: Development
funds: 180 XMR
done: 4 March 2024
status: finished
- name: Security Enhancements
funds: 24 XMR
done: 12 August 2024
status: finished
- name: Continuous Integration & Testing
funds: 51 XMR
done:
status: unfinished
- name: Maintenance (3 months)
funds: 20 XMR
done:
status: unfinished
- name: Maintenance (3 months)
funds: 20 XMR
done:
status: unfinished
payouts:
- date: 21 March 2024
amount: 180
- date: 14 August 2024
amount: 24
- date:
amount:
- date:
amount:
- date:
amount:
---
### Summary
We propose supporting the development of the new Monero SDK for Android that the [Molly.im](https://molly.im) team is actively working on.
The goal of this SDK is to provide a solution for developers to integrate Monero into their apps by offering an Android wallet library and a sample app. The library will include advanced features such as support for multiple wallets, sandboxed C++ code, client-side load balancing and asynchronous API. It will be compatible with Android Studio and fully optimized for size and performance. The demo app will feature the capabilities of the library, using the best practices and tools.
The development of this SDK aims to resolve issues found in existing libraries during the integration of Monero into Molly. If you would like to know the rationale behind this SDK, and learn about the Molly project and background, we recommend checking out our CCS titled "Decentralizing Molly.im to support Monero payments" and the latest follow-up at the following links: [CCS proposal](https://ccs.getmonero.org/proposals/vd-molly-payments-stage1.html) and [update post](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/252#note_20900).
### SDK Overview
The Monero SDK consists of two components:
1. **Android Library**: A specialized library that allows developers to interact with the Monero network and perform wallet operations. This library is written in Kotlin and offers a reliable asynchronous API.
2. **Sample Wallet App**: An example app written in Kotlin that showcases the usage of the library for wallet app development. It serves as an integration guide for developers and facilitates the testing of new functionalities.
### Android Library
The Android library is the core component of the SDK. Internally it wraps and extends the wallet2 low-level API.
Key features and design decisions of the Android library include:
- **Kotlin Language**: The library is implemented in Kotlin, which is the preferred language for Android development. Kotlin's interoperability with Java ensures compatibility with existing apps.
- **Asynchronous API**: It leverages Kotlin's Coroutines support for asynchronous programming, providing a reliable and non-blocking API that seamlessly integrates with Android's event-driven development model.
- **Sandboxed Execution**: All non-memory-safe code (C++) runs within an isolated process with zero privileges and restricted access to the host app or system resources. Even if a remote execution exploit affects Monero, it becomes extremely difficult for an attacker to elevate privileges to the system or host app.
- **Modular Architecture**: The library is built as an Android service, using Android's AIDL interprocess communication (IPC) to connect the Kotlin layer with the sandboxed native code. This client-server architecture decouples the internal wallet2 implementation from the public API of the SDK, facilitating future swapping of the wallet2 module without major changes to the API. This enables smoother migration to Seraphis for developers using our SDK.
- **Storage Abstraction**: The library provides a storage abstraction layer, simplifying wallet persistence for developers. It allows the SDK to be agnostic about the underlying storage mechanism (files, database, cloud, etc.). This flexibility enables developers to improve data-at-rest encryption without modifying the SDK code.
- **Network Client Injection**: Instead of relying on the networking code of wallet2, the SDK allows the app to provide its own HTTP client. This gives the app the freedom to support any transport protocol, such as Tor, transparently to the SDK.
- **Custom Logging**: The library includes a logging adapter that developers can customize. It enables the host app to determine log storage and location, providing a way to encrypt or remove sensitive information from the logs if needed.
- **Client-side Load Balancing**: The library enables the host app to dynamically select the optimal remote node for RPC calls, ensuring efficient synchronization with the Monero blockchain. This can significantly reduce synchronization time by choosing the fastest node.
- **Android Studio Compatibility**: The SDK is fully compatible with Android Studio, supporting native debugging, code navigation, and linter capabilities, for both the SDK library and the Monero codebase.
- **Optimized Build System**: The library has optimized CMake files that vendor all dependencies of wallet2, and applies Link-time optimizations (LTO) to remove all C++ code that is never called by the SDK. The result is a reproducible and lightweight library size of only 6 MB per arch, that can be built directly from Gradle.
### Sample Wallet App
The sample app is a fully functional multi-wallet app that serves as a reference for developers on integrating Monero into their apps. It is also a way to test if the library works well in a real-world application. Key features of the sample wallet app include:
- **Clean Architecture**: The sample app uses the latest Android libraries and follows the [official architecture guidance](https://developer.android.com/topic/architecture#recommended-app-arch).
- **Kotlin and Jetpack Compose**: The sample app is entirely written in Kotlin and uses Jetpack Compose for the UI, as well as many architecture components like Room, Lifecycle, and Navigation.
### Use Cases
The SDK is primarily designed to support two use cases: (i) local synchronized mobile wallets and (ii) Monero payments, with a focus on security, simplicity and performance. Although we are centered on these specific use cases, it would be beneficial to consider other potential applications where the SDK could be used in the future.
In the first stable release, it is planned to provide the following functionality:
1. Wallet Management
1. Create and restore wallet from mnemonic seed (25-words standard) or secret key
2. Export wallet seed and secret key
3. Save and load wallet from the storage defined by the app
2. Account Generation and Subaddresses
1. Derive account subaddresses and track their usage
2. Parse base58 public addresses
3. Balance Inquiry
1. Query locked/unlocked balance at a specific time
2. Retrieve transaction history
3. Listen to balance and transaction (ledger) updates
4. Transaction Handling
1. Construct, sign, and broadcast single and multi-recipient TXs
2. Handle network fee automatically
3. Create and verify payment proofs
5. Blockchain Synchronization
1. Resume scanning or restart it from a specific height
2. Load balance RPC calls and failover to multiple remote nodes
3. Monitor remote node status and response time
The following features would be left out of the first release: fine-grained coin control, hardware wallets, manual transaction input, message signing, and multisig. There is no roadmap or timeline yet for when these additional features will be included in future releases.
### Code Example
This snippet of code is a basic example to show how to use the API: [wallet-sdk-android-example.kt](https://gist.github.com/valldrac/54ff6842e4cc6d624ab893f4e839b2ae)
### Limitations and Known Issues
The biggest issue we have come across is how wallet2 trusts the remote nodes for blockchain synchronization. While it is widely known that malicious nodes can manipulate the returned blocks to deceive clients, the current lack of validation in wallet2 makes it too easy to exploit. Unfortunately, wallet2 fails to verify if the returned blocks line up with the previous blocks in the chain. This vulnerability has already been described in a security advisory ([link](https://www.reddit.com/r/Monero/comments/134jbdt/security_advisory_new_attack_from_malicious/)).
To mitigate this problem, we suggest adding basic integrity checks into wallet2, but without validating PoW. These checks will help wallet2 to early detect the attack when connecting to an honest node.
Our plan is to address this issue for the initial release of the SDK, as well as upstream the fixes to wallet2.
### Comparative Analysis
The main difference, in addition to the aspects mentioned in the design section, is that the existing libraries are essentially "library wrappers". They consist of a thin layer of code that translates the wallet2 API into a compatible interface for Java while maintaining the same (and intricate) semantics. However, in our SDK we have tried to develop a simplified yet flexible API explicitly designed for Android that prevents common pitfalls associated with wallet2.
It is important to note that we have not conducted a comprehensive comparative analysis yet between our SDK and existing Java libraries like Monerujo's [xmrwallet](https://github.com/m2049r/xmrwallet) or woodser's [monero-java](https://github.com/monero-ecosystem/monero-java).
### Progress Report
The development progress of the library API at a high-level is as follows:
- Wallet Management: 90% complete.
- Account Generation and Subaddresses: 20% complete.
- Balance Inquiry: 70% complete.
- Transaction Handling: 0% complete.
- Blockchain Synchronization: 80% complete.
We have made significant progress in the demo wallet app as well, implementing key features such as multiple wallet creation, customizable settings, balance checking, and individual remote node configuration for each wallet. The demo includes a basic syncing service that automatically refreshes and saves the wallets. It also supports syncing over SOCKS proxies.
Based on the progress made so far, we have spent a total of 625 hours on development. Out of these, 550 hours until the end of April, and 75 hours from May until now.
The SDK, that includes the library and the demo, is available on GitHub: https://github.com/mollyim/monero-wallet-sdk
### Proposal & Milestones
By funding this project we aim to accelerate the adoption of Monero in the Android ecosystem, providing a reliable and flexible solution for developers to integrate Monero into their apps. This funding will also drive the integration of Monero into Molly.im.
The proposed milestones for this project are as follows:
1. Development
- Complete the development of the library for the planned use cases.
- Complete the implementation of the remaining features for the demo wallet app.
2. Security Enhancements
- Implement and validate basic integrity checks in wallet2 to mitigate the risk of malicious nodes.
- Upstream the improvements to the core library.
3. Continuous Integration & Testing:
- Set up CI pipeline to automate builds, testing, and release processes.
- Maintain a minimum unit test coverage of 70% for the library (excluding 3rd party and generated code).
4. Release Management
- Iterate on the SDK based on community feedback, fixing issues, and reviewing pull-requests on GitHub.
- Coordinate new releases, including versioning and release notes.
5. Documentation
- Create a clear README that provides an overview of the project and build instructions.
- Generate the API reference documentation.
- Include code snippets and recipes to demonstrate how to solve common problems with the SDK.
- Create a component diagram that illustrates the architecture and key components.
- Comment the code of the wallet app to serve as an integration guide, explaining the implementation details.
- Regularly update the documentation.
6. Community Engagement
- Engage actively with the community on Matrix to understand their needs and include their suggestions into future updates.
7. Seraphis Migration Planning
- Join the Seraphis Working Group to provide feedback, share design ideas, and review migrations plans for a smooth transition to Seraphis.
### Funding
We are requesting a total of $36,000 in funding to support this project, allocated in these milestones:
1. Development: $22,000
2. Security Enhancements: $3,000
3. Continuous Integration & Testing: $6,200
For the remaining milestones (4 to 7) we propose to allocate $4,800 for 6 months of maintenance, with payouts of $2,400 every 3 months.
Based on current rate of 1 XMR = $140 (as of June 10th 2023) with a 15% volatility buffer, the equivalent amount of $36,000 would be approximately 295 XMR.
### Expiration
If no milestones have been claimed within 9 months from the start of the project (since moved to work-in-progress) or latest payout, the CCS for the project shall be considered expired. In case of expiration, the remaining unclaimed funds will be donated to other CCS proposals.
---
layout: wip
layout: cp
title: vtnerd Full-Time 2021 Q1
author: Lee Clagett (vtnerd)
date: February 17, 2021
......@@ -7,23 +7,23 @@ amount: 133.4 XMR
milestones:
- name: Month 1 (160 hours)
funds: 44 XMR
done:
status: unfinished
done: 09 April 2021
status: finished
- name: Month 2 (320 hours)
funds: 44 XMR
done:
status: unfinished
done: 19 May 2023
status: finished
- name: Month 3 (480 hours)
funds: 45.4 XMR
done:
status: unfinished
done: 14 July 2023
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 4 January 2023
amount: 44
- date: 12 June 2023
amount: 44
- date: 26 July 2023
amount: 45.4
---
3-Months full-time software development on monero "core" components in 2021 q1 (through early q2).
......
---
layout: cp
title: vtnerd Full-Time 2023 Q3
author: Lee Clagett (vtnerd)
date: June 11, 2023
amount: 166.95 XMR
milestones:
- name: Month 1 (160 hours)
funds: 55 XMR
done: 20 September 2023
status: finished
- name: Month 2 (320 hours)
funds: 55 XMR
done: 26 November 2023
status: finished
- name: Month 3 (480 hours)
funds: 56.95 XMR
done: 11 February 2024
status: finished
payouts:
- date: 3 November 2023
amount: 55
- date: 1 December 2023
amount: 55
- date: 9 March 2024
amount: 56.95
---
3-Months full-time software development on monero "core" components in 2023 q3.
## What
Work primarily on the `monerod`, `wallet`, and `monero-lws`. Some of the work to be attempted or investigated:
- Complete p2p Noise encryption (already in-progress)
- Get new serialization routine merged (work on piecemeal PRs for reviewers sake)
- Complete work necessary to merge [DANE/TLSA in wallet2/epee](https://github.com/vtnerd/monero/tree/improve/dane_tlsa).
- Adding trust-on-first-use support to wallet2
- Add msgpack support to monerod-ZMQ (requires merging of new serialization system)
- `monero-lws` work:
- Optional full chain verification for malicious daemon attack
- Subaddresses
- A accept-all-new-accounts mode similar to MyMonero behavior (instead of manually callback)
- Webhook for new account creation (prevents polling for new accounts)
- ZMQ pub support for incoming transactions and blocks (notifies of _any_ new transaction or block)
- Create Github Actions that run unit-tests and provide binaries
- 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
More than 3 months listed there, priorities may change as community requests or issues arise.
## Who
Lee Clagett (vtnerd). I've had [three](https://ccs.getmonero.org/proposals/vtnerd-tor-tx-broadcasting.html) [CCS](https://ccs.getmonero.org/proposals/vtnerd-2020-q4.html) [proposals](https://ccs.getmonero.org/proposals/vtnerd-2021-q1.html). The [full list of my monero PRs since last CCS](https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Avtnerd+created%3A%3E2021-02-17). I've also written a [msgpack implementation](https://github.com/vtnerd/monero-lws/pull/63) for the new serialization system (in Monero-LWS), an [admin REST](https://github.com/vtnerd/monero-lws/pull/62) api to Monero-LWS, as well as [webhooks for incoming transactions](https://github.com/vtnerd/monero-lws/pull/66) (including a [zero-confirmation](https://github.com/vtnerd/monero-lws/pull/72) for webhooks) (instead of the previously proposed ZMQ-PUB). [Unit tests](https://github.com/vtnerd/monero-lws/pull/53) were also finally added to Monero-LWS.
## Proposal
Work on the various tasks outlined above for 40 hours/week over the next 3 months after potential funding. I already use time-tracking software for work; if the hours dip in a given month unexpectedly, the update/milestone will be at the completion of the hours listed above.
The funds were calculated with 55 USD/hour with ~158.13 USD/XMR which is the 14-day exponential moving average on Kraken through 2023/07/02.
---
layout: cp
title: vtnerd full-time 2024 q3
author: Lee Clagett (vtnerd)
date: July 11, 2024
amount: 208.12 XMR
milestones:
- name: Month 1 (160 hours)
funds: 69 XMR
done: 24 August 2024
status: finished
- name: Month 2 (320 hours)
funds: 69 XMR
done: 03 October 2024
status: unfinished
- name: Month 3 (480 hours)
funds: 70.12
done: 22 November 2024
status: finished
payouts:
- date: 4 September 2024
amount: 69
- date: 26 October 2024
amount: 69
- date: 6 December 2024
amount: 70.12
---
3-Months full-time software development on monero "core" components in 2024 q3.
## What
Work primarily on the `monerod`, `wallet`, and `monero-lws`. Some of the work to be attempted or investigated:
- Code reviews of monero core PRs
- Optimization work in monero core (work with the new stressnet team)
- Add socks5 support to wallet and monerod (which adds IPv6 support to proxies)
- Add support for [torspec/control-spec](https://github.com/torproject/torspec/blob/main/control-spec.txt). This is similar to the SAM proposal for I2P
- Get new serialization routine merged (continue work on piecemeal PRs for reviewers sake)
- Complete work necessary to merge [DANE/TLSA in wallet2/epee](https://github.com/vtnerd/monero/tree/improve/dane_tlsa).
- Adding trust-on-first-use support to wallet2
- Add msgpack support to monerod-ZMQ (requires merging of new serialization system)
- `monero-lws` work:
- Complete LWS frontend (using `wallet_api.h` as interface) so that wallets can begin using LWS API easily. This is separate from woodser et al working on LWS API within `wallet2` which may be deprecated.
- Perform apache-benchmark test on REST api to determine effects of blocking ZMQ calls
- Cache some ZMQ calls performed during REST api responses to reduce burden on `monerod` and improve REST throughput
- Add concurrency to REST API responses - remove blocking ZMQ calls which starve valuable REST thread resources
- A switchover to boost asio/beast/azmq from epee/zmq to handle async http responses will be needed
- `get_random_outs` endpoint has blocking ZMQ calls that cannot be cached, thus the potential need for async-zmq
- Add a "scale" factor to remote scanning load balancing - send more accounts to systems with faster single thread performance
- Add 64-bit ed25519 code for faster arm64 scanning
- Provide official LWS docker-image
- Provide pre-built binaries
- (Unlikely) - reproducible builds so community members can verify+sign the binary hashes
There is intentionally more work than time allows - to ensure there is always something to work on in the proposal.
## Who
Lee Clagett (vtnerd). I've had [four](https://ccs.getmonero.org/proposals/vtnerd-tor-tx-broadcasting.html) [CCS](https://ccs.getmonero.org/proposals/vtnerd-2020-q4.html) [proposals](https://ccs.getmonero.org/proposals/vtnerd-2021-q1.html) ([last one](https://ccs.getmonero.org/proposals/vtnerd-2023-q3.html)), and [one Magic Grant](https://monerofund.org/projects/Q1Q2_2024_dev_vtnerd).
Some of my biggest features in monero core repo are [Dandelion++](https://github.com/monero-project/monero/pull/6314), [adding supercop ASM speedups to wallet code](https://github.com/monero-project/monero/pull/6337), [ZeroMQ Pub Support for new blocks and transactions](https://github.com/monero-project/monero/pull/6418), and [SSL support to p2p](https://github.com/monero-project/monero/pull/8996).
I've also made a functional LWS wallet scanner under CCS/Magic - which now has a MyMonero compatible REST API, admin REST API, LMDB storage, subaddress support, webhook/zmq/rmq publishing (new receives, spends, and accounts), multi-machine scanning with (primitive) load-balancing, and an untrusted daemon mode that verifies PoW is valid (whereas normal wallets trust `monerod` responses entirely).
## Proposal
Work on the various tasks outlined above for 40 hours/week over the next 3 months after potential funding. I already use time-tracking software for work; if the hours dip in a given month unexpectedly, the update/milestone will be at the completion of the hours listed above.
The funds were calculated with 65 USD/hour with ~157.41 USD/XMR which is the 9-day exponential moving average on Kraken through 2024/07/11. The rate is up a bit: (1) inflation, (2) volatility protection, and (3) closer in hourly compensation to 2 other contributors.
\ No newline at end of file
---
layout: wip
title: vtnerd full-time 2025 q1/q2
author: Lee Clagett (vtnerd)
date: February 21, 2025
amount: 134.37 XMR
milestones:
- name: Month 1 (160 hours)
funds: 44.79 XMR
done:
status: unfinished
- name: Month 2 (320 hours)
funds: 44.79 XMR
done:
status: unfinished
- name: Month 3 (480 hours)
funds: 44.79
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
3-Months full-time software development on monero "core" components in 2025 q1/q2.
## What
Work primarily on `monerod`, `wallet`, and `monero-lws`. Some of the work to be attempted or investigated:
- Code reviews of monero core PRs
- monerod/monero-lws bug fixes and HackerOne mitigations as they arrive
- Keep existing PRs up-to-date:
- New Serialization routine
- Change from raw pointers to weak_ptrs in levin code
- Socks v5
- P2P SSL Support
- Updating levin callbacks to C++14 moves
- Embargo timeout fix
- Find (possible) memory leak in weak_ptr PR
- Complete work necessary to merge [DANE/TLSA in wallet2/epee](https://github.com/vtnerd/monero/tree/improve/dane_tlsa).
- Adding trust-on-first-use support to wallet2
- Add msgpack support to monerod-ZMQ (requires merging of new serialization system)
- `monero-lws` work:
- Determine a “push” interface for LWS clients (instead of existing poll interface)
- Complete LWS frontend (using `wallet_api.h` as interface) so that wallets can begin using LWS API easily. This is separate from woodser et al working on LWS API within `wallet2` which may be deprecated.
- Add a new utility (to LWS-frontend) that accepts a spend key to report balance+spent transactions of wallet (requested via Github Issues). This will help verify accuracy of LWS endpoints
- Update LWS spec and implementation to support new "carrot" features (view-balance key, etc)
- Update LWS backend to work with fcmp++ experimental branch
- Add a "scale" factor to remote scanning load balancing - send more accounts to systems with faster single thread performance
- Add 64-bit ed25519 code for faster arm64 scanning
- Provide official LWS docker-image
- Provide pre-built binaries
- (Unlikely) - reproducible builds so community members can verify+sign the binary hashes
There is intentionally more work than time allows - to ensure there is always something to work on in the proposal.
## Who
Lee Clagett (vtnerd). I've [had](https://ccs.getmonero.org/proposals/vtnerd-tor-tx-broadcasting.html) [five](https://ccs.getmonero.org/proposals/vtnerd-2020-q4.html) [CCS](https://ccs.getmonero.org/proposals/vtnerd-2021-q1.html), [proposals](https://ccs.getmonero.org/proposals/vtnerd-2023-q3.html) ([last one](https://ccs.getmonero.org/proposals/vtnerd-2024-q3.html)), and [one Magic Grant](https://monerofund.org/projects/Q1Q2_2024_dev_vtnerd).
Some of my biggest features in monero core repo are [Dandelion++](https://github.com/monero-project/monero/pull/6314), [adding supercop ASM speedups to wallet code](https://github.com/monero-project/monero/pull/6337), [ZeroMQ Pub Support for new blocks and transactions](https://github.com/monero-project/monero/pull/6418), and [SSL support to p2p](https://github.com/monero-project/monero/pull/8996).
I've also made a functional LWS wallet scanner under CCS/Magic - which now has a MyMonero compatible REST API (now fully non-blocking to support more responses per thread), admin REST API, LMDB storage, subaddress support, webhook/zmq/rmq publishing (new receives, spends, and accounts), multi-machine scanning with (primitive) load-balancing, and an untrusted daemon mode that verifies PoW is valid (whereas normal wallets trust `monerod` responses entirely).
## Proposal
Work on the various tasks outlined above for 40 hours/week over the next 3 months after potential funding. I already use time-tracking software for work; if the hours dip in a given month unexpectedly, the update/milestone will be at the completion of the hours listed above.
The funds were calculated with 65 USD/hour with ~232.20 USD/XMR which is the 14-day exponential moving average on Kraken through 2025/02/21.
---
layout: wip
layout: cp
title: German translation of Monero Means Money (subtitles) and Sound Money, Safe Mode (subtitles)
author: Wobole
date: June 27, 2021
......@@ -20,6 +20,17 @@ payouts:
amount:
---
## Proposal Update 2024/09/05
- Wobole completed this proposal Jan 22, 2022 as confirmed independantly by 2, native german, community members.
- A partial address was posted in [this payout request](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/237#note_21125).
- The full address was never shared with Luigi or the acting CCS Coordinator at that time.
- Wobole has 1 year from now, to attempt to claim these funds by pasting a _new_ payout address from the same Gitlab account.
- After 2025-09-05 the entire balance (9.9 XMR) will be returned to the General Fund.
---
Hello everybody, this is Wobole again :)
## What and Why
......
---
layout: wip
layout: cp
title: xiphon full-time coding (3 months)
author: xiphon
date: 6 Feb 2021
......@@ -26,6 +26,19 @@ payouts:
amount:
---
### Proposal closed
The remaining funds (121XMR) have been donated to the general fund.
- Xiphon has not been seen/heard of for >2 years.
- This proposal has been abandonned.
- Xiphons total earnings from the CCS (year/xmr/price on day of payout(s))
- 2019: 190, $12533.36 USD
- 2020: 1051, $86310.75 USD
- 2021: 222.0, $56598.92 USD
- Should they re-appear they are welcome to create a fresh proposal.
# What
Would love to prolong my Monero coding for another 3 months and dedicate 40h/week, i.e. to work full-time.
......
---
layout: wip
title: XMRChat - a service for content creators to receive messages and tips in Monero.
author: FiatDemise
date: December 8, 2024
amount: 114
milestones:
- name: Milestone 1 - MVP (minimum viable product) using LWS
funds: 40
done: August 4, 2024
status: finished
- name: Milestone 2 - video display of xmrchats with Streamyard and OBS, find creator page, private xmrchats, making repo open source
funds: 30.56
done: November 20, 2024
status: finished
- name: Milestone 3 - creator specific minimum tip amount, links to more creator content + new tab UI for that and other settings, audio tip received notification, How To section in FAQ, old xmrchats expiration, admin page, site monitoring.
funds: 17
done:
status: unfinished
- name: Milestone 4 - on screen special effects and notifications based on tip tier, moderator / cohost page, feature currently live streams, fee system
funds: 27
done:
status: unfinished
payouts:
- date: 19 March 2025
amount: 70.56
- date:
amount:
- date:
amount:
- date:
amount:
---
_Note: 70.56XMR has been awarded to XMRChat from [TipXMR](https://ccs.getmonero.org/proposals/tipxmr.live.html)_
Who?
Douglas Tuman - Host of popular YouTube show, Monero Talk. Host of weekly show Monerotopia livestreamed in multiple platforms. Creator of Monerotopia annual conference - monerotopia.com. Creator of the Copamonero annual Monero-sponsored soccer tournament - copamonero.com. Sets up booth/tent at Libertarian party conventions and Porcfest to spread Monero awareness. Creator of gratuitas.org coffee beans business (and coffee brewer/bartender at XMR meetups/conventions. Founder of xmrbazaar.com online, p2p marketplace. Founder of plug-n-play XMR node implementation, the Nodo - moneronodo.com. X handle @DouglasTuman.
FiatDemise - Guy with project management experience that joined the Monero community in 2020. Helped save Kuno (kuno.anne.media) and volunteers time there as a moderator. Contributed to testing and provided feature feedback for xmrbazaar. Created a Monero for All brochure that is available in several languages and was distributed at Porcfest 2024. X handle @FiatDemise.
Saeed - Front-end web developer found via Monero Jobs & Proposals Telegram group, GitHub https://github.com/sa8ab. Developed dex alcor.exchange, github.com/avral/alcor-ui. Created raceroms.com. Has a network of other front and back end developers he partners with.
What?
XMRChat is website that provides content creators with a service, allowing them a way to receive messages and tips in Monero. We launched https://xmrchat.com/ on 8/4/2024, using it for the first time in MoneroTopia episode 177, where Doug interviewed Saeed, going over the project and what the site is capable of. https://www.youtube.com/watch?v=f1sy8ICsgBQ. We are looking to raise a total amount of 114 XMR at this time, split in 4 milestones as seen above.
Website: https://xmrchat.com/
X Account: https://x.com/xmr_chat
Code: https://github.com/sa8ab/xmrchat
How we got started?
In early 2024, FiatDemise was watching a streamer, one that accepts tips from viewers and reads their messages as part of their show. They accept fiat using YouTube Superchats, Rumble Rants, and Streamlabs. They publicly stated they’d like to accept crypto too. FiatDemise started a conversation with their staff to try to get them to use Luke Smith’s Shadowchat. FiatDemise volunteered to pay for a company to install and configure it too. After some promising back and forth, FiatDemise got a response saying the team’s web dev / admin was too busy with current projects and they didn’t want to devote any time towards installing or managing Shadowchat. FiatDemise learned that the market wanted a very simple solution that doesn’t require any installation, hosting, or technical knowledge.
At the time, FiatDemise was volunteering as a tester for xmrbazaar and raised the idea of a simple, hosted superchat solution in that Matrix group. Doug supported it right away, and we began working on requirements and giving shape to the vision with a Balsamiq wireframe. We worked with one developer to create a rough proof of concept. Then we found Saeed, a talented developer who could take the project to the next level. We saw the limitation of RPC, only being able to monitor incoming tips for one wallet, which wouldn’t work with the goal of hosting a solution for many content creators. After research, trial and error, and consultations with VTNerd and Radanne, we got LWS to work. After several more updates, the MVP was launched.
---
layout: wip
layout: cp
title: Monero Outreach Round 3
author: xmrhaelan
date: 22 May 2019
......@@ -22,10 +22,14 @@ payouts:
amount: 36.66
- date: 23 November 2020
amount: 36.67
- date: TBD
- date:
amount: 36.67
---
### Proposal closure/repurposed
_All remaining funds (36.67 XMR) have been transferred to [Monerotopia 2024 marketing and publicity](https://ccs.getmonero.org/proposals/monerotopia2024publicity.html)_
A big thanks again to everyone who supported Round 2 of funding for Monero Outreach! Final report can be found [here](https://www.reddit.com/r/Monero/comments/bonpt3/monero_outreach_round_2_ccs_final_report_see_what/).
We have made significant progress in our ability to support and enhance the outreach efforts of the Monero Community, and are beginning to receive requests for support from various areas of the Monero ecosystem. We are honored to be able to support Monero in this way, and we look forward even more to what is ahead!
......
---
layout: wip
layout: cp
title: xmrSale Payment Processor Development
author: xmrsale
date: 10 August, 2021
......@@ -15,8 +15,8 @@ milestones:
status: finished
- name: Zeronode mode viewkeys
funds: 20
done:
status: unfinished
done: 10 March 2021
status: finished
- name: RPC via tor hidden service
funds: 10
done:
......@@ -30,14 +30,18 @@ payouts:
amount: 25
- date: 22 November 2021
amount: 10
- date:
amount:
- date: 17 March 2022
amount: 20
- date:
amount:
- date:
amount:
---
### Proposal closed
The remaining funds (30XMR) have been absorbed by https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/374
# What
[xmrSale](https://github.com/xmrsale/xmrSale) is a lightweight Monero payment processor that connects to your own Monero node, striving to be modular and lightweight. xmrSale has an accessible API written in python that talks to your own Monero node, uses RPC to generate new addresses, and monitors payment success with your own copy of the Monero blockchain.
......