githubEdit

Overview

Architecture Diagram

spinner

The rise of Web3 and distributed infrastructure is reshaping how storage and AI resources are discovered and consumed. The ISP Market is designed as a decentralized cloud and AI resource marketplace that connects Consumers and Providers with transparent coordination between off-chain services and on-chain enforcement.


ISP Market: Decentralized Cloud and AI Resource Marketplace

The ISP Market manages key operations, including SLA alignment, allocation workflows, quality verification, and payment enforcement.

To ensure flexibility, the solution supports both fiat and cryptocurrency payments (BTC, XLM, STRK, ALGO, and others). Providers and Consumers can use the ecosystem that best fits their operations, while the platform handles orchestration and settlement logic.

Smart Contract Orchestrators

Orchestrators communicate with the ISP Market control plane, ensuring SLAs, payments, and quality metrics are synchronized and enforced.

  • Orchestrator for Providers: Manages published Data Units, SLA commitments, and quality monitoring.

  • Orchestrator for Consumers: Handles reservations, payment flows, and data-access rights for allocated units.

ISP Market Core Functions

The marketplace core integrates operational tooling to simplify provider onboarding and consumer adoption:

  • Monitor: Tracks Provider and Data Unit performance signals used for SLA and reputation decisions.

  • Registry: Maintains certified Providers and Consumers meeting market compliance requirements.

  • Marketplace: Public discovery layer where Consumers compare Data Units, capabilities, and reliability indicators.

  • Oracles: Validation network that reports SLA/QoS observations to orchestrators and smart contracts.


Consumers (or Unit Consumers)

  • Individuals, organizations, or applications requiring storage and AI/compute resources.

  • Allocate Data Units through the marketplace and then consume them with generated credentials compatible with the allocated unit type.

SLA payments depend on requested resources, reservation duration, provider profile, redundancy, QoS targets, and allocation terms.


Providers (or Unit Providers)

Providers with storage and/or compute infrastructure can publish Data Units to the marketplace. Payments can be streamed to Provider wallets according to orchestration rules and verified service delivery.

  • Offer storage and/or compute infrastructure by submitting Data Units to the marketplace.

  • Commit to declared quality and availability standards.

  • Maintain certification and reporting status to remain discoverable.

Bridge Node

The Bridge Node remains a key infrastructure component for provider integration:

  • Manages data transfer paths between Consumer and Provider using compatible protocols (e.g., S3/GCS for storage scenarios).

  • Sends performance reports to oracle pipelines for SLA/QoS verification.

Typical provisioning flow:

  • The Provider installs the Bridge Node locally. A registration signal is sent to the platform and an installation secret is generated.

  • The Provider connects a wallet to claim the Bridge Node and authorize collateralized operations.

  • Once registered, the Provider can submit Data Units and make them available for reservation in the ISP Market.

Last updated

Was this helpful?