John Tromp

It would be helpful to look into your grin-miner.log for when these faulty shares are found and submitted to server and post that section of a few dozen lines here.

Could you please cut and paste text instead of posting pictures of them?

> our pool (2Miners.com) is fully anonymous not having any sort of a client area or secure page where the miner could potentially grab these Slatepack Messages for a direct...

Latest master build errors on this older config file: $ ./target/debug/grin-wallet thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', config/src/comments.rs:393:44 note: run with `RUST_BACKTRACE=1` environment variable to display...

>for each output, sign a message with those r this can be done more efficiently by summing the commitments first. For a set S of outputs, whose commitments sum to...

> Prove outgoing transactions (sends) Such proofs may not be convincing, since once an output is spent, its owner could leak or reveal its blinding factor, allowing others to "prove"...

Yes, proofs of past ownership are not convincing, so proofs of ownership should apply to unspent outputs.

> Digishield and Grin are an SMA inside a wtema: > next_target = avg_17_targets* (1 + avg_17_st/T/N - 1/N) > N = 4 Digi, N=2 Grin. Grin uses a DIFFICULTY_ADJUST_WINDOW...

Are you saying N corresponds more to a dampening factor than to a block window?

In wtema, you don't compute any average target or difficulty; you just multiply the previous one by some factor depending on last solvetime to get the next. Multiplying the target...