IFMP is a sovereign, cryptographically hardened messaging layer for financial institutions. It does not settle, lend, guarantee, or intermediate. It provides the inviolable envelope — banks arrange their commercial relationship outside this protocol.
IFMP is an independent financial internet, designed to operate beyond the control of legacy clearinghouses and intermediaries. We do not participate in commercial disputes, currency settlement, or credit mediation.
- What IFMP Does: Provides a sovereign, cryptographically hardened layer for the transmission of irrefutable financial intent and proofs. It ensures that if a message is delivered, it is authentic, unaltered, and auditable.
- What IFMP Does NOT Do: It does not act as a clearinghouse, central bank, or correspondent bank. It does not provide pre-funding, liquidity, or mediation services. It explicitly excludes integration with legacy messaging systems (SWIFT, CIPS, SPFS, Fedwire, TARGET2 and all alternatives, networks and compensation systems that operate globally, regionally or digitally.).
- Commercial Non-Intervention: The protocol transports immutable proof of intent; it does not guarantee or perform the underlying settlement. All commercial terms (pre-funding, netting, credit lines) are the sole responsibility of the participating institutions.
- Independent Interoperability: We do not build bridges or adapters for legacy systems. Our protocol is an open-source standard; integration requires the implementation of the IFMP specification.
- Cryptographic Sovereignty: All signatures are verified by the distributed network of nodes, removing any reliance on central authorities or "trusted" third-party intermediaries.
- Hexagonal Integrity: The core domain logic is strictly decoupled from transport mechanisms, ensuring that the protocol's rules cannot be bypassed or compromised by infrastructure changes.
The documentation for this protocol is organized into three main areas to facilitate navigation for integrators, auditors, and engineers:
Core system requirements, network topology, and cryptographic invariants are fully documented:
- Protocol Specification:
specifications/PROTOCOL.md - Network Fabric:
specifications/NETWORK.md - Security & Cryptography:
specifications/CRYPTO.md
- System Design: Visual architectural diagrams detailing the event flows, node topology, and boundaries can be found in the
architecture/directory.
- Operator & Integration Guide: The user manual for commercial bank integrators and infrastructure operators is currently under active development and will be published in the
manuals/directory.
The IFMP ecosystem is strictly designed to isolate responsibilities across different architectural boundaries, ensuring that distinct actors interact only with their designated subset of the system. As formally defined in the system interactions are divided as follows:
- Central Bank Engineer: Operates at the infrastructural and governance level, managing the sovereign deployment topology, institutional registry invariants, and multi-signature quorums.
- Commercial Bank Integrator: Interacts exclusively through the protocol's outer hexagonal ports (API bindings), focusing on messaging translation, core banking integration, and failover procedures without exposing or altering the core domain.
- Security Auditor: Validates the protocol's internal integrity, focusing on cryptographic invariants, signature verification, and event immutability proofs within the Event Store.
For a detailed technical breakdown of how these roles are isolated at the code level and the rationale behind these boundaries, please review the Architectural Decision Records.
This protocol treats state as a derivative of immutable events. Full audit trails, temporal queries, and the ability to reconstruct system state are critical for the financial domain. The software architecture strictly enforces:
- Framework Agnosticism: The core domain logic is entirely decoupled from infrastructure and delivery mechanisms.
- Industrial-Grade Testing: Validation processes require successful passage of unit tests, architectural fitness functions, and deterministic domain scenarios.
Note for Recruiters
This project is an Applied Data Science and Distributed Systems solution, developed under industrial-grade engineering standards. It is intended for educational and research purposes, demonstrating the application of Domain-Driven Design, Hexagonal Architecture, and Event Sourcing in high-stakes financial environments.
Author: Johny Se
Contact: https://github.com/johnyse99
IFMP is licensed under the GNU Affero General Public License v3.0 (AGPLv3).
See COPYING for the full text. Documentation is licensed under CC-BY-SA 4.0.
This program is free software: you can redistribute it and/or modify it under
the terms of the GNU Affero General Public License as published by the Free
Software Foundation, either version 3 of the License, or (at your option) any
later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.