Ben Westgate

This solves a threat model where you want recovery to absolutely require a third party or an international flight. Example 1: 2 shares; local, international, threshold 2 4 sub-shares in...

> In the 2-level case it also lets you fit the data into a single cryptosteel side, provided you drop the `MS1Z` prefix ... which is very inadvisable in general...

If the `ms1` `threshold` is stored the sub-share padding, only the `threshold` and `hrp` change when converting from a "sub-share secret" to a codex32 share. This lets the identifier match...

If your sub-shares combine successfully the checksum is no longer needed except for recovery by hand, where you may want to calculate two or three share checksums before the final...

I had multi-level SSS in mind. I agree then, the checksum should preserve by hand. Let's abandon 48-char then, keep 'ms' or 'ms1' as beginning of header for disambiguation, and...

I'm not suggesting to add it to the import document now. I think the import document is ready to review if you like this version: https://github.com/BenWestgate/codex32/blob/import-doc/docs/wallets.md It's clear to me,...

I have a project that syncs bitcoin core on an external drive and this would really help a lot of people testing it with smaller flash drives and higher RAM....

> The UX for downloading two verification files sucks IMO. I think we should just go for the clearsign option, even if it's exclusive. > > Thoughts? We have [`./contrib/verify-binaries/verify.py`](https://github.com/bitcoin/bitcoin/tree/master/contrib/verify-binaries)...

Concept ACK. Except for: > make startup abort if the value provided is too high, rather than quietly rounding it down. This breaks scripts that set dbcache to a %...

> > This breaks scripts that set dbcache to a % of available RAM. > > Do you know any example of people doing that? My [project](https://github.com/BenWestgate/Bails/blob/master/share/applications/bitcoin-qt.desktop) Bails puts this...