Skip to content
Products

FxBank

Programmable finance connecting regulated rails.

FxBank

Research
Powered by FxChain
Product blueprint

A rail research blueprint that starts with what it is not

FxBank is the research surface for bank-rail semantics, health receipts, aliases, partner boundaries and sovereign fallback paths. It is not a bank; it is the discipline for proving a rail claim before anyone relies on it.

Typical flow

  1. 1A rail event is described as a claim, not as a marketing promise.
  2. 2The claim states who stands behind it and what evidence is required.
  3. 3FxChain judges the claim against rail health and protocol rules.
  4. 4Products may consume only the admitted state, not the external story.
  5. 5If evidence fails, the refusal is visible rather than hidden from users.

Rail claim model

Expresses external rail events as claims with issuer, scope, validity, revocation and evidence requirements.

Health receipts

Requires a dependency to keep proving it stands, so a rail cannot silently decay into fiction.

Alias sandbox

Tests account-like references in non-production conditions before any regulated promise exists.

Fallback map

Pairs regulated dependencies with explicit fallback paths and refusal conditions.

Truth vector

Authority that can only narrow

FxBank is a research programme about mandates, limits and duties - not a bank, and not a licence.

01
Mandate
A bounded capability with provenance and expiry; there are no roles and no ambient authority.
02
Limit
Narrowed by composition, never widened by a risk score; incomparable dimensions stay incomparable.
03
Hold
Eligibility can be paused by evidence; power is not restored except by a new issuance.
04
Duty
Every change of authority carries the duties it creates or breaches; liability is legal only with an instrument.
05
Licence
None held, none claimed. Regulated activity would come from partners, under their authority, never a fiction.
A design vector, not a service: it shows which facts this surface is built to keep apart. Its status is the claim scope below.
Claim scope

What is real, stated plainly

Proven today

  • Nothing - no service, no accounts, no license, no partners

In development

  • Nothing operational - research only

Later gates

  • Sandbox exploration with explicit aliases
  • Partnership conversations with regulated institutions

Not claimed

  • NOT a licensed bank - and not pretending to be
  • No deposits, no accounts, no banking services
  • No promise that banking services will ever exist

Proven today, or practised on the lineIn development / qualifiedDirection: planned or researchLater gateNot claimed

The problem

Connecting chains to banking is usually done with legal fictions: wrappers presented as deposits, "banking" products with no license behind them, rails claimed as integrated when they are screen-scraped.

The result is systemic: users believe they hold one thing while legally holding another.

The Flowesome answer

FxBank is a research program with one rule: no legal fiction. A rail claim must carry health receipts - proof the rail actually stands behind it - and a sovereign fallback must be proven before any dependency is accepted.

The path is staged: sandbox and aliases first, regulated partners next, own permissions only if and when they are earned. At every stage, what FxBank is not is stated as loudly as what it is.

Capabilities

Research directions - nothing here exists as a service

Rail claim vocabulary

Bank-rail semantics (ISO 20022-aligned) expressed as claims the protocol can judge.

Health receipts

A rail dependency must continuously prove it stands - no silent degradation into fiction.

Sovereign fallback

Every regulated dependency is paired with a proven fallback path that needs no permission.

Staged permissions

Alias and sandbox first; regulated partners next; own permissions only if earned.

FxBank is research. It holds no license, operates nothing, and offers nothing. This page describes the questions being worked on, bounded by the claim scope above.
Place in the network

Where it sits, and why that matters

FxBank sits where the network meets regulated finance - the most delicate boundary in the ecosystem, which is why it moves last and speaks most carefully.

It underpins future payment flows (FxPay) wherever regulated rails are involved.

Products

FxWalletFxTradeFxBankFxPayFxSentinelFxLabFxScan

Foundation

FxChain
Boundaries

Security and authority boundaries

What this product will not do, stated before what it will.

  • FxBank never describes itself as a bank while it is not one.
  • No wrapper will ever be presented as a deposit.
  • Regulated steps happen with regulated partners, in writing, or not at all.
  • The research can conclude "no" - and would say so publicly.
Staged roadmap

Gates, not dates

  1. 01

    Research

    Research

    Rail semantics, health receipts, fallback proofs.

  2. 02

    Sandbox with aliases

    Planned

    Non-production exploration, explicitly labeled.

  3. 03

    Regulated partners

    Reserved

    Real rails through licensed institutions.

  4. 04

    Own permissions

    Reserved

    Only if earned - never assumed.

Talk to us about FxBank.

info@flowesome.com - we answer with what is provable today and what is staged for tomorrow.