-
Notifications
You must be signed in to change notification settings - Fork 70
Issues: tlsnotary/tlsn
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Add support for multiple attestation keys
enhancement
New feature or request
notary server
Improvements or problems in the notary server reference implementation
#596
opened Sep 19, 2024 by
sinui0
Update Notary server to use secp256k1
notary server
Improvements or problems in the notary server reference implementation
tlsn-wasm: the prover and verifier class should throw error in typescript
#578
opened Sep 1, 2024 by
0xtsukino
TLSNotary server wont start without Good for newcomers
private-key-pem-path
defined even when its unused
good first issue
#565
opened Aug 14, 2024 by
pirate
Remove Good for newcomers
#[allow(clippy::blocks_in_conditions)]
when clippy fixes it
good first issue
#535
opened Jul 12, 2024 by
yuroitaki
Batch MAC decommitment for decryption
enhancement
New feature or request
#527
opened Jun 28, 2024 by
th4s
Disable nightly features for wasm build
good first issue
Good for newcomers
#524
opened Jun 26, 2024 by
themighty1
Encrypt/Decrypt many TLS records at once
enhancement
New feature or request
#495
opened Jun 11, 2024 by
th4s
Add memory profiling to benchmarks
enhancement
New feature or request
#462
opened Mar 21, 2024 by
sinui0
[Placeholder] Proofs with duplicate HTTP headers should be treated as invalid
#431
opened Feb 9, 2024 by
themighty1
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.