Glacis Core

Cross-chain messaging router and firewall. One integration, every bridge, with redundancy and configurable security built in.

Read the docs
Any bridge
Custom forks supported
Any quorum
Configurable security
Any validator
Swappable in production
Core features

Built to bend

Build applications with full control over the data transport layer, not just marketing hype. Choose between speed, cost, or security, and configure them to meet your needs.

Abstraction

A single integration allowing dynamic data transport in real time. Ensure liveness during service outages, security issues, or changes in terms of use, without updating your interface.

Redundancy

Delivery guaranteed. Send data across multiple paths to guarantee availability. Configure delivery for “just once”, “request delivery confirmation” or “fire and forget”.

Retry Management

Delayed or stuck messages impact the user experience. Ensure delivery with fail over settings to dynamically route around potential issues or retry across any messaging path.

Modular Security

Program your data transport security anyway you want for any message. Dynamically update m-of-n requirements in real time to enhance reliability and security.

The network inside it.

Any bridge
WormholeLayerZeroAxelarCCIPHyperlane+ More
And any custom GMP, fork, or private configuration you bring
Supported chains
EthereumArbitrumOptimismBasePolygon+ 38 More

How teams use
Glacis Core.

As the messaging substrate

Glacis Core is the messaging substrate underneath every ZeroDelta settlement. It handles cross-chain dispatch, quorum, and retry — without the application above it seeing the plumbing.

Read about ZeroDelta

As a standalone product

Teams building governance, treasury, or asset-transfer flows use Glacis Core directly. Same redundancy and quorum guarantees, with full control over per-application policy.

Read the docs

As an audited security layer

Quorum requirements are configurable per application and per message. The validation layer is replaceable without changing integrations or the contracts above it.

Talk to our security team
In practice

Code, configuration, confirmation.

Every message goes through multiple GMPs in parallel. Glacis Core tracks each through its own state machine, and resolves the result when the configured quorum agrees.

Request
// Illustrative — final SDK signature in the docs
import { GlacisRouter } from '@glacis-labs/sdk';

const router = new GlacisRouter({
    destination: { chain: 42161, target: '0x...' },
    quorum:      { required: 2, of: 3 },
    retry:       'auto', });

const tx = await router.send({ payload: encoded });

// → returns { messageId, attestations[], finality }

Response
message_id0x4f2b…8a91
attestations3 of 3
quorumreached
statusaccepted
finalityconfirmed (7 blocks)
Full SDK and receipt format on docs.

Cross-chain messaging
should be the boring part.

Glacis Core makes it so.

LinkedInWhitepaperXEmail