Compare commits

...

10 Commits

Author SHA1 Message Date
Meowing Cat
302bf6c81a Merge branch 'master' into 'master'
Monero Poker Infrastructure Project

See merge request monero-project/ccs-proposals!461
2024-06-24 19:25:51 +00:00
luigi1111
0f8250b022 Update plowsof-ccs-coordinator-4.md 2024-06-24 16:18:42 +00:00
luigi1111
0d96a078c7 Update revuo-monero-maintenance-2024-q3.md 2024-06-24 16:17:30 +00:00
luigi1111
0f4d0a37cf Merge !467
Jeffro256 Full-time 2024 Q3

See merge request monero-project/ccs-proposals!467
2024-06-24 15:59:08 +00:00
luigi1111
4d62d57d53 Merge !466
Revuo Monero maintenance (2024 Q3)

See merge request monero-project/ccs-proposals!466
2024-06-24 15:58:27 +00:00
luigi1111
518fc223c7 Update plowsof-ccs-coordinator-4.md - ms1 2024-06-24 15:56:05 +00:00
jeffro256
0e6e925259
add jeffro256-full-time-2024Q3 2024-06-16 03:35:40 -05:00
rottenwheel
3a3ca83284 Add new file 2024-06-03 12:50:36 +00:00
Meowing Cat
7c3d8ed2e9 Update Poker-Game-for-Monero-Ecosystem.md 2024-05-14 14:37:59 +00:00
Meowing Cat
143e071ccb Add Poker Infrastructure Project 2024-05-14 00:57:18 +00:00
4 changed files with 178 additions and 6 deletions

View File

@ -0,0 +1,50 @@
layout: fr
title: Monero Poker Infrastructure with %100 True Randmness
author: Meowing Cat <meowingcate@gmail.com>
date: May 14, 2024
amount: 100
milestones:
- name: Game Server and Client (already published)
funds: 25
done:
status: unfinished
- name: SW Robustness and ensuring the game Logic is %100 true
funds: 25
done:
status: unfinished
- name: Making game client robust (especially web version)
funds: 25
done:
status: unfinished
- name: Withdrawal feature and implementing true multiplayer randomness thing
funds: 25
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
Hi, I'm Meowing Cat, Full-Stack SW Engineer (self-taught) and game Game Developer. Previously I made MoneroSharp library. (https://github.com/rohanrhu/MoneroSharp)
Things about the game:
* Play: https://meowingcat.io/projects/poker/play/
* Game Server Repo: https://github.com/rohanrhu/pokerunicorn-server
* Game Client Repo: https://github.com/rohanrhu/pokerunicorn-client
* Game Server Docs: https://rohanrhu.github.io/pokerunicorn-server/
* Website: https://rohanrhu.github.io/pokerunicorn-website/
My true multiplayer randomness protocol: https://github.com/rohanrhu/TruthfulMultiplayerRandomness
I've already published the game server and client. It has game server and client, Monero deposits, you can play multiple games simultaneously.
As long as we can fund the project I'll work on this full-time and make it purrfect and add more features. I hope you like my game.
I'm not good at writing proposals but if I can be funded for working on it full-time, I'll make it purrfect and add more features.
Thank you.

View File

