Bloch Inc Explore the ecosystem
Institutional overviewPanama / incorporation in progress

Products + infrastructure + research

Products.Infrastructure.Long-term research.

Building a connected digital-asset ecosystem around deliberate access, visible execution and resilient protocol infrastructure.

Explore the portfolio Institutional overview
05Product
lines
01Infrastructure
foundation
01Managed research
organization
01

The company

One company. A connected ecosystem.

Product ownership, protocol infrastructure and research coordination — under one accountable structure.

Bloch Inc is being incorporated in Panama to connect product development with the infrastructure and research supporting the broader Bloch ecosystem.

Incorporation in progress

Corporate structure

Three complementary roles.

Clear separation of product ownership, infrastructure services and research management.

Company

Bloch Inc

Panama / incorporation in progress

Owned products

Product portfolio

  • DEX
  • Cross-Chain Aggregator
  • Wallet
  • Bloch L2
  • Bridge
Infrastructure

Bloch Protocol

  • Nodes & RPC
  • Explorer
  • Developer tools
Management

Postern Labs

  • Research
  • Engineering
  • Long-term capability

Product vision

Five products.
One connected journey.

Organized around the actions a user needs to take: access, discover, trade, execute and transfer.

01 Access

Public beta

Wallet

Start with a clear view of assets and deliberate, on-device authorization for the native Bloch experience.

Open Postern Wallet ↗
02 Discover

Deployment unverified

Aggregator

Compare candidate routes, costs and trust assumptions before coordinating a sequence of approvals.

Decision support / product mandate
03 Trade

Development preview

DEX

Access market interfaces, route comparison, pool discovery and liquidity mechanisms in a review-first workflow.

Explore Bloch DEX ↗
04 Execute

Integration in progress

Bloch L2

Build Solidity applications in the ECDSA-based L2 domain with an implemented EVM core and reproducible witness verification, toward settlement on Bloch L1.

Explore Bloch L2 ↗
05 Transfer

Qualification in progress

Bridge

Move between supported domains through explicit custody, identity, backing and finality verification gates.

Explore Bloch Bridge ↗

A complete public L2 node, Bloch L1 settlement and public bridge asset transfers are not enabled. DEX interfaces remain development software. Product status should be verified before use.

Bloch Protocol / infrastructure

The foundation
beneath the products.

Native network foundations, operational access and tools for the developer ecosystem.

Open Bloch Explorer ↗
FoundationBloch
ProtocolGenesis-4 / PoS
Nodes
RPC
Explorer
Tools
01

Native Layer 1

Genesis-4 proof of stake with ML-DSA-65 + Falcon-1024 at the native authorization boundary.

02

Nodes & validators

Node software, checkpoint procedures, operator guidance and validator admission tooling.

03

Data & visibility

RPC access, read-only observation and Bloch Explorer for blocks, transactions, epochs and validators.

04

Developer platform

Bloch L2 execution, local EVM and Solana DevKits, technical documentation and network adapter development.

Architectural principle

Interoperability is a boundary,
not a security shortcut.

Distinct authorization domains require distinct trust assumptions. A cross-chain path must be assessed end to end.

Bloch L1 / native domain

Post-quantum authorization

Native L1 fund movement retains the ML-DSA-65 + Falcon-1024 authorization boundary. ECDSA does not apply here.

PQ
Verification
boundary
Bloch L2 / EVM domain

ECDSA applies to L2 only

Bloch L2 accounts and contracts use ECDSA and retain separate security assumptions. Settlement on Bloch L1 remains in development.

EVM

ECDSA is confined to Bloch L2/EVM. A bridge, L2 account or wrapped asset does not automatically inherit Bloch L1's native post-quantum guarantees.

02

Who we are building for

Built for users.
Designed for an ecosystem.

Three audiences, with a shared need for clear, usable and observable infrastructure.

01

Individuals

Control & clarity

  • Readable transaction flows
  • Explicit approvals
  • Visible route assumptions
02

Builders

Tools & integration

  • Reusable interfaces
  • Technical documentation
  • A path from local testing
03

Ecosystem partners

Connection & reach

  • Product integrations
  • Liquidity collaboration
  • Distribution opportunities

Operating principles

Trust is an
operating discipline.

Evidence, accountability and clear boundaries should precede expansion.

  1. 01

    Secure development

    Testing, independent review and release gates before activation.

  2. 02

    Clear responsibilities

    Distinguish product ownership, infrastructure services and network control.

  3. 03

    Operational accountability

    Define responsible operators, incident response and change approval.

  4. 04

    Jurisdiction-aware launch

    Review legal and operational needs for each product and target market.

Directional priorities

Build readiness.
Then expand.

A milestone-led direction for corporate formation, infrastructure and product integration.

Now / 01

Foundation

  • Complete Panama incorporation
  • Verify infrastructure and release identities
  • Review custody, finality and security
Next / 02

Integration

  • Connect wallet-to-product journeys
  • Validate risk-aware route selection
  • Qualify eligible asset pathways
Forward / 03

Scale

  • Broaden reviewed integrations
  • Develop partner distribution
  • Strengthen infrastructure operations

Progress is measured by verified capability, not by a fixed launch-date promise.

Let's connect what comes next

Products.
Infrastructure.
Research.

01Research collaboration↗ 02Product integration↗ 03Institutional overview↓