Practical overview
When it fits
Consider Exonum when a project needs a permissioned blockchain application and the team wants Rust framework components rather than a hosted blockchain service.
Who it is for
- Rust developers creating private or permissioned blockchain applications.
- Teams designing distributed ledgers for domains such as FinTech, GovTech or LegalTech.
Documented uses
- Create a blockchain application around a known set of infrastructure providers.
- Build ledger software using framework crates for nodes, cryptography, key management and data storage.
- Explore application patterns through cryptocurrency and timestamping examples.
Requirements & limits
- The repository is licensed under Apache-2.0.
- The README lists Rust 1.55.0 or later in its requirement badge and notes that dependency changes may affect the effective minimum version.
- Some APIs are explicitly described as unstable or experimental in the project documentation.
- The main repository includes a Rust runtime and test framework; Java support and JavaScript and Python light clients are separate projects.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Choose an Exonum starting point for a permissioned blockchain application
Identify the Rust crates, service-building tools, or example project relevant to an Exonum application.
Before you start
- Access to the Exonum repository README.
- A blockchain application intended for a permissioned network with known infrastructure providers.
Steps
Review the repository’s main crates: the core library, node implementation, and node CLI.
For service development, review the Rust runtime and testing framework listed under Tools for Building Services.
Choose an example matching the application area: cryptocurrency, advanced cryptocurrency, timestamping, or the sample runtime.
Open the linked README for the chosen crate, tool, or example to continue with its specific instructions.
Expected outcome
A repository-documented starting point is selected for further application development.
Guide limitations
- The repository overview does not provide the implementation steps for building or running an application; those are in the linked component or example documentation.
- The README notes that some APIs are unstable or experimental and may change in non-breaking releases.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- exonum/exonum · Official homepage title · retained in its source language

