RACKBID

      
      ◆
      THE DEMAND LAYER FOR DECENTRALIZED COMPUTE
    
RACKBIDPost the job. Let compute compete.
Fund a compute job in USDC. Qualified providers bid on price and delivery. Payment settles only after the work passes verification.

      POST A JOB→
      BECOME A PROVIDER
    
FUND → BID → EXECUTE → VERIFY → SETTLE

        SETTLEMENT LOCK · ESCROW SEALED
      
        SCROLL TO ZOOM

    
    RACKBID
  
      SOLANA · NATIVE USDC ESCROW
    
    OPEN THE APP →

01 · THE GAP
Compute has supply.
It lacks funded demand.DePIN spent years attracting machines. The scarce side is the purchase contract. RACKBID connects enterprise work orders to existing GPU networks and private clusters through one specification, one auction and one settlement flow.

          SUPPLY DENSITY · SOLANA
          77.54
        
16 active projects competing for the same hardware pool. More capacity adds no marginal value.

          MEASURED DEMAND
          39.35
        
Buyers stay on traditional cloud because that is the only place a binding SLA gets signed.
SEGMENT INDICES MEASURED 2026-08-27 · NOT RACKBID PERFORMANCE DATA

02 · MECHANISM
Fund → Bid → Execute → Verify → SettleNo idle-node rewards. No project token. Revenue comes from completed work.

        01
        FUND
        Maximum budget enters a job-specific USDC escrow. An unfunded job never reaches the market.
      

        02
        BID
        Qualified providers commit sealed bids and lock a performance bond, then reveal.
      

        03
        EXECUTE
        The awarded supplier gets time-limited access to encrypted inputs. Heartbeats and logs are recorded.
      

        04
        VERIFY
        The declared acceptance suite runs. The verifier signs pass, fail or inconclusive.
      

        05
        SETTLE
        Accepted value is released in USDC, the bond returns, the outcome enters the public record.
      

03 · SEALED REVERSE AUCTION
Bids stay sealed until reveal.01A provider commits a hash of price, delivery estimate and salt.
02The performance bond locks at commitment — default 10% of contract value.
03After the commit window closes, each reveal is checked against its commitment.
04The buyer awards on price, promised delivery and raw execution history. Losing bonds unlock.

        OPEN LOTS
        SEALED
        AWARDED
      

        JOB RB-2418 · BLENDER FRAME BATCH
        REVEAL CLOSES 00:04:12
      
PROVIDER
PRICE USDC
DELIVERY
ON-TIME
NODE-OPS EU-WEST
1,840.00
9h 20m
96.2%
CLUSTER-07 SG
1,712.50
8h 05m
98.9%
RENDERFARM NORDIC
1,905.00
7h 40m
94.1%
UNREVEALED · 1 BID
—
—
—

        ESCROW 2,100.00 USDC · BOND 10%
        LOWEST VALID BID SELECTED
      

04 · VERIFICATION
The contract does not guess.Every job declares its acceptance tests before bidding. Evidence is verified off-chain; funds move on Solana according to the recorded result.

      DRAFT
      →
      FUNDED
      →
      COMMITTING
      →
      REVEALING
      →
      AWARDED
      →
      RUNNING
      →
      SUBMITTED
      →
      SETTLED
      ↳ DISPUTED / REFUNDED
    

        AUTOMATIC EVIDENCE
        Container digest, input and output manifest hashes, timestamps, heartbeats, exit status, telemetry, acceptance-test results.
      

        SIGNED ATTESTATION
        The program trusts only signatures from the configured verifier and dispute authority. Pass, fail, or inconclusive.
      

        FAILURE PATH
        Missed deadline or failed acceptance refunds by milestone state. A published portion of the bond may be slashed.
      
This is a transparent, enforceable marketplace — not a fully trustless proof-of-compute protocol. Verifier sets, independent operators and two-of-three attestation policies are later stages.

05 · PILOT PARAMETERS
Operating defaults, not protocol constants.The 3% rate is a launch assumption to validate with buyers and suppliers. Failed or refunded jobs carry no execution fee.
Settlement assetNative USDC on Solana
Take-rate on settlement3%
Performance bond10% of contract value
Minimum qualified bidders2
Bid commitment window2–24 h by job size
Bid reveal window30 min
Buyer award window2 h
Acceptance window24 h
Manual arbitration target3 business days

BUYERS
        AI and ML teams with bursty batch inference or evaluation jobs.
        VFX and media studios needing temporary render capacity under a hard deadline.
        Infrastructure teams testing alternative providers without separate long-term contracts.
        Finance and operations teams that require invoices and a responsible counterparty.
      
SUPPLIERS
        Integrated decentralized compute networks.
        Professional operators and resellers using those networks.
        Private GPU clusters and regional data centers with spare capacity.
        Specialized rendering and inference providers.
      

06 · BOUNDARIES
What RACKBID is not.

      —Not a GPU hardware owner.
      —Not a node-reward network.
      —Not another compute token.
      —Not a cloud provider pretending to be a marketplace.
      —Not an onchain storage layer for customer data.
      —Not a claim that a blockchain can judge every output.
      —Not a speculative ranking system.
    

Post the job.
Let compute compete.Bring one real batch job and receive competing, bonded USDC quotes from at least two compute suppliers.

      POST A JOB→
      BECOME A PROVIDER
    

      RACKBID · THE DEMAND LAYER FOR DECENTRALIZED COMPUTE
      SOLANA · NATIVE USDC · NO TOKEN
      OPEN THE APP →
      JOB SPEC v1
      PROVIDER WHITELIST
    

Compute has supply.It lacks funded demand.

Fund → Bid → Execute → Verify → Settle

Bids stay sealed until reveal.

The contract does not guess.

Operating defaults, not protocol constants.

What RACKBID is not.

Post the job.Let compute compete.

Compute has supply.
It lacks funded demand.

Post the job.
Let compute compete.