I believe this thread needs to be moved to work in progress, the final payment of the previous fund a developer thread paid out and any milestones met on this thread also paid out.
A continuation for all purpose programming of what needs to[...]
moneromooo posted this 8 years ago
I have now finished the second to last milestone in my current contract. I'd originally committed to a short enough time in case it wouldn't work out well, but I think this has worked quite well, so I'm proposing a new contract to follow as soon as the last milestone is done. I have had several requests about applying for an extension, so I think some people at least are keen to see that happening :)
This extension will be a pretty similar deal, but for a longer time period: a set amount of time spent working on monero. I will up the price a bit (both because it's been taking so much of my free time, and because the price of monero has gone down since then), and I will commit to more time in total, with the same average weekly time target. Even though I consistently managed at least equal to the target 10 hours a week so far, this may or may not continue.
I propose the following:
- 450 hours spent working on monero (previous was 260)
- A guideline of about 10 hours a week, as previously, but this is only indicative
- 40 monero per hour (previous was 30, but monero was also valued about a quarter higher in fiat terms)
- 10 milestones, at regular 45 hours intervals (previous was 6 every 45)
- so a total of 18000 monero (previous was 7800)
To be started as milestones get funded. There's a 12.92 leftover in the previous fund, it can probably be used to seed this one.
First 45 hours in, still going strong!
- you knew it: even more hardfork code. A testnet fork was done, and stuff went a bit wonky (the state rescan when restarting a node), so I fixed it
- more wallet refresh speedups - pulling blocks from the daemon is now parallel with the processing of the previous pulled blocks
- a fix to the longstanding crash when using a locale that boost doesn't like
- transactions are now relayed after they're first created (so if you make a tx when the daemon is offline, it'll be sent when it gets online)
- improved tracking/listing of outgoing transactions (show_transfers command)
- set store-tx-keys renamed to set store-tx-info, and now defaults to true. It now selects saving extra info from outgoing txes (address, payment id)
- merging the IP banning code from AEON, and adding new commands and RPC calls to manage bans (which AEON might want to merge)
