Skip to content
Flowesome
Flowesome · FxChain

Every financial action needs a clear mandate.

Proof before power.

Flowesome is building FxChain, a native blockchain protocol for financial workflows, and the applications designed to use it. Its design makes explicit who may act, what was observed and which evidence is needed before acting again.

Defined local profiles - implemented under internal review.No public network active.Current status and evidence
One operation, three questions

Keep authority, effects and evidence connected.

FxChain is designed to make these distinctions explicit across an operation, including when it is interrupted. Each implemented capability has its own scope and evidence.

Before: who may act?

A key or a spending ceiling does not describe the whole mandate. The recipient, asset, fees, purpose and expiry also matter before an action is admitted.

During: what was observed?

An intention, an emitted request and an observed result are different facts. A missing response leaves an outcome unknown; it does not establish failure.

After: what justifies the next action?

An interruption can leave obligations elsewhere. Recovery must account for those obligations, the evidence still missing and the authority needed to continue.

An FxWallet authorization, illustrated

Planned

In the proposed wallet experience, a user could authorize an agent to transfer 40 units of a specified asset to one recipient. The review would also show fees, expiry and permitted actions. A different recipient would require a different authorization. The wallet would display the outcome or the reason for refusal, with its supporting evidence.

Illustrative product design; FxWallet is not available. Explore the intended experience.

A provider response that disappears and a system restored from backup raise related questions: which effects remain possible, what is still owed and who may resume? Explore workflow scenarios.

Capabilities and evidence

Start with a result you can examine.

These public explanations describe specific local work and the checks behind it. Each link identifies what was examined and what a reader can inspect.

Follow a bounded operation through interruptions

The 13 October local delivery records native service, numerical execution and composition profiles that preserve specified commitments, sources and staged synthetic payments.

Implemented locally; formal acceptance remains open.

Inspect the native profiles

Examine how a preserved result was reached

Bounded reconstruction compares observations from separate oracle and engine paths. Agreement, disagreement and refusal remain distinct outcomes.

Internal, scope-bound review; the public note explains its evidence and limits.

Read the reconstruction evidence

Understand a mandate on a concrete example

The supplier invoice review illustrates data admission, quarantine and a bounded action in an internal finance-operations lab.

Synthetic data; the FxChain core is illustrated, not executed.

Explore the internal example

Availability, verification and the next gates: What exists today.

Evaluation

Bring the workflow you already operate.

Access controls, approvals, idempotency and reconciliation already solve important problems. A useful evaluation asks what explicit authority, effects and evidence could add on the same cases.

Read and inspect now.

Follow the architecture and public scope notes. The developer reading path identifies the material currently accessible and the planned executable tools.

Discuss one bounded evaluation.

Identify one operation, one failure case, the observations available and the decision that becomes difficult. Compare the proposed approach with a competent existing procedure.

Choose deployment by the need.

Middleware integration, hybrid use and a future native network have different prerequisites. Local profiles are documented; a deployed integration or public network requires its own qualification.
Applications

One protocol, four product directions.

FxWallet is the proposed first user experience. Trading, payments and banking extend the vision; each product retains its own status and dependencies.

This presentation order is a product hypothesis, not an adopted release schedule. Shared settlement and integration capabilities follow their actual dependencies.

Latest engineering update

Engineering the foundations of financial continuity.

Deep design work by the FxChain engineering team connects evidence, obligations and resources into a systemic approach to financial continuity. The next step is complete implementation of the foundations required by M1, with real integration and end-to-end verification.

The native foundation

Explore how the parts fit together.

FxChain is the native protocol; Flowesome builds the applications and integration paths around it. This architecture map presents the vision and scoped statuses, rather than live network activity.

Read the dated development-line record

Evidence

sealed development line

Sealed
protocol eras sealed
7(D0-D6)
capability crossings
372
conformance checks
50/50green
public deployment claims
none
assurance programme
closed
snapshot
2026-09-28
verified
2026-09-28
reference
dev 11c96351 · assurance closure

A dated snapshot of the sealed development line at assurance closure. Not a live counter. what a crossing is.

Bring one workflow and one failure case.

Tell us which actions must remain controlled, what evidence you can observe and where recovery becomes difficult. We can discuss a bounded evaluation against your existing operating procedure.