Home / Knowledge Vault / Platform & Product

Server-Authoritative Bidding: Why Fair Auctions Cannot Trust the Browser

In a real auction, the screen displays the result. It never decides it.

By AA Exchange Desk, Platform & Market Operations — AA Enterprises (Est. 1974) · Published · Updated · 6 min read

Key takeaways

  • Time on the exchange is server time only. A bidder’s device clock is irrelevant.
  • Every bid is checked for eligibility, status, timing, amount and increment before it is accepted.
  • Accepted and rejected bids are both recorded, with the reason for any rejection.
  • Because the record is authoritative, results can be explained and disputes resolved from facts.

1. The risk with client-side logic

If the part of an application that runs in the browser decides whether a bid is valid, anyone who can modify the browser can modify the outcome. A changed clock, a replayed request or a doctored amount can all slip through.

A fair auction needs a single authority that nobody on the bidding side controls. On AA Exchange that authority is the server.

2. What the server checks on every bid

For each bid the server verifies, in order, that the user is authenticated, that the enterprise is approved, that it is eligible for this event, that the event is open, that the bid arrived inside the time window by server time, that the amount respects the starting price, the direction of the auction and the minimum step, and that the quantity makes sense for the lot.

Only after those checks does the bid become part of the auction. If a bid fails, the bidder sees the specific rule that rejected it rather than a generic error.

3. The record that backs every result

Each accepted and rejected bid is stored with a server timestamp. The live ranking is computed from that record, not from what any screen happens to show. At the end of the event the same record supports evaluation and award.

That record is why outcomes can be explained. If someone asks why a bid did not count, or why one offer ranked above another, the answer is on file.

4. Why this matters to bidders

Honest bidders benefit most. They know the rules are applied the same way to everyone, that nobody can gain from a faster machine or a manipulated clock, and that the operator can reconstruct what happened if there is a disagreement.

For buyers and sellers, it means the prices discovered in an event are prices they can stand behind. Explore the bidding tools on the trading cockpit.

Frequently asked questions

What happens if my connection drops during an auction?

The cockpit reconnects automatically and resyncs to the current server state, so you see the live price, ranking and remaining time rather than a stale screen.

Can a bidder bid after the end time?

No. The server decides whether a bid arrived inside the window, using its own clock, including any soft-close extensions.

Why does the platform record rejected bids?

A complete record makes the result explainable. If a bid was rejected, the reason is on file, which helps settle questions quickly.

Related guides

Textile glossary · How AA Exchange works