Build and operate on Smainer
Smainer is a Starknet-settled compute network: Telegram is the first demand interface, providers supply compute, the relayer coordinates execution, and contracts settle STRK rewards and protocol fees.
Privacy AI path
Telegram request, MiniApp payment, relayer scheduling, provider execution, callback, and settlement.
Developer API
Task schema, callback contract, HMAC verification, status polling, and sandbox access plan.
Provider runtime
Desktop app, Linux daemon script, WebSocket lifecycle, logs, diagnostics, and node eligibility.
Security model
No prompt retention by default, isolated execution, signed results, and staged public release gates.
Live System
Task lifecycle
The production beta path moves from Telegram payment approval through relayer scheduling, Starknet escrow, provider execution, result callback, and settlement.
Telegram bot
Relayer API
Starknet escrow
Provider node
Callback result
Implementation guide
Demanders
Connect a Starknet wallet, submit task requirements, approve payment, then receive results by status polling or callback.
Providers
Install Smainer Desktop or run backend/provider/local-provider-daemon.sh, configure wallet and relayer URL, then keep the provider online.
Integrators
Use signed callbacks and store only the data your product needs. Treat task payloads as sensitive user data.
Relayer API
/api/v1/tasks
Submit an AI or custom compute job with requirements and callback metadata.
/api/v1/tasks/{task_id}
Read lifecycle state, provider assignment, result, and settlement fields.
/api/v1/tasks/{task_id}/callback
Receive signed result callbacks for product integrations.
/api/v1/nodes
List active provider nodes and scheduler-visible capabilities.
/api/v1/health
Service health for relayer, Redis, WebSocket, and Starknet connectivity.
/api/v1/stats
Network counters for task throughput, active providers, and settlement volume.
Cairo contract surface
create_task
Escrow STRK-compatible payment and record task metadata hash.
assign_task
Bind an eligible provider to a task after scheduler selection.
submit_proof_and_claim
Submit result proof and settle provider, gas subsidy, and treasury split.
register_node
Register provider address and capability tier.
get_task
Read creator, provider, amount, status, hashes, and timestamps.
get_user_earnings
Read accumulated provider earnings by Starknet address.
Open-source rollout
Step 1
Public docs and installer
Publish the website docs, desktop release links, setup guides, and responsible disclosure path.
Step 2
Provider and SDK surface
Open the provider daemon, task client examples, callback verifier, and local dev instructions after secret scanning.
Step 3
Contracts and protocol docs
Publish Cairo contract interfaces, fee accounting notes, deployment status, and testnet/devnet reproducibility guides.
Step 4
Full public beta workflow
Move issues, examples, roadmap, and support triage into public GitHub/Discord channels where safe.
Support and beta limits
Payment truth: STRK approval, escrow, provider payout, gas subsidy, and treasury fee should be verifiable against Starknet settlement events.
Provider truth: scheduler fairness means a task can run on any eligible active node, not always the local desktop node.
Security truth: deployment files, secrets, and unsafe operational details stay private until release gates pass.
Security expectations
Public beta users and builders should treat payloads, private keys, and callback secrets as production-sensitive material.