sinu.eth
sinu.eth
Hi, we're currently enjoying using this crate in our project. However, we're now looking to allow users to provide their own hash algorithms which are plugged in with dynamic dispatch....
This PR completely rewrites `tlsn-core` for our alpha.7 release. Closes #438 There are still a couple of loose ends that I'm tidying up but the vast majority of the deliverable...
This PR integrates the changes from #574 into the rest of our crates.
The recently implemented WASM bindings #536 are still coupled to `web-sys`, which prevent them from being used in node.js. It should be possible to remove this dependency by lifting the...
The keyword `gen` is being reserved and we use it various places related to a garbled circuit generator. We must replace our usage.
Ferret needs COT for bootstrapping, implement the traits for KOS
Our `secp256k1` signer we provide in `tlsn-core` is not compatible with Ethereum as the `k256` crate uses `sha256` to hash the message. We should update [our signer implementation](https://github.com/tlsnotary/tlsn/blob/4d5102b6e141ecb84b8a835604be1d285ae6eaa5/crates/core/src/signing.rs#L252) to hash...
We want to support having the Prover prove the certificate chain to the Notary without revealing the server identity but instead obtaining a commitment to the Server's DNS name.
[Major browsers/runtimes support](https://webassembly.org/features/) native WASM threads now, which is far preferable over using Web Workers for multithreading. However, the `wasm32-unknown-unknown` target does not support the WASM threads extension (AFAIK), which...
After the TLS connection, it may be desirable for the Prover to prove the server MAC key to the Verifier instead of performing 2PC-GHASH to verify tags. This would allow...