Ergo Job Broadcasting only once?

[belmix]

Bitcoin family

Ergo coin
why is it not by analogy with bitcoin family? this is normal?

[oliverw]

For Bitcoin and family jobs get refreshed periodically to include the latest transaction hashes in the Merkle Tree.

[belmix]

Ok thanks, what is MaxActiveJob? How does MaxActiveJob affect hardware? did not notice the difference MaxActiveJob = 20 and MaxActiveJob = 100

[oliverw]

It's the maximum number of active generations of a block - only differing in parameters such as Merkle Tree etc. - this pool will maintain and accept shares for. Get's reset with every new block.

[belmix]

nicehash is also not supported

	"nicehash": 
	{
	"enableAutoDiff": true
	},

Set diff = 1

[oliverw]

I'm confused by this comment.

[belmix]

[belmix]

maybe the reason is this?

[oliverw]

No.

[belmix]

[0HMDDL26LAU1M] Accepting connection from ::ffff:35.233.71.192:45830 ... 
[0HMDDL26LAU1M] Connection from ::ffff:35.233.71.192:45830 accepted on port 3037 
[0HMDDL26LAU1M] [NET] Waiting for data ... 
[0HMDDL26LAU1M] [NET] Received data: {"id": 1, "method": "mining.subscribe", "params": ["NiceHash/1.0.0"]}
{"id": 2, "method": "mining.authorize", "params": ["88dhgzEuTXaRRBrBZZ9tREuKM1gX6A7XSxEr1FunHswveamYxWvfX4KwM1XHrEgYTk6zsxpT1ACRuiu1", "d=4000000000"]}
[0HMDDL26LAU1M] [NET] Waiting for data ... 
[0HMDDL26LAU1M] [PIPE] Waiting for data ... 
[0HMDDL26LAU1M] [PIPE] Received data: {"id": 1, "method": "mining.subscribe", "params": ["NiceHash/1.0.0"]}
{"id": 2, "method": "mining.authorize", "params": ["88dhgzEuTXaRRBrBZZ9tREuKM1gX6A7XSxEr1FunHswveamYxWvfX4KwM1XHrEgYTk6zsxpT1ACRuiu1", "d=4000000000"]}
[0HMDDL26LAU1M] Dispatching request 'mining.subscribe' [1] 
[0HMDDL26LAU1M] Dispatching request 'mining.authorize' [2] 
[0HMDDL26LAU1M] Authorized worker 88dhgzEuTXaRRBrBZZ9tREuKM1gX6A7XSxEr1FunHswveamYxWvfX4KwM1XHrEgYTk6zsxpT1ACRuiu1 
[0HMDDL26LAU1M] Sending: {"result":[[["mining.set_difficulty","0HMDDL26LAU1M"],["mining.notify","0HMDDL26LAU1M"]],"1001",6],"error":null,"id":1} 
[0HMDDL26LAU1M] Sending: {"result":true,"error":null,"id":2} 
[0HMDDL26LAU1M] Nicehash detected. Using miner supplied difficulty of 4000000000 
[0HMDDL26LAU1M] Setting static difficulty of 4000000000 
[0HMDDL26LAU1M] [PIPE] Waiting for data ... 
[0HMDDL26LAU1M] Sending: {"jsonrpc":"2.0","method":"mining.set_difficulty","params":[1],"id":null} 
[0HMDDL26LAU1M] Sending: {"jsonrpc":"2.0","method":"mining.notify","params":["00000001",625418,"3c317470e59342fe744c855b3d7c99fd9c16e2dc763d2e52e7ff0ab4f20e3684","","",2,"0","",true],"id":null} 
[0HMDDL26LAU1M] [PIPE] Received data:  
[0HMDDL26LAU1M] Received EOF 
[0HMDDL26LAU1M] Connection closed 

Hmm.. "method":"mining.set_difficulty","params":[1] - 1?

[oliverw]

The actual difficulty is pre-multiplied into the target sent to the miner.

[belmix]

Diff parameter not passed in current version
GPU vardiff work breaks down if 40000000

[Konstantin35]

You can do this
await connection.NotifyAsync(BitcoinStratumMethods.SetDifficulty, new object[] { context.Difficulty * BitcoinConstants.Pow2x32 });

[belmix]

The actual difficulty is pre-multiplied into the target sent to the miner.

yes but in this case it is not compatible with nicehash

[belmix]

#1000
Close