Skip to content

feat!: improve hyperkzg api#353

Merged
srinathsetty merged 4 commits intomicrosoft:mainfrom
JayWhite2357:feat/improve-hyperkzg-api
Jan 23, 2025
Merged

feat!: improve hyperkzg api#353
srinathsetty merged 4 commits intomicrosoft:mainfrom
JayWhite2357:feat/improve-hyperkzg-api

Conversation

@JayWhite2357
Copy link
Copy Markdown
Contributor

@JayWhite2357 JayWhite2357 commented Jan 11, 2025

Rationale

There are a few things in hyperkzg that make upstream usage impossible or difficult. In particular, the actual proof is inaccessible in a transparent fashion.

Changes

Take a look at the individual commits.

@JayWhite2357 JayWhite2357 force-pushed the feat/improve-hyperkzg-api branch from d09c9da to 74b783e Compare January 22, 2025 13:59
@JayWhite2357 JayWhite2357 changed the title feat: improve hyperkzg api feat!: improve hyperkzg api Jan 22, 2025
This makes the transcript more compatible with the EVM, which is big-endian
This is accomplished via `new` and `into_inner` methods
This is accomplished via `com`, `w`, and `v` accessors.
This can be used instead of `CommitmentEngineTrait::setup` to generate a reproducible commitment key
@JayWhite2357 JayWhite2357 force-pushed the feat/improve-hyperkzg-api branch from 74b783e to 26cd4a9 Compare January 23, 2025 03:36
@srinathsetty srinathsetty merged commit 2a513f5 into microsoft:main Jan 23, 2025
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.

2 participants