**[Caution]** NPM package currently in public is unknown 0.2.5 version

[ChiaMineJP]

The problem

If you install bls-signatures via npm install bls-signature, you will install bls-signatures of version 0.2.5,
whose source code has not yet been published to this repository.
https://www.npmjs.com/package/bls-signatures
Maybe a developer built and published its private source code into the npm registry.

I cannot say it is untrusted because the one who published the 0.2.5 version of the npm package is one of the original authors.

But in the world of crypto currency, it requires extreme level of transparency.
The npm package published to the npm registry should be synced to the source code publicly available by this repository.

Note

Anyone who wants to install the latest package including fixed js-typings which is recently committed, please go visit my forked repository.

[tiantianlikeu]

I have a this problem

[hoffmang9]

The version in npm is a legitimate js binding of bls-signatures from before it was modified to be fully IETF BLS compliant. It is totally out of date. We are currently working on getting a new release into npm and should have that complete in the next few days.

[tiantianlikeu]

@hoffmang9 ok ,thanks

[tiantianlikeu]

@hoffmang9 Hello, Are U sleep? I has a new problem, Do you consider adding mnemonic genration and mnemonic import in the new version?

[ChiaMineJP]

@hoffmang9
Let me help you.
If you have a plan for js-bidings, please provide it to me.
I'll create some PR for it.

Current situation

js typings was fixed by my past PR and old test specs are also updated to the latest in #242
So publishing new npm package is almost ready to go.

What's remaining

• Review and merge this PullRequest Reconstruct js test #242
• Update version value in https://github.com/Chia-Network/bls-signatures/blob/main/js-bindings/package.json#L3
  to 0.2.6.
• Build js source

  cd /path/to/repository/root
  ./js_build.sh

• Publish to npm registry

  cd js_build/js-bindings
  npm whoami # Confirm you are logged in as the appropriate npm user
  npm publish  # Publish package to npm registry. Be careful, canceling the package is very difficult.

[tiantianlikeu]

@hoffmang9 hello ，when can release bls-sign for npm?

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.'

[ChiaMineJP]

This ticket should not be closed.

[ChiaMineJP]

Oh god! You haven't forgot this issue!

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[ChiaMineJP]

Bump. I still want to contribute to this project, if you allow me.

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[taro199]

Don't go stale

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.'

[github-actions]

'This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[hoffmang9]

And finally addressed by #335