FAQ
Answers to common questions about 0bit documentation, products, assets, and integration paths.
Answers to common questions about 0bit documentation, products, assets, and integration paths.
What this page covers
- Integration questions
- Asset and protocol activity questions
- Operational and support questions
Integration questions
Where should I start?
Start with Quickstart if you are new to the docs. If you already know the product surface, use the product-specific quickstart for 0Gate, 0Pools, 0Base, or 0Link.
Why do product sidebars differ?
Each top-level section owns its own sidebar. Get Started pages should not show product-only build pages, and product pages should not send introduction links back to Get Started unless the link is intentionally cross-product.
Can I use the /docs/... links?
Yes. Internal docs links are written with the short /docs/... alias where possible, while the app continues to resolve them to the active documentation route.
Asset and protocol activity questions
Does an asset page mean the asset is live everywhere?
No. Asset docs describe configured documentation surfaces. Live availability depends on environment, entitlement, region, liquidity, risk controls, and operational rollout.
Is 0Pools Scan the source of settlement truth?
No. 0Pools Scan helps inspect protocol activity. Settlement and finance decisions should also use product API records, verified webhooks, and operations reports.
Operational and support questions
What should I trust for payment completion?
Use verified server-side signals. Browser callbacks are useful for UX, but signed webhooks and reconciliation records are the reliable source for fulfillment and finance workflows.
What should I log for support?
Log request IDs, product surface, environment, status, event IDs, and partner-visible references. Do not log secret keys, raw webhook secrets, payment credentials, or sensitive identity data.