void

[ghost]

No description provided.

[tomusdrw]

@lazaridiscom Unfortunately this is not feasible to implement, and we have no plans to do so.
There are multiple assumptions in the code and multiple levels of caches that would have to be re-initialised during such reset and long term maintainance of this would be a nightmare.

As you saw we are providing a reset option, but the node has to be stopped before doing so. We were considering writing a wrapper app that intercepts the RPC call and restarts the node with DB reset, but it didn't get enough traction yet.

Closing, since as I said it's not long term feasible to support this.

[tomusdrw]

@lazaridiscom It's Parity Ethereum's issue tracker, it's meant to represent potential issues and feature requests for the client and it's owned by the team. I don't think treating it as your personal work tracker is a good idea.
Please re-open the issue if you need any more feedback on the subject, but for now I believe I've addressed all questions raised in the thread.