Lagrange

• Lagrange provides zero-knowledge proving infrastructure through a prover network and a ZK coprocessor.

• Its coprocessor lets contracts run queries over historical blockchain data with proofs of correctness.

• LA is used for proof fees, staking and governance.

• Supply allocated across community, ecosystem and investors.

• Provers stake LA and earn fees for generating proofs.

• Security is derived partly through EigenLayer restaking.

Pros:

• Two distinct products, proving and data queries, rather than a single offering.

• Restaked security avoids bootstrapping an independent validator set.

• Targets AI verification alongside conventional rollup proving.

Cons:

• Dependency on EigenLayer means inherited risk from that protocol.

• Crowded proving market with several well-funded competitors.

• AI verification demand is speculative rather than established.

• Exposure to proving infrastructure with a second product line in data queries.

• Restaked security is a credible design choice.

• Weigh the competitive density in proving.

• A coprocessor that answers historical data queries with proofs, so contracts can compute over chain history they cannot otherwise read.

• Smart contracts can only see recent state, so anything requiring history must be reported by a trusted oracle.

• Proving the query result removes the need to trust the reporter.

• Founded by Ismael Hishon-Rezaizadeh.

• Backed by Founders Fund, Archetype and 1kx.

• No public ICO. Distributed via Binance ecosystem programmes and airdrop in 2025.

• EigenLayer dependency introduces inherited slashing and protocol risk.

• Crowded proving market.

• AI verification demand is unproven.

• Proving cost limits economic use cases.