Isn't this the name of the corrupt wallet?

wallet.1387632456.bak

Why dump the new wallet.dat?

pywallet has more options. Try using --dumpwithbalance instead of --dumpwallet to see the balances.

I don't really know about the __db.00# files

 

No the version is fine, I used it on test wallet.

Is your wallet encrypted?
Also, are protosharesd or protoshares-qt running?

Quote from: arubi on December 17, 2013, 10:50:19 pm

Quote from: bytemaster on December 17, 2013, 05:15:51 pm

Not if you want massive hash power to find very long vanity names.


Sent from my iPhone using Tapatalk

Wait, do you mean that there will be massive hash power to find long names, or there won't?

Imagine all the hash power that is 'securing' the network would go to finding your vanity address?   You could create addresses that have very few random bits and a lot of leading 0's.  It would be like a mining pool for vanity addresses.

Well, this is exactly what I'm excited about.

Consider this bitcoin vanity address : 1abcdefghi***....
Solo-mining this address at about 18M keys/s has about a 50% chance for a hit in about 10 days

This address however : 1abcdefghij***...
Has a 50% chance for a hit in about 300 days.
A 10 characters address is not "very long" by any means

This address : 1abcdefghijk***...
Has a 50% chance for a hit in just about 24 years.

So suppose our network is what, 1000 times as strong? 10000 times? Creating addresses such as 1Encyclopedia would still take months if not years to generate.

Should miners participating in this DAC be prepared for years and years of mining?
Maybe it's not even such a bad deal, since difficulty does not change, and is just an outcome of the length of the address that's being mined?

A very interesting concept imo. I would very much like to hear more.

If a miner generate the private key for a vanity address, how do you keep it private?

Miner pass it to the final user and who can assure that the miner doesnt keep a copy?

This problem has been solved. Take a look at 'vanitygen' for bitcoin and specifically the 'keyconv' program that comes with it.

This post on bitcointalk.org explains the process pretty well:

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

Oh! you beat me to it. Expect more giveaways soon 

And so I won't stand out in the crowd...

PZaMiD9PtjBJJUobTJqn5TZ86xeKNYnMzv

Thank you!

Quote from: arubi on December 10, 2013, 04:00:35 pm

Is it not possible to map public PTS addresses to public MC2.0 addresses, then just import your private key from Protoshares on the MC2.0 wallet?

no 3rd party necessary

Yes - this is exactly how it works.

Oh Okay, so It's not like you even share your private key with anyone.

From their FAQ :

Is TREZOR compatible with other virtual currencies (like Litecoin, Namecoin etc.?)

Currently TREZOR supports Bitcoin and Litecoin. Since we are keeping TREZOR implementation agnostic, it should be possible to enlarge the scope to other significant alt-coins n the future.

I guess not

Does anyone know the values that should go into bitcoin-abe in order to parse the PTS blockchain?

magic number, genesis transaction hash.. etc.