# Ecash TIDES using Cashu and Stratum v2 **URL:** \ **Category:** Implementation\ **Created:** [May 15, 2024, 4:53pm UTC](https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870 "2024-05-15T16:53:09Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![EthnTuttle](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ethntuttle/32/26_2.png) [@EthnTuttle](https://delvingbitcoin.org/u/EthnTuttle)\ **Post date:** [May 17, 2024, 2:14am UTC](https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870/11 "2024-05-17T02:14:39Z")
> Is it correct to assume that you’re measuring the value of a blind signature by the target of the submitted PoW share and get that signed by the mint? Yes. A valid target difficulty for a share to be accepted is generally a threshold below the network difficulty. With various machines of different hash rates, a pool uses a variety of target PoW difficulties to prevent DoSing itself. Giving the same target to a S9 and a S21 would either result in the S9 never finding that target in the given timeframe or the S21 inundating the pool with shares. Given the possibility of small payouts, it seemed appropriate to include hash providers with less robust machines. > Am I right to assume that when the user wants to convert the `eShares` to satoshis, the mint would look take the target values of the eShares and convert them to satoshis? Yes. I believe the TIDES documentation cover the weighting of shares as it relates to the `share_log_window` but accounting specifics would be left to the implementation. Since a blinded signature corresponds to a target difficulty, and TIDES uses the target difficulty as a weighting for valuation within a share\_log\_window, a `eShare` would not be a 1:1 for satoshis. --- _[View the full topic](https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870)._