Search results

I'll check tomorrow and post my findings.

Almost certain i used 5.1. (Don't have access to that machine until tomorrow) I can do one better though for future reference. Here is the db.log file. http://pastebin.com/QxZUmQs5 Edit: But then again, my original wallet from way back when has no issues whatsoever. Once again, almost positive...

The error I had above was serious. The wallet was originally made on a linux system, and then swapped into a windows system. It seems like that could of caused an issue somehow. I was able to transfer the full balance into a freshly created windows wallet. Shortly after the transaction was...

After the hardfork minimum. The reputation system that was used has not been updated for the latest version of the forum software. More than likely, will have to implement a different reputation system all together. That's going to take some time to test before adding.

doctr try wrapping your address with ' ' symbols. Like so: importprivkey 'privekey' PaperWallet true

Oddly enough, my server is using a lot more memory after switching to dstorms repo. Something added between then and chaeplins will be the largest culprit I think. Here is my p2pool fee address. As you can see, it is almost always reliably consistent. This is with a 1% fee.

nj47 Yeah. Never had it happen before though. Really expected at least an email.

Wow! Your patience is amazing. How are you handling the memory management if you don't mind me asking? I'm using 5gb of ram for one node at the moment but even that gets run over and requires a manual restart.

Swapped in main net MN wallet. Can set everything up just fine. When I go to shutdown the wallet, I get this error message. Anything that I should be concerned about?

Not that I'm aware. Possibly a slight delay with the IP to the network, but even then, I believe it waits 10 blocks for confirmation of MN creation.

I'm not sure. I do like amazon because of the web console. It makes it really fool proof for security. Plus, if you have more than one MN, it is possible to clone the original image. Amazon really does have an outstanding web interface! Finally, you can always pay for a non spot instance to...

Could be memory management issue. Maybe try lowering max connections to the daemon. Yet to see a daemon shutdown for no reason though. Are you using a small unknown provider?

I'll bet you ten dark they'll be a massive amount of volume (direction depending on the outcome) shortly after the implementation of Friday's fork. Until then, it's a waiting game.

Just a heads up to everyone, my Amazon Spot Instance was terminated without any warning from them. In fact, looking at the amazon console, I'm unable to find any information of it ever existing! The ip was 54.213.240.24 With adress XgMAEMH6CrdFUNJ1vjFkjUY59dcWXhbdHf chaeplin can you tell me...

When you copy it into usr/bin, it makes it possible to run the daemon from anywhere. The .darkcoin directory is the place the daemon looks into for information.

You could do it against the qt wallet. Just set your config file with -server.

Hate to ask this, but is more testing needed? It sounds like what yidakee did by accident could be exploitable.