1006fd9503
keyfork-derive-util: cleanup types
96e6c236f0
keyfork-derive-util: add some documentation
5424e66aed
**/Cargo.toml: refactorings
e850c75879
keyfork-derive-util: Flesh out most of secp256k1
735f9b4442
Makefile: add kustomize
ae7166d7d3
Makefile: fix gopath issues
0a444e205a
go toolchain 1.20.4: not working, need to fix GOROOT
98baaed81c
cargo fmt
da96ea94bd
keyforkd: extract DerivablePath
a9209ee36a
keyforkd: swap minicbor for serde + bincode
067de52e4b
keyforkd: initial commit
fa8e6d726d
keyfork-frame: add asyncext to allow AsyncRead/AsyncWrite
Rewrite keyfork-frame in terms of
bytes::Buf
and bytes::BufMut
76c9214d73
keyfork-mnemonic-util: impl FromStr for Mnemonic
ee15145662
keyfork-frame: initial commit
8ec5dc0dec
keyfork-mnemonic-generate: test ensure entropy floats around what we expect from birthday values
keyfork mnemonic recover
should accept words in a randomized pattern
Resolved. Vec::dedup only removes sequential duplicates.
keyfork mnemonic recover
should accept words in a randomized pattern
use std::io::Read;
use rand::prelude::*;
fn get_u32_os(file: &mut std::fs::File) -> u32 {
let mut bytes = [0u8; 4];
file.read_exact(&mut bytes).unwrap();
u32::from_le_by…
keyfork mnemonic recover
should accept words in a randomized pattern
The math says this should be 12%. snail's Python code says this should be 12%. My Rust code - even with OS RNG - says this should be 12%. And yet, for some reason, this test stops at 1%.
https:/…
keyfork mnemonic recover
should accept words in a randomized pattern
Figuring out the math for the possibility a 24 word mnemonic has duplicate words, using some rough birthday-problem math (https://en.wikipedia.org/wiki/Birthday_problem#Calculating_the_probability)…