# 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:** 8

<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 16, 2024, 10:18am UTC](https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870/8 "2024-05-16T10:18:22Z")

</div>

Thank you, interesting post and very thoughtful use of blind signatures. I have a question on the value field for keysets that correspond to difficulty targets. These normally represent a satoshi amount in Cashu, but it’s totally fine to replace them with anything else. 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?

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? I understand that the accounting of which target gets what amount is not part of the protocol here but I’m trying to understand why the values aren’t just directly Satoshis. I’m sure there is a good reason for that.

Thanks!

---

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