pull down to refresh
184 sats \ 3 replies \ @ek 7h \ on: Stacker Saloon
How come the two most popular secp256k1 implementations in Golang (decred and go-ethereum) are from shitcoins, and LND uses one of them? 🧐
Mhhh, if I really cared, there would be a way to use libsecp256k1 in Golang ...
/cc @optimism
reply
Sorry, updated my comment after I did some research myself first before asking you, haha
With FFI, you mean this? Never did anything like that, might be a good time now.
According to my research, FFI can also mean "free from infection", haha
Edit: Oh, that's apparently literally what go-ethereum did:
Package secp256k1 wraps the bitcoin secp256k1 C library.
reply
With FFI, you mean [foreign function interface]?
YES!
Never did anything like that, might be a good time now.
It's also what all these Rust->Dart repos do; maybe that's a more useful skill these days than C->golang. Lotsa people poop on C and go these days and while optisaur is a C(++) coder that loves doing things in golang (as a python/java replacement), that's probably not a great skillset if you're not close to retirement, especially since all the rust people make promises that are just an
.unwrap() away from disaster. But then imagine having Claude or Gemini building you some code with malloc().that's apparently literally what go-ethereum did
I feel that as long as something is foss and it is maintained, we should not care too much about shitcoiners. If it were to force us into ethereum then it would be a different story of course.
reply