The repository has not been updated in over 2 years, including a pull request from that time with an unaddressed comment that indicates development was taken elsewhere. We initially wrote our test script to use this node-electrum-client npm package however it appears to be abandoned. We hit one issue where electrs wouldn't shut down as expected:Īfter those issues were patched, we then found ourselves having to work our way through electrum client challenges as we tuned our performance testing setup. Unfortunately we ran into several issues with electrs while testing it in our development environment. We don't find it worth performance testing since it's not designed to be highly performant. ![]() This is basically like Electrum Personal Server, but based upon Electrs and designed as an easily installed plugin for the Electrum Client. This is basically a stripped-down Electrum server that is only designed to be used by a single user it only accepts one connected client at a time. The devs stopped maintaining it in 2017 and handed the reins over to ElectrumX. The original Electrum server, it was the only implementation from 2012 to late 2016. With these new indexes, Bitcoin Core is no longer queried to serve user requests and is only polled periodically for new blocks and for syncing the mempool. Blockstream's fork builds extended indexes and database storage for improved performance under high load. It has become quite popular to run Electrs on Raspberry Pi-based nodes.Įlectrs generally acts as a proxy and forwards many queries to Bitcoin Core to actually serve data.īlockstream was looking to run an electrum server to power their public Esplora instance at, but Electrs was not indexing data well enough to serve enterprise level queries. Given the resource requirements of ElectrumX, this project was started specifically to be an efficient re-implementation of Electrum Server in Rust. ![]() Until 2019 it was the only option available for people to run. The second iteration of Electrum server implementations, this project was started in late 2016. The following report will walk you through the entire process we undertook. Casa engineers recently rewrote our back end infrastructure to use Electrum - in order to architect the best possible solution we needed to investigate how the different server implementations compared in terms of performance. As such, the next most mature protocol still standing is Electrum. ![]() However, since writing that article SPV has been deprecated for several reasons such as its poor privacy properties and DoS vulnerabilities.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |