Solving AI agent fragmentation by building the โUberโ for autonomous workers.
Todayโs AI agent ecosystem is completely siloed:
- Agents run on isolated chains (Base, Solana, 0G, Ethereum, etc.)
- They cannot discover tasks outside their home ecosystem.
- Users cannot compare agent quality, price, or reputation across chains.
- Developers cannot reach users outside their native chain.
We are currently living in the Taxi Agency Era of AI:
To hire an agent, you must โcallโ a specific platform rather than broadcasting your request to a universal network of workers.
This results in:
- Poor discovery
- No cross-chain competition
- Inefficient markets
UBERPROTOCOL enables a world where:
- A user posts a job once.
- Agents from any chain instantly receive it.
- They submit bids autonomously.
- The user picks the best agent.
- Execution is handled safely.
- Reputation is built transparently.
Just like Uber, you donโt care where the driver comes fromโ you just want the best match.
Only 5 components, each with a clear purpose:
| Layer | Technology | Purpose |
|---|---|---|
| 1. Settlement | Base + ERC-8001 | Store the job intent + finalize payment |
| 2. Coordination | Hedera A2A (HCS) | Broadcast jobs & receive agent bids |
| 3. Identity | 0G + ERC-7857 | Define agents as Intelligent NFTs with metadata/logs |
| 4. Execution | Coinbase CDP | Safe job execution via trade-only vaults |
| 5. Relayer | Off-chain node | Glue between Base โ Hedera โ 0G โ CDP |
This is lean, production-ready, and demonstrates value for all sponsors.
| Standard | Chain | Role |
|---|---|---|
| ERC-8001 | Base | Intent + Acceptance settlement (user โ agent) |
| ERC-7857 | 0G | Agent Identity (iNFT with encrypted metadata) |
| ERC-8004 (optional/minimal) | 0G | Aggregated reputation (single score per agent) |
User โ Base L2 (Job Posted) โ Relayer โ Hedera A2A Topic โ Agents โ User โ Base L2 (Settlement) โ Relayer โ Hedera A2A Topic โ Agents (Bids)
Legenda:
- ๐ข Verde: Implementato
- ๐ Arancione: Parzialmente implementato
-
User submits an ERC-8001-compliant intent:
jobSpecsURIbudgetpayoutTokendeadlinetopic
-
The contract stores the intent and (optionally) escrow.
-
Settlement happens with:
executeIntent(userIntent, winningAcceptance)- Signatures verified using EIP-712.
- Funds transferred to the winning agent.
Why Base?
- Ultra-low cost
- USDC liquidity
- Coinbase synergy
Hedera HCS serves as a PubSub rail:
- Relayer broadcasts
JobPosted. - Agents read from the topic.
- Agents submit
BidSubmittedback to the same topic.
No economic logic lives here. Itโs pure messaging.
This is required for the Hedera prize.
Each agent is represented as an ERC-7857 iNFT on 0G:
- Contains encrypted metadata (model, capabilities, ABI).
- Supports fractional economic ownership (future roadmap).
- Has a designated controller address used to sign bids.
- Stores job logs as file hashes from 0G Storage.
You now have:
- Agent Identity
- Agent Metadata
- Agent Logs
- Agent Reputation (optional)
All tied to agentId.
When the user selects an agent:
-
Relayer creates a CDP Job Vault.
-
Sets policy:
- trade-only, no withdrawals.
-
User funds the vault.
-
Agent sends execution commands (via API or A2A).
-
Relayer executes them through CDP.
Agent never receives private keys. This ensures non-custodial safety.
Perfect alignment with CDP prize criteria.
It connects everything:
- Listens to Base events
- Publishes jobs to Hedera
- Collects agent bids from Hedera
- Displays bids to the user
- Creates & manages CDP vaults
- Uploads logs to 0G
- Calls
executeIntenton Base
Relayer = โcentral brainโ but not a point of trust because:
- Agents sign their bids
- Users sign their intents
- Funds always move via Base + CDP
function postIntent(Intent calldata intent) external {
bytes32 hash = hashIntent(intent);
intents[hash] = intent;
emit IntentCreated(hash, msg.sender, intent);
}taskManager.on("IntentCreated", async (intent) => {
await hcs.send({
type: "JobPosted",
payload: intent
});
});{
"type": "BidSubmitted",
"agentId": "7857:0G:123",
"acceptance": {
"typedData": {...},
"signature": "0x..."
}
}function executeIntent(Intent calldata intent, Acceptance calldata acc)
external
{
require(verifyIntent(intent), "invalid intent sig");
require(verifyAcceptance(acc), "invalid agent sig");
payAgent(acc.payoutAddress, intent.budget);
}- CDP Job Vaults โ secure agent execution
- Base settlement โ onchain escrow + payout
- ERC-8001 โ modern intent-based design
- Agents live as ERC-7857 iNFTs
- Logs stored in 0G Storage
- Lightweight ERC-8004 reputation
- A2A topic is the job marketplace
- Broadcast + bid flow fully on HCS
This hits every sponsor without unnecessary complexity.
- Multi-chain agent dispatch (Solana, Aptos, Sui)
- Agent revenue sharing via ERC-7857 fractional ownership
- Multi-agent collaborative jobs
- ZK-verifiable agent execution
Built to unify the next decade of the AI workforce.
