# Mimblewimble Whitepaper V2

**URL:** <https://forum.grin.mw/t/mimblewimble-whitepaper-v2/8224>\
**Category:** Research\
**Created:** [January 13, 2021, 9:49am UTC](https://forum.grin.mw/t/mimblewimble-whitepaper-v2/8224 "2021-01-13T09:49:17Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [January 13, 2021, 6:22pm UTC](https://forum.grin.mw/t/mimblewimble-whitepaper-v2/8224/4 "2021-01-13T18:22:43Z")

</div>

> [@oryhp](#):
>
> I’d go as far as saying that the MW itself doesn’t leak unaggregated block txs

As you can see in my privacy chart at [https://forum.grin.mw/t/scalability-vs-privacy-chart](https://forum.grin.mw/t/scalability-vs-privacy-chart), I ascribe the linkability problem to Mimblewimble itself, since the only reasonably straightforward way to make transactions known to arbitrary miners for inclusion is by broadcast.

---

_[View the full topic](https://forum.grin.mw/t/mimblewimble-whitepaper-v2/8224)._