mirror of
https://repo.getmonero.org/monero-project/ccs-proposals.git
synced 2024-12-24 15:09:24 -05:00
26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
---
|
|
layout: cp
|
|
title: More mooo coding goodness
|
|
author: moneromooo
|
|
amount: 1800
|
|
date: October 8, 2016
|
|
---
|
|
|
|
As most of you know, I am one of the main contributors to Monero.
|
|
|
|
My previous contract finished in july, and I have since continued contributing, mostly to finish off the RingCT integration, as well as various other bits and bobs.
|
|
|
|
As I said, "Once the summer is out, I might go for another similar contract.". I have to admit I was kind of browbeaten by rct and was looking forward to sunshine with no pressure. I'm now ready to commit to more work to make Monero better, if the community wants it, with a new contract along the lines of the previous one:
|
|
|
|
- 450 hours spent working on monero (previous was 450)
|
|
- A guideline of about 10 hours a week, as previously, but this is only indicative [1]
|
|
- 4 monero per hour (previous was 40 [2])
|
|
- 10 milestones, at regular 45 hours intervals (previous was 10 every 45)
|
|
- so a total of 1800 monero (previous was 18000)
|
|
|
|
[1] Over the last two contracts I have averaged a bit above that, but the variance is high-ish.
|
|
|
|
[2] Monero was cheaper then. The fiat rate is also a bit higher (~26 USD/hour vs ~19 USD/hour, but I have shown I do good work, the previous rate was pretty low, and the downside risk is a lot higher now).
|
|
|
|
As before, I will not commit to any particular piece of work, but will work on whatever needs doing to further Monero. Currently, my target is rct verification performance, and then there is multisig, though I will need help for someone who understands the crypto well to guide me.
|