-
Notifications
You must be signed in to change notification settings - Fork 77
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
Improve README of tlsn-wasm
documentation
Improvements or additions to documentation
wasm
#625
by heeckhau
was closed Jan 14, 2025
feat(notary-client): Add support for specifying path
enhancement
New feature or request
#612
by sinui0
was closed Oct 4, 2024
Support reading config values from CLI for notary-server
good first issue
Good for newcomers
notary server
Improvements or problems in the notary server reference implementation
#604
by yuroitaki
was closed Oct 11, 2024
Update Notary server to use secp256k1
notary server
Improvements or problems in the notary server reference implementation
TLSNotary server wont start without Good for newcomers
notary server
Improvements or problems in the notary server reference implementation
private-key-pem-path
defined even when its unused
good first issue
#565
by pirate
was closed Nov 22, 2024
Remove Good for newcomers
#[allow(clippy::blocks_in_conditions)]
when clippy fixes it
good first issue
#535
by yuroitaki
was closed Oct 1, 2024
Previous Next
ProTip!
Updated in the last three days: updated:>2025-01-15.