A map, not a partnership claim
These technologies illustrate roles in a possible mining or compute observation stack. SiliconMining.com does not operate live connectors to them, claim certification, or imply a commercial relationship. Exact support depends on the product, version, and configuration you choose.
Start with the role you need, then verify the relevant documentation. A brand name in an architecture diagram is not evidence that two components will work together without an integration project.
Bitcoin Core: network and block context
A node is distinct from mining hardware and from a pool-accounting system. Its documented interfaces can provide network or block-related information for an appropriately secured application. Do not expose node administration publicly to support a marketing dashboard.
Read the Bitcoin developer mining guide and our proof-of-work overview to understand the roles before defining an adapter.
Stratum: work communication
A mining connection may include a device, a translation proxy, and an upstream pool. Record which protocol components each participant supports and verify the full path in a controlled pilot. Keep the transport, session state, and accounting outcome separate.
The Stratum field guide explains the evaluation method. The protocol specification is the direct reference for implementation details.
Prometheus: metric organization
A metrics system needs consistent units, stable labels, and sensible cardinality. Design an exporter around documented observations rather than creating a new label for every log message or timestamp.
Use Prometheus naming guidance alongside the monitoring design guide. No Prometheus server or exporter runs behind the public site.
NVIDIA telemetry: device observations
Read-only GPU queries can support an initial experiment, while a maintained collector should follow the vendor's programmatic-interface guidance for the supported environment. Document unavailable fields and keep device observations tied to workload results.
The GPU monitoring guide introduces the workflow, with the official nvidia-smi documentation as the interface reference.
Define an adapter acceptance test
For each adapter, document inputs, output fields, units, identities, timestamps, permissions, and failure behavior. Test absent measurements, unsupported values, restarts, and delayed responses. Begin with a read-only boundary and add no privileged operations incidentally.
The public JSON contract offers a small starting shape. A production integration still requires its own implementation, authentication where needed, monitoring, and operational review.