sinu.eth

> because it's unclear which transcript it is What other transcript would be getting notarized? I think we can assume _some_ context has been established. We don't want to have...

> transcripts normally contain every message sent in both directions, from beginning to end We are including every message sent in both directions (minus the handshake messages, but keeping the...

> Could you give a specific scenario? There can be use cases where someone wants to distribute the `Notarized Transcript` and plaintext to another party so they can use it...

In our weekly meeting we discussed this and concluded some things: - We will use the term `User` to refer to the `Requester` and `Prover` when talking about the protocol...

That was my original plan until I saw just how deep our changes were going to be. Ultimately I decided to rip out quite a lot from rustls (Ring is...

The test suite can be diffed without encapsulating it as a commit, it's a couple of files. Rustls also has a BoringSSL (bogo) test shim so we will be able...

Closing, stale issue and I believe we concluded against.

Relevant: tlsnotary/mpz#4

## Framing I do not think we can structure the Notarization document around "Rounds", as those are application layer concepts/framing. During the construction of this document the Notary will not...

> A Chacha20 circuit has ~2x less AND gates per byte of output compared to the AES128 circuit How did you determine this? Is there a ChaCha20 circuit somewhere I...