Funding & Settlement

Funding & settlement.
Explain every credit and withdrawal.

Help treasury and operations teams follow a deposit from external-chain observation to an eligible Hybrid balance, and a redemption through its release records. Investigate delayed credits and withdrawals without piecing together disconnected status updates.

See how it works ↓Discuss your deployment

Network-gated · Check the exact operation and deployment.

Funding historyWhere did this balance come from?
  1. Deposit observed
  2. Eligibility checks
  3. Credit or release
Illustrative workflow · availability and access controls apply
A familiar challenge

A customer can see their deposit on an external chain, but their usable balance has not changed. Support needs an explanation.

A more useful way forward

Follow the observation, the eligibility decision, and the enabled issuance or redemption route without treating them as the same event.

See a practical example ↓
Why it matters

Give treasury a record it can reconcile.

For treasury, exchange, and payment operations teams.

Explain each balance

Trace an issued balance back to the funding observation and reserve decision behind it.

Separate the gates

A detected deposit, accepted reserve, and activated funding route are different states with different requirements.

Reconcile both ends

Follow issuance and redemption through their receipts instead of relying on a single status label.

Core capabilities

The capabilities behind the outcome.

Match these capabilities to your workflow. Enabled operations and access are confirmed during integration planning.

  • Deposit observations

    Identify the incoming event, funding route, and confirmation state before deciding whether to credit it.

  • Reserve and issuance checks

    Connect eligibility and reserve decisions to the balance issued under the enabled route.

  • Redemption lifecycle

    Review the burn, separate signing authorization, external release, and finality requirements.

  • Reconciliation records

    Trace funding and redemption receipts back to the original operation for exception review.

Inspect public records Review documented operations

Public records illustrate inspectable data; they are not customer results or confirmation of production activation.

How Funding & Settlement works

Observe first. Make value available only after checks.

  1. 01
    Observe the funding

    Record the external-chain event and its route. Detection starts the evidence trail; it is not finality or permission to issue a balance.

  2. 02
    Check and issue

    Apply the required ownership, confirmation, reserve, and route-activation checks before issuing spendable Hybrid value.

  3. 03
    Reconcile the exit

    For enabled redemptions, connect the Hybrid burn to separately authorized signing, external release, and final reconciliation.

A practical example · illustrative

An exchange reviews a customer deposit.

A deposit is visible on an external chain. The operations team needs to explain when it can become available inside its product.

Detected
Retain the external observation and identify the funding route.
Eligible
Confirm finality, reserve policy, and route readiness before crediting usable value.
Reconciled
Keep the balance decision tied to the original observation and subsequent receipts.
What the team takes away

A traceable crediting decision, with a clear distinction between seen, eligible, and issued.

Start with this guide

Trace funding readiness from observation to settlement

Inspect funding routes, deposits, and settlement intent evidence while keeping observation, credit availability, and permission to move funds distinct.

One useful first evaluation.

Follow the worked example, inspect the current contracts, and use the failure cases and checklist to review your own results.

Read the practical guide
Network-gated

Plan your first deployment.

Funding and redemption are enabled per route and network. A published architecture or a visible funding record does not activate deposits, withdrawals, or external-chain signing.

Before your first integration

  • Choose a funding route, asset, and network whose activation is confirmed.
  • Define crediting and redemption acceptance criteria with treasury.
  • Test delayed confirmations, rejected eligibility, and unresolved releases.
Review the integration Check the API contract
Open workspace
Questions before you build

Funding & Settlement, explained.

Is detecting a deposit enough to credit it?

No. Detection is evidence of an observation. The configured confirmation, ownership, reserve, and route policies determine eligibility for issuance.

Does a Hybrid balance automatically enable withdrawal?

No. Withdrawal also depends on the enabled redemption route, burn requirements, customer authority, signing availability, and external-chain finality.

What should we agree before starting a pilot?

Use the product-specific checklist above to define scope and acceptance tests. Ask the team to confirm the deployment environment, access, supported operations, integration responsibilities, support arrangements, and commercial terms. Availability labels are not a pricing quote or a service-level commitment.

Explore the technical architecture and walkthroughs

Optional deeper reading. Demonstrations are illustrative, not live operational status or a promise of activation. Use the availability guidance above and the current API contract for integration decisions.

WATCH-ONLY CANARY VERIFIEDRESERVE POLICY FAIL-CLOSEDBURN-BEFORE-RELEASE ENFORCEDDEVNET VALUE MOVEMENT DISABLED

THE FUNDING LIFECYCLE

Six boundaries.
One continuous claim.

Explore the route from an external-chain observation to a reconciled withdrawal. Each stage changes a different piece of state, creates its own evidence, and remains unable to silently inherit the authority of the next.

RESERVE-BACKED FUNDING ROUTEOne claim. One reserve. One continuous proof.
VALUELESS DEVNET
01 · OBSERVE

See the Layer‑1 deposit.

