---
guosmmDocumentId: GUOSMM-E-2026-012
title: "GRU, Chain 138, and x402 Canonical Terms Notice"
instrumentVersion: 1.0
language: en
publishedAt: 2026-07-12T19:45:00Z
effectiveAt: 2026-07-12T19:45:00Z
signingAuthority: "Sovereign Military Order of Malta"
draftStatus: production_signed
---

# GAZZETTA UFFICIALE DELL'ORDINE SOVRANO MILITARE DI MALTA
# OFFICIAL GAZETTE OF THE SOVEREIGN MILITARY ORDER OF MALTA (GUOSMM)

| Field | Value |
|-------|-------|
| Document ID | `GUOSMM-E-2026-012` |
| Series | E |
| Document type | Supervisory Notice — Canonical Terms |
| Published | 2026-07-12T19:45:00Z |
| Effective | 2026-07-12T19:45:00Z |
| Counsel gate | `signed` |
| Related acts | `GUOSMM-D-2026-011`, `GUOSMM-E-2026-011` |

---

# GRU, Chain 138, and x402 Canonical Terms Notice

## Section 1 — Purpose

1.1 This Notice establishes the canonical Gazette terminology for the GRU / DBIS architecture as it relates to:

- Defi Oracle Meta (`ChainID 138`)
- the Global Reserve Unit (`GRU`)
- native `c*` hub-layer assets
- `cW*` transport-form assets
- network interoperability
- systematic machine-payable and settlement-related flows, including x402-related lanes

1.2 The purpose of this Notice is to preserve definitional clarity, operational continuity, and publication discipline while preventing unsupported claims of regulatory equivalence, issuer equivalence, deposit status, legal-tender status, universal network support, or mutable live-status overstatement.

## Section 2 — Defi Oracle Meta / Chain 138

2.1 **Defi Oracle Meta**, identified on the EVM registry as **`ChainID 138`**, is designated as the principal GRU hub-settlement chain within the DBIS architecture.

2.2 Chain 138 is the canonical on-chain environment for:

- native GRU hub-asset issuance where separately authorized
- hub-directed x402 settlement surfaces
- registry, policy, and settlement-control functions
- related audit, ledger-correlation, and machine-payable workflow support

2.3 This designation does not by itself create:

- nation-state central-bank status
- payment-system designation by an external competent authority
- automatic host-state licensing effect
- universal corridor activation across all external networks

## Section 3 — Global Reserve Unit

3.1 The **Global Reserve Unit** or **`GRU`** is the governing reserve-basket, monetary-policy, and asset-taxonomy architecture for the designated DBIS token system.

3.2 GRU defines, within the applicable architecture:

- token-family taxonomy
- reserve-basket logic
- issuance structure
- transport-extension structure
- interoperability model
- policy and accounting treatment

3.3 GRU is not, by that status alone:

- the sovereign issuer
- a nation-state central bank
- a nation-state electronic money institution
- a substitute for any external regulatory authorization otherwise required

## Section 4 — Native c* hub assets

4.1 A **`c*`** asset is a native GRU compliant digital settlement instrument issued within the hub architecture and structured as part of the GRU M1 settlement layer where separately authorized.

4.2 A `c*` asset may be designated for:

- hub settlement use
- accounting alignment
- machine-payable workflows
- registry-linked or policy-governed financial operations

4.3 Such designation remains subject to:

- the governing acts
- reserve policies
- issuance controls
- operational rulebooks
- respondent-jurisdiction requirements where applicable

4.4 **`cUSDC_V2`** is designated as a native GRU M1 hub settlement asset on Chain 138 and may serve as the primary x402 settlement asset on the hub chain where the relevant technical surface, policy profile, and operational controls are active.

4.5 `cUSDC_V2` is structured for:

- par-style redeemability intent
- interoperability within approved corridors
- financial-integrity controls within the GRU stack

4.6 Nothing in this Section shall be read to create, without a separately applicable legal instrument or competent-authority perimeter:

- deposit status
- legal-tender status
- EMI authorization
- bank authorization
- an unconditional external redemption undertaking

## Section 5 — cW* transport-form assets

5.1 A **`cW*`** asset is a GRU transport-form digital instrument used to extend designated GRU payment and settlement functionality beyond the native hub chain into approved external execution environments.

5.2 A `cW*` asset is not the hub-native form of the corresponding GRU instrument. It is a transport extension intended to preserve defined settlement semantics, transfer utility, and machine-payable routing capability across approved network corridors.

5.3 **`cWUSDC_V2`** is designated as a GRU transport-form x402 extension for approved external network corridors and related machine-payable functions.

