Support
FAQ
Questions are grouped to match XSIC decision flow so operators can validate assumptions quickly.
Workflow and scope
- What is the recommended way to use XSIC?
- Run Sell Impact first, then check Liquidity Pulse persistence, confirm Exit Coverage Map route availability, and finish with Exposure Graph concentration review.
- Can one app be used alone?
- Yes, but confidence improves when at least one neighboring context app is used for cross-checking.
Data freshness and availability
- How fresh is XSIC data?
- Freshness varies by app and endpoint. Always read timestamp, state badge, and source label before acting.
- What does stale or partial mean?
- It means XSIC is retaining the latest readable snapshot while some refresh paths are delayed or degraded.
Accuracy and model limits
- Are outputs final execution results?
- No. They are bounded estimates from observed state and can differ from realized fills.
- Can XSIC predict future prices?
- No. XSIC provides context and pressure signals, not deterministic price forecasts.
Privacy and security basics
- Do I need to provide wallet secrets?
- No. XSIC analytics pages do not require seed phrase or private key submission.
- What should users avoid?
- Never paste secret material into websites, chats, screenshots, or browser extensions.
Support and requests
- Where should bugs be reported?
- Use the contact route in navigation and include URL, timestamp, pair/preset, and state badge.
- Can I request new pairs or features?
- Yes. Include concrete workflow impact so prioritization can be done objectively.