Human Bond

Partnership infrastructure for humans. Two World-ID-verified partners each get a private AI agent, plus a third agent representing their bond. The agents manage the partnership, including: multi-sig wallet, decisions and communications - with clean exit/dissolution. Ideal for: marriages, co-ownership, business partners, friends/family. Live on World Chain mainnet.

HumanBond began at ETHGlobal Buenos Aires 2025. For Lisbon we shipped three major additions: a 50/50 income split contract, a three-agent AI layer, and World's new NFC Credentials integration.

Smart contracts (Foundry, World Chain Mainnet) Four contracts, all deployed and verified: HumanBond.sol, VowNFT.sol (soulbound, non-transferable), MilestoneNFT.sol, and TIMEToken.sol (ERC-20). When two partners accept a bond, HumanBond.sol calls VowNFT.sol to mint a soulbound NFT and TIMEToken.sol to mint their first TIME — all in one transaction. New at Lisbon: finalizeWorkAndDistribute() mints Work TIME and splits it 50/50 between both partners atomically on payment receipt. The non-market partner (caregiver, homemaker) receives equal income — enforced in code, no trust required.

World ID — three credential tiers World ID is load-bearing, not cosmetic. Bond formation uses two separate external nullifiers (propose-bond and accept-bond) so a propose proof cannot be replayed as an accept. New at Lisbon: we integrated World's NFC Credentials beta — partners can scan their passport NFC chip to extract ZK proofs of age >18 and jurisdiction, stored immutably in the VowNFT. Also integrated: Selfie Check beta for lower-friction onboarding. Identity tier (Selfie / NFC / Orb) is recorded in the bond.

Three AI agents (World AgentKit + 0G) Each partner has a Human-Backed Agent anchored to their World ID nullifier via World AgentKit. A third Partnership Agent acts as neutral mediator — it serves the bond, not either partner. Agent preference models are built from each partner's on-chain TIME governance staking history and income split records. Inference runs on 0G Compute inside a TEE enclave — neither partner can see the other's agent deliberations, only the output. Preference models are stored encrypted on 0G Storage and evolve over time. When both agents agree on a spending decision, both partners must explicitly approve before anything executes.

ENS — partnership and agent identities During bond formation, partners register a shared ENS subname: partner1-partner2.humanbond.eth. Each of the three agents also has an ENS identity. Text records store the VowNFT pointer, identity tiers, and 0G Storage endpoint. The Partnership Registry is queryable by anyone: one ENS resolution returns the shared receiving address and partnership status.

The hacky part We built a chat-based interface between the agents and the partners — so when a dispute arises, each partner talks to their own agent, the agents negotiate in the background via the Partnership Agent, and the mediated result surfaces as a readable summary. The Partnership Agent reads raw on-chain event history (not just metadata) to infer each partner's actual values — what they consistently allocated TIME to — rather than relying on self-reported preferences. The gap between what people say they want and what their on-chain history shows they actually want turned out to be the most interesting design problem of the weekend.