Cleber Lecheta
Connect on LinkedIn

JBLOCK · JAVA-BLOCKCHAIN-API · BENCHMARK V5

5M accounts. 150B moved. 418 seconds.

A Java blockchain API built for real financial load. Not a demo.

5.0M
accounts created
150B
volume transferred
75 ms
p50 per transfer (p95 175 ms)
~60k
sustained SQL rows/s

What it is

A private ledger and settlement plane on Quarkus and Java 25: ECDSA wallets, PostgreSQL as source of truth, and Kafka for node fan-out. Apache 2.0 license, with open capacity evidence, for engineers and fintech teams who need measured numbers rather than slides.

  • Java 25 and Quarkus LTS, with an optional GraalVM native image
  • PostgreSQL 17 as the ledger source of truth; Kafka for sync
  • Single root settlement writer, with idempotency and API keys
  • Apache 2.0 license. Issues and merge requests on GitLab only

Architecture in four steps

  1. 1
    Wallets and transactions

    Wallet creation, authenticated funding, and transfer pool over REST.

  2. 2
    Accept

    Accept writes pending state and reservations to Postgres; spends survive restarts.

  3. 3
    Mine / settle

    Only the root node batch-settles under lock; Micrometer metrics are exposed.

  4. 4
    Peers via Kafka

    Peer nodes sync via Kafka plus HTTP bootstrap from the root.

From baseline to V5

Baseline

1M accounts · 100k coins

V5

5,001,010 accounts · 150,000,000,000 volume · 418 s

5×accounts
1.5M×volume

Next volume stages

  • V10Not run
  • V50Not run
  • V100Not run

Same lab · same load

An operator-run lab comparison. It does not certify superiority in every scenario.

JBlock V5Fabric V5*
ResultPassed · 418 sAborted · ~22 min
Accounts5,001,010890,208 (~18%)
Volume150B0

* Hyperledger Fabric (lab 3.1.5) aborted populate at about 666 accounts/s; about 2.1 h projected for 5M. Own evidence, same reference hardware. JBlock is not a direct substitute for Fabric, Corda, or Besu.

What V5 does not prove

  • It does not certify a regulated digital bank or core banking readiness.
  • It does not prove multi-region cloud SLAs.
  • Numbers on the reference host (i7-1355U) do not generalize without a dedicated re-run.

How to contribute

Contributions under Apache 2.0. GitLab-only workflow (Issues and merge requests). Before an MR: Docker with Postgres + Kafka and `./mvnw test`.

  1. 1
    Read CONTRIBUTING.md in the repository
  2. 2
    Open an Issue or pick an existing one
  3. 3
    Keep MRs small, with tests for API/persistence changes

Frequently asked questions

Direct answers for people searching, citing, or contributing to JBlock.

What is JBlock?

JBlock (java-blockchain-api) is a Java/Quarkus blockchain API for a private ledger and settlement plane: ECDSA wallets, PostgreSQL as source of truth, and Kafka for node sync. It is open source under Apache 2.0.

Is it a public or private blockchain?

Private and permissioned. It is designed as an internal settlement plane, not as a public network like Bitcoin or Ethereum.

What does the V5 benchmark prove?

On the reference lab, stage V5 passed with 5,001,010 accounts present, 150 billion units moved in about 418 s, accept latency p50 of about 75 ms, and sustained populate near 60k SQL rows/s. JSON evidence is in the repository.

How does JBlock compare to Hyperledger Fabric?

It is not a direct substitute for Fabric. In a same-load V5 populate lab run, JBlock finished and Fabric aborted around 890k accounts. That is a single operational data point, not a universal ranking.

How do I run it locally?

Clone the GitLab repository, start Postgres and Kafka (docker compose), use Java 25, and follow the README (`./mvnw` / root and peer modes).

How do I contribute?

Issues and MRs on GitLab only, under Apache 2.0. Run tests with the Docker stack before opening a merge request. Details are in CONTRIBUTING.md.

Back to home