What this map is for
The Principles for Financial Market Infrastructures (PFMI), issued by the Committee on Payments and Market Infrastructures (CPMI) and the International Organization of Securities Commissions (IOSCO) in April 2012, are the international standard for payment systems, central securities depositories, securities settlement systems, central counterparties and trade repositories [1].
A financial market infrastructure (FMI) shows how it meets the 24 principles in a public disclosure, written to the CPMI-IOSCO disclosure framework of December 2012 [2]. KXCO supplies software. The licensed institution that runs a payment or settlement system on that software is the FMI, and its disclosure is its own.
This map gives that institution, its overseer and its participants KXCO's half of the answer. For each principle it shows who carries it, what KXCO's software provides, and the status of each capability as KXCO's pages state it on 18 October 2026.
Where the 24 principles sit
| Carried by | Principles |
|---|---|
| KXCO software | 3: settlement finality, exchange-of-value settlement and communication standards |
| Shared | 10, with the institution and KXCO each carrying a part |
| Operating institution | 11, with KXCO's software supporting most of them |
Table 1. The 24 principles by who carries them. The three principle tables that follow give each one.
KXCO and the system it supplies
KXCO is the trading name of Knightsbridge Financial Ltd, registered in England and Wales, company number 15684975 [3]. KXCO is a software company. Licensed institutions that deploy its software hold the customer assets and the regulated relationships [4].
Four KXCO products make up a settlement system. KXCO Armature is the layer-one network and public record: four named validators run QBFT consensus with deterministic finality, and each attests every finalised block with an ML-DSA-87 key [5]. KXCO Sovereign is the software institutions use to hold, exchange and settle value under common rules, across FX, securities, futures, options, bonds, tokens, stablecoins and cash [4].
KXCO Guildhall runs the deal and the register's capital machinery, including capital tables, capital calls and bank reconciliation [6]. KXCO Round Table records each decision, and decisions stay with named people [7].
Legal and regulatory position
- Settlement finality. KXCO's counsel advises that a transfer in a final Armature block is legal settlement finality.
- Licences. The operating institution holds the licences its service needs.
- Custody. Customer assets stay with the licensed institution or the Member's own custodian [4].
- The network. A change to the validator set needs 3 of the 4 current validators to vote for it on chain [8].
Principles 1 to 8
| Principle | Carried by | What KXCO provides | Status |
|---|---|---|---|
| 1. Legal basis | Shared | KXCO's counsel advises that a transfer in a final Armature block is legal settlement finality. The institution's rules adopt that point, and its own counsel confirms the legal basis in each jurisdiction where it operates. | Counsel's advice given |
| 2. Governance | Shared | The institution governs its infrastructure. A change to Armature's validator set needs 3 of the 4 current validators to vote for it on chain, with no admin keys and no multisig [8], and the validator keys and their history are published [5]. | Live |
| 3. Framework for the comprehensive management of risks | Shared | The institution owns its risk framework. KXCO's software contributes the controls set out under Principles 8, 12, 16 and 17. | Live |
| 4. Credit risk | Operating institution | Armature extends no credit to anyone. A token transfer settles only against a balance that covers it, so no on-chain balance can fall below zero. | Live |
| 5. Collateral | Operating institution | The institution sets its collateral policy. Collateral held as tokens settles with the same finality as any other asset on Armature. | Institution's policy |
| 6. Margin | Operating institution | Applies to a central counterparty. The institution sets its margin system, and margin moves settle on Armature like any other transfer. | Institution's policy |
| 7. Liquidity risk | Operating institution | Each transfer settles gross and final in its block, so unsettled obligations do not build up on chain between cycles. The institution sets its liquidity arrangements. | Live |
| 8. Settlement finality | KXCO software | Deterministic finality in each block, with no forks and no reorgs [5] [8]. Blocks arrive every 2.0 seconds on average [9], measured at 2.0000 seconds over 59,211 blocks on 7 October 2026 [8]. Settlement is final intraday, in real time. | Live |
Principles 9 to 16
| Principle | Carried by | What KXCO provides | Status |
|---|---|---|---|
| 9. Money settlements | Shared | The cash leg settles in the money the institution chooses: central bank money where it has access, commercial bank money, or a tokenised deposit or stablecoin it holds [4]. ARMR is Armature's native gas asset [10], and on the path an institution writes through, KXCO pays the gas [8]. | Live |
| 10. Physical deliveries | Operating institution | Armature settles digital records. Where an asset is physical, the register records its custodian and provenance [8], and the institution's rules govern delivery. | Institution's rules |
| 11. Central securities depositories | Shared | The register holds ownership, with effective-dated capital tables that keep their full history [6], and applies the transfer rule before a unit moves [8]. Units exist only in dematerialised form, and no balance can fall below zero. | Live |
| 12. Exchange-of-value settlement systems | KXCO software | Both legs of a delivery-versus-payment or payment-versus-payment trade settle in one transaction, or neither does, which removes principal risk [10]. KXCO's reference contracts for both patterns are proposed. | Live. Reference contracts proposed |
| 13. Participant-default rules and procedures | Operating institution | The institution writes its default rules. The register applies each transfer rule the institution sets before a unit moves [8]. | Institution's rules |
| 14. Segregation and portability | Operating institution | Applies to a central counterparty. Every holder is a named party with its own positions in the register [8], so customer positions are held apart from the start. | Live |
| 15. General business risk | Operating institution | The institution holds its own capital against general business risk. Its supply agreement with KXCO sets the terms on which it uses the software. | Institution's own |
| 16. Custody and investment risks | Shared | Customer assets stay with the licensed institution or the Member's own custodian [4]. Institution keys are generated inside hardware security modules [11], and holders who use self-custody keep their keys on their own devices [8]. | Live |
Principles 17 to 24
| Principle | Carried by | What KXCO provides | Status |
|---|---|---|---|
| 17. Operational risk | Shared | Four validators under QBFT tolerate one faulty node, with three signing each block [8]. Each finalised block is attested with ML-DSA-87 [5]. KXCO's post-quantum cryptography passed 2,130 test cases on NIST's ACVTS demonstration server with zero failures [12], and its packages ship with signed build provenance [11]. The institution runs its own business continuity arrangements. | Live |
| 18. Access and participation requirements | Operating institution | The institution publishes its participation criteria. The register admits a participant only after the institution's KYC, and a position exists only for an admitted holder [8]. | Live |
| 19. Tiered participation arrangements | Operating institution | Every holder, whether a direct or an indirect participant, is a named party in the register, so the institution can identify its indirect participants [8]. | Live |
| 20. FMI links | Shared | Armature is EVM-compatible and speaks standard Ethereum JSON-RPC [13], and links to ISO 20022 systems follow KXCO's message mapping [14]. A reference gateway for links to external payment systems is proposed. | Live. Reference gateway proposed |
| 21. Efficiency and effectiveness | Shared | Blocks every 2.0 seconds on average [9], standard EVM tooling [10], and gas paid by KXCO on the institution's path [8]. The institution sets its own prices. | Live |
| 22. Communication procedures and standards | KXCO software | Standard Ethereum JSON-RPC, EIP-1474 [13], signatures under NIST FIPS 204 [15], and a published ISO 20022 message mapping [14]. | Live |
| 23. Disclosure of rules, key procedures and market data | Shared | The institution publishes its rules and its own disclosure. KXCO publishes its product status pages, its validator set and key history [5], its signing keys [3], the ISO 20022 mapping and this map. | Live |
| 24. Disclosure of market data by trade repositories | Operating institution | Applies to a trade repository. Armature keeps a signed, append-only history that a repository can read through the public explorer and RPC [16] [13]. | Live |
Using this map in a disclosure
An institution preparing its own PFMI disclosure can take the KXCO column of each principle as its technology provider's contribution, and write its own arrangements beside it.
Three principles rest on KXCO's software alone: settlement finality, exchange-of-value settlement and communication standards. For each of them, this map and the ISO 20022 message mapping give the evidence an overseer asks for [14].
The shared principles divide cleanly. The institution sets the rule, the policy or the governance, and KXCO's software applies it, records it and settles it. The institution's own principles remain its own, and KXCO's register supports most of them by naming every holder and dating every position.
Related documents
- ISO 20022 message mapping for KXCO Armature. Each Armature event mapped to its ISO 20022 message [14].
- The validator set and key history. Published on the network's own page [5].
- KXCO's signing keys. Published in the key file [3].
KXCO is a software company. Licensed institutions hold the assets and operate the regulated service. KXCO holds no financial licences, takes no custody of customer assets and is not a broker or placement agent.
Sources
- CPMI-IOSCO, Principles for financial market infrastructures, April 2012. bis.org/cpmi/publ/d101a.pdf
- CPMI-IOSCO, Principles for financial market infrastructures: disclosure framework and assessment methodology, 14 December 2012. bis.org/cpmi/publ/d106.htm
- KXCO post-quantum public key file, updated 11 October 2026. kxco.ai/.well-known/pq-keys.json
- KXCO Sovereign product page, status Live, read 18 October 2026. kxco.ai/sovereign/
- KXCO Armature validator page, read 18 October 2026. chain.kxco.ai/validators
- KXCO Guildhall product page, status Live, read 18 October 2026. kxco.ai/guildhall/
- KXCO Round Table product page, read 18 October 2026. kxco.ai/round-table/
- KXCO, Tokenising real-world assets on a post-quantum chain, developer blog, read 18 October 2026. kxco.ai/developers/blog/tokenising-real-world-assets-post-quantum-chain/
- KXCO Armature public statistics, read 18 October 2026: block 5,453,796, average block time 2.0 seconds. chain.kxco.ai/api/stats
- KXCO Armature smart contracts page: EVM-compatible, ERC-20, ERC-721 and ERC-1155, ARMR the native gas and settlement asset, read 18 October 2026. chain.kxco.ai/developers/contracts
- KXCO, Why use ML-DSA-87, developer blog, October 2026. kxco.ai/developers/blog/why-use-ml-dsa-87/
- KXCO developer blog on the NIST demonstration, September 2026: 2,130 test cases, zero failures, demonstration certificate A11025. kxco.ai/developers/blog/nist-graded-our-post-quantum-cryptography/
- KXCO Armature JSON-RPC reference: standard Ethereum JSON-RPC (EIP-1474) plus QBFT methods, read 18 October 2026. chain.kxco.ai/developers/rpc
- KXCO, ISO 20022 message mapping for KXCO Armature, version 1.0, 18 October 2026. kxco.ai/developers/blog/iso-20022-message-mapping-for-kxco-armature/
- NIST FIPS 204, Module-Lattice-Based Digital Signature Standard, August 2024. csrc.nist.gov/pubs/fips/204/final
- KXCO Armature product page, status Live, read 18 October 2026. kxco.ai/armature/