Please login or register.
This location

Fund a Developer: moneromoo will work part-time on Monero fo[...]

fluffypony posted this 8 years ago

fluffypony | 8 years ago

moneromoo is well-known contributor with a string of commits and good pull requests: https://github.com/monero-project/bitmonero/commits/master?author=moneromooo-monero

I personally support his application for funding, as does the rest of the core team. He has committed to working for 260 hours over 6 months or so (until they run out) at a total cost of 7800 XMR, ie. 30 XMR per hour. This is obviously a vastly reduced rate for a competent C / C++ developer, and moneromoo is taking on the effort in his spare time in the hopes that the XMR will be worth significantly more some day.

Milestones will be time based, with 1300 XMR released every 45 hours worked (or 35 hours for the last bit). As with all funding using the FFF (forum funding system) the funds will only be released to him on completion of a milestone and on a general community agreement that there was work done in that period. He will not be expected to put in a timesheet, per se, but he will be expected to provide a list of things he worked on and associated PRs / commits for that period.

Replies: 57
moneromooo edited 8 years ago Replies: 1 | Weight: -201 | Link [ - ]

Another 45 hours down.

This was mostly filled with the hard fork voting code, which turned out to be a larger chunk of work than I thought at first: https://github.com/moneromooo-monero/bitmonero/commits/hard-fork

I also debugged and fixed the lingering issue with bitmonerod running out of file descriptors, along with misc improvements I found while doing so: https://github.com/moneromooo-monero/bitmonero/commits/fd-leak

Another interesting bit was the mnemonics seed test, which failed on me. The test itself was actually wrong, and would fail with low probability: https://github.com/moneromooo-monero/bitmonero/commits/seed-test

Reply to: moneromooo
Gingeropolous edited 8 years ago Weight: -237 | Link [ - ]

bravo sir! 64 bit encrypted payment IDs... i need to play around with this.

I'd argue its time to make it rain!

moneromooo edited 8 years ago Replies: 1 | Weight: -243 | Link [ - ]

I reached 90 hours now, and with the following to show for the latest 45:

  • 64 bit encrypted payment IDs: https://github.com/monero-project/bitmonero/commit/a2d7a5fb49dedd6c7e024701eefc4c0beade1edd
  • misc fixes for print_tx being broken: https://github.com/monero-project/bitmonero/commit/1d678b1ee286b07fbe3904e5f282354b4ffc3810
  • use of smooth's triangular distribution to select fake outputs in the DB code: https://github.com/monero-project/bitmonero/commit/275894cdefeb80095b4b3463ec732c6e728f91b9
  • misc fixes to bring the new code closer to the original CN code to diminish the risk of accidental hard forks: https://github.com/monero-project/bitmonero/commit/533acc30eda7792c802ea8b6417917fa99b8bc2b, https://github.com/monero-project/bitmonero/commit/e63b85496790b458ac8b49d9d26c9de75b84859c, and a few more
  • A command to refresh spent status for your outputs: https://github.com/monero-project/bitmonero/commit/aa5bc351d422fd31e66e01a46b166952ef91e958 (this leaks information to the daemon, so not for use with a third party daemon, there will be a flag for this later)
  • Per tx keys can now be optionally stored in the wallet cache, and retrieved later: https://github.com/monero-project/bitmonero/commit/6c995710d8cdc8dbbb3da2d11dc8dfe335074ec9. https://github.com/monero-project/bitmonero/commit/e20a3ae011dcc8724d8131ba245141a6ef2c16e3
  • the cache file is now encrypted, as it contains private information: https://github.com/monero-project/bitmonero/commit/f19759992cbd70db8736e1485138f0af647cc047
  • misc other small fixes and improvements, the full list of commits is at https://github.com/monero-project/bitmonero/commit/f19759992cbd70db8736e1485138f0af647cc047
nioc edited 8 years ago Weight: -282 | Link [ - ]

It seems like dEBRUYNE's post that moneromoo responded to doesn't show for me. I can see part of it by hovering over Reply to:

