6 releases

0.3.0 Jul 19, 2023
0.2.1 May 3, 2023
0.1.6 Oct 13, 2022
0.1.2 Aug 25, 2022

#270 in Cryptography

Download history 394/week @ 2023-12-11 361/week @ 2023-12-18 200/week @ 2023-12-25 259/week @ 2024-01-01 147/week @ 2024-01-08 160/week @ 2024-01-15 388/week @ 2024-01-22 275/week @ 2024-01-29 132/week @ 2024-02-05 446/week @ 2024-02-12 232/week @ 2024-02-19 165/week @ 2024-02-26 423/week @ 2024-03-04 442/week @ 2024-03-11 556/week @ 2024-03-18 166/week @ 2024-03-25

1,599 downloads per month
Used in 3 crates (via wnfs)



Skip Ratchet Logo

Skip Ratchet

Crate Information Code Coverage Build Status License Docs Discord

This library implements the Skip Ratchet paper. Skip ratchet is a data structure for deriving keys that maintain backward secrecy. Unlike hash chains, this data structure is capable of efficiently making large leaps in hash count.



Creating a new ratchet and advancing it.

use skip_ratchet::Ratchet;

let mut ratchet = Ratchet::new();

println!("{:?}", ratchet.derive_key());

Getting the previous versions of a ratchet.

use skip_ratchet::Ratchet;

let mut old_ratchet = Ratchet::new();

let mut recent_ratchet = old_ratchet.clone();

for revision in recent_ratchet.previous(&old_ratchet, 10).unwrap() {
    println!("{:#?}", revision);

Building the Project

  • Clone the repository.

    git clone https://github.com/WebNativeFileSystem/rs-skip-ratchet.git
  • Change directory

    cd rs-skip-ratchet
  • Build the project

    cargo build

Testing the Project

  • Run tests

    cargo test


Pre-commit Hook

This library recommends using pre-commit for running pre-commit hooks. Please run this before every commit and/or push.

  • Once installed, Run pre-commit install to setup the pre-commit hooks locally. This will reduce failed CI builds.
  • If you are doing interim commits locally, and for some reason if you don't want pre-commit hooks to fire, you can run git commit -a -m "Your message here" --no-verify.

Conventional Commits

This project lightly follows the Conventional Commits convention to help explain commit history and tie in with our release process. The full specification can be found here. We recommend prefixing your commits with a type of fix, feat, docs, ci, refactor, etc..., structured like so:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Getting Help

For usage questions, usecases, or issues reach out to us in our Discord webnative-fs channel. We would be happy to try to answer your question or try opening a new issue on Github.


This project is licensed under the Apache License 2.0.


~53K SLoC