Why a duplicate find pays nothing

The network pays for the first observation of a product, not for every confirmation of it. The uniqueness rule is what makes that possible.

Phone home screen photographed at an angle on a pale surface

Every product identifier appears once in the logs. When a node reports one that already exists, the server answers with a duplicate status and a reward of zero. The balance does not move, and no new row is created.

The rule in plain terms

A find is a fact about a product. The first report establishes that fact. A second report of the same product, from any user, adds nothing the network can sell. Paying twice would turn the reward into a race for confirmations, and the data would get worse as the payments grew.

  • First report: a row is inserted, the tiered DASH reward is credited, the balance increases.
  • Later report of the same identifier: no row, no reward, status DUPLICATE.
  • The original report is never revoked because a copy arrived later.

Why there is no penalty

A duplicate is not treated as cheating. A node that sees a real price drop and reports it has done exactly what it was asked to do; it simply was not first. Rejecting the report with a clear status is the fair outcome, and it costs the user nothing beyond the missed reward.

Two nodes, one fact. The network buys the fact once.

How to be first more often

There is no trick that guarantees a first report, but the odds follow coverage. Nodes with longer uninterrupted windows read more pages, and nodes that poll consistently catch the change closer to the moment it happens. Popular categories fill up fast; quieter platforms and less-watched catalogs stay open longer.

Because the identifier is what counts, two reports of the same product with different names or prices still collide. Spelling a name differently does not create a new fact.

Where the duplicate status appears

The public channel only shows finds that were accepted, so a duplicate will not appear there. In the app, a duplicate response is a normal outcome, not an error. If your history looks quiet, the more useful question is whether your sessions are long enough, not whether the network is rejecting you.

The record also tracks whether a find reached the channel. A find can be stored and paid without a successful broadcast, and that flag is how the network notices the gap.

All field notes

Be the first report, not the second

Longer uptime means more pages read, and more chances to be the node that saw it first.