This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Stratum: submit share #6258
Comments
Which version of Parity is that? |
@5chdn I've updated issue. |
I think the problem cause is here (no error handling): https://github.com/paritytech/parity/blob/master/ethcore/src/miner/stratum.rs#L147 Unfortunately, I'm not familiar with Rust. |
debris
added a commit
that referenced
this issue
Aug 8, 2017
debris
added a commit
that referenced
this issue
Aug 8, 2017
thanks for tips @Kondratovich . #6260 should fix the issue |
arkpar
pushed a commit
that referenced
this issue
Aug 9, 2017
arkpar
pushed a commit
that referenced
this issue
Aug 18, 2017
arkpar
added a commit
that referenced
this issue
Aug 19, 2017
* overflow check in addition * add test * Unexpose methods on UI RPC. (#6295) * Add more descriptive error when signing/decrypting using hw wallet. * format instant change proofs correctly * propagate stratum submit share error upstream, fixes #6258 (#6260) * updated jsonrpc (#6264) * Using multiple NTP servers (#6173) * Small improvements to time estimation. * Allow multiple NTP servers to be used. * Removing boxing. * Be nice. * Be nicer. * Update list of servers and add reference. * Fix dapps CSP when UI is exposed externally (#6178) * Allow embeding on any page when ui-hosts=all and fix dev_ui * Fix tests. * Fix cache path when using --base-path (#6212) * Time should not contribue to overall status. (#6276) * v1.7.1
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello, I'm using stratum protocol in Parity.
When I submit invalid work package, Parity returns me okay response, but should return failure.
In parity console I can read error message.
I'm using Olympic chain. Main chain has the same behaviour.
I think the problem cause is here (no error handling): https://github.com/paritytech/parity/blob/master/ethcore/src/miner/stratum.rs#L147
Unfortunately, I'm not familiar with Rust.
The text was updated successfully, but these errors were encountered: