Jason Dreyzehner

Thinking about it more: using the `p` character as a separator makes it hard to visually parse the "depth" of a path, so it's easy to confuse two paths as...

One remaining ambiguity with using `:` – should relative paths be prefixed with `./` even if that segment wouldn't otherwise have an initial `/`? E.g. for absolute path `r/0'/1':2/3`, given...

Maybe the best option: don't support relative paths. [YAGNI](https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it) There are probably exceptionally few applications where it would be a good idea to even use a relative path. For the...

Ya, after this discussion, I think you're right – we should probably leave the API mostly as-is, and just allow support for "relative" paths without any new character scheme, e.g....

Hey @MicahZoltu – thanks for opening an issue! I would definitely like to add support for Keccak-256: this might be a good thing for @ARitz-Cracker to chime in on (he...

Hey guys – @ARitz-Cracker thanks for the detailed info, glad to hear you got it working! > but I've created a WASM version here: https://github.com/ARitz-Cracker/keccak-wasm This looks awesome! Nice work....

This isn't necessarily related to the issue, but for building, try `yarn compile:hashes` or `yarn compile:debug:hashes`. On determinism – you're definitely right. In fact, the Secp256k1 build isn't necessarily deterministic...

Thanks for opening an issue! Yes, that tsdoc line seems to be outdated now. Would you mind [sending a PR to remove it](https://github.com/bitauth/libauth/edit/master/src/lib/key/key-utils.ts)? (I can definitely remove that line in...

Thanks for opening an issue! I'll definitely want to add this. I'll probably get started on it after https://github.com/bitjson/bitcoin-ts/pull/9 👍

Relevant comment from @joshmg in Bitcoin ABC Telegram group: `Would it at all be possible to add unique-identifiers to each test case? Perhaps just a UUID or something simple. The...