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 (67)
Showing
with 635 additions and 113 deletions
---
layout: wip
layout: cp
title: "Curation of Getting to grips with Monero mini series"
author: Monero-Guides
date: November 16, 2021
......@@ -7,25 +7,23 @@ amount: 12
milestones:
- name: Importing public keys and verifying hashes
funds:
done:
status: unfinished
done: 25 April 2022
status: finished
- name: Setting up a node
funds: 5 XMR
done:
status: unfinished
done: 25 April 2022
status: finished
- name: Using Monero as money
funds:
done:
status: unfinished
done: 25 April 2022
status: finished
- name: Using monero with enhanced privacy
funds: 7 XMR
done:
status: unfinished
done: 25 April 2022
status: finished
payouts:
- date:
amount:
- date:
amount:
- date: 25 April 2022
amount: 12
---
## Preface
......
---
layout: wip
title: Funding for The Monero Moon Newsletter - 2022
author: John Foss
date: March 2, 2022
amount: 36 XMR
milestones:
- name: Publish issues #34 through #39
funds: 12 XMR
done:
status: unfinished
- name: Publish issues #40 through #45
funds: 12 XMR
done:
status: unfinished
- name: Publish issues #46 through #51
funds: 12 XMR
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
THE MONERO MOON NEWSLETTER - Funding
WHAT: The Monero Moon is a free weekly news publication created in 2018 in an effort to keep the Monero community up to date on all the latest news and developments related to Monero. I aim to achieve this by aggregating all the relevant information into one convenient location in an easy-to-digest format. I sift through the noise so you don’t have to. I also endeavour to cross promote other Monero initiatives as much as possible, while also encouraging others to participate in or support the Monero project.
The Monero Moon is independently published by myself on Medium. I have already published 32 issues. View previous issues 1-32 here. I am in the middle of trialling different newsletter platforms such as Ghost and Substack, however am yet to make the switch to a different platform.
Weekly readership has been varied, and it has appeared that readership increases the more social media promotion gains traction.
Issues from 2018 regularly had on avg 1.5k views per issue, and issues #12 to #32 have averaged 1.2k views per issue. The number of views appeared to be correlated to the price of XMR, meaning the higher the price or the more upwards trajectory the price showed correlated to view count. The most views a single issue has received was approximately 2.5k views (issues #22 & #27)
WHO: I am John Foss. Like many of you, I am a firm believer and supporter of the Monero Project. I have previously written Monero articles on Medium, a couple of How To Buy Monero Guides for the Monero.How website, and wrote Your Guide to Monero, and Why It Has Great Potential back in 2018 which I posted to r/cryptocurrency and had over 25k views and received 1.5k upvotes. Besides that, I have been following Monero for a fair while now, generally hanging out on r/xmrtrader and Twitter, and I also occasionally venture over to the IRC channels.
WHY: As Monero continues its journey, I believe it is extremely important for everyone (community members and outsiders looking in) to be able to closely follow along with all the latest news and developments surrounding Monero, whether it's the latest community update from the developers, or if Monero was featured in a large media publication. And I believe The Monero Moon will help bridge that gap. I believe that the Monero Moon will be extremely beneficial for the growth and adoption of Monero as the newsletter will continue to help spread awareness.
THE PROPOSAL AND MILESTONES: As stated in my previous CCS, as Monero grows in popularity, it takes more and more time to put together an issue from start to finish. It currently takes me about 10 hours of work per issue. This involves me researching and collating the information, writing it up, then publishing and promoting it via social media platforms.
I am proposing to publish The Monero Moon for 2 XMR per issue from 16th of March until late July 2022, or whenever the CCS is complete. At the current exchange rate of approximately $163USD per XMR based on the 20 day moving average, that comes out to ~$346 per issue which I believe is fair compensation. For example, 1000 readers is equivalent to ~0.34c per read. The milestones are straightforward, for every 6 issues I publish, payment is released. This comes out to 3 milestones in total.
Milestone 1: Publish issues #34 through #39 - 12 XMR
Milestone 2: Publish issues #40 through #45 - 12 XMR
Milestone 3: Publish issues #46 through #51 - 12 XMR
There may be periods where I miss a week due to life commitments, however I will endeavour to cover all the recent news in one big bumper newsletter issues, and this will still just count as one issue. The newsletter issues will carry on from previous publications. Additionally, at the end of this period of 18 issues published I will re-evaluate whether I shall continue the newsletter.
Cheers,
John Foss
---
layout: wip
layout: cp
title: "XMR BTC Atomic Swaps Desktop GUI"
author: binarybaron
date: October 1, 2021
......@@ -11,8 +11,8 @@ milestones:
status: finished
- name: "Tor & Rendezvous Protocol Integration"
funds: 4
done:
status: unfinished
done: 7 May 2022
status: finished
- name: "Infrastructure maintenance (October - November)"
funds: 1
done: 30 November 2021
......@@ -34,8 +34,8 @@ payouts:
amount: 45
- date: 2 April 2022
amount: 1
- date:
amount:
- date: 18 May 2022
amount: 4
---
# What
......
---
layout: wip
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:
status: unfinished
payouts:
- date: 1 June 2022
amount: 8
- date:
amount:
---
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
layout: cp
title: escapethe3RA Monero Observer maintenance (Spring 2022)
author: escapethe3RA
date: February 26, 2022
......@@ -7,23 +7,23 @@ amount: 27
milestones:
- name: March
funds: 9
done:
status: unfinished
done: 31 March 2022
status: finished
- name: April
funds: 9
done:
status: unfinished
done: 30 April 2022
status: finished
- name: May
funds: 9
done:
status: unfinished
done: 31 May 2022
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 17 April 2022
amount: 9
- date: 19 May 2022
amount: 9
- date: 29 June 2022
amount: 9
---
# What
......
---
layout: wip
title: escapethe3RA Monero Observer maintenance (Summer 2022)
author: escapethe3RA
date: May 29, 2022
amount: 36
milestones:
- name: June
funds: 12
done:
status: unfinished
- name: July
funds: 12
done:
status: unfinished
- name: August
funds: 12
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
# What
I will continue to maintain *Monero Observer* (https://monero.observer) for the next 3 months (summer 2022): June, July and August.
Tasks:
- Daily: search, curate, structure and post new reports/stories
- Daily: update stats, changelog, version control
- Daily/As Needed: post new *MO Community Messages*
- Daily/As Needed: post new *MO Resources*
- Daily/As Needed: post new *MO Calendar Events*
- Weekly (Monday): publish the *MO XMR TA Report* (technical analysis Monero price report)
- Weekly (Saturday): publish the *MO Artistic Saturday Top 5 Report*
- Weekly (Sunday): publish the *Monero Dev Activity Report*
- Monthly (1st): publish the *MO Blitz Report* (includes everything that happened the previous month)
- As Needed: housekeeping (revise stories to make sure links and content is still relevant)
- 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 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 975 x daily MO stories/reports (https://www.monero.observer/stories)
- published 37 x weekly MO XMR TA reports (https://www.monero.observer/tag/analysis)
- published 12 x weekly Monero Dev Activity Reports (https://www.monero.observer/tag/dev)
- published 18 x weekly MO Artistic Saturday Top 5 Reports (https://www.monero.observer/tag/art)
- published 9 x monthly MO Blitz reports (https://www.monero.observer/tag/blitz)
- published 294 x MO Community Messages (https://www.monero.observer/tag/community)
- published 4 x Monero Workgroup Meeting Log Summaries (https://monero.observer/tag/logs/)
- 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://www.monero.observer/ultimate-guide-new-monero-contributors/, https://www.monero.observer/gpg-cleartext-signatures/, https://www.monero.observer/gpg-generate-full-keypair/, https://monero.observer/list-anon-email-service-providers/, https://monero.observer/read-monero-observer-terminal-newsboat/)
- 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 and MO Artistic Saturday initiatives (https://www.monero.observer/tag/community, https://monero.observer/tag/dev/, https://www.monero.observer/tag/art)
- added a MO Resources section (https://www.monero.observer/resources)
- added a MO Calendar section (https://www.monero.observer/tag/calendar)
- added multiple RSS feeds (https://www.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://www.monero.observer/changelog)
# Proposal
I will work for 25 hours per week over 3 months at a rate of 0.12 XMR / hour. At $130 / XMR (21 daily EMA) this makes 36 XMR (0.12 * 100 * 3).
*Note: After this period, Monero Observer will turn 1, marking 365 days of uninterrupted daily Monero news reporting. Thanks for being a loyal reader and supporter, I am very proud to be part of the best community out there.*
---
layout: wip
title: Research Computing Upgrade
author: Gingeropolous
date: May 10, 2022
amount: 51
milestones:
- name: Expand data storage on existing server
funds: 27
done:
status: unfinished
- name: Month 1 support
funds: 8
done:
status: unfinished
- name: Month 2 support
funds: 8
done:
status: unfinished
- name: Month 3 support
funds: 8
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
---
# Gingeropolous CCS Request
Hello all! This CCS proposal is to fund me to work part time on monero in various capacities, fund some monero research computing infrastructure, and to support my official training in Computer Science. I am a long time member of the monero community, and I've always wanted to dedicate more time to Monero. I am in a place professionally where I can potentially pivot to become "full time monero" if support is available. I have a lot of projects that have interested me over the years. This first CCS is to increase the storage capacity of a particular machine, as Rucknium is embarking on a project that needs a lot of fast storage. In addition, I also requests funds for my time. In the future, I plan on submitting additional CCS requests to further improve computational and storage infrastructure for the monero research and development community, perform various monero R&D, and begin my official computer science education / training.
# Who:
I am Gingeropolous, long time community member and tinkerer. Over the years I've worked on various things in Monero. Notable things include webmin for xmrchain.net, testing fluffyblocks on mainnet (https://www.reddit.com/r/Monero/comments/6dords/help_test_fluffyblocks_compact_blocks_whatever/), and being sometimes the only mining pool for testing PoW variants during the ASIC war (remember killallasics.moneroworld.com ?). For some background, I do hold a PhD in a field of biomedical science, and I am/was a Research Assistant Professor. I came into monero years ago with no cryptocurrency, linux, or software development experience - but I've been building and working with computers for decades. I've had a lot of help from many monero contributors, and I feel i've reached a point of competance that I hope is valuable to the project. This CCS will hopefully be my first of many. During the dedicated and protected time (that I will request in the future), I hope to become even more valuable to the project through various training, infrastructure, and research activities. I have already begun my path to getting a Masters in Computer Science by working on the pre-requisite courses, as I have nothing on paper that indicates that I will perform well in a CS degree.
# What:
## Infrastructure: high end servers and tools for monero development and research
## Specific to this CCS: Funds to increase storage on existing hardware to fascilitate current research
I would like to build, maintain and administrate high-end servers for monero development and research in a cost effective manner. From my own experience in monero, it's ideal if you can just do things faster. Build something, test it / run it, tweak something, do it again. Time spent waiting for the computer to do something means you lose time and momentum - and this momentum, and time in general, is scarce for open source contributors that mostly contribute in their free time. Thus, I plan on providing high end servers to the monero developer and researcher community. Lots of ram, virtually unlimitted storage, and threads everywhere.
I've already done this at a small scale with my own funds, providing access to my existing mining hardware (with some additional memory and storage upgrades just for monero R&D) to researchers like Sarang, Rucknium, and ack-j; members of the Noncesence Research Lab, and developers like TheCharlatan, mj-xmr, jberman. For example, ack-j recently told me "Hey so that the multiprocessing worked great yesterday and saved an estimated 100 days compared to running it on my VM with 1 thread." Renting this kind of hardware from a hosting provider can get expensive. Furthermore, CCS investments in this infrastructure represesent one-time investments. Once it is built, I will provide access to the monero R&D community as long as I can keep the lights on (with or without community funding). The end goal of this effort (built over the years) will be a veritable research computing cluster with job scheduling etc (if people want that - sometimes direct shell is just easier). For the time being though, it will be much simpler - custom VM provisioning (if needed) and dedicated metal. Additionally, I will provide i2p and/or onion connections to allow any member of the community to use the resources in a private manner.
Granted, the building of this infrastructure creates an obviously centralized thing, and I'm not a huge fan of that. For the time being, I think it will be OK, but part of my future effort will include a way by which other monero folks rich in computer resources (e.g., those with big monero mining ops) can add their computers to a global monero research computational resource. To this end, a future project will include scripts that allow for anyone to launch their own Monero Research and Development cluster. For instance, a way for someone to build their own databases etc.
## Existing infrastructure in the Monero Research Computing garage:
HPE Proliant DL325 Gen10 AMD EPYC 7402P 48 thread, 64 GB RAM
ASUS Zenith 2 Alpha with 64 thread Threadripper 3970x , 256 GB ram, 2TiB NVME, 24TiB HDD. (I maxed out the RAM on this one)
some sad old opterons with 96 GB ram
~6 3900x AMD systems with 16-64gb ram and various storage abilities.
1 1920x threadripper with 32gb ram
old laptops so we can run performance tests on scrap
UPS:
N1C L-series 3000VA
Network:
1 gbps up/down with unlimitted bandwidth
1 gbps 48 port network switch
# Funds requested in this CCS:
A. 5 * 4096 Gb NVME SSDs to max out the high-speed storage capability of the Zenith 2 Alpha. Market prices have these around $1k. Currently considering Kingston KC3000 M.2
B. 3 months of part time salary support and partial costs: this will allow me to spend more time with the hardware (for instance, that new UPS isn't installed yet), focus on computer science pre-reqs, and assist with electrical costs. During this time I will also assist with whatever Monero things I can assist with - usually these involve testing software and trying to find bugs. I will also put more time into helping folks on Reddit, IRC, and Matrix. I am requesting $1500 a month.
# Timeline / Milestones:
Storage: I will purchase the drives upon full funding of the request, and request a payout once I provide a screenshot of the drives mounted.
Monthly: I will provide an update (roughly a month) when I feel I have completed enough to warrant a payout.
I have calculated the XMR based on the USD fiat price of ~~$165~~. $185 (roughly using the daily 21 ema as of commit)
I am open to any suggestions for this proposal.
Expiration 2022-12-01 (YYYY-MM-DD). If not all claimed, released to the general fund.
51 xmr total, 27 for SSDs, 8x3 for monthly support
......@@ -8,11 +8,11 @@ milestones:
- name: Month 0
funds: 151 XMR
done:
status: unfinished
status: finished
- name: Month 1
funds: 151 XMR
done:
status: unfinished
status: finished
- name: Month 2
funds: 151 XMR
done:
......@@ -28,6 +28,8 @@ milestones:
payouts:
- date: 9 April 2022
amount: 151
- date: 20 May 2022
amount: 151
---
Hello again everyone. As promised, after improving Haveno's structure, we come back with a new (much cheaper) CCS proposal.
......
---
layout: wip
title: j-berman full-time development (3 months)
author: j-berman
date: July 18, 2022
amount: 187.5 Monero
milestones:
- name: Month 1
funds: 33% (62.5 Monero)
done:
status: unfinished
- name: Month 2
funds: 33% (62.5 Monero)
done:
status: unfinished
- name: Month 3
funds: 33% (62.5 Monero)
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
## What
I'd like to continue full-time another 3 months in a similar capacity:
- Continue with PR review (especially on larger time-intensive PR's), including wrapping up [8076](https://github.com/monero-project/monero/pull/8076) (reduce wallet load and refresh time).
- Patch bugs.
- Finish the background sync mode that enables scanning for txs without a spend key. My code is [here](https://github.com/j-berman/monero/commit/238ea538f218ad447808c6806386a73bb1ab0fd5) and is functional as is. I approached it cautiously and thoughtfully to ensure it's safe as I went along. I still have some final touches on it + tests to add to wrap it up, [described here](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/285#note_15356).
- Potential tasks:
- Start going deeply through Seraphis code, implementing Jamtis features, and working toward completing a handoff from UkoeHB -> core repo. [From @UkoeHB](https://libera.monerologs.net/monero-research-lab/20220713#c120001): "Todos after [he finishes his final poc tasks]: investigate/implement the wallet-side features of Jamtis (RIDs, Polyseed, address authentication), build wallets that use the seraphis library interface for building/handling txs and enotes (full wallet, view-only wallet, multisig full wallet, payment validator), integrate seraphis into the daemon/ledger, ...".
- My own opinion on the state of Seraphis/Jamtis: both should undergo deeper review and round(s) of audits from independent parties and earn "rough consensus" before ultimately deployed. It would also be nice to see research into trustless zk-SNARKs move further along to have a better idea of how they could fit alongside Seraphis/Jamtis. Still, I think it would be valuable to start getting more finalized audit-able code prepared, especially code that likely wouldn't be impacted by the latter (such as RIDs, Polyseed, and address authentication).
- Work together with @endogenic on factoring wallet2.
- Implement subaddresses in `monero-lws` as per [this spec](https://github.com/monero-project/meta/pull/647). At this point, moving this forward feels dependent on others in the light wallet ecosystem and isn't fully in my hands (unless enough people want subaddress support in the server and don't need a client).
- Whatever seems highest priority to work on to me that I know can add value on that comes along. As of this moment, [PR 7999](https://github.com/monero-project/monero/pull/7999) (a serialization overhaul) is a leading candidate; however, with 7999, there is a chance I'm unable to provide an adequately deep review that the PR requires as my skill level may not be at that point yet. If I do decide to work on 7999, I wouldn't count my hours toward my CCS unless those hours lead to demonstrable value that pushes what the PR aims to solve forward.
## Who
I've identified and patched several privacy issues with varying severity in the Monero ecosystem:
1. The reference wallet's decoy selection algorithm didn't select very recent spendable outputs in some cases. ([source](https://www.getmonero.org/2021/09/20/post-mortem-of-decoy-selection-bugs.html))
2. The reference wallet truncated integers in the decoy selection algorithm, which would have borked the decoy selection algorithm entirely if tx volume were to increase; in the normal case, it marginally weakened the algorithm. ([source](https://www.getmonero.org/2021/09/20/post-mortem-of-decoy-selection-bugs.html))
3. `openmonero` was still using the old proven weak decoy selection algorithm, also leaving a fingerprintable trail by decoy selection algo. ([source](https://github.com/moneroexamples/openmonero/pull/177))
4. MyMonero doesn't use the updated CLSAG fee calculation which fingerprints MyMonero txs on chain by tx fee. ([source](https://github.com/mymonero/mymonero-core-cpp/pull/35))
5. MyMonero's fee calculation->input selection logic differs ever-so-slightly from the reference wallet, resulting in a fingerprintable tx fee. ([source](https://github.com/mymonero/mymonero-core-cpp/pull/36))
6. `monero-lws` fee masking on the server also caused ever-so-slightly different fee calculations from the reference wallet, resulting in a fee fingerprintable to `monero-lws` (a fingerprint that is distinct from MyMonero). ([source](https://github.com/vtnerd/monero-lws/pull/31))
7. In PR review on the upcoming hard fork's changes to the tx fee, identified the introduction of [slightly different fee calculation logic](https://github.com/monero-project/monero/pull/7819#discussion_r804404285) that would have caused tx fees to be fingerprintable to either old or new version until the hard fork.
Most of the above took a significant amount of time to investigate and in some of the cases, patch. Some were really simple to patch, some were difficult but only took a couple lines.
Some other contributions:
- implemented [view tags](https://github.com/monero-project/monero/pull/8061) to speed up wallet scanning.
- identified and patched daemon reliability issues, especially for users of tor/i2p daemons (moved forward solving long-standing issues [6631](https://github.com/monero-project/monero/issues/6631), [6929](https://github.com/monero-project/monero/issues/6929), and [6938](https://github.com/monero-project/monero/issues/6938)):
- [Tor/i2p daemons periodically send a peer list that gets itself dropped](https://github.com/monero-project/monero/pull/8324).
- [The daemon periodically drops outgoing tor/i2p connections](https://github.com/monero-project/monero/pull/8330).
- [Tx re-relay math was off](https://github.com/monero-project/monero/pull/8326).
- since Ledger was fairly unresponsive, I implemented the changes for the upcoming hard fork needed to send and receive:
- [monero repo](https://github.com/j-berman/monero/commit/cfbd590fd63ff9e0c5ec68c618e2f3fdaf24d241)
- [ledger repo](https://github.com/j-berman/app-monero/commit/c1a6eb8bbbc1cc7974ce0938e9d8f920d0ad3ae9)
- patched a [cryptographic vulnerability in monero-python](https://github.com/monero-ecosystem/monero-python/commit/ece5b9d4cd929ced9539dca839d8a9fda4271663) (identified by kayabaNerve) where a malicious sender can get an honest recipient (who's using `monero-python` to scan for txs) to assume they received an arbitrary amount chosen by the sender (e.g. a 0.00000001 XMR tx could be made to look like 1000 XMR).
- [identified that the updated fee algorithm didn't implement the expected algorithmic block size increase at consensus](https://github.com/monero-project/monero/pull/7819#discussion_r799064615).
- implemented view tags in:
- [the onion block explorer](https://github.com/moneroexamples/onion-monero-blockchain-explorer/pull/266)
- [monero-lws](https://github.com/vtnerd/monero-lws/pull/33)
- [openmonero](https://github.com/moneroexamples/openmonero/pull/181)
## Proposal
187.5 XMR. 480 hours, 0.12 XMR/hr + $36/hr, $133/XMR from coingecko.
I'm requesting a raise from my prior CCS because I feel I have demonstrated my contributions are worth a more competitive rate, and can continue to provide (increasing) value to Monero in a full-time capacity.
---
layout: wip
title: "jeffro256: part-time dev work 2022Q3"
author: jeffro256
date: 17 May 2022
amount: 60
milestones:
- name: Month 1
funds: 33% (20 XMR)
done:
status: unfinished
- name: Month 2
funds: 33% (20 XMR)
done:
status: unfinished
- name: Month 3
funds: 34% (20 XMR)
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
## What
I propose to spend 20 hours a week for 3 months working on Monero Core and the Monero GUI. Here are some areas, in tentative order of descending importance/specificity, that I'd work on:
1. Work with @selsta to protect GUI users in "simple mode" by implementing a trusted community node system
2. Create a RPC SSL connection integrity indicator for the CLI and GUI wallets
3. Allow GUI users more fine-grained control of their SSL connections
4. Create a more thorough UI for warning users of GUI mode of high fees
5. Draft a formal Levin/Cryptonote protocol specification
6. Revamp Doxygen documentation
7. Do other general documentation of the codebase
8. Transition legacy OpenSSL code to comply with OpenSSL 3.0 (already started)
9. Explore using faster & smaller EC OpenSSL certificates in place of traditional RSA certificates
10. Continue to remove dead code, and simplify codebase, especially the (epee module)[https://github.com/monero-project/monero/pull/8211]
12. Misc developing / reviews
## Who
My name is Jeffrey Ryan and I am a senior student at Texas A&M University, currently working on completing a computer science major with a minor in both cybersecurity and mathematics. I have always been fascinated with cryptography and digital privacy, so learning about Monero during the altcoin boom of 2017 was eye-opening and exciting. Soon enough, supporting Monero became a no-brainer for someone who is passionate about digital privacy.
I got my first PR merged on March 18th, and you can see the rest of them here: <https://github.com/monero-project/monero/pulls?q=is%3Apr+is%3Amerged+author%3Ajeffro256>. So far I have been doing it as a hobby, but I would love to spend more time on this project than I currently am, as I am rather busy with schoolwork and my job. As this is my first CCS proposal, I am very open to criticism and questions, so don't be afraid to ask! I will do my best to respond in the comments below.
## Why
### Trusted community node system and high fees (1 & 4)
As can be seen in [this issue](https://github.com/monero-project/monero/issues/8298), among others, there appear to be malicious node(s) which advertise themselves as public nodes, allow users using the GUI wallet in "simple node" to connect, and respond with insanely high fees. This issue runs even deeper, and this exploit can be used to deanonymize GUI users to a certain degree in simple mode when they send transactions. There's no replacement for running your own node (and double-checking your fee amounts), but for those who choose not to, they should be able to expect at a minimum to not have their funds stolen from them.
### RPC connection integrity indicator and fine-grained SSL control (2 & 3)
Getting SSL right is difficult and nuanced. You can verify with system certificates, user-supplied certificates, accept any connection as long as it is secured, or any combination of these options. You can have certificates which sign other certificates. As it stands, the way the GUI wallet secures connections is not ideal. It more or less accepts any connection, using SSL if its available, but for no specific ccertificate, and there is not a way to specify how to connect with SSL (unlike in the CLI wallet). I want to afford the users two things: the ability to quickly asses the quality of their connections to their nodes via an elegant UI element, and the ability to tweak their SSL settings if so desired.
### Levin/Cryptonote Specification (5)
Unclear protocols cause bugs and choke out emerging projects which wish to incorporate into the ecosystem. Here are a couple recent PRs to fix bugs with the p2p/relay code:
* <https://github.com/monero-project/monero/pull/8330>
* <https://github.com/monero-project/monero/pull/8326>
* <https://github.com/monero-project/monero/pull/8324>
While it would be quite a feat to document ALL of the cryptonote protocol, it could be helpful to more thoroughly document the Levin protocol commands and the expectations surrounding the calls (interface, relay rules, ban criteria, etc). The p2p protocol of Monero is useful not only for nodes, but also for wallets and light wallet servers, especially when using untrusted connections. This was already started in [this document](https://github.com/monero-project/monero/blob/master/docs/LEVIN_PROTOCOL.md), but could certainly be fleshed out.
### OpenSSL 3.0 Compatibility (8)
It's always a nice thing to have your code compile on all your targets. In newer versions of OpenSSL, they have deprecated a large portion of the API, much of which we rely on to secure connections in Monero, particularly RPC.
### EC OpenSSL certificates (9)
Currently, we use RSA certificates for RPC SSL, but EC certificates are smaller and thus faster. This could offer speed improvements while syncing, etc. @HYC suggested the idea while I was working on moving certain parts of the codebase to OpenSSL 3.0: <https://github.com/monero-project/monero/pull/8335>.
### Nice-to-haves (6, 7, 10, 11)
All of these points do not directly affect the end-user experience but will ultimately improve the developer experience, reducing friction in the future, contributing to the long-term health of the codebase.
## Funding
* Wage: 30 USD/hr
* Hours: 12 weeks x 20 hours/week = 240 hours
* Total pay in USD: 240 hours x 30 USD/hr = $7200 USD
* Exchange rate: $116.41 USD/XMR. Calculated from one week simple average of closing prices on coinmarketcap.com
* 24 June: $126.47
* 23 June: $122.70
* 22 June: $111.18
* 21 June: $118.80
* 20 June: $117.30
* 19 June: $114.22
* 18 June: $104.18
* Total pay in XMR: $7200 USD / $116.41 USD/XMR = 61.85 XMR
Expiration Date
1 August, 2022
---
layout: fr
layout: cp
title: Deploy and maintain Monero Casino.
author: M0n3r0d1c3
date: April 4, 2022
......@@ -7,11 +7,11 @@ amount: 1
milestones:
- name: Deployment
funds: 100% (1 XMR)
done:
status: unfinished
done: 5 May 2022
status: finished
payouts:
- date:
amount:
- date: 5 May 2022
amount: 1
---
Hello! I'm M0n3r0D1c3, and I've created casino for Monero.
......
---
layout: wip
layout: cp
title: "Spanish translation and proofreading of the monero site, GUI/CLI wallets and User Guides"
author: michaelizer
date: May 28, 2021
......@@ -7,23 +7,19 @@ amount: 12
milestones:
- name: Milestone 1 - Translation and proofreading of the Monero site
funds: 33.33% (4 XMR)
done:
status: unfinished
done: 15 July 2022
status: finished
- name: Milestone 2 - Translation and proofreading of the GUI and CLI wallets
funds: 41.67% (5 XMR)
done:
status: unfinished
done: 15 July 2022
status: finished
- name: Milestone 3 - Translation and proofreading of the user guides
funds: 25% (3 XMR)
done:
status: unfinished
done: 15 July 2022
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 23 July 2022
amount: 12
---
## What the proposal is about?
......
---
layout: fr
layout: wip
title: midipoet-Oslo_Freedom_Forum_CCS_proposal.md
author: midipoet
date: April 6, 2022
amount: 8.5 XMR
milestones:
- name: Proposal funded
funds: 5 XMR
done:
status: unfinished
funds: 4.25 XMR
done: 25 April 2022
status: finished
- name: Report submitted
funds: 3.5 XMR
funds: 4.25 XMR
done:
status: unfinished
payouts:
- date:
amount:
- date: 25 April 2022
amount: 4.25
- date:
amount:
---
......
......@@ -11,19 +11,19 @@ milestones:
status: finished
- name: Month 2
funds: 34.0 XMR
done:
status: unfinished
done: 10 May 2022
status: finished
- name: Month 3
funds: 34.0 XMR
done:
status: unfinished
done: 18 June 2022
status: finished
payouts:
- date: 2 April 2022
amount: 34
- date:
amount:
- date:
amount:
- date: 18 May 2022
amount: 34
- date: 4 July 2022
amount: 34
---
......
---
layout: wip
layout: cp
title: monero-bash, a wrapper for monero written in bash, for Linux
author: hinto-janaiyo
date: March 24, 2022
......@@ -7,29 +7,27 @@ amount: 10.0 XMR
milestones:
- name: Integrated P2Pool Mining
funds: 5 XMR
done:
status: unfinished
done: 30 April 2022
status: finished
- name: RPC/Daemon API integration
funds: 3.5 XMR
done:
status: unfinished
done: 30 April 2022
status: finished
- name: Mining quickstart commands
funds: 1 XMR
done:
status: unfinished
done: 30 April 2022
status: finished
- name: Automated encrypted wallet backup
funds: 0.25 XMR
done:
status: unfinished
done: 30 April 2022
status: finished
- name: Auto GPG key verification for binaries
funds: 0.25 XMR
done:
status: unfinished
done: 30 April 2022
status: finished
payouts:
- date:
amount:
- date:
amount:
- date: 30 April 2022
amount: 10
---
# Intro
......
......@@ -7,21 +7,21 @@ amount: 43.2
milestones:
- name: MLSAG
funds: 14.4
done:
status: unfinished
done: 31 May 2022
status: finished
- name: CLSAG
funds: 14.4
done:
status: unfinished
done: 3 July 2022
status: finished
- name: Seraphis / Optimizations / Functional website delivery
funds: 14.4
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date: 2 June 2022
amount: 14.4
- date: 6 July 2022
amount: 14.4
- date:
amount:
---
......
---
layout: wip
layout: cp
title: ETH-XMR Atomic Swap Development
author: noot
date: Dec 4 2021
......@@ -15,24 +15,24 @@ milestones:
status: finished
- name: DLEq integration
funds: 12 XMR
done:
status: unfinished
done: 1 May 2022
status: finished
- name: Integration testing
funds: 8 XMR
done: 21 March 2022
status: finished
- name: Network testing
funds: 8 XMR
done:
status: unfinished
done: 24 May 2022
status: finished
- name: Pre-print paper and additional research
funds: 5 XMR
done:
status: unfinished
done: 23 June 2022
status: finished
- name: UI
funds: 10 XMR
done:
status: unfinished
done: 23 June 2022
status: finished
payouts:
- date: 28 January 2022
amount: 8
......@@ -40,14 +40,12 @@ payouts:
amount: 5
- date: 22 March 2022
amount: 8
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 27 May 2022
amount: 20
- date: 29 June 2022
amount: 5
- date: 29 June 2022
amount: 10
---
# Summary
......
---
layout: fr
layout: wip
title: New Animated Videos
author: savandra
date: April 7, 2022
......@@ -62,7 +62,7 @@ voice-over
sound effects
Considering the above, I think $1000 per minute of the animation should work out nicely.
Considering the above, I think $400 per minute of the animation should work out nicely.
Also, it's been a while since the last video, so let me know if there are any updates on how the pitch should be handled.
It is expected to complete one video a month
......
---
layout: wip
layout: cp
title: selsta part-time monero development (3 months)
author: selsta
date: 12 Jan 2022
......@@ -15,15 +15,15 @@ milestones:
status: finished
- name: March
funds: 33% (31 XMR)
done:
status: unfinished
done: 31 March 2022
status: finished
payouts:
- date: 22 February 2022
amount: 32
- date: 22 March 2022
amount: 32
- date:
amount:
- date: 18 April 2022
amount: 31
---
## What
......
---
layout: wip
title: selsta part-time monero development (3 months)
author: selsta
date: 18 Apr 2022
amount: 75
milestones:
- name: May
funds: 33% (25 XMR)
done: 31 May 2022
status: finished
- name: June
funds: 33% (25 XMR)
done: 30 June 2022
status: finished
- name: July
funds: 33% (25 XMR)
done:
status: unfinished
payouts:
- date: 13 June 2022
amount: 25
- date: 6 July 2022
amount: 25
- date:
amount:
---
## What
- Focus on preparing the next network update (Bulletproofs+, view tags, multisig fixes, ...)
- Smaller dev work on CLI and GUI
- Put effort where necessary
- Testing and reviewing pull requests (CLI, GUI, site)
- Monero release engineering for CLI and GUI
- Organizing what goes into a release
- Compiling CLI and GUI, packaging for distribution
- Writing release notes
- Misc work (user support, issue tracker maintanace, HackerOne)
## Who
selsta, I have been contributing to monero since around 2018 with over 525 merged commits. Here is a list of my previous work:
- CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
- GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
- Previous CCS: https://ccs.getmonero.org/proposals/selsta-4.html
If funded I will provide monthly updates in the CCS comment section.
## Proposal
Work for 30 hours per week over the next 3 months (from May to end of July) at a rate of 45€ / hour. At 214€ / XMR (14 day EMA) this makes 75 XMR.