Chainlink Faces Backlash for Quietly Changing Multisig Wallet Configuration

Crypto researcher Chris Blec has raised concerns about Chainlink’s recent decision to reduce the number of signatures required on its multi-signature wallet. This controversial move has ignited a heated discussion within the crypto community, highlighting potential security risks and centralization concerns.

Explanation of Multisig Requirement

Multisignature wallets serve as a crucial security measure by requiring multiple signatures to authorize a transaction. In the case of Chainlink, the 4-of-8 multisig requirement means that four out of the eight designated parties must sign off on a transaction, ensuring higher security and reducing the risk of unauthorized access or malicious behavior.

Discovery of the Change

On September 25th, a pseudonymous user drew attention to the removal of a wallet address from Chainlink’s multisig wallet without any public announcement. This move, discovered by Chris Blec, sparked immediate concerns about transparency and the potential implications for the security of user funds.

Community Concerns

Members of the crypto community quickly voiced their concerns over Chainlink’s decision to make such a significant change without proper communication. Users argued that changes to security measures should be transparent and well-documented to maintain trust within the ecosystem.

Chainlink’s explanation

Responding to the backlash, a spokesperson for Chainlink clarified that the modification was part of a standard signer rotation process. They emphasized that this procedure aims to ensure the reliable operation of Chainlink services and is a routine measure taken to enhance security.

Signer Rotation Process

The rotation of signers, as explained by Chainlink, involves updating the multisignature Gnosis Safes without altering the regular threshold configuration. The modification is completed to ensure the continued stability of Chainlink’s service and align with industry best practices for maintaining decentralization and security.

Confirmation of Threshold Configuration

To alleviate concerns about the reduced number of required signatures, Chainlink clarified that the multisig threshold remains unchanged at 4-of-9. This means that despite the signer rotation, the same level of consensus is still necessary for transaction validation, maintaining the desired security standards.

Chris Blec’s Criticism

While the spokesperson’s clarification attempted to address the situation, Chris Blec, a vocal critic of Chainlink, expressed long-standing concerns regarding the platform’s centralization risks. Blec went as far as suggesting that if Chainlink’s signers were to “go rogue,” the entire DeFi ecosystem could be decimated. Blec’s viewpoint raises questions about the potential vulnerabilities present in widely adopted projects such as Aave and MakerDAO, which rely on Chainlink’s oracles for accurate price data.

Centralization Risks for DeFi Projects

Blec’s criticism extends beyond Chainlink to encompass other mainstay DeFi projects. A centralized oracle service like Chainlink has the power to influence numerous DeFi platforms that rely on its data feed. Should Chainlink experience any centralized failures or manipulation, it could have far-reaching consequences for the DeFi ecosystem, affecting the overall trust and reliability of decentralized finance.

Chainlink, as a decentralized oracle network, connects Ethereum-based smart contracts with external data and services beyond the confines of blockchain networks. However, recent controversy surrounding the reduction of required signatures on its multisignature wallet has highlighted concerns about transparency, security, and the overall decentralization of Chainlink and its impact on the broader DeFi ecosystem. As the crypto community continues to grapple with these issues, it is crucial for platforms like Chainlink to address these concerns and ensure communication and transparency to instill trust within the community.

Explore more

SAP Updates Cloud ERP to Advance the Autonomous Enterprise

The transition to an autonomous enterprise is an incremental achievement built upon the convergence of trusted data, specific process contexts, and established business rules. The deployment of SAP Cloud ERP Private 2025 Feature Pack Stack 02 represents a definitive pivot toward a reality where business logic and artificial intelligence operate as a unified entity. Organizations no longer view AI as

Celo Launches Marketplace for Autonomous AI Agent Commerce

By utilizing decentralized physical infrastructure networks, the platform ensures that service delivery meets the data-intensive demands of modern artificial intelligence. The digital landscape is currently witnessing a transformative shift where software is no longer just a tool but an active participant in the global economy. Celo has stepped into this breach by launching its specialized marketplace, known as “buy,” which

How Low Will Bitcoin and Ethereum Go After the Crash?

The shift in market sentiment follows a rapid descent in which Bitcoin shed fifteen hundred dollars in value within minutes of a key economic announcement. This precipitous drop has rattled the confidence of retail participants who had grown accustomed to the relatively stable upward trend characterizing the first half of the year. While the digital asset class is no stranger

Google Gemini Evolves From Chatbot to Proactive Assistant

By integrating with the broader Google software suite, Gemini can now function as a logistical coordinator that audits schedules and calculates travel times. This shift from a traditional conversational interface to an autonomous agent marks a turning point in personal computing history. No longer is the system merely waiting for a prompt; it actively monitors the digital landscape to provide

How Did a Fake Chrome App Bypass Google Play Security?

The package name com.android.chrome serves as the primary technical differentiator between the official browser and the fraudulent Hizbartech version found on the storefront. The incident involving Hizbartech has exposed a glaring vulnerability in the way mobile applications are vetted and presented to the public, especially when high-trust brands like Google Chrome are targeted. For several weeks, unsuspecting users downloaded a