Lelang

Subscribe to the audit trail

Public bodies, watchdogs and journalists can follow every Lelang tender as it happens: when a tender opens, who wins, which bid was slashed and on what evidence, how appeals ended, and whether the goods arrived. It is free and needs no account, no key and no sign-up. Every item links to the transaction on Kitescan, so you can check it without trusting us.

Three ways to subscribe

In a feed reader (people). Paste https://lelang-ten.vercel.app/feed.xml into any reader that takes Atom or RSS: Feedly, Inoreader, NetNewsWire, Thunderbird, or a Slack or Teams RSS app. You get one item per event.

As open contracting data (analysts and data tools). https://lelang-ten.vercel.app/ocds-feed.json is a single OCDS 1.1.5 record package with every tender, using the official Bids extension. It validates against the official schema and loads into any OCDS tool, such as the OCDS Data Review Tool, Kingfisher or Flatten Tool for spreadsheets. Each tender also has its own release under tenders/<id>.ocds.json.

From the live API (agents). https://lelang-6k05.onrender.com/api/rfqs returns the tenders running right now, and /api/rfqs/<id>/ocds returns one as OCDS. It is a free instance that sleeps when idle, so the first call can take a while. Poll it, or poll the feed.

What each event means

EventWhat happenedWhat you can check
Tender openedA buyer published a tender: what it wants, the budget cap, minimum specs and the scoring weights, all fixed before any bid arrives.The tender transaction on the escrow.
Award decisionThe decision node picked a winner and said whether that matches the published formula. If the two disagree, or a bid is under review, the award goes to a human.Formula scores and the full tender record.
Human approver signedA named approver signed off on a held award. Their address is in the entry.The signed message in the tender record.
SettlementThe escrow paid out: bonds refunded, the winner paid, the fee taken, or a balance held until delivery. A settlement can also be held for human review.The settle transaction on Kitescan.
SlashA bidder lost its bond, usually for hiding instructions to the AI evaluator in its bid. The entry includes the evidence hash, which is the keccak256 of the quoted evidence and is recorded on-chain.The proof page recomputes the hash in your browser and compares it with the chain.
AppealA slashed bidder appealed with a signed statement. An independent panel re-checked the evidence and the slash was upheld, or it was overturned by a named approver and the bond refunded.The panel verdict, the signatures and the refund transaction.
Delivery confirmedThe buyer confirmed delivery and the escrow released the held balance to the winner.The release transaction.
Delivery disputedThe buyer reported that the delivery did not meet the offer. Two independent models read the inspection report, and approvers decide what happens to the held balance.The hash of the inspection evidence, anchored on Kite.

What it is built from

The feed lists only what is in the published tender records: the tender logs and the escrow events on Kite testnet. Nothing is summarised or edited by hand. Timestamps come from those records, so an item never changes once published. The feed is rebuilt each time the tenders are published.