Roadmap
See what 0bit is building across payments, liquidity, protocol data, and connected apps.
See what 0bit is building across payments, liquidity, protocol data, and connected apps.
Documentation boundary
Resource pages orient readers without creating a second implementation contract. Product docs, API reference pages, and release notes are the source for exact integration details.
What this page covers
- Roadmap
- Product navigation, availability wording, and next-step routes
- Availability caveats, route ownership, and support boundaries
How it fits
Resource pages orient readers without creating a second implementation contract. Product docs, API reference pages, and release notes are the source for exact integration details.
Workflow
- Choose the product or resource area.
- Confirm the current product page for implementation details.
- Check API and configuration pages for auth, webhook, and error behavior.
- Use operations pages for reconciliation and monitoring.
- Treat roadmap and support matrices as review-dependent unless explicitly approved.
Status and data signals
| Signal | Use it for | Do not use it for |
|---|---|---|
| Product map | Where to start. | Duplicate navigation system. |
| Support context | How to verify compatibility. | Universal availability claim. |
| Roadmap item | Planning direction. | Committed launch date. |
| Related link | Route to implementation docs. | Missing or placeholder href. |
Implementation notes
- Start in sandbox or test mode with fake data.
- Keep server-only credentials, webhook secrets, PII, provider payloads, and internal runbooks out of public docs and browser code.
- Use documented ids, request ids, event ids, timestamps, status fields, asset symbols, and environment names for support and reconciliation.
- Treat browser callbacks as user-experience signals; use signed webhooks, API reads, scan records, or settlement reports for durable backend state.
- Confirm product access, entitlement, regional availability, and review status before presenting the workflow as live.
Related pages
Products
Choose the product area that owns the workflow.
0Pools asset support
Review asset-specific context, mint/burn records, and pool activity views.
API reference
Use the API overview for endpoint groups, auth, errors, and webhooks.
Roadmap
Read planning context without treating it as a launch commitment.
Example trace
A resource page should help a reader choose where to go next. If the reader needs to implement, send them to the product page. If they need credentials, send them to configuration and authentication. If they need support or finance review, send them to operations. If they need to evaluate public availability, keep the wording cautious and point to current product docs rather than creating a second source of truth.