0.2.7 Aug 16, 2022
0.2.6 Aug 13, 2022
0.2.2 Jul 22, 2022
0.1.7 Jul 9, 2022
0.1.0 May 26, 2022

#7 in #ed25519-private

Download history 45/week @ 2023-10-31 59/week @ 2023-11-07 45/week @ 2023-11-14 33/week @ 2023-11-21 69/week @ 2023-11-28 13/week @ 2023-12-05 21/week @ 2023-12-12 30/week @ 2023-12-19 61/week @ 2023-12-26 25/week @ 2024-01-02 25/week @ 2024-01-09 46/week @ 2024-01-16 39/week @ 2024-01-23 42/week @ 2024-01-30 40/week @ 2024-02-06 84/week @ 2024-02-13

216 downloads per month
Used in 72 crates (13 directly)


11K SLoC

id: secure_storage title: Secure Storage custom_edit_url: https://github.com/aptos-labs/aptos-core/edit/main/secure/storage/README.md

Secure Storage

Secure storage provides a secure, persistent data store for sensitive data in the blockchain. Examples of sensitive data here include information required for safety and identity, such as cryptographic keys and consensus safety rules, as well as run-time configuration data.


For a design overview of secure storage, including the APIs, error types and policies, refer to the secure storage specification: [TODO(joshlind): publish the secure storage spec!]

Implementation Details

This crate defines the secure storage API, made up of two separate Rust traits (interfaces):

  • KVStorage: The KVStorage trait offers a key-value storage abstraction (e.g., to get and set key-value pairs).
  • CryptoStorage: The CryptoStorage trait offers a cryptographic-key based storage abstraction for Ed25519 keys (e.g., key creation, rotation and signing).

This crate provides four different secure storage implementations, each of which implements both KVStorage and CryptoStorage:

  • Github: The Github secure storage implementation provides a storage backend using a Github repository.
  • Vault: The Vault secure storage implementation uses the Vault Storage Engine (an engine offered by HashiCorp: https://www.vaultproject.io/). The Vault secure storage implementation is the one primarily used in production environments by nodes in the blockchain.
  • InMemory: The InMemory secure storage implementation provides a simple in-memory storage engine. This engine should only be used for testing, as it does not offer any persistence, or security (i.e., data is simply held in DRAM and may be lost on a crash, or restart).
  • OnDisk: Similar to InMemory, the OnDisk secure storage implementation provides another useful testing implementation: an on-disk storage engine, where the storage backend is implemented using a single file written to local disk. In a similar fashion to the in-memory storage, on-disk should not be used in production environments as it provides no security guarantees (e.g., encryption before writing to disk). Moreover, OnDisk storage does not currently support concurrent data accesses.

In addition, this crate also offers a Namespaced wrapper around secure storage implementations. Using the Namespaced wrapper, different entities can share the same secure storage instance, under different namespaces, providing an abstraction that each entity has its own secure storage backend.

How is this module organized?

    ├── github             # Contains the secure storage implementation based on Github.
    ├── src                # Contains the definitions for secure storage (e.g., API and error types),
                                as well as lightweight implementations for testing (e.g in-memory and on-disk).
    |── src/tests          # Contains the testsuite for all secure storage implementations.
    ├── vault              # Contains the secure storage implementation based on Vault, including the client
                                add fuzzing helper functions.


~740K SLoC