IOTA Stronghold is a secure software implementation with the sole purpose of isolating digital secrets from exposure to hackers and accidental leaks. It uses encrypted snapshots that can be easily backed up and securely shared between devices. Written in stable rust, it has strong guarantees of memory safety and process integrity.
There are three main components of Stronghold:
- Client: The high-level interface to Stronghold (prefers Riker, functional integration also available)
- Engine: Combines a persistence store (Snapshot) with an in-memory state interface (Vault), a read/write key:value system (Store) and memory protection services (Runtime).
- P2P-Communication: Enables Strongholds in different processes or on different devices to communicate with each other securely.
In April of 2021, F-Secure performed a security assessment of the core crates of IOTA Stronghold and found nothing of concern. This is not an explicit declaration of fitness or freedom of error, but it is an indicator of the high quality of the code. You may review the audit here.
Here are some of the features and tasks that we are working on.
- Engine
- Client (with dual interfaces)
- peer-to-peer communications
- Secure runtime zone
- Integration with crypto.rs
- User Handbooks
- Specification Documentation
- Tutorials
- Unit Tests
- Lowlevel Library Fuzzing
- Realworld tests
- Multiplatform benchmarks
- Continuous Fuzzing
- CLI binary
- Dynamic high-performance store
- Standalone Desktop Application
- Portable Daemon (for nodes, etc)
- C FFI bindings
- Works with USB Armory Mk II
- Works with Yubikey
- Works with Ledger Nano X
- Use Secure Element to generate private keys for decryption
- Move entirely to FPGA
cargo doc --workspace --no-deps --open
cargo test --all --all-features
If you want to get involved in discussions about this technology, or you're looking for support, go to the #stronghold-discussion channel on Discord.
If you wish to join the Stronghold X-Team, please fill out this form.