Works with X11 Coins? about blockparser HOT 7 CLOSED

What is an X11 blockchain ?

On Saturday, July 5, 2014 11:43 PM, cryptocuttlefish [email protected] wrote:

I was trying to modify blockparser to work with an X11 coin (Uro) and when I try to run a command I get "warning: at depth 0 in chain, failed to locate parent block " (many of them, followed by a segmentation fault). I noticed that somebody else on a different X11 coin (Truck) was also having these problems.
Does blockparser not work with X11 blockchains?
—
Reply to this email directly or view it on GitHub.

from blockparser.

http://wiki.darkcoin.eu/wiki/X11

It's an hashing algorithm (actually 11 of them) used on some altcoins.

Besides Litecoin, I've seen successful deployments of blockparser to SHA 256 altcoins (petrodollar) and Scrypt altcoins (Nautilus, Razorcoin) but I haven't seen anybody set up a successful deployment for any other algorithms.

I'm guessing that this would take more substantial editing of the parser code than just changing the magic number and address first bits then.

from blockparser.

Well, if the hashing algorithm X11 is used for anything other than
computing the hash of the block header (litecoin uses scrypt only
for that, and sha256 is used everywhere else), then at the very least
you're going to need to add an X11 implementation to the blockparser
code.

On Sunday, July 6, 2014 8:04 AM, cryptocuttlefish [email protected] wrote:

http://wiki.darkcoin.eu/wiki/X11
It's an hashing algorithm (actually 11 of them) used on some altcoins.
Besides Litecoin, I've seen successful deployments of blockparser to SHA 256 altcoins (petrodollar) and Scrypt altcoins (Nautilus, Razorcoin) but I haven't seen anybody set up a successful deployment for any other algorithms.
I'm guessing that this would take more substantial editing of the parser code than just changing the magic number and address first bits then.
—
Reply to this email directly or view it on GitHub.

from blockparser.

Hi,

X11 is only used to hash the block header.

This is the problem I am having with my blockchain:

info: starting command "simpleStats"
end of map, reason : magic is fucked 33554428 away from EOF
Segmentation fault (core dumped)

size of the blk file is 33554432 , so it didn't see the magic in the first 4 bytes of the file

but, when looking at it in hexdump, I see the magic number just fine in the blk file.

00000000 d3 ed c9 f1 2e 01 00 00 01 00 00 00 00 00 00 00 |................|

and in parser.cpp I have:

static const uint32_t expected =
0xd3edc9f1

Thanks for taking the time.

from blockparser.

Don't suppose anyone got this working with X11 coins? Or maybe found a fork of the project that already supports it?

from blockparser.

I suspect the block header for X11 coins might be different
(as in : they might have added fields in the block header).

If so, then various adjustments to the code are required:

In parser.cpp, in function parseBlock, more stuff might need to get skipped.

In parser.cpp, in function buildblock, the variable headerSize needs a correct value.

On Wednesday, July 9, 2014 7:47 PM, morinpa [email protected] wrote:

Hi,
X11 is only used to hash the block header.
This is the problem I am having with my blockchain:
info: starting command "simpleStats"
end of map, reason : magic is fucked 33554428 away from EOF
Segmentation fault (core dumped)
size of the blk file is 33554432 , so it didn't see the magic in the first 4 bytes of the file
but, when looking at it in hexdump, I see the magic number just fine in the blk file.
00000000 d3 ed c9 f1 2e 01 00 00 01 00 00 00 00 00 00 00 |................|
and in parser.cpp I have:
static const uint32_t expected =
0xd3edc9f1
Thanks for taking the time.
—
Reply to this email directly or view it on GitHub.

from blockparser.

X11 coins are supported as of commit bd37a16

from blockparser.