Sentio Docs
Ask or search…
⌃K
👋
Welcome to Sentio
🔗
Setup
🗄
Samples
💡
Quickstart
How-to Guides (by examples)
➡
Adding ABIs
➡
Data collection
➡
Visualize results
➡
Create alerts
➡
Share your project
Developer Guides
➡
CLI Reference
➡
SDK Guide
Access Sentio Via APIs
Prerequisite
Debug API
Simulation API
Code Index API
References
✅
How Sentio Works
🖥
Concepts
▶
UI layout
🔒
Quotas and Limits
💎
Supported Networks
🤝
Permission and Sharing
Sentio Debugger
⚙
Basic
ℹ
Transaction info
💰
Trace the money
🛣
Trace and Call
🔎
Debugging
⚙
Simulation
Best Practices
🔍
Best Way To Manage nodejs
🔍
Multi-Chain Support
🔍
Avoid High Cardinality
🔍
Updating Processors
🔍
Handling Errors
🔍
Performance Tuning
🔍
Cost Reduction
🔍
How To Handle Proxy Contracts?
🔍
Upgrade SDK Version
🔍
Processor State and Execution Order
🔍
Formula usage best practices
Powered By GitBook
Comment on page
🔍

Multi-Chain Support

Sentio allows users to write monitoring code in the same processor for different chains (Yes, Even for EVM and non-EVM chains!!). This is pretty convenient for monitoring multi-chain application. See this for an example.
Best Practices - Previous
Best Way To Manage nodejs
Next - Best Practices
Avoid High Cardinality
Last modified 9mo ago