LavenderFive leads on 2 of 11 shared benchmarks, Polkachu on 9. LavenderFive wins on Fastest free Stride RPC, live no-key endpoint latency (192 ms vs 192 ms), Fastest free Terra RPC, live no-key endpoint latency (176 ms vs 192 ms). Polkachu wins on Fastest free Osmosis RPC, live no-key endpoint latency (189 ms vs 191 ms), Fastest free Cosmos Hub RPC, live no-key Cosmos SDK endpoint latency (190 ms vs 191 ms), Fastest free Injective RPC, live no-key Cosmos SDK endpoint latency (189 ms vs 194 ms), Fastest free Neutron RPC, live no-key Cosmos SDK endpoint latency (190 ms vs 191 ms).
Cosmos validator running multi-chain no-key RPC endpoints under rpc.lavenderfive.com/<chain> and lcd.lavenderfive.com/<chain>. Covers Osmosis, Cosmos Hub, Neutron, Injective and 20+ other Cosmos SDK chains.
Community-run Cosmos validator and public RPC network. Operates no-key Tendermint RPC endpoints across 40+ Cosmos SDK chains (osmosis-rpc.polkachu.com, cosmos-rpc.polkachu.com, etc.) with archive support on a paid tier.
LavenderFive
Trails191 ms
Polkachu
Leads189 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 192 ms | 188 ms |
| EU-West | 191 ms | 189 ms |
| Singapore | 191 ms | 189 ms |
LavenderFive
Trails191 ms
Polkachu
Leads190 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 192 ms | 189 ms |
| EU-West | 191 ms | 190 ms |
| Singapore | 191 ms | 191 ms |
LavenderFive
Trails194 ms
Polkachu
Leads189 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 194 ms | 188 ms |
| EU-West | 194 ms | 189 ms |
| Singapore | 193 ms | 190 ms |
LavenderFive
Trails191 ms
Polkachu
Leads190 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 191 ms | 190 ms |
| EU-West | 191 ms | 191 ms |
| Singapore | 190 ms | 190 ms |
LavenderFive
Trails192 ms
Polkachu
Leads178 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 192 ms | 178 ms |
| EU-West | 192 ms | 178 ms |
| Singapore | 191 ms | 177 ms |
LavenderFive
Trails192 ms
Polkachu
Leads190 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 192 ms | 190 ms |
| EU-West | 191 ms | 189 ms |
| Singapore | 192 ms | 190 ms |
LavenderFive
Leads192 ms
Polkachu
Trails192 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 192 ms | 191 ms |
| EU-West | 192 ms | 191 ms |
| Singapore | 191 ms | 195 ms |
LavenderFive
No data in window
Polkachu
Trails189 ms
LavenderFive
Trails191 ms
Polkachu
Leads189 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 192 ms | 189 ms |
| EU-West | 191 ms | 190 ms |
| Singapore | 191 ms | 189 ms |
LavenderFive
Trails191 ms
Polkachu
Leads190 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 191 ms | 189 ms |
| EU-West | 190 ms | 194 ms |
| Singapore | 191 ms | 188 ms |
LavenderFive
Trails191 ms
Polkachu
Leads191 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 192 ms | 191 ms |
| EU-West | 191 ms | 194 ms |
| Singapore | 191 ms | 189 ms |
LavenderFive
Leads176 ms
Polkachu
Trails192 ms
Per region
| Region | LavenderFive | Polkachu |
|---|---|---|
| US-East | 176 ms | 192 ms |
| EU-West | 176 ms | 194 ms |
| Singapore | 176 ms | 189 ms |
LavenderFive and Polkachu are compared on 12 shared OpenChainBench benchmarks. LavenderFive leads on Fastest free Stride RPC, live no-key endpoint latency. Polkachu leads on Fastest free Osmosis RPC, live no-key endpoint latency. See the live table on this page for every metric.
On the Fastest free Stride RPC, live no-key endpoint latency benchmark, LavenderFive leads at 192 ms versus Polkachu at 192 ms. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest free Osmosis RPC, live no-key endpoint latency benchmark, Polkachu leads at 189 ms versus LavenderFive at 191 ms. Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.