roconnor-blockstream

The current proposal has left semantics for data portions beginning with A-Z as undefined (aka invalid). So there is room to repurpose that for multi-level schemes. Multi-level schemes will likely...

For the simple transport case, a simple one time pad with a QQQ checksum would suffice.

Here is a crazy half-baked idea. Currently our HRP of "ms" implies a prefix that is effectively "PRRQDN". But what if we made our prefix "PRRQDNSSSSSSSS". This has no effect...

No, my intention was to begin with "ms2g1" for a 2-of-n second level split, and "ms9g1" for a 9-of-n second level split. That said, there are some variations that are...

Another line of thought is that we should be able to insert a carefully crafted 13 or longer character string at the beginning without changing the checksum. Possibly somewhat fewer...

Okay I think we can move all the nastiness into a specification of the second-level sharing. Given any first level prefix, which currently is drafted to be `PRRQDN` and, because...

For the worksheet, what I'm imagining would require adding threshold - 1 many Ss to the start and having a lookup table to tell give you a compacted start for...

I believe that is accurate.

Fair point. Probably everything should have a table and a volvelle format.

There are a couple of other sources of arithmetical undefined behaviour: * negating MIN_INT causing signed integer overflow. * bit shifting by greater than or equal to the width of...