Do VEIL & GIN use different versions of X16RT?

[joblo]

Gin & veil both claim they use X16RT but they are listed seperately at zergpool.
Suprminer X16RT only works for VEIL.

For GIN the miner hangs after setting stratum difficulty message, waiting for work that never comes.
I've waiting several minutes. I've seen delays of a few seconds on occasion for
some algos/pools but eventually the work arrives. With GIN it never arrives.
It's the same at zergpool and zpool.

Clearly there's a difference if zergpool lists it seperately but what is it and how to
make it work?

[1714062700]

1714062700

[1714062700]

1714062700

[1714062700]

1714062700

[1714062700]

1714062700

[andrucrypt]

Algo is the same, but Veil uses additional data in it block and job messages(for who knows why, data is useless for miner software). Check here ccminer implementation, but as I remember there is some bug causes a crash, but pretty simple to fix.

[joblo]

Thanks but that's the miner I'm using and it works for veil.

That extra code is only called after a job is received, with GIN the the job never comes.

Edit: OK I've found somehing. If I try mining GIN with X16R I get a job, so the x16rt code
in suprminer is breaking the protocol. I should be able to work around this by defining seperate
algos.

[andrucrypt]

Thanks but that's the miner I'm using and it works for veil.

That extra code is only called after a job is received, with GIN the the job never comes.

Oh, misunderstood a bit, and didn't complete the answer. x16rt in GIN is x16rt without that parsing for VEIL and using default solution few lines below. Everything else is the same as for VEIL.

That extra code is only called after a job is received, with GIN the the job never comes.

probably zergpool problem, because there is no other difference.

update: checked x16rt on zerg - works for me.

[joblo]

update: checked x16rt on zerg - works for me.

That's interesting. It doesn't for me with suprminer.

See my previous post, I may have a workaround to avoid the veil code with gin.

[andrucrypt]

That's interesting. It doesn't for me with suprminer.

I checked my own miner, not suprminer. We are talking here about protocol and pool, not about concrete miner, right?

[joblo]

I've got it working for both as 2 seperate algos. Many thanks

Suprnova has a bad habit of reusing algo names. When he made a veil miner he just
added the veil code without changing the algo name.