Blockchain Primitive Protocol · Deployable · JSON Configured

The building block
for verifiable
digital records.

Mini Ledger produces the core outputs of a blockchain — immutable records, Merkle proofs, chain of custody — without the constraints. No coin. No node. No gas. A JSON file on your server.

Off-chain
Private by design
Coin-less
No speculation
Node-less
Your infrastructure
JSON
One config file
The Primitive
Blockchain outputs.
Without blockchain constraints.

A primitive is a foundational building block. Mini Ledger produces everything a blockchain produces — provability, immutability, chain of custody — but it runs on your server, configures from a JSON file, and requires no public infrastructure.

REF-01

What it produces

MemoEntries bundled into MemoBlocks, sealed with a Merkle Root, linked back to the previous block via genesis chain. Every record is immutable, every chain is provable, every proof is verifiable by any third party without accessing the underlying data.

REF-02

What it removes

No consensus mechanism. No gas fees. No native coin you didn't create. No public node network. No speculative asset. No regulatory burden from public token issuance. The complexity of blockchain infrastructure — gone. The utility — retained.

REF-03

What you compose

Chain any record type. Run sequential chains for audit trails. Run stateless blocks for individual credentials. Run multiple concurrent chains for different purposes. Roll up to a parent chain or anchor to any public blockchain. Your architecture, your choice.

REF-04

How it deploys

A single deployable binary. Configured by one JSON file. Two parameters are fixed — block trigger and naming. Everything else is yours. Stop it, reconfigure, restart — the last genesis block carries forward. The chain is unbroken.

What You Can Build
Six capabilities.
One deployment.

Everything Mini Ledger produces is a variant of the same primitive — a verifiable, tamper-proof record. What you name it and how you use it depends on your use case.

Financial

MemoLedger

The original use case. A tamper-proof chain of financial transactions or records. Every entry is immutable, every chain is verifiable, every block is linked to the one before it.

Transaction records with full chain of custody
Time-triggered or volume-triggered blocks
Merkle proof per block for audit verification
Compliance

Chain of Search

Every 132recon query and its result — Hit or Confirmed Negative — captured as a MemoEntry. The chain proves which checks were run, when, and what they returned. Regulatory-grade evidence trail.

Query + result captured per entry
MissProb=0 results preserved immutably
Satisfies MiCA Article 72/73 documentation requirements
AI Governance

Chain of Thought

Every step of an AI model's reasoning captured and sealed. Makes black-box AI systems transparent, auditable, and defensible. Each decision point is an immutable MemoEntry.

AI decision steps captured in sequence
Tamper-proof reasoning trail
Satisfies EU AI Act auditability requirements
Governance

Chain of Decision

Human compliance decisions captured alongside the data that drove them. Who approved, what they saw, when they decided. The complete governance trail for any regulated process.

Decision + context captured together
Approver identity and timestamp immutable
Compatible with four-eyes principle workflows
Finance

Financial Instruments

Issue bonds, notes, equity-like instruments, and commercial paper within your network. They can be traded and settled internally but cannot be sold outside your market. Contained by architecture, not by policy.

Issuance and transfer recorded immutably
Cannot leave the network by design
Potential MiCA exemption — not publicly transferable
Assets & Currency

Internal Currency & NFTs

Issue a coin, token, or NFT that operates within your network. Game assets, loyalty points, credentials, licences. Every transaction captured. Every ownership transfer proven. Nothing leaves unless you decide it does.

Internal economy — contained by design
NFT ownership history on-ledger
Game assets, credentials, loyalty — all provable
How It Works
From entry to proof.

Every record follows the same path — submitted, bundled, sealed, linked. The Merkle root is the proof. The chain link is the continuity. Toggle between process views.

Process view
Your System
Record origin
Mini Ledger
Captures & bundles
Block Engine
Seals & links
Proof
Verifiable by any party
REF-01
01
Submit a record
Any data — a transaction, a decision, a search result, an asset issuance. Your system sends it to Mini Ledger.
REF-02
02
MemoEntry created
Record becomes a timestamped MemoEntry and joins the pending block. Accumulates until the block trigger fires.
REF-03
03
Block sealed
Trigger fires — by time or transaction count. Block closes, Merkle root computed, linked to previous block via genesis chain.
Merkle Proof
Any party can verify any record without accessing the underlying data. Optionally anchored to XRPL or any public chain.
Spec
TriggerTime-based or transaction-based
Block linkGenesis chain — every block linked to previous
Proof typeMerkle root per block
AnchorOptional — XRPL or any chain
Input
Your system
MemoEntry
Record creation
MemoBlock
Accumulation
Merkle Engine
Sealing
Chain & Anchor
Continuity & proof
REF-01
01
Record submitted
Any data type — typed and validated against JSON config schema.
→ AES-256 encryption at rest
REF-02
02
MemoEntry created
Timestamp, hash, type, payload. Added to pending MemoBlock.
→ SHA-256 entry hash generated
REF-03
03
Block accumulates
Entries accumulate until trigger — time elapsed or N transactions reached.
→ Configurable in JSON
REF-04
04
Merkle root computed
Tree built from entry hashes. Root seals the block.
→ Pruned blocks resubmittable
Sealed Block
Linked to previous via genesis hash. Optional XRPL or multi-chain anchor.
→ Rollup to parent · Redundant nodes
Technical spec
EncryptionAES-256 at rest
ProofMerkle tree — lightweight verification
ResilienceStop · Reconfigure · Restart — chain unbroken
PruningPruned blocks resubmittable
Deployment Modes
Your architecture.
Your choice.

Mini Ledger is not opinionated about how you deploy it. Run one chain or many. Sequential or stateless. Roll up to a parent or anchor to a public chain. All from the same binary.

Sequential

Ordered chain

Blocks are created in sequence, each linked to the previous. The canonical mode for audit trails, MemoLedgers, Chain of Search, and any compliance record that requires ordered, unbroken history.

Genesis → Block 1 → Block 2 → Block N → ...
Stateless

Independent blocks

Each block is a standalone record with no dependency on previous blocks. Ideal for individual verifiable credentials, one-off NFT issuance, single decision captures, or any record that stands alone.

Block A · Block B · Block C · (no chain)
Chain A Chain B
Multi-chain

Concurrent chains

Run multiple independent chains simultaneously from one deployment. One for AML checks, one for AI decisions, one for NFT issuance. All running concurrently, all independent, all configured from one JSON file.

Chain A ∥ Chain B ∥ Chain C · same deployment
children parent
Rollup & Redundancy

Parent chains & backup nodes

Child chains roll up to a parent Mini Ledger instance. Branch ledgers aggregate to head office. Run multiple nodes of the same chain for redundancy. Lose one node — the others hold the chain. Anchor the root to XRPL or any public chain.

Child → Parent → XRPL · or · Node 1 ∥ Node 2 ∥ Node 3
Configuration
One JSON file.
Two fixed parameters.

Two things are fixed: how often the block triggers, and what you call it. Everything else — record schema, encryption, chain mode, anchor target, rollup destination — is yours to define.

Fixed parameters

Block trigger (time interval or transaction count) and chain name are the only constraints. They define the rhythm and identity of your deployment. Everything else is configurable.

Reconfigurable without breaking the chain

Stop the deployment, update the JSON, restart. The last genesis block is carried forward automatically. The chain remains unbroken. No migration, no data loss.

Pruning and resubmission

If a block is pruned, it can be resubmitted. The chain reconstructs correctly. Mini Ledger is designed for production environments where things occasionally go wrong.

mini-ledger.config.json Example config
// Two fixed parameters
"chain_name": "aml-chain-of-search",
"block_trigger": {
  "mode": "transaction", // or "time"
  "value": 50 // 50 entries per block
},

// Everything else is yours
"encryption": "AES-256",
"chain_mode": "sequential",
"anchor": {
  "enabled": true,
  "target": "xrpl"
},
"rollup": {
  "enabled": false,
  "parent_endpoint": ""
},
"redundancy": {
  "nodes": ["node-1", "node-2"]
},
"record_schema": {
  "type": "ChainOfSearch",
  "fields": ["query", "result", "miss_prob"]
},
"internal_currency": {
  "enabled": false,
  "symbol": "",
  "contained": true // cannot leave network
}
The Complete Stack
132recon completes it.
Together, nothing is missing.

Mini Ledger proves what happened. 132recon proves what didn't. Combined, you can prove the complete picture — every record that exists, and every record that definitively does not.

Mini Ledger

Creates the record

Every event, decision, transaction, and issuance captured as an immutable MemoEntry.

Issues the instrument

Financial instruments, NFTs, internal currency — issued and tracked within your contained network.

Contains the market

Internal economy — assets and instruments cannot leave your network by design, not by policy.

Seals with Merkle proof

Every block sealed with a cryptographic root. Verifiable by any third party without accessing the data.

Chains and rolls up

Sequential, stateless, or multi-chain. Roll up to parent chains. Anchor to XRPL or any public blockchain.

+
equals
The complete
information system
for trust.
132recon

Queries the record

Search any transaction, wallet, or amount range against the ingested record set at constant speed.

Returns a Hit

Record found — frequency, history, flags. Returned to your system immediately.

Returns a Confirmed Negative

MissProb=0. Definitively not in the record set. A mathematical proof of absence. No other tool does this.

Feeds the Chain of Search

Every query and result captured by Mini Ledger as a MemoEntry. The compliance trail is automatic.

Runs on your infrastructure

Same deployment model as Mini Ledger. Your server, your records, your data sovereignty.

Get in Touch
Build on the primitive.

Mini Ledger is deployable today. Every integration starts with a conversation about your use case and what you need to prove.

or
Open email client →

We respond within one business day · All conversations are confidential