iLocking Kft. — mission-critical systems engineering

Systems that must not fail.

Correctness at scale.

Three disciplines meet here. Business — twenty years inside banking, settlement and energy markets, where we learned what a process is actually worth. Cryptography — fifteen years of protocol design, up to schemes of our own invention. Engineering — distributed systems that scale linearly and run for decades. Most firms offer one of the three. Mission-critical systems need all of them, in the same room, at the same table.

25 yrs
the company
20 yrs
building critical software
15 yrs
cryptographic engineering
1st
blockchain-based core banking platform behind an EU-licensed e-money institution
1st
MiCA licence in an EU state, engineered by us

Proof, in one line each

  1. 01

    Core banking platform designed from a blank page for one of Central Europe's largest banking groups — from user management to the general ledger.

  2. 02

    Clearing & settlement specification for a national power exchange; balancing-energy tender optimization for the national grid operator, publishing to the European transparency platform.

  3. 03

    A factoring operation's agreement & calculation engine, derived from first principles — variable rates, variable instalments, solved for any unknown.

  4. 04

    A new-generation neo-core banking and account management system, designed and built by us: online general ledger, highly distributed, linearly scalable — an average node on 2 CPUs and 4 GB RAM books 10–15,000 transactions per second and serves 100,000 client accounts. It runs today beneath an EU member state's first MiCA licence.

  5. 05

    Published open research: NPVDKGRS — non-interactive, publicly verifiable distributed key generation over BLS12-381; post-quantum variant designed. — NPVDKGRS

  6. 06

    Our own protocols in the wild: the Pactena Protocol and Qashmore — private, offline-capable digital cash where fraud reveals itself. — Pactena Protocol · Qashmore

Boring, in the best sense.

Mission-critical systems should be dull: deterministic, auditable, reconciled to the cent and to the megawatt-hour. We spent our first decade making classical finance so — account management, securities settlement, pension fund accounting, power markets. We spent the most recent one proving the same discipline holds for the new world: a neo-core banking system with an online general ledger, distributed and linearly scalable; threshold key management where the complete private key never exists; digital asset custody that satisfied a MiCA licensing review. New technology is welcome here — after it passes the same audit as the old.

Real digitization hasn't started yet.

What passes for digitization today is paper processes projected onto screens — the same routing slips, the same waiting, now with login pages. Digital islands, stitched together by email. We build born-digital processes instead: the signature, the authorization, the transmission and the archive form one mathematically protected chain. Turnaround drops from days to seconds, every step leaves evidence — and the evidence works in both directions:

Manifesto

The data stays. The proof travels.

Sensitive records never leave their owner. What leaves is a proof — that the transaction happened, the deadline held, the rules were followed — verifiable by anyone, revealing nothing. Auditable systems without opening the envelope.

Our test for "mission-critical"

Three questions decide how we build:

  1. 01

    If it stops — who notices, and how fast?

  2. 02

    If it's wrong — who pays, and how much?

  3. 03

    If it's audited — what does the trail show?

If the answers frighten you, we should talk.

Have a system that must not fail?

Write to us