Jeff Burdges

I'd second that this would be great, but good to know the official way to do cryptographic keys now.

We added backcerts of operator keys alraedy, no? Or was that an RFC but not yet implemented? We could use backcerts for proof-of-possession. Ideally, we should place system randomness into...

https://github.com/polkadot-fellows/RFCs/pull/48 It's seemingly just ownership proofs, but really they should sign the operators key, making them backcerts. I proposed having some master session key too, but that's a bigger change....

It's offten that backcerts get forgotten because we do not see them in TLS since the handshake itself represents the backcert, meaning the site itself sent you their certificate in...

> The binary trie format is a trade-off. It's worse for disk accesses but better for proof size. There is no reason every layer should be stored on disk, just...

> Changing the trie format is something we already did once .. it seems to be a painful process, but something doable We could make storage orthogonal from the rest...

I'd expect common prefixing of related storage would typically occur in one or maybe two layers. You could treat NOMT as a storage of storage roots, by placing blake3 encoded...

We should really not overload the usage of the keyword `use` so much, but ignoring the keyword.. Isn't it easier to understand if we've some macro for the multiple clones...

We've past proposals for inherent trait methods I think, mostly proposing a second inherent looking `impl` block, not sure that syntax matters, but this winds up functionally equivelent, yes? There...

I'm more asking what's the best default. If the best default were to be in the vtable, then you can just do ``` trait Trait { #[inline(always)] impl(crate) fn f(&self)...