Copper Delegation Incident : A Call for Stronger UI Controls in Delegation Flows

Hello everyone,

I would like to bring attention to the recent Copper delegation issue and frame it as a clear, non‑arguable point: delegation interfaces must guarantee full visibility and control at every step.

Case Scenario

  1. A user interacting with Copper’s interface left the DRep field blank, intending to abstain from delegation.
  2. However, due to a default setting, the system automatically delegated their ADA to DRep “Yuta,” without this being visible or confirmed by the user.
  3. Upon discovering the issue, Copper corrected the behavior by defaulting blank selections to “Abstain.” The affected DRep also communicated with Copper to resolve the situation.

Core Principle

Delegation tools must never assume user intent. If a user does not actively select a DRep, the platform should clearly interpret this as an “abstain” action, not automatically assign a delegate.

Delegators deserve clarity on who is representing their stake. A default assignment violates that trust.

Even small, unintended delegations could influence signalling or cause confusion in close votes.

Should wallets and tools like Yoroi, Daedalus, GovTool, and others be audited to ensure no similar blind‑spot bugs exist?

As Cardano’s on‑chain governance continues to scale, ensuring correctness in even small delegation steps will be essential for user trust and system integrity. I look forward to hearing perspectives from DReps, developers, and everyday delegators alike.

Professional regards,
Abdul Aziz

3 Likes