weft

Demo

About

weft is an autonomous coordination layer for the post-company economy. It solves four problems that currently require corporations, lawyers, and managers: identity, funding, verification, and settlement — for teams of humans, agents, or both. A builder posts a project with discrete milestones and a funding target. Backers stake capital against specific milestones rather than taking equity. A Hermes Agent instance then acts as the autonomous verifier — reading git commits, deployment addresses, on-chain activity, and usage signals to determine whether a milestone was genuinely hit. When it is, KeeperHub releases the staked capital automatically. Every verified action — milestone funded, work completed, capital released, revenue earned — gets written as a structured attestation to 0G Storage as a permanent evidence archive, with a human-readable summary pushed to the builder's ENS profile as text records. The ENS name becomes a portable, machine-readable track record: what they shipped, who co-signed it, what it earned, how long it lasted. This record travels with the builder across every project they touch. Agents participate as first-class co-builders. They hold project shares via ENS subnames, their output history is stored and verified exactly like a human's, and their earnings are settled the same way. Multiple Hermes nodes reach consensus on milestone completion over Gensyn's AXL peer-to-peer network — no central coordinator, no single point of trust. The result is a composable primitive: reputation that compounds, capital that flows programmatically, and verification that requires no institution to back it.

How it's made

Weft is built around a Hermes Agent instance as its autonomous core — the piece that makes trustless verification possible without a human intermediary. We extended Hermes with three custom skills: a GitHub skill that reads commit history and PR merges, a deployment skill that checks contract activity on 0G Chain, and a usage skill that reads onchain interaction counts. When a milestone deadline passes, Hermes runs all three skills, synthesises the evidence using Kimi models into a structured attestation object, and makes a binary verified/unverified determination. That attestation is the trigger for everything downstream. The evidence archive lives on 0G Storage. Raw evidence blobs — git snapshots, deployment proofs, usage logs, the full Kimi synthesis — are written to 0G's Log layer permanent, append-only keyed by milestone hash. The structured attestation summary is written to 0G's KV layer for fast lookup. A third KV key weft:milestone:<hash>:state holds the agent's real-time working memory — the current verification state, timestamp, and evidence root — updated on every cycle. This is the "KV for real-time state + Log for history" architecture that makes Weft a genuine Digital Twin. The receipts are always there even if the frontend isn't. For multi-verifier consensus, we run three Hermes nodes that each independently verify the same milestone and broadcast their determination over Gensyn's AXL peer-to-peer network. AXL handles encrypted routing and peer discovery with zero infrastructure — each node talks to localhost and AXL handles the mesh. A 2-of-3 agreement triggers the capital release. The live AXL node is publicly verifiable at https://weft.thisyearnofear.com/api/status/axl — real public key, IPv6 address, and two connected Gensyn bootstrap peers. This is genuine distributed verification with no coordinator, using AXL's built-in MCP support for structured agent-to-agent messaging. On-chain, the milestone staking contract is deployed on 0G Chain chain 16602. Builders call createMilestone() which locks ETH against a specific outcome. The Hermes agent — once consensus is reached across AXL nodes — calls submitVerdict() which triggers KeeperHub to execute the capital release. We route through KeeperHub specifically because autonomous agent-triggered transactions are exactly where gas spikes and MEV extraction hurt most — KeeperHub's retry logic and private routing mean we can trust the release to actually fire. The creative layer is powered by Kimi and fal.ai. After each successful verification, Kimi generates a multi-chapter Builder Journey chronicle — narrative non-fiction from the blockchain. Each milestone is a thread; peer consensus is the interlacing; the final fabric is the verified project story. fal.ai generates a unique AI-woven milestone swatch image whose visual character is driven by the verification metrics callers, commits, peer signers. Together, the chronicle and swatch form a shareable artifact that transforms a cold verified=true into a human moment. Technology provides the warp. Liberal arts provide the weft. Identity is entirely ENS-based. The protocol itself has an ENS identity at weft.thisyearnofear.eth — mirroring the frontend URL weft.thisyearnofear.com — with six text records live onchain: url, description, com.github, weft.role, weft.contract.0g, and weft.tagline. ENS is the entry point, not just the exit point: the frontend resolves any .eth name to an address and loads their milestone history. Verified builders automatically receive subnames under thisyearnofear.eth as portable onchain credentials — <project>.thisyearnofear.eth — issued autonomously by the daemon when WEFT_ENS_PARENT is set. The ENS profile becomes a machine-readable reputation graph that any future backer, collaborator, or agent can query before engaging. The notably emergent thing: Hermes's persistent memory means verification patterns accumulate in 0G Storage KV across milestones, making each subsequent verification informed by prior ones. We didn't build explicit heuristic generation — it's an emergent property of the architecture. We kept it.