Beyond ElectrumX


The ElectrumX indexer

Wallet restoration

Why transaction history?

Affected users

Replacement approaches

  • It is not intended that this restoration index be a complete pushdata index. It would instead only index receipt and spending of standard type scripts. P2PK, P2PKH, P2MS and P2SH pre-Genesis. Unlike tip scanning which is mentioned later, this would also handle the 65 byte pushdata used for uncompressed public keys.

Transaction state

Replacement approaches

  • The user provides parameters with their filter, which might alter the default types of pushdata that their filter is checked against. Filters by default might only process 20 bytes (public key hash), 33 bytes (compressed public key with uncompressed being excluded intentionally) and 32 byte pushdata (SHA 256 hash) but a user could opt to pay more and process other sizes. They might just process 32 byte pushdata by default, and none of the other sizes.

Final thoughts

An Open API

Our indexer

Other indexers

Payment for usage





ElectrumSV developer

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

8 Amazing Most satisfying & Cleaning Vehicles you need to see

Understanding Ycash, Part 1: Why Ycash?


Allow total privacy warning last warning

Goldfinch protocol — a new type of credit


Understanding Blockchain in Mischiefs Cryptinity

Update to our Analysis and Valuation of Republic Protocol

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Roger Taylor

Roger Taylor

ElectrumSV developer

More from Medium

Celo Contract Subgraph Syncing Failure and Debugging

DLT Interoperability and More ⛓️#1 ⛓️

How does blockchain transparency drive value

Expanding Consensus