Irakli Gozalishvili

> Whether or not there is a need to have a human-readable form of this and what that would look like could be deferred till later. Have not had a...

@mikeal I think you may be misunderstanding what I was trying to say in quoted message. I do agree on the proposed layering. And agree that dag-secretbox should encode info...

> > There will be codecs that are more of a "transcoders" if you will. It takes data in some format say encoded in "dag-cbor" and encrypts it. The problem...

> ```js > let container = { > _encryption: { nonce, publicKey, algo } > _data: encrypt(dagCbor.encode({ foo: “i’m secret encrypted data” }, nonce, algo, privateKey)) > } > let...

It's not that it's not doable, I'm already doing it by using multicodec and prefixing encoded bytes before encryption (which also hides format that your proposed solution doesn't) and on...

@mikeal also worth mentioning that your proposed solution works with one layer of encryption, but what if you have multiple layers that you have a problem.

> Let’s explore this a little further. Is the fact that you’re encoding git data sensitive as well? In other words, if we were to encode a CID, would we...

> Let’s explore this a little further. Is the fact that you’re encoding git data sensitive as well? In other words, if we were to encode a CID, would we...

> > > > So, the format is _not_ encrypted? Or at least, not encrypted at layer these encodedBytes are stored, but it may be inside another encrypted container. It...

It is worth mentioning that if in the above case `block` was `CID` it would have worked exactly as desired (well except secret won't be a secret, or be inaccessible)...