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
  • NorrinRadd/ccs-proposals
207 results
Show changes
Commits on Source (160)
Showing
with 423 additions and 60 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
...@@ -31,6 +31,9 @@ payouts: ...@@ -31,6 +31,9 @@ payouts:
- date: 28 September 2024 - date: 28 September 2024
amount: 10 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 # Monero Signer Resurrection: Reviving and Enhancing the Monero Signing Project
## Proposal ## Proposal
......
--- ---
layout: wip layout: cp
title: "0xfffc full-time C++ development (3 months, Sep, Oct, Nov, 2024)" title: "0xfffc full-time C++ development (3 months, Sep, Oct, Nov, 2024)"
author: 0xfffc author: 0xfffc
date: 14 Aug 2024 date: 14 Aug 2024
...@@ -11,19 +11,19 @@ milestones: ...@@ -11,19 +11,19 @@ milestones:
status: finished status: finished
- name: 160 hours - name: 160 hours
funds: 37 funds: 37
done: done: 14 November 2024
status: unfinished status: finished
- name: 160 hours - name: 160 hours
funds: 37 funds: 37
done: done: 25 December 2024
status: unfinished status: finished
payouts: payouts:
- date: 7 October 2024 - date: 7 October 2024
amount: 37 amount: 37
- date: - date: 15 November 2024
amount: amount: 37
- date: - date: 4 January 2025
amount: amount: 37
--- ---
### What ### What
......
--- ---
layout: wip layout: cp
title: Create Educational Content in Spanish title: Create Educational Content in Spanish
author: Lovera author: Lovera
date: August 28, 2023 date: August 28, 2023
...@@ -15,15 +15,15 @@ milestones: ...@@ -15,15 +15,15 @@ milestones:
status: finished status: finished
- name: Videos and Educational Articles - name: Videos and Educational Articles
funds: 3.5 XMR funds: 3.5 XMR
done: done: 16 February 2025
status: unfinished status: finished
payouts: payouts:
- date: 11 November 2023 - date: 11 November 2023
amount: 3.5 amount: 3.5
- date: 15 January 2024 - date: 15 January 2024
amount: 3.5 amount: 3.5
- date: - date: 25 February 2025
amount: amount: 3.5
--- ---
### Introduction ### Introduction
......
---
layout: cp
title: MoneroKon 2025 CCS
author: hbs
date: February 24, 2024
amount: 99
milestones:
- name: Funding goal reached
funds: 99
done: 19 March 2025
status: finished
payouts:
- date: 3 April 2025
amount: 99
---
# 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
...@@ -11,8 +11,8 @@ milestones: ...@@ -11,8 +11,8 @@ milestones:
status: finished status: finished
- name: Milestone 2 - Deliver initial probability density function to scientific review panel - name: Milestone 2 - Deliver initial probability density function to scientific review panel
funds: 74 funds: 74
done: done: 15 January 2025
status: unfinished status: finished
- name: Milestone 3 - Deliver final version of probability density function to Monero developers - name: Milestone 3 - Deliver final version of probability density function to Monero developers
funds: 30 funds: 30
done: done:
...@@ -20,8 +20,8 @@ milestones: ...@@ -20,8 +20,8 @@ milestones:
payouts: payouts:
- date: 24 September 2022 - date: 24 September 2022
amount: 67 amount: 67
- date: - date: 23 January 2025
amount: amount: 74
- date: - date:
amount: amount:
--- ---
......
...@@ -11,8 +11,8 @@ milestones: ...@@ -11,8 +11,8 @@ milestones:
status: finished status: finished
- name: Month 2 - name: Month 2
funds: 33% (68 XMR) funds: 33% (68 XMR)
done: done: 18 February 2025
status: unfinished status: finished
- name: Month 3 - name: Month 3
funds: 33% (68 XMR) funds: 33% (68 XMR)
done: done:
...@@ -20,8 +20,8 @@ milestones: ...@@ -20,8 +20,8 @@ milestones:
payouts: payouts:
- date: 16 October 2024 - date: 16 October 2024
amount: 68 amount: 68
- date: - date: 26 February 2025
amount: amount: 68
- date: - date:
amount: amount:
--- ---
......
--- ---
layout: wip layout: cp
title: SNeedlewoods-01_part-time dev work (1 month) title: SNeedlewoods-01_part-time dev work (1 month)
author: Sneedlewooods author: Sneedlewooods
date: October 4, 2024 date: October 4, 2024
...@@ -7,11 +7,11 @@ amount: 2.15 ...@@ -7,11 +7,11 @@ amount: 2.15
milestones: milestones:
- name: month 1 - name: month 1
funds: 18.64 funds: 18.64
done: done: 4 December 2024
status: unfinished status: finished
payouts: payouts:
- date: - date: 13 December 2024
amount: amount: 18.64
--- ---
## What? ## What?
......
---
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).
...@@ -3,7 +3,7 @@ layout: cp ...@@ -3,7 +3,7 @@ layout: cp
title: Continuation of Core Monero Concepts - A Series of Animated Explainers title: Continuation of Core Monero Concepts - A Series of Animated Explainers
author: VOSTOEMISIO author: VOSTOEMISIO
date: October 3, 2023 date: October 3, 2023
amount: 1 amount: 37
milestones: milestones:
- name: Random X and Understanding the significance of ASIC resistance - name: Random X and Understanding the significance of ASIC resistance
funds: 18 funds: 18
...@@ -20,19 +20,21 @@ payouts: ...@@ -20,19 +20,21 @@ payouts:
amount: 18 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! 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. 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: 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 Random X: Understanding the significance of ASIC resistance
Breaking down the how-to and the rationale for P2Pool. Breaking down the how-to and the rationale for P2Pool.
Nodes: Why every Monero enthusiast should consider running one. Nodes: Why every Monero enthusiast should consider running one.
Fungibility: Explaining its essence in the context of Monero. Fungibility: Explaining its essence in the context of Monero.
Quality & Timeline: Quality & Timeline:
......
--- ---
layout: fr layout: cp
title: "VOSTOEMISIO - FCMP Animated Explainer Video" title: "VOSTOEMISIO - FCMP Animated Explainer Video"
author: VOSTOEMISIO author: VOSTOEMISIO
date: July 29, 2024 date: July 29, 2024
...@@ -7,11 +7,11 @@ amount: 20 ...@@ -7,11 +7,11 @@ amount: 20
milestones: milestones:
- name: Complete FCMP Video - name: Complete FCMP Video
funds: 20 funds: 20
done: done: 16 December 2024
status: unfinished status: finished
payouts: payouts:
- date: - date: 13 January 2025
amount: amount: 20
--- ---
Hey Everyone, Hey Everyone,
......
---
layout: wip
title: acx part-time work on Monfluo (3 months)
author: acx
date: February 28, 2025
amount: 13.98
milestones:
- name: Month 1
funds: 4.66 XMR
done:
status: unfinished
- name: Month 2
funds: 4.66 XMR
done:
status: unfinished
- name: Month 3
funds: 4.66 XMR
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
## Who
Hi, I am acx.
About six months ago I have forked Mysu (an abandoned Android wallet) and continued its development and maintenance.
The fork is named Monfluo and is available [here](https://codeberg.org/acx/monfluo)
Since starting the fork, I did (among other things) the following:
* Implemented multi-wallet functionality (also wallet renames and deletion)
* Implemented multi-account functionality
* Separated wallet password and seed offset (previously you could not set them to different values)
* Reworked secrets tab, allowing the user to apply seed passpharse offset when saving seed
* Fixed a bug where sync progress was lost when the wallet was closed before the sync is finished
* Implemented APK building in the pipeline (making it easier for users to test any commit without waiting for a release)
* and several other changes, you can check all of them [here](https://codeberg.org/acx/monfluo/compare/b939d526652d174eb6081a0b5e9dd407c409c90a...master)
Monfluo is by design a very simple wallet, and one of the goals is having no "integrations" such as swapping services, sending to other cryptos, fiat on/off-ramps, etc. I do not earn any fees from the wallet.
## What
I will continue maintenance and development of Monfluo. I will be working on the things listed [here](https://codeberg.org/acx/monfluo/issues), among the most important ones:
* Updating to newer Monero versions, when required
* Setting up a clearnet F-Droid repo together with an onion mirror
* Setting up translations
* Issues [#67](https://codeberg.org/acx/monfluo/issues/67) and [#71](https://codeberg.org/acx/monfluo/issues/71)
* Working on making Monfluo reproducible (I do **not** expect to finish this one during this CCS, but I want to start investigating it)
## Funding
I am asking for 25$/h.
With 40 hours a month (~9 hours a week) \* 3 months at ~$215/XMR this makes 25\*40\*3/215 ~= 14 XMR
...@@ -26,6 +26,14 @@ payouts: ...@@ -26,6 +26,14 @@ payouts:
amount: amount:
--- ---
### Deadline update: July 1, 2025
Prior to the deadline, the proposer MUST provide regular updates on their progress as per the CCS rules.
If the provided updates/progress (or lack thereof) is unsatisfactory, all remaining funds **can be** relinquished either before or after the deadline.
The community will then seek another person/team to take over. If this cannot be accomplished within a reasonable timeframe, the funds will be repurposed or reallocated to a similar proposal (subject to community consensus).
# Monero Garden # Monero Garden
## The idea ## The idea
......
--- ---
layout: wip layout: cp
title: "anon: perfect peer to peer protocol from bottom to top" title: "anon: perfect peer to peer protocol from bottom to top"
author: anon author: anon
date: 24 Jan 2021 date: 24 Jan 2021
...@@ -26,6 +26,10 @@ payouts: ...@@ -26,6 +26,10 @@ payouts:
amount: amount:
--- ---
## Proposal closure / Repurposing of funds (1st Jan, 2025)
All remaining funds (160.08014XMR) will be repurposed or reallocated to a similar proposal (subject to community consensus).
## What ## What
~~~ ~~~
......
--- ---
layout: wip layout: cp
title: Boog900 full time work on Cuprate (3 months) title: Boog900 full time work on Cuprate (3 months)
author: Boog900 author: Boog900
date: June 28, 2024 date: June 28, 2024
...@@ -11,19 +11,19 @@ milestones: ...@@ -11,19 +11,19 @@ milestones:
status: finished status: finished
- name: Month 2 - name: Month 2
funds: 72 XMR funds: 72 XMR
done: done: 29 October 2024
status: unfinished status: finished
- name: Month 3 - name: Month 3
funds: 72 XMR funds: 72 XMR
done: done: 6 January 2025
status: unfinished status: finished
payouts: payouts:
- date: 27 September 2024 - date: 27 September 2024
amount: 71 amount: 71
- date: - date: 10 November 2024
amount: amount: 72
- date: - date: 21 January 2025
amount: amount: 72
--- ---
This proposal is to continue my work on [Cuprate](https://github.com/Cuprate/cuprate). This proposal is to continue my work on [Cuprate](https://github.com/Cuprate/cuprate).
......
---
layout: wip
title: Boog900 full time work on Cuprate (3 months) + January
author: Boog900
date: February 11, 2025
amount: 160
milestones:
- name: January
funds: 40 XMR
done:
status: unfinished
- name: Month 1
funds: 40 XMR
done:
status: unfinished
- name: Month 2
funds: 40 XMR
done:
status: unfinished
- name: Month 3
funds: 40 XMR
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
---
# Who
I am [Boog900](https://github.com/Boog900), you can see my last CCS [here](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/469).
# What
I will work for 3 months on Cuprate with an initial focus on releasing an alpha `cuprated`, the basic roadmap can be seen here: https://github.com/Cuprate/cuprate/issues/376.
I plan to work on what I think is best to advance the project.
I am also asking for payment for the hours I worked in January. We had some discussions about changing the way we
get funded, potentially making a combined "cuprate CCS", however we decided against it, this lead to the delay of this CCS.
A list of things I did during January:
- finished the init PR: https://github.com/Cuprate/cuprate/pull/344
- worked on improving our consensus API: https://github.com/Cuprate/cuprate/pull/366, to prepare for fast-sync.
- Started working on [issue 174](https://github.com/Cuprate/cuprate/issues/174): https://github.com/Cuprate/cuprate/pull/382
- Investigated why monerod was syncing the first 100,000 blocks faster than cuprated, which lead to this PR: https://github.com/Cuprate/cuprate/pull/377
- Started working on changing monero-oxide's tx type to use compressed points: https://github.com/Cuprate/serai/tree/monero-comp-points
- Started working on fast-sync: https://github.com/Cuprate/cuprate/tree/fast-sync
All the tasks that have been started are pretty much ready just need to be cleaned up, they are all used in the fast-sync branch
which a few people have tested syncs on, the quickest sync _so far_ was just over 4 hours.
# Funding
I am asking for 40 XMR for my work in January.
$55/hr for 480 hrs at $220/XMR: 120 XMR
total: 160 XMR
...@@ -3,7 +3,7 @@ layout: wip ...@@ -3,7 +3,7 @@ layout: wip
title: Standalone AcceptXMR title: Standalone AcceptXMR
author: busyboredom author: busyboredom
date: February 31, 2023 date: February 31, 2023
amount: 14 amount: 44
milestones: milestones:
- name: Dockerize AcceptXMR - name: Dockerize AcceptXMR
funds: 14 funds: 14
...@@ -20,8 +20,22 @@ milestones: ...@@ -20,8 +20,22 @@ milestones:
payouts: payouts:
- date: 19 July 2024 - date: 19 July 2024
amount: 14 amount: 14
- date:
amount:
- date:
amount:
--- ---
_Note: this proposal has been awarded 30 XMR from [xmrSale](https://ccs.getmonero.org/proposals/xmrsale-2021.html)_
### Deadline update: July 1, 2025
Prior to the deadline, the proposer MUST provide regular updates on their progress as per the CCS rules.
If the provided updates/progress (or lack thereof) is unsatisfactory, all remaining funds **can be** relinquished either before or after the deadline.
The community will then seek another person/team to take over. If this cannot be accomplished within a reasonable timeframe, the funds will be repurposed or reallocated to a similar proposal (subject to community consensus).
# Standalone AcceptXMR # Standalone AcceptXMR
Another payment gateway CCS proposal. Another payment gateway CCS proposal.
......
...@@ -7,20 +7,20 @@ amount: 99.0 ...@@ -7,20 +7,20 @@ amount: 99.0
milestones: milestones:
- name: Month 1 - name: Month 1
funds: 33.0 funds: 33.0
status: unfinished status: finished
done: done: 22 November 2024
- name: Month 2 - name: Month 2
funds: 33.0 funds: 33.0
status: unfinished status: finished
done: done: 16 February 2025
- name: Month 3 - name: Month 3
funds: 33.0 funds: 33.0
status: unfinished status: unfinished
done: done:
payouts: payouts:
- date: - date: 6 December 2024
amount: 33.0 amount: 33.0
- date: - date: 26 February 2025
amount: 33.0 amount: 33.0
- date: - date:
amount: 33.0 amount: 33.0
......
...@@ -14,6 +14,14 @@ payouts: ...@@ -14,6 +14,14 @@ payouts:
amount: amount:
--- ---
### Deadline update: July 1, 2025
Prior to the deadline, the proposer MUST provide regular updates on their progress as per the CCS rules.
If the provided updates/progress (or lack thereof) is unsatisfactory, all remaining funds **can be** relinquished either before or after the deadline.
The community will then seek another person/team to take over. If this cannot be accomplished within a reasonable timeframe, the funds will be repurposed or reallocated to a similar proposal (subject to community consensus).
## What and Why ? ## What and Why ?
Since we have now a basic demonstrator of a wallet using a mock ledger, my next goal is to have it on a real ledger. Many components are well developed for that goal like the enote_scanner from @jberman with @SNeedlewoods modifications and the serialization functions from @jeffro256 to enable write/reading transactions into a block in a blockchain file. So the idea is to put all the components together and finish developing the remaining ones in order to have a functional (local) regtest. Since we have now a basic demonstrator of a wallet using a mock ledger, my next goal is to have it on a real ledger. Many components are well developed for that goal like the enote_scanner from @jberman with @SNeedlewoods modifications and the serialization functions from @jeffro256 to enable write/reading transactions into a block in a blockchain file. So the idea is to put all the components together and finish developing the remaining ones in order to have a functional (local) regtest.
......
...@@ -48,12 +48,12 @@ payouts: ...@@ -48,12 +48,12 @@ payouts:
amount: 70 amount: 70
- date: 13 August 2024 - date: 13 August 2024
amount: 38 amount: 38
- date: - date: 25 November 2024
amount: amount: 38.5
- date: - date: 13 December 2024
amount: amount: 118.5
- date: - date: 7 March 2025
amount: amount: 53.43
- date: - date:
amount: amount:
- date: - date:
......