Explore the ecosystem
Products + services / September 2026Panama / incorporation in progress

Products + infrastructure + research

Products.Infrastructure.Long-term research.

What exists today. What comes next. An evidence-led roadmap for useful products in Latin America and global markets.

Explore the portfolio Products + roadmap PDF
05Current product
lines
04Delivery
gates
02Regional + global
tracks
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.

Current state / September 2026

What exists today.

Operating services and software previews are shown at their actual stage. A proposal is not a launch.

Operating / qualify release

Bloch L1 + Explorer

Genesis-4 proof of stake, node and RPC access, public chain exploration and historical transaction receipts.

View the network ↗
Public beta

Postern Wallet

Native Bloch authorization and browser extension. The Genesis-4 JavaScript exchange SDK is published separately.

Open the wallet ↗
Development preview

DEX + Aggregator

DEX interfaces and external EVM-chain pools are preview software. Aggregator route comparison exists in code; broad deployment is unverified.

Explore the DEX ↗
Integration / qualification

Bloch L2 + Bridge

Local execution and reference components exist. Complete public L2 settlement and public bridge asset transfers remain pending.

Explore L2 ↗

Proposed product portfolio

Turn verifiable trust
into useful workflows.

The next services follow a dependency order. Existing code is identified separately from a production-qualified service.

P0 / MVP implemented

Bloch Verify

Evidence comparison for exchanges, custodians, validators and risk teams. An offline CLI now validates checkpoint bundles; authenticated operator identity and production finality proofs remain future gates.

  • Checkpoint comparison
  • State evidence reports
  • Operator package proposal
P1 / planned service

Bloch Data + Dev Cloud

Build on the live historical index and published SDK toward versioned APIs, idempotent webhooks and a reproducible developer sandbox.

Gate: complete indexing, API versioning and observable availability.Explore Bloch Data
P2 / design only

Bloch Treasury + Pay

Policy wallet, approvals, invoices, reconciliation and finality receipts for organizations, without assuming initial custody or live payment-rail access.

Gate: hardened wallet, complete indexing and documented credit policy.Explore Bloch Pay
P3 / qualification

Router + Bridge + L2

Compare costs, time, custody and security boundaries before any cross-network execution. Public asset transfers wait for settlement proof and independent review.

Gate: reserve reconciliation, settlement verification and security review.

Two market tracks

Global reach.
Local relevance.

Start with software and evidence. Regulated activities depend on authorized institutions, legal structure and operational controls.

Global / Bloch MarketsProposed

Infrastructure for market participants.

A software line for position reconciliation and proof of reserves before exploring asset lifecycle and coordinated settlement with partners.

  1. Proof LedgerProvenance, reserve evidence and audit export.
  2. Asset LifecycleIssuance and corporate-action controls with authorized partners.
  3. DvP / PvP EngineResearch and partner pilots after verified finality and cash-leg arrangements.
Not an operating exchange, central counterparty or settlement system.
Latin America / Bloch LatAmPartner-dependent

Interoperability for regional workflows.

Begin with observation and reconciliation; test regulated connections only through qualified local participants.

  1. Brazil / Pix + Open FinanceConnector design and BRL-flow reconciliation with authorized institutions.
  2. Receivables + assetsEligibility, lifecycle and audit trails with legal and regulated partners.
  3. Regional corridorsControlled cross-border pilots with explicit FX, compliance and settlement.
No live Pix, Open Finance or Drex production integration is claimed.

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.

Evidence-led roadmap

Four delivery gates.
One accountable sequence.

Each gate requires a documented network result before the next product claim. These are priorities, not fixed launch dates.

G0 / reliable base

Prove the foundation

Regular checkpoints, fresh independent node sync, reproducible releases and compared finality evidence.

Unlocks: production qualification for Verify.
G1 / data + integration

Make data usable

Complete index, versioned API, webhooks, SDK examples, monitoring and support procedures.

Unlocks: Data + Dev Cloud pilots.
G2 / value workflows

Control real flows

Treasury policies, reconciliation, documented credit rules and a controlled partner pilot.

Unlocks: Treasury + Pay evaluation.
G3 / markets + networks

Qualify expansion

Bridge, L2, global-market and LatAm pilots with verified finality, authorized partners, audit and recovery.

Unlocks: limited, jurisdiction-specific launch decisions.
GLOBAL PATH

Proof Ledger → partner asset lifecycle → DvP/PvP research and pilots.

LATAM PATH

Read-only rail observation → partner reconciliation → controlled regional corridors.

Progress is measured by verified capability, not by a fixed launch-date promise. The network remains open; company services are optional.

Download the complete products + roadmap presentation

Let's connect what comes next

Products.
Infrastructure.
Research.

01Research collaboration↗ 02Product integration↗ 03Products + roadmap presentation↓