Topic: [ANN] Zcoin (XZC) - Implementing ZKP privacy without trusted setup - page 213. (Read 663504 times)

Quote from: HexxoDev on March 29, 2017, 04:42:30 PM

Quote from: HexxoDev on March 29, 2017, 04:31:04 PM

Quote from: HexxoDev on March 29, 2017, 04:53:34 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

because it is good for your trolling credits ? because noone goes to hexxcoin page and you need to promote somehow your clone ?

Just keep in the issue.
No promotions.

data_size = 128 fixed to wallet works perfectly.

So? What we can tell?
Should wallet give false size or use none compatible code?

Why you look at neoscrypt?
It had 84 / 80 issue that was not related to this.

Also they did not tweak the getwork code like vertcoin did, they broke it.

that didn't prevent to mine it either.
and that datasize doesn't prevent it to mine it either... and being the one who asked vertcoin dev to fix their header, it was a lot more serious than here...(when they were still running lyra2)

The conclusion

Why not just ask Zcoin devs to use the old fashion getwork.

Quote from: HexxoDev on March 29, 2017, 04:42:30 PM

Quote from: HexxoDev on March 29, 2017, 04:31:04 PM

Quote from: HexxoDev on March 29, 2017, 04:53:34 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

because it is good for your trolling credits ? because noone goes to hexxcoin page and you need to promote somehow your clone ?

Just keep in the issue.
No promotions.

data_size = 128 fixed to wallet works perfectly.

So? What we can tell?
Should wallet give false size or use none compatible code?

Why you look at neoscrypt?
It had 84 / 80 issue that was not related to this.

Also they did not tweak the getwork code like vertcoin did, they broke it.

that didn't prevent to mine it either.
and that datasize doesn't prevent it to mine it either... and being the one who asked vertcoin dev to fix their header, it was a lot more serious than here...(when they were still running lyra2)

The conclusion

Why not just ask Zcoin devs to use the old fashion getwork.

Well, I am just answering to your claim that the miners weren't working with getwork (which it did as far as I am concerned)
For the rest bring that to dev attentions on the slack channel where they hang around... (please don't use @channel Grin

)

It is not my concern. Tried just to help.
Never said gpu miner did not..

Read the fucking code and tell me who the fuck did the trick with rpcmining
it seems like cpuminer solo was prevented in the early phase..

I Have my own work to do, porting code to greater core and POS 3.0.

Thanks..

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: HexxoDev on March 29, 2017, 04:42:30 PM

Quote from: HexxoDev on March 29, 2017, 04:31:04 PM

Quote from: HexxoDev on March 29, 2017, 04:53:34 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

because it is good for your trolling credits ? because noone goes to hexxcoin page and you need to promote somehow your clone ?

Just keep in the issue.
No promotions.

data_size = 128 fixed to wallet works perfectly.

So? What we can tell?
Should wallet give false size or use none compatible code?

Why you look at neoscrypt?
It had 84 / 80 issue that was not related to this.

Also they did not tweak the getwork code like vertcoin did, they broke it.

that didn't prevent to mine it either.
and that datasize doesn't prevent it to mine it either... and being the one who asked vertcoin dev to fix their header, it was a lot more serious than here...(when they were still running lyra2)

The conclusion

Why not just ask Zcoin devs to use the old fashion getwork.

Quote from: HexxoDev on March 29, 2017, 04:42:30 PM

Quote from: HexxoDev on March 29, 2017, 04:31:04 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

because it is good for your trolling credits ? because noone goes to hexxcoin page and you need to promote somehow your clone ?

Just keep in the issue.
No promotions.

data_size = 128 fixed to wallet works perfectly.

So? What we can tell?
Should wallet give false size or use none compatible code?

Why you look at neoscrypt?
It had 84 / 80 issue that was not related to this.

Also they did not tweak the getwork code like vertcoin did, they broke it.

that didn't prevent to mine it either.
and that datasize doesn't prevent it to mine it either... and being the one who asked vertcoin dev to fix their header, it was a lot more serious than here...(when they were still running lyra2)

The conclusion

Why not just ask Zcoin devs to use the old fashion getwork.

Well, I am just answering to your claim that the miners weren't working with getwork (which they did as far as I am concerned)
For the rest bring that to dev attentions on the slack channel where they hang around... (please don't use @channel Grin

)

HexxoDev

full member

Activity: 154

Merit: 100

Quote from: HexxoDev on March 29, 2017, 04:42:30 PM

Quote from: HexxoDev on March 29, 2017, 04:31:04 PM

Quote from: HexxoDev on March 29, 2017, 04:42:30 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

