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

Expose ComputeEpochID in SDK #6

Open
konradkonrad opened this issue Jan 16, 2025 · 2 comments
Open

Expose ComputeEpochID in SDK #6

konradkonrad opened this issue Jan 16, 2025 · 2 comments

Comments

@konradkonrad
Copy link
Contributor

For proper encryption according to the protocol, an identifier needs to be encoded according to shcrypto.ComputeEpochID.

This function internally uses blst to hash the identifier bytes.

For SDK users, we should make it easy to calculate the correct format and therefore expose computeEpochID.

We have two options:

  1. either through some js/ts blst library
  2. or through adding an exposed function in shcryptowasm
@konradkonrad
Copy link
Contributor Author

  1. I found https://github.com/ChainSafe/blst-ts -- but unfortunately it does not seem to expose blst.hash_to_G1

@konradkonrad
Copy link
Contributor Author

  1. I tried exporting shcrypto.ComputeEpochID in Experimental: add ComputeEpochID to WASM rolling-shutter#570

Our wasm build seems broken with supranational/[email protected]

@ylembachar ylembachar mentioned this issue Jan 16, 2025
Closed
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
@konradkonrad