Account constitution
enforced at consensus
Spending limit
a constitutional rule
Recovery path
not a support ticket
Permissions
consensus-enforced
Intent
declared meaning
A wallet that explains authority before it signs
FxWallet is the planned user surface for account constitutions, balances, permissions and transaction intent. Its job is to make power legible before the user grants it.
Typical flow
- 1The user selects an account and sees its active constitution.
- 2The wallet composes an FxIntent with constraints, expiry and required proofs.
- 3The user reviews the exact authority being requested before signing.
- 4FxChain admits or denies the claim; the wallet displays receipts and denial reasons.
- 5History remains explainable as evidence, not just as a list of app events.
Account constitution view
Shows the limits, signers, recovery paths and permissions that the protocol recognizes for an account.
Intent composer
Builds transactions as constrained FxIntent objects: action, expiry, proofs and authorization are visible before signing.
Evidence-based balances
Renders assets and history from provable state and receipts rather than from a trusted display layer alone.
Recovery workspace
Presents recovery as a protocol-governed path with thresholds, delays and proofs instead of a support-ticket promise.
A key is not a mandate
FxWallet is designed around the difference between holding a key and holding authority.
- Key held
- Yes. A key proves the ability to sign, and nothing about what may be signed.
- Mandate declared
- Scope, amount and time, stated before anything executes; an agent acts under it like any other holder.
- Within scope
- Checked at admissibility, not after the fact. Exhausted means the key still works and the authority is gone.
- Refused
- Sealed with its reason class; the detail stays with the claimant; the refusal is portable to an auditor.
- Moved without a mandate
- Never. No status, urgency or score widens a grant; only a new issuance does.
What is real, stated plainly
Proven today
- Nothing - no application, no beta, no waitlisted product
In development
- Nothing yet - design work is staged behind chain surfaces
Later gates
- Staged product design once chain account surfaces exist
- Prototype against a devnet when one activates
Not claimed
- No custody of any kind today
- No key management, no assets, no users
- No release date
Proven today, or practised on the lineIn development / qualifiedDirection: planned or researchLater gateNot claimed
The problem
Wallets today sit at two extremes: custodial trust boxes where someone else holds the power, or raw key managers where one mistake is unrecoverable.
In both cases the account rules - limits, recovery, permissions - are wallet-side conventions. The chain does not enforce them; the wallet just promises.
The Flowesome answer
FxWallet is designed as a window onto FxChain account constitutions: the account rules live in the protocol, enforced at consensus - not in the app.
The wallet composes intents (declared meaning, constraints, expiry) and shows you what the chain can prove. It is a surface over authority, never the authority itself.
Designed capabilities - nothing here is shipped
Account constitutions surfaced
Limits, permissions and recovery paths defined at protocol level, made visible and composable.
Intent composition
Transactions built as declared meaning: action, constraints, expiry, authorization - before execution.
Provable views
Balances and history rendered from evidence the chain can prove, not from an indexer you must trust.
Recovery by law
Recovery designed as a constitutional path of the account, not a support ticket.
Where it sits, and why that matters
FxWallet is the primary user surface of the network: the first place people meet FxChain accounts and assets.
It follows the chain strictly - a wallet cannot exist before the deployments and account surfaces it depends on.
Products
Foundation
FxChainSecurity and authority boundaries
What this product will not do, stated before what it will.
- FxWallet will not custody funds outside an explicit, regulated framework.
- It never precedes the chain: no wallet before the surfaces it depends on exist.
- Account authority stays consensus-enforced; the app never becomes the authority.
Gates, not dates
- 01
Design
PlannedProduct design over FxChain account constitutions.
- 02
Prototype on devnet
ReservedFirst working surface against a running deployment.
- 03
Public release
ReservedOnly behind proven custody and compliance boundaries.
Talk to us about FxWallet.
info@flowesome.com - we answer with what is provable today and what is staged for tomorrow.