# BitFury (Bitfury Group)

> Bitfury Group is a blockchain technology company founded in 2011 as one of the earliest Bitcoin mining hardware makers and full-cycle infrastructure providers, now operating as a technology incubator headquartered in London. Its developer-facing surface is Exonum, the open-source (Apache-2.0) framework Bitfury Group Limited built for private and permissioned blockchain applications. Bitfury publishes no llms.txt of its own; this file was generated by API Evangelist from the artifacts in this repository on 2026-07-31.

Key facts an agent should know before using anything here:

- Exonum is **self-hosted software**, not a hosted API. There is no vendor base URL, no signup, no API key and no sandbox tenant. Every endpoint below is served by a node the operator runs.
- A node runs **two HTTP servers**: a public one (client reads and transaction submission) and a private one (node administration). The private server has no credential scheme — it is protected by network placement only.
- Writes are authenticated by an **Ed25519 signature over the transaction**, not by an HTTP credential.
- The API is **not idempotent by design**: transactions carry a `seed` field specifically to guarantee non-idempotence, and there is no Idempotency-Key contract.
- Reads are **eventually consistent** for in-pool transactions; a getter may return "not found" for ~20ms after a submit. Poll with a delay.
- The last release is **1.0.0 (2020-03-31)**; the repository is unarchived but dormant.

## Company

- [Bitfury](https://bitfury.com/): Company site, news and portfolio (Cipher Mining, Crystal, LiquidStack, Axelera AI).
- [Terms of Service](https://bitfury.com/terms-of-service)
- [Privacy Policy](https://bitfury.com/privacy-policy)
- [Contact](https://bitfury.com/contacts)

## APIs

- [Exonum Node HTTP API](https://exonum.com/doc/version/latest/): REST and WebSocket endpoints served by an Exonum node — explorer service (`/api/explorer`), system API plugin (`/api/system`), and per-service endpoints (`/api/services/{service_name}`).

## Docs

- [Exonum documentation](https://exonum.com/doc/version/latest/)
- [Design overview / getting started](https://exonum.com/doc/version/latest/get-started/design-overview/)
- [Explorer service API reference](https://docs.rs/exonum-explorer-service/latest/exonum_explorer_service/api/index.html)
- [Explorer WebSocket API reference](https://docs.rs/exonum-explorer-service/1.0.0/exonum_explorer_service/api/websocket/index.html)
- [System API plugin reference](https://docs.rs/exonum-system-api/)
- [Networking specification](https://exonum.com/doc/version/latest/advanced/network/)
- [Artifact versioning](https://exonum.com/doc/version/latest/advanced/versioning/)
- [Service testing with the testkit](https://exonum.com/doc/version/latest/advanced/service-testing/)
- [Light client tutorial](https://exonum.com/doc/version/latest/get-started/light-client/)
- [Roadmap](https://exonum.com/doc/version/latest/roadmap/)
- [FAQ](https://exonum.com/faq.html)

## Endpoints

- `GET /api/explorer/v1/blocks` — list block headers over a range (`count`, `latest`, `earliest`, `skip_empty_blocks`, `add_blocks_time`, `add_precommits`); returned latest-first.
- `GET /api/explorer/v1/block` — content of the block at a given `height`.
- `GET /api/explorer/v1/transactions` — transaction by `hash`, with its commit status.
- `POST /api/explorer/v1/transactions` — submit a signed transaction.
- `GET /api/explorer/v1/call_status/transaction` — execution status of a transaction call.
- `GET /api/explorer/v1/call_status/before_transactions` — execution status of a service's before_transactions hook.
- `GET /api/explorer/v1/call_status/after_transactions` — execution status of a service's after_transactions hook.
- `WS /api/explorer/v1/ws` — WebSocket with no initial subscription.
- `WS /api/explorer/v1/blocks/subscribe` — subscribe to block-commit events.
- `WS /api/explorer/v1/transactions/subscribe` — subscribe to transaction-commit events (filterable by service and method ID).
- `GET /api/system/v1/info` — node info (private server).
- `GET /api/system/v1/stats` — node stats (private server).
- `POST /api/system/v1/peers` — add a peer connection (private server).
- `POST /api/system/v1/consensus_status` — enable/disable consensus (private server).
- `POST /api/system/v1/shutdown` — shut the node down (private server).
- `GET /api/services/supervisor/services` — deployed artifacts and running service instances.
- `GET /api/services/supervisor/consensus-config` — current consensus configuration.
- `GET /api/services/{time_service}/v1/current_time` — consolidated time from the time oracle.

## Specs

- [Protobuf message definitions](https://github.com/exonum/exonum-proto-sources) — saved verbatim in this repo under `grpc/`.
- No OpenAPI, Swagger, GraphQL, AsyncAPI or MCP definition is published for Exonum, and no `/.well-known/` documents or A2A agent card exist on bitfury.com or exonum.com (all probed 404 on 2026-07-31).

## Packages

- Rust (crates.io): `exonum`, `exonum-node`, `exonum-cli`, `exonum-crypto`, `exonum-merkledb`, `exonum-rust-runtime`, `exonum-explorer`, `exonum-explorer-service`, `exonum-system-api`, `exonum-supervisor`, `exonum-testkit`, `exonum-btc-anchoring`, `exonum-time` — all 1.0.0.
- JavaScript (npm): [`exonum-client`](https://www.npmjs.com/package/exonum-client) 0.18.4, [`exonum-client-anchoring`](https://www.npmjs.com/package/exonum-client-anchoring) 0.7.2.
- Python (PyPI): [`exonum-python-client`](https://pypi.org/project/exonum-python-client/) 1.0.1, [`exonum-launcher`](https://pypi.org/project/exonum-launcher/) 0.2.0.
- Java (Maven Central): `com.exonum.binding:exonum-java-binding-core` and siblings, 0.10.0.

## Source

- [github.com/exonum](https://github.com/exonum) — the Exonum GitHub organization.
- [exonum/exonum](https://github.com/exonum/exonum) — framework monorepo (Apache-2.0).
- [exonum/exonum-doc](https://github.com/exonum/exonum-doc) — documentation source.
- [CHANGELOG](https://github.com/exonum/exonum/blob/master/CHANGELOG.md)