$1,040 Loss via Limit Order Placement on Pool 2741 (ATONE/USDC)

Proposal Discussion
1

Title: Technical Post-Mortem & UX Defect

Dear Osmosis Community, Support DAO, and Web Engineering Team,

I am writing to report a critical frontend UX safeguard issue regarding Osmosis limit orders that resulted in a ~$1,040 loss on an intended ~$1,158 trade, and to respectfully request review for potential assistance/reimbursement from the Community Support DAO or bug bounty fund.

### 1. Incident Overview

* User Address: osmo1jqvjmp8r3pv5nd2sqfdkv8fhrrxtpysm8kpyr2

* Transaction Hash: 25A07705EC0557241DB77E4E7AF944889C645FBE236EE6FC944FB8F6303480C8

* Block Height: 70818029 (2026-09-18 08:23:25 UTC)

* Target Contract: osmo19vdxnm90fc24ztnerdsy9ylxc639230lhcfc8qf0raj6j0rj4ftq8a90h9 (sumtree_orderbook / CosmWasm Pool #2741)

* Pair: ATONE / USDC

### 2. What Happened

While placing a Limit Buy order for ATONE (which was trading on-chain at approximately $0.10), a typographical mistake occurred and the limit price was set to $1.00 instead of $0.10.

A deposit of 1,158.38 USDC was committed.

In standard financial markets, CeFi, and leading DEX implementations (dYdX, CowSwap, Uniswap), a buy limit order above market price acts as an immediate marketable order that fills against the best available asks (at $0.10), giving the user price improvement.

Instead, the Osmosis frontend directly broadcast a place_limit CosmWasm message placing a resting maker bid at tick_id: -20000 ($1.00 / ATONE):

```json

{

“place_limit”: {

"tick_id": -20000,

"order_direction": "bid",

"quantity": "1158380000",

"claim_bounty": "0.0001"

}

}

2

Sorry this happened. Regardless of how the limit order is designed, a strong warning when the entered price is far from the current market price—and a final estimate of what the user will receive—could help catch mistakes like this before signing. I hope the team can review the transaction and improve the confirmation screen.