When to Use EasyLayer
Use EasyLayer when blockchain state is part of your product and you need to control what state is stored, how it is updated, and where the service runs.
Good fit
EasyLayer is a good fit when you need one or more of these:
| Need | Why EasyLayer helps |
|---|---|
| Custom blockchain state | You define the model instead of accepting a generic dataset. |
| Focused storage | The application can persist model-specific events/state instead of unrelated full-chain data. |
| Reorg-aware workflows | State changes are event-based, so rollback/replay is part of the runtime model. |
| Self-hosted runtime | Data and infrastructure stay under your control. |
| Live events | Models can emit events and clients can subscribe through transports. |
| Desktop/browser integration | Transport options include Electron IPC and browser/shared-worker runtime paths. |
| Backend integration | HTTP, WebSocket, and IPC give multiple ways to connect services. |
Concrete examples
Use EasyLayer for workflows like:
- monitor one EVM contract and expose its current product state;
- track selected wallets instead of indexing every wallet on-chain;
- maintain a focused UTXO view for a Bitcoin wallet application;
- keep protocol-specific counters or status from blocks/logs;
- run a crawler inside a desktop application and query it from the UI;
- stream model events into another service without building the delivery layer from scratch.
Not the best first step
EasyLayer is probably not the first tool to use when:
- you only need a simple hosted balance lookup;
- you do not want to operate any runtime yourself;
- your required chain is not supported by current packages;
- you need a finished managed SaaS/SLA without custom agreement;
- your actual goal is a full analytics warehouse before you have defined the state model.
Decision check
Before implementing, answer these questions:
If the answers are still vague, start with a smaller model. EasyLayer works best when the state boundary is clear.