# Examples

> Source: https://docs.erpc.cloud/presets
> Drop-in eRPC config presets for specific scenarios (DVN, indexer, frontend, etc.).
> Format: machine-readable markdown export of the docs page above.
> All collapsible AI sections are inlined and fully expanded.

# Examples

Drop-in eRPC config examples for specific scenarios. Each example is a minimal, self-hosted starting point you can adapt to your chains and providers.

- [DVN (LayerZero)](/presets/dvn-ready.llms.txt) — multi-provider consensus profile for DVN operators and any verifier service that can't trust a single RPC stack.

## Agent reference

**Prompt Example #1: start from a preset and adapt it to my stack**

```text
I want to start my eRPC setup from one of the official presets and adapt it to my
chains and providers. List the available presets, pick the closest one for my use
case, and walk me through customizing it into my eRPC config. Reference:
https://docs.erpc.cloud/presets.llms.txt
```


## Navigation (machine-readable surface)

- Up: [All pages index](https://docs.erpc.cloud/llms.txt)
- Root index of every page: [llms.txt](https://docs.erpc.cloud/llms.txt) · everything in one file: [llms-full.txt](https://docs.erpc.cloud/llms-full.txt)

### Child pages

- [DVN-ready preset (LayerZero)](https://docs.erpc.cloud/presets/dvn-ready.llms.txt) — A drop-in eRPC config for DVN operators — unanimous consensus on the four source-chain verification methods closes the forged-log attack vector that hit KelpDAO.

### Sibling pages

- [FAQ](https://docs.erpc.cloud/faq.llms.txt) — Quick answers to the most common eRPC questions — config files, caching gotchas, auth setup, rate limits, and error codes decoded.
- [Free & Public RPCs](https://docs.erpc.cloud/free.llms.txt) — Zero config, zero API keys — eRPC auto-connects to thousands of free public EVM endpoints the moment you start it.
- [Quick start](https://docs.erpc.cloud/index.llms.txt) — Stop babysitting RPC providers. eRPC handles failover, caching, and multi-chain routing so your stack stays fast even when providers don't.
- [Why eRPC?](https://docs.erpc.cloud/why.llms.txt) — eRPC eliminates provider failures, stale data, and blind spots — one proxy in front of every RPC upstream you run.