Many GPUs.
One model.Every shard accounted for.
Shardwood is building accountable inference lanes across independent GPUs. The private alpha now measures devices and verifies bounded browser work while real split-model execution remains gated.
Reading the coordinator now—no fallback numbers are displayed.
Split the model. Trace the work.
The innovation is not sharding by itself. It is a complete, bonded inference route where adjacent workers co-sign every useful handoff and each stage can be settled independently.
Capacity is fragmented
Useful GPUs live across homes, studios, labs and data centers. Isolated machines often cannot fit larger models.
Shardwood builds accountable lanes
Compatible devices become a short-lived model pipeline with measured topology, signed prices, bonds and auditable receipts.
Fund
Deposit the stable settlement asset and authorize a capped inference session.
Route
Match compatible GPUs and allocate contiguous bundles of model layers.
Verify
Co-sign each handoff and replay a sample through deterministic witnesses.
Settle
Commit one payout root and let each contributor claim with a proof.
Smart contract data without the smoke.
The private-alpha source now implements the core token, staking, settlement, slashing and recovery modules. It is pre-audit and not deployed; addresses, balances and transactions remain explicitly pending.
ShardwoodToken.sol
BUILT · PRE-AUDITFixed 420,690 SHWD supply with permit and voluntary burn; no mint, tax, blacklist or transfer pause.
permit · burn · burnFrom · totalSupplyGenesisAllocator.sol
BUILT · PRE-AUDITCreates the official token, exact allocation vaults, liquidity lock and capped contributor distributor.
distribute · token · contributorAirdrop · allocation vaultsCreatorTreasuryVault.sol
BUILT · PRE-AUDITHolds the fixed 10% creator allocation under one wallet, with an optional two-step controller handoff later.
disburse · proposeController · acceptController · cancelControllerTransferNodeRegistry.sol
BUILT · PRE-AUDITWorker identities, metadata commitments, operator self-bonds, terminal exits and attributable slashes.
registerNode · addSelfBond · requestExit · withdrawSelfBondNodeDelegationVault.sol
BUILT · PRE-AUDITNode-specific staking with a 24-hour warm-up, seven-day cooldown, stable-fee accounting and slash exposure.
delegate · activateDelegation · requestWithdrawal · claimRewardJobEscrowSettlement.sol
BUILT · PRE-AUDITCustomer-funded job caps, challenged payout roots, context-bound route proofs and failure refunds.
fundJob · proposePayout · finalize · routeFinalizedFee · refundProtocolFeeRouter.sol
BUILT · PRE-AUDITVersion-pinned seven-category settlement with exact conservation and executor-favoring rounding dust.
routeFees · scheduleFeeConfig · executeFeeConfig · feeConfigByHashSlashController.sol
BUILT · PRE-AUDITEvidence replay protection and atomic self-bond-first penalties split equally between burn and recovery.
resolve · maxBps · setResolver · processedEvidenceContributorAirdrop.sol
BUILT · PRE-AUDITPrefunded cumulative contributor roots with domain separation, challenge delay, invalidation and a hard cap.
publishRoot · invalidateEpoch · claim · leafHashA fixed supply. A disclosed path for every token.
The custom contract design fixes supply and allocation rules before deployment. The launch route is still under review, and no token, sale, staking pool, fee stream or contract address is live.
Minted once by the proposed genesis allocator. Supply may decline through real onchain burns, but no contract role can increase it.
allocations
Bond capacity. Delegate to a named node.
SHWD is proposed for operator bonds, node-specific delegation and useful-work contributor programs. Delegation carries the selected node pool's disclosed slash risk; it does not create fixed yield.
Customers fund work. Finalized work funds rewards.
Customers pay an approved stable settlement asset. USDG is proposed but not selected until an exact Robinhood Chain contract is verified. Failed, disputed and unused work remains refundable.
Design hypothesis only. The stable asset and final routing parameters require deployment review, security testing and published contract addresses.
Named capacity pool
No paid customer work means no stable-fee reward. Principal may be reduced by a valid node-specific slash.
Real tokens or no burn.
Holder-approved burns and finalized slashes are supported; slashes split actual SHWD 50% to burn and 50% to recovery. Node count never creates a synthetic burn.
BUYBACK RESERVE: 0% AT LAUNCH10% disclosed. No vesting.
42,069 SHWD is proposed for immediate project costs under one controller, with an optional two-step controller handoff later.
ONCHAIN INFLOWS AND OUTFLOWSCustom suite or compatible launchpad?
The choice must preserve fixed supply, exact allocations, treasury custody, staking compatibility and auditable fee behavior. A launchpad token would require contract integration changes.
STATUS: UNDER REVIEWUseful work, not idle emissions.
The 35% prefunded allocation may reward accepted useful work. The production scoring system, rolling caps and root builder are not finished.
UPTIME ALONE EARNS ZEROThese are proposed technical parameters, not a sale, investment promise or earnings guarantee. Final launch terms depend on product readiness, legal review, security audits and a public deployment manifest.
Say exactly what is proven.
Verification is progressive. The interface distinguishes route attribution from stronger evidence instead of presenting every hash as proof of correct AI computation.
Signed route
Adjacent workers co-sign the causal path. Proves attribution, ordering and agreed metering.
Does not prove computation.Witness replay
Random deterministic stages are independently repeated before final settlement.
Sampled evidence, not full coverage.Attested execution
Future trusted-execution or cryptographic evidence strengthens selected operations.
Not available in this prototype.A concept paper that starts with the limits.
Technical scope, trust assumptions, contracts, verification, economics and the path from a controlled prototype to an audited network.
01System thesis+
Shardwood coordinates independent GPUs into temporary inference pipelines. The chain is the settlement and security layer; model execution remains offchain. The initial goal is to let compatible smaller GPUs collectively fit models that may not fit on one participating device.
02Elastic Shard Routing+
A disclosed scheduler evaluates VRAM, runtime compatibility, measured bandwidth, round-trip latency, reliability, signed price and bond status. It assigns contiguous layer bundles to a short-lived route. Early releases intentionally use a limited coordinator and allowlisted operators while measurable responsibilities are hardened.
03Causal Handoff Receipts+
Every stage signs a commitment to the job, model manifest, shard index, salted input and output commitments, metered units, price and prior receipt. The receiving node co-signs the handoff. The ordered chain proves attribution and metering—not complete computational correctness.
04Witness verification+
A configurable sample of deterministic stages is replayed by independent witnesses. Agreement supports settlement; disagreement can delay a payout and open a challenge. Future verification tiers may add trusted-execution attestations or cryptographic proofs for selected operations.
05Bonds and delegation+
Operators maintain a self-bond. Token holders may delegate to a specific node or capacity pool and receive a defined share of fees only when that capacity participates in completed paid work. Delegators share disclosed node-specific slash risk and use a cooldown to exit.
06Settlement+
Accepted receipt paths and payout schedules are compressed into Merkle roots. Robinhood Chain contracts release the stable settlement asset through inclusion proofs, preserve challenge windows, and minimize calldata. Prompts, outputs and intermediate activations never belong onchain.
07Threat model and limits+
The protocol considers forged receipts, node collusion, replay, model substitution, false capacity, witness bribery, coordinator manipulation, key compromise and unsafe administration. Wide-area pipelines may increase latency, witness sampling can miss invalid work, and volunteer nodes are not inherently private.
08Progressive decentralization+
The credible path begins with one model, two or three nodes in one region, deterministic replay and low-value testnet settlement. Decentralized scheduling, broader model support, privacy systems and advanced verification are later research milestones, not launch claims.
Wide-area sharding can add latency and reduce reliability. Simulations are not benchmarks.
Receipt signatures prove attribution; sampled replay can still miss invalid work.
Volunteer operators may observe prompts, activations, outputs or timing information.
Fees depend on paid usage. Bonded assets may be penalized. No return is guaranteed.
Light the route. Earn every gate.
The roadmap is an inference path, not a calendar of promises. Every node lights only after its measurable completion gate is satisfied.
Foundation
Brand system, concept interface, ShardLab simulator and the v0.2 technical paper.
Public materials clearly separate proposed, simulated, measured and deployed work.
Local split proof
Qwen3-0.6B across two local processes with partial weight loading and signed handoffs.
Distributed logits and output match a single-process reference across repeatable runs.
Cross-border WAN
Connect two independent computers in the USA and Canada over an authenticated route.
Publish hardware, model revision, RTT, throughput, reconnect behavior and receipt artifacts.
Elastic routing
VRAM-aware placement, bandwidth scoring, direct return, retry and live stage replacement.
A route survives a node loss and either completes safely or restarts without false settlement.
Private GPU alpha
Installer, node registry, metering and an allowlisted network of independent operators.
Five to ten operators complete hundreds of test jobs with disclosed reliability metrics.
Testnet settlement
Stable-asset escrow, operator bonds, payout roots, claims and dispute windows on chain 46630.
Contracts pass adversarial tests, capped-value trials and independent security review.
Public beta
Public node onboarding, an inference API, receipt explorer and limited paid workloads.
Recurring paid demand and stable job completion exist without unresolved critical incidents.
Token decision
Evaluate $SHWD only after the network demonstrates technical need and real customer usage.
Requires legal review, audited contracts, disclosed vesting and a utility the product needs.
See fragmented GPUs become one accountable inference lane.
Configure the hardware, split the model, stress the network and inspect how useful work and fees move through the system.