because it is good for your trolling credits ? because noone goes to hexxcoin page and you need to promote somehow your clone ?

Just keep in the issue.
No promotions.

data_size = 128 fixed to wallet works perfectly.

So? What we can tell?
Should wallet give false size or use none compatible code?

Why you look at neoscrypt?
It had 84 / 80 issue that was not related to this.

Also they did not tweak the getwork code like vertcoin did, they broke it.

that didn't prevent to mine it either.
and that datasize doesn't prevent it to mine it either... and being the one who asked vertcoin dev to fix their header, it was a lot more serious than here...(when they were still running lyra2)

The conclusion

Why not just ask Zcoin devs to use the old fashion getwork.

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: HexxoDev on March 29, 2017, 04:31:04 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

because it is good for your trolling credits ? because noone goes to hexxcoin page and you need to promote somehow your clone ?

Just keep in the issue.
No promotions.

data_size = 128 fixed to wallet works perfectly.

So? What we can tell?
Should wallet give false size or use none compatible code?

Why you look at neoscrypt?
It had 84 / 80 issue that was not related to this.

Also they did not tweak the getwork code like vertcoin did, they broke it.

that didn't prevent to mine it either.
and that datasize doesn't prevent it to mine zcoin either... and being the one who asked vertcoin dev to fix their header, it was a lot more serious than here...(when they were still running lyra2)

HexxoDev

full member

Activity: 154

Merit: 100

Quote from: HexxoDev on March 29, 2017, 04:31:04 PM

Quote from: HexxoDev on March 29, 2017, 04:31:04 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

because it is good for your trolling credits ? because noone goes to hexxcoin page and you need to promote somehow your clone ?

Just keep in the issue.
No promotions.

data_size = 128 fixed to wallet, works perfectly.

So? What we can tell?
Should wallet give false size or use none compatible code?

Why you look at neoscrypt?
It had 84 / 80 issue that was not related to this.

Also they did not tweak the getwork code like vertcoin did, vertcoin broke it.
This code is a poor fork of vertcoin, all shit remains there.

- for(int i = 0; i < 4; i++)
- {
- vchData.insert(vchData.begin(), 0);
- }

Why on earth to break old working rules when not needed?

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: joblo on March 29, 2017, 04:18:54 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

because it is good for your trolling credits ? because noone goes to hexxcoin page and you need to promote somehow your clone ?

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: djm34 on March 29, 2017, 03:57:31 PM

Quote from: joblo on March 29, 2017, 03:51:05 PM

1. When you changed the size test from 128 to 132 you left the byte swap at 128.
2. Hexx getwork was broken testing for 132, fixed by testing for 128.
3. The stratum code for zcoin uses 128, why not getwork?
4. 128 is the size used by most algos, stratum and getwork.

If you're so convinced the cpuminer-opt is wrong show me a miner that works.

https://github.com/djm34/sgminer-msvc2015
https://github.com/djm34/ccminer-msvc2015
enough ?

also getwork and stratum doesn't carry the same information
getwork produce a pre-arranged ascii line with the message for a miner
stratum: full header

No. It uses 128.

Code:

