Skip to content
Snippets Groups Projects

Compare revisions

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

Source

Select target project
No results found

Target

Select target project
  • monero-project/ccs-proposals
  • rehrar/ccs-proposals
  • DSal/ccs-proposals
  • el00ruobuob/ccs-proposals
  • TONGZHENGSHIJIE/ccs-proposals
  • SarangNoether/ccs-proposals
  • pwrcycle/ccs-proposals
  • onosendai/ccs-proposals
  • xeagu/ccs-proposals
  • b-g-goodell/ccs-proposals
  • xmrhaelan/ccs-proposals
  • moneromooo-monero/ccs-proposals
  • AcceptThisYouCensors/ccs-proposals
  • Needmoney90/ccs-proposals
  • erciccione/ccs-proposals
  • knueffelbund/ccs-proposals
  • xiphon/ccs-proposals
  • dsc/ccs-proposals
  • Codivorous/ccs-proposals
  • serhack/ccs-proposals
  • sgp/ccs-proposals
  • Kukks/ccs-proposals
  • gingeropolous/ccs-proposals
  • hyc/ccs-proposals
  • saumyabratadutt/ccs-proposals
  • kayront/ccs-proposals
  • rellis/ccs-proposals
  • Avantpay19/ccs-proposals
  • lazaridiscom/ccs-proposals
  • omani/ccs-proposals
  • JackBlack/ccs-proposals
  • Kyoto/ccs-proposals
  • Endogen/ccs-proposals
  • sri346/ccs-proposals
  • asymptotically/ccs-proposals
  • Avis/ccs-proposals
  • Monero/ccs-proposals
  • jtgrassie/ccs-proposals
  • Fudin/ccs-proposals
  • helloworld9998/ccs-proposals
  • lalanza808/ccs-proposals
  • TheCharlatan/ccs-proposals
  • atoc/ccs-proposals
  • randybrito/ccs-proposals
  • Ministo/ccs-proposals
  • objectorange/ccs-proposals
  • adrelanos/ccs-proposals
  • mj/ccs-proposals
  • MoneroAddict/ccs-proposals
  • h4sh3d/ccs-proposals
  • paulshapiro/ccs-proposals
  • pricode/ccs-proposals
  • naijaminer/ccs-proposals
  • niyiajayi/ccs-proposals
  • cryptosourov/ccs-proposals
  • Drowxes/ccs-proposals
  • Mon_icp/ccs-proposals
  • Madbu221b/ccs-proposals
  • suyash67/ccs-proposals
  • kdavid2008/ccs-proposals
  • xmrLovera/ccs-proposals
  • lh1008/ccs-proposals
  • jatinajwani/ccs-proposals
  • normoes/ccs-proposals
  • Wobole/ccs-proposals
  • lederstrumpf/ccs-proposals
  • AlexAnarcho/ccs-proposals
  • readifugly/ccs-proposals
  • binaryFate/ccs-proposals
  • oeAdgK01/ccs-proposals
  • nio21/ccs-proposals
  • michaelizer/ccs-proposals
  • janowitz/ccs-proposals
  • fleaw/ccs-proposals
  • gusan/ccs-proposals
  • Leo27/ccs-proposals
  • tobtoht/ccs-proposals
  • anon/ccs-proposals
  • panagot12/ccs-proposals
  • kysn/ccs-proposals
  • monerotesla/ccs-proposals
  • sahil07/ccs-proposals
  • xmronadaily/ccs-proposals
  • ClaytonBHooverIII/ccs-proposals
  • txstreet/ccs-proposals
  • Aron/ccs-proposals
  • jklein/ccs-proposals
  • wtii/ccs-proposals
  • alynoe/ccs-proposals
  • selsta/ccs-proposals
  • johnfoss67/ccs-proposals
  • benevanoff/ccs-proposals
  • op/ccs-proposals
  • cirocosta/ccs-proposals
  • ragazzo/ccs-proposals
  • 888/ccs-proposals
  • elibroftw/ccs-proposals
  • amr-monero/ccs-proposals
  • behash/ccs-proposals
  • AnonDev/ccs-proposals
  • Rucknium/ccs-proposals
  • rating89us/ccs-proposals
  • AdorableTanuki/ccs-proposals
  • neat/ccs-proposals
  • plowsoff/ccs-proposals
  • xmr_sale/ccs-proposals
  • escapethe3RA/ccs-proposals
  • DouglasTuman/ccs-proposals
  • Bl5ckj5ck/ccs-proposals
  • j-berman/ccs-proposals
  • CrypticEntertainments/ccs-proposals
  • Geroser/ccs-proposals
  • ava_haidang/ccs-proposals
  • pluja/ccs-proposals
  • msvblab/ccs-proposals
  • monerokage/ccs-proposals
  • noot/ccs-proposals
  • RogueMaven/ccs-proposals
  • xmrman/ccs-proposals
  • moneronews/ccs-proposals
  • spirobel/ccs-proposals
  • winstonsthiccbooty/ccs-proposals
  • help.ukraine/help-ukraine-to-use-monero
  • dangerousfreedom/ccs-proposals
  • moneroist/ccs-proposals
  • anon_/ccs-proposals
  • agustincruz/3-d-metal-printer-project
  • savandra/ccs-proposals
  • willk/ccs-proposals
  • max.zab/ccs-proposals
  • rimuru/ccs-proposals
  • CryptoMorpheus_/ccs-proposals
  • jeffro256_/ccs-proposals
  • m0n3r0d1c3/ccs-proposals
  • leonerone/ccs-proposals
  • marjorie69/ccs-proposals
  • monero_archive/monero-archive
  • forgotsudo/ccs-proposals
  • mikigrey321/ccs-proposals
  • anhdres/ccs-proposals
  • thelefterisjp/ccs-proposals
  • lescuer971/ccs-proposals
  • MoneroBro/ccs-proposals
  • rayatina/ccs-proposals
  • HoudiniSwap/ccs-proposals
  • nightwolf361/ccs-proposals
  • z00t/ccs-proposals
  • markofdistinction_/ccs-proposals
  • busyboredom/ccs-proposals
  • Mitchellpkt/ccs-proposals
  • Fierfek/p-2-p-publisher-monerotopia-mexico-city
  • BigmenPixel/ccs-proposals
  • cmiv/ccs-proposals
  • VOSTOEMISIO/ccs-proposals
  • valldrac/ccs-proposals
  • Titus/ccs-proposals
  • C0mradeBlin/ccs-proposals
  • kayabaNerve/ccs-proposals
  • Boog9001/ccs-proposals
  • 4rkal/ccs-proposals
  • binarybaron2/ccs-proposals-bb
  • ajs/ccs-proposals
  • sacatunquetun/ccs-proposals
  • vtnerd/ccs-proposals
  • 0xFFFC0000/ccs-proposals
  • Clodagh/ccs-proposals
  • mrcyjanek/ccs-proposals
  • detheforxmr/ccs-proposals
  • r4v3r23/ccs-proposals
  • janaka303/ccs-proposals
  • eyedeekay/ccs-proposals
  • Secrecy1337/ccs-proposals
  • rohanrhu/ccs-proposals
  • baldeagle/ccs-proposals
  • fengzie_mbz/mobazha-with-monero-in-privacy-ecommerce
  • freeross/ccs-proposals
  • DiosDelRayo/ccs-proposals
  • omnedeus/ccs-proposals
  • geonic/ccs-proposals
  • untraceable/ccs-proposals
  • ki9/ccs-proposals
  • monerobullgitlab/ccs-proposals
  • sybann/ccs-proposals-bb
  • hinto/ccs-proposals
  • HardenedSteel/ccs-proposals
  • Kewbit/ccs-proposals
  • plowsofff/ccs-proposals
  • mainnet-pat/ccs-proposals
  • SimplifiedPrivacy/ccs-proposal-carrot-animated-video
  • SimplifiedPrivacy/ccs-proposal-carrot-animated-video-b
  • SNeedlewoods/ccs-proposals
  • midipoet/ccs-proposals
  • soufiane/ccs-proposals
  • geonic1/ccs-proposals
  • v1docq47/ccs-proposals
  • fullmetalScience/ccs-proposals
  • FiatDemise/xmrchat
  • dadybayo/ccs-proposals
  • rottenwheel/ccs-proposals
  • napoly/ccs-proposals
  • techpopulus/marketplace-monero-techdaddi
  • hbs/ccs-proposals
  • acx/ccs-proposals
  • wallet-verse/ccs-proposals
  • N1co1asB1ancon1/monero-contract-system
  • SyntheticBird/ccs-proposals
