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

Privacy Preserving Nameswap - DRAFT #854

Closed
wants to merge 1 commit into from

Conversation

Anunayj
Copy link
Contributor

@Anunayj Anunayj commented Sep 28, 2023

This test showcases the application of adapter signatures to facilitate privacy-preserving name swaps on handshake. Additionally, this approach can be employed for privacy-preserving cross-chain swaps.

I'll follow this up with a Blog Post in the future possibly. I am not sure if something like this is fit for HSD's main repository, and just want some opinions here.

This test showcases the application of adapter signatures to
facilitate privacy-preserving name swaps on handshake.
Additionally, this approach can be employed for privacy-preserving
cross-chain swaps.
@coveralls
Copy link

Coverage Status

coverage: 68.641% (-0.02%) from 68.656% when pulling 696493b on Anunayj:adaptor-sigs into e4245e5 on handshake-org:master.

@nodech
Copy link
Contributor

nodech commented Oct 2, 2023

I'll follow this up with a Blog Post in the future possibly. I am not sure if something like this is fit for HSD's main repository, and just want some opinions here.

Yeah, I had the same thoughts. It's not testing specific thing in the codebase. Also tests are not good place for any docs in general - Even though it can help users figure out how to use some APIs. But nature of this with extra crypto - don't want someone using this right away.

Having standalone repository - with real simple usage be much better. Which can have POC Notice and you can be more flexible in the standalone repo describing the intended flow and API.

I am looking forward to the Blog Post, so you can demystify whatever is happening on crypto side :)
I believe blog, separate repo and then sharing to Group Chats is the way to go for this.

@Anunayj Anunayj closed this Oct 4, 2023
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

Successfully merging this pull request may close these issues.

3 participants