Skip to content
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

move any schnorr logic into nostr-rs #9

Open
futurepaul opened this issue Jan 11, 2022 · 1 comment
Open

move any schnorr logic into nostr-rs #9

futurepaul opened this issue Jan 11, 2022 · 1 comment

Comments

@futurepaul
Copy link
Contributor

I see there's a few places where we're using types from secp256k1. that should probably be re-exported from nostr-rs. ideally an "application author" doesn't have to think about that stuff.

there might be places where the whole schnorr logic probably belongs in nostr-rs, like peer_pk = PublicKey::from_str(ev.tags[0].content()).unwrap(); feels like nostr-rs's job

@emeceve
Copy link
Owner

emeceve commented Jan 12, 2022

I would suggest re-export secp256k1 in first place but I think the Keys struct can be used instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants