Inspiration
The inspiration for Kinetic came from witnessing the growing demand for GPU compute resources in the AI/ML space, while simultaneously seeing thousands of underutilized GPUs sitting idle in data centers, gaming rigs, and research labs worldwide. We recognized a fundamental inefficiency: researchers and developers struggle to access affordable compute power, while hardware owners have no easy way to monetize their idle resources.
Traditional cloud providers like AWS and Google Cloud charge premium prices and require complex setup processes. Meanwhile, the decentralized compute space lacked a trustworthy, user-friendly marketplace with verifiable execution guarantees. We saw an opportunity to build a truly peer-to-peer marketplace on Algorand that could solve both problems—connecting compute providers directly with consumers while ensuring trust through cryptographic proofs and smart contract-based payments.
The vision was clear: create a decentralized marketplace where anyone can rent or provide GPU/CPU resources with instant provisioning, transparent pricing, and cryptographic proof of execution—all powered by Algorand's fast, low-cost blockchain.
What it does
Kinetic is a fully decentralized peer-to-peer marketplace for high-performance computing resources built on the Algorand blockchain. It enables:
For Compute Providers:
- Register hardware resources (GPUs, CPUs, storage) on-chain via smart contracts
- Set custom pricing and availability parameters
- Receive automatic job matching based on hardware specifications
- Earn instant payments in ALGO upon job completion
- Build reputation through ARC-3 badge NFTs based on performance
For Compute Consumers:
- Browse available compute providers with real-time pricing and availability
- Submit compute jobs with automatic provider discovery and matching
- Monitor job execution in real-time with live progress updates
- Receive cryptographic proof-of-compute for every job
- Pay only for completed work through secure escrow contracts
Key Features:
- Autonomous Agent System: Zero human intervention—agents handle provider discovery, job matching, execution, and payment verification automatically
- Cryptographic Proof Chain: Every job generates a 9-step SHA-256 proof chain (Job Received → Escrow Locked → Resource Allocation → Execution → Verification → Payment Released)
- X-402 Payment Protocol: Novel HTTP-native payment flow enabling machine-to-machine transactions
- Real-time Updates: Server-Sent Events (SSE) provide live job progress, proof generation, and payment status
- Escrow Protection: Smart contracts hold funds until job completion is cryptographically verified
- Reputation System: Providers earn on-chain reputation badges (NFTs) based on completed jobs and uptime
How we built it
Smart Contract Layer (Algorand):
- Built 3 core smart contracts using
algopy(modern alternative to PyTeal):- ProviderRegistry: Stores provider information, hardware specs, and reputation on-chain using BoxMap storage
- EscrowContract: Manages payment escrow with lock/release/refund patterns and timeout protection
- BadgeMinter: Issues ARC-3 reputation badges as frozen ASAs (Soul-Bound Tokens)
- Leveraged Algorand's box storage for scalable on-chain data
- Implemented inner transactions for atomic escrow releases and badge minting
- Used ARC-4 ABI methods for typed contract interfaces and ARC-56 for deployment metadata
Backend (Python + FastAPI):
- Built RESTful API with FastAPI for high-performance async operations
- Implemented Server-Sent Events (SSE) for real-time job updates and proof broadcasting
- Created autonomous agent system (
consumer_agent.py) with:- Provider discovery via Algorand Indexer API
- Intelligent job matching based on VRAM, GPU model, price, and uptime
- Budget controls with per-job and daily spending limits
- Fraud detection using SHA-256 verification + 10% spot-check reruns
- Integrated
py-algorand-sdkfor blockchain interactions - Built comprehensive proof-of-compute system with 9-step cryptographic chain
- Implemented X-402 payment middleware for HTTP-native blockchain payments
Frontend (Vanilla JavaScript + Tailwind CSS):
- Created 5-page responsive web interface:
- Marketplace: Provider discovery with filters and search
- Providers: Detailed provider grid with real-time data
- Activity: Live job monitoring with proof-of-compute visualization
- Wallet: Balance tracking, transaction history, and spending analytics
- Dashboard: System health and node status
- Designed custom "Stitch Algorand Compute Exchange" design system with dark theme, glassmorphism effects, and electric cyan accents
- Integrated Pera Wallet for user authentication and transaction signing
- Built real-time event streaming using EventSource API for SSE
Development Tools:
- Used Vite for fast frontend builds and hot module replacement
- Implemented comprehensive testing with pytest for smart contracts and backend
- Set up SQLite databases for job history, spending logs, and provider data
- Created deployment scripts for Vercel (frontend/backend) and Algorand TestNet (contracts)
Challenges we ran into
1. Smart Contract Storage Limitations: Initially, we tried using global and local state for provider data, but quickly hit Algorand's 128-byte key-value limits. We solved this by migrating to BoxMap storage, which provides virtually unlimited scalable storage while maintaining on-chain verifiability.
2. Real-time Proof Broadcasting: Implementing real-time updates without WebSockets was challenging. We chose Server-Sent Events (SSE) over WebSockets for simplicity and better compatibility with serverless deployments. However, managing multiple concurrent SSE connections and ensuring proof delivery required careful connection pooling and retry logic.
3. Autonomous Agent Reliability: Building an agent that could autonomously discover providers, verify payments, and handle failures without human intervention was complex. We implemented multiple fallback mechanisms:
- On-chain registry queries with API fallbacks
- Payment verification with retry logic and timeout handling
- Spot-check fraud detection (10% random reruns) to balance security and performance
- Budget controls to prevent runaway spending
4. Cryptographic Proof Chain Integrity: Ensuring the proof chain remained tamper-proof required careful design. Each step's hash must include the previous hash, creating an immutable chain. We had to handle edge cases like network failures mid-execution and ensure proofs could be independently verified by third parties.
5. X-402 Payment Protocol Implementation: Creating a novel HTTP-native payment protocol that works with standard HTTP clients was challenging. We had to design the flow carefully: return 402 status → consumer pays on-chain → retry with transaction ID → verify payment → execute job. Handling payment verification timing and blockchain confirmation delays required robust retry logic.
6. Escrow Contract Security: Designing an escrow contract that protects both providers and consumers was critical. We implemented:
- Consumer-only release with proof hash verification
- Timeout-based refunds for failed jobs
- Protection against re-entrancy attacks
- Proper access controls for admin functions
7. Frontend State Management: Managing real-time state updates from SSE streams while keeping the UI responsive was challenging without a framework like React. We built a custom event bus system and implemented efficient DOM updates to handle high-frequency proof updates.
Accomplishments that we're proud of
1. Complete Decentralized Architecture: We built a truly peer-to-peer system with no central authority. Providers register permissionlessly on-chain, consumers discover them via blockchain queries, and payments flow directly through smart contracts. No middleman, no central server controlling the marketplace.
2. Novel X-402 Payment Protocol: We created an innovative HTTP-native payment protocol that enables standard HTTP clients to interact with blockchain-paid APIs. This bridges Web2 and Web3, making decentralized compute accessible to developers who don't want to learn smart contract development.
3. Cryptographic Proof-of-Compute System: Every job generates a complete 9-step proof chain with SHA-256 hashing and chain linkage. This provides irrefutable evidence of execution that can be independently verified by anyone—solving the trust problem in decentralized compute.
4. Autonomous Agent Economy: Our agent system operates completely autonomously with budget controls, fraud detection, and automatic payment verification. This demonstrates a vision of autonomous economic agents that can participate in decentralized markets without human intervention.
5. Production-Quality Smart Contracts: We leveraged modern Algorand features (algopy, BoxMap storage, inner transactions, ARC-4 interfaces, ARC-56 specs) to build contracts that are type-safe, scalable, and gas-efficient. The contracts handle real money and need to be bulletproof.
6. Beautiful, Functional UI: We designed a custom "Stitch" design system with dark themes, glassmorphism, and real-time updates that rivals centralized cloud provider UIs. The interface makes blockchain complexity invisible to end users.
7. Comprehensive Testing: We built extensive test coverage including on-chain integration tests, unit tests for the agent system, and end-to-end flow testing. This ensures reliability for a system handling real financial transactions.
What we learned
Technical Learnings:
1. Algorand's Box Storage is Powerful: BoxMap storage solved our scalability challenges elegantly. Unlike global/local state, boxes provide virtually unlimited storage while maintaining on-chain verifiability. This is perfect for marketplace applications with many providers.
2. algopy > PyTeal:
Using algopy instead of raw PyTeal dramatically improved development speed and code safety. Type checking, better error messages, and Python-native syntax made smart contract development feel like regular Python programming.
3. Server-Sent Events are Underrated: SSE provided a simpler alternative to WebSockets for real-time updates. They work better with serverless deployments, have automatic reconnection, and are easier to implement. Perfect for one-way server-to-client streaming.
4. Autonomous Agents Need Robust Fallbacks: Building reliable autonomous systems requires multiple layers of fallbacks. We learned to always have: on-chain + API fallbacks, retry logic with exponential backoff, timeout handling, and budget controls to prevent runaway behavior.
5. Proof Systems Require Careful Design: Creating tamper-proof cryptographic chains requires thinking through every edge case: network failures, partial executions, replay attacks, and independent verification. The chain linkage pattern (each hash includes previous hash) was crucial.
Product Learnings:
1. Decentralization Requires Trust Mechanisms: Users won't trust a decentralized marketplace without verifiable execution guarantees. Our proof-of-compute system and reputation badges were essential for building trust in a permissionless environment.
2. Developer Experience Matters: The X-402 protocol makes blockchain payments feel like regular HTTP APIs. Abstracting blockchain complexity is crucial for mainstream adoption—developers shouldn't need to understand smart contracts to use decentralized compute.
3. Real-time Feedback is Critical: Users expect instant feedback. Our real-time proof broadcasting and progress updates make the system feel responsive and trustworthy, even though blockchain confirmations take seconds.
4. Escrow Protection is Non-Negotiable: Both providers and consumers need protection. Escrow contracts that lock funds until verified completion, with timeout refunds for failures, were essential for a fair marketplace.
What's next for Kinetic
Phase 1: Real GPU Integration (Weeks 1-4)
- Replace simulated compute with actual GPU job execution
- Integrate Docker/Kubernetes for containerized workloads
- Support popular ML frameworks (PyTorch, TensorFlow, JAX)
- Implement job templates for common tasks (Stable Diffusion, LLM fine-tuning)
Phase 2: Enhanced Trust & Security (Weeks 5-8)
- Implement provider staking/slashing for stronger fraud deterrence
- Add multi-party verification for high-value jobs
- Store proof hashes on-chain for permanent auditability
- Implement zero-knowledge proofs for private computation
Phase 3: Advanced Features (Weeks 9-12)
- Payment streaming for per-second billing
- Multi-provider job splitting for large workloads
- Advanced reputation system with uptime tracking and user reviews
- Mobile app for iOS/Android
Phase 4: Ecosystem Growth (Weeks 13-16)
- Developer SDK for programmatic API access
- Webhook integrations for CI/CD pipelines
- Marketplace for pre-trained models and datasets
- Community governance via DAO
Phase 5: MainNet Launch (Weeks 17-18)
- Security audits by third-party firms
- MainNet contract deployment
- Genesis provider onboarding program
- Marketing campaign and partnerships
Long-term Vision:
- Cross-chain bridges (Ethereum, Solana) for broader access
- Decentralized job queue using IPFS
- Proof compression for reduced storage costs
- Integration with major AI platforms and tools
- Become the go-to decentralized compute marketplace for AI/ML workloads
Log in or sign up for Devpost to join the conversation.