Protocol documentation · v0 prototype

Duckie docs

Everything about how Duckie thinks, what it never does, and how to run the interface.

Overview

Duckie Agent is an autonomous Web3 intelligence companion. It researches tokens, tracks wallets, detects on-chain risk, monitors positions, and prepares wallet-approved transactions — then translates all of it into decisions you can actually understand.

The system is organized around a single conversational core (Duckie Core) supported by a swarm of specialized agents. You talk to one duck; the flock does the work.

The current build is a frontend prototype. All analysis output is labeled demonstration data until live data providers are connected via the environment configuration.

Architecture

A request flows through four stages: intent parsing, data collection, risk evaluation, and action synthesis.

USER REQUEST
   └─▶ DUCKIE CORE (intent parsing, memory)
         ├─▶ ONCHAIN DATA   (contracts, holders, liquidity)
         ├─▶ RISK ENGINE    (heuristics, simulations, flags)
         └─▶ MARKET SIGNALS (price, flows, narratives)
   └─▶ CLEAR ACTION (plain-language answer + prepared steps)

The Swarm

Five specialist agents extend the core: Scout Duck (opportunity discovery), Guard Duck (contract security), Whale Duck (smart-money tracking), Farmer Duck (yield analysis), and News Duck (narrative synthesis). Each specialist can be activated independently or invoked automatically by the core.

Safety model

Duckie is strictly non-custodial. It can analyze and prepare actions, but every transaction requires explicit confirmation in your own wallet. Duckie never holds funds, never signs on your behalf, and never asks for private keys or seed phrases.

  • →Transactions are simulated before they are presented
  • →Every prepared action includes a human-readable preview
  • →Risky contracts and permissions are flagged before interaction
  • →Existing token approvals are surfaced and scored
  • →Execution always ends at your wallet's confirmation screen
No legitimate interface will ever ask for your seed phrase. If anything claiming to be Duckie does, close it.

Network modules

Ethereum-aligned, launching on Robinhood Chain

Duckie is an Ethereum-aligned agent. Its planned launch chain is Robinhood Chain — an Ethereum Layer-2 built on the Arbitrum stack for real-world assets — which settles to Ethereum. That makes ETH the home base of the protocol, with other chains added as modules around it.

Duckie's interface is also prepared for BNB Chain, Solana, and Base as modular network adapters. Module status reflects the prototype roadmap, not live integrations or partnerships — Duckie is not affiliated with Robinhood.

  • →Robinhood Chain — planned launch chain (Ethereum L2)
  • →Ethereum — settlement layer Duckie aligns with
  • →BNB Chain & Solana — supported scanning modules in the prototype
  • →Base — additional Ethereum L2 module, planned
# .env.local
NEXT_PUBLIC_RPC_ROBINHOOD=…
NEXT_PUBLIC_RPC_ETHEREUM=…
NEXT_PUBLIC_RPC_BNB=…
NEXT_PUBLIC_RPC_BASE=…
NEXT_PUBLIC_RPC_SOLANA=…
"Different chains. One Duckie." — the agent's intelligence is chain-agnostic; the launch chain is where $DUCKIE and execution go live first.

$DUCKIE token

$DUCKIE is the utility token of the Duckie protocol: agent execution credits, advanced monitoring slots, premium intelligence modules, protocol-fee discounts, agent-node staking, governance, and developer rewards.

Contract address: TO BE ANNOUNCED. Any address claiming to be $DUCKIE before official announcement should be treated as fake.

Getting started

Run the interface locally:

npm install
npm run dev
# open http://localhost:3000

Copy .env.example to .env.local and fill in provider endpoints when connecting real data. With no configuration, the app runs entirely in labeled demo mode.