Skip to content

Instantly share code, notes, and snippets.

@christroutner

christroutner/blockbook-vs-insight.md

Last active February 26, 2020 11:01
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save christroutner/ff1af0ee4f5a207571fe7857acdc916e to your computer and use it in GitHub Desktop.
Save christroutner/ff1af0ee4f5a207571fe7857acdc916e to your computer and use it in GitHub Desktop.
Download ZIP
BlockBook vs Insight API in rest.bitcoin.com
Raw
blockbook-vs-insight.md

Overview

This document is an analysis of the endpoints in rest.bitcoin.com that rely on Insight API. Each endpoint is analyized with respect to replacing the use of Insight API.

My take-away from this analysis is that BlockBook API is very close to a drop-in replacement for Insight API. If there is ever any risk of Insight API ending support or getting forked off the network, BlockBook API would be an adaquate replacement. If the BITBOX team wants to be proactive, we could create additional endpoints and slowly begin to phase out Insight API, giving our users time to migrate.

There are approximately 5 endpoints on rest.bitcoin.com that call Insight API. Here is how they compare with BlockBook API:

address/details/:address

address/utxos/:address

address/transactions/:address

  • Example rest.bitcoin.com call
  • Endpoint is missing in Blockbook. But same output can be achieved by getting transactions list from address/details then iteratively calling rawTransaction/getRawTransaction/:txid on each TXID returned.

transaction/details/:txid

block/detailsByHash/:hash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment