# Important Announcement: Bug Fix - Double Jailing Issue Resolution

**URL:** <https://forum.fuse.io/t/important-announcement-bug-fix-double-jailing-issue-resolution/690>\
**Category:** Fuse Network\
**Created:** [February 22, 2024, 8:19am UTC](https://forum.fuse.io/t/important-announcement-bug-fix-double-jailing-issue-resolution/690 "2024-02-22T08:19:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![emmanuel](https://avatars.discourse-cdn.com/v4/letter/e/3e96dc/32.png) [@emmanuel](https://forum.fuse.io/u/emmanuel)\
**Post date:** [February 22, 2024, 8:19am UTC](https://forum.fuse.io/t/important-announcement-bug-fix-double-jailing-issue-resolution/690/1 "2024-02-22T08:19:06Z")

</div>

Dear Fuse Community,

We hope this message finds you well. Our development team has been actively working on addressing a critical issue related to the Consensus contract on the Fuse chain. **We have identified a bug that poses the risk of validators encountering a double jailing scenario, preventing them from leaving the jail.**

## Problem Overview:

The issue arises from an edge case where a validator may be jailed twice, specifically after submitting a maintenance request and remaining inactive in the subsequent cycle.

## Affected Component:

Consensus Contract.

## Resolution:

To rectify this problem, we are implementing a comprehensive fix to address the identified edge case. Our goal is to ensure the seamless operation of the consensus mechanism and prevent validators from facing unnecessary “double jailing” scenarios.

## Release Date:

The fix is scheduled to be released in the first quarter of 2024. We are committed to delivering a robust solution and appreciate your patience as we work towards the resolution.

## Voting Process:

To implement this fix, we are introducing a voting process within the Fuse chain. Validators are kindly requested to participate in this crucial decision-making phase. The vote will determine the adoption of the double jailing resolution.

In line with our commitment to community governance, we are initiating a voting process to decide on the adoption of the proposed double jailing resolution. We invite all validators to actively participate in this decision-making process.

## How to Vote:

### Ballot Information:

ID: 27

### Beginning

**Block: 28208871** (With blocks occurring every 5 seconds, voting opens approximately 23:00 UTC on February 26th, 2024)

### Closing:

**Block: 28312551**

To cast your vote for or against the proposed update, send a transaction to the voting contract. When doing so, use the vote function, entering the ballot ID and your decision (choose 1 for acceptance, 2 for rejection) as the parameters.

## Validator Tasks:

- Vote on the Proposed Update.
- The voting process will be conducted through an on-chain vote on the Fuse chain.
- Validators are encouraged to participate in decision-making by voting on the proposed update.
- Share your insights and opinions on the proposal in the community forum to foster informed decision-making.

Detailed information on the voting process can be found in the Docs [https://docs.fuse.io/docs/validators/participating-in-network-consensus/vote](https://docs.fuse.io/docs/validators/participating-in-network-consensus/vote)

## Details on the new consensus contract:

> **[Fuse address details for 0x4374db7eF1A32Cef53AB81CB31eAC65f89B5F2e1 | Blockscout](https://explorer.fuse.io/address/0x4374db7eF1A32Cef53AB81CB31eAC65f89B5F2e1?tab=contract)**
>
> View the account balance, transactions, and other data for 0x4374db7eF1A32Cef53AB81CB31eAC65f89B5F2e1 on the Fuse Explorer

We appreciate your cooperation and involvement in ensuring the stability and reliability of the Fuse network. Your active participation in the voting process is crucial for successfully implementing this bug fix.