XGR Network develops XGRChain, an EVM compatible blockchain focused on deterministic on chain process execution rather than simple value transfer.
The core technology is XDaLa, a validation to execution engine that extends transactions into auditable multi step workflows by combining on chain rules, external data sources and smart contract execution.
This repository contains public specifications, standards and reference material for XGR Network.
XDaLa is a process layer that operates across three stages:
-
Validation
Structured rules validate transaction intent, parameters and external conditions. -
Orchestration
Multi step execution paths are defined using permits, limits and triggers. -
Execution
Smart contracts are executed only after successful validation, producing verifiable and auditable outcomes.
XDaLa is designed for use cases that require deterministic behavior, regulatory constraints or controlled execution flows.
The XGR MCP Gateway is the AI-native access layer to the XGR stack.
It exposes XGRChain data, XDaLa sessions, Explorer evidence, XRC standards, schemas and authoring knowledge as semantic Model Context Protocol tools. MCP-compatible agents can inspect deployed workflows, draft and validate XDaLa process bundles, and prepare human-in-the-loop handoffs for local wallet signing.
The gateway never holds private keys, never signs transactions and never takes custody.
- Mainnet MCP: https://mcp.xgr.network/mcp
- Testnet MCP: https://mcp.testnet.xgr.network/mcp
- MCP documentation: https://xgr.network/docs/mcp_overview/
This repository provides public documentation and specifications for XDaLa and related components.
- General overview of the XDaLa process model
- Endpoint and validation reference
- Permit and limit definitions
- Encryption and grant handling
The current documents include:
- XDaLa general overview
- XDaLa endpoint reference
- XDaLa limits specification
- XDaLa permit catalog
- XGR encryption and grant model
All specifications are evolving and subject to versioning.
XDaLa is privacy first by design.
- Payloads and outputs can be end to end encrypted
- Decryption remains on the user side using wallet based keys
- No plaintext sensitive data is required to be stored on chain
- Validation and execution are separated from data visibility
This enables auditable processes without compromising data sovereignty.
This repository is intended for:
- Developers building on EVM compatible blockchains
- Infrastructure and protocol engineers
- Teams working on regulated or compliance sensitive workflows
- Auditors and reviewers evaluating deterministic execution models
- XGRChain: Mainnet live, testnet available
- XDaLa: Active specification and implementation phase
- MCP Gateway: Phase 1 live, read tools and handoff preparation available
- Standards: Draft and review status
The repository reflects the public and stable interface of the system.
This repository focuses on specifications and reference material.
- Issues may be opened for clarification or discussion
- Pull requests should be limited to documentation improvements or corrections
Implementation specific code is maintained in separate internal repositories.
If you discover a potential security issue, please report it responsibly.
Contact: [email protected]
These are the canonical entry points for the public ecosystem. If you are unsure where to start, begin with the Website and the specs in this repository.
- Website: https://xgr.network
- GitHub Organization: https://github.com/xgr-network
- Specs & Standards (this repo): https://github.com/xgr-network/XGR
- Node Implementation (xgr-node): https://github.com/xgr-network/xgr-node
- Documentation Hub: https://xgr.network/docs
- Testnet Faucet: https://faucet.xgr.network
- Explorer: https://explorer.xgr.network
- MCP Gateway Mainnet: https://mcp.xgr.network/mcp
- MCP Gateway Testnet: https://mcp.testnet.xgr.network/mcp
Reference chain configuration artifacts live in this repository under genesis/.
- Mainnet genesis:
genesis/mainnet/genesis.json
If you are running a local/dev network, prefer generating a fresh genesis via the CLI tooling rather than hand-editing production genesis files.
Unless stated otherwise, all documentation in this repository is licensed under the Apache License 2.0.