---
# System prepended metadata

title: Make Burning Configurable

---

# Make Burning Configurable

This approach talks about making the burning configurable in the scenario where the node doesn't submit fulfilment on time but has a correct result.


### Current Approach:
Currently, we have three burning cases:
1. Node submits a different result at the time of reveal.
2. Node didn't submit the fulfilment(reveal result).
3. Node submits incorrect result.

Out of these three, we need to make the second case configurable in the proposed approach.

The second case contains two more scenarios where we don't get fulfilment from the node.

1. Node doesn't  want to submit the fulfilment.
2. Node wasn't able to submit the fulfilment at the time of reveal window.

More specifically, we'll make the burning configurable for the case where node wasn't able to submit the fulfilment on time.

### Proposed Sequence Diagram:
![](https://i.imgur.com/T6s8QkC.png)


In the above diagram, the dotted lines specify the case for which we need to make burning configurable.

### Proposed Technical Flow Diagram:
![](https://i.imgur.com/PqRqTJU.png)




#### Proposed Solution: 

Have an additional key(within_reveal_window) in the Commits storage for tracking submissions (whether received in the reveal period or not).




