-
Notifications
You must be signed in to change notification settings - Fork 19
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
replace secp256k1 with bcrypto#secp256k1 #34
Conversation
Does this work in the browser? |
I tried it briefly in chrome and had no issues due to Also, could forks be enabled on CircleCI so that the tests could run? |
There 2 more things that could be done to streamline things a bit.
|
I tested this with couple different networks on the browser and it is working great. Awesome job @faustbrian ! |
Doing a release later. Good idea about the steps reduction! From a developer experience perspective I would avoid two builds if not necessary. What is your reasoning for having 2? |
I generally like to keep browser and node.js builds separated to avoid having dependencies or polyfills included that would be useless for node.js or could potentially even cause issues with making wrong assumptions about the environment and its data types. |
I published the package |
good argument. happy about a PR doing though. Rn we are a bit busy with other things. |
Will try to find some time for it in the next days. |
Possibly addresses #13 as I am currently experiencing this issue which makes it impossible to sign transactions with a server-side application.