A watch-only source observer records the external-chain event without receiving spending authority.

CUSTOMER STATE
The deposit appears as detected—not yet spendable.
PUBLIC-SAFE EVIDENCE
Observer identity, chain, source commitment, sequence, confirmations, and observation signature.
FAIL-CLOSED RULE
Observation alone can never create a Hybrid balance.
EXTERNAL VALUE MOVEDFALSEBALANCE EFFECTDISABLEDPROOF CHAININTACT

RESERVE INTEGRITY

Never confuse visibility with authority.

Hybrid-Chain’s funding plane treats observers, attestors, ledger issuers, MPC signers, broadcasters, and finality watchers as separate jobs. The safest route is the one where no single job can invent both the asset and the evidence supporting it.

Follow a public funding proof
OBSERVED DEPOSIT≠SPENDABLE BALANCE

Detection creates evidence—not buying power.

FINALIZED RESERVE+POLICY CERTIFICATE

Only an admitted reserve claim can authorize issuance.

LAYER‑2 BURN→MPC RELEASE

The internal claim disappears before the external asset can leave.

PUBLIC PROOF CLASSES

See why every unit
entered and left.

The Explorer exposes commitments and verification state across the entire reserve lifecycle while customer identity, protected routing information, and private signing material remain outside the public record.

01 · SOURCE OBSERVATION

What the external rail reported.

Watch-only evidence records the chain event, source identity, sequence, and confirmation context without gaining control of the asset.

Inspect the evidence
02 · RESERVE ATTESTATION

Why value became eligible.

A signed policy result binds finality, ownership, currency, amount, route, and freshness to one collateral claim.

Inspect the evidence
03 · LEDGER RECEIPT

What became spendable.

Issuance and every later movement retain the exact reserve relationship, account sequence, authorization, and canonical balance effect.

Inspect the evidence
04 · REDEMPTION PROOF

Why the reserve could leave.

The public chain connects burn, threshold signing, broadcast, finality, and reconciliation without exposing secret key material.

Inspect the evidence

SETTLE WHERE THE WORK HAPPENS

Use Layer 1 for backing.
Use Hybrid for motion.

The architecture avoids forcing every payment, trade, reserve, or internal transfer through the latency and fee market of an external chain. Layer 1 establishes and releases the reserve; Hybrid handles the high-frequency operating history between those events.

01 · EXTERNAL RAILDeposit once

Observe, finalize, bind, and attest the reserve.

BLOCK-TIME FINALITY
→
02 · HYBRID SETTLEMENTTransact many times

Pay, trade, reserve, allocate, and reconcile between native public keys.

APPLICATION-SPEED FINALITY
→
03 · EXTERNAL RAILWithdraw when needed

Burn, threshold-sign, broadcast, confirm, and close the claim.

BLOCK-TIME FINALITY

WHAT IT ENABLES

One reserve model.
Many financial products.

Bridge observed Layer-1 collateral into fast Hybrid settlement. The same funding boundary can serve customers directly or sit beneath payments, markets, strategy products, and institutional operations.

01EXCHANGE FUNDING

Credit customer accounts only after chain observation, route ownership, finality, and reserve policy are independently satisfied.

02GLOBAL TRANSFERS

Move reserve-backed value between Hybrid public keys in seconds while preserving a clean external-chain exit path.

03STRATEGY POOLS

Reserve an exact, governed allocation for a strategy without giving the strategy operator custody of the underlying reserve.

04MERCHANT SETTLEMENT

Accept multiple funding rails, settle internally, and reconcile the customer payment to its reserve and delivery evidence.

05INSTITUTIONAL TREASURY

Separate deposit monitoring, reserve approval, balance issuance, signing, broadcast, and reconciliation across accountable roles.

06TRADING COLLATERAL

Make buying power fast enough for markets without allowing a detected deposit to masquerade as finalized collateral.

NETWORK READINESS

Prove the route before enabling the value.

Hybrid-Chain currently exercises watch-only observations, activation governance, fail-closed workers, funding evidence, and wallet signing health on devnet. Value-bearing routes remain separately disabled until independent regional infrastructure, audited chain adapters, reserve operations, and governance acceptance are complete.

PROVENVALUELESS DEVNET EVIDENCE

Observer identity, signed shadow observations, wallet activation, route policy, and public proof surfaces.

NEXTINDEPENDENT TESTNET OPERATIONS

Regional signers, validators, reserve operators, chain adapters, rotation drills, and adversarial reconciliation tests.

TARGETGOVERNED MAINNET FUNDING

Audited value routes, production reserve controls, monitored coverage, recovery procedures, and explicit activation ceremonies.

Start with one useful result

Make it work for your team.

Bring your workflow. We’ll help identify the scope, access, and acceptance checks for a practical pilot.

Discuss your deployment
Build the next part of your workflow

Connected products.

Start with Funding & Settlement. Review these adjacent capabilities when your requirements call for them.

Plan your integration Discuss a scoped pilot All products