# Management of reverted transactions in StarkNet

**URL:** <https://community.starknet.io/t/management-of-reverted-transactions-in-starknet/136>\
**Category:** Starknet Technical Development\
**Created:** [December 2, 2021, 3:53pm UTC](https://community.starknet.io/t/management-of-reverted-transactions-in-starknet/136 "2021-12-02T15:53:36Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![RoboTeddy](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/roboteddy/32/114_2.png) [@RoboTeddy](https://community.starknet.io/u/RoboTeddy)\
**Post date:** [December 9, 2021, 8:55pm UTC](https://community.starknet.io/t/management-of-reverted-transactions-in-starknet/136/15 "2021-12-09T20:55:00Z")

</div>

> While it might not matter, it seems like a waste of resources to spend such a computation power on useless computation, especially after knowing they will fail.

This is a good point. I wonder what fraction of tx on Ethereum were reverted; this could give us an estimate of the overhead.

> What I like about the PoW/VDF approach

A question about this approach:

> but in the case too many reversions, the PoW will be much larger

How will it be determined whether there was a reversion, if reversions can’t be proven?

* * *

I should note that overall I don’t have a view of which solution is best, I’m just helping discuss the pros/cons of the various approaches.

---

_[View the full topic](https://community.starknet.io/t/management-of-reverted-transactions-in-starknet/136)._