# Will Ledger publicly confirm tampered devices from a reseller or sales channel other than CryptoBilis by Nov 30, 2026?

- Space: [Trueo](https://snapshot.box/s:truemarkets.eth.md)
- Author: 0x3b43172F7018366E0259759bf947Af0131b36D82
- State: Active
- Voting type: Single choice
- Start: 2026-11-21 17:47 UTC
- End: 2026-11-24 17:47 UTC
- Votes: 12
- Open in Snapshot: https://snapshot.box/#/s:truemarkets.eth/proposal/0x2af5414cc50196fb2531dcce4fbc7a0abf3e1ca5b08cb8a0f234b81dfcf84deb

## Results

- \#1: [8]: 770,815.21 voting power, 23.7%
- \#2: [16]: 0 voting power, 0.0%
- \#3: [24]: 0 voting power, 0.0%
- \#4: [32]: 2,484,659.13 voting power, 76.3%

## Proposal

### **Voting Title**

Will Ledger publicly confirm tampered devices from a reseller or sales channel other than CryptoBilis by Nov 30, 2026?

---

### **Market Description**

This market will resolve to “Yes” if Ledger publicly confirms that devices sold by a reseller or sales channel distinct from CryptoBilis were tampered with at any time after the creation of this market and before November 30, 2026 - 00:00 PST.

Otherwise this market will resolve to “No.”

For the purposes of this market, “publicly confirms” means an explicit statement issued by Ledger through one or more official Ledger channels (e.g., Ledger’s official website or blog, Ledger security advisory pages, official press releases, or Ledger’s verified social media accounts). Private or customer-support-only messages do not qualify.

For the purposes of this market, “tampered” means Ledger explicitly states devices were physically modified, compromised, altered from factory specifications, or otherwise subject to a supply-chain or device compromise.

For the purposes of this market, a “second reseller or sales channel” means any named reseller, distributor, marketplace, or sales channel that is not CryptoBilis. Ledger must identify or provide sufficient identifying details about the reseller/sales channel in its public statement for the confirmation to qualify.

Only confirmations issued after the creation of this market are eligible for resolution.

View on Trueo: https://trueo.com/market/0xf0893e2cb55b308b72cb5bcd3dd434e0a129ff39

---

### **Voting Description**

This vote addresses a dispute regarding the "Will Ledger publicly confirm tampered devices from a reseller or sales channel other than CryptoBilis by Nov 30, 2026?" on Trueo. Initially, the Resolver proposed the outcome as "Yes". The Disputer challenged this outcome, but the Oracle Council refused the dispute, maintaining the outcome as "Yes". Subsequently, the Escalated Disputer contested the Oracle Council's decision, requesting a re-vote by $TRUE Holders.

---

### **Reasons For Dispute**

Proposition: This market should not resolve Yes and should be returned to Open to Proposals

I believe this market should not be resolved "Yes" based on Ledger's official statement, and should instead be returned to Open to Proposals.

Ledger has publicly confirmed that tampered devices were found in Berlin and the UAE. However, it has not identified which reseller or sales channel those devices came from.

This distinction matters because the market explicitly states:

> A “second reseller or sales channel” means any named reseller, distributor, marketplace, or sales channel that is not CryptoBilis. Ledger must identify or provide sufficient identifying details about the reseller/sales channel in its public statement for the confirmation to qualify.

There were no **named** resellers or sales channels in the official statement at the time of resolution. There are 9 authorized resellers in Germany and 7 in the UAE (https://shop.ledger.com/pages/resellers). The available information does not provide "sufficient identifying details about the reseller/sales channel" to establish which one was responsible.

I disagree with the argument that, since CryptoBilis has no operations in Berlin, Ledger's confirmation of tampered devices there is sufficient for the market to resolve "Yes." If confirmation of tampered devices in any location outside CryptoBilis' operations were sufficient on its own, there would be little reason for the rules to separately require the reseller or sales channel to be identified or sufficiently identifiable. That requirement should have independent meaning and should not be effectively bypassed simply because the incident occurred in a different city or country. 

Given this ambiguity, I believe the fairest course of action is to return the market to Open to Proposals, allowing the resolution criteria to be clarified before a definitive outcome is determined, rather than resolving "Yes" under an interpretation that effectively removes the reseller-identification requirement.

---

**Dispute Background**:

- **Initial Resolution**: Resolver proposed the outcome as "Yes".
- **Dispute and Arbitration**: Disputer challenged the outcome, but the Oracle Council refused the dispute, maintaining the outcome as "Yes".
- **Escalated Dispute**: Escalated Disputer contested the new outcome, requesting a re-vote.

---

### **Voting Items Description**

$TRUE Holders are now required to vote on the following items:

- **#1** - Keep the outcome as **Yes**, and Don't Slash. [8]
- **#2** - Set the outcome to **No**, and Don't Slash. [16]
- **#3** - Set the outcome to **CANCELED**, and Don't Slash. [24]
- **#4** - Set the outcome to **RESET**, and Don't Slash. [32]

---

### **Additional Info**

- **Market**: 0xf0893e2cb55b308b72cb5bcd3dd434e0a129ff39
- **Resolver**: 0x9e6DbFEc934b50249a43FB991348Ca1747f3c2CB
- **Disputer**: 0x4524EF81e5e2F3CE5d95e4C39ea86596d1c69Ef4
- **Escalated Disputer**: 0x4524EF81e5e2F3CE5d95e4C39ea86596d1c69Ef4

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

