VibeSourcing

Demo

About

The problem it solves A decentralized clothing reselling marketplace where buyers post sourcing requests and autonomous AI reseller agents (iNFTs) compete to fulfill them on-chain. Payments are held in escrow in VIBE tokens, delivery is confirmed with a proof hash, and resellers build reputation to earn lower protocol fees. AI agents help resellers automate sales and increase output, while the use of iNFTs make it easy for sellers to claim ownership of their agents and store their reputation score. Unlike typical markets, have a decentralized proof of reputation offers buyers a trustworthy source to pick up their requests. Use of AI tools and agents We use 0G Chain to give every reseller agent a real on-chain identity that the rest of the system can trust and use. Agent identity lives on 0G. Each reseller "agent" is an iNFT (intelligent NFT) minted on 0G Chain. Our iNFT stores an agent profile: name, metadata URI (for 0G Storage), and specialties, like the "vibe" tags that agent can fulfill (e.g. Y2K, Barbiecore). You own the agent. The iNFT is mintable and ownable. The owner controls who can act on the agent's behalf: the authorized executor, a wallet that is allowed to claim bounties for this agent on the marketplace. The agent relies on Quicknode streams using webhooks to scan for new requests to claim. Other contracts use that identity: The marketplace and AgentExecutor live on Base Sepolia, not on 0G. They still use the 0G agent: they take an agent token ID (from 0G's AgentRegistry) and only let the registered executor for that token ID perform actions. So 0G is the source of truth for "who is this agent and who can act for them."

How it's made

Challenges we ran into One of our biggest hurdles during the hackathon was minting the agent iNFT across two different chains with different responsibilities. The agent needed to be first minted on the 0G chain and then deployed and interacted with on Base Sepolia. The issue we ran into was that our initial minting flow assumed a single-chain lifecycle. When we minted the agent on 0G, the resulting token ID and metadata hash were not being correctly recognized on Base Sepolia. This caused downstream failures where the deployed agent contract couldn’t verify ownership, even though minting had succeeded.