If you delete it, it is a good idea to use a "secure erase" or "shred" type utility. Otherwise the contents may stick around in file system free space. Less of an issue for SSDs, depending on OS and other factors.

Not if the code doesn't even work because catastrophic bugs are uncovered and no one is maintaining it.

In any case I see no reason to belabor this. You already said you estimate a 5% chance of a million users, so clearly you must think there is far more than a 1% chance that it exists at all (maybe we define that as 5000+ users, which of course would include the 1m user case).

I think the original claim was trolling or if sincere then the oddsmaker is a terribly inept one. Either way not worth much attention.

We'll have to figure out what's gone wrong with the built-in seed nodes, but for now you can use one of these options on the command line:


You will only need to do that once, after that your p2pstate file will have everything it needs to connect to the network.

That is the plan but there are some bugs that needed to be fixed to actually do that; the current simplewallet build isn't quite up to the task. Some of them are fixed in github and some are waiting to be merged.

However, as long as you have your seed words recorded, in the event of a sudden failure of the site, you can be sure the fixes would be pushed through (even someone other than the core devs could do it) and you would indeed be able to recover your coins.

The current issue with the site will be resolved shortly so no reason to go into emergency recovery mode just yet.

Nothing related to coins as at all. It is a network facilities issue.

I think you need to learn what fsync does and whether or not there is one in the daemon.

But this is off topic for the thread, so let's stop now.

Which version are you using?

4 GB is plenty for that. Problems are still being found in testing (that's the point of it cf course) so it is good to be realistic about "soon". 4 GB does work (and as David pointed out, quite reasonably with an SSD), so not really an urgent issue in any case.

Valid point, but I'd just say that at 4 GB you are pretty close to a critical point where even a small increase would have a disproportionately large benefit. The blockchain on disk is currently 3.2 GB. I don't know how that translates directly to in-RAM usage but I guess it might be slightly higher (or at least higher including other code, other applications, etc.). So you are right on the cusp of it being able to fit in RAM with a bit left over for I/O buffers and not being able to fit (i.e. swapping). 6 GB would probably be much faster than 4 GB and 2 GB is definitely much slower (I've tested it).

Summary: I recommend 6+ GB for best performance currently, 2+ GB for a bare minimum (with questionable at best performance). 4 GB is in between.

See bolded above. SSD helps a lot if you are already short of RAM (which at 4 GB, you are). Bump up the RAM on there and a dozen minutes will be down to a minute or two (more or less regardless of drive).

Unless you have other problems you can leave them

p2pstate - list of nodes to try to connect to
poolstate - unconfirmed transactions sent by you or others

Looks like a corrupt blockchain save file. Unless you can restore it from a backup you will need to download a new one, or resync the whole chain.

I don't know why it happened. Maybe you ran out of free disk space while saving it? That is just a guess.

Its not going to happen.

It was a "secret" (aka ninja) premine so coinmarketcap can't really list it as a premine. Scam in any case.

https://bitcointalk.org/index.php?topic=740112.0

Thank you GreekBitcoin, Jungian and everyone for the donations.

There was one attack, but that happened before the price drop and was quickly patched, and the bcx/anonymint noise turned into much ado about nothing. (BCX was nothing but pure FUD bullshit -- probably run by a competitor. Anonymint now supports ring sigs as the most viable method of anonymity, as far as I can tell, though some minor tweaks continue to be needed in his view, and I don't necessarily disagree.)

Since that time we have added a web wallet, fixed a bunch of bugs, released a few test versions with a database, and now had someone launch a Monero version of localbitcoins. Still, the price drops.

No, the only reason it is going all to shit pricewise is simply supply and demand and nothing about the tech at all. There is a lot of mining and we just ran out of people who wanted to accumulate (in the current overall pretty negative crypto-environment). At this point the only way to find buyers for the mined coins is for the price to drop where people will average down. Until some equilibrium is reached, whenever that might be.

Better discussion for the Speculation thread though, since there is nothing fundamentally wrong with the technology as you say. It is all a market effect.

It isn't really ambiguous. It's a English word that has a pretty well defined meaning. Any nodes or any users still using it, or something very close to that.

As far as another bet on a million users or something, i don't have a strong opinion on it, so no reason to bet. I just have an opinion on 1% to exist in two years and that is absurdly low, essentially a trolling statement  (which I guess worked).

In theory this is supposed to work. There was a bug which I'm not sure whether or not has been fixed. If not then you will have to restore using an older version of simplewallet then you can use the wallet with the current version.

60 seconds is not "pretty quick" for real time trading. For something more like shapeshift, it is certainly fine.

As you say, the advantages of being trustless may outweigh the very slow trading, and lack of HFT might turn out to be an advantage, but I see this as being very questionable to assume.


Exactly!

Anything that isn't here already might well not be here (or not scale up enough to have much impact) by 2015. So that gives Monero a shot to be relatively high impact.

Yes it is maxed out doing all the swapping, since you are short of RAM. For swapping which is random access 8 MB/sec wouldn't be unexpected.