Yes more development would be great. I feel it's not a choice of either moneromoo or somebody else later on but more devs both now and later on.

Looks like moneromoo was busy over the weekend.

Reply to: moneromooo dEBRUYNE moneromooo
dEBRUYNE edited 8 years ago Weight: -282 | Link [ - ]

An extension would be great in my opinion! There is enough room to work simultaneously and collaborate right?

Regarding the core-team: I think they currently don't have much free time to apply for this, but perhaps this will change in the future. Also, see smooth's comment regarding this -> https://bitcointalk.org/index.php?topic=583449.msg12090063#msg12090063

Perhaps @fluffypony could clarify a bit more? I would greatly appreciate if one of the core team members would pitch for x hours per week as well, even if it is at a higher rate or only for a few hours.

Reply to: dEBRUYNE moneromooo
moneromooo posted 8 years ago Replies: 1 | Weight: -283 | Link [ - ]

Thanks :)

I'd thought about possibly applying for an extension, maybe a month before finishing. However, maybe another coder may want to give this a go. I was surprised nobody from the core team replied to the original post. Maybe one of them might want to in a few months' time.

Reply to: moneromooo
dEBRUYNE posted 8 years ago Replies: 1 | Weight: -283 | Link [ - ]

At first I want to say you are doing great work and I greatly appreciate it!

Your finishing ahead of schedule got me contemplating a bit. I for instance wouldn't mind if you kept on working (if you have time left to do this) and finish the 260 hours in let's say 4-5 months instead of 6 months. Of course pay would stay the same since you put the same amount of hours into it, but this shortens the total time span. If you finish your total amount earlier, we could put you up for funding again (if you are still interested by then).

This is just a thought and I would like to hear your and other's opinions on this.

PS: Congratulations on the 25% price increase ;)

Reply to: moneromooo
antw081 edited 8 years ago Weight: -293 | Link [ + ]

Wow, great work!

moneromooo edited 8 years ago Replies: 2 | Weight: -294 | Link [ + ]

I've reached the first 45 hours, ahead of schedule, so I get some buffer for the next few months already :)

These 45 hours included:

Plus random other smaller changes dotting https://github.com/monero-project/bitmonero/commits/master

The new tx construction code is not PRed yet, I'm waiting for comments about this. It's a fairly complex change that has implications on anonimity and blockchain size.

Encrypted payment IDs are not done yet. While the commit above works, encrypted payment IDs will be decreased to 64 bit, also on blockchain.

Reply to: dEBRUYNE
moneromooo edited 8 years ago Weight: -300 | Link [ + ]

I'm still in the middle of changes to the tx construction code. While it works, it can still be better.

If you want the latest, you can hang around IRC. And https://github.com/moneromooo-monero/bitmonero/branches lets you know the very latest, before even it gets PRed.

I'll also put a recap on this thread whenever I reach a milestone, which will be kinda redundant with the "this week on github" posts I make on BCT, but only for my stuff.

Reply to: dEBRUYNE
rocco posted 8 years ago Weight: -307 | Link [ + ]

there will sure be new projects that need funding too :-) the monero about page needs content too, and yesterday there was discussion about CN internal functionallity on BCT, so new, understandable material on that is needed too.

dEBRUYNE edited 8 years ago Replies: 2 | Weight: -307 | Link [ + ]

Came back from vacation and to my pleasant suprise the target is already met! Any ideas what I should do with the 100 XMR I pledged? Should I just keep it for the next funding proposal?

@Moneromooo, it would be nice if you could give us an update every once a week (or two weeks). I hope this is feasible for you :)

moneromooo posted 8 years ago Weight: -316 | Link [ + ]

Thanks everyone!

Just to let you know, I'm currently hacking on the tx construction code, to make it less prone to problems when sending large amounts. I've got it working now (it can be used as the new "transfer_new" command in simplewallet), and I'll be making further modifications after feedback from smooth and fluffypony.

antw081 posted 8 years ago Weight: -317 | Link [ + ]

Awesome, fully funded!

45 contributions from the community - very impressive.