IXO is a software system for intelligent cooperation. It gives people, organisations, and AI agents shared state, shared structure, and shared rules to coordinate work, financing, verification, and governance using the IXO Spatial Web platform and Impact Hub interchain blockchain network.

This GitHub organisation hosts the core SDKs, smart contracts, and services you use to build applications on the IXO Spatial Web stack. These are the same components used by IXO products such as Impacts X, IXO Portal, Qi (a Flow engine for human–AI cooperation over shared state).

• Website: ixo.world
• Products and tools:
  IXO mobile wallet · Impacts Exchange asset marketplace · Jambo Wallet for Opera on Android
• Protocol and token:
  IXO Protocol · IXO Whitepaper · IXO Token
• Community:
  Telegram · X · Discord · LinkedIn

As an app developer, the IXO SDKs let you:

• Build wallets and dApps that connect to the Impact Hub (ixo-5) network and other Cosmos appchains.
• Create Spatial Web applications that use on-chain digital twins plus off-chain data rooms and messaging.
• Integrate AI agents and oracles that act on behalf of users, subject to explicit authorisation and verifiable logs.
• Manage verifiable credentials, claims, and digital rights in your own application domain.
• Orchestrate human–AI workflows that coordinate over shared state, using the same patterns that power Qi.

These are the main entry points for application development.

Type-safe TypeScript SDK for interacting with the IXO Protocol blockchain and other Cosmos chains. It provides query, signing, and smart contract clients, plus helpers for IXO-specific modules (entities, tokens, claims, bonds, etc.).

• GitHub: https://github.com/ixofoundation/ixo-multiclient-sdk
• NPM: https://www.npmjs.com/package/@ixo/impactxclient-sdk

Install:

npm install @ixo/impactxclient-sdk
# or
yarn add @ixo/impactxclient-sdk

Typical use cases:

• Query on-chain state (entities, claims, balances).
• Sign and broadcast transactions with your own wallet logic or via SignX.
• Interact with CosmWasm contracts on Impact Hub and connected appchains.

Client SDK for IXO Matrix, the sovereign data and messaging layer used to back Spatial Web “rooms” (CRDT documents, chats, data feeds, etc.).

• NPM: https://www.npmjs.com/package/@ixo/matrixclient-sdk

Install:

npm install @ixo/matrixclient-sdk
# or
yarn add @ixo/matrixclient-sdk

Typical use cases:

• Create secure data rooms for your app (for example per project, user, or digital twin).
• Store encrypted JSON documents and events.
• Coordinate multi-user editing and messaging around shared on-chain state.

SDK for integrating mobile-to-web authentication and transaction signing through the Impacts X mobile app. Use this when you want a clean separation between your web app and private keys on users’ phones.

• NPM: https://www.npmjs.com/package/@ixo/signx-sdk

Install:

npm install @ixo/signx-sdk
# or
yarn add @ixo/signx-sdk

Typical use cases:

• Connect web apps to Impacts X for login and signing.
• Hand off transaction payloads from browser to mobile wallet and back.
• Implement “Sign in with IXO” flows.

Expose IXO’s agentic layer from your app. These are used by Qi and other cooperating systems.

• Agentic Oracles SDK: https://www.npmjs.com/package/@ixo/assistant-sdk (see IXO docs and organisation repos for latest package and usage patterns)

Use them to:

• Call into Agentic Oracles from your app to access verifiable agent services.
• Integrate your own MCP / tool servers as IXO-compatible services.
• Build agents that act over both blockchain and Matrix state with explicit accountability.

Utility SDK for integrating apps with Jambo Wallet where that is part of your distribution strategy.

• NPM: https://www.npmjs.com/package/@ixo/jambo-wallet-sdk

did:ixo DID provider that plugs into DID tooling and wallets.

• NPM: https://www.npmjs.com/package/@ixo/did-provider-x

Use it to:

• Issue and resolve DIDs for users, organisations, devices, and agents that operate within IXO domains.
• Interoperate with verifiable credential stacks that expect a DID provider abstraction.

This is the minimal path to build against Impact Hub and Matrix using the SDKs.

# Core blockchain + Matrix SDKs
npm install @ixo/impactxclient-sdk @ixo/matrixclient-sdk
# Optional: SignX for mobile signing
npm install @ixo/signx-sdk

You need:

• An RPC endpoint and chain-id for Impact Hub (mainnet: ixo-5, testnets also available).
• A Matrix homeserver URL (for example your own IXO Matrix deployment).
• Your own key or an external signer (for example via SignX or a wallet).

Endpoints and chain metadata for Impact Hub mainnet, testnet, and devnet are maintained in the Cosmos chain-registry:

• Mainnet chain.json (Impact Hub):
  https://github.com/cosmos/chain-registry/blob/533af67f3a21bb952189070c106859eac59e4466/impacthub/chain.json
• Testnet chain.json:
  https://github.com/cosmos/chain-registry/blob/533af67f3a21bb952189070c106859eac59e4466/testnets/impacthubtestnet/chain.json
• Devnet chain.json:
  https://github.com/cosmos/chain-registry/blob/533af67f3a21bb952189070c106859eac59e4466/testnets/impacthubdevnet/chain.json

Faucets (for testing only):

• Devnet: https://faucet.devnet.ixo.earth
• Testnet: https://faucet.testnet.ixo.earth

Mainnet has no faucet and requires IXO tokens.

The following example shows how to:

• Connect to Impact Hub using the MultiClient SDK.
• Connect to Matrix with the Matrix SDK.
• Create a simple on-chain entity and a Matrix room to hold its off-chain data.

import { createClient } from '@ixo/impactxclient-sdk'
import { createMatrixClient } from '@ixo/matrixclient-sdk'

async function main() {
  // 1. Connect to Impact Hub
  const chain = await createClient({
    rpcEndpoint: 'https://<your-rpc-endpoint>', // see chain-registry for options
    chainId: 'ixo-5',
    // signer: your signing implementation (offline signer, SignX, etc.)
  })

  // Example: query chain height
  const status = await chain.getStatus()
  console.log('Chain height:', status.latestBlockHeight)

  // 2. Connect to Matrix
  const matrix = await createMatrixClient({
    baseUrl: 'https://<your-matrix-homeserver>',
    accessToken: '<user-or-bot-access-token>',
  })

  // 3. Example: create a digital twin entity on-chain
  const entity = await chain.createEntity({
    type: 'Asset',
    name: 'Example Solar Array',
    data: {
      capacityKw: 5,
      location: {
        lat: -33.9249,
        lng: 18.4241,
      },
    },
  })

  console.log('Created entity:', entity.id)

  // 4. Example: create a Matrix data room bound to this entity
  const room = await matrix.createRoom({
    name: `entity:${entity.id}`,
    encryption: true,
  })

  // Store some JSON data in the room
  await matrix.sendEvent(room.roomId, 'm.room.message', {
    msgtype: 'm.data',
    body: JSON.stringify({
      entityId: entity.id,
      note: 'First reading',
      timestamp: new Date().toISOString(),
    }),
  })

  console.log('Created Matrix room:', room.roomId)
}

main().catch(console.error)

For real applications you should externalise configuration, implement a robust signer abstraction (for example using SignX, Passkey, or browser wallets), and add error handling and retries.

These are the most relevant repos in this organisation when building apps on the IXO stack:

1. ixo-multiclient-sdk
   MultiClient SDK source, docs, and examples for Impact Hub and other Cosmos appchains.

2. ixo-blockchain
   Impact Hub (IXO Protocol) Cosmos SDK appchain implementing entities, claims, tokens, bonds, smart accounts, and governance modules.

3. ixo-contracts
   CosmWasm smart contracts used across the IXO ecosystem, including IXO Swap and DAO/asset contracts.

4. ixo-blocksync
   Indexer for Impact Hub, exposing public chain data via GraphQL and optimised queries for apps.

5. cosmos-chain-resolver
   Utility for resolving chain-registry metadata and active endpoints programmatically.

6. ixo-Mobile-dev (private)
   IXO mobile wallet application source.

Each repo has its own README and, in many cases, additional docs and example projects.

We welcome contributions from app developers across the stack:

1. Pick the repository that matches what you want to improve (SDK, contracts, infra, docs).
2. Fork the repository and create a feature or bugfix branch.
3. Add tests and update any related docs or examples.
4. Open a pull request with a clear description, motivation, and implementation notes.

Where available, follow the contribution guidelines in the target repository. For this organisation root, you can also open issues to discuss cross-cutting changes (for example SDK ergonomics, new example apps, or documentation gaps).

Ways to get help and stay in sync:

• Open issues and discussions in the relevant GitHub repo.
• Visit Qi to get first-hand experience of using the IXO Portal and chat with our AI companion.
• Use Telegram and X for ecosystem news and broader coordination.
• Follow IXO on LinkedIn for partnership and product updates.

If you are building a substantial product or platform on IXO and need deeper support (for example infrastructure, custom domains, or enterprise integration), reach out through the official channels listed on ixo.world.

Unless otherwise specified in a particular repository, code in this organisation is licensed under Apache 2.0.

You are free to use, fork, and extend the software under that license. For regulated or high-stakes deployments, involve your legal and compliance teams in reviewing dependencies, deployment patterns, and governance models.