LogoLogo
  • Nesa Docs
    • Introduction to Nesa
    • Overview of the Nesa System
      • AI Models: Repository, Standardization, Uniformity
      • Users: Why Do We Need Private Inference?
      • Node Runners: Doing Inference and Earning $NES
    • Organization of the Documentation
  • Technical Designs
    • Decentralized Inference
      • Overview
      • Model Partitioning and Deep Network Sharding
      • Dynamic Sharding of Arbitrary Neural Networks
      • Cache Optimization to Enhance Efficiency
      • BSNS with Parameter-efficient Fine-tuning via Adapters
      • Enhanced MTPP Slicing of Topological Order
      • Swarm Topology
      • Additional: Free-Riding Prevention
    • Security and Privacy
      • Overview
      • Hardware Side: Trusted Execution Environments (TEEs)
      • Software/algorithm Side: Model Verification
        • Zero-knowledge Machine Learning (ZKML)
        • Consensus-based Distribution Verification (CDV)
      • Software/algorithm Side: Data Encryption
        • Visioning: Homomorphic Encryption
        • Implementation: Split Learning (HE)
      • Additional Info
        • Additional Info: Trusted Execution Environments (TEEs)
        • Additional Info: Software-based Approaches
    • Overview of $NES
      • $NES Utility
    • The First Application on Nesa: DNA X
    • Definitions
    • Additional Information
      • Dynamic Model Versioning and Fork Management
      • Nesa's Utility Suite
      • The AI Kernel Market
      • Privacy Technology
        • Trusted Execution Environment (TEE)
        • Secure Multi-Party Computation (MPC)
        • Verifiable Random Function (VRF)
        • Zero-Knowledge Proof (ZKP)
      • The Integration of Evolutionary AI to Evolve the Nesa Ecosystem
      • Interoperability and Nesa Future Plans
  • Using Nesa
    • Getting Started
      • Wallet Setup
      • Testnet Nesa Faucet
    • Via Web
      • Your Nesa Account
      • Selecting an AI Kernel
      • Submitting a Query
    • Via SDK
    • Via IBC
    • Via NESBridge
      • On Sei
  • Run a Nesa Node
    • Prerequisites
    • Installation
    • Troubleshooting
    • FAQ
  • Links
    • nesa.ai
    • Nesa Discord
    • Nesa Twitter
    • Nesa dApp: dnax.ai
    • Nesa dApp: DNA X Docs
    • Terms of Service
    • Privacy Policy
Powered by GitBook
On this page
  1. Technical Designs
  2. Additional Information

Interoperability and Nesa Future Plans

PreviousThe Integration of Evolutionary AI to Evolve the Nesa EcosystemNextGetting Started

Last updated 1 year ago

As the Nesa platform matures, our vision for its future encompasses not only expansion in capabilities but also a strong emphasis on interoperability. This is crucial to ensuring the platform can seamlessly integrate with the broader ecosystem of decentralized technologies and cater to a growing range of use cases.

NESBridge facilitates cross-chain interactions on the NES network, enabling the platform to interoperate with different blockchain networks. This protocol allows for the transfer of models, data, and even computational tasks across platforms, contributing to a more integrated and powerful decentralized AI offering for Kernels on Nesa. Nesa's network interoperability has the potential to establish standards for AI model execution and storage on distributed ledgers for the industry as it brings more partner networks into the ecosystem.

As we move to the main net, we plan to update the AI Kernel Market for a wider array of AI models and inference scenarios. This includes scaling up to handle larger and more complex models, integrating new machine learning frameworks, and adopting the latest advancements in AI research to provide users with a state-of-the-art execution environment.

The AI Kernel is designed with a modular architecture, allowing for components to be added, removed, or upgraded without disrupting the overall system. This flexibility ensures that the AI Kernel can adapt to new requirements and technologies as they emerge, fostering long-term sustainability and growth.

L2s connecting to Nesa by adapter. L2’s are representative of any blockchain based service in the AI domain, not just a Layer 2. The L2 posts data to Nesa and Nesa communicates back with the L2 to ensure proper data format and quality. From there, results are sent to Nesa’s Consensus and Execution Layer, and then rolled up for settlement.