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
Commits on Source (645)
Showing
with 1112 additions and 26 deletions
---
layout: wip
title: "0xfffc full-time C++ development (3 months, Jan, Feb, Mar, 2025)"
author: 0xfffc
date: December 13, 2024
amount: 111
milestones:
- name: 160 hours
funds: 37
done:
status: unfinished
- name: 160 hours
funds: 37
done:
status: unfinished
- name: 160 hours
funds: 37
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
### What
The bulk of my focus will be on opportunities related to performance improvement. To find out performance improvement opportunities a performance test suite is necessary for the Monero project. Here is a list of tasks I have on my todo list:
- Bandwidth-Efficent Transaction Propagation Usage: Work on the @boog900 proposal ( https://github.com/monero-project/monero/issues/9334 ). And reduce the communication load between peers when syncing. The final goal is to merge a PR that uses this mechanism in Monero P2P subsystem.
- Exclusive incoming ip: --exclusive-incoming-ip flag: (a) Require --add-exclusive-node to be set. (b) Be able to be set multiple times.
- Cleanup the sleepwait: Remove this _sleep_wait_ and change it to condition variable: https://github.com/monero-project/monero/blob/cc73fe71162d564ffda8e549b79a350bca53c454/src/daemon/daemon.cpp#L198
- Sync time estimation: When calculating how long it will take to finish the sync, is uses a number of blocks. Example: 200 blocks remaining, synced 20 blocks in 1 min = 10 mins remaining. It should use the size, instead of the block number.
- Performance benchmarks. The performance benchmark test I am working on right now is stress testing Monerod under an intense load that tries to mimic a real-world heavy node. Right now it is in very early shape. The end goal is to mimic real-world wallet usage on the Monero daemon.
- Completion of Read/Write Lock PR [#9181](https://github.com/monero-project/monero/pull/9181). PR 9181 is a huge change to the core of the blockchain implementation of the Monero project. It requires a lot of careful analysis and testing. Task 1 and Task 2 are kind of depend on each other. I use benchmarking results from task 1 to test/improve/debug 9181. @jeffro256_ has implemented an important and sensitive part of the 9181 code and has improved the PR with his suggestions.
- Seraphis wallet LMDB storage. Based on our discussion in the IRC #monero group, it seems porting the entire wallet2 storage to LMDB at this point is not a wise decision. Instead of that, we should start implementing the Seraphis wallet cache with LMDB. Once I am finished with Task 1 and 2, my next big goal is to start focusing on this task. The target of this task is to have Seraphis wallet only using LMDB as its cache/storage engine.
- Static analysis. This task hasn't been finished from my previous CCS by the time I am submitting this CCS. I am hopeful I will finish it before the end of my previous CCS. But in case I am not able to finish it, this is one of the tasks I have on my todo list: "Analyze existing static analyzers (clangd-based analyzer, NASA/ikos, Facebook/infer, etc) and report to @selsta about the possibility of adding one of them as a workflow to our GitHub repository. Target will be running static analysis on submitted PR as workflow."
### Who
I have been contributing to the Monero core repository for the past few months with a total of multiple ([PRs]( https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3A0xFFFC0000+)) merged commits thus far. Some ongoing contributions:
- Helped review multiple [PRs](https://github.com/monero-project/monero/pulls?q=is%3Apr+reviewed-by%3A%40me).
- Implemented Read/Write lock mechanism for core blockchain implementation. [9181](https://github.com/monero-project/monero/pull/9181).
- Helped to review and fix multiple HackerOne reports with @selsta.
A special thanks to all community members who are always available to help me with technical questions.
Previous Proposals:
- [429](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/429)
- [438](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/438)
- [487](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/487)
### Funding
- 37xmr/mth * 3 months = 111xmr
- Schedule: 40hr/week * 12week
Freedom wins.
0xFFFC
---
layout: cp
title: "Monero Signer Resurrection: Reviving and Enhancing the Monero Signing Project"
author: Thor a.k.a vthor a.k.a DiosDelRayo
date: May 24, 2024
amount: 55.38
milestones:
- name: Monero Signer basics on emulator
funds: 5.38 XMR
done: 19 June 2024
status: finished
- name: Monero Signer working with companion Application
funds: 5 XMR
done: 28 July 2024
status: finished
- name: Cleanup and production ready
funds: 35 XMR
done: 12 August 2024
status: finished
- name: Monero-GUI integration
funds: 10 XMR
done: 27 September 2024
status: finished
payouts:
- date: 20 June 2024
amount: 5.38
- date: 29 July 2024
amount: 5
- date: 13 August 2024
amount: 35
- date: 28 September 2024
amount: 10
---
_Note: this proposal has been awarded 55.38 XMR from [MoneroSigner](https://ccs.getmonero.org/proposals/MoneroSigner.html)_
# Monero Signer Resurrection: Reviving and Enhancing the Monero Signing Project
## Proposal
This project has been stagnant since [December 28th, 2023](https://github.com/Monero-HackerIndustrial/polyseed.py/commit/2887588a1ebb6ccc6a48772595891175b5ce3c25). In taking over, I have updated the original proposal to include essential features for the current Monero ecosystem, such as:
Adding UR (Unified Resource) support
Integrating with [polyseed](https://github.com/DiosDelRayo/polyseed-python')
Interfacing with the Monero GUI
I have already made progress on some of these components, visible in my GitHub repositories, listed at the end of the proposal.
I propose to take over and finish the Monero Signer project, which was funded but never really started. After learning about Monero Signer and researching the existing work, I found it to be a stale project that was never truly initiated. I aim to complete the project by delivering what was originally promised, with some modifications to make it more useful and avoid wasting time on potentially unnecessary features.
I will complete all the work myself, as I prefer to move quickly, keep things streamlined, and discard unnecessary elements. Security and usability are my top priorities, followed by features and fancy extras. This approach leads to more secure and maintainable code, better user experience, and reduced documentation needs.
## Features
### Monero Signer
- [x] Monero seed generation by dice rolls (without password)
- [x] Monero seed generation camera (without password)
- [x] Monero seed generation by picking 24 words (without password)
- [x] Polyseed generation by dice rolls
- [x] Polyseed generation by camera
- [ ] Full Polyseed support
- [ ] Wallet import with seed words (Monero/Polyseed)
- [ ] Wallet import with QR code
- [ ] Wallet export via Seed~~/hex~~/QR code
- [ ] View key only wallet export
- [ ] Receive via QR code unsigned transactions
- [ ] Sign transaction
- [ ] Send via QR code signed transaction
Reasoning why this is proposal is without password encryption for monero seeds:
```
On using monero-python there is no password protection implemented and after investigating a little bit,
the reason behind is probably, that the encryption/decryption is not really mad in a "standard" way.
So to be compatible with Monero-CLI and Monero-GUI the encryption must be implemented in CryptoNight and
another propiatary way to add and substract the mask of the CryptoNight password hash.
This will be a rabbit hole I can estimate.
Why not another encryption instead? I dislike to have various standards until nobody knows anymore what and where to use.
A temporary password encryption would in my opinion also only make the things worse on reaching compatibility with the
original implementation. Because now, what to do, support two different standards? Remove the way, people protected the
password of there seeds before?
If there is interest, and somehow funding for it I will implement it later in the monero-python fork (the original was archived) for MoneroSigner. But until then password encryption for seed will only supported for Polyseed.
```
### Monerosigner companion application (Desktop):
- [ ] Prepare unsigned transaction
- [ ] Send unsigned transaction via QR code
- [ ] Receive unsigned transaction via QR code
- [ ] Publish signed transaction
### Monero-GUI integration (Optional)
- [ ] Send unsigned transaction via QR code (hidden but accessible)
- [ ] Receive signed transaction via QR code (hidden but accessible)
- [ ] Check transaction and publish to network
- [ ] Process flow in `Send` for view key only wallet, to make the workflow natural as possible
### Documentation:
- [ ] Short and simple step-by-step guide
- [ ] README on how to use the automatic build process, including `git clone`, `make`, `make install`, and troubleshooting
### Tools and Scripts:
- [ ] Build image for target device
- [ ] Build emulator
I want to express that I will try to minimize the need for documentation by making the process easier to build and use. Nobody wants to read a book to get something done.
### ~~PortableMoneroQR:~~ dropped in favor of UR's
- [ ] ~~Well-defined data protocol~~
- [ ] ~~Targeting low-end cameras and screens~~
- [ ] ~~Targeting high speed~~
- [ ] ~~Application agnostic~~
- [ ] ~~Library Python~~
- [ ] ~~Library Java/Kotlin~~
There is no need for that, I was not aware of Blockchain Commons’ Uniform Resources (URs), but that is the way to go. Sending and receiving data will be implemented using URs.
## Milestones and Timeline
### Monero Signer basics on emulator (5.38 XMR) (10 days from now)
- [x] Emulator easy start
- [x] implement Polyseed in (pure) Python
- [x] Monero seed generation by camera
- [x] Monero seed generation on dice rolls
- [x] Polyseed generation by camera
- [x] Polyseed generation by dice rolls
- [x] Wallet export Seed~~/hex~~/QR code
- [x] Build script to generate executable (For macOS only Docker provided and I have no way to verify)
### Monero Signer working with companion Application (5 XMR) (25 days from now)
- [ ] Monero signer companion Application finished
- [ ] All missing Monero signer functionality
- [ ] ~~PortableMoneroQR stable~~
- [ ] UR's implemented
### Cleanup and production ready (35 XMR) (45 days from now)
- [ ] Tools
- [ ] Scripts
- [ ] Documentation final version
- [ ] Final cleanup Monero Signer
- [ ] Final cleanup companion Application
- [ ] ~~Final cleanup PortableMoneroQR~~
### Monero-GUI integration (10 XMR) (60 days from now from, until PR)
- [ ] Fork
- [ ] Modify
- [ ] PR
The given timeline reflects the upper bounds, but I target myself:
- Milestone 1: 7 days from now, June 1, 2024
- Milestone 2: 14 days from now, June 8, 2024
- Milestone 3: 30 days from now, June 24, 2024
- Milestone 4: 45 days from now, July 9, 2024
I kindly request that the payouts be made promptly upon completion of each milestone to allow me to concentrate fully on delivering Monero Signer successfully.
An expiration date for the proposal is set for 70 days from now, August 3, 2024.
- Milestone 4: 45 days from now, July 9, 2024
I kindly request that the payouts be made promptly upon completion of each milestone to allow me to concentrate fully on delivering Monero Signer successfully.
An expiration date for the proposal is set for 70 days from now, August 3, 2024.# Monero Signer Resurrection: Reviving and Enhancing the Monero Signing Project
Progress can be watched at:
[MoneroSigner](https://github.com/DiosDelRayo/MoneroSigner)
[Emulator](https://github.com/DiosDelRayo/monerosigner-emulator)
[polyseed python](https://github.com/DiosDelRayo/polyseed-python)
[monero python Todo, where is no work at the moment, but tracked about password encryption](https://github.com/DiosDelRayo/polyseed-python/Todo.md)
(will add with time other repositories, as soon there is code to see)
\ No newline at end of file
---
layout: cp
title: "0xfffc part-time C++ development (3 months, February, March, April, 2024)"
author: 0xfffc
date: 8 Jan 2024
amount: 45
milestones:
- name: 80 hours
funds: 15
done: 29 February 2024
status: finished
- name: 80 hours
funds: 15
done: 30 March 2024
status: finished
- name: 80 hours
funds: 15
done: 30 April 2024
status: finished
payouts:
- date: 4 March 2024
amount: 15
- date: 9 April 2024
amount: 15
- date: 2 May 2024
amount: 15
---
### What
I propose to spend 20 hours a week for 3 months working on Monero Core. Here are some areas, in tentative order of descending importance/specificity, that I'd work on:
- Will focus on reviewing and testing different PRs.
- Work with @selsta to fix different issues.
- Work with @hyc to fix incoming issues and improve our LMDB usage in Monero.
- Improve Doxygen documentation.
- Improve general documentation of the codebase.
- General improvements to our codebase. Like removing dead code, and simplifying the codebase, especially the [epee module](https://github.com/monero-project/monero/pull/9090).
- Investigate wallet2 API interoperability with other languages. As it comes up regularly in IRC dev channel discussions, we need to interoperability of wallet2 API. There have been suggestions like rewriting it from scratch or exposing C-style API from wallet2 C++ code. I am planning to investigate this issue and report to the community about the pros and cons of each approach and how much investment we need for each approach.
- Go through the issue tracker and look into solving existing issues, will confirm issues to work with trusted developers in the community.
- Analyze existing static analyzers (clangd-based analyzer, NASA/ikos, Facebook/infer, etc) and report to @selsta about the possibility of adding one of them as a workflow to our GitHub repository. Target will be running static analysis on submitted PR as workflow.
### Who
I am anonymous; you can call me 0xFFFC; after I finished my Master's degree in compilers, I worked as a C++ engineer (9-5) in a big-tech software company for 3 years on a product with more than 1 billion active users, chances are you are using it right now as you reading this text. But over time I realized that I wanted to work on crypto, because I believe in Monero's mission. My technical background is mostly in Compilers (GCC) and Operating Systems (Linux kernel). But I have always followed cryptography and now I am switching to cryptocurrency as my long-term career plan.
I have already finished [one bounty](https://bounties.monero.social/posts/75/6-500m-blake2b-c-dev-challenge-seraphis) and have [another bounty](https://bounties.monero.social/posts/91/1-000m-twofish-addition-to-monero) in the pipeline. Submitted different [PRs](https://github.com/monero-project/monero/pull/9090). and multiple reviews, including [9103](https://github.com/monero-project/monero/pull/9103), [9084](https://github.com/monero-project/monero/pull/9084), [9061](https://github.com/monero-project/monero/pull/9061), [7935](https://github.com/monero-project/monero/pull/7935).
Helped @hyc to close bug report LMDB side [9378](https://bugs.openldap.org/show_bug.cgi?id=9378#c14), working on [9920](https://bugs.openldap.org/show_bug.cgi?id=9920) at the moment. With the help of @selsta, I am managing labels for all the incoming PRs and issues on our repo too.
I will provide regular updates at each milestone. Including details regarding (a) how much time I have spent on each specific problem, (b) what I have done, (c) what I am currently doing, and (d) what is my plan for the next milestone. Each update will provided publicly and will be reviewed by trusted developers in the community.
### Funding
- 15xmr/mth * 3 months = 45xmr
- Schedule: 20hr/week * 12week
Freedom wins.
0xFFFC
---
layout: cp
title: "0xFFFC full-time C++ development (3 months, May, June, July, 2024)"
author: 0xFFFC
date: 21 March 2024
amount: 90
milestones:
- name: 160 hours
funds: 30
done: 17 June 2024
status: finished
- name: 160 hours
funds: 30
done: 16 July 2024
status: finished
- name: 160 hours
funds: 30
done: 14 August 2024
status: finished
payouts:
- date: 20 June 2024
amount: 30
- date: 19 July 2024
amount: 30
- date: 26 August 2024
amount: 30
---
### What
The bulk of my focus will be on opportunities related to performance improvement. To find out performance improvement opportunities a performance test suite is necessary for the Monero project.
I have been experimenting with the idea of performance tests with Monero past few weeks ( [perf script](https://github.com/0xFFFC0000/monero-perf), [small C++ code to benchmark monero](https://github.com/0xFFFC0000/benchmark-project), [monero rpc test](https://github.com/0xFFFC0000/monero/pull/17) ). and I believe a RPC client that stress tests the daemon is the way to go. My intended goals first this CCS:
- Performance benchmarks. The performance benchmark test I am working on right now is stress testing Monerod under an intense load that tries to mimic a real-world heavy node. Right now it is in very early shape. The end goal is to mimic real-world wallet usage on the Monero daemon.
- Completion of Read/Write Lock PR [#9181](https://github.com/monero-project/monero/pull/9181). PR 9181 is a huge change to the core of the blockchain implementation of the Monero project. It requires a lot of careful analysis and testing. Task 1 and Task 2 are kind of depend on each other. I use benchmarking results from task 1 to test/improve/debug 9181. @jeffro256_ has implemented an important and sensitive part of the 9181 code and has improved the PR with his suggestions.
- Seraphis wallet LMDB storage. Based on our discussion in the IRC #monero group, it seems porting the entire wallet2 storage to LMDB at this point is not a wise decision. Instead of that, we should start implementing the Seraphis wallet cache with LMDB. Once I am finished with Task 1 and 2, my next big goal is to start focusing on this task. The target of this task is to have Seraphis wallet only using LMDB as its cache/storage engine.
- Static analysis. This task hasn't been finished from my previous CCS by the time I am submitting this CCS. I am hopeful I will finish it before the end of my previous CCS. But in case I am not able to finish it, this is one of the tasks I have on my todo list: "Analyze existing static analyzers (clangd-based analyzer, NASA/ikos, Facebook/infer, etc) and report to @selsta about the possibility of adding one of them as a workflow to our GitHub repository. Target will be running static analysis on submitted PR as workflow."
If all milestones are not claimed within 100 days of start of the CCS, then this CCS will automatically expire and remaining funds should return to GeneralFund Wallet.
### Who
I have been contributing to the Monero core repository for the past few months with a total of multiple ([PRs]( https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3A0xFFFC0000+)) merged commits thus far. Because i have been averaging over 40 hours a week, I have decided to change my CCS to full time work. Some ongoing contributions:
- Implemented Read/Write lock mechanism for core blockchain implementation. [9181](https://github.com/monero-project/monero/pull/9181).
- Helped review multiple [PRs](https://github.com/monero-project/monero/pulls?q=is%3Apr+reviewed-by%3A%40me).
- Helped to review and fix multiple HackerOne reports with @selsta.
A special thanks to all community members who are always available to help me with technical questions.
Previous Proposals:
- [429](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/429)
### Funding
- 30xmr/mth * 3 months = 90xmr
- Schedule: 40hr/week * 12week
Freedom wins.
0xFFFC
\ No newline at end of file
---
layout: cp
title: "0xfffc full-time C++ development (3 months, Sep, Oct, Nov, 2024)"
author: 0xfffc
date: 14 Aug 2024
amount: 111
milestones:
- name: 160 hours
funds: 37
done: 30 September 2024
status: finished
- name: 160 hours
funds: 37
done: 14 November 2024
status: finished
- name: 160 hours
funds: 37
done: 25 December 2024
status: finished
payouts:
- date: 7 October 2024
amount: 37
- date: 15 November 2024
amount: 37
- date: 4 January 2025
amount: 37
---
### What
The bulk of my focus will be on opportunities related to performance improvement. To find out performance improvement opportunities a performance test suite is necessary for the Monero project. Here is a list of tasks I have on my todo list:
- Dynamic BSS: The issue is dynamic BSS (block-sync-size) size. If BSS goes over a threshold, then we hit the packet limit size (100mb). I expect to hit the serialization limit (https://github.com/monero-project/monero/pull/9433) too at some point if we fix the packet size limit. This one hopefully will be solved by the time this CCS kicks in.
- Bandwidth-Efficent Transaction Propagation Usage: Work on the @boog900 proposal ( https://github.com/monero-project/monero/issues/9334 ). And reduce the communication load between peers when syncing. The final goal is to merge a PR that uses this mechanism in Monero P2P subsystem.
- OOM: Spend time on finding the root cause of OOM. Report to community and eventually submit PR fixing it.
- Exclusive incoming ip: --exclusive-incoming-ip flag: (a) Require --add-exclusive-node to be set. (b) Be able to be set multiple times.
- Cleanup the sleepwait: Remove this _sleep_wait_ and change it to condition variable: https://github.com/monero-project/monero/blob/cc73fe71162d564ffda8e549b79a350bca53c454/src/daemon/daemon.cpp#L198
- Sync time estimation: When calculating how long it will take to finish the sync, is uses a number of blocks. Example: 200 blocks remaining, synced 20 blocks in 1 min = 10 mins remaining. It should use the size, instead of the block number.
- Performance benchmarks. The performance benchmark test I am working on right now is stress testing Monerod under an intense load that tries to mimic a real-world heavy node. Right now it is in very early shape. The end goal is to mimic real-world wallet usage on the Monero daemon.
- Completion of Read/Write Lock PR [#9181](https://github.com/monero-project/monero/pull/9181). PR 9181 is a huge change to the core of the blockchain implementation of the Monero project. It requires a lot of careful analysis and testing. Task 1 and Task 2 are kind of depend on each other. I use benchmarking results from task 1 to test/improve/debug 9181. @jeffro256_ has implemented an important and sensitive part of the 9181 code and has improved the PR with his suggestions.
- Seraphis wallet LMDB storage. Based on our discussion in the IRC #monero group, it seems porting the entire wallet2 storage to LMDB at this point is not a wise decision. Instead of that, we should start implementing the Seraphis wallet cache with LMDB. Once I am finished with Task 1 and 2, my next big goal is to start focusing on this task. The target of this task is to have Seraphis wallet only using LMDB as its cache/storage engine.
- Static analysis. This task hasn't been finished from my previous CCS by the time I am submitting this CCS. I am hopeful I will finish it before the end of my previous CCS. But in case I am not able to finish it, this is one of the tasks I have on my todo list: "Analyze existing static analyzers (clangd-based analyzer, NASA/ikos, Facebook/infer, etc) and report to @selsta about the possibility of adding one of them as a workflow to our GitHub repository. Target will be running static analysis on submitted PR as workflow."
### Who
I have been contributing to the Monero core repository for the past few months with a total of multiple ([PRs]( https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3A0xFFFC0000+)) merged commits thus far. Some ongoing contributions:
- Helped review multiple [PRs](https://github.com/monero-project/monero/pulls?q=is%3Apr+reviewed-by%3A%40me).
- Implemented Read/Write lock mechanism for core blockchain implementation. [9181](https://github.com/monero-project/monero/pull/9181).
- Helped to review and fix multiple HackerOne reports with @selsta.
A special thanks to all community members who are always available to help me with technical questions.
Previous Proposals:
- [429](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/429)
- [438](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/438)
### Funding
- 37xmr/mth * 3 months = 111xmr
- Schedule: 40hr/week * 12week
Freedom wins.
0xFFFC
---
layout: cp
title: "Create Educational Content in Spanish"
author: Lovera
date: December 15, 2022
amount: 10.5
milestones:
- name: Milestone 1 - Videos and Educational Articles
funds: 3.5 XMR
done: 7 March 2023
status: finished
- name: Milestone 2 - Videos and Educational Articles
funds: 3.5 XMR
done: 11 April 2023
status: finished
- name: Milestone 3 - Videos and Educational Articles
funds: 3.5 XMR
done: 16 May 2023
status: finished
payouts:
- date: 16 March 2023
amount: 3.5
- date: 15 April 2023
amount: 3.5
- date: 19 May 2023
amount: 3.5
---
### Introduction
Hi Monero community, Lovera here! this is my third proposal for my work. As you know I am dedicated to create content about Monero in Spanish, in this period I would like to dedicate more time to Monero so I would like to have the support of the community. I want to be as transparent as possible. I am seeking funding from the community to working on Monero related projects all days full time. Im truly thankful for all the support i have received from the community and my sponsor Cakewallet who currently makes it possible to publish 5 videos per month about monero on my main channel.
But if I am going to dedicate myself full time to Monero i will need much more, so the plan is to take the leap full-time again!
#### Clarification:
All the videos proposed here are a completely separate work from cakewallet's sponsorship. This means that in these videos there will be no advertising to any sponsor of the channel, in fact the monetization will be turned off. However it is not guaranteed that there will not exist ads by YouTube because since 2020 they introduce ads in any video, even if it is not monetized.
### Who?
I'm Lovera, creator of satoshilov.com and YouTube Channels LoveraTV and LoveraXMR I'm a big enthusiast, supporter and contributor of Monero. Since 2019 I am actively sharing educational content about Monero on my social networks. I’m creating educational videos about Monero, writing guides and tutorials in Spanish. I also translate into Spanish everything related to Monero and post it on my website. You can check my Guides and articles here:
* [Monero Blog](https://satoshilov.com/monero/)
And my Videos about Monero
* [Monero Videos in LoveraTV](https://www.youtube.com/playlist?list=PLGX_LoM5yemgt3ppLXvNBKYf6IuFI7BPS)
* [Monero News on LoveraXMR](https://www.youtube.com/playlist?list=PL2Lfro_oKAVHxYdbD_6RkNnda8HGbKOgg)
* [LoveraXMR YT Channel](https://www.youtube.com/@loveraxmr)
### ¿What is the proposal about?
- Create quality educational content for the Spanish-speaking community. The objective is to transmit the benefits, characteristics and importance of Monero for financial privacy, through guides, articles, videos and in general written and audio visual material.
- These video tutorials will not only help new Spanish-speaking users coming to Monero, but will also raise awareness of the only currency that protects users' privacy by default, yes, you could even call it marketing?
- I will share all this content in my social networks:
- LoveraTV YT Channel: 15,000+ suscribers
- LoveraXMR YT Channel: 500+ suscribers
- TikTok Channel: 20,000+ suscribers
- Telegram Channel: 1000+ suscribers
### Milestones and projected schedule
* Create a weekly video about Monero News on LoveraXMR and shorts on LoveraTV
* Create a weekly video on the most common Q&A about Monero on LoveraXMR and LoveraTV
* Create at less 2 video per month about Monero Mining and promote the use of P2pool on LoveraXMR and LoveraTV
* Create at less 3 Video tutorial per month about Monero (Wallets, Node in differents OS, using tools like monero bash, GUPAX when will finished, i2p, xmr.sh, etc) on LoveraTV and LoveraXMR
* Create a weekly short video About monero News on TikTok and Instagram
* Create quality educational content by my self for the Spanish-speaking community. The objective is to transmit the benefits, characteristics and importance of Monero for financial privacy, through guides and articles. (at less 1 per month)
* Review and update all past tutorials
* promotion of Monerokon 2023 to my audience in my social media (TikTok, LoveraXMR, LoveraTV and Telegram groups)
* maintance of the site
### Why it is important for Monero and the community?
Monero is an incredible project, but there are many false beliefs and ignorance about it in the Spanish-speaking community. By providing more quality content in Spanish, we will be able to raise awareness in the Spanish community about the importance of financial privacy, about the importance and role that Monero plays in our financial activity.
### How much and Payouts?
A good work must be paid or rewarded, specially if this contribute to a good cause. payment on first days of every month during 3 months for my upcoming work. The price is fixed in Monero and regardless of market fluctuation (downward or upward) it will not affect the achievement of the milestones. 3.5 XMR per month for 160 hours of work, to be fair usually i spend much more time. In total: 3.5 XMR per moth - 10.5 XMR for three months. Starting from January.
Please feel free to let me know if you have any questions in the comments.
Thanks
---
layout: wip
layout: cp
title: 36C3 Supplies
author: rehrar
date: 8 November 2019
......@@ -7,13 +7,13 @@ amount: 560
milestones:
- name: Disperse to discretionary, multisig wallet
funds: 560
done:
status: unfinished
done: 16 November 2023
status: finished
payouts:
- date: 16 December 2019
amount: 280
- date:
amount:
- date: 27 November 2023
amount: 280
---
What up guys? It's rehrar with another CCS proposal, but this time it's not about me. We're talking about the big C3 conference.
......@@ -38,4 +38,4 @@ We are requesting that this XMR be released immediately to a 2/3 multisig wallet
Any questions or concerns can be raised on this MR, or at our weekly C3 meetings.
Thanks everyone. I hope we can all make this happen!
\ No newline at end of file
Thanks everyone. I hope we can all make this happen!
---
layout: wip
layout: cp
title: Archive Monero Github code on a self-host onion instance and sia network
author: monero_archive
date: August 19, 2022
......@@ -19,4 +19,9 @@ payouts:
- date:
amount:
---
### Proposal closed
The remaining funds (0.2XMR) have been donated to the general fund.
Recently tornado cash is sanctioned and its github repo is deleted. Monero code should be mirrored on censorship resistant platforms to avoid being vaporized by a government order. I plan to setup a gitea hidden mirror to mirror all monero code on github as a backup, and regularly pack monero source code and upload them on sia network. Sia network is a file storage network that allows you to host large files in a very cheap and decentralized way. Unlike IPFS it guarantees your file will always be online. Funds received will be mainly used to maintain the server that host the onion gitea site. This can sustain around 1 year if the monero price does not drop too much.
---
layout: wip
layout: cp
title: Douglas Tuman Working full-time on Monero Projects (6 months)
author: Douglas Tuman
date: August 30, 2021
......@@ -7,23 +7,19 @@ amount: 240
milestones:
- name: Month 1 and 2
funds: 80
done:
status: unfinished
done: 13 December 2023
status: finished
- name: Month 3 and 4
funds: 80
done:
status: unfinished
done: 13 December 2023
status: finished
- name: Month 5 and 6
funds: 80
done:
status: unfinished
done: 13 December 2023
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 11 January 2024
amount: 240
---
**INTRO**
......
---
layout: cp
title: Create Educational Content in Spanish
author: Lovera
date: August 28, 2023
amount: 10.5
milestones:
- name: Videos and Educational Articles
funds: 3.5 XMR
done: 7 November 2023
status: finished
- name: Videos and Educational Articles
funds: 3.5 XMR
done: 3 January 2024
status: finished
- name: Videos and Educational Articles
funds: 3.5 XMR
done: 16 February 2025
status: finished
payouts:
- date: 11 November 2023
amount: 3.5
- date: 15 January 2024
amount: 3.5
- date: 25 February 2025
amount: 3.5
---
### Introduction
Hello friends and Monero Fam, Lovera Here!
This is my fourth funding request for my work. As you know I am dedicated to create content about Monero in Spanish. Im truly thankful for all the support i have received from the community. As you already know, all the videos proposed here are a completely separate work from cakewallet's sponsorship. This means that in these videos there will be no advertising to any sponsor of the channel, in fact the monetization will be turned off. However it is not guaranteed that there will not exist ads by YouTube because since 2020 they introduce ads in any video, even if it is not monetized.
### Who
I'm Lovera, creator of satoshilov.com and YouTube Channels LoveraTV and LoveraXMR I'm a big enthusiast, supporter and contributor of Monero. Since 2019 I am actively sharing educational content about Monero on my social networks. I’m creating educational videos about Monero, writing guides and tutorials in Spanish. I also translate into Spanish everything related to Monero and post it on my website. You can check my Guides and articles here:
* [Monero Blog](https://satoshilov.com/)
And my Videos about Monero
* [Monero Videos](https://youtube.com/playlist?list=PLGX_LoM5yemgt3ppLXvNBKYf6IuFI7BPS)
* [Monero News Videos](https://youtube.com/playlist?list=PLGX_LoM5yemgVhlwCEn_Z5m0LPMxQgNZj)
* [Monero Pods](https://youtube.com/playlist?list=PLGX_LoM5yemhq5KMyPeUr6JzJSqkqjzHL)
* [Monero News in LoveraXMR](https://www.youtube.com/playlist?list=PL2Lfro_oKAVHxYdbD_6RkNnda8HGbKOgg)
### ¿What is the proposal about?
Create quality educational content for the Spanish-speaking community. The objective is to transmit the benefits, characteristics and importance of Monero for financial privacy, through guides, articles, videos and in general written and audio visual material.
These video tutorials will not only help new Spanish-speaking users coming to Monero, but will also raise awareness of the only currency that protects users privacy by default,
I will share all this content in my social networks:
LoveraTV YT Channel: 15,000+ suscribers
LoveraXMR YT Channel: 900+ suscribers
TikTok Channel: 20,000+ suscribers
Telegram Channel: 1000+ suscribers
Instagram Channel
### Milestones and projected schedule
LoveraXMR YouTube Channel
Milestones
* Go From 1000 to over 2k Suscribers on YouTube
* Created 4 short Videos per month about Monero News (weekly)
* Created 2 Short Video per month on the most common Q&A about Monero
* Created at less 1 Video Tutorial about Monero per Month (Wallets, GUI Wallet, Node in differents OS, etc)
* Created at less 1 Video per month About Monero Mining and promote descentralized p2pool
* Continue to improve our studio and production quality
LoveraTV YouTube Channel
Milestones
* Created 4 full Videos per month about Monero News (weekly)
TikTok, Instagram :
* Create a weekly short video About monero News on TikTok and Instagram
Satoshilove (Website)
* Create quality educational content by my self for the Spanish-speaking community. The objective is to transmit the benefits,
characteristics and importance of Monero for financial privacy, through guides and articles. (at less 1 per month)
* Work in Moneropedia in satoshilov.com/moneropedia
* maintance of the site
### Why it is important for Monero and the community?
Monero is an incredible project, but there are many false beliefs and ignorance about it in the Spanish-speaking community. By providing more quality content in Spanish, we will be able to raise awareness in the Spanish community about the importance of financial privacy, about the importance and role that Monero plays in our financial activity.
### ¿How much and Payouts?
A good work must be paid or rewarded, specially if this contribute to a good cause. payment on first days of every month during 3 months for my upcoming work. The price is fixed in Monero and regardless of market fluctuation (downward or upward) it will not affect the achievement of the milestones. 3.5 XMR per month for 160 hours of work, to be fair usually i spend much more time. In total: 3.5 XMR per moth - 10.5 XMR for three months. Starting from October.
Please feel free to let me know if you have any questions in the comments.
Thanks
---
layout: wip
layout: cp
title: "MoneroKon 2022 CCS"
author: midipoet
date: December 7, 2021
......
---
layout: wip
title: MoneroKon 2025 CCS
author: hbs
date: February 24, 2024
amount: 99
milestones:
- name: Funding goal reached
funds: 99
done:
status: unfinished
payouts:
- date:
amount:
---
# Table of Contents
- [Who?](#who)
- [What?](#what)
- [Amount](#amount)
- [Exchange Rate](#exchange-rate)
# Who:
I, hbs, am one of many MoneroKon staff members contributing to this funding proposal. I have been actively involved with the Monero project for several years and have taken part in MoneroKon organizing team since its 2022 edition in Prague. This CCS proposal is intended to support the work of a larger team, not just my own. Active community members, including ajs, midipoet, monerobull, franciscom, dadajo, comradeblin, Siren, ceetee, recanman, and others, coordinate and hold weekly meetings in the [#monerokon Matrix room](https://matrix.to/#/#monerokon:matrix.org).
In 2024, a Czech non-profit [Twisted Edwards z.s.](https://twed.org/) was set up to support education and scientific research in cryptography, distributed systems, and information technology security. Siren, ajs, and midipoet volunteered as directors of Twisted Edwards z.s., with their roles confirmed through community voting. Twisted Edwards z.s. oversees the organization of MoneroKon and is responsible for contracting essential services, including the venue, A/V staff, equipment rentals, food trucks, storage, and more.
As of 19 February 2025, Twisted Edwards holds approximately 32,200 EUR in stablecoins in a [Safe Polygon multisig wallet](https://polygonscan.com/address/0x22942517e3eDEF1e1016070951a7081F99AE50A3) and 105.43 XMR in a hardware wallet in accordance with the [Cryptocurrency Funds Management Policy](https://github.com/MoneroKon/meta/blob/main/policies/funds-management-policy.md).
All MoneroKon staff members are unpaid volunteers.
# What
[Monero Konferenco (“MoneroKon”)](https://www.monerokon.org/) is an annual gathering of privacy advocates, cypherpunks, scientists, and philosophers focused on advancing privacy and financial technologies such as censorship-resistant digital cash. The event first took place in Denver, Colorado in 2019, and after a hiatus due to COVID-19, it resumed in Lisbon, Portugal in 2022. In 2023 and 2024, MoneroKon was held in Prague.
The popularity of MoneroKon has steadily increased, with growing attendance over the years:
* 2019 - Denver - 73 attendees - [27 speakers](https://www.youtube.com/playlist?list=PLsSYUeVwrHBkJHJg_l2uDgbicDJ1PmAVW)
* 2022 - Lisbon - 160 attendees - [40 speakers](https://www.youtube.com/playlist?list=PLsSYUeVwrHBndRQoQ-vLezzlHPLRDNzaw) |
* 2023 - Prague - 200 attendees - [~40 speakers](https://www.youtube.com/playlist?list=PLsSYUeVwrHBm1m7IaU3JiDVb5EC7cn0KG) |
* 2024 - Prague - 300 attendees - [~40 speakers](https://www.youtube.com/playlist?list=PLsSYUeVwrHBk-C3zImaDAQLx453PL7dR-) |
Previous MoneroKon editions in [2019](https://forum.getmonero.org/22/completed-tasks/90909/surae-noether-first-denver-monero-konferenco-spring-2019) ([postmortem](https://github.com/ajs-xmr/mrl-skunkworks-mirror/blob/master/Konferenco/2019/postmorto.md#1-budget-actuals)), [2022](https://ccs.getmonero.org/proposals/MoneroKon-2022-CCS.html), and [2023](https://ccs.getmonero.org/proposals/monerokon-2023-ccs-1.html) were partially funded through the CCS. For MoneroKon 2024, the organizers aimed to make the event self-funded through ticket sales and sponsorships. A concerted effort was made to keep costs low, such as by renting a smaller section of the venue. The previous edition taught us that a smaller, more intimate space created a better experience for all attendees. Feedback confirmed that this was a successful change. Moreover, cost savings efforts resulted in approximately 20,000 EUR net surplus, which has been rolled over to finance future editions of the conference.
For MoneroKon 2025, we also aim to achieve self-funding through ticket sales and sponsorships. However, as of February 2025, several [sponsor slots](https://www.monerokon.org/sponsor.html) remain unfilled. The funds raised so far, combined with the surplus from the previous edition and projected ticket sales, suggest a potential shortfall for paying some major suppliers on time. Additionally, some community members have expressed concerns about seeking sponsorships from "pre-mined" or "dev-tax" funded projects, contributing to delays in sponsor outreach efforts. Given the economic uncertainty, we are requesting community funding via this CCS proposal to bridge the gap until ticket sales and sufficient sponsorships are fully secured.
Compared to earlier editions, MoneroKon 2025 has a more modest budget. The [current budget](https://cryptpad.monerokon.org/sheet/#/2/sheet/view/t+QGKaxkHNqtRn2HKQlM168Cddh5G3uh6aO7uuyGnOc/embed/) will remain balanced if sponsorships and ticket sales meet the specified targets. To ensure the event proceeds smoothly, the organizing team is requesting 20,000 EUR in funding as a safety buffer. The funds raised will be used for MoneroKon-related expenses. Any leftover funds will be allocated to future editions of the conference.
MoneroKon 2025 Budget Breakdown:
* La Fabrika, event venue - 33,520 EUR - 42.6% of total
* A/V and livestreaming - 4,612.2 EUR - 5.9% of total
* [Speaker](https://github.com/MoneroKon/meta/blob/main/policies/contributor-travel.md) and [staff](https://github.com/MoneroKon/meta/blob/main/policies/staff-travel.md) travel reimbursement - 9,000 EUR - 11.4%
* IT Stuff - 4,000 EUR - 5.1%
* Accounting and tax related expenses - 6,260 EUR - 8%
The "IT Stuff" category is a one-time investment in network and IT infrastructure. This equipment will be reused for future editions, as we cannot rely on the venue’s Wi-Fi to meet the high standards expected by our attendees. The investment includes dedicated local nodes (one for P2P and one for RPC) to ensure the best possible Monero transaction experience. It will also allow us to set up multiple screens with high-quality livestreaming, reducing the need for extra rental equipment.
As attendee numbers continue to grow, MoneroKon 2025 is likely to be the last edition at this venue. The organizing team has already begun scouting alternative venues for MoneroKon 2026, and initial findings suggest that venue costs may be lower, further reducing the need for community funding.
# Amount and milestone
The MoneroKon 2025 organizing team is seeking to raise 99 XMR and, given the nature of event organization and the track record of the team for delivering the previous editions, proposes a single milestone for full amount released on reaching funding goal.
# Exchange rate
20,000 EUR / 223.650 EUR ([EMA50 Euro monthly rate](https://www.investing.com/crypto/monero/xmr-eur-technical)) + 10% volatility buffer = 99 XMR
---
layout: wip
layout: cp
title: "MoneroSigner. Fork of seedsigner for Monero."
author: Monero-HackerIndustrial
date: June 08, 2022
......@@ -35,6 +35,19 @@ payouts:
- date:
amount:
---
----
### Proposal Closure/Transferral 17th June 2024
All remaining funds (55.38 XMR) have been transferred to/repurposed for: [MoneroSigner Resurrection](https://ccs.getmonero.org/proposals/%20MoneroSignerResurrection.html)
Effective immediately:
- HackerIndustrial is hereby terminated from this project and relinquishes any claim to the remaining CCS funds.
- The project will now proceed under vthor, who has already achieved significant progress in a matter of weeks, demonstrating the competence and dedication required.
----
The Monero community could benefit from a fork of [seedsigner](https://seedsigner.com/) to supports Monero. Seedsigner uses an air-gapped Raspberry Pi Zero to sign for Bitcoin transactions. The project aims to make it easy for anybody to make a dedicated offline signing device out of low-cost commodity computer components (raspberry pi zero). This helps in reducing the need to trust hardware verndors. The most private hardware wallet, is the only only **you** know about.
Seedsigner is focused only on Bitcoin, because of this, the UI/UX and features are not very helpful to Monero users.
......
......@@ -11,8 +11,8 @@ milestones:
status: finished
- name: Milestone 2 - Deliver initial probability density function to scientific review panel
funds: 74
done:
status: unfinished
done: 15 January 2025
status: finished
- name: Milestone 3 - Deliver final version of probability density function to Monero developers
funds: 30
done:
......@@ -20,8 +20,8 @@ milestones:
payouts:
- date: 24 September 2022
amount: 67
- date:
amount:
- date: 23 January 2025
amount: 74
- date:
amount:
---
......
---
layout: wip
title: Rucknium Statistical Research
author: Rucknium
date: March 28, 2024
amount: 204
milestones:
- name: Month 1
funds: 33% (68 XMR)
done: 10 October 2024
status: finished
- name: Month 2
funds: 33% (68 XMR)
done: 18 February 2025
status: finished
- name: Month 3
funds: 33% (68 XMR)
done:
status: unfinished
payouts:
- date: 16 October 2024
amount: 68
- date: 26 February 2025
amount: 68
- date:
amount:
---
## What
I propose to carry out statistical research to improve Monero's privacy, guide protocol decisions, and respond to Monero developer requests for statistical analysis of code changes where needed. In the short term I will complete in-progress analysis of the suspected transaction spam attack to provide a comprehensive view of the options to defeat this attack and possible future ones. This involves producing a Monero Research Lab research bulletin from the draft of ["March 2024 Suspected Black Marble Flooding Against Monero: Privacy, User Experience, and Countermeasures"](https://github.com/Rucknium/misc-research/blob/main/Monero-Black-Marble-Flood/pdf/monero-black-marble-flood.pdf). I will work with ArticMine to evaluate changes to ring size, fees, and block size scaling parameters to balance privacy, usability, and decentralization. Some items to complete the draft research bulletin:
- Derive the tradeoff function between ring size and transaction fees, i.e. how does a marginal increase in each variable affect the cost to a potential attacker?
- Simulate the combined black marble attack and Dulmage-Mendelsohn decomposition from Vijayakumaran (2023) to evaluate vulnerability to chain reaction analysis.
- Estimate any changes in the real spend age distribution during the spam incident using OSPEAD techniques. Movement toward more recent outputs suggests more evidence for the spam hypothesis.
- Create a node network crawler that seeks the source of large transaction volumes. Possibly combine the crawler with statistical analysis techniques of Sharma, Gosain, & Diaz (2023).
- Finish the research literature review.
Once the black marble flood analysis is completed, I would move to other research priorities:
- PocketChange privacy evaluation
- Ring member binning
- Fee discretization and fee prediction
- Safety of adjusting the 10 block lock
- Preparation of a paper describing OSPEAD for peer review and research journal publication
- EAE/EABE attack and churning
- Network privacy through steganography
I will not be able to complete all of these projects during this work period. Research priorities can be modified at Monero Research Lab meetings due to new events or findings.
I am nearing completion of [the OSPEAD improvement to Monero's decoy selection algorithm](https://ccs.getmonero.org/proposals/Rucknium-OSPEAD-Fortifying-Monero-Against-Statistical-Attack.html). OSPEAD probably can only be safely implemented at a hard fork boundary because multiple decoy selection algorithms being used at the same time is [a potential threat to user privacy](https://github.com/Rucknium/misc-research/blob/main/Monero-Fungibility-Defect-Classifier/pdf). In the short them, analysis of the suspected flood attack is a higher priority. After, I will put hours into finishing the OSPEAD CCS proposal. Then after OSPEAD I will return to putting hours into this CCS proposal.
## Who
I am an empirical microeconomist. My recent contributions to Monero include:
- [Discovery of a mining pool misconfiguration. Sped up average time to first transaction confirmation by 60 seconds.](https://reddit.com/r/Monero/comments/11nu4aj/monero_transaction_confirmations_are_now_60/)
- [Privacy vulnerability report to Exodus Wallet about nonstandard fees. Successfully resolved.](https://reddit.com/r/Monero/comments/176e1zr/privacy_advisory_exodus_desktop_users_update_to/)
- ["Discussion Note: Formula for Accuracy of Guessing Monero Real Spends Using Fungibility Defects"](https://github.com/Rucknium/misc-research/blob/main/Monero-Fungibility-Defect-Classifier/pdf)
- [Identification of privacy-reducing nonstandard transaction fees](https://github.com/Rucknium/misc-research/tree/main/Monero-Nonstandard-Fees)
- [Analysis of the privacy impact of Mordinals (Monero NFTs)](https://reddit.com/r/Monero/comments/12kv5m0/empirical_privacy_impact_of_mordinals_monero_nfts/)
- [Monerotopia 2023 presentation: "A Statistical Research Agenda for Monero"](https://github.com/Rucknium/presentations/blob/main/Rucknium-Monerotopia-2023-Slides.pdf)
- [Statistical privacy analysis of P2Pool coinbase outputs in ring signatures](https://github.com/monero-project/research-lab/issues/109)
- ["Closed-form Expression of Monero's wallet2 Decoy Selection Algorithm"](https://github.com/Rucknium/misc-research/tree/main/Monero-Decoy-Selection-Closed-Form/pdf)
Pull requests reviewed for statistical issues:
- [wallet: mitigate statistical dependence for decoy selection within rings](https://github.com/monero-project/monero/pull/9023#issuecomment-1802593848)
- [wallet2: prevent duplicate outs](https://github.com/monero-project/monero/pull/8047#issuecomment-967113046)
- [monero-serai: fix decoy selection algo and add test for latest spendable](https://github.com/serai-dex/serai/pull/384#issuecomment-1870597406)
## Budget
I will work 20 hours/week for three months (13 weeks). My fiat-equivalent labour rate is the same as my previous proposal, adjusted for the lower purchasing power of the USD today: 110 USD/hour. The average daily opening USD/XMR exchange rate for the last 14 days (2024-03-15 to 2024-03-28) according to CoinGecko was 139.49.
The above numbers compute to `20 * 13 * (110/139.49) = 205.0326`. Rounding down to get whole numbers for the three milestones sets the total budget for this proposal to 204 XMR paid in three milestones of 68 XMR each. This proposal expires on January 1, 2025.
## References
Sharma, P. K., Gosain, D., & Diaz, C. (2023). "On the Anonymity of Peer-To-Peer Network Anonymity Schemes Used by Cryptocurrencies." Proceedings 2023 Network and Distributed System Security Symposium.
Vijayakumaran, S. (2023). "Analysis of CryptoNote Transaction Graphs using the Dulmage-Mendelsohn Decomposition." 5th Conference on Advances in Financial Technologies (AFT 2023), volume 282 of Leibniz International Proceedings in Informatics (LIPIcs).
---
layout: cp
title: SNeedlewoods-01_part-time dev work (1 month)
author: Sneedlewooods
date: October 4, 2024
amount: 2.15
milestones:
- name: month 1
funds: 18.64
done: 4 December 2024
status: finished
payouts:
- date: 13 December 2024
amount: 18.64
---
## What?
For this proposal the focus of work will be on the new wallet API ([context](https://github.com/monero-project/monero/issues/9308)). The work is already ongoing since May 2024, there is [this PR](https://github.com/monero-project/monero/pull/9368) to organize functions and [this branch](https://github.com/monero-project/monero/compare/master...SNeedlewoods:seraphis_wallet:x_api_comments) to add comments, but most recent and most important is this [WIP PR](https://github.com/monero-project/monero/pull/9464) that adds functions to the API to make it "feature-complete" with `wallet2`.
There will not be a direct deliverable for the milestone and it's very unlikely the feature-complete API will be completely done (including reviews) before this proposal ends, but here are alternatives I would work on:
- If current API PR gets finished:
- Help with step 2 from [this proposal](https://github.com/seraphis-migration/wallet3/issues/64): "Stop using the wallet2 object in the CLI and RPC wallets and instead use the wallet API."
- Add unit_tests for the wallet API, or try to resurrect libwallet_api_tests (which are [temporarily disabled](https://github.com/monero-project/monero/blame/9866a0e9021e2422d8055731a586083eb5e2be67/Makefile#L60))
- If for any reason current API PR gets blocked:
- Things found during the API work, mostly in CLI and RPC wallet. An incomplete list can be found [here](https://github.com/SNeedlewoods/seraphis_wallet/issues/1).
I give weekly updates on what I've worked on in the "Monero Tech Meeting", where I also get feedback from more experienced devs to decide which way to go.
Besides that I try to help out where I can.
This is a "pilot" proposal to see how things work out. If the majority is satisfied at the end of this proposal, I see it as confirmation that I can justify putting more time and energy into Monero (and will increase my hourly rate in future proposals). Hopefully I will become a long term contributor for general development.
I aim for 15+ hours/week on average, but for precaution I won't promise more than 10 hours/week.
## Who?
Hey, I'm SNeedlewoods, since early 2023 I'm lurking around in the Monero community.
In November 2023 I joined the weekly "Seraphis wallet workgroup meeting" (now called "Monero Tech Meeting") in the [no-wallet-left-behind](https://matrix.to/#/#no-wallet-left-behind:monero.social) matrix room and got encouraged by our friendly and very helpful devs to start coding for Seraphis.
Only when the main focus in development shifted from Seraphis to FCMPs earlier this year, I started working on Monero core or more accurately on wallet related stuff.
Admittedly I don't have much to show and my expertise is not on par with other contributors, but I think considering the amount I'm asking for this proposal is fair.
Code contributions so far:
[Seraphis](https://github.com/UkoeHB/monero/pulls?q=is:pr+author:SNeedlewoods)
[Monero](https://github.com/monero-project/monero/pulls?q=is:pr+author:SNeedlewoods)
## Payment
Work 10 hours/week for 1 month.
10 (hours/week) * 4.3 weeks_per_month = 43 hours total. I am setting my hourly rate at 0.05 XMR/hour regardless of fiat market price (but for those who care, that is roughly around 6,50€ or $7.50 per hour, according to the current 7-day range on coingecko: 123,43€-147,32€ or $136.38-$164.58), that makes for a total of 2.15 XMR.
---
layout: wip
title: SNeedlewoods-02_part-time dev work
author: SNeedlewooods
date: January 27, 2025
amount: 23
milestones:
- name: M1 - Harden sensitive material in the Wallet API
funds: 2.4
done:
status: unfinished
- name: M2 - Replace wallet2 with Wallet API in simplewallet
funds: 20.6
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
---
## What?
Since the feature-complete Wallet API [PR](https://github.com/monero-project/monero/pull/9464) from my previous CCS proposal is finally in "pending review" state (I will give my best to quickly resolve issues coming up during the review, so it hopefully will get merged soon), it's time for the next steps:
- Harden handling of sensitive material in the Wallet API (Discussions: [#1](https://github.com/monero-project/monero-gui/issues/1537), [#2](https://github.com/feather-wallet/feather/issues/72#issuecomment-1405602142), [#3](https://github.com/monero-project/monero/pull/8619#issuecomment-1632951461)).
- Replace wallet2 with the Wallet API in simplewallet as proposed [here](https://github.com/seraphis-migration/wallet3/issues/64) in step 2 by @j-berman.
I'll try to spend at least 12 h/week coding.
## Who?
This is my second proposal, the previous one can be found here:
- [Proposal 1](https://ccs.getmonero.org/proposals/SNeedlewoods-01_part-time-dev-work-1-month.html)
## Milestone
(Disclaimer: I can't promise the estimated times are accurate, but I tried to keep them low and I'll take the risk if a milestone takes longer to complete.)
1. M1 (2.4 XMR): PR to harden handling of sensitive material in the Wallet API is merged to monero-project/monero
- Stop caching the password (in Wallet API and GUI)
- Use `epee::wipeable_string` instead of `std::string` for secret keys
I estimate this can be completed in ~ 2 weeks, which makes:
12 (h/week) * 2 (weeks) = 24 (h total M1).
2. M2 (20.6 XMR): PR to replace wallet2 with the Wallet API in simplewallet is merged to monero-project/monero
I estimate this can be completed in ~ 4 months, which makes:
12 (h/week) * 4.3 (weeks/month) * 4 (months) = 206.4 (h total M2).
## Payment
I am setting my rate at 0.1 (XMR/h) regardless of fiat market price (but for reference, that is roughly around 20,50€ or $21.50 per hour, according to the current 7-day range on coingecko: 195,68€-217,73€ or $202.95-$226.65).
M1: 24 (h) * 0.1 (XMR/h) = 2.4 (XMR).
M2: 206.4 (h) * 0.1 (XMR/h) = 20.64 (XMR).
That makes for a (rounded) total of:
2.4 (XMR) + 20.64 (XMR) = 23 (XMR total).
---
layout: cp
title: Continuation of Core Monero Concepts - A Series of Animated Explainers
author: VOSTOEMISIO
date: October 3, 2023
amount: 37
milestones:
- name: Random X and Understanding the significance of ASIC resistance
funds: 18
done: 26 June 2024
status: finished
- name: Nodes and why every Monero enthusiast should consider running one.
funds: 18
done: 8 April 2024
status: unfinished
payouts:
- date: 30 April 2024
amount: 18
- date: 16 July 2024
amount: 18
---
_Note: this proposal has been awarded 36 XMR from [New Animated Videos](https://ccs.getmonero.org/proposals/savandra-videos-for-monero.html)_
Hey all!
Thank you for the amazing reception and feedback of our first ccs-proposal and the Tail Emission video. We've seen a lot of excitement and engagement with over 7,000 accumulated views in just the initial days.
Our vision is to keep diving deeper into Monero's complex and sometimes tricky and misunderstood features, translating them into short, engaging, and most importantly, understandable animated videos. Here's what we suggest to cover in this proposal:
• Random X: Understanding the significance of ASIC resistance
• Breaking down the how-to and the rationale for P2Pool.
• Nodes: Why every Monero enthusiast should consider running one.
• Fungibility: Explaining its essence in the context of Monero.
Quality & Timeline:
As we've showcased in our recent work, we promise high-quality output, similar to our Tail Emission video ( https://youtu.be/sRwSqM0YBto?si=vAFA7iRUWAvaV5Wi ). In this proposal, we are committing to an accelerated timeline and we aim to finalize and release one video per month. Therefore, we aim to wrap up the entire series in just 4 months after proposal’s approval. However, acknowledging the potential for unforeseen challenges, we request an additional 2 months as a buffer, making the total proposed timeline 6 months. We estimate each video to be approximately 2 minutes in length.
Budget & Collaboration:
Given the scope, we propose 18 XMR per video, a total of 72 XMR for the entire series, broken down across milestones. As with our first video, we will collaborate with Xenu, sharing 5 XMR per video of the funds with him. This collaboration ensures the technical soundness of our scripts and storyboards, guaranteeing that each video is not only engaging but also accurate. As always, we are open to adjustments based on feedback and the evolving requirements of the project.
Open Source & Community:
Post-completion, all materials and animations will be open-sourced for the community's further use and reference.
We're eager to dive deep and clarify these essential Monero concepts with everyone. Your feedback, suggestions, and enthusiasm drive us, and we're all ears for what you have to say.
//VOSTO
www.vostoemisio.com
2CA8 85AC 923F 07A3 3656 8425 83F1 9CFF 27BE A177
---
layout: cp
title: "VOSTOEMISIO - FCMP Animated Explainer Video"
author: VOSTOEMISIO
date: July 29, 2024
amount: 20
milestones:
- name: Complete FCMP Video
funds: 20
done: 16 December 2024
status: finished
payouts:
- date: 13 January 2025
amount: 20
---
Hey Everyone,
We are happy to inform you that we have already received private funding for the introductory
Monero video, and therefore, we have adjusted the proposal accordingly.
After receiving the community’s feedback, we're now excited to present our revised proposal:
one explainer video about FCMP (Full-Chain Membership Proofs). This will be our 4th video for
the Monero CCS.
Our previous videos covering core Monero concepts like Tail Emission, the importance of
running a node, and RandomX have been informative, engaging, and uploaded on
Getmonero.org, shared across X and YouTube. We believe that visual learning and breaking
down complex ideas into digestible formats is highly effective, and we aim to do the same with
FCMP.
References:
1. [Youtube - Monero's Tail Emission](https://youtu.be/vjn9l3hG4ME)
2. [Youtube - Monero Nodes](https://youtu.be/hM6TF3co7lI)
3. [Youtube - Monero's RandomX](https://youtu.be/RsNOi0lpiyM)
Although we haven't finalized the script yet for the FCMP video, we're committed to delivering a
high-quality video approximately 2-3 minutes long, or however long it needs to be to effectively
explain the concept. We're proposing a budget of 20 XMR for this video. This is slightly higher
than our initial proposal since we agreed to extend the scope to include both dark and light
backgrounds. As before, Xenu will assist with the script and storyboard, with 5 XMR allocated
for his contribution. Additionally, we've reached out to kayabaNerve (Luke Parker) for
fact-checking the script to ensure accuracy, and he's agreed to help us. A big thanks to him for
his support.
As always, we will open-source our project materials after completion.
We believe we've done a good job of gathering the community's feedback so far in our previous
proposals, and we'll continue to do so by posting our script and storyboards on Matrix and here
in the repo.
If anyone has any questions or suggestions, please feel free to chime in.
Thanks!
---
layout: cp
title: VostoEmisio Animated Tail Emission Core Concept Video
author: VOSTOEMISIO
date: May 12, 2023
amount: 9
milestones:
- name: Complete Script
funds: 3
done: 26 September 2023
status: finished
- name: Complete Look and feel
funds: 3
done: 26 September 2023
status: finished
- name: Complete Video
funds: 3
done: 26 September 2023
status: finished
payouts:
- date: 6 November 2023
amount: 9
---
Hey everyone!
Since this is my first CCS proposal, I thought I'd give you a quick intro to who we are:
I run a marketing company in the traditional space. Here, we work under the name "VostoEmisio,". We've already done some work for Monero and other privacy-centric projects. Our journey began in early 2022 when we helped Rucknium revamp the logo and branding for these two projects:
https://bchmempool.cash/
https://beta.redteam.cash/
This year, we won the Monerokon 3 Design Proposal (www.monerokon.com), and we're currently working on brand refreshing and marketing for Firo: https://forum.firo.org/t/fcs-proposal-firo-3-month-trial-marketing-contract/2905/4
However, we haven't had the chance to show off our skills in motion assets and animation yet. As a long-time Monero user, I find it frustrating when browsing crypto-Twitter and seeing basic misconceptions like "infinite supply," "can't scale," and "dynamic block size???" still being spread, particularly by the uninformed "BTC maxis."
So, I propose that we create an animation series featuring short (1 min or so), ELI5-style explainer videos that break down the key concepts of how Monero works in a simple and digestible way that could easily be shared every time we, the community, face misleading comments. I suggest we start with one video and, if the result is satisfactory, create more based on the community's preferred topics.
### Promise and assurances:
- With the budget for this proposal, we're confident we can deliver quality on par with this example: https://www.youtube.com/watch?v=pYOSfEgF32Y&ab_channel=XPLAI
- Completion expiry date set to 4 months post-approval for this proposal
- Open-sourcing the project materials after completion
If that sounds good to you all, I'd be happy to jump into the details and start working on the script and storyboard. I would like to start with ( as our name vosto emisio also springs from), the tail emission concept.
Regarding the budget, we're not sure, but we're willing to try this out for 9 XMR for the first video. We can adjust the amount up or down after we see how the first project goes since this would be our first official collaboration with the community. I believe this project will take about a month to complete, maybe a bit longer since this is our first time working with the community.
Any questions or thoughts?