During the first three stages, the user (channel owner or validator identities only) files a claim, which the zone has to respond to. The dispute process is always biased against the deployment, meaning the zone has to defend its actions before the smart contract and the user, either by countering the user's claim, or by replying with an acceptable action taken. Failing to reply results in a decision in favor of the user, one that cannot be undone. This is an important feature to ensure a dispute process can result in assets released to users even in extreme situations where Kchannels is completely down and unavailable. Also, by creating an "asymmetric" dispute process as explained above, we can put disproportional burden on the zone to reply quickly, thus resulting in a much more expedient dispute process than would normally be possible between two users. The goal is to have dispute processes end within hours at most. Also, due to the localized nature of the dispute process, multiple concurrent disputes on different channels are possible within the same smart contract.