# MTT-Induced Vulnerabilities in Randomized Events

**URL:** <https://vechain.discourse.group/t/mtt-induced-vulnerabilities-in-randomized-events/88>\
**Category:** VIPs\
**Created:** [December 7, 2023, 3:25pm UTC](https://vechain.discourse.group/t/mtt-induced-vulnerabilities-in-randomized-events/88 "2023-12-07T15:25:11Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![brettski](https://avatars.discourse-cdn.com/v4/letter/b/dfb087/32.png) [@brettski](https://vechain.discourse.group/u/brettski)\
**Post date:** [January 25, 2024, 12:14pm UTC](https://vechain.discourse.group/t/mtt-induced-vulnerabilities-in-randomized-events/88/5 "2024-01-25T12:14:22Z")

</div>

Is this similar to to the [VIP regarding Private State Variable Visibility Exposure](https://vechain.discourse.group/t/add-vip-private-state-variable-visibility-exposure/84/8)? The same issue but from a different perspective?

I think vechain.energy provides a useful scenario exposing this vulnerability and also a design on how to avoid being impacted by this vulnerability from a dApp developer perspective. [Multi-Task atomic Transactions – docs.vechain.energy](https://learn.vechain.energy/Vechain/Develop-with/Common-Pitfalls/Multi-Task-atomic-Transactions/#vulnerability-scenario)

---

_[View the full topic](https://vechain.discourse.group/t/mtt-induced-vulnerabilities-in-randomized-events/88)._