On-chain identity for every provider
The Provider Registry is a smart contract that maintains a verifiable record of all compute providers. Capacity, pricing, and reputation - all on-chain and queryable.
The source of truth for provider data
In traditional cloud, you trust that AWS has the capacity they claim. In decentralized compute, trust is replaced by verification.
The Provider Registry is a smart contract where:
- Every provider registers their wallet address
- Capacity is declared (CPU, memory, storage, GPU)
- Pricing is set (per-unit rates for each resource)
- Metadata is stored (location, description, etc.)
- The LinqProtocol installer benchmarks hardware and submits verified data on-chain
Anyone can query this registry to verify a provider's claims before deploying.
On-chain provider data
Identity
AddressEthereum wallet address (unique identifier)
Metadata HashIPFS or off-chain link to additional information
Capacity
vCPUTotal CPU cores available
MemoryTotal RAM in GB
StorageTotal disk space in GB
GPU ClassesAvailable GPU types and quantities
Pricing
Base RangesPrice per unit for CPU, memory, storage
GPU PricingPer-class pricing for GPU resources
Rate StructureHow pricing is calculated (hourly, etc.)
Usage
Used CapacityCurrently allocated resources
Available CapacityWhat's left for new deployments
Registration and updates
Provider Registers
Provider Updates
updateBaseRanges() - Change resource pricingupdateCapacity() - Adjust available resourcesupdateGpuClass() - Add or modify GPU offeringsupdateMeta() - Change metadata hashOrchestrator Queries
- 1. When you deploy, the orchestrator queries the registry
- 2. Finds providers with matching capacity and acceptable pricing
- 3. Matches you with the optimal provider
- 4. Creates escrow referencing the provider address
Don't trust. Verify.
Before Deploying
- Query a provider's registered capacity
- Check their pricing matches your budget
- Verify they have resources for your workload
During Deployment
- The escrow references the provider's on-chain address
- Provider identity is cryptographically verified
- No impersonation possible
After Deployment
- Provider address is recorded in escrow events
- Anyone can audit which provider served which jobs
- Reputation builds on-chain over time
What this means for you
Transparent Selection
See exactly which providers are available and at what price.
Verified Capacity
Providers can't claim capacity they don't have (enforced by escrow limits).
Price Discovery
Compare providers by price to find the best deal for your workload.
Low Sybil Risk
Staking requirements and reputation scoring make cheating expensive and limit bad actors.
Build your on-chain reputation
Verified Identity
Your wallet address is your identity. Build reputation over time.
Self-Service Updates
Adjust your capacity and pricing whenever market conditions change.
Competitive Positioning
Set attractive prices to win more deployments.
Earnings Tracking
All escrows reference your address - track total earnings on-chain.
Registration Process
Under the hood
ProviderRegistry.sol
Key Functions
register(baseRanges, gpuClasses, capacity, meta)Register as a provider
updateBaseRanges(ranges)Update resource pricing
updateCapacity(capacity)Update available resources
updateGpuClass(classId, pricing)Add/update GPU class
updateMeta(metaHash)Update metadata pointer
unregister()Remove from registry
View Functions
getProvider(address)Get full provider data
getProviders()List all registered providers
getUsedCapacity(address)Get current utilization
getCapacityTotals()Network-wide capacity
Events
ProviderRegisteredProviderUpdatedProviderUnregisteredCapacityChanged