Bank-controlled native assets, not a detached token

Apply institutional issuance and transfer controls to the network’s primary asset. The banking interface is integrated with the canonical EVM balance ledger rather than maintaining an unrelated token balance.

Understand native asset configuration, institutional reserve ownership, governance, settlement assumptions, and the boundary between platform services and assets.

The native asset is the network’s primary asset and uses the canonical EVM balance ledger. That architecture matters operationally: the banking view is not an unrelated copy of token balances, and a balance used for asset accounting remains distinct from the technical gas required to execute network operations.

An institution chooses the asset’s purpose and its own issuance, reserve, and customer policies. The platform provides configuration and governed controls, not reserves or a promise of backing, redemption, custody, or financial treatment. Decide these boundaries explicitly before designing workflows around the asset.

One canonical balance ledger

Native asset balances are represented in the canonical EVM ledger, which is the source of network balance state. The banking interface presents administrative and policy-oriented views of that state; it does not maintain a second independent balance book that can silently diverge from the network’s authoritative record.

This ledger design should be distinguished from off-chain banking records and core banking systems. Those systems can retain customer identity, account relationships, product terms, and institution-specific accounting, while the network records applicable addresses, asset balances, and transactions. Mapping and reconciliation between records is an integration responsibility that must be designed and tested.

A balance change is reflected through canonical network state

Authorized actionA permitted issuance, burn, or transfer follows configured authority.
EVM executionThe network applies the transaction under its current rules.
Canonical balanceThe network ledger records the resulting native asset state.
Institutional reviewApproved interfaces and records support reconciliation and oversight.

The sequence is conceptual; it does not depict a live transaction or guarantee an outcome.

Issuance, burning, and authority

Authorized operators can administer supported issuance and burning actions within the configured roles and governance process. Before launch, define the purpose of each action, which role may propose it, what approvals are required, how execution is recorded, and who reviews the resulting supply and balances. A technical capability does not replace treasury or product policy.

The institution should test issuance and burn procedures with approved non-production cases, including rejected or incomplete approvals and subsequent reconciliation. Document how changes are communicated to application and operations teams. The actual permissions and approval thresholds depend on the deployed configuration; no universal administrator or unrestricted single-person authority should be assumed.

Reserves, gas, and fee accounting

The institution owns and manages any reserves associated with its programme. FusionPointAI supplies technology and agreed services, not reserve assets. Issuing a native asset does not itself establish backing, redemption rights, custody, a claim on external funds, or a particular legal characterization; those arrangements are institution-defined and must be handled through the institution’s own processes.

Native asset accounting and transaction gas are related to the network but remain different operational concerns. Gas funds execution at the protocol level, while a customer-facing fee policy may charge or sponsor an eligible operation separately. Finance and operations teams should reconcile asset movements, gas funding, customer charges, and service costs as distinct records.

Separate the asset programme from technical gas

Native asset programmeInstitution-defined issuance, supply policy, and reserve responsibility.
Canonical EVM balanceNetwork state records balances and applicable asset movements.

Technical gasNetwork execution requires protocol-level gas settlement.
Customer fee policyA separate policy may charge or sponsor eligible activity.

Two accounting concerns can interact operationally without becoming the same balance or obligation.

Configuration and launch decisions

Settle the asset name, symbol, intended use, administrative roles, supply controls, governance model, fee assumptions, and interfaces during configuration. Confirm which data belongs on the network and which remains in institutional systems. If external integrations are needed, assess data mapping, authentication, ownership, and test access rather than relying on an assumed prebuilt connector.

Network identity deserves particular care: Chain ID is immutable after creation. Other supported settings remain subject to governance and may require a coordinated software upgrade. Validate application assumptions, permissions, issuance and burn pathways, balance presentation, and reconciliation in the selected environment before production. Continue with the restriction-controls and Paymaster chapters for adjacent policy choices.

Govern issuance and supply

Authorized operators can manage the configured minting, burning, supply administration, and transaction restrictions through the banking control interfaces. Approval requirements and available actions follow network roles and governance policy.

Administrative actions produce records that institutions can inspect and reconcile. Network asset accounting and transaction gas remain distinct concerns even when the same native ledger is involved.

Keep reserve responsibilities clear

The institution owns and manages its reserves. FusionPointAI provides technology and the services agreed with the institution; it does not provide reserves.

Any relationship between an asset and external funds or assets is determined and managed by the institution under its own arrangements.

Approve configuration before launch

Confirm names, identifiers, governance, access controls, and integration assumptions through the institution’s approval process.

Chain ID cannot be changed after network creation. Supported mutable network settings remain governance-controlled; some approved changes require a coordinated upgrade and change procedure.

FAQ

Does creating a native asset mean it is backed by gold or another reserve?

No. No backing is implied. The institution owns and manages any reserves and determines its own arrangements.

Can network parameters change after launch?

Chain ID is immutable after creation. Other governed parameters may be changeable only through the applicable governance process and a coordinated upgrade.