debacle

Decentralizing execution through an army of specialized agents. Submit your intent in plain text; our Orchestrator settles it on-chain using ENS identities, Li.Fi cross-chain routes, and Yellow Network clearing automating all possible DeFi workflows under a single prompt.

Want to earn yield on your idle USDC? Want to buy ETH? Want to directly transfer your BTC in $ to your Mom? Every such action is treated as an intent and can be performed in a single prompt via a network of specialized & secure agents present on the network. All agents that get registered on the marketplace have their unique ENS names as identities & also have to mandatorily perform KYA (Know your Agent) for participating in the network.

Orchestrator (backend): FastAPI service (app/orchestrator_server.py) exposing chat/orchestration and registry endpoints. It lazy-initializes an orchestrator agent that can analyze intents, discover agents, verify KYA metadata, and delegate work. Architecture Diagram

Agent Registry (discovery & reputation): In app/core/agent_registry.py. Holds AGENT_REGISTRY with AgentInfo metadata (id, type, endpoint, KYA, score, reputation, metrics). Supports ENS-based discovery and KYA verification, and selection algorithms (select_best_agent).

Workers & Tools (execution layer): Workers in app/workers/ implement concrete flows (swap, bridge, rebalancer). Tools in app/tools/ provide building blocks for swaps/bridges (e.g., lifi_tool.py, wrap_eth_tool.py, complete_swap_tool.py). Orchestrator delegates to workers or calls tools directly.

Smart Contracts: Contracts in contracts/src/ (e.g., MasterAgent.sol, AgentFactory.sol, Agent.sol) provide on-chain routing and execution primitives. Deploy/scripting is in contracts/script and broadcast.

Frontend: React + Vite app under frontend/ offering agent lists, deployment UI, and a chat-based orchestration interface that uses the orchestrator API.

Data & State: Off-chain state includes orchestrator session state, registry metrics, and KYA cards. On-chain state includes MasterAgent and AgentFactory/Agent deployments. The current registry is in-memory/dummy (replaceable by a DB).

Integrations / Sponsor details: LiFi (li.quest): Route discovery, swapping, depositing on Aave, opening a perp position onchain. Where used: app/tools/lifi_tool.py and any worker that performs bridging. Config: LIFI_API_URL, LIFI_API_KEY in app/config.py. Notes: validate quotes, token decimals, slippage and required approvals before executing.

Yellow Network (Nitrolite): sessioned off-chain transfers, channel lifecycle, adjudicator settlement. Where documented: YELLOW_INTEGRATION.md (step-by-step blueprint included). Where used: channel/session flows in workers/tools that need instant off-chain transfers or channel-based funding. Notes: always wait for L1 confirmations for create_channel and preserve proof_states for resize/close flows.

ENS: decentralized agent identity and KYA metadata hosting. Where used: app/core/agent_registry.py for resolution and KYA parsing. Config: ENS_ENABLED, ENS_RPC_URL, ENS_CACHE_TTL, and ENS_KYA_PREFIX in app/config.py.