Four application directions, one native foundation
Flowesome is building toward a wallet, trading, payments and banking product family. FxWallet is the proposed first user entry. Each product has its own users, integrations and release requirements.
FxWallet
Wallet and personal financial app: accounts, assets, authorized actions.
Learn moreFxTrade
A planned trading platform for orders, execution and settlement evidence.
Learn moreFxPay
Payments platform and merchant services.
Learn moreFxBank
Programmable banking platform, under research. Not a bank.
Learn moreThe protocol and the supporting tools
FxChain is the native foundation. These additional tool directions keep their own scope and are not extra application releases in the proposed sequence.
FxSentinel
Intelligence and monitoring for the network.
FxLab
Experimentation environment for builders.
FxScan
Exploration, verification and audit interface. Documented scope: proposed local views of receipts and refusals, not a live-network explorer.
Applications use shared capabilities
A product needs its own useful journey and qualification, even when it reuses a protocol capability.
Products
FxWallet for accounts and assets, FxTrade for trading, FxPay for payments and merchant services, and FxBank for the banking-platform vision. Each remains a complete product direction with its own status.
FxChain capabilities
The native protocol supplies separately scoped mechanisms for authority, intents, deterministic local execution and evidence. Current implementations and target architecture remain distinct.
Shared, not owned
Transfer, settlement, receipts, reconciliation and recovery can support several products and external integrations. They can be built before the release of FxPay or FxBank when another use needs them.
- FxWallet is not signing: it uses signing, and shows the authority behind it.
- FxTrade is not an order format: it uses ordering, execution receipts and settlement facts.
- FxPay is not a payment rail: it uses routing, receipts and reconciliation.
Five words, used strictly
Implementation status, public availability and the nature of a review answer different questions.
Being designed and studied. No implementation is claimed.
Implemented and sealed on the development line - not publicly deployed.
Actively being built toward a public surface.
A proposed product or capability direction; availability follows its own implementation and release requirements.
Named and bounded, intentionally not started.
Bring one workflow and one failure case.
Discuss which product journey matters, what needs to remain controlled and which integrations it would require.