Skip to content
DBIS ExplorerChain 138 Explorer by DBIS
Explorer Documentation

Posture glossary

First-read explanations for institutional posture badges shown on token, address, transaction, and search surfaces.

How to use this glossary

Click any posture badge on a live token, address, or transaction page to open the same definitions in a drawer. This page is the canonical long-form reference for audit and policy reviewers.

GRU instrument

A Global Reserve Unit instrument issued under DBIS taxonomy on Chain 138 or represented on public networks.

Methodology

The explorer marks GRU when token metadata, registry tags, or curated catalog entries align with the GRU transport and compliance model documented in the GRU guide.

x402 readiness

The token surface exposes the typed-data and domain metadata commonly required for HTTP-native payment authorization flows.

Methodology

Readiness is inferred from detected signing surfaces (EIP-712 domain, ERC-5267, and ERC-2612 or ERC-3009). It describes technical capability — not a guarantee that a live x402 merchant endpoint exists.

ISO-20022 alignment

The asset is modeled as part of the ISO-20022-aligned settlement and reporting posture for institutional messaging.

Methodology

This badge reflects GRU metadata and governance expectations around supervised disclosure — not a claim that every transfer is already formatted as an ISO-20022 message on-chain.

Forward-canonical posture

The asset version is the forward-looking canonical representation operators should wire for new integrations.

Methodology

Used when a token family has legacy or parallel deployments. Prefer forward-canonical addresses for routers, wallets, and explorer deep links unless a migration note says otherwise.

Reference asset

A non-GRU mirrored or externally issued asset shown for routing, liquidity, or price context.

Methodology

Reference assets help explain cross-chain routes and pool composition. They are not implied to be DBIS-issued compliant instruments unless separately tagged.

cW public-network representation

A wrapped GRU instrument activated on a public network (for example mainnet cWUSDC) while Chain 138 remains the program ledger.

Methodology

Public-network overlays use cW* naming. Liquidity and bridge lanes may reference these addresses even when the canonical compliant token lives on Chain 138.

transportActive (config compatibility)

Legacy JSON key indicating whether a public-network transport overlay is active in published `/config` manifests.

Methodology

Machine consumers should treat this as a v1 compatibility field. A future v2 schema will expose `publicNetworkActive` aliases before old keys are removed.

Planned v2 aliases: publicNetworkActive and livePublicNetworkAssets.