The ethereum community has broken its silence over a move to better facilitate the return of funds lost on the platform.

In wake of the departure of ethereum developer Yoichi Hirai, who resigned from his role supervising the software’s changes Thursday, community members have stormed Github in resounding rejection of the controversial proposal over which he left his post.

In the last 24 hours, over 80 comments have been posted to the blockchain network’s official GitHub, with most stating they “do not support” or are “strongly opposed” to ethereum improvement proposal (EIP) 867, which details a method to standardize the use of system-wide software upgrades to return funds lost on the platform.

Often occurring as a result of faulty code, fund recovery is a sensitive topic for the platform, having previously led to the development of a rival cryptocurrency named ethereum classic.

The heated response, in which many are coming forward to express support for the developer, marks a sharp contrast to the silence earlier in the week, with some even writing that the proposal is a “complete disgrace to the ethereum community.”

Speaking on the thread, developer William Entriken warned about the potential consequences of normalizing lost fund recovery in comments that showcased the emerging sentiment.

“Here’s the unintended consequence of having a readily available, well documented, and standardized tool like this available,” he wrote.

Others dismissed the proposal as “very damaging” as well as “scary, and an absolute joke,” while another wrote that it “goes against everything I thought this movement was for.”

The outrage also mirrors reaction observed in a core developer meeting last week, where ethereum developer Vlad Zamfir spoke of the necessity for community feedback on the matter, stating that EIP 867 was perhaps too important to undergo the usual EIP process.

Adding to the issue is that confusion has emerged over the status of the proposal, which was formally entered into GitHub, first as an “issue” (or an early-stage sketch), and later as a “pull request,” a formal software outline that code become merged with the platform’s live code.

James Levy from Tap Trust, one of the three developers leading the proposal, closed the Github issue in the midst of the activity last night, sparking confusion that EIP 867 is no longer active.

However, to date, the corresponding pull request remains open, and at press time, continues to generate feedback.

Smashed keyboard via Shutterstock