Skip to content
Network

Architecture

Three layers with strict boundaries: Flowesome products on top, the FxChain protocol at the base, deployments only when earned. Below, the anatomy of the protocol itself.

Protocol anatomy

The organs of FxChain

Each organ owns one responsibility inside the protocol. Dedicated module pages ship in a later phase.

FxCore

The constitutional kernel: native laws, admissibility, refused powers.

FxVM

Deterministic execution with declared access and observed receipts.

FxDAG

The ordering carrier: order-invariant windows, conflicts as economic objects.

FxIntent

Transactions that declare meaning before execution: action, constraints, expiry, proofs.

FxBlock

Capsules committing results together with denial roots.

FxState

State whose transitions carry evidence, not authority.

FxWire

The network fabric between deployments and surfaces.

The protocol foundations - including these organs - are implemented and sealed on the development line. Organ-by-organ specifications become public with the developer documentation phase, not before.
Design posture

Three commitments the architecture never trades away

Laws first

Native laws form the constitutional layer every mechanism must satisfy before it is allowed to exist.

Powers refused, and proven refused

The protocol can prove, at all times, what it cannot do. Refusals are first-class, sealed artifacts.

Prior art confronted, never hidden

Known results are reused as known results - never as identity. Divergences are stated, not implied.

From architecture to staged delivery.