The OpenForex Stack
The OpenForex Stack (OFS) describes the boundaries between monetary methodology, value computation, data provenance, and the systems that may use their results.
Publication status
Published by the OpenForex Society, the standard-setting core of the OpenForex Foundation, as part of its established standards service to the open standards community.
Version
0.2.0
Last Updated
2026-09-24
From principle to implementation
The foundational literature establishes the Third Value Neutrality Standard. The stack separates the engineering responsibilities needed to examine it. This separation allows a methodology to be reviewed independently from an application or hosting platform.
| Layer | Responsibility | Boundary |
|---|---|---|
| Monetary methodology | Define the reference unit and explain its valuation basis | Does not follow automatically from software |
| Oracle inputs | Identify, time, normalize, and preserve observations | An observation is not a promise of execution |
| TVX transformation | Describe the mathematical relationship between inputs and reference values | Use the applicable Society methodology and technical revision |
| OFS-Kernel | Apply a pinned method to validated inputs with reproducible results | Should not fetch changing inputs during replay |
| Application integration | Present results and handle user workflows | Must distinguish estimates from executable commitments |
| Settlement and custody | Fulfil obligations and maintain accountable balances | Separate operational systems, not included here |
Processing boundary
An application identifies the requested operation and relevant specification versions. An input process creates a time-bounded snapshot. The kernel validates that snapshot, executes the selected method, and returns either a result with provenance or an explicit failure. An application can then display or inspect the result under its own operating rules.
This describes a design boundary, not an implemented public endpoint. The API page documents the content API actually referenced by this package.
Keep value calculation and settlement separate
A reproducible number proves that a calculation can be repeated. It does not prove that funds exist, an asset can be redeemed, a counterparty will execute, or an obligation has settled. Implementations should retain that distinction in naming, records, and user interfaces.
Evidence expected from an implementation
- Exact kernel and method versions, including draft status.
- Input snapshot, observation times, units, and source identifiers.
- Numeric representation and rounding configuration.
- Result trace and failure outcomes for invalid inputs.
- Explicit list of layers implemented and layers outside scope.
Continue with the kernel reference, oracle design, and implementation registry.
Sources & citation
- Material type
- Project reference
- Publisher
- OpenForex Society
- Source version
- 0.2.0
- Source-stated update
OpenForex Society. “The OpenForex Stack.” Version 0.2.0. https://openforex.io/?page=seed-content%2Fofs%2Findex. Include your access date when citing.
Download the exact published MarkdownText fingerprint (SHA-256)
8e4614483f4478c2de4ef06b2783ab563a787c0089eac57a08c500eec98a9caeThis identifies the downloadable text, not an independent approval or a permanent archived edition.
Referenced material (4)
- API pageProject reference
- kernel referenceProject reference
- oracle designProject reference
- implementation registryProject reference
Standards, implementation references and worked calculations identify their sources and publication status. Read our sourcing and corrections policy.
Your first TVX integration
Step 1 of 4 in this reading path.
Continue View the complete path