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.

Sign up for GitHub

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

Jump to bottom

Can we get rid of XOnly? #102

Closed
LLFourn opened this issue Jul 1, 2022 · 1 comment
Closed

Can we get rid of XOnly? #102

LLFourn opened this issue Jul 1, 2022 · 1 comment

Comments

@LLFourn
Copy link
Owner

LLFourn commented Jul 1, 2022

It's usually better to just use Point<EvenY>. I think I had the idea that it was faster and used less memory to just have the pre-serialized x coordinate rather than representing them as full points (3 field elements). But is this tiny speedup worth the complexity of having two types of xonly things?
@LLFourn
Copy link
Owner Author

LLFourn commented Sep 9, 2022

I decided to remove as described above in #114

@LLFourn LLFourn closed this as completed Sep 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LLFourn