# Ecash TIDES using Cashu and Stratum v2

**URL:** <https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870>\
**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:** 13

<div class="post-metadata">

**Author:** ![calle](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/calle/32/84_2.png) [@calle](https://delvingbitcoin.org/u/calle)\
**Post date:** [May 17, 2024, 10:28am UTC](https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870/13 "2024-05-17T10:28:36Z")

</div>

> [@EthnTuttle](#):
>
> 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.

Alright, I get it now. An alternative would have been to let the mint decide the values of blind signatures after the fact (the user doesn’t have to decide on the value when sending the blind message). But I think your approach is more simple and doesn’t require the mint operator to store all outstanding blind messages and imprint them with value after doing all the accounting. It’s much better than my original idea I had discussed with you on GitHub!

---

_[View the full topic](https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870)._