Lagrange
LA7D price series. Open $0.05, close $0.0508, high $0.0566, low $0.0443, change 1.6%.
Today, Lagrange has expanded its ZK Prover Network to power proof generation for ZK rollups, adding onto Lagrange’s existing ZK Coprocessor and State Committee offerings. With this new addition, Lagrange now unlocks proofs for anything – for rollups, apps, coprocessors and interoperability – as an infinite proving layer that enables anyone to prove everything at internet scale. Previously, Lagrange launched the first production-ready ZK prover network in the industry, operated by top operators including Coinbase, Kraken, OKX and more. Now, Lagrange’s ZK Prover Network is expanding to address key challenges faced by rollups and advance ZK adoption and utility. The ZK Coprocessor can generate a proof of correct computation over arbitrary storage slots for arbitrary block ranges. For example, consider an application that wishes to compute the average on Ethereum for ETH / USDC pricing. A developer must first specify the memory slots and block range (~50,400) that they are interested in including in the data set. Next the developer writes the computations that is to be executed across the storage slots over the different blocks in parallel. Once the proof is generated, it will prove both the storage inclusion and the aggregated computation as valid with respect to a block header derived from smart contract information.
A freshness-weighted mid, and the complete venue breakdown behind it.
One normalized endpoint, 1 credit per call. The responses below are this instrument’s real data.
The normalized mark, with opt-in freshness and confidence.
curl "https://api.getliaw.com/v1/prices/latest?assets=LA"e=USD" \ -H "Authorization: Bearer $LIAW_KEY"
{ "data": [ { "asset": "LA", "quote": "USD", "price": "0.050800000000000000", "updated_at": "2026-08-09T04:54:58.574Z" } ], "meta": { "request_id": "<request id>", "served_at": "<ISO 8601 serve time>", "count": 1 } }
Live LA values, straight from the feeds on this page. request_id and served_at are per-request — the server fills those in.
