Hi,

I'm experiencing serious issues with my wallet.dat. After the mandatory update to the new fork my client kept crashing randomly (just shutting down with no error). Now I can't get it up because it can't open my wallet.dat file. I'm on ubuntu linux.

Will try to replace my wallet.dat with a backup copy I made earlier. Anyone with similar issues? That shouldn't happen just by using the software!

Flush(false)
wallet.dat refcount=0
wallet.dat checkpoint
wallet.dat detach
wallet.dat closed
DBFlush(false) ended               0ms
StopNode()
Committing 0 changed transactions to coin database...
*** System error: CDB() : can't open database file wallet.dat, error -30973
Error: System error: CDB() : can't open database file wallet.dat, error -30973
Error: System error: CDB() : can't open database file wallet.dat, error -30973
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
msghand thread interrupt
ProtoSharesMiner terminated
keypool return 15
ProtoSharesMiner terminated
keypool return 5
ProtoSharesMiner terminated
keypool return 7
ProtoSharesMiner terminated
keypool return 11
Flushed 9448 addresses to peers.dat  81ms
terminate called after throwing an instance of 'std::runtime_error'
  what():  CDB() : can't open database file wallet.dat, error -30973
Aborted (core dumped)

Quote from: Proto on November 10, 2013, 04:18:56 pm

I tested gigawatts implementation.

14.33 collisionspermin instead of 180 collisionspermin stock client, 32 threads.

The point is that gigawatts algorithm could yield a GPU implementation which could be a 100x faster version of a slower algorithm, with a net gain.

But I will try to change the memory requirements and see what happens on the CPU if we bring it down to using very little memory.

What were you using for CHAIN_LENGTH?

I've been running a test with CHAIN_LENGTH = 2 on a 1 CPU/1GB test box overnight and got this:
http://i.imgur.com/wknTeLb.png

If I try to run the default implementation, it crashes because it requires too much memory.  However, on a 2 CPU/2 GB test box running only one thread, I get around 2.2 hpm.  However, I need to rerun these tests because the hashperminute calculation was updated with a recent commit.


I've also updated the source code: http://pastebin.com/VTCMFQXg
It now uses the thread interruption from the recent commit and makes debug messages optional.


To compile: Pull the source from the main github branch, then take my code and overwrite momentum.cpp with it.  Compile as normal.

I first tested with CHAIN_LENGTH = 2 (default), this got me 14.33 collisionspermin. If I remember it well, it still used a lot of memory: 20 GB instead of 26GB stock client.

Setting it to 4 got me around 2 collisionspermin, with a notable reduction in memory usage.

Setting it to 32 didn't get me a collision at all in a couple of minutes. But it used very little memory.

I can play with a 16 core (32 threads w hyperthreading) machine and 64 gig memory. Let me know if you want me to test something new.

Quote from: Lighthouse on November 08, 2013, 11:53:24 pm

I would very much support BTC-e

BTC-e very strange exchange with high volume, they keep NVC and really add new coins only when coin come to top list of coins with high capitalization


Sent from my iPhone using Tapatalk

BTC-E simply hand selects coins. We not going to see that soon, it took primecoins months to get listed there. Cryptsy does many more coins, so I suspect that Protoshares is going to be listed there first. Has anyone talked to the admin of cryptsy?

Quote from: Proto on November 10, 2013, 02:36:52 pm

Very risky move. If you look at how protocol changes in other altcoins have been handled, where has always been a grace period of at least a couple of days. This gives all miners the time needed to update to a newer version.

What is going to happen if you don't get the majority of miners to adopt the new protocol in time?

That said, I've updated my miners (300+ cores) to the new protocol version. Lets hope that we get through this smooth.

I have a pool with 3000 miners that has migrated and the other major pool has too.   

Solo mining already takes a week so only 10% of the solo miners will be effected because the rest would not have found anything anyway.  If the difficulty adjusted as it should then these solo miners also wouldn't have gotten anything.  I think it will be smooth as these things go.

That is not how this works. All solo miners with the old version of the miner can be seen together as one entity with a certain hash rate. It doesn't matter that some people are not getting any blocks, some will. And its not only miners who have to upgrade, also people who just use the software to make transactions.

This could be ugly:

The old miners will just make an 4x adjustment. They accept any blocks whether it be the ones generates with lower diff (4x increase) or higher diff (32x increase max).

The new miners reject blocks with lower diff (the ones with 4x adjustment), because these blocks don't match the new requirement. However they will produce blocks much slower than the old version of the miner, so many people using an older version of the software will make invalid transactions!

Thus: Any payments made with an older version of the client could get lost and someone falling for that could easily be scammed.

Quote from: seanwang1105 on November 09, 2013, 05:11:19 pm

Guys. I feel it is really hard to buy PTS currently. Really tired. Hope it will raise 100 times. LOL

Yes, My feeling is the same, tired.

We really need an exchange!

There's the 3 BTC.

txid: 2ba81995db67a2f0c3ea4309c12a2bc2849abf6e3da6bf7d8318a9815cf6462f

Lighthouse, my PTS address is: PrwBKaXgb4np7cCYWcDcuH221BP8wtbEWW

When Proto is satisfied with confirmations.

Thanks! I can see all 3 transactions now. Once they have 3 confirmations, PTS can be released. Many thanks for escrowing all 3 trades Lighthouse! I've tipped you a bit extra for your trouble

I got a few new PMs with new offers (seems as if I've sold to low... ha), but I'm not selling any PTS anymore, at least not today. Sorry! I want to keep a bit, too

Alright thats 1.6 BTC (0.0032*500) to 1HpfvgBXsbct19nYYE9CK9bQEPxn2QvVKn

Please let me know from which address you sent it (or txid), so that I know from whom I already received it.

3 BTC sent to Proto's address: 1HpfvgBXsbct19nYYE9CK9bQEPxn2QvVKn

Will post txid when it shows on blockchain.

Oh, there should be an unconfirmed transaction by now... what did you use to send it?