-
Notifications
You must be signed in to change notification settings - Fork 68
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
[version 3.0.0] Major version bump #199
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…instead of throwing
…e-client-nodejs package
* add normalization fix * use different prop names for signature data * feat: refactor normalizeParams * fix jsparam undefined case, adds test --------- Co-authored-by: Ansonhkg <[email protected]>
* pkpethers - tableland works * feat: lit config & pkp-ethers update
* mint by auth method * remove url * feat: fix authmethod type 6 * add a note * feat: add enums * remove declare * rename from 'mint' to 'mintWithAuth' for better clarity * fix: ignore_dirs
…function (#254) * feat: public static to get auth id by auth method * fix: import
* WIP * wip2 - awaiting verifyAndMintPKPThroughRelayer to be implemented * fix: verifyAndMintPKPThroughRelayer with custom args * update pkg * remove comment * rm lock --------- Signed-off-by: Anson <[email protected]>
Signed-off-by: VoR0220 <[email protected]>
A hack was added a year ago to suppress a webpack complaint. Other packages import crypto and don't seem to contain this hack. The metro bundler doesn't allow for conditional requires / substitutions, and as such causes react-native to fail loading the crypto library. This PR removes the hack. I have not checked if webpack still complains but am hoping Chris can chime in.
* feat: Store blockhash from handshake + use it in SIWE * feat: Pass blockhash instead of client in authSig functions * refac: Cleanup * feat: Client getter for blockhash + Manual tests * refac: Remove comments * refac: latest_blockhash -> latestBlockhash * test: Display result of manual tests * test: Node E2E test for creating authSig by fetching the blockhash from the client
closing for #266 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
!! SDK VERSION 3.0.0 Release Branch !!
Changes from #145
Changes from #107
computePubKey
tolit-core
which wraps an implementation incrypto
for interfacing with a new wasm module for deriving HD public keys: for reference the implementation which is compiled to WASM is here: https://github.com/LIT-Protocol/lit-ecdsa-wasm-combine/blob/main/src/combiners/hd_ecdsa/mod.rsclaimKeyId
method onlit-node-client-nodejs
for deriving a key from anauthMethod
MintCallBack
which is defined asasync (params: ClaimKeyResponse): Promise<ClaimKeyResponse>
which is called to route derived keys from a claim operation on chain.ClaimProcessor
abstraction for specifying arguments to a callback implementation for forwarding aggregated claim responses from nodes to theChronicle
chain which can be done by arelayer
orcontract client
implementation within the callback.