XePHY
  • Introduction
    • What is XePHY
  • Key features
  • Architecture
  • components
    • Messaging layer 🔥
      • Data Pub-Sub
      • Solana Integration
      • RPC Call
      • RPC Endpoints
      • Best Practices
      • Verifiable logs
    • XePHY ID [Coming Soon]
      • Register products
      • Mint DID
      • Use DID as token gate (access control)
      • Extentions
      • Build with XePHY ID
      • Hardware integration and attestation
    • Liquidity layer
      • Stake Pool
      • Yield Pool
      • PayFi Pool
    • Verification layer
      • Proof of real device
      • Integration
      • Proof of location
      • XePHY NCN (on Jito Restaking)
      • Trusted DePIN network map
  • Tutorials 🔥
    • Build a Hello World (Rust)
  • Build a Hello World (TypeScript)
  • Build a XeCharge Machine
  • Build a Gacha Machine
  • Build a LLM Proxy
  • Service Mesh
    • MCP Services
      • About MCP
  • Resources
    • Contact
  • GitHub
  • X
Powered by GitBook
On this page
  • Connecting to the Messaging Layer
  • Recommended Messaging Layer Client
  1. components
  2. Messaging layer 🔥

RPC Call

PreviousSolana IntegrationNextRPC Endpoints

Last updated 8 days ago

Connecting to the Messaging Layer

To interact with the Messaging Layer, you have two options: connect to XePHY’s public relay URL or deploy a local instance. Choose based on your needs—public for simplicity, local for development or control.

1. Local Deployment

  • Prerequisites:

    • Docker: Ensure is installed and running on your system to manage the messaging network services.

  • Steps:

    1. Clone the repository:

      Copy

      git clone https://github.com/xephy-io/xephy-messaging-network-self-hosted.git
      cd xephy-messaging-network-self-hosted/xephy-messaging-network
    2. Launch the messaging layer using Docker Compose:

      Copy

      docker compose up --pull always

This deploys a self-hosted Nostr-based messaging network locally, ready to handle event subscriptions and publications for your XePHY applications. By default, it will be accessible at wss://localhost:8080.

Recommended Messaging Layer Client

Below are recommended libraries for interacting with the Nostr protocol across multiple programming languages, with hyperlinks to their official repositories or documentation.

Rust

JavaScript/TypeScript

Python

Go

Kotlin

Swift

Docker
nostr-sdk
nostr
nostr-tools
nostr-relay
pynostr
nostr-py
go-nostr
nostr-kotlin
NostrKit