@ -0,0 +1,67 @@
---
layout: fr
title: jeffro256 full-time development 2024Q3
author: jeffro256
date: June 14, 2024
amount: 146
milestones:
- name: Month 1
funds: 33% (48.0)
done:
status: unfinished
- name: Month 2
funds: 33% (49.0)
done:
status: unfinished
- name: Month 3
funds: 33% (49.0)
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
## What
In the last three months, the likely direction of the future of the Monero protocol changed
drastically with all the work done to bring FCMPs to RingCT. At my last CCS proposal, I
proposed that I would be working on the Seraphis wallet and consensus integrations. Then
I shifted gears to implementing [Jamtis-RCT](https://gist.github.com/tevador/d3656a217c0177c160b9b6219d9ebb96#).
I propose to refine this codebase and produce and LWS-client demo, in order to have these
set of features complete before the FCMP++ upgrade, assuming all goes well. This codebase
can currently construct `cryptonote::transaction`s with Jamtis info encode in the `extra` field,
and then successfully scan that data. Here is a non-exhaustive list of points that need
work with this library:
- Legacy address integration and testing
- Optimization: post-primary-view-tag scanning is about 20% slower than expected
- Testing against actual FCMP++ composition proofs
- Multi-threaded compute
- A live, over-the-wire LWS demo for evaluating the filter-assist/hidden enote trade-offs
I would also like to work on replacing `wallet2` internals with the Seraphis library 'legacy handling'
code, as discussed at this Github issue: https://github.com/seraphis-migration/wallet3/issues/64. A few people
are already working on it, but it will need a lot of manpower to bring it to fruition.
## Who
I have been contributing to the Monero core repository for [over two years](https://github.com/monero-project/monero/pulls?page=2&q=is%3Apr+author%3Ajeffro256) with a total of [68 merged commits to master](https://github.com/monero-project/monero/commits?author=jeffro256) thus far. I also began working on the Seraphis migration project, so you can see some of my contributions [here](https://github.com/seraphis-migration/monero/pulls?q=is%3Apr+author%3Ajeffro256) and [here](https://github.com/UkoeHB/monero/pulls?q=is%3Apr+author%3Ajeffro256). Some more notable contributions from this last quarter:
- Implemented [Jamtis-RCT](https://gist.github.com/tevador/d3656a217c0177c160b9b6219d9ebb96#) into the Seraphis library [here](https://github.com/jeffro256/monero/tree/jamtis_rct). This branch provides support for storing Jamtis scanning data into `tx_extra`, and performs a unit test where a pruned transaction is constructed addressed to Jamtis payment proposals, and then successfully scanned for both plain and self-send enote types. The way this branch was written merges the code paths for doing Jamtis on RingCT and Seraphis together. It could use some cleaning up, and the Seraphis multisig tests need to be updated, but otherwise all Seraphis tests are passing.
- Some other Seraphis stuff including a unified transaction format for Cryptonote, RingCT, and Squashed-Seraphis transactions.
Previous Proposals:
- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/319
- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/390
- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/421
- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/436
## Payment
I propose to work 40 hours/week for 3 months so `40 (hours/week) * 3 (months) * weeks_per_month = 40 (hours/week) * 3 (months) * (365 / 12 / 7) (weeks/month) = 521` hours total on-paper, though I usually work more than that. The proposal is broken into 3 milestones, one for each month. I am setting my hourly rate at 46 USD/hour (+1 USD/hour higher than last quarter), and at a market price of 163.97 USD/XMR, that makes for a total of 146.2 XMR. Price was calculated as 14-day simple average of opening prices on [CoinGecko](https://www.coingecko.com/en/coins/monero/historical_data) from 2024-06-01 to 2024-06-14 (day of writing), same as last quarter.

View File

@ -7,20 +7,20 @@ amount: 80.07
milestones:
- name: 2 meetings + hours worked
funds: 26.69 XMR
done:
status: unfinished
done: 2 June 2024
status: finished
- name: 2 meetings + hours worked
funds: 26.69 XMR
done:
status: unfinished
done: 2 June 2024
status: finished
- name: 2 meetings + hours worked
funds: 26.69 XMR
done:
status: unfinished
payouts:
- date:
- date: 24 June 2024
amount: 26.69
- date:
- date: 24 June 2024
amount: 26.69
- date:
amount: 26.69

View File

@ -0,0 +1,55 @@
---
layout: fr
title: Revuo Monero maintenance (2024 Q3)
author: rottenwheel
date: June 3, 2024
amount: 8
milestones:
- name: July
funds: 3
done:
status: unfinished
- name: August
funds: 3
done:
status: unfinished
- name: September
funds: 2
done:
status: unfinished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
---
# What
I will maintain Revuo Monero (https://www.revuo-xmr.com/) for the next 3 months (2024 Q3): July, August and September. There is a chance I may skip one week to tend to real life issues, in such case, next issue will just cover 2 weeks instead of 1.
Tasks:
- Daily/weekly: search, curate, structure and post new reports/stories.
- 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.)
# Who
rottenwheel, I joined the Monero community some time in 2017 by jumping into IRC, attending some Workgroup meetings, volunteering at the Monero village at DEFCON 28 in 2019 (https://redlib.zaggy.nl/r/Monero/comments/cqegma/monero_village_defcon_2019_report/), participating in community events and being involved with other community-driven, smaller projects.
As a proof of work for this specific proposal, I have, since January 2022 until now, written almost 200 issues, 195 of which were published in current Revuo's self-hosted website. That does not take into account the following enhancements.
Up to this point, all efforts behind Revuo Monero's comeback after Diego "rehrar" Salazar was let go and Revuo Monero's publication was paused for a few months, include but are not limited to:
- Light/dark theme with a toggle button (mostly in CSS/HTML, minimizing the reliance in JavaScript as much as possible; site loads everything just fine in Tor browser with strict security mode on.)
- Support and Source Code sections added.
- RSS and Support icons.
- Google fonts removed.
- Twitter and Nostr profiles set up and posting new issues every week automatically. Twitter: https://nitter.poast.org/revuoxmr; Nostr: https://primal.net/p/npub1tn8spk9zhxrctg2qym3gj8r7eq2wk6z3phrl8304wc54vt9qam4qvzw6jx
# Proposal
I will publish weekly issues (4 per month) at a rate of $100 / issue. At $157.5 / XMR this makes 8 XMR (~7.6++) (100 * 4 * 3 = $1200) to be split in 3 monthly milestones. Rounding current 7.6++ XMR to 8 XMR to cover for price votatility between Work In Progress phase and progressive milestone(s) payouts.