libsecp256k1 JNI Deprecation Notice

[Jonas Nick]

bitcoinj optionally allows using the JNI bindings of libsecp256k1 [0] for

signature operations.

One month from now the libsecp256k1 project will remove the Java Native

Interface from the master branch.

The reason for this is that the JNI bindings would require way more work to

remain useful to Java developers but the maintainers and regular contributors of

libsecp are not very familiar with Java. There are properly maintained (but

unvetted) alternatives such as

https://github.com/ACINQ/secp256k1/tree/jni-embed/src/java

https://github.com/bitcoin-s/bitcoin-s/tree/master/secp256k1jni

You can find the discussions about this issue at

https://github.com/bitcoin-core/secp256k1/pull/682

[0] https://github.com/bitcoin-core/secp256k1

[Jonas Nick]

I hope this does not break any of your setups. In the unlikely case that it

does, you're probably better off with using above alternatives. If you have

concerns, please let me know.

[Andreas Schildbach]

Thanks for the notice. If no one objects, and if no one steps up to maintain these bindings in a useful form for JVM developers, I'll probably remove them for the next release.

[Marc Richard]

I load BTC wallets, Recover lost Bitcoins, & help with BITCOINS Investments. For more info text or send me a message via whatsApp - +1 661-410-6042.

On Wed, Jan 22, 2020 at 3:12 PM Andreas Schildbach <and...@schildbach.de> wrote:

Thanks for the notice. If no one objects, and if no one steps up to maintain these bindings in a useful form for JVM developers, I'll probably remove them for the next release.

--
You received this message because you are subscribed to the Google Groups "bitcoinj" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoinj+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoinj/019a30b6-c4f0-44d3-8f3b-8d9517053f03%40googlegroups.com.