So I have some questions. Not trying to troll although what I'm about to say/ask may come off that way...
can any one tell me how big the monero blockchain is? how much memory does it currently take up and roughly how much does it grow by each day?
Blockchain size is ~2.3GB takes the minimum of that on RAM, its growing about 20mb day
I've seen these numbers before but wanted it confirmed. So 20mb day or 1gb in 50 days+/-? That seems like a lot. Are you sure?
I'm thumb-sucking numbers, don't take these guesstimates as anything actual or realistic.- Embedded DB solution/implementation - 6 man weeks is a pretty solid guess, so I'll leave the $14 500
- Convertion of C-code - it's not as simple as this. Apart from this specific item, there needs to be an incremental audit and refactor. Just because the bug was lurking in a piece of C code with this doesn't mean there can't be a bug elsewhere, it's just easier to obfuscate it in C. Holistically this is an active, ongoing task, that will likely end up costing in the $80k - $140k range over many, many months.
- Finished (official) GUI - assuming all the other pieces are in place, then dEBRUYNE is correct - anything from $15k - $20k.
- C++ version of the I2P router (IP obfuscation) - this is already making rapid progress:
https://github.com/PrivacySolutions/i2pd. To get it to a point where it's usable and implementable as submodule / library I'd imagine is easily a $50k job, but I'm guessing at what orignal's hourly is.
- ... (blockchain bloat issue?) -
not really an issue, and I'm unsure as to what we'd consider "solving" it.[/color] A linear reduction? A lightweight access methodology that heavily reduces the need for local storage / bandwidth? The amount of experimentation and research needed here to find a cryptographically sound "solution" makes it hard to pin a value down.
Based on the details provided by Nekomata above, how is blockchain bloat considered "not really an issue"? Monero wants to grow and increase adoption but you are limiting your coin to only desktop computers and basically only 64 bit machines with plenty of ram. How will you offer mobile wallets for devices with a blockchain this big? If the blockchain wasn't so heavy on ram but increased at the rate given above, it would still be a storage issue for many devices. How will you expand your adoption and user base with this problem? To fix this, would it take a significant rewrite of the current code?
Based on the list above, there are at least $160,000 needed to complete 4 items before the blockchain bloat issue is considered. Shouldn't blockchain bloat be fixed first so you do not have to rebuild parts of the new GUI wallet that will cost "anything from $15k - $20k"? I assume that if significant changes are required to the code this could impact the wallet as well.
Wasn't there a bounty already offered and paid for a GUI wallet. One of which seems to have quite a bit of use already. Is this wallet not good enough to get some of this cost down?
"Does our community have 1000 people willing to donate 15$ now?" This question is now in 2 threads and I've brought it up in the Polo trollbox and there is still no response to it from anyone willing to donate. What happens a couple months down the line when roughly $160,000+ isn't raised for this project?
At current market value we're talking about roughly 140,000xmr or roughly 3.75% of the current supply. I think MEW has only raised like 6,600 +/- XMR so far and paid 3,300+/- of that to the devs. Risto's analysis says there are between 5,000 and 13,000 monero holder (I think these are way too high). If that's the case, where are they?
Some have said there is not a funding crisis but there is also not a solution to the problem. Smooth said it could be months before "we hit a dead end" but writing it off now like there is not a problem does not fix the problem. It just sugar coats it with an attempt to cover it up and deal with it later.
