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

Disable claims (non-working) #10116

Merged
merged 3 commits into from
Dec 19, 2023
Merged

Disable claims (non-working) #10116

merged 3 commits into from
Dec 19, 2023

Conversation

jacogr
Copy link
Member

@jacogr jacogr commented Dec 19, 2023

Closes #10115

This might be an easy fix for the specific issue above, however as per the code comment there is just no way of verifying that it actually works if anything is applied. (Original development as I recall from those involved did have extensive tests for all scenarios, so could be verified as working)

For future reference: the above error stack seems to point to the fact that we don't have Buffer in the browser context - it may even be more sane if a revival is made to not use the (now very outdated, non-touched) secp256k1 libs and rather use those from @noble/*.

@jacogr jacogr added the -auto label Dec 19, 2023
@polkadot-js-bot polkadot-js-bot merged commit bc1d40e into master Dec 19, 2023
7 checks passed
@polkadot-js-bot polkadot-js-bot deleted the jg-disable-claims branch December 19, 2023 12:28
@polkadot-js-bot
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Dec 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pre-sale tokens cannot be claimed: "TypeError: message should be a Buffer"
2 participants