Skip to main content
All documentation

Banking Blockchain

Prepare an institutional banking blockchain review across network identity, governance, transaction controls, gas funding, deployment, and commercial scope.

Workflow
  1. Set institutional requirementsMap policy owners, participants, assets, and operating responsibilities.
  2. Approve network identityValidate the Chain ID before creation; it cannot be changed later.
  3. Choose governanceDefine administrative, democratic, or hybrid approval authority.
  4. Review controls and feesSpecify freeze policy and the funding model for eligible operations.
  5. Confirm scopeUse technical documentation and formal commercial review.

Plan network identity and governance

Treat creation of an institutional network as a governed decision. Confirm its Chain ID and environment identity with the teams responsible for applications and integrations before the network is created: Chain ID is immutable afterward. The documented governance models are administrative, democratic, and hybrid. Decide who can propose, approve, and execute changes, including thresholds and any timelock, and document responsibility for validator operations and coordination of changes to settings that remain mutable.

  1. Validate the Chain ID and network identifiers with integration owners.
  2. Select an administrative, democratic, or hybrid governance model.
  3. Document proposal, approval, execution, and validator responsibilities.

Define banking controls

Translate institutional policy into explicit control requirements before implementation. The banking materials describe native-asset issuance and burning, account or address restrictions, partial balance holds, and controls that can pause applicable transfers, with release subject to authorised procedures. Distinguish a restriction on an address from a hold on a selected amount, and decide how customer identity records map to network addresses without putting private customer data on-chain merely to express that relationship. Agree roles, approvals, and audit needs.

  1. Name the policy owner and the cases each control should cover.
  2. Specify approval and release procedures for restrictions or pauses.
  3. Review address mapping and privacy boundaries with the institution.

Choose fee and Paymaster policy

A Paymaster can change how an eligible smart-account operation is funded from the user’s perspective; it does not remove network gas. The configured policy determines which operations qualify and whether an approved settlement token or sponsor funds them. The responsible institution must plan the applicable native EntryPoint deposit and stake, funding ownership, monitoring, permitted use, and replenishment. Keep protocol gas, customer-facing fees, sponsorship budgets, implementation charges, and network reserves separate in operational and financial planning.

  1. Identify eligible operations, accounts, and approved settlement assets.
  2. Assign funding, monitoring, replenishment, and exception responsibilities.
  3. Reconcile protocol gas separately from customer fees and sponsorship.

Review technical and commercial scope

Use the banking documentation pages for governance, freeze controls, Paymaster, APIs, security, deployment, pricing, and pilot topics. The technical overview is a broader reference; it should be read alongside the institution’s own architecture and policy decisions. Confirm deployment boundaries, integration interfaces, support responsibilities, and commercial commitments in the written scope. A pilot is an evaluation, not a production commitment. Avoid treating general product descriptions as an institution-specific service level, supported integration, or customer deployment claim.

  1. Read the relevant banking documentation topics and technical overview.
  2. List architecture, security, integration, and operational questions for review.
  3. Confirm commitments and exclusions in the formal written agreement.

Frequently asked questions

Can the Chain ID be changed after network creation?

No. Chain ID is immutable after creation. Validate it with application and integration owners before launch.

Which governance models are documented?

Administrative, democratic, and hybrid models. The institution must define the actual authority, thresholds, and execution process.

Does a Paymaster make transactions use no gas?

No. Network gas still exists. A Paymaster changes funding for eligible operations under the configured policy, and the responsible party must fund it.

Can the banking guide replace technical review?

No. It is planning information. Confirm interfaces, controls, deployment, and commercial responsibilities for the institution’s specific scope.

Related pages