Sentio Processor
by @sentioxyz
Use when initializing Sentio projects, writing blockchain processor code, adding contracts/ABIs, testing processors, or deploying to the Sentio platform. Tri...
1. Use sequential: true when handlers share state via entity store
2. Do NOT use global variables for persistent state β use ctx.store
3. Use startBlock to skip irrelevant history and reduce backfill cost
4. Prefer Metrics over Logs/Entities for aggregated numerical data (lower cost)
5. Never use addresses/hashes as metric labels β ~10k series limit per metric
6. Use event filters (Processor.filters) to reduce unnecessary handler executions
7. Increase backfill intervals to the largest acceptable value for cost reduction
8. Use listIterator() instead of list() for large entity datasets
9. Use Promise.all for parallel contract calls and entity processing
10. Use BigDecimal and scaleDown() for precision β avoid floating point
11. Filter null addresses with isNullAddress() for mint/burn events
12. Skip self-transfers β if (from == to) return;
clawhub install sentio-processor