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

support for RFC9380 DST G1 scheme #39

Merged
merged 7 commits into from
Sep 21, 2023

Conversation

CluEleSsUK
Copy link
Contributor

  • refactored the IBE code to be more generalised

@CluEleSsUK
Copy link
Contributor Author

Created a draft of this - just realised I haven't updated the client yet, so should probably do that first, then update tlock go, then create test vectors

@CluEleSsUK CluEleSsUK marked this pull request as ready for review September 11, 2023 09:02
Copy link
Member

@AnomalRoil AnomalRoil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM, but these are very breaking changes for the users, since the API of the function themselves changed, no?

test/crypto/rfc-scheme.test.ts Show resolved Hide resolved
@CluEleSsUK
Copy link
Contributor Author

yes and no - the interface for encryption and decryption hasn't changed, though users who have been using MAINNET_URL or mainnetClient() who upgrade will now automagically use quicknet rather than fastnet. In a sense this is a breaking change.
I'll bump the major version

@CluEleSsUK
Copy link
Contributor Author

actually wait it's still in 0.x.x, so I think it's fine to bump minor

- refactored the IBE code to be more generalised
* fixed some compat tests
* pointed the URLs to the right places (left the fastnet ones for compat)
@CluEleSsUK CluEleSsUK force-pushed the feature/support-for-rfc-g1-swap branch from 1cbc84d to 6a29950 Compare September 21, 2023 13:44
src/crypto/ibe.ts Outdated Show resolved Hide resolved
const opts = {
...defaultChainOptions,
chainVerificationParams: {
chainHash: "52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could have added a comment with the name of the network :P

return new HttpChainClient(chain, opts)
}

export function nonRFCMainnetClient(): HttpChainClient {
const opts = {
...defaultChainOptions,
chainVerificationParams: {
chainHash: "dbd506d6ef76e5f386f41c651dcb808c5bcbd75471cc4eafa3f4df7ad4e4c493",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could have added a comment with the name of the network :P

@CluEleSsUK CluEleSsUK force-pushed the feature/support-for-rfc-g1-swap branch from b6d496f to 484df96 Compare September 21, 2023 13:56
Copy link
Member

@AnomalRoil AnomalRoil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@CluEleSsUK CluEleSsUK merged commit d629080 into master Sep 21, 2023
1 check passed
@AnomalRoil AnomalRoil deleted the feature/support-for-rfc-g1-swap branch September 21, 2023 14:01
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