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

Feature request: pure parser #6

Open
chidg opened this issue Mar 28, 2024 · 0 comments
Open

Feature request: pure parser #6

chidg opened this issue Mar 28, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@chidg
Copy link

chidg commented Mar 28, 2024

For the extension, we generally follow a practice of avoiding cryptographic operations on the front end as much as possible for performance reasons, and also to avoid bundle size blowout. Some of the @polkadot/util-crypto utilities use large wasm blobs and increase build size and script loading time considerably. Over time, we've reduced our use of these utilities on the front end and plan to remove them entirely.

For integration with the extension, we would love to see a version of SiwsMessage which would not import any cryptographic modules like those from @polkadot/util-crypto or @azns/resolver-core. As a suggestion, it could be structured so that users of the API could pass in their own verification methods - then we could call the existing utilities on the extension backend to verify - alternatively, since we don't need currently use those methods, we would be happy with a base SiwsMessage class without them.

@chidg chidg added the enhancement New feature or request label Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant