MAINNET LIVE

🚀 XGR Actual News

loading… Get XGR

17.01.2026: Mainnet is live — and the first tranche was sold out on day one. 🔥

Next tranche opens:

XGR — Beyond Blockchain

The revolution of on‑chain data processing

Build deterministic workflows that move from intent to verified outcome — approvals, limits, multi‑step orchestration, and real‑world checks included. XGR pairs fast (~2s blocks), energy‑efficient consensus with full EVM compatibility. XDaLa by XGR.Network adds a process layer: sessions can spawn, join, and wait — producing auditable receipts and optional encrypted artifacts.

Why XGR

A modern chain for real‑world automation — simple to adopt, powerful to scale.

~2s Block time · Responsive UX
EVM Works with Solidity / Hardhat / Foundry
Low power Energy‑efficient by design
Impact Programmable impact primitives (optional)
xDaLa Deterministic Layer‑1 Process Engine — xdala.testnet.xgr.network
Encrypted artifacts On‑chain receipts · privacy‑first (grant‑based)
Solidity Hardhat Foundry ethers.js web3.js

From intent to outcome — with proof along the way

Design flows that start with a real‑world intent and end with settlement. Keep sensitive details private; keep the important evidence on‑chain.

How XDaLa works (Quickstart)

Write a rule, deploy it, publish an orchestration, then start a session via RPC with a signed permit. This is the smallest end‑to‑end mental model.

1 · Rule

Write an XRC‑137 rule JSON

Define typed inputs and deterministic branching via onValid / onInvalid.

Minimal XRC‑137 example
{
  "payload": {
    "Amount": { "type": "int64" }
  },
  "rules": [
    "[Amount] > 0"
  ],
  "onValid": {
    "payload": {
      "result": "ok",
      "amount": "[Amount]"
    }
  },
  "onInvalid": {
    "payload": {
      "result": "invalid",
      "reason": "Amount must be > 0"
    }
  }
}
2 · Deploy

Deploy XRC‑137.sol and upload the JSON

The XRC‑137 contract is an on‑chain container for one rule document (plain JSON or encrypted blob).

Canonical interface shape
interface IXRC137 {
  function getRule() external view returns (string memory);
  function setRule(string calldata jsonOrBlob, bytes32 rid, string calldata suite) external;
  function isEncrypted() external view returns (bool);
  function getEncrypted() external view returns (bytes32 rid, string memory suite);
}

After deployment, call setRule(ruleJson, 0x00..00, "") to store plain JSON, then verify via getRule().

3 · Orchestration

Publish an XRC‑729 orchestration (process graph)

Store a small orchestration JSON that maps step IDs (like S1) to XRC‑137 rule contracts.

Minimal orchestration example
{
  "id": "hello_xdala",
  "structure": {
    "S1": {
      "rule": "0x<your_XRC137_rule_contract>",
      "onValid": {},
      "onInvalid": {}
    }
  }
}

Your client typically pins an ostcHash (keccak256 of the UTF‑8 JSON) for auditability.

4 · Session

Start a session via RPC + SessionPermit

Fetch chainId and nextProcessId, sign an EIP‑712 SessionPermit, then call xgr_validateDataTransfer.

Minimal RPC call shape
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "xgr_validateDataTransfer",
  "params": [
    {
      "stepId": "S1",
      "payload": { "Amount": 42 },
      "permit": { "...": "SessionPermit (EIP-712) + signature" },
      "orchestration": "0x<your_XRC729_contract>"
    }
  ]
}

The engine executes the XRC‑137 step, selects onValid or onInvalid, emits receipts/log artifacts, and spawns the next steps defined by the orchestration.

Want the full spec and typed‑data definitions? Jump into Docs.

What you can build

Policy‑gated transfers

Movement with guardrails

Enforce roles, limits, approvals, or whitelists before value moves. Make exceptions explicit and auditable.

Automations

From events to execution

Trigger multi‑step actions on schedules or external facts. Spawn sub‑flows and loop with safeguards.

Private data · public proof

Confidence without exposure

Keep sensitive details private while producing verifiable evidence for decisions and outcomes.

Enterprise workflows

Multi‑party, accountable

Coordinate teams and systems with tamper‑evident trails and clear hand‑offs between steps.

Concrete examples

A few patterns teams can ship with XDaLa on XGR — adaptable to your rules and data.

ISO‑style transaction flows

Structured payments, policy‑first

Validate structured payment data, enforce limits and approvals, then settle — with verifiable evidence, without exposing sensitive details.

Data feeds & attestations

Act on real‑world facts

Consume signed feeds (prices, FX, weather, IoT, oracles) and trigger actions when thresholds or conditions are met.

Order processing

From order to settlement

Coordinate order → fulfillment → settlement with milestone‑based releases, exceptions, and approvals — all auditable.

KYC / AML & sanctions

Checks before action

Run policy checks before transfers or contract calls. Keep private inputs private while keeping the proof on‑chain.

Treasury automation

Streams, splits, and caps

Automate multi‑sig approvals, streaming payouts, vesting schedules, and budget caps tied to events or time.

Marketplace & escrow

Trust with clear rules

Hold funds in escrow, define dispute windows, and resolve outcomes automatically with a transparent audit trail.

Built in Europe. Built for builders.

From the heart of Europe

Created by XGR.Network GmbH, we champion privacy, security, and responsible innovation — with European quality at our core. Impact features are supported as optional primitives, not as a blanket promise.

Builder‑first experience

Clean APIs, familiar tooling, fast confirmations. Go from idea to production without reinventing your stack.

Auditable by design

Keep the important evidence on‑chain so teams, partners, and auditors can verify outcomes without friction.