@JonathanSilverblood
Release v1.1.0 of electrum-cash. This is a stability and quality improvement release with no new features, but it does convert the codebase to typescript and applies stronger linting. Also fixes a handful of small bugs and edgecases: - Trying to connect to an already established peer no longer returns undefined. - Clusters can no longer select inactive peers to send data to. - Clusters now validate connections before marking them as usable. - Subscribing to the same electrum method multiple times no longer produce multiple event listener. - Batch responses no longer breaks due to incorrect JSON.encode call.
5 comments
Can you link it, please.
- GIT: https://gitlab.com/GeneralProtocols/electrum-cash - NPM: https://www.npmjs.com/package/electrum-cash
This is an __AMAZING__ library .. I've been using it for a few months now with __[Insomnia](https://github.com/fountainhead-cash/insomnia)__ and it works flawlessly!! shout out to @rosco for the amazing refactoring job 👏👍
It's kindof nice, but it's not flawless. We fixed some bugs lately so it's better now, but still - if you try to do some long-running apps (start once, run for months, or years even), you will eventually find out that the electrum servers gets restarted and/or have network issues, but the library doesn't properly restore you back to a working state when those restarts/network issues are resolved. In the next version of the library, that too should be fixed so running it with a cluster of peers over very long period should be a rock-solid experience. Once that release is out, I plan to make an article serie showing how to do common things like looking up a balance, monitoring changes and such. If you have anything you'd want me to cover with those article series, lemme know :)
> you will eventually find out that the electrum servers gets restarted and/or have network issues, but the library doesn't properly restore you back to a working state when those restarts/network issues are resolved. __ahhhh, you're right!__ I did run into that .. was only connected to 1 server at one point and kept getting an error because it wasn't the 2 of the 3 required by the cluster (or at least that's what I suspected) .. i setup an automated check to run every 5mins and restart the PM2 process if it encountered an error, and since THEN Insomnia has been working flawlessly 🥰 __imo, having this cluster functionality available to webapps would be game-changing .. i don't even see that on Ethereum 😉__