The main critique about Sv2 JD protocol is that, in FULL_TEMPLATE mode, the miner sends the tx_ids list to the server (this doesn't happen in COINBASE_ONLY mode).
By looking at the DATUM gateway code, I noticed it does the same, when a request for it comes from the server 👇
People who criticize this aspect of DATUM and/or JD don't have a clue what they're talking about. The main job of a pool operator is to prevent pool members from cheating each other and the operator himself. And he can't do it without asking the members to reveal their templates.
The main critique of Sv2JD is that it has (so far) two failed implementations on their track record (OCEAN and DMND Pool), while DATUM has (so far) two successful implementations on their track record (OCEAN and GridPool).
Generated by Thread Navigator
Press ⌘ + S to quick-export