206 results
Show changes
Showing
with 1070 additions and 4 deletions
---
layout: wip
title: Standalone AcceptXMR
author: busyboredom
date: February 31, 2023
amount: 44
milestones:
- name: Dockerize AcceptXMR
funds: 14
done: 5 July 2024
status: finished
- name: Wordpress Plugin
funds: 10
done:
status: unfinished
- name: Maintenance 1 year
funds: 20
done:
status: unfinished
payouts:
- date: 19 July 2024
amount: 14
- date:
amount:
- date:
amount:
---
_Note: this proposal has been awarded 30 XMR from [xmrSale](https://ccs.getmonero.org/proposals/xmrsale-2021.html)_
# Standalone AcceptXMR
Another payment gateway CCS proposal.
## Summary
I would like to create a standalone, dockerized, AcceptXMR-based payment gateway with wordpress
support.
AcceptXMR ([demo](https://busyboredom.com/projects/acceptxmr),
[docs](https://docs.rs/acceptxmr/latest/acceptxmr/),
[repo](https://github.com/busyboredom/acceptxmr/)) is a payment gateway library (or crate, in rust
lingo) I wrote as a hobby project and have made available to the community. While my library serves
its purpose well, I understand that most merchants are not programmers therefor cannot use
AcceptXMR.
This proposal aims to make AcceptXMR usable for anyone capable running a docker container and
installing a wordpress plugin.
## Why AcceptXMR
Lots of reasons!
* View pair only, no hot wallet.
* Subaddress based (as opposed to the older integrated addresses).
* Pending invoices can be stored persistently, enabling recovery from power loss.
* Ignores transactions with non-zero timelocks.
* Zero-conf works out of the box.
* No local node, wallet RPC, or block explorer needed. Just pick a public remote node.
And of course, I am already intimately familiar with it.
## How It'll Happen
I will dedicate a portion of my weekends (you can expect about 10 hours a week on average) to
completing the following milestones. There will be some weeks with more progress and others with
less, but that's the average I'll be aiming for.
### Dockerize AcceptXMR
_14 XMR from xmrSale's abandoned funding._
This is the largest milestone. I'll be taking the webserver and frontend work you see in my demo,
cleaning it up significantly to bring it up to production standards and dockerizing it for easy
setup. I will also provide documentation on how to perform that setup.
### Wordpress Plugin
_10 XMR from xmrSale's abandoned funding._
Wordpress is popular, and it has a plugin system that supports custom payment gateways. I will write
a wordpress plugin for the freshly dockerized AcceptXMR implementation. I will also provide
documentation on how to use the plugin.
### Maintenance for 1 Year
_20 XMR total, with 6 XMR coming from xmrSale's abandoned funding and the remaining 14 XMR coming
from this CCS proposal._
Both rust and monero have rapidly changing ecosystems. Left alone, my work would likely be out of
date by the end of the year due to breaking changes in my library's dependencies if nothing else.
Keeping AcceptXMR up-to-date and functional is something I currently do for free, but building out a
full standalone gateway adds overhead. For this reason, I've bookmarked 20 XMR for maintenance for 1
year from the funding date.
I am hesitant to provide target dates for first two milestones above, but I have been maintaining
AcceptXMR for over a year now and I don't plan on ghosting on it now.
## Stretch Goals / Future work
I'm not promising any of the following happens, but I'm putting it here to let the community know
it's on my radar and I want to do it if I get the opportunity:
* TOR support for the daemon RPC connection.
* A no-JS frontend. I have an example with this implemented on github, but I'll have to clean it up
a bit and integrate it into the new dockerized setup.
* ZMQ support as a more performant alternative to polling the remote node.
## Prerequisites
Before I start work on this CCS, I'll need to wrap up changes I'm making with v0.12.0 of AcceptXMR.
I'm not charging for that work, I'm just disclosing here that I need to resolve the issues in that
milestone before I start work on this CCS.
## License
AcceptXMR is dual-licensed under the MIT and Apache 2.0 licenses. I am not planning on changing the
license. It will always be under a permissive license.
## About Me
Busyboredom is _not_ an anonymous alias, you can see my minimally-redacted resume on my personal
website [busyboredom.com](https://busyboredom.com).
Proposal Expiration: January 1st, 2025.
Note: This CCS was originally intended to be funded entirely by the 30 XMR leftover from the abanoned
xmrSale project. At the request of the community, I have extended my maintenance commitment and
increased the maintenance budget by 14 XMR. This change allows CCS donors to act as a final check on
whether this proposal goes forward.
---
layout: wip
title: CCS Coordinator
author: plowsof
date: September 14, 2024
amount: 99.0
milestones:
- name: Month 1
funds: 33.0
status: finished
done: 22 November 2024
- name: Month 2
funds: 33.0
status: finished
done: 16 February 2025
- name: Month 3
funds: 33.0
status: unfinished
done:
payouts:
- date: 6 December 2024
amount: 33.0
- date: 26 February 2025
amount: 33.0
- date:
amount: 33.0
---
# Who?
Hello, plowsof here, I show up and try to be helpful. My [previous](https://ccs.getmonero.org/proposals/plowsof-com-rel.html) [proposals](https://ccs.getmonero.org/proposals/plowsof-ccs-coordinator-2.html) [happened](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/418), [previously](https://ccs.getmonero.org/proposals/plowsof-ccs-coordinator-4.html). I would like to make it happen again, and do more of the same things.
# What?
- Gather consensus for CCS proposals. (feedback from GitLab/IRC/Reddit).
- Organise bi-weekly meetings to discuss proposals / current events (more if necessary).
- Provide decisions in 1 month or less (Yes/No to being funded or if something has to be changed with the proposal to satisfy our community).
- Be impartial when communicating with CCS proposers - everyone gets a fair shake.
- Checking up on the WIP list to find / fix problems early (e.g. payments overdue or proposers AWOL).
- Take responsibility for the entire CCS process - It's my fault when 'things go wrong'.
- Someone who is online for several hours a day / 7 days a week that knows what's going on.
- Act as a liaison to Core - keep them informed of whats happening / poke them when required / handle their requests.
- As part of this CCS, you will also be sponsoring my work when quality assurance testing new features/bug fixes each release cycle in the GUI, CLI, and RPC wallets.
- And Getmonero.org contributions.
- Consultancy before / during / after the idea stage.
- Secretarial tasks for https://bounties.monero.social/ (requesting payouts upon completion of bounties and such)
# Funding
Work for 25 hours per week over the next 3 months (from September to end of November 2024) at a rate of 45€ / hour. At 147.94€ / XMR (90-day EMA) this makes ~99.0 XMR.
---
layout: cp
title: "Do they know its CCSmas time again?"
author: plowsof
date: December 25th 2023
amount: 0.069
milestones:
- name: 3+ months of transaction fees
funds: 0.069 XMR
done: 28 December 2023
status: finished
payouts:
- date:
amount: 0.069
---
## Update
We're back! here is a brief summary of events before we get testing:
- After the [CCS wallet was drained](https://github.com/monero-project/meta/issues/916) a Vote was held to determine if luigi [should continue as an escrow](https://github.com/monero-project/meta/issues/935).
- Feedback obtained from the community determined how the new CCS wallet would be created/used in a secure manner;
- A new, single-purpose, air-gapped laptop was purchased (bluetooth/wifi disabled).
- The OS is Debian, and FeatherWallet will be used to sign and transport transaction files (via QR codes)
- Special thanks to tobtoht of FeatherWallet who worked tirelessly to push out a new version with convenient air-gapped signing capabilities, and every community member who offered feedback on how to best move forward.
- The exact amount stolen + 21 XMR extra was sent to the General Fund ([X](https://twitter.com/WatchFund/status/1732391070216908886) / [nitter](https://nitter.net/WatchFund/status/1732391070216908886))
- The machine where the drained wallet resided is being [forensically anaylised](https://github.com/monero-project/meta/issues/923) to determine if it was compromised.
- Luigi will escrow a temporary wallet until the [31st March 2024](https://github.com/monero-project/meta/issues/935#issuecomment-1867257410).
We must now begin to prepare for a 'post March 31st CCS' and wish everyone a merry RandomX'mas and a happy new year!
## Milestone 1
Lets test the new CCS wallet by raising approx ~$12.16 / 0.069XMR to subsidise transaction fees for several hundred consolidations/payouts for the next 3 months.
---
layout: cp
title: HotShop Point of Sale
author: cryptogrampy
date: April 7, 2022
amount: 18
milestones:
- name: Milestone 1 - Create and publish payment code, perform basic payment generation and verification on deployed webapp
funds: 0
done: 29 May 2022
status: finished
- name: Milestone 2 - Create and publish draft Point of Sale user interface for feedback
funds: 8
done: 29 May 2022
status: finished
- name: Milestone 3 - Create finalized Point of Sale interface, create install and deployment instructions, publish freely available version
funds: 10
done: 27 May 2023
status: finished
payouts:
- date: 1 June 2022
amount: 8
- date: 7 June 2023
amount: 10
---
HotShop - a browser-based, ephemeral, no-server point of sale
**who**
Hello, it's me, your great-grandfather CryptoGrampy. You might know me on Twitter as @CryptoGrampy or from my work on the Monerod-on-Termux Android script, the Android PocketNode(tm), the Monero Drag n' Drop Electron app or from Friday morning bridge club in the cafeteria.
**what is this**
Monero is really lacking in the physical Point of Sale department. Let's fix that.
The HotShop will be a simple to use webapp with a simple aesthetic and UI similar to Kasisto (RIP) and POS.cash that can be accessed from just about any web browser (on mobile or desktop) with a slight amount of user customization (company name/image, etc).
You will be able to hit HotShop.cryptogrampy.com, enter your payment details, type in the desired XMR (optionally USD if you allow that API request) amount... a QR code and address will display, and the UI will update (payment confirmation progress as well) immediately when someone has paid the correct amount.
No hosting, private spend keys, personal servers/VPS's or payment gateways will be required. The app will be able to be added to any free web host- Github pages, etc and available for anyone to use because the magic happens in your browser (you'll be able to self-host it if you want) Users will need provide the app with their primary and view keys (no spend key involved!) on the client side (this info does NOT get sent to the server) and they will specify a remote Monero node of their choice.
The tech stack will be something like: Monero-Javascript, Vue3, and Typescript.
You'll be able to set this up at a garage sale, coffee shop, with your friends, etc and generate fresh/unused payment addresses displayed as QR codes. In the settings, you'll set your desired number of confirmations (or do zero conf!), point it at a remote Monero node of your choice, and be able to collect payments and immediately validate that they were received/watch them as they get confirmed.
You'll be able to bookmark a link on your phone/browsers that contain all of the credentials necessary to start up the POS or have a QR code on a card containing a special link in your wallet... Just scan it with any device- your friend's phone, the library computer, the ipad at your store, and Boom! you have an instant Point of Sale.
**Who does this benefit? Why do I need this when I can just use a mobile wallet?**
- I think the physical Point of Sale situation is still pretty lacking in Monero
- No existing wallets have good Point of Sale tech or UI
- Perhaps you're in a situation where you can't have a wallet app on your phone/desktop but want to receive/validate payment
- Perhaps you're in a situation where you want to be able to accept payments, but are worried about someone stealing your device or spend key wallet
- An ephemeral point of sale that sort of lives on a QR code or bookmark in your phone sounds really cool
- Maybe your mobile wallet is 1000000 blocks behind and want to IMMEDIATELY accept and verify a payment
- Don't you want to make 100% sure your buddy at the bar *actually* sent those funds? It's better than a static payment address.
Also... Need yet another payment gateway? The code for this will be written in a clean way that could be used in a NodeJS server or as a different front end implementation via simple exposed methods for instantiating the gateway, creating new payment requests and verifying payments. If I have enough time, I will publish this portion of the code separately, and ideally as an npm library.
**what does this not do**
- It's not going to keep track of payments that occurred before you hit the website (it's not going to be a full wallet). It will sync at the latest block height to have the ability to immediately begin accepting payments
- It's not going to keep track of prices, photos and items you have for sale in your store
**potential reach ideas**
- CSV export of tx's that occur in a session
- Vending machine exploration
- Pin code lock/unlock
- Display past tx's within the session in a pleasant way
- Local browser storage of user data
- Importing prices/items via github repo json files
- TOR support
- Payment completion callback (provide a POST endpoint to receive completed payment data)
**milestones**
1st milestone - Coding up the basic payment portion in a nice/clean way, publishing a mostly bug-free, minimal version for testing user setting import and payments
2nd milestone - Publish first draft of the POS interface (will be responsive), getting feedback from testers
3rd milestone - Publish functioning POS to Github pages, etc, create documentation/video demo for use and self-hosting
**amount**
I estimate that this will take about 4 to 5 weeks of mostly full time work and I am asking for 18 XMR.
**expiration**
I will be working on this in the evenings and weekends but expect to have this complete within 4-8 months.
---
layout: wip
title: Carrot Spec Peer Review
author: Monero Research Lab
date: October 11, 2024
amount: 126
milestones:
- name: Carrot spec peer review
funds:
done:
status: unfinished
payouts:
- date: 24 October 2024
amount: 126
---
## Carrot Peer Review
This CCS will provide funding for the first step towards a Carrot implementation in Monero. Carrot is a specification for a backwards-compatible addressing protocol, as well as a new wallet key hierarchy for the upcoming FCMP++ consensus upgrade. This peer review will be over the specification, not any specific implementation. CypherStack was chosen for this audit from among several firms during the Monero Resarch Lab meetings the last couple weeks.
## Scope / Deliverables
A full peer review of the spec document [[link](https://github.com/jeffro256/carrot/blob/master/carrot.md)]. Note that at the time of writing this proposal, the paper is not yet published in a peer-reviewed conference/journal.
The deliverable is a write-up which will include security proofs for all properties listed in section 9. It will also include notes on weaknesses, issues, or recommendations (if any). In the case that a security proof is not possible, a note will be included describing why that proof is not possible. In the case that CypherStack requires more funds to complete the security proofs, an MRL meeting will be held and a new CCS may be opened.
## Out of scope
- Multiparty computation. There are no specific protocols presented for this, and no corresponding security model of proofs of security.
- Collaborative construction. For the same reason as multiparty computation.
## Funding
Because CypherStack has had a long successful history with Monero, has agreed to accept the XMR directly, wishes to mitigate volatility risks, and has received upfront payment for reviews before, the 126 XMR for this review is to be paid out in full to Cypherstack immediately upon reaching the funding goal.
---
layout: cp
title: Generalized Bulletproofs Security Proofs
author: Cypher Stack
date: April 4, 2024
amount: 200
milestones:
- name: Funded
funds: 200
done: 11 April 2024
status: finished
- name: Completed
funds: 0
done: May 6th, 2024
status: finished
payouts:
- date: 11 April 2024
amount: 200
---
Hello everyone, Diego "rehrar" Salazar here on behalf of [Cypher Stack](https://cypherstack.com/). We've recently [made a proposal to review the general Seraphis paper](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/441). After some discussion with MRL, including at an official MRL meeting, it was decided that while all parties do want this done eventually, there are perhaps some more immediate wins available for Monero's privacy tech, particularly in the form of Generalized Bulletproofs (GBP).
To summarize what it is, why it's important, and what work will be done, I post a blurb from Dr. Aaron Feickert, Cypher Stack's on-staff cryptographer:
```
"Full-chain membership proofs are a construction being proposed for future Monero protocol upgrades. These proofs can be used to replace ring signatures (used in the current Monero protocol) and membership proofs (used in the proposed Seraphis protocol) to improve privacy.
The proofs use a technique called curve trees that in turn rely on a Bulletproofs arithmetic circuit protocol. However, to meet technical requirements, the arithmetic circuit protocol needs to be modified to handle Pedersen vector commitments in a specific way. The modification, called generalized Bulletproofs, was informally described, but completely implemented, in a curve trees proof-of-concept implementation by one of its authors.
In collaboration with Firo and Luke Parker, we've already done a more thorough documentation of generalized Bulletproofs to aid future implementation. To our knowledge, however, the technique has never been proven secure.
Cypher Stack proposes to develop security proofs for generalized Bulletproofs. The goal is to produce a modified Bulletproofs arithmetic circuit protocol security proof that accommodates the generalized Bulletproofs technique and shows the required properties of perfect completeness, perfect special honest-verifier zero knowledge, and computational witness-extended emulation. This will mirror the existing proof of Theorem 4 in the Bulletproofs preprint.
We stress that it is not known if the generalized Bulletproofs technique readily admits such a security proof. As such, this is a research proposal that has a nontrivial risk of failure. Should the research be successful, Cypher Stack will produce a report containing the proof. Should it fail, Cypher Stack will produce a report containing any relevant information that may be useful for other researchers."
```
A few things I (rehrar) want to emphasize on this quote.
1. There is a non-negligible chance of failure to produce a satisfying proof. If this happens, the proposal is not considered a failure, and our deliverable changes to a report for future research.
2. Much of this work will be directly applicable and cross-over with Seraphis in the future. So it's not a distraction that will delay things, in that sense.
Cypher Stack asks for a total of 200 XMR to complete the review. We add a 10% volatility buffer, bringing the total up to 220 XMR. We aim to complete the review within 1.5 calendar (actual hours are not 1.5 months of man hours, but we have other work for other clients as well) months of the proposal being funded.
EDIT: We have been asked during the community and MRL meetings to remove the volatility buffer and receive the entirety of the money up front to simplify things and get this merged faster. The original proposal above remains in its original state for posterity purposes, but the proposal has changed to reflect the new terms. The new total is 200 XMR to be paid out as soon as the proposal is merged and fully funded.
---
layout: cp
title: Triptych research and optimizations
author: Cypher Stack
date: April 8, 2021
amount: 22.86
milestones:
- name: First 20 hours complete
funds: 6.325
done: 28 June 2021
status: finished
- name: Second 20 hours complete
funds: 6.325
done: 28 July 2021
status: finished
- name: Third 20 hours complete
funds: 6.325
done:
status: unfinished
- name: Fourth 20 hours complete
funds: 6.325
done:
status: unfinished
payouts:
- date: 28 June 2021
amount: 6.325
- date: 28 July 2021
amount: 6.325
- date:
amount:
- date:
amount:
---
### Proposal closed
The remaining funds (12.65XMR) have been donated to the General Fund.
THIS PROPOSAL HAS BEEN CHANGED FROM TRIPTYCH RESEARCH OPTIMIZATIONS TO TRIPTYCH MULTISIG RESEARCH AFTER A MEETING WITH THE MONERO DEVS ON APRIL 21, 2021.
## Brief Intro
As of April 12th, 2021, Aaron "Sarang Noether" Feickert has joined Cypher Stack LLC as a resident researcher.
Cypher Stack is a for-profit LLC owned by Diego "rehrar" Salazar. It started as a design firm but has since expanded to include blockchain consultancy and digital utilities and infrastructure hosting. They already donate to the Monero Project in the form of employing Dan "pigeons" Miller as a system administrator, who is responsible for running and securing much of Monero's infrastructure including Taiga, Matrix, and other key infrastructure in conjunction with the core team.
Sarang himself needs no introduction. A previous full-time researcher of MRL paid for by the CCS, he wants to continue doing research into next-gen privacy with Monero (particularly in Triptych), hence this proposal.
## The scope
Sarang Noether and collaborators created the Triptych and Arcturus privacy protocols, which, if implemented in Monero, could allow ring sizes of greater than 100 with similar size transactions to present ones (though verification times would increase linearly).
Work is already underway to include Triptych into Monero's codebase, but one of the big question marks shrouding the new protocol is multisig. The Monero ecosystem is maturing in such a way that Monero's multisig feature is being used in more and more applications, and moving to Triptych would break the current implementation. This could potentially stop Triptych's implementation in its tracks.
The goal of this proposal would be to do further research into Triptych's multisig options. Some research has already been done, and a path forward is already known, but the details and specifics need to be ironed out. Sarang would conduct this research to see if multisig is possible, and how a migration from the old to the new might be conducted in a way that is safe, private, and efficient.
## The structure, milestones, and price.
This proposal is structured to be paid out along time-based milestones, but the time will not be consecutive. Each milestone will be paid out at intervals of 20 hours.
In other words, after 20 hours-worth of work is complete, a payout will be made to the completed milestone, but it may take one month or more to complete this 20 hours depending on time, availability, and other concurrent projects.
We are putting in a request for 80 hours (one cumulative month worth) of work. We are requesting $100/hour for this highly specialized work, which comes out to $8,000. At the exchange rate of $350/XMR we reach 22.86 XMR. We round it up to 23 and add a 10% buffer, which brings us to 25.3 requested XMR.
## The Deliverables
Deliverables to the community: Sarang will give an update every calendar month on his progress to the Monero community in the form of a Reddit post in the Monero subreddit. Other update platforms can be explored as well. Keep in mind, because of the structure of the proposal, some updates may have little to no progress as a result of other work. These reports would say as much.
Deliverables to the devs: Sarang will provide write-ups, documentation, or proof-of-concept code to the developers as applicable based on research progress and results, toward the goal of a potential future Triptych release that meets the needs of the community.
## Risks
A risk of this research is that multisig may not be possible with Triptych after all. If this is ascertained early on, further research on Triptych may be unnecessary as it will not be fit for our use given the importance of multisig in the Monero ecosystem. This means the research will stop immediately, and any partially completed milestones will be paid out to the extent of hours fulfilled. Remaining funds can be dispersed amongst other active fundraising proposals or however Core sees fit. The funds should NOT be rolled into the general fund as usual due to a conflict of interest, which is outlined below.
It is also possible that the work is finished early. If this occurs, the remaining funds from milestones will be utilized in the same manner as previously stated in the event that Triptych multisig can not be used.
## Conflict of interest
After some discussion on IRC I have added this section at the end to clarify that I, Diego Salazar, owner of Cypher Stack and employer of Sarang Noether, am also paid by the general fund to work for the Core Team. I have powers to merge in the CCS but only do so with permission from luigi1111, who oversees the whole CCS system. I recuse myself from any sort of merging or moving processes with this CCS proposal due to the conflict of interest.
Cypher Stack also has another active research contract with privacy coin Firo, and Sarang works on this project.
---
layout: cp
title: dangerousfreedom - wallet work
author: DangerousFreedom
date: September 17, 2023
amount: 64
milestones:
- name: deliver of proposed demonstrator and wallet functions
funds: 56
done: 30 March 2024
status: finished
payouts:
- date: 10 April 2024
amount: 56
---
## Note amount wasn't updated properly so there is 8 XMR left over from this proposal.
## What and Why ?
The end goal is twofold:
1) Get started with a basic variant to handle transactions both in legacy and seraphis: since a blockchain is made of blocks and blocks are made of transactions, we probably need a class to handle node queries smoothly between the classes `transaction` and `SpTxSquashedV1`. Hopefully this will generate discussions and start paving the way for future works about reading/writing data from/in the blockchain (1/4 of total time).
2) Make a basic but broad demonstrator of the seraphis_wallet by: opening a wallet, make mock transactions, make transaction proofs, show enotes and balance, close wallet. A lot of work has been done in this direction but they are not yet fully organized. So the goal is to have this basic but organized demonstrator capable of doing that (3/4 of total time).
I would work on the following tasks:
- Create the `TransactionVariant = tools::variant<transaction, SpTxSquashedV1>` to handle similar methods of these classes.
- Create unit_tests with legacy and seraphis transactions to test these methods.
- Create basic functions for wallet initialization, program flow and terminal handling.
- Create the basic components of a seraphis_wallet (basically the wallet needs to load/save the `KeyContainer`, `EnoteStore` and `TransactionHistory` components).
- Create basic function to fill `EnoteStore`.
- Use mock transactions like `construct_tx_for_mock_ledger_v1` to create txs.
- Add entries to `TransactionHistory` when a transaction creation is attempted.
- Create terminal functions to show enotes and provide knowledge proofs.
- Close/save wallet and make sure it loads everything when reopened.
All the efforts will be documented and made public on the seraphis_wallet group. Unit_tests will be provided whenever possible.
## Who?
- I did [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/298), [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/344) and [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/377) previous works.
I propose to work for 40 USD per hour, 20h per week, for 12 weeks (or until I finish all the tasks), which makes 64 XMR considering 150 USD/XMR.
---
layout: cp
title: dangerousfreedom - more Seraphis development
author: DangerousFreedom
date: September 20, 2022
amount: 120
milestones:
- name: Audit framework Seraphis.
funds: 20
done: 9 February 2023
status: finished
- name: PoC CLI Wallet.
funds: 100
done: 9 February 2023
status: finished
payouts:
- date: 23 February 2023
amount: 120
---
## TLDR
Hello, I would like your help to develop more features for Seraphis like the audit framework and a simple CLI wallet.
## What and Why ?
I will try to address the following issues:
1) Create the necessary functions and explanation for the audit framework in Seraphis, i.e., proofs of ownership, unspentness, tx in, tx out (InProof,UnspentProof,SpendProof, OutProof) and update the [legacy](https://github.com/monero-project/monero/issues/7353) protocol if necessary .
2) Help developing a wallet for Seraphis. My goal is to be able to create the necessary functions to open a wallet, perform a CLI 'transfer address amount' that would create a transaction in the Seraphis/Jamtis standards, close the wallet, re-open a new wallet where the transferred funds are, 'scan the blockchain' and transfer the funds back to the original wallet. I will closely work with koe, rbrunner and jberman to better elaborate the tasks and get feedbacks or follow-ups whenever possible. Initially, the simplest wallet would open/save/close a file, keep track of the transactions inputs and outputs, perform a transfer in the Seraphis standards and prepare everything for the serialization and storage in the blockchain. These are the minimum features I will implement. More about it [here](https://github.com/seraphis-migration/wallet3/issues/10).
## Who
- I created the website [www.moneroinflation.com](www.moneroinflation.com) where you can find some information to improve your odds of winning a debate about the inflation issue in Monero.
- I have spotted a [fungibility issue](https://github.com/monero-project/monero/issues/8351) (Monero allows the storage of non-canonical points which harms the fungibility of transactions).
- I have spotted a [malleability issue](https://github.com/monero-project/monero/issues/8438) (Monero has wrong signatures - signatures that don't match the data stored in the blockchain according to the canonical standards, which came from a wrong operation of a function when certain conditions are not met).
- AFAIK I was the first to make an implementation of the core functions of Monero in another language and (try to) scan the whole blockchain with them.
I propose to work for 40 EUR per hour, 25h per week, for 18 weeks. Which makes 120 XMR considering 150 EUR/XMR.
If everything goes well, I believe we could have a basic PoC CLI wallet by the end of January/23 and enough achievements to move to testnet.
---
layout: wip
title: dangerousfreedom - seraphis wallet work until regtest
author: DangerousFreedom
date: March 30, 2024
amount: 80.64
milestones:
- name: deliver of proposed demonstrator of a wallet in a regtest
funds: 80.64
done:
status: unfinished
payouts:
- date:
amount:
---
## 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.
The tasks I can foresee for that goal are:
- Review @ghostway's KeyContainer to get it into its final form
- Have a working MockLedger that correctly handles legacy and seraphis enotes.
- Have a prototype of a wallet that loads a legacy wallet, derive a seraphis wallet from that and create seraphis transactions (both using Grootle proofs and FCMP) using legacy enotes.
- Create the basic functions to mine blocks and send enotes to an user.
- Save/Load the blocks into the blockchain using a LMDB database.
- Make sure to have a basic wallet working on a LMDB regtest database capable of doing basic functions like loading the wallet keys and its enote/history, transferring, visualizing and making knowledge proofs on enotes.
There are many intermediary tasks that would be necessary to do that I am not fully aware of now.
## Who?
- I did [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/298), [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/344), [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/377) and [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/409) previous works.
I propose to work for 42 USD per hour, 20h per week, for 12 weeks (or until we have a functional seraphis wallet in regtest), which makes 80.64 XMR considering 125 USD/XMR.
---
layout: cp
title: dangerousfreedom - wallet development 2
author: DangerousFreedom
date: February 26, 2022
amount: 31
milestones:
- name: deliver of proposed wallet functions
funds: 31
done: 19 September 2023
status: finished
payouts:
- date: 30 November 2023
amount: 31
---
## What and Why ?
Transaction history component with knowledge proofs
The idea is to collect transaction records (both for legacy and seraphis) authored by the wallet in order to provide the user the information he wants to look back. This component should import or update authored txs by looking at their enote's key-image and spent status.
The plan is to go in the direction of building a component to handle transactions by integrating the following non-comprehensive list of equivalent wallet2 methods into a component: get_transfers, get_payments, get_payments_out, get_unconfirmed_payments_out, get_unconfirmed_payments, export_outputs, import_outputs, import_outputs_from_str, export_payments, import_payments, import_payments_out, get_num_transfer_details, transfer_details, get_tx_proof, check_tx_proof, get_spend_proof, check_spend_proof, get_reserve_proof, check_reserve_proof.
An initial discussion about this topic can be found [here](https://github.com/seraphis-migration/wallet3/issues/49).
Since some of these functions are not purely wallet functions as they depend on a daemon, I expect to help and get help to properly interface them with a proto daemon.
All the efforts will be documented and unit_tests will be provided whenever possible.
## Who?
- I did [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/298) and [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/344) previous works and I believe I'm sharpening my skills and understanding of Jamtis and Seraphis to accomplish this work as described.
I propose to work for 30 USD per hour, 20h per week, for 8 weeks (2 months). Which makes 31 XMR considering 155 USD/XMR.
---
layout: wip
layout: cp
title: "ErCiccione: 3 more months part time work on Getmonero.org (October-December)"
author: erciccione
date: 11 October 2020
......@@ -15,14 +15,15 @@ milestones:
status: finished
- name: December
funds: 31
done:
status: unfinished
done: 31 December 2020
status: finished
payouts:
- date: 16 November 2020
amount: 30
- date: 16 December 2020
amount: 30
- date: 17 February 2021
amount: 31
---
I'm proposing to continue my part time work on Getmonero.org (monero-site repository), 20 hours a week for 3 more months.
......
---
layout: cp
title: "ErCiccione: 3 more months part time work on Getmonero.org (January-March)"
author: erciccione
date: 11 January 2021
amount: 71
milestones:
- name: January
funds: 24
done: 31 Janauary 2021
status: finished
- name: February
funds: 23
done: 28 February 2021
status: finished
- name: March
funds: 24
done: 31 March 2021
status: finished
payouts:
- date: 17 February 2021
amount: 24
- date: 47
amount: 14 March 2021
---
I'm proposing to continue my part time work on Getmonero.org (monero-site repository), 20 hours a week for 3 more months.
## What
I will work on the website in the same terms as in [my last proposal](https://ccs.getmonero.org/proposals/erciccione-website3.html), so basically:
- Triaging issues
- Adding new functionalities according to the feedback of the community
- Increasing user friendliness
- Updating obsolete sections
- Improving localization process
- Bug fixes
- Reviews
I triage or review the vast majority of the [issues](https://github.com/monero-project/monero-site/issues) and merge requests on the monero-site repository. You can also see the list of my [past direct contributions](https://github.com/monero-project/monero-site/pulls?q=is%3Apr+author%3Aerciccione) to have an idea of the work i do. I usually post updates about the website on reddit as well (see [the last one](https://www.reddit.com/r/Monero/comments/kl1zen/getmoneroorg_updated_new_faqs_new_workgroup_page/)).
## Milestones
I'm proposing to work as developer on the monero-site repository for three months at a rate of €30/hour, starting on Januyary 11th 2020, 20 hours a week. This results in a total of 71 XMR at the rate 1 XMR == €102 (10% buffer from current price).
---
layout: cp
title: "ErCiccione: 3 more months part time work on Getmonero.org (April-June) + Holiday"
author: erciccione
date: 11 April 2021
amount: 37
milestones:
- name: April
funds: 12
done: 30 April 2021
status: finished
- name: May
funds: 12
done: 31 May 2021
status: finished
- name: June
funds: 13
done: 30 June 2021
status: finished
payouts:
- date: 12 July 2021
amount: 37
---
I'm proposing to continue my part time work on Getmonero.org (monero-site repository), 20 hours a week for 3 more months. This proposal includes 2 weeks of holiday.
## Holiday
I've been working non stop on Monero for the last 4 years, most of the time 7 days a week. The only time i had to take a forced break was when my laptop was stolen. Situation that forced me to interrupt all my activities for 10 days. Since i couldn't work i waited to open another CCS proposal, effectively losing ten days of salary.
I've been feeling quite burned out for some time and i really need to take a break, that's why i included two weeks of holiday in this proposal. I will use this time to rest, but also to take care of other Monero stuff that i'm working on.
The two weeks of holiday will be in effect as soon as this proposal is merged.
## What
I will work on the website in the same terms as in [my last proposal](https://ccs.getmonero.org/proposals/erciccione-website4.html), so basically:
- Triaging issues
- Adding new functionalities according to the feedback of the community
- Increasing user friendliness
- Updating obsolete sections
- Improving localization process
- Bug fixes
- Reviews
I triage or review the vast majority of the [issues](https://github.com/monero-project/monero-site/issues) and merge requests on the monero-site repository. You can also see the list of my [past direct contributions](https://github.com/monero-project/monero-site/pulls?q=is%3Apr+author%3Aerciccione) to have an idea of the work i do. I usually post updates about the website on reddit as well (see [the last one](https://www.reddit.com/r/Monero/comments/kl1zen/getmoneroorg_updated_new_faqs_new_workgroup_page/)).
## Milestones
I'm proposing to work as developer on the monero-site repository for three months at a rate of €30/hour, starting on April 11th 2020, 20 hours a week. This results in a total of 37 XMR at the rate 1 XMR == €196 (10% buffer from current price).
---
layout: cp
title: "ErCiccione: 3 more months part time work on Getmonero.org (July-September)"
author: erciccione
date: 11 July 2021
amount: 44
milestones:
- name: July
funds: 14.7
done: 31 July 2021
status: finished
- name: August
funds: 14.7
done: 31 August 2021
status: finished
- name: September
funds: 14.6
done: 30 September 2021
status: finished
payouts:
- date: 20 August 2021
amount: 14.7
- date: 12 October 2021
amount: 29.3
---
I'm proposing to continue my part time work on Getmonero.org (monero-site repository), 20 hours a week for 3 more months.
## What
I will work on the website in the same terms as in [my last proposal](https://ccs.getmonero.org/proposals/erciccione-website5.html), so basically:
- Triaging issues
- Adding new functionalities according to the feedback of the community
- Increasing user friendliness
- Updating obsolete sections
- Improving localization process
- Bug fixes
- Reviews
I triage or review the vast majority of the [issues](https://github.com/monero-project/monero-site/issues) and pull requests on the monero-site repository. You can also see the list of my [past direct contributions](https://github.com/monero-project/monero-site/pulls?q=is%3Apr+author%3Aerciccione) to have an idea of the work i do. I usually post updates about the website on reddit as well (see [the last one](https://www.reddit.com/r/Monero/comments/nu8vch/getmoneroorg_updated_many_new_merchants_fixes_and/)).
## Milestones
I'm proposing to work as developer on the monero-site repository for three months at a rate of €30/hour, starting on July 11th 2020, 20 hours a week. This results in a total of 44 XMR at the rate 1 XMR == €163 (10% buffer from current price).
---
layout: cp
title: "ErCiccione: 3 more months part time work on Getmonero.org (flexible)"
author: erciccione
date: 11 October 2021
amount: 33
milestones:
- name: First month
funds: 11
done: 31 December 2021
status: finished
- name: Second month
funds: 11
done: 21 October 2022
status: finished
- name: Third month
funds: 11
done: 30 October 2023
status: finished
payouts:
- date: 6 January 2022
amount: 11
- date: 25 October 2022
amount: 11
- date: 6 November 2023
amount: 11
---
I'm proposing to continue my part time work on Getmonero.org (monero-site repository), 20 hours a week for 3 more months worth of work. This is a flexible ccs proposal: The 3 months of work will not be done linearly as done up to now, but they will be distributed according to my availability. Note that i still want to complete the work on the moneropedia soon, so at least initially i will work as done until now and the flexible part of this ccs will start later on.
## What
I will work on the same items as in [my last proposal](https://ccs.getmonero.org/proposals/erciccione-website6.html), so basically:
- Triaging issues
- Adding new functionalities according to the feedback of the community
- Increasing user friendliness
- Updating obsolete sections
- Improving localization process
- Bug fixes
- Reviews
I triage or review the vast majority of the [issues](https://github.com/monero-project/monero-site/issues) and pull requests on the monero-site repository. You can also see the list of my [past direct contributions](https://github.com/monero-project/monero-site/pulls?q=is%3Apr+author%3Aerciccione) to have an idea of the work i do. I usually post updates about the website on reddit as well (see [the last one](https://www.reddit.com/r/Monero/comments/nu8vch/getmoneroorg_updated_many_new_merchants_fixes_and/)), but for this proposal might be more appropriate to share updates on the gitlab repository.
## Milestones
I'm proposing to do three months worth of work on monero-site at a rate of €30/hour, starting on October 11th 2021, 20 hours a week. This results in a total of 33 XMR at the rate 1 XMR == €217 (10% buffer from current price).
---
layout: cp
title: escapethe3RA Monero Observer maintenance (2023 Q4)
author: escapethe3RA
date: Oct 12, 2023
amount: 39
milestones:
- name: October
funds: 13
done: 1 November 2023
status: finished
- name: November
funds: 13
done: 1 December 2023
status: finished
- name: December
funds: 13
done: 1 January 2024
status: finished
payouts:
- date: 7 January 2024
amount: 39
---
# What
I will continue to maintain *Monero Observer* (https://monero.observer) for the next 3 months (2023 Q4): October, November and December.
Tasks:
- Daily: search, curate, structure and post new reports/stories
- Daily: update reports, stats, changelog
- Daily/As Needed: post new *MO Community Messages*
- Daily/As Needed: post new *MO Resources*
- Daily/As Needed: post new *MO Calendar Events*
- Weekly (Sunday): publish the *Monero Dev Activity Report*
- Weekly (Saturday): publish the *MO Artistic Saturday Top 5 Report*
- Monthly/As Needed: publish the *MO Cypherpunk Transmission Report*
- Monthly (1st): publish the *MO Blitz Report*
- As Needed: housekeeping (revise and update reports)
- As Needed: outreach (engage with the community on Matrix, Reddit, XMPP, emails)
- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc)
- Optional/bonus: publish new Monero and privacy related guides, meeting logs and summaries, add new features, improvements and website sections, start new community initiatives
# Who
escapethe3RA, I have started contributing to the Monero ecosystem in August 2021 with Monero Observer and other smaller projects:
- published 1926 x daily MO stories/reports (https://monero.observer/stories)
- published 960 x on demand MO Community Messages (https://.monero.observer/tag/community)
- published 22 x monthly MO Blitz reports (https://monero.observer/tag/blitz)
- published 67 x weekly Monero Dev Activity Reports (https://monero.observer/tag/dev)
- published 56 x weekly MO XMR TA reports (https://monero.observer/tag/analysis)
- published 72 x weekly MO Artistic Saturday Top 5 Reports (https://monero.observer/tag/art)
- published 21 x on demand Monero Workgroup Meeting Log Summaries & uploaded 100 meeting logs to MO (https://monero.observer/tag/logs/)
- published 16 x on demand MO Cypherpunk Transmission reports (https://monero.observer/tag/CT)
- added 295 x on demand MO Resources (https://monero.observer/resources)
- created several Monero, privacy and security related guides (https://monero.observer/tag/guides/, https://monero.observer/verify-install-update-monero-cli-wallet-linux-guide/, https://monero.observer/ultimate-guide-new-monero-contributors/, https://monero.observer/gpg-cleartext-signatures/, https://monero.observer/gpg-generate-full-keypair/, https://monero.observer/list-anon-email-service-providers/, https://monero.observer/read-monero-observer-terminal-newsboat/, https://monero.observer/monero-cli-wallet-cheat-sheet/)
- redesigned *Monero Means Money* website, donated bounty to GF (https://moneromeans.money/, https://github.com/escapethe3RA/monero-means-money/)
- started MO Community Messages, Monero Dev Activity Report, XMR TA Report, MO Artistic Saturday, and Cypherpunk Transmission initiatives (https://monero.observer/tag/community, https://monero.observer/tag/dev/, https://monero.observer/tag/analysis, https://monero.observer/tag/art, https://monero.observer/tag/CT)
- added MO XMR Stats section (https://monero.observer/stats/)
- added MO Resources section (https://monero.observer/resources/)
- added MO Calendar section (https://monero.observer/tag/calendar/)
- added MO Blacklist section (https://monero.observer/blacklist/)
- added multiple RSS feeds (https://monero.observer/rss/)
- started self-hosting a terminal-based git server containing the MO UI source code (https://monero.observer/monero-observer-self-hosted-git-server/)
- created a hidden service for MO (https://monero.observer/monero-observer-new-server-hidden-service/)
- other project improvements (https://monero.observer/changelog/)
# Proposal
I will work for 25 hours per week over 3 months at a rate of 0.13 XMR / hour. At $150 / XMR (21 daily EMA) this makes 39 XMR (0.13 * 100 * 3).
---
layout: cp
title: escapethe3RA Monero Observer maintenance (2024 Q1)
author: escapethe3RA
date: Jan 19, 2024
amount: 36
milestones:
- name: January
funds: 12
done: 31 January 2024
status: finished
- name: February
funds: 12
done: 29 February 2024
status: finished
- name: March
funds: 12
done: 31 March 2024
status: finished
payouts:
- date: 9 April 2024
amount: 36
---
# What
I will continue to maintain *Monero Observer* (https://monero.observer) for the next 3 months (2024 Q1): January, February and March.
Tasks:
- Daily: search, curate, structure and post new reports/stories
- Daily: update reports, stats, changelog
- Daily/As Needed: post new *MO Community Messages*
- Daily/As Needed: post new *MO Resources*
- Daily/As Needed: post new *MO Calendar Events*
- Weekly (Sunday): publish the *Monero Dev Activity Report*
- Weekly (Saturday): publish the *MO Artistic Saturday Top 5 Report*
- Monthly/As Needed: publish the *MO Cypherpunk Transmission Report*
- Monthly (1st): publish the *MO Blitz Report*
- As Needed: housekeeping (revise and update reports)
- As Needed: outreach (engage with the community on Matrix, XMPP, email)
- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc)
- Optional/bonus: publish new Monero and privacy related guides, meeting logs and summaries, add new features, improvements and website sections, start new community initiatives
# Who
escapethe3RA, I have started contributing to the Monero ecosystem in August 2021 with Monero Observer and other smaller projects:
- published 2250 x daily MO stories/reports (https://monero.observer/stories)
- published 1087 x on demand MO Community Messages (https://.monero.observer/tag/community)
- published 25 x monthly MO Blitz reports (https://monero.observer/tag/blitz)
- published 81 x weekly Monero Dev Activity Reports (https://monero.observer/tag/dev)
- published 86 x weekly MO Artistic Saturday Top 5 Reports (https://monero.observer/tag/art)
- published 56 x weekly MO XMR TA reports (https://monero.observer/tag/analysis)
- published 24 x on demand Monero Workgroup Meeting Log Summaries & uploaded 195 meeting logs to MO (https://monero.observer/tag/logs/)
- published 17 x on demand MO Cypherpunk Transmission reports (https://monero.observer/tag/CT)
- added 305 x on demand MO Resources (https://monero.observer/resources)
- posted 295 x on demand Calendar events (https://monero.observer/tag/calendar)
- created several Monero, privacy and security related guides (https://monero.observer/tag/guides/, https://monero.observer/verify-install-update-monero-cli-wallet-linux-guide/, https://monero.observer/ultimate-guide-new-monero-contributors/, https://monero.observer/gpg-cleartext-signatures/, https://monero.observer/gpg-generate-full-keypair/, https://monero.observer/list-anon-email-service-providers/, https://monero.observer/read-monero-observer-terminal-newsboat/, https://monero.observer/monero-cli-wallet-cheat-sheet/)
- redesigned *Monero Means Money* website, donated bounty to GF (https://moneromeans.money/, https://github.com/escapethe3RA/monero-means-money/)
- started MO Community Messages, Monero Dev Activity Report, XMR TA Report, MO Artistic Saturday, and Cypherpunk Transmission initiatives (https://monero.observer/tag/community, https://monero.observer/tag/dev/, https://monero.observer/tag/analysis, https://monero.observer/tag/art, https://monero.observer/tag/CT)
- added MO XMR Stats section (https://monero.observer/stats/)
- added MO Resources section (https://monero.observer/resources/)
- added MO Calendar section (https://monero.observer/tag/calendar/)
- added MO Blacklist section (https://monero.observer/blacklist/)
- added multiple RSS feeds (https://monero.observer/rss/)
- started self-hosting a terminal-based git server containing the MO UI source code (https://monero.observer/monero-observer-self-hosted-git-server/)
- created a hidden service for MO (https://monero.observer/monero-observer-new-server-hidden-service/)
- other project improvements (https://monero.observer/changelog/)
# Proposal
I will work for 25 hours per week over 3 months at a rate of 0.12 XMR / hour. At ~$160 / XMR (21 daily EMA) this makes 36 XMR (0.12 * 100 * 3).
---
layout: cp
title: escapethe3RA Monero Observer maintenance (2024 Q2)
author: escapethe3RA
date: Apr 11, 2024
amount: 48
milestones:
- name: April
funds: 16
done: 2 May 2024
status: finished
- name: May
funds: 16
done: 1 June 2024
status: finished
- name: June
funds: 16
done: 1 July 2024
status: finished
payouts:
- date: 18 May 2024
amount: 16
- date: 17 June 2024
amount: 16
- date: 16 July 2024
amount: 16
---
# What
I will continue to maintain *Monero Observer* (https://monero.observer) for the next 3 months (2024 Q2): April, May and June.
Tasks:
- Daily: search, curate, structure and post new reports/stories
- Daily: update reports, stats, changelog
- Daily/As Needed: post new *MO Community Messages*
- Daily/As Needed: post new *MO Resources* and *Blacklist* items
- Daily/As Needed: post new *MO Calendar Events*
- Weekly (Sunday): publish the *Monero Dev Activity Report*
- Weekly (Saturday): publish the *MO Artistic Saturday Top 5 Report*
- Monthly/As Needed: publish the *MO Cypherpunk Transmission Report*
- Monthly (1st): publish the *MO Blitz Report*
- As Needed: housekeeping (revise and update reports)
- As Needed: outreach (engage with the community on Matrix, XMPP, emails)
- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc)
- Optional/bonus: publish new Monero and privacy related guides, meeting logs and summaries, add new features, improvements and website sections, start new community initiatives
# Who
escapethe3RA, I have started contributing to the Monero ecosystem in August 2021 with Monero Observer and other smaller projects:
- published 2438 x daily MO stories/reports (https://monero.observer/stories)
- published 1181 x on demand MO Community Messages (https://.monero.observer/tag/community)
- published 28 x monthly MO Blitz reports (https://monero.observer/tag/blitz)
- published 93 x weekly Monero Dev Activity Reports (https://monero.observer/tag/dev)
- published 98 x weekly MO Artistic Saturday Top 5 Reports (https://monero.observer/tag/art)
- published 56 x weekly MO XMR TA reports (https://monero.observer/tag/analysis)
- published 25 x on demand Monero Workgroup Meeting Log Summaries & uploaded 235 meeting logs to MO (https://monero.observer/tag/logs/)
- published 17 x on demand MO Cypherpunk Transmission reports (https://monero.observer/tag/CT)
- added 320 x on demand MO Resources (https://monero.observer/resources) & 16 x Blacklist items (https://monero.observer/blacklist)
- posted 336 x on demand Calendar events (https://monero.observer/tag/calendar)
- created several Monero, privacy and security related guides (https://monero.observer/tag/guides/, https://monero.observer/verify-install-update-monero-cli-wallet-linux-guide/, https://monero.observer/ultimate-guide-new-monero-contributors/, https://monero.observer/gpg-cleartext-signatures/, https://monero.observer/gpg-generate-full-keypair/, https://monero.observer/list-anon-email-service-providers/, https://monero.observer/read-monero-observer-terminal-newsboat/, https://monero.observer/monero-cli-wallet-cheat-sheet/)
- redesigned *Monero Means Money* website, donated bounty to GF (https://moneromeans.money/, https://github.com/escapethe3RA/monero-means-money/)
- started multiple MO initiatives: Community Messages, Monero Dev Activity Report, XMR TA Report, MO Artistic Saturday, and Cypherpunk Transmission (https://monero.observer/tag/community, https://monero.observer/tag/dev/, https://monero.observer/tag/analysis, https://monero.observer/tag/art, https://monero.observer/tag/CT)
- added multiple MO sections: XMR Stats, Resources, Calendar, Blacklist (https://monero.observer/stats/, https://monero.observer/resources/, https://monero.observer/tag/calendar/, https://monero.observer/blacklist/)
- added multiple RSS feeds (https://monero.observer/rss/)
- other project improvements (https://monero.observer/changelog/)
# Proposal
I will work for 25 hours per week over 3 months at a rate of 0.16 XMR / hour. At $127 / XMR (21 daily EMA) this makes 48 XMR (0.16 * 100 * 3).
---
layout: cp
title: escapethe3RA Monero Observer maintenance (2024 Q3)
author: escapethe3RA
date: Jul 10, 2024
amount: 42
milestones:
- name: July
funds: 14
done: 31 July 2024
status: finished
- name: August
funds: 14
done: 31 August 2024
status: finished
- name: September
funds: 14
done: 1 October 2024
status: finished
payouts:
- date: 5 September 2024
amount: 28
- date: 10 October 2024
amount: 14
---
# What
I will continue to maintain *Monero Observer* (https://monero.observer) for the next 3 months (2024 Q3): July, August and September.
Tasks:
- Daily: search, curate, structure and post new reports/stories
- Daily: update reports, stats, changelog
- Daily/As Needed: post new *MO Community Messages*
- Daily/As Needed: post new *MO Resources* and *Blacklist* items
- Daily/As Needed: post new *MO Calendar Events*
- Weekly (Sunday): publish the *Monero Dev Activity Report*
- Weekly (Saturday): publish the *MO Artistic Saturday Top 5 Report*
- Monthly (1st): publish the *MO Blitz Report*
- As Needed: publish the *MO Cypherpunk Transmission Report*
- As Needed: housekeeping (revise and update reports)
- As Needed: engage with the community on Matrix, XMPP, emails
- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc)
- Optional/bonus: publish new Monero and privacy related guides, meeting logs and summaries, add new features, improvements and website sections, start new community initiatives
# Who
escapethe3RA, I have started contributing to the Monero ecosystem in August 2021 with Monero Observer and other smaller projects:
- published 2677 x daily MO stories/reports (https://monero.observer/stories)
- published 1299 x on demand MO Community Messages (https://.monero.observer/tag/community)
- published 31 x monthly MO Blitz reports (https://monero.observer/tag/blitz)
- published 106 x weekly Monero Dev Activity Reports (https://monero.observer/tag/dev)
- published 112 x weekly MO Artistic Saturday Top 5 Reports (https://monero.observer/tag/art)
- published 56 x weekly MO XMR TA reports (https://monero.observer/tag/analysis)
- published 27 x on demand Monero Workgroup Meeting Log Summaries & uploaded 280 meeting logs to MO (https://monero.observer/tag/logs/)
- published 17 x on demand MO Cypherpunk Transmission reports (https://monero.observer/tag/CT)
- added 342 x on demand MO Resources (https://monero.observer/resources) & 18 x Blacklist items (https://monero.observer/blacklist)
- posted 385 x on demand Calendar events (https://monero.observer/tag/calendar)
- created several Monero, privacy and security related guides (https://monero.observer/tag/guides/, https://monero.observer/verify-install-update-monero-cli-wallet-linux-guide/, https://monero.observer/ultimate-guide-new-monero-contributors/, https://monero.observer/gpg-cleartext-signatures/, https://monero.observer/gpg-generate-full-keypair/, https://monero.observer/list-anon-email-service-providers/, https://monero.observer/read-monero-observer-terminal-newsboat/, https://monero.observer/monero-cli-wallet-cheat-sheet/)
- redesigned *Monero Means Money* website, donated bounty to GF (https://moneromeans.money/, https://github.com/escapethe3RA/monero-means-money/)
- started multiple MO initiatives: Community Messages, Monero Dev Activity Report, XMR TA Report, MO Artistic Saturday, and Cypherpunk Transmission (https://monero.observer/tag/community, https://monero.observer/tag/dev/, https://monero.observer/tag/analysis, https://monero.observer/tag/art, https://monero.observer/tag/CT)
- added multiple MO sections: XMR Stats, Resources, Calendar, Blacklist (https://monero.observer/stats/, https://monero.observer/resources/, https://monero.observer/tag/calendar/, https://monero.observer/blacklist/)
- added multiple RSS feeds (https://monero.observer/rss/)
- other project improvements (https://monero.observer/changelog/)
# Proposal
I will work for 25 hours per week over 3 months at a rate of 0.14 XMR / hour. At ~$160 / XMR (21 daily EMA) this makes 42 XMR (0.14 * 100 * 3).
\ No newline at end of file