Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-11-16 · today

blockrun.ai/api/v1/defillama/protocol/aerodrome

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://blockrun.ai/api/v1/defillama/protocol/aerodrome
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0xe9030014f5dae217d0a152f02a043567b16c1abf
Declared price (base units)6000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-11-16 16:06 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-09-222026-11-16
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-16 16:40 UTCGETpass402307 ms—
2026-11-13 04:40 UTCGETpass402596 ms—
2026-11-11 04:40 UTCGETpass402501 ms—
2026-11-08 22:40 UTCGETpass402108 ms—
2026-11-06 16:40 UTCGETpass402171 ms—
2026-11-04 13:40 UTCGETpass4022093 ms—
2026-11-01 13:40 UTCGETpass402186 ms—
2026-10-30 13:40 UTCGETpass402464 ms—
2026-10-28 13:40 UTCGETpass40288 ms—
2026-10-26 18:40 UTCGETpass402117 ms—
2026-10-25 00:40 UTCGETpass402157 ms—
2026-10-23 04:40 UTCGETpass402157 ms—
2026-10-04 22:40 UTCGETpass402101 ms—
2026-10-04 04:40 UTCGETpass402143 ms—
2026-10-03 13:40 UTCGETpass40262 ms—
2026-10-02 13:40 UTCGETpass40294 ms—
2026-10-01 16:40 UTCGETpass402313 ms—
2026-09-30 22:40 UTCGETpass4021136 ms—
2026-09-30 04:40 UTCGETpass402838 ms—
2026-09-29 13:40 UTCGETpass402236 ms—
2026-09-28 16:40 UTCGETpass4022202 ms—
2026-09-27 22:40 UTCGETpass402479 ms—
2026-09-27 04:40 UTCGETpass402363 ms—
2026-09-26 13:40 UTCGETpass402323 ms—
2026-09-25 16:40 UTCGETpass402159 ms—
2026-09-24 22:40 UTCGETpass402108 ms—
2026-09-24 04:40 UTCGETpass402123 ms—
2026-09-23 13:40 UTCGETpass402270 ms—
2026-09-22 16:40 UTCGETpass402109 ms—
2026-09-22 04:40 UTCGETpass402355 ms—

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 1 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.

Terms in this table

settled (nonce-bound)
vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 not_checked
not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Stage delivered
vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side
the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txPayment chainLatency
09-05 12:09settled (nonce-bound)2000x93aac1c3…6cfaBase3249 ms
6000 units (≈ $0.006 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered)Stage: delivered

Add this badge to your docs

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a deliverable HTTP 2xx response. settled is the confirmed transfer; delivered is a 2xx other than 202 with a non-empty body. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (blockrun.ai · measured 2026-09-05)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/30f45387-5290-4e5f-9e85-30ba2b862c16.svg)](https://vet402.com/observatory/e/30f45387-5290-4e5f-9e85-30ba2b862c16)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

No listing changes observed.

unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.

5.Dispute this record

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight. If it was right, it stands. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far