5.4 Where activated on an approved external network, `cWUSDC_V2` serves as the transport-form settlement asset for that corridor while remaining conceptually distinct from the native hub-chain GRU M1 asset.

5.5 As of **12 July 2026**, the technical evidence set cited in Section 9 identifies `cWUSDC_V2` as the evidenced v2 transport-form x402 asset on **Base** and **Polygon**.

5.6 No statement in this Section shall be read to imply:

- activation on every GRU corridor
- perpetual or immutable activation status
- universal support on all partner, wallet, exchange, or bridge surfaces

## Section 6 — Network interoperability

6.1 **Network interoperability** within the GRU / DBIS architecture means the controlled ability of designated assets, registries, settlement instructions, and machine-payable payment flows to operate across the hub chain and approved external networks under defined policy, accounting, compliance, and technical controls.

6.2 Interoperability may include:

- corridor-based transfer and settlement support
- registry or discovery synchronization
- machine-payable challenge and settlement lanes
- policy-bound routing and entitlement flows

6.3 Interoperability does not by itself imply:

- unrestricted convertibility
- universal network availability
- universal legal recognition
- automatic cross-border regulatory acceptance

## Section 7 — Systematic flows and ecosystem functionality

7.1 The GRU / DBIS ecosystem is designed to support **systematic flows**, meaning repeatable, policy-governed, machine-readable financial and settlement operations.

7.2 Such flows may include:

- discovery
- pricing
- entitlement
- payment challenge
- settlement authorization
- transfer execution
- registry update
- ledger correlation
- audit or compliance event generation

7.3 Ecosystem functionality and interoperability are recognized only to the extent that such flows remain within:

- the published control perimeter
- approved asset classes
- approved corridors
- the applicable operational rulebooks

## Section 8 — Public non-claims and drafting controls

8.1 Public-facing and counterparty-facing materials derived from this Notice shall preserve the following non-claims unless a separately governing act, license, or competent-authority determination expressly provides otherwise:

- no nation-state licensing equivalence claim
- no deposit-status claim
- no legal-tender claim
- no universal network-support claim
- no automatic bank, EMI, or payment-institution claim
- no implication that architecture wording alone creates a legally enforceable redemption right in every jurisdiction

8.2 A publication derived from this Notice should prefer:

- `asset`
- `settlement asset`
- `transport-form asset`
- `approved corridor`
- `structured for par-style redeemability intent`

over the more legally aggressive terms:

- `money`
- `par redeemable`
- `systemic money`
- `globally interoperable`

unless those stronger terms are expressly created and bounded by a separate governing act.

## Section 9 — Authoritative reference set

9.1 The authoritative technical and policy reference set for this Notice consists of the following records, as updated from time to time:

- `docs/04-configuration/X402_VERIFIED_POSITIONING.md`
- `docs/04-configuration/X402_CHAIN138_LIVE_TESTS_AND_PROOFS.md`
- `reports/status/x402-chain138-proof-suite-latest.json`
- `config/x402-route-pricing.v1.json`
- `config/chain138-x402-touchpoints.v1.json`
- `config/x402-cw-transport-v2-deploy.v1.json`

9.2 The Gazette text is the canonical definitional layer. Mutable deployment, route, support, or proof status should be taken from the authoritative technical reference set and not inferred solely from the generalized wording of this Notice.

## Section 10 — Public reliance boundary

10.1 Counterparties may rely on this Notice to understand the canonical Gazette vocabulary for Chain 138, GRU, `c*`, `cW*`, interoperability, and systematic x402-related ecosystem functionality.

10.2 Counterparties may not rely on this Notice alone as proof of:

- external regulatory approval
- external redemption enforceability
- universal route availability
- universal partner support
- immutable network activation status

10.3 Any package seeking technical, commercial, supervisory, or operational reliance should pair this Notice with the applicable technical proof records, governing charter stack, and respondent-jurisdiction filings or approvals where required.

## Section 11 — Publication and update procedure

11.1 This Notice should be published as the canonical Gazette terminology source for the GRU / Chain 138 / x402 lane.

11.2 Where a future publication seeks to change:

- the core designation of Chain 138,
- the role of GRU,
- the classification of `c*` or `cW*` assets,
- the non-claims boundary,
- or the corridor-activation framing,

such change should be made by an amending Gazette notice rather than by silent drift in technical or marketing materials.

11.3 Where only mutable technical status changes, the preferred update path is:

- refresh the technical proof and policy records in Section 9
- preserve this Notice unless its canonical legal or definitional content also changes

---

*Signing authority: Sovereign Military Order of Malta*