Earlier this year, CMTA and Nethermind published a case study on applying AuditAgent to the CMTAT codebase ahead of the v3.1.0 release. That effort focused on security, including automated pre-audit analysis, transparent reporting, and findings addressed before release.

CMTAT-FIX builds on that collaboration by extending CMTAT itself. It is an open-source, modular engine that enables CMTAT tokens to commit FIX protocol metadata on-chain, with cryptographic field-level verification via Merkle proofs, without the contract ever parsing FIX messages. Nethermind developed the engine in collaboration with CMTA and Taurus. This extends the collaboration beyond security tooling and into protocol infrastructure.

Why This Matters for Tokenized Securities

Traditional financial infrastructure relies on standardized instrument descriptors. Trading systems, custody platforms, and settlement infrastructure all use FIX to automatically identify and process securities.

Tokenized securities typically introduce custom smart contract fields for instrument data such as maturity date, coupon rate, or ISIN. These formats vary between implementations and are not directly readable by institutional systems.

As a result, each new token requires custom integration work. Counterparties must build adapters, manually map fields, and validate schemas before trading or settlement can occur. This process can take weeks per integration and must be repeated whenever contract structures change.

This introduces a scaling challenge. Each new token and each new counterparty introduces additional integration work, slowing time-to-market and increasing operational risk. Without standardized descriptors, tokenized securities remain siloed and difficult to integrate into existing financial infrastructure.

CMTAT-FIX addresses this by embedding standardized FIX descriptors directly at the token level. Instrument metadata can be verified on-chain and read by counterparties using existing FIX-compatible systems, reducing integration overhead and improving interoperability.

How It Works

A FIX message describing the instrument is converted into a canonical, deterministic form and committed on-chain as a Merkle root alongside its SBE (Simple Binary Encoding) form. The contract stores only the commitment and does not parse FIX directly. To verify a specific field, a caller supplies the field path, value, and a Merkle proof, and the contract checks the proof against the stored root. This enables field-level verification. To optimize gas usage, the SBE data is saved utilizing the SSTORE2 pattern.

The engine is modular, with each instance binding to a single token and integrating into CMTAT-compliant tokens through the FixDescriptorEngineModule.

Alongside the smart contracts, Nethermind led the engineering of a TypeScript SDK for interacting with the module. The SDK assists developers in calculating both the Merkle root and the SBE encoded data. Additionally, it facilitates the decoding of SBE data and the creation of proofs required for Merkle verification.

Built With CMTA and Taurus

CMTAT-FIX was developed by Nethermind in collaboration with CMTA and Taurus. 

The FIX integration adheres to the latest FIX technical standards, utilizing the specified SBE encoding. This ensures compatibility with existing traditional tooling, thereby facilitating easy integration into users' established workflows.

Jean-Philippe Aumasson, Chair of CMTA’s Tech Committee and Co-Founder and CSO at Taurus SA:

"CMTAT-FIX addresses a real gap in how tokenized securities interoperate with institutional systems. FIX is the language traditional finance uses to describe instruments, and having that on-chain in a verifiable form makes CMTAT more useful to the institutions that are actually deploying it. We're glad to have built this with Nethermind."

Tomasz Kurowski, Head of Enterprise Business at Nethermind:

"With CMTAT-FIX, we moved from reviewing the standard to extending it. CMTA members brought production requirements into the design process, which shaped what we built. The result is infrastructure that institutions can actually integrate with their existing systems, not a proof-of-concept. This is the direction we want to keep moving with CMTA and partners like Taurus."

Swapnil Raj, Head of Innovation at Nethermind:
“CMTAT-FIX bridges regulated token infrastructure and established market practice around instrument data. Working with CMTA and Taurus, we want issuers to have a straightforward way to make that information more transparent and interoperable for the ecosystem.”

Security Review

The CMTAT-FIX codebase was reviewed using Nethermind’s AuditAgent prior to publication, following the same approach used in the earlier CMTAT collaboration.

AuditAgent is an automated pre-audit analysis tool and not a substitute for a full manual security audit. The repository explicitly notes that a full audit has not yet been conducted.

Multiple automated scans were performed, and the findings were reviewed and assessed by the development team. Slither found no issues in scope. Aderyn's findings were assessed as false positives or valid-by-design.

The findings and developer responses are publicly available in the repository, supporting transparency and independent review.

Links

• CMTAT-FIX GitHub: https://github.com/CMTA/CMTAT-FIX

• FIX Descriptor Toolkit: https://github.com/NethermindEth/fix-descriptor

• FIX Descriptor Specification: https://erc-fix.com/spec

• Previous announcement: Using AI-assisted security analysis on the CMTAT

• AuditAgent: https://auditagent.nethermind.io/