CoreFoundations
Module Reference
A guided map of every public module exported from @qubiq/core.
Pick a module to dive in:
HTTP Clients
Live, Query, Archive REST bindings.
Connectors & Node Facades
Event-driven connectors plus QubicNodeClient.
Wallets & Signing
Derivation, signing, secure storage, watchers.
Automation Pipelines
Pipelines, transaction queues, runtimes.
Monitoring & Telemetry
Tick/balance monitors + Prometheus.
Boot Management
Boot flags, state stores, restart logic.
Serialization
Transaction and header encoders.
Proposals & CCF
Workflow helpers + contract queries.
Interop & Protos
HTTP clients today, proto refs for future transports.
Testing & Fixtures
Mocks, snapshot replays, smoke tests.
Types & Schemas
Zod schemas for RPC + governance.
Utilities
Byte helpers, config, builders.
How modules layer together
Stack overview
- Types & Serialization — shared Zod schemas + byte encoders.
- Clients & Connectors — HTTP bindings plus event emitters (proto ready for future gRPC).
- Wallets — derivation, signing, watchers feeding automation.
- Automation + Monitoring — pipelines dispatch transfers, metrics observe them.
- Proposals — CCF contract helper + registries for governance-aware automation.
Tips for SDK authors
- Mix and match modules; everything exports plain classes/functions with rich typings.
- Use the TypeScript/TSDoc guide to pull inline API references into your own docs.
- Downstream packages (CLI, desktop wallet, @qubiq/sdk) will pull straight from these modules—mirror that approach in your libraries to stay compatible.