KalyRails Bank · Hyperledger Besu

Stop silent mass fraud. Before it happens.

A permissioned Hyperledger Besu blockchain that sits alongside your core banking system as invisible security infrastructure. Zero crypto. Zero customer-facing change. Mathematical proof that every withdrawal was authorized.

Talk to sales See how it works

One night. 3,421 fraudulent withdrawals. 1.14 billion CFA gone.

In a recent and widely reported incident at a major West African bank, attackers breached the centralized database, inherited internal access controls, and silently executed thousands of coordinated withdrawals across branches nationwide in a single overnight window. No real-time anomaly detection fired. The audit trail was retrospective — the losses were booked hours before anyone noticed.

1.14B
CFA embezzled

Direct losses in a single incident, attributed to coordinated cross-branch withdrawal fraud.

3,421
Fraudulent withdrawals

Executed simultaneously across multiple branches. None were blocked in real time.

1 night
Total attack duration

Linked to an international cybercriminal network with cross-border operations.

Traditional banking has single points of failure

Traditional architecture

  • ✕  Centralized database — one breach = total access
  • ✕  Internal access controls inherited by attackers
  • ✕  Transaction records can be silently altered
  • ✕  No real-time cross-branch anomaly visibility
  • ✕  Audit trails are retrospective, not preventive

KalyRails Bank architecture

  • ✓  Distributed ledger — no single point of compromise
  • ✓  Cryptographic signing required per transaction
  • ✓  Immutable records — tampering is mathematically impossible
  • ✓  Real-time network-wide transaction visibility
  • ✓  Smart contracts enforce rules automatically

A permissioned Hyperledger Besu network, built for banking

KalyRails Bank deploys a private Proof-of-Authority blockchain built on Hyperledger Besu — the same technology powering SWIFT's new shared settlement ledger and Nigeria's eNaira CBDC. It sits alongside your existing core banking system (Temenos, Flexcube, Finacle, or equivalent) and enforces withdrawal rules in code.

🔒

Permissioned access

Only authorized validator nodes can participate. Every transaction requires cryptographic signing — no anonymous access, no way to forge approvals from a database breach alone.

IBFT 2.0 / QBFT consensus

Proof-of-Authority consensus with ~2-second finality, low latency, and known validator identities. Purpose-built for regulated banking — not public crypto speculation.

🛡

Smart contract guardrails

On-chain withdrawal limits, velocity checks, multi-sig approval thresholds, and branch-level spending caps — enforced in code, impossible to bypass from the IT layer.

👁

Real-time monitoring

Every branch transaction is visible network-wide in real time. Anomaly patterns trigger automatic contract-level freezes — before the losses are booked, not after.

Drop-in security layer for your existing stack

Existing core banking system
Temenos  ·  Flexcube  ·  Finacle  ·  Customer databases  ·  ATM/POS  ·  SWIFT messaging
API & integration layer
JSON-RPC API  ·  Web3 middleware  ·  Event listeners  ·  Oracle feeds
Smart contract layer
Withdrawal limits  ·  Velocity controls  ·  Multi-sig auth  ·  Freeze/pause  ·  Audit logging
Hyperledger Besu — Proof of Authority Network (IBFT 2.0)
HQ Validator
Branch Region 1
Branch Region 2
Regulator Node
Disaster Recovery
Permissioned — only known validators can join

Every withdrawal, validated on-chain before funds move

STEP 01

Customer initiates withdrawal

Request enters through your existing ATM, POS, or mobile banking channel. No customer-facing changes required — the customer uses the same card, same app, same PIN.

STEP 02

API translates to on-chain transaction

The integration layer creates a blockchain transaction carrying the amount, branch ID, and customer parameters — cryptographically signed by your operational key.

STEP 03

Smart contract validation

On-chain rules check: daily limit not exceeded? Velocity normal? Multi-sig approval needed? Branch cap OK? If any check fails, the transaction is rejected before it reaches consensus.

STEP 04

PoA consensus & finality

Validator nodes (HQ + branch regions) confirm the transaction. 2/3 validator agreement required. Finalized in approximately 2 seconds.

STEP 05

Settlement & immutable audit trail

Funds release through core banking. A permanent, tamper-proof on-chain record is created — available to regulators, auditors, and compliance in real time.

THE RESULT

Silent mass fraud becomes mathematically impossible

An attacker with full database access still cannot forge cryptographic signatures. Smart contract velocity limits halt coordinated withdrawals before they compound. Real-time anomaly detection flags cross-branch patterns in seconds — not hours.

