# Is MimbleWimble cut-through actually useful for pruning chain state?

**URL:** <https://forum.grin.mw/t/is-mimblewimble-cut-through-actually-useful-for-pruning-chain-state/10623>\
**Category:** Research\
**Created:** [July 8, 2023, 4:04am UTC](https://forum.grin.mw/t/is-mimblewimble-cut-through-actually-useful-for-pruning-chain-state/10623 "2023-07-08T04:04:05Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![tromp](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/tromp/32/22_2.png) [@tromp](https://forum.grin.mw/u/tromp)\
**Post date:** [July 8, 2023, 8:35am UTC](https://forum.grin.mw/t/is-mimblewimble-cut-through-actually-useful-for-pruning-chain-state/10623/6 "2023-07-08T08:35:54Z")

</div>

> [@Anynomous](#):
>
> if you receive a transaction, you can directly spend that transaction in the same block and there will be no trace on the blockchain.

You’d have to spend from a transaction that’s still in the mempool; while possible in theory, I don’t think any wallets currently support that.

> [@Anynomous](#):
>
> save space and transaction costs.

I don’t see how you’d save any transaction costs. You cannot fill the mempool with a chain of transactions each spending the previous one’s output unless you pay increasing transaction fees. Otherwise that would constitute some sort of DoS attack where the network has to relay arbitrarily large amounts of data for only a negligible fee.

---

_[View the full topic](https://forum.grin.mw/t/is-mimblewimble-cut-through-actually-useful-for-pruning-chain-state/10623)._