OpenViSTAI · Agents · Blockchain · Crypto
Menu
Explorers & Analytics

Blockapi

Blockapi is a Scala API for extracting Bitcoin and Ethereum data, constructing database views that can include external data, and analyzing those views with the database’s query language. It supports MongoDB, MySQL, PostgreSQL, and Apache Jena Fuseki.

Independent OpenViST project profile, based on linked sources.

Blockapi — OpenViST project profile in Explorers & Analytics.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Blockapi when you can operate a local blockchain client and database and want to turn Bitcoin or Ethereum data into a database-backed view for analysis.

Who it is for

  • Developers building database-backed analytics workflows for Bitcoin or Ethereum
  • Researchers or analysts who want to query extracted blockchain data using a database query language
  • Teams combining blockchain views with external data for analysis

Documented uses

  • Extract supported blockchain data into a database view.
  • Analyze a built view using the database's query language.
  • Construct views in MongoDB, MySQL, PostgreSQL, or Fuseki.
  • Include external data in a blockchain view for downstream analysis.
Before you choose

Requirements & limits

The project is published as a public GitHub repository under GPL-3.0. Its documented workflow uses local clients and databases.

  • The documented chain sources are Bitcoin and Ethereum, accessed through Bitcoin Core and Parity.
  • Database choice determines the view format and query environment: MongoDB, MySQL, PostgreSQL, or Fuseki.
  • The workflow requires a local copy of the target blockchain and RPC-enabled client; acquiring that copy may take several hours.
  • Java JDK 1.8 is a stated prerequisite. Command-line execution additionally requires SBT; IDE use is also documented.
  • The README names versions it tested, including Bitcoin Core 0.19.0.1, Parity 2.6.8, MongoDB 4.2, MySQL 5.7, PostgreSQL 11, and Fuseki 3.14.0; these do not guarantee compatibility with other versions.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up a local Blockapi analysis environment

Prepare a local blockchain client and database, then import the project into IntelliJ.

Before you start

  • Java JDK 1.8
  • A supported blockchain client: Bitcoin Core or Parity
  • A supported database: MongoDB, MySQL, PostgreSQL, or Apache Jena Fuseki
  • A local copy of the target blockchain; the README notes obtaining it may take several hours

Steps

  1. Run the client to obtain a local copy of the target blockchain.

  2. Enable the blockchain client's RPC calls. The README provides a Bitcoin Core example.

  3. Run a local database instance on its default port.

  4. Clone the Blockapi repository and import its build.sbt file into IntelliJ.

Expected outcome

The documented local components are prepared and the project is imported into IntelliJ.

Guide limitations

  • This is a setup guide; it does not establish that an analysis has run.
  • The README describes the Bitcoin Core RPC command specifically; it does not provide an equivalent command here for Parity.
  • Additional prerequisites may depend on the analysis. The README also lists a Bitcoinj build prerequisite for compiling the project.
Source-based practical guide

Run a repository analysis and query its database

Run one of the repository's documented analysis use cases and then query the database it builds.

Before you start

  • A prepared Blockapi project and the local blockchain client and database required for the chosen analysis
  • An analysis use case from the repository
  • An IDE, or SBT for command-line execution

Steps

  1. Choose a use case from the repository's Scala analyses.

  2. Run its file in an IDE, or from the project root use the documented form: sbt "runMain it.unica.blockchain.analyses.ClassName".

  3. After the analysis builds the database, use an available project query against it.

Expected outcome

The selected analysis is run according to the README workflow, with the resulting database available for querying.

Guide limitations

  • The command uses a placeholder class name that must correspond to a chosen analysis.
  • Further prerequisites can depend on the analysis.
  • The guide reflects repository instructions and is not an execution test.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
blockchain-unica/blockapi · Official homepage title · retained in its source language