Quote from: roundrobin on July 27, 2014, 03:58:29 PM

Quote from: xpansive on July 27, 2014, 02:54:53 PM

....

So, yes, like bitcoin, both values.

There's no policy setting in my .conf file, only dirname, chain, conf, loader (blkfile), and code3, although I thing they will be unnecessary since all of them are specified in the DataStore.py file.

But still getting the same error.

And another thing, is the 'ltc_scrypt module available from https://github.com/CryptoManiac/bitcoin-abe' (as stated in the abe doc) functional? I have it installed, but it looks it is useless...

Any other thing you could have or be doing in a different way? My coin is a very straightforward LTC clone, so if yours is running fine, mine should also work...

Thanks roundrobin.

Cheers!

I got the ltc_scrypt module from there, but as it's not used I guess it doesnt matter. The only other thing I can think of is if you are using the wrong older buggy version of pycrypto that is often installed with older versions of python, like with python 2.6 on centos. If so then replace with this version: https://pypi.python.org/pypi/pycrypto/2.6 and I changed Abe/util.py on line ~26 to "import Crypto.Hash.RIPEMD as RIPEMD160" This problem got in the way for me, took a while to find out.

Thanks again for your reply roundrobin,

I already checked that, and I discarded it as the source of my problem because my version of pycrypto is 2.6.2.

May I ask you what version of abe are you running? Mine is 0.8pre:

Code:

$ python -m Abe.abe --version
Abe 0.8pre
Schema version Abe39