static bool getwork_decode(json_t *res_val, struct work *work)
{
  size_t worklen = 128;
  worklen = ((work->pool->algorithm.type == ALGO_CRE) ? sizeof(work->data) : worklen);
  if (unlikely(!jobj_binary(res_val, "data", work->data, worklen, true))) {
    if (opt_morenotices)
      applog(LOG_ERR, "%s: JSON inval data", isnull(get_pool_name(work->pool), ""));
    return false;
}

Indeed, I also use 128 and it works... so something wrong in your code however it use only the first 19 uint32_t the 20 (in 80) being the nonce...
so don't know why you have a problem... Roll Eyes

and actually why you are complaining...
here how it is done in ccminer, as you can see we accomodate for the different wallet with what they ask...

Code:

	switch (opt_algo) {
	case ALGO_M7:
		data_size = 122;
		adata_sz = data_size / 4;
		break;
	case ALGO_DECRED:
		data_size = 192;
		adata_sz = 180/4;
		break;
	case ALGO_NEOSCRYPT:
	case ALGO_ZR5:
		data_size = 80;
		adata_sz = data_size / 4;
		break;
	default:
		data_size = 128;
		adata_sz = data_size / 4;
	}

HexxoDev

full member

Activity: 154

Merit: 100

Quote from: djm34 on March 29, 2017, 03:57:31 PM

Guys, maybe you want to meet in a chatroom, or so ?

I prefer it here?

HexxoDev

full member

Activity: 154

Merit: 100

Im too tired..

Joblo, right answer!

djm, this time you and zcoin devs cant see what is wrong..

Next episode tomorrow!

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: joblo on March 29, 2017, 03:51:05 PM

1. When you changed the size test from 128 to 132 you left the byte swap at 128.
2. Hexx getwork was broken testing for 132, fixed by testing for 128.
3. The stratum code for zcoin uses 128, why not getwork?
4. 128 is the size used by most algos, stratum and getwork.

If you're so convinced the cpuminer-opt is wrong show me a miner that works.

https://github.com/djm34/sgminer-msvc2015
https://github.com/djm34/ccminer-msvc2015
enough ?

also getwork and stratum doesn't carry the same information
getwork produce a pre-arranged ascii line with the message for a miner
stratum: full header

No. It uses 128.

Code:

static bool getwork_decode(json_t *res_val, struct work *work)
{
size_t worklen = 128;
worklen = ((work->pool->algorithm.type == ALGO_CRE) ? sizeof(work->data) : worklen);
if (unlikely(!jobj_binary(res_val, "data", work->data, worklen, true))) {
if (opt_morenotices)
applog(LOG_ERR, "%s: JSON inval data", isnull(get_pool_name(work->pool), ""));
return false;
}

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: joblo on March 29, 2017, 03:51:05 PM

1. When you changed the size test from 128 to 132 you left the byte swap at 128.
2. Hexx getwork was broken testing for 132, fixed by testing for 128.
3. The stratum code for zcoin uses 128, why not getwork?
4. 128 is the size used by most algos, stratum and getwork.

If you're so convinced the cpuminer-opt is wrong show me a miner that works.

https://github.com/djm34/sgminer-msvc2015
https://github.com/djm34/ccminer-msvc2015
enough ?

also getwork and stratum doesn't carry the same information
getwork produce a pre-arranged ascii line with the message for a miner
stratum: full header

Ivanovski

member

Activity: 79

Merit: 10

I see zcoin near zcash on coinmarketcap in near future!

joblo

legendary

Activity: 1470

Merit: 1114

1. When you changed the size test from 128 to 132 you left the byte swap at 128.
2. Hexx getwork was broken testing for 132, fixed by testing for 128.
3. The stratum code for zcoin uses 128, why not getwork?
4. 128 is the size used by most algos, stratum and getwork.

If you're so convinced the cpuminer-opt is wrong show me a miner that works.

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: HexxoDev on March 29, 2017, 03:13:58 PM

Guys, maybe you want to meet in a chatroom, or so ?

(yeah not sure why he isn't doing this on slack)

ocminer

legendary

Activity: 2702

Merit: 1240

Guys, maybe you want to meet in a chatroom, or so ?

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: djm34 on March 29, 2017, 03:11:48 PM

Quote from: HexxoDev on March 29, 2017, 03:05:18 PM

Quote from: HexxoDev on March 29, 2017, 02:39:48 PM

Quote from: HexxoDev on March 29, 2017, 12:18:36 PM

Quote from: zcoinofficial on March 29, 2017, 10:43:31 AM

Quote from: HexxoDev on March 29, 2017, 07:54:00 AM

Quote from: zcoinofficial on March 29, 2017, 05:38:15 AM

Quote from: HexxoDev on March 29, 2017, 04:25:39 AM

Dont waste your time using Getwork, it will show as it would hash but it will not ever find a block.
All shares willbe rejected.

Devs should fix the wallet.

We are mining with getwork on our testnet though? Will look into it. You fixed it on yours?

You are probably using GBT.
Getwork size is 128 if you did not change the size to lyra2z.
HexxCoin has it fixed, atlest when using cpuminer wallet needs the fix.
cpuminer-opt v3.6.0 works with fixed Zcoin wallet solo/Getwork.
Gpu miners not tested by myself because HexxCoin has none.

User felixbrucker has done more testing with the issue with cpuminer.

- for(int i = 0; i < 4; i++)
- {
- vchData.insert(vchData.begin(), 0);
- }
- if (vchData.size() != 132)
+ if (vchData.size() != 128)

I have compiled Zcoin windows 64bit wallet with the fix if you need with testing..

https://github.com/zcoinofficial/zcoin/commit/feb30a4dec722d5bce989e0840b9c50ed4affec5
Was fixed on 5 Feb I believe.

No..
That broke it!

It was working before that commit..

I developped both sgminer and ccminer on the wallet using getwork (testnet)
So I can confirm the wallet is working for both miners.

This has been tested and validated. (now in view of the size of the hashrate, it will take some time before you get a block)

Wrong!
Ask joblo for help.
Or Pm me.

Im not telling that your miner would not accept current getwork code, cpuminer will not.
Wallet source is coded wrong.
Validate drops after tesing 132 size. Gpu miner allows greater.??
Also the code above not valid for cpuminer.

Why none cant see it?

then it is the cpuminer you are using which should be fixed.
Don't reverse the problem.
Fix your miner and be done with it, don't ask everybody (else) to fix their code Angry

ps: and don't say "wrong" you weren't be there...

Are you telling me Zcoin datasize is 132?
Why fix MY miner when it is not mine?

not my part... but there is no test of the size of the header (if it is what you are talking) so it doesn't really matter.
miners (gpu) are only reading 80 like for most coins

YEP!

explain this for cpuminer

- for(int i = 0; i < 4; i++)
- {
- vchData.insert(vchData.begin(), 0);
- }

how it could validate data size?

Lets just give time to dev fix the wallet and we move on.

well if it just do that, then it should work... and that 132 shouldn't even concern you.
(validation is required for some coin (not zcoin) and takes place when the data are requested or uploaded to the server through getwork
(example FTC/neoscrypt)

HexxoDev

full member

Activity: 154

Merit: 100

Quote from: djm34 on March 29, 2017, 03:11:48 PM

Quote from: HexxoDev on March 29, 2017, 03:05:18 PM

Quote from: HexxoDev on March 29, 2017, 02:39:48 PM

Quote from: HexxoDev on March 29, 2017, 12:18:36 PM

Quote from: zcoinofficial on March 29, 2017, 10:43:31 AM

Quote from: HexxoDev on March 29, 2017, 07:54:00 AM

Quote from: zcoinofficial on March 29, 2017, 05:38:15 AM

Quote from: HexxoDev on March 29, 2017, 04:25:39 AM

Dont waste your time using Getwork, it will show as it would hash but it will not ever find a block.
All shares willbe rejected.

Devs should fix the wallet.

We are mining with getwork on our testnet though? Will look into it. You fixed it on yours?

You are probably using GBT.
Getwork size is 128 if you did not change the size to lyra2z.
HexxCoin has it fixed, atlest when using cpuminer wallet needs the fix.
cpuminer-opt v3.6.0 works with fixed Zcoin wallet solo/Getwork.
Gpu miners not tested by myself because HexxCoin has none.

User felixbrucker has done more testing with the issue with cpuminer.

- for(int i = 0; i < 4; i++)
- {
- vchData.insert(vchData.begin(), 0);
- }
- if (vchData.size() != 132)
+ if (vchData.size() != 128)

I have compiled Zcoin windows 64bit wallet with the fix if you need with testing..

https://github.com/zcoinofficial/zcoin/commit/feb30a4dec722d5bce989e0840b9c50ed4affec5
Was fixed on 5 Feb I believe.

No..
That broke it!

It was working before that commit..

I developped both sgminer and ccminer on the wallet using getwork (testnet)
So I can confirm the wallet is working for both miners.

This has been tested and validated. (now in view of the size of the hashrate, it will take some time before you get a block)

Wrong!
Ask joblo for help.
Or Pm me.

Im not telling that your miner would not accept current getwork code, cpuminer will not.
Wallet source is coded wrong.
Validate drops after tesing 132 size. Gpu miner allows greater.??
Also the code above not valid for cpuminer.

Why none cant see it?

then it is the cpuminer you are using which should be fixed.
Don't reverse the problem.
Fix your miner and be done with it, don't ask everybody (else) to fix their code Angry

ps: and don't say "wrong" you weren't be there...

Are you telling me Zcoin datasize is 132?
Why fix MY miner when it is not mine?

not my part... but there is no test of the size of the header (if it is what you are talking) so it doesn't really matter.
miners (gpu) are only reading 80 like for most coins

YEP!

explain this for cpuminer

- for(int i = 0; i < 4; i++)
- {
- vchData.insert(vchData.begin(), 0);
- }

how it could validate data size?

Lets just give time to dev fix the wallet and we move on.

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: HexxoDev on March 29, 2017, 03:05:18 PM

Quote from: HexxoDev on March 29, 2017, 02:39:48 PM

Quote from: HexxoDev on March 29, 2017, 12:18:36 PM

Quote from: zcoinofficial on March 29, 2017, 10:43:31 AM

Quote from: HexxoDev on March 29, 2017, 07:54:00 AM

Quote from: zcoinofficial on March 29, 2017, 05:38:15 AM

Quote from: HexxoDev on March 29, 2017, 04:25:39 AM

Dont waste your time using Getwork, it will show as it would hash but it will not ever find a block.
All shares willbe rejected.

Devs should fix the wallet.

We are mining with getwork on our testnet though? Will look into it. You fixed it on yours?

You are probably using GBT.
Getwork size is 128 if you did not change the size to lyra2z.
HexxCoin has it fixed, atlest when using cpuminer wallet needs the fix.
cpuminer-opt v3.6.0 works with fixed Zcoin wallet solo/Getwork.
Gpu miners not tested by myself because HexxCoin has none.

User felixbrucker has done more testing with the issue with cpuminer.

- for(int i = 0; i < 4; i++)
- {
- vchData.insert(vchData.begin(), 0);
- }
- if (vchData.size() != 132)
+ if (vchData.size() != 128)

I have compiled Zcoin windows 64bit wallet with the fix if you need with testing..

https://github.com/zcoinofficial/zcoin/commit/feb30a4dec722d5bce989e0840b9c50ed4affec5
Was fixed on 5 Feb I believe.

No..
That broke it!

It was working before that commit..

I developped both sgminer and ccminer on the wallet using getwork (testnet)
So I can confirm the wallet is working for both miners.

This has been tested and validated. (now in view of the size of the hashrate, it will take some time before you get a block)

Wrong!
Ask joblo for help.
Or Pm me.

Im not telling that your miner would not accept current getwork code, cpuminer will not.
Wallet source is coded wrong.
Validate drops after tesing 132 size. Gpu miner allows greater.??
Also the code above not valid for cpuminer.

Why none cant see it?

then it is the cpuminer you are using which should be fixed.
Don't reverse the problem.
Fix your miner and be done with it, don't ask everybody (else) to fix their code Angry

ps: and don't say "wrong" you weren't be there...

Are you telling me Zcoin datasize is 132?
Why fix MY miner when it is not mine?

not my part... but there is no test of the size of the header (if it is what you are talking) so it doesn't really matter.
miners (gpu) are only reading 80 like for most coins

HexxoDev

full member

Activity: 154

Merit: 100

Quote from: HexxoDev on March 29, 2017, 02:39:48 PM

Quote from: HexxoDev on March 29, 2017, 12:18:36 PM

Quote from: zcoinofficial on March 29, 2017, 10:43:31 AM

Quote from: HexxoDev on March 29, 2017, 07:54:00 AM

Quote from: zcoinofficial on March 29, 2017, 05:38:15 AM

Quote from: HexxoDev on March 29, 2017, 04:25:39 AM

Dont waste your time using Getwork, it will show as it would hash but it will not ever find a block.
All shares willbe rejected.

Devs should fix the wallet.

We are mining with getwork on our testnet though? Will look into it. You fixed it on yours?

You are probably using GBT.
Getwork size is 128 if you did not change the size to lyra2z.
HexxCoin has it fixed, atlest when using cpuminer wallet needs the fix.
cpuminer-opt v3.6.0 works with fixed Zcoin wallet solo/Getwork.
Gpu miners not tested by myself because HexxCoin has none.

User felixbrucker has done more testing with the issue with cpuminer.

- for(int i = 0; i < 4; i++)
- {
- vchData.insert(vchData.begin(), 0);
- }
- if (vchData.size() != 132)
+ if (vchData.size() != 128)

I have compiled Zcoin windows 64bit wallet with the fix if you need with testing..

https://github.com/zcoinofficial/zcoin/commit/feb30a4dec722d5bce989e0840b9c50ed4affec5
Was fixed on 5 Feb I believe.

No..
That broke it!

It was working before that commit..

I developped both sgminer and ccminer on the wallet using getwork (testnet)
So I can confirm the wallet is working for both miners.

This has been tested and validated. (now in view of the size of the hashrate, it will take some time before you get a block)

Wrong!
Ask joblo for help.
Or Pm me.

Im not telling that your miner would not accept current getwork code, cpuminer will not.
Wallet source is coded wrong.
Validate drops after tesing 132 size. Gpu miner allows greater.??
Also the code above not valid for cpuminer.

Why none cant see it?

then it is the cpuminer you are using which should be fixed.
Don't reverse the problem.
Fix your miner and be done with it, don't ask everybody (else) to fix their code Angry

ps: and don't say "wrong" you weren't be there...

Are you telling me Zcoin datasize is 132?
Why fix MY miner when it is not mine?

explain this for cpuminer

- for(int i = 0; i < 4; i++)
- {
- vchData.insert(vchData.begin(), 0);
- }

how it could validate data size?

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: HexxoDev on March 29, 2017, 02:39:48 PM