Colony

Agent Swarm that collaborates to manage portfolios to optimize yields through Tokenized Stocks .

Colony

Created At

HackMoney 2026

Project Description

Colony is a multi-agent DeFi swarm built on ElizaOS that manages USDC-denominated portfolios across Solana and Ethereum. Specialized agents handle bridging, RWA acquisition, lending/leverage, and risk monitoring to optimize yield through Real-World Assets (RWAs) with an execution-first workflow

The problem

  • Cross-chain yield requires too many manual steps.
  • Strategies are fragmented across bridges, DEXs, and lending markets.
  • Most bots are single-threaded and slow to react to risk.

What Colony does (end-to-end)

  1. Accept USDC deposits.
  2. Bridge liquidity cross-chain (Arc).
  3. Swap USDC → tokenized RWAs (Uniswap on EVM).
  4. Move assets to Solana and collateralize on Kamino.
  5. Borrow USDC and reinvest to compound (loop).
  6. Monitor risk + news continuously and rebalance when needed.

Why a swarm (the key idea)

  • Split the workflow into specialists.
  • Coordinate via shared state and strict step order.
  • Act first, report after.
  • Log failures and continue instead of blocking.

The 4 core agents

  • Manager: single user interface, orchestration, final summaries.
  • Treasurer: bridging, custody flows, RWA acquisition, settlement.
  • Strategist: Kamino collateral, borrow loops, LTV/health management.
  • Guardian: news + risk monitoring, alerts, triggers emergency actions.

What makes it work (integrations)

  • Arc: wallets, balances, cross-chain transfer/BridgeKit.
  • Uniswap: USDC ↔ RWA swaps on Ethereum.
  • Kamino: lending + leverage loops on Solana.
  • DeFi News: market context and risk signals.
  • Optional extensions: Circle/CCTP, Morpho, plugin-swarm.

Primary user workflows

  • Deposit: deposit → bridge → swap into RWAs → collateralize → borrow → reinvest.
  • Withdraw: unwind Kamino → swap RWAs → USDC → bridge back to user.
  • Risk response: Guardian alert → Strategist reduces leverage / repays / adds collateral.

Why it matters

  • Cross-chain by design: pick the best venue per step.
  • Fewer clicks: automation replaces repetitive ops.
  • Faster reaction time: risk monitoring + automated rebalancing.
  • Built for demos and iteration: Bun + ElizaOS dev workflow.

How it's Made

  • ElizaOS swarm of 4 agents (Manager, Treasurer, Strategist, Guardian) coordinating via shared state.
  • Plugins are the execution layer (bridge, swap, lend, monitor).
  • Workflows encode deposit, withdrawal, and risk response in a strict step order (act first, report after).
background image mobile

Join the mailing list

Get the latest news and updates