Hybrid Protocol

Shared rules for connected financial systems

Hybrid Protocol defines how applications can use shared rules, act within their permissions, and leave records that others can verify.

Public evidence

Follow a published TestNet transfer from its operation record to the validator certificate.

Published record

Internal transfer

FINALIZED
Network
Hybrid TestNet
Finalized
Operation ID
af6a9c7917823a8034cb7660d7de0f7a
Available proof
Validator certificate at height 798

Core reports finality for this transfer of non-value TestNet units. The record provides no evidence of Mainnet activity or external-chain settlement.

Shared ledger and authority

The intended design gives participating systems one canonical financial history. Each application uses the interfaces and permissions appropriate to its role.

Intended architecture
  1. Applications

    Wallets, business apps and service operators.

    Versioned request
  2. Scoped interfaces

    Check the request, permissions and required approvals.

    Authorized operation
  3. Shared ledger

    Record accepted changes under common rules.

    Published proof
  4. Public evidence

    Inspect disclosed records and linked proofs in Explorer.

One shared ledger
Under the intended protocol design, participating partner deployments use the same canonical financial ledger. A local replica verifies relevant history; it is not a separate balance that needs a bridge back to another copy.
Independent verification
Partners can maintain local replicas and check relevant finalized financial information rather than rely only on a remote application response. Verification is meaningful only for the information and evidence actually available.
Explicit authority
User authorization, business approvals, consensus validation and custody signing have different jobs. Identity, node admission or a favorable policy evaluation cannot substitute for the authority required to execute an operation.
Connected services
Versioned interfaces let organizations describe and connect compatible services. Finding a service does not establish trust, permission, a commercial agreement or availability; participants decide which providers and versions to use.
Shared rules, local flexibility
Organizations retain responsibility for their customers, business workflows, local compliance controls and service offerings. Local extensions must preserve common financial rules and the permissions of each operation.

How the ecosystem fits together

Applications
Where customers and organizations work: Banking, Exchange, Wallet, Cortex, Vault, ID and Explorer.
Shared infrastructure
Reusable policy, protected storage, distributed wallet authority, controlled execution and evidence interfaces supplied through Hybrid-Chain.
Protocol & network
Hybrid Protocol defines the intended common financial rules, canonical ledger, node roles and native network economics.
Federation
Hybrid Federation coordinates organizational participation, partner relationships and shared governance—not permission for every application operation.

Hybrid Vault is the protected workspace built on Quantum Data Vault infrastructure. Hybrid Wallet is the user experience and Native MPC Wallets provide distributed signing. Hybrid Verify checks selected evidence, Explorer publishes records, and Trust Center covers credentials and their lifecycle.

Explore infrastructure capabilities

Developer integration

Choose the operation and environment first. The published contract describes what it supports and the permissions it requires.

Scoped read

Discover token-import networks

Use the Chain API v2 with a bearer token scoped to wallets:read. The response lists supported import choices. Signing, deposits, and withdrawals have separate contracts and permissions.

Environment
Published Chain API · api.hybrid-chain.com
Operation
GET /api/v2/wallets/token-import-networks
Read the API v2 contract
Preview · version 0.1

Try HybridScript

Use the deterministic reference interpreter and examples to inspect inputs, capability requirements and execution results. Runtime access depends on the target deployment and documented execution-node path.

Mainnet user-contract execution is not activated by this design. Other compatible languages remain possible under the proposed service-interface model.

Explore HybridScript 0.1

Compatible service contracts can describe inputs, outputs, versions and authority requirements. SDKs and conforming implementations connect those contracts to a service. Agree the provider and permission scope before sending an operation.

Federation participation

Organizations can explore operating local infrastructure and offering compatible services. They retain responsibility for their operations, customers, and service agreements.

  1. Public evidence

    Observe & verify

    Inspect public financial information and available network evidence.

    A receipt check is not a full replay when the required inputs are unavailable.
  2. Admission required

    Connect & serve

    Operate an admitted partner node, local replica, scoped submissions and compatible services.

    Installation alone grants neither user spending authority nor access to private customer records.
  3. Separate approval

    Secure the network

    Participate only through separately governed consensus or custody roles.

    Partner nodes do not automatically become validators, receive custody shares or gain votes by adding nodes.

Prepare your organization, authorized representatives, and intended service scope for review. Federation membership, member access, and Chain node admission are separate decisions.

Choose your participation path

Banks & financial institutions

Connect controlled financial workflows with reviewable outcomes.

Chain supplies infrastructure and evidence; Hybrid Banking supplies the institutional application experience.

Can reviewers connect a decision, its authority and the exact financial outcome?

Explore financial operations
Fintech & payment operators

Reuse transaction infrastructure without losing operational control.

Connect permitted wallet, payment and reconciliation services with the operator's own customer experience.

Can the team resolve a pending operation without duplicating it?

Explore funding & settlement
Exchanges & digital-asset operators

Manage asset lifecycles and settlement responsibilities precisely.

Chain provides authority and evidence infrastructure; Exchange and Wallet retain their own product roles.

Can the team distinguish ownership, reserved authority and completed settlement?

Explore digital assets
Prospective Federation participants

Operate local infrastructure and participate in a wider service economy.

Partner-operated verification and relay infrastructure follows common protocol rules and separate admission.

Which services, operating responsibilities and verification coverage would the organization own?

Discuss participation with Ovryde
AI & automation developers

Connect useful context to bounded, accountable actions.

Hybrid ID establishes identity; Cortex provides the collaboration layer; Chain separates policy, approvals, execution and evidence.

Does access to context remain separate from authority to make a financial commitment?

Explore accountable agentic commerce

Ovryde coordinates enterprise commercialization, implementation and service delivery. For product or technical support, contact Hybrid Chain .

Protocol and participation questions
Planned

HYBRID Coin and network fees

HYBRID Coin is the planned native currency of Hybrid Protocol, designed to support network transaction fees, execution resources and the economic operation of shared infrastructure. It is distinct from independently issued digital assets and application-specific tokens.

Floating value and reference pricing

The intended model uses a floating market price, not a fiat peg. Protocol charges can follow a defined reference-currency pricing policy, with the corresponding HYBRID amount determined at the applicable quotation. The tariff reference and the currency used to pay are different concepts.

Eligible HYBRID payments

Eligible fee payment in HYBRID is intended to cost less than supported alternative methods. The policy does not require a minimum retained holding or holding duration. Holding-based tiers are deferred; exact discounts, eligible charges, tariffs and liquidity arrangements are not finalized.

How earned fees would be used

Properly earned and reconciled fees are initially intended to support infrastructure, security and development. Customer backing, refundable amounts and uncertain reservations are not earned revenue. Automatic coin burning is deferred, not an active or promised mechanism.

External network costs

Bitcoin, Ethereum, Solana and other external networks still require their own native transaction fees to be funded. HYBRID payment does not remove those costs or create conversion liquidity. Each supported payment route needs an authorized quotation and actual funding.

  1. Network operation
  2. Applicable fee quotation
  3. Authorized payment
  4. Earned protocol fee
  5. Network operations

Conceptual economic flow, not a payment interface. Authorized limits are not automatically charged in full. No issuance, staking, token sale, listing, return or guaranteed market value is announced here. Coin ownership grants no consensus, custody or regulatory privileges.