Zero cryptocurrency. Zero gas fees. Zero customer data on-chain.

This is not a crypto project. There is no token, no coin, no digital currency, and no transaction fees. The blockchain operates as invisible security infrastructure — like upgrading from a paper ledger to a tamper-proof one.

On-chain (Besu network)

  • ✓  Smart contract rules — limits, velocity, multi-sig, freeze logic
  • ✓  Cryptographic transaction approvals
  • ✓  Immutable audit log — who, what, when, which branch
  • ✓  Validator node signing keys

Off-chain (core banking)

  • ✓  Customer accounts & balances — stay in Temenos / Flexcube / Finacle
  • ✓  KYC data (names, IDs, addresses) — never written to chain
  • ✓  Fund settlement — through existing RTGS, correspondent, SWIFT
  • ✓  Customer interfaces — ATMs, mobile, POS unchanged

Full GDPR and data sovereignty compliance. Customer PII never touches the blockchain.

The blockchain client of choice for the world's largest financial institutions

Hyperledger Besu is not experimental technology. It is in production at central banks, global settlement networks, and tier-1 financial institutions on every continent.

SWIFT Shared Ledger (2026)

SWIFT's new blockchain-based settlement ledger is built on Hyperledger Besu. 40+ institutions collaborated on the design — including JP Morgan, HSBC, Deutsche Bank, and Bank of America. Live MVP goes into production in 2026.

Nigeria — eNaira CBDC

Africa's first CBDC. Retail payments have been running on Besu since October 2021 — proving production viability in West African regulatory and infrastructure contexts.

Brazil — DREX

The wholesale CBDC project from Brazil's Central Bank. Built on Hyperledger Besu as the settlement backbone.

Indonesia — Digital Rupiah

Project Garuda: 10+ commercial banks testing wholesale settlement on Besu. Led by Bank Indonesia.

Citi Token Services

Citi's tokenized deposit platform runs on private Ethereum / Besu infrastructure — moving real institutional balances between clients, 24/7.

DTCC, Santander, Accenture

Co-chair the Besu Financial Services Working Group — the governance body defining how Besu evolves for regulated financial institutions.

The right partner for African banking infrastructure

🌍

Proven in African banking

Nigeria's eNaira runs on Besu. We operate production Besu PoA networks today — not in a proof-of-concept, not in a lab, but serving real users in production.

🔑

Permissioned privacy (Tessera)

Private transaction groups keep sensitive data confidential between specific parties while maintaining full audit transparency for regulators and supervisors.

</>

Full EVM compatibility

Access to the largest smart-contract developer ecosystem on earth. All Solidity tooling, OpenZeppelin libraries, and Hardhat workflows work natively.

BCEAO regulatory alignment

Built-in permissioning, KYC/AML integration points, and granular access controls designed to meet central bank requirements across the WAEMU region.

Non-disruptive integration

Sits alongside your existing Temenos, Flexcube, or Finacle deployment. No rip-and-replace. Customers see no change. Staff workflows unchanged.

Full-stack operator

We run an L1 blockchain, a cross-chain bridge, a DEX, an on-chain DAO, and a stablecoin protocol in production. This is not consultancy — this is operational experience.

From kickoff to production in ~8 weeks

Our smart contracts — withdrawal limits, velocity checks, multi-sig, freeze/pause, audit logging — are pre-built, battle-tested, and ready to deploy. We're not writing them from scratch for every engagement. That's why our timeline is a fraction of what traditional enterprise blockchain projects quote.

PHASE 1 · WEEKS 1–2

Assessment & architecture

Infrastructure audit, network topology design, validator node placement, integration requirements mapping against your existing core banking stack. Pace depends primarily on your team's availability.

PHASE 2 · WEEK 3

Network deployment & integration

Besu PoA network goes live in 2–3 days (IBFT 2.0, permissioning, validators). Pre-built smart contracts are parameterized to your limits and policies. Remainder of the week covers API integration with core banking. Staging environment live by end of week.

PHASE 3 · WEEKS 4–5

Testing & security audit

Penetration testing, load testing across all branches, independent smart-contract audit, disaster recovery validation. No go-live without sign-off from your team and ours.

PHASE 4 · WEEKS 6–8

Phased rollout & training

Pilot branch deployment, staff training, monitoring dashboards, gradual rollout to all branches. 24/7 support from day one of pilot.

Let's secure your bank's future together

We'd welcome the opportunity to discuss how a private Hyperledger Besu deployment can protect your customers and your reputation — built by a team that runs this infrastructure in production every day.

Talk to sales