Repository navigation
feat: claim xe flow with xe address generator - #293
Merged
Merged
Conversation
This file contains hidden or 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
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.
Summary
Adds a Claim XE flow to the wallet. Holders send EDGE to the claims wallet and claim the same amount of XE on the new XE network, 1:1.
VITE_CLAIMS_API_URLis set and the claims service/infosays claims are open.data: { memo: "Claim XE", ref }. The progress view follows the transfer: posted, in a block, 10+ confirmations, received by the claims service.xe/account/v1followed by the public key, as 64 lowercase hex.src/utils/xe-recovery-phrase-vectors.jsonholds the XE core test vectors.Configuration
VITE_CLAIMS_API_URL: the claims service URL. Unset hides the Claim XE button.Dependencies
@scure/bip39,@noble/curves,@noble/hashes(2.4).Testing
npm test: 117 tests pass, including the XE core recovery phrase vectors.