Skip to content
FxChain · Financial continuity

Financial continuity, made inspectable.

Follow a financial instruction through authority, execution, interruption and recovery. Discover what FxChain already establishes locally, how the architecture is advancing, and where external confirmation remains essential.

In developmentReading position · 8 November 2026The five-minute routeRead the dated milestone

01One operation, one continuous responsibility

Chapter 01

One operation, one continuous responsibility

A financial operation has a life beyond the request that starts it. Someone authorises it. A system admits it, performs an effect and retains evidence. A caller may receive the answer, lose it or return later. The operation can also leave duties that survive its immediate result.

FxChain is a native blockchain protocol project. Its financial-continuity work connects those responsibilities at the foundation: what may happen, what happened, which resources remain committed and what can be justified next. The aim is useful progress with an intelligible financial history.

The local work gives that direction concrete behaviour. Its value is not that every event becomes a green status. It is that a committed effect, an explicit refusal and a fact still awaiting evidence can each keep their own meaning.

A result is more useful when its authority and its remaining responsibilities travel with it.

That relationship is the common thread from the original instruction to recovery and reconciliation.

Chapter 02

What has become concrete

The progress is a set of specific engineering results, not a blanket release claim. These capability passports give each result a useful meaning, its own verification environment and the evidence needed for its next gate.

Implemented locally

Keep authority attached to the operation

A missing response does not create a fresh spending allowance.

Observed result
The local reservation binds the amount, unit, recipient, request and attempt. Unresolved authority stays represented when a receipt is missing.
Environment
Local reservation and signed-transfer fixtures using synthetic units.
Verification
Retained source-bound fixture and conformance evidence, explained in the dated engineering record.
Scope
This is local spending authority, not a bank balance or proof that a bank has placed a hold.
Next gate
Observe the complete operation on its identified integrated source, with its admission and release evidence.
Implemented locally

Connect an authorised instruction to its effect

The financial result has an identity that can be followed and checked.

Observed result
A signed local transfer updates the sender, recipient and nonce under the declared native profile, preserving the relationship to the instruction.
Environment
A finite native transfer fixture with synthetic balances and a named recipient.
Verification
Local implementation and conformance fixture on their identified source.
Scope
The fixture is not an external payment, a general application runtime or a public financial service.
Next gate
Connect the same financial meaning to the applicable caller and receiver in the integrated acceptance scope.
Implemented locally

Recover the original result

An operator can resolve a lost reply without treating it as a new operation.

Observed result
The documented local continuity cases recover the committed result through an authorised lookup, without repeating the recorded effect.
Environment
Declared local continuity profiles and their exercised process and response interruptions.
Verification
The published native-delivery record distinguishes its current cases from earlier interruption evidence.
Scope
Each result keeps its own source and fault model. It does not establish duplicate prevention across an external payment rail.
Next gate
Retain the original operation and lookup rights through the complete witnessed scenario.
Implemented locally

Make a read answer for the right operation

A missing or mismatched reply is not presented as a successful observation.

Observed result
The local read client checks reply identity and direction, handles explicit refusal and retires an ambiguous connection.
Environment
The local transport and node paths examined by the October source-bound review.
Verification
Retained transport and node checks on the reviewed local candidate.
Scope
This validates the examined local read path, not a bank endpoint or every possible transport environment.
Next gate
Exercise the corresponding read behaviour with the real integrated caller and declared failure cases.
Implemented locally

Keep the cause visible through recovery

A recovered state can still explain the earlier failure and the work left to resolve.

Observed result
Focused journal checks retain the recorded first failure and qualify storage selection. Healthy native recovery cases have their own retained histories.
Environment
The tested local filesystems, injected cases and healthy input/output recovery conditions.
Verification
Separate dated journal checks and a local work register, retained with their source references.
Scope
Healthy reopen and injected faults do not establish emergency recovery or physical storage-fault tolerance.
Next gate
Qualify the required emergency branches and actual client replacement on the applicable source.
In development

Bring the foundations into one integrated account

Evidence, effects, resources and lasting duties can be assessed together.

Observed result
The identified November integration candidate has a recorded local receiving run and strict workspace lint result. Its reception and operating decisions remain distinct.
Environment
The identified local source and configuration recorded in the dated integration news.
Verification
A dated receiving ledger with its complete result population and ignored tests; underlying records are retained privately.
Scope
Later source-only contributions and detached overlays do not inherit this validation. This is not closure of the whole architecture programme.
Next gate
Complete the applicable source-bound execution, witness and reception requirements for the integrated milestone.

Chapter 03

Authority before action

An operation starts with an authority to do something specific. The recipient, amount, unit and applicable request belong to that authority. A repeated request is not automatically a renewed mandate.

The local reservation work preserves this relationship while a receipt is missing. That gives the caller a better account of the authority still committed and prevents a timeout from being interpreted as a fresh allowance.

In a bank-facing design, the same discipline would distinguish authority reserved locally from funds actually held by an institution. Those are separate records, established by different actors.

Chapter 04

When the reply disappears

The reply can disappear after the effect has already been committed. In the documented local continuity cases, an authorised lookup recovers the original result rather than performing the recorded effect again. Earlier interruption evidence keeps its own source; it is not silently counted as a rerun on a later candidate.

This changes the useful question from “Should I send it again?” to “What can I establish about the operation I already sent?” A separate right to inspect the receipt also matters: removing a reader's disclosure permission does not undo the original effect.

  1. Step 1

    Retain the original instruction

    Keep its identity, authorised scope and unresolved commitment. The lost response is part of its history, not a reason to create a replacement financial instruction.

  2. Step 2

    Ask about that same operation

    Use an authorised lookup against the original reference. Check who supplied the answer, which operation it concerns and what fact it actually establishes.

  3. Step 3

    Continue on the evidence available

    Recover the original result where the qualified profile supports it. Keep an external outcome open when the corresponding bank observation has not arrived.

Chapter 05

Where the bank's evidence begins

A native receipt can establish the outcome of the native operation within its declared profile. It cannot, on its own, establish that an external bank accepted an instruction or that a supplier was credited. An integration has to name who can attest to each fact.

A Japanese notice gives a concrete reason to preserve this distinction. Following the shared shinkin-system incident on 6 November 2026, the joint announcement recorded restoration at 19:05 JST. Kurayoshi Shinkin Bank separately announced that delayed transfers to other financial institutions would be credited on the next business day, 9 November. Restoring access and establishing one payment's outcome answer different questions.

Native responsibility

  1. Mandate: who may do what.
  2. Local effect: what was committed.
  3. Evidence: what can be recovered.

External institution

Bank acceptance and beneficiary credit are separate facts supplied by the institution able to establish each one.

Read authority, unresolved exposure and evidence together before the next action.

Architectural reading map, not a live bank integration. A recoverable native receipt and a beneficiary credit answer different questions. The missing external fact remains visible until appropriate evidence arrives.

The proposed payment walkthrough therefore separates the native instruction from bank acceptance and beneficiary credit. Its banks and payment events are simulated. A missing, stale or contradictory observation keeps the corresponding fact open and identifies the evidence needed for reconciliation.

Public context: joint notice, 6 November; Kurayoshi customer notice, 6 November. The latter is an announced credit date, not independent confirmation that any particular beneficiary was paid.

Chapter 06

Quality you can examine

The November receiving record identifies a particular local integration candidate and configuration. Its validation and strict workspace lint are evidence about that candidate. They give the engineering work an inspectable basis without substituting for the applicable execution, witness and reception decisions.

Useful quality evidence says what was exercised, what was observed and what remained unexamined. Healthy reopen, an injected failure and a physical storage interruption are different tests. A later detached change needs its own qualification; it does not inherit the result of an earlier run.

The dated news keeps the complete result population, including ignored tests, alongside the source reference. This permanent chapter explains the capabilities and their boundaries rather than turning a historical test count into a live quality meter.

A result worth inspecting carries

  • The date and identified source.
  • The environment and exercised fault.
  • The observed outcome and retained record.
  • The open question and next acceptance condition.
Examine the dated validation record

Underlying engineering exhibits remain private. The historical assurance closure and native delivery keep their original dates and meanings; this chapter does not revise them.

Chapter 07

What this enables for applications

The capabilities are shared foundations for Flowesome applications, powered by FxChain. Their usefulness depends on the complete workflow, its users and the external systems involved. Each application keeps its own product identity and availability gate.

FxWallet

Planned

A payer could approve a recipient, amount, asset and expiry, then inspect the same operation after an interrupted reply. The local signing mechanism supports the design; the public wallet experience has its own availability gate.

FxTrade

Planned

A trading workflow could keep execution evidence and the external cash leg distinct. An executed trade does not make an unobserved payment leg complete.

FxPay

Planned

A merchant or payment operator could distinguish the original instruction, provider acceptance and beneficiary credit, while retaining the authority and duties attached to unresolved work.

FxBank

Research

Programmable banking research considers how account authority, commitments and evidence could support a coherent operational view. It remains a product direction, not a constituted bank or a banking licence.

For treasury and finance operations, the same direction is a view across commitments, evidence and outstanding duties. That is an application opportunity to specify, not a new service made available by this milestone.

Chapter 08

The next demonstrable milestone

The next useful demonstration follows one authorised operation through its actual dependencies. It retains the original instruction, the effect or refusal, an interrupted response, the recovery path and any later evidence. A separate reviewer should be able to reconstruct the decision from the same record.

The public payment-recovery walkthrough makes that question approachable through a fictional scenario. A witnessed integration run has a different purpose: demonstrate the applicable native behaviour on its identified source and preserve the reception evidence required for that milestone.

An institutional evaluation would then require an agreed workflow, named operator, authorised environment and a fair comparison with established recovery procedures. A bank supplies the authoritative external observations. Any public operational claim follows the measured result and permission to disclose it.

The next milestone is a decision another person can reconstruct.

Same instruction, same evidence, same justified next action, with the remaining responsibility visible.

Bring one workflow to examine.

Start with a useful operation, an interruption and the evidence your team can supply. Define the next justified decision together.