Dave Longley

@RieksJ, I do think that's a useful construct, but also use-case dependent. I don't think this group should define it (I don't think that's what you meant though?) ... and...

@daniel-dewa, > Currently GZip is hardcoded into the standard, could it be possible to have a prefix or something that specifies which algorithm the data is compressed with? Yes, however,...

@adeinega, > Just out of curiosity... what are you thoughts about [ZLIB](https://datatracker.ietf.org/doc/html/rfc1950)? GZIP, the standard's current choice, is more or less just ZLIB (deflate algorithm) with a different header. It...

We should probably set (or suggest) a maximum list size of `2^26` (= `67108864`) as this is the largest list that fits in 10MiB (67108864 bits / 8 / 1024...

It's important to allow for cases like "canon hash" as well, i.e., data was canonicalized and *then* hashed, self-expression as well. For example, see these entries (and maybe those between...

When using semantic compression, the context used by a producer and a consumer needs to be stable -- any changes to the context (with the exception of changing scoped-contexts that...

> it's more the inconsistency in how things degrade, rather than the degradation itself. Really, the scenario here is around devices being deployed for years without firmware upgrades, which is...

I support adoption of this work item.

TL; DR: I think we can be flexible here to be supportive of an existing community, but the proposal above doesn't seem like the optimal way to do that. I...

As you say, the `0xe7` code (encoded as `0xe701` as a varint) entry in the multikey table is for a compressed secp256k1 public key (i.e., 33 bytes w/1 byte for...