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 705 additions and 48 deletions
---
layout: cp
title: selsta part-time monero development (3 months)
title: selsta part-time monero development (3 months) (1)
author: selsta
date: 8 Apr 2021
amount: 76
......
---
layout: cp
title: selsta part-time monero development (3 months)
title: selsta part-time monero development (3 months) (2)
author: selsta
date: 8 Jul 2021
amount: 90
......@@ -51,7 +51,7 @@ selsta, I have been contributing to monero since around 2018 with over 420 merge
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-1.html
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-1p.html
If funded I will provide monthly updates in the CCS comment section.
......
---
layout: cp
title: selsta part-time monero development (3 months)
title: selsta part-time monero development (3 months) (3)
author: selsta
date: 7 Oct 2021
amount: 75
......@@ -45,7 +45,7 @@ selsta, I have been contributing to monero since around 2018 with over 470 merge
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-2.html
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-2p.html
If funded I will provide monthly updates in the CCS comment section.
......
---
layout: cp
title: selsta part-time monero development (3 months)
title: selsta part-time monero development (3 months) (4)
author: selsta
date: 12 Jan 2022
amount: 95
......@@ -45,7 +45,7 @@ selsta, I have been contributing to monero since around 2018 with over 500 merge
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-2.html
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-3p.html
If funded I will provide monthly updates in the CCS comment section.
......
---
layout: fr
title: selsta part-time monero development (3 months)
layout: cp
title: selsta part-time monero development (3 months) (5)
author: selsta
date: 18 Apr 2022
amount: 75
milestones:
- name: May
funds: 33% (25 XMR)
done:
status: unfinished
done: 31 May 2022
status: finished
- name: June
funds: 33% (25 XMR)
done:
status: unfinished
done: 30 June 2022
status: finished
- name: July
funds: 33% (25 XMR)
done:
status: unfinished
done: 31 July 2022
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 13 June 2022
amount: 25
- date: 6 July 2022
amount: 25
- date: 4 August 2022
amount: 25
---
## What
......@@ -44,7 +44,7 @@ selsta, I have been contributing to monero since around 2018 with over 525 merge
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-4.html
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-4p.html
If funded I will provide monthly updates in the CCS comment section.
......
---
layout: cp
title: selsta part-time monero development (3 months) (6)
author: selsta
date: 30 July 2022
amount: 110
milestones:
- name: August
funds: 33% (37 XMR)
done: 31 August 2022
status: finished
- name: September
funds: 33% (37 XMR)
done: 30 September 2022
status: finished
- name: October
funds: 33% (36 XMR)
done: 31 October 2022
status: unfinished
payouts:
- date: 5 September 2022
amount: 37
- date: 4 October 2022
amount: 37
- date: 6 November 2022
amount: 36
---
## What
- Focus on preparing the next network update (Testing Ledger and Trezor integration, prepare v0.18.1.0)
- Smaller dev work on CLI and GUI
- Put effort where necessary
- Testing and reviewing pull requests (CLI, GUI, site)
- Monero release engineering for CLI and GUI
- Organizing what goes into a release
- Compiling CLI and GUI, packaging for distribution
- Writing release notes
- Misc work (user support, issue tracker maintanace, HackerOne)
## Who
selsta, I have been contributing to monero since around 2018 with over 572 merged commits. Here is a list of my previous work:
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-5p.html
If funded I will provide monthly updates in the CCS comment section.
## Proposal
Work for 30 hours per week over the next 3 months (from August to end of October) at a rate of 45€ / hour. At 148€ / XMR (14 day EMA) this makes 110 XMR.
---
layout: cp
title: selsta part-time monero development (3 months) (7)
author: selsta
date: 5 November 2022
amount: 135
milestones:
- name: November
funds: 33% (45 XMR)
done: 30 November 2022
status: finished
- name: December
funds: 33% (45 XMR)
done: 31 December 2022
status: finished
- name: January
funds: 33% (45 XMR)
done: 31 January 2023
status: finished
payouts:
- date: 9 December 2022
amount: 45
- date: 13 January 2023
amount: 45
- date: 13 February 2023
amount: 45
---
## What
- Focus on setting up community node infrastructure: https://github.com/monero-project/monero/issues/8624
- Smaller dev work on CLI and GUI
- Put effort where necessary
- Testing and reviewing pull requests (CLI, GUI, site)
- Monero release engineering for CLI and GUI
- Organizing what goes into a release
- Compiling CLI and GUI, packaging for distribution
- Writing release notes
- Misc work (user support, issue tracker maintanace, HackerOne)
## Who
selsta, I have been contributing to monero since around 2018 with over 595 merged commits. Here is a list of my previous work:
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-6p.html
If funded I will provide monthly updates in the CCS comment section.
## Proposal
Work for 30 hours per week over the next 3 months (from November to end of January) at a rate of 45€ / hour. At 120€ / XMR this makes 135 XMR.
---
layout: cp
title: selsta part-time monero development (3 months) (8)
author: selsta
date: 28 January 2023
amount: 102
milestones:
- name: Februrary
funds: 33% (34 XMR)
done: 28 February 2023
status: finished
- name: March
funds: 33% (34 XMR)
done: 31 March 2023
status: finished
- name: April
funds: 33% (34 XMR)
done: 10 May 2023
status: finished
payouts:
- date: 14 March 2023
amount: 34
- date: 10 April 2023
amount: 34
- date: 11 May 2023
amount: 34
---
## What
- Focus on major release v0.18.2.0 (P2Pool hard-fork support, Dandelion++ fixes, RandomX refactor, RingCT cache, network stability improvements)
- Smaller dev work on CLI and GUI
- Put effort where necessary
- Testing and reviewing pull requests (CLI, GUI, site)
- Monero release engineering for CLI and GUI
- Organizing what goes into a release
- Compiling CLI and GUI, packaging for distribution
- Writing release notes
- Misc work (user support, issue tracker maintanace, HackerOne)
## Who
selsta, I have been contributing to monero since around 2018 with over 615 merged commits. Here is a list of my previous work:
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-7p.html
If funded I will provide monthly updates in the CCS comment section.
## Proposal
Work for 30 hours per week over the next 3 months (from Februrary to end of April) at a rate of 45€ / hour. At 159€ / XMR (14-day EMA) this makes 102 XMR.
---
layout: cp
title: selsta part-time monero development (3 months) (9)
author: selsta
date: 1 May 2023
amount: 117
milestones:
- name: May
funds: 33% (39 XMR)
done: 5 June 2023
status: finished
- name: June
funds: 33% (39 XMR)
done: 2 July 2023
status: finished
- name: July
funds: 33% (39 XMR)
done: 13 August 2023
status: finished
payouts:
- date: 8 June 2023
amount: 39
- date: 6 July 2023
amount: 39
- date: 16 August 2023
amount: 39
---
## What
- Start the planning of a network upgrade with RandomX changes (https://github.com/monero-project/monero/issues/8827) and Bulletproofs++
- Smaller dev work on CLI and GUI
- Put effort where necessary
- Testing and reviewing pull requests (CLI, GUI, site)
- Monero release engineering for CLI and GUI
- Organizing what goes into a release
- Compiling CLI and GUI, packaging for distribution
- Writing release notes
- Misc work (user support, issue tracker maintanace, HackerOne)
## Who
selsta, I have been contributing to monero since around 2018 with over 628 merged commits. Here is a list of my previous work:
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-8p.html
If funded I will provide monthly updates in the CCS comment section.
## Proposal
Work for 30 hours per week over the next 3 months (from May to end of July) at a rate of 45€ / hour. At 138.5€ / XMR this makes 117 XMR.
---
layout: cp
title: "koe: Seraphis Library Work 2"
author: koe
date: 26 Dec 2022
amount: 125
milestones:
- name: PoC
funds: 100% (125 XMR)
done: 31 March 2023
status: finished
payouts:
- date: 6 April 2023
amount: 125
---
## Intro
Hi all, I [closed out](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/338#note_20190) my previous [Seraphis Library Work CCS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/338) after consuming all the hours. There are additional tasks I would like to work on. For background on this CCS, please see the links in the previous sentence.
In the previous CCS I finished adding new things to the seraphis library, and from here on mainly have cleanup tasks left.
## Continuing work
Here are the tasks I hope to finish by the end of this CCS.
- Complete the 'final draft' of my seraphis library (finish my cleanup and review pass).
- Update the [Seraphis paper draft](https://github.com/UkoeHB/Seraphis).
This CCS should be a long-term one, with intermittent hours spent on miscellaneous Monero R&D tasks and working with Monero devs on seraphis library reviews and PRs. I may also update the seraphis library to replace BP+2 with BP++ at some point.
## Funding
- Rate: 50 USD + 0.2 XMR
- Hours: 240hrs
- XMR equivalent: 48 + (50\*240)/USD\_EXCHANGE\_RATE XMR
- USD\_EXCHANGE\_RATE: set from 14-day EMA on a major exchange
- 155 USD/XMR at 2325 UTC 01/11/2023 w/ 14-day EMA on Kraken -> 125 XMR total
---
layout: cp
title: "koe: Seraphis Library Work"
author: koe
date: 18 Aug 2022
amount: 122
milestones:
- name: PoC
funds: 100% (122 XMR)
done: 26 December 2022
status: finished
payouts:
- date: 30 December 2022
amount: 122
---
## Intro
Hi all, I [closed out](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/314#note_18262) my previous [Seraphis Wallet PoC CCS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/314) after consuming all the hours. There are additional tasks I would like to work on. For background on this CCS, please see the links in the previous sentence.
In the last CCS period I decided that an actual wallet proof-of-concept is too ambitious. My more modest/realistic goal is to complete the Seraphis library so wallets can be (relatively) easily built.
## Continuing work
Here are the tasks I hope to finish by the end of this CCS (a continuing refrain, maybe some day my list will have no more items). As before, these will be implemented in my [seraphis_lib](https://github.com/UkoeHB/monero/tree/seraphis_lib) branch.
- Legacy/Seraphis integration so old cryptonote-style enotes can be spent in Seraphis transactions.
- Seraphis-style coinbase transaction type.
- Test out tevador's [x25519 library](https://github.com/tevador/mx25519) for enote ECDH instead of ed25519, which may speed up enote scanning by a non-trivial amount (>10%). (big thanks to @tevador for putting that library together)
- Miscellaneous code cleanup (mostly update/add comments, cleanup TODOs).
- Update the [Seraphis draft](https://github.com/UkoeHB/Seraphis), which I have not touched for 6 months.
As usual, I will also lump all the miscellaneous Monero R&D tasks that I work on into this CCS (e.g. in the last period I did more review/work on multisig security patches, among other things).
## Funding
- Rate: 50 USD + 0.2 XMR
- Hours: 12 weeks @ 20hr/wk = 240hrs
- XMR equivalent: 48 + (50\*240)/USD\_EXCHANGE\_RATE XMR
- USD\_EXCHANGE\_RATE: set from 14-day EMA on a major exchange
- 163 USD/XMR at 0045 UTC 08/18/2022 w/ 14-day EMA on Kraken -> 122 XMR total
If I require more time, and the community supports it, then I may make another proposal to extend the hours.
---
layout: wip
title: "koe: Seraphis Ongoing Support"
author: koe
date: 31 March 2023
amount: 163.7
milestones:
- name: PoC
funds: 100% (163.7 XMR)
done:
status: unfinished
payouts:
---
## Intro
Hi all, I [closed out](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/369#note_21022) my previous [Seraphis Library Work 2 CCS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/369) after consuming all the hours. There are additional tasks I would like to work on. For background on this CCS, please see the links in the previous sentence.
In the previous CCS I refined the seraphis library to a satisfying state. It can now be considered in 'final draft' form.
## Continuing work
Here are the tasks I hope to finish by the end of this CCS.
- Update the [Seraphis paper draft](https://github.com/UkoeHB/Seraphis). I will split the current draft into two papers, one focused on the core Seraphis abstraction and the other focused on the current implementation using Jamtis. My goal is to get those papers to a place where I can collaborate with (as yet undetermined) security researchers to add proper security analysis.
- Support the seraphis migration workgroup with focused architecture design work, and possibly contribute development work to that effort.
- Build a demo for a secure and efficient escrowed market using Monero 2-of-3 multisig with the seraphis library.
- As usual, participate in ongoing Monero R&D discussions and tasks.
## Funding
It has been a year and a half since I opened my first Seraphis-related CCS. I feel I have reached a level of proficiency with Monero research and development to justify asking for a raise of `10 USD + 0.1 XMR / hr` in this CCS.
- Rate: 60 USD + 0.3 XMR
- Hours: 240hrs
- XMR equivalent: 72 + (60\*240)/USD\_EXCHANGE\_RATE XMR
- USD\_EXCHANGE\_RATE: set from 14-day EMA on a major exchange
- 157 USD/XMR at 2135 UTC 03/31/2023 w/ 14-day EMA on Kraken -> 163.7 XMR total
---
layout: cp
title: "koe: Seraphis Wallet Proof-of-Concept 2"
author: koe
date: 1 May 2022
amount: 155
milestones:
- name: PoC
funds: 100% (155 XMR)
done: 18 August 2022
status: finished
payouts:
- date: 24 October 2022
amount: 155
---
## Intro
Hi all, I [closed out](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/290#note_16046) my previous [Seraphis Wallet PoC CCS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/290) after consuming all the hours. There are additional tasks I would like to work on. For background on this CCS, please see the links in the previous sentence.
## Continuing work
Here are the tasks I hope to finish by the end of this CCS. As before, these will be implemented in my [seraphis_lib](https://github.com/UkoeHB/monero/tree/seraphis_lib) branch.
- Add tx builder plumbing for _discretized_ tx fees (see the [04/20/22 MRL meeting](https://github.com/monero-project/meta/issues/691) for a discussion).
- Consider using 16-byte address indices (instead of 7), with 2-byte encoded address index MACs (instead of 1).
- Implement a robust 'input selection' solver that takes advantage of statically-determinable tx weights.
- Implement a maximally-efficient and generic enote-scanning workflow.
- Build a wallet proof-of-concept that demonstrates all the 'transaction engineering' capabilities and implementation modularity of Seraphis/Jamtis. My goal is to have unit tests representing all the main workflows possible with Seraphis, and all the main wallet implementations necessary (i.e. mock-ups of interfaces that could potentially be developed into full-fledged wallet software).
- Test out using x25519 for enote ECDH instead of ed25519, which may speed up enote scanning by a non-trivial amount (>10%).
- Miscellaneous code cleanup (mostly update/add comments, cleanup TODOs).
As usual, I will also lump all the miscellaneous Monero R&D tasks that I work on into this CCS (e.g. in the last period I did more review/work on multisig security patches, among other things).
## Funding
- Rate: 50 USD + 0.2 XMR
- Hours: 16 weeks @ 20hr/wk = 320hrs
- XMR equivalent: 64 + (50\*320)/USD\_EXCHANGE\_RATE XMR
- USD\_EXCHANGE\_RATE: set from 14-day EMA on a major exchange
- 175 USD/XMR at 0100 UTC 05/16/2022 w/ 14-day EMA on Kraken -> 155 XMR total
If I require more time, and the community supports it, then I may make another proposal to extend the hours.
---
layout: wip
layout: cp
title: "koe: Seraphis Wallet Proof-of-Concept"
author: koe
date: 23 February 2022
......@@ -7,9 +7,11 @@ amount: 81.4
milestones:
- name: PoC
funds: 100% (81.4 XMR)
done:
status: unfinished
done: 25 April 2022
status: finished
payouts:
- date: 12 May 2022
amount: 81.4
---
## Intro
......
......@@ -67,4 +67,12 @@ I would like to expand more this section since it is a subject close to my heart
### Costs
If milestones are not modified, I'll ask 11 XMR (~700 euros) - fixed price.
\ No newline at end of file
If milestones are not modified, I'll ask 11 XMR (~700 euros) - fixed price.
### Proposal transfer
This proposal will be transferred to recanman who will enjoy an exclusivity period of 5 months to show reasonable progress in completing this proposal. They will receive payments for completed milestones directly.
SerHack: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/402#note_22039
>To consider the CCS completed, all the issues mentioned in the CCS must be completed: recanman will need to push changes to monero-integrations repositories and after reviewing the PRs, I'll close the issues.
......@@ -7,23 +7,33 @@ amount: 110.55 XMR
milestones:
- name: 1 Initial setup
funds: 20.10 XMR
done:
status: unfinished
done: 29 May 2022
status: finished
- name: 2 Profitability calculator
funds: 16.75 XMR
done:
status: unfinished
- name: 3 Measurements
funds: 36.85 XMR
- name: 3.1 Measurements mj
funds: 20.10 XMR
done: 22 July 2022
status: finished
- name: 3.2 Measurements Endor
funds: 16.75 XMR
done:
status: unfinished
- name: 4 Automation
funds: 36.85 XMR
- name: 4.1 Automation mj
funds: 20.10 XMR
done: 24 November 2022
status: finished
- name: 4.2 Automation Endor
funds: 16.75 XMR
done:
status: unfinished
payouts:
- date:
amount:
- date: 2 July 2022
amount: 20.1
- date: 28 December 2022
amount: 40.2
- date:
amount:
- date:
......
---
layout: cp
title: Robust and modular wallet-rpc library
date: Sep 10, 2024
author: Spirobel
amount: 100
milestones:
- name: Deved + prepayment for first month
funds: 20 XMR
done: 9 October 2024
status: finished
- name: First month
funds: 30 XMR
done: 23 December 2024
status: finished
- name: Second month + value commitment
funds: 50 XMR
done: 19 February 2025
status: finished
payouts:
- date: 16 October 2024
amount: 20
- date: 28 February 2025
amount: 80
---
# Robust and modular wallet-rpc library
## Who
**Spirobel**
References:
#### found and reported a "pay what you want" vulnerability in AcceptXMR
https://x.com/spirobel/status/1672479215512588288
https://github.com/busyboredom/acceptxmr/issues/64
#### open sourced a Patreon like tool for Monero
https://x.com/spirobel/status/1595949928634667008
https://github.com/spirobel/monero-discourse-subscriptions
#### open sourced a merchant focused wallet-rpc
https://x.com/spirobel/status/1596299822516285440
https://github.com/spirobel/monerochan-merchant-rpc
#### implemented a Monero Browser wallet extension
https://www.youtube.com/watch?app=desktop&v=4DLcsQ45zoE
Contact: twitter.com/spirobel
## What
Result: A robust and modular wallet-rpc library, implemented in Rust with WebAssembly (WASM) as the primary target. This library aims to provide a flexible foundation for Monero wallet functionality. The deliverable for this proposal will be:
1. the first part of the wallet-rpc library that can sync transactions and works reliably with remote nodes.
2. A checkout flow built with this library. This is meant to be used, not just to demonstrate the features.
3. Detailed documentation for the library, the relationship between nodes and wallets during the syncing process and a guide on how to use this to implement monero payment gateways.
### Implementation
list of initial tasks:
- create function to turn address and private viewkey into viewpair
- create function to scan transaction with sub functions
- verify that there is no timelock present
- calculate transaction amount
- clarify responsibility of burning bug prevention for the caller
- implement transaction fetching and storage
- implement burning bug prevention in the checkout flow
- write unit tests, document and publish the library
- implement UI for the checkout flow
this task list is not exhaustive and subject to change
## Why
As discussed as far back as two years ago: https://github.com/seraphis-migration/strategy/issues/2
The wallet2 Monero library is a 15k lines CPP file. The official monero repo does not contain a deliverable that is easily linkable from other programs. Every project that is a wallet or contains wallet-like functionality (payment processors, hardware wallets, point of sale terminals) needs to implement its own wrapper to expose a C ABI.
This results in collectively wasted hours and headaches. It increases supply chain risk and makes building things with Monero harder. As a result, projects get more expensive, take longer or don't happen at all.
This library aims to counteract the issues and limitations of wallet2.cpp by directly targeting wasm.
Using wasm as the main target means that this library is forced to be implemented in a way that meets the expectations outlined here: https://github.com/seraphis-migration/strategy/issues/1
The benefits of this approach:
### 1. It will be easily linkable
WASM is a very constrained target. There is no garbage collection and multi threading. Getting code to run there means having to write it in a way that is easy to interact with from any language and in any environment.
### 2. It will be more robust
The current monero wallet-rpc is at times unresponsive, because its concurrency mixes the responses of the local rpc with the network interacting with the node. More details in the [monero-playground repository](https://github.com/spirobel/monero-playground). The WASM target constraints ensure that this library decouples the concurrency and networking from the wallet code. The result will be more robust.
### 3. It will be more flexible and not tied to any platform / target
Wallet code deals with the most sensitive data. It should not have unnecessary dependencies or bloat. To give a practical example: monero currently vendors a 4000 lines of code [logging library](https://github.com/monero-project/monero/blob/master/external/easylogging%2B%2B/easylogging%2B%2B.cc) that introduces a dependency on signals. The WASM target constraint means that things like that can't and wont be introduced into this library.
## Milestones and Timeline
value commitment:
The 3 deliverables outlined in the **What** section are the promised outcome of this proposal. Any time left over from the time commitment will be used to further advance the road map. The value commitment is due for the milestone of the second month.
time commitment:
- 100 hours per month for two months (100 hours total)
- Compensation: 50 XMR per month (100 XMR total)
- Total compensation: 100 XMR
## Future Roadmap
The next step on the road map is to add transaction building and signing functionality to the library and migrate [the browser wallet](https://www.youtube.com/watch?v=4DLcsQ45zoE) to it.
My endgame is to **remove all friction from the privacy enabled web shopping experience**. Currently most **Monero shoppers** have to copy and paste addresses from the tor browser into their wallets. This opens the door to unnecessary opsec failures, as it is easy to get confused and intimidated by long strings of random numbers.
**A core part of staying private and safe online is to compartmentalize identities.** Qubes OS made some advancements in improving the UX of this activity by coloring different windows that are tied to different identities in a unique way.
The reality is, that installing a different operating system is a large ask for the average person. At the same time we need to onboard as many people as possible to these habits, so we can operate safely in the crowd.
The other venue of attack is **using the browser for compartimentalization.** And before anybody complains: no this does not involve untrusted javascript frontend code.
There is a big difference between a browser wallet and web wallet. A web wallet is a flawed experiment that is borderline custodial, as it runs wallet code inside the context of a website. This is not to be confused with a browser wallet.
**A browser wallet runs trusted code as a compartmentalized, constrained program inside of a sandbox.**
There is a massive opportunity here to reduce friction by making it easy to separate online identities. The TOR browser currently enables the use of one separate TOR circuit for each tab. **Imagine we have one monero address per tab that is used for login and to send and receive payments.** It makes it much harder to mess up.
One last concern that comes up is that there might be zero day exploits in the browser, as it exposes a potentially larger attack surface. This can be mitigated by making the wallet a multisignature wallet and **using a second device like an android phone or a monero seedsigner to authorize every transaction.**
This means two devices need to be compromised to capture funds, which is unlikely.
---
layout: wip
layout: cp
title: Translation and review of GUI Wallet, monero-site, Monero Means Money (subtitles) and Sound Money, Safe Mode (subtitles) to Italian.
author: staff91
date: November 18, 2020
......@@ -20,6 +20,12 @@ payouts:
amount:
---
## Proposal Closure
The remaining funds (28 XMR) have been donated to the General Fund.
---
# About this Proposal
Translation and review of the [GUI Wallet](https://translate.getmonero.org/projects/monero/gui-wallet/), [monero-site](https://translate.getmonero.org/projects/getmonero/monero-site/), [Monero Means Money (subtitles)](https://translate.getmonero.org/projects/community/monero-means-money/) and [Sound Money, Safe Mode (subtitles)](https://translate.getmonero.org/projects/community/sound-money-safe-mode-subtitles/) to Italian.
......
---
layout: wip
title: SyntheticBird Cuprate Arti integration and development (2 months)
author: SyntheticBird
date: March 9, 2025
amount: 52.5
milestones:
- name: April
funds: 50% (26 XMR)
done:
status: unfinished
- name: May and completion of Arti integration
funds: 50% (26.5 XMR)
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
---
# Who
I am [SyntheticBird](https://github.com/SyntheticBird45), Cuprate contributor.
# What
Cuprate is currently in alpha version and a lot of features are planned on the roadmap up to beta phase. One of the features present on this roadmap, and that was [originally presented when announcing Cuprate](https://github.com/Cuprate/cuprate/blob/fc9b077d946fe8b7746c45ae8b299a87b2014cbf/readme.md?plain=1#L57), is native support for Tor network. This CCS proposal intend to fulfill this milestone.
I will work for an estimated 2 months, from April to end of May, on Cuprate with the goal of implementing native Tor support into `cuprated` through the `arti-client` crate and other miscellaneous improvements.
At the end of this CCS, testers will be able to:
- Bootstrap Tor network within Cuprate or use Tor system daemon.
- Use Tor for outbound clearnet connections.
- Natively connect to onion monero nodes.
- Generate an onion service for accepting inbound Tor connections.
# Tasks
The planned set of tasks to complete can be found at this Github gist: https://gist.github.com/SyntheticBird45/4c554d3c1e7ae6f8d237d7dd49c2d2f0
It is subject to change but overall the required work can be separated into 3 categories:
### 1. Alternative network integration into P2P components.
Currently, Some P2P components have limited support for alternative network rules. This will require modifying `AddressBook`, `Connector`, `HandshakeBuilder`, `cuprate-dandelion` crate and `cuprated`'s dandelion implementation, and others to be *anonymization-network-aware*. After this work, we will define a new `NetworkZone` called `Tor` to connect to onion monero nodes.
### 2. Implementation of Arti and Tor Daemon support
Implementing `arti-client` inside `cuprated` and `cuprate-p2p{-*}`. Configurations, initialization, bootstrapping and launching onion services if requested. System tor daemon will also be supported.
### 3. Documentation
Update [Architectural book](https://architecture.cuprate.org) and [User book](https://user.cuprate.org/)
# Additional work
In the event that all guaranteed items are completed before the 2 months, I will spend my remaining time assisting (Issues, PRs and Reviews) on whatever is agreed is highest priority, or working on the following items:
- Custom Allocator support (Performance improvements for Musl based linux distributions and potentially minor improvements on other OSs)
- SOCKS5 proxy support for p2p
- Fjall database integration
- Related documentation
# Milestones
### 1. First month
26 XMR
### 2. Second Month and completion of main tasks
26.5 XMR
# Licensing
All the works completed under this CCS will be delivered to the [`Cuprate/cuprate.git`](https://github.com/Cuprate/cuprate) github repository. This work will follow the current repository licensing:
- All work inside `/binaries` is licensed under `AGPL-3.0-only`.
- The rest of the root and crates are licensed under `MIT`.
For more information about the Cuprate github organization, please [visit the organization page](https://github.com/Cuprate)
# Funding
I will be working 30 hours per week during 8 weeks at 45\$/hr - 205\$/XMR.
30×8=240 | 240×45=10800 | 10800÷205=52.5
Total: 52.5 XMR
---
layout: wip
layout: cp
title: "tipxmr.live - a non-custodial livestream donation service for OBS"
author: AlexAnarcho and hundehausen
date: September 16, 2020
......@@ -7,25 +7,47 @@ amount: 72
milestones:
- name: Milestone 1 - Basic setup of webpack with monero javascript and react
funds: 2% (1.44 XMR)
done:
status: unfinished
done: 17 March 2022
status: completed
- name: Milestone 2 - Working Prototype with implemented WASM wallet and front-end mockups
funds: 48% (34.56 XMR)
done:
status: unfinished
done: 21 December 2024
status: completed
- name: Milestone 3 - Finished product and launch of serivce
funds: 50% (36 XMR)
done:
status: unfinished
done: 21 December 2024
status: completed
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 17 March 2022
amount: 1.44
- date: 12 February 2025
amount: 70.56
---
## Proposal deprecation / Repurposing of funds (21st Dec, 2024)
AlexAnarcho and hundehausen shared a [candid update](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/524#note_27732) regarding progress of TipXMR. Exerpt below:
>We were young and naive and thought "how hard can it be to code this up" - harder than we thought it turned out.
>
>We had very high standards, trying to use WASM wallets on the client-side where no info is leaked to the hoster of the TipXMR service, but this lead to a high barrier - which in turn lead to us never shipping anything
>
>[...]
>
>We are okay to deprecate the TipXMR CCS proposal and pass our collected funds on to this XMRChat proposal.
The remaining funds from:
* Milestone 2 - Working Prototype with implemented WASM wallet and front-end mockups (34.56XMR)
* Milestone 3 - Finished product and launch of serivce (36XMR)
Will be rewarded to https://xmrchat.com/ - [source](https://github.com/sa8ab/xmrchat)
Who instead of implementing a WASM wallet to not share view keys with the service host have performed the following tasks deemed to be of the same value/importance:
* Integrated monero-lws to handle multiple streamer view-keys.
* extra misc. features such as a personal donation page with comments attatched.
# CCS Proposal: tipxmr.live - a non-custodial livestream donation service for OBS
......