DOCUMENTATION

AZUKA Docs

Everything you need to know about AZUKA, IronClaw, governance, staking, and the ecosystem.

TABLE OF CONTENTS

What is AZUKA?IronClaw AI Agent Security Engine On-Chain Governance Staking & Yield Contests & Earn Technical Architecture $IRONCLAW Token Community & Links

What is AZUKA?

AZUKA is a decentralized AI security and intelligence platform built on NEAR Protocol. At its core is IronClaw: an autonomous AI agent that operates inside Telegram and Discord communities, providing real-time threat detection, token research, portfolio tracking, and governance: all controlled by token holders on-chain.

Unlike traditional security tools that require constant manual oversight, IronClaw is always-on, always-learning, and community-governed. Every mission it runs, every prompt it follows, and every capability it unlocks is decided by $IRONCLAW stakers through on-chain proposals.

IronClaw AI Agent

IronClaw is the autonomous AI agent at the heart of AZUKA. Powered by NEAR AI, it operates 24/7 inside your community chats without any manual intervention.

/research [token]Full token report: price, market cap, liquidity, audit status, risk flags, and trust score

/summary [group]Summarize any public Telegram group's recent conversation into key points, tokens mentioned, and red flags

/verify [claim]Fact-check any claim against live data: returns verdict (Verified/False/Unverified) with sources

/portfolioMulti-wallet portfolio view with 24h P&L, token breakdown, and risk alerts

/scan [url/wallet]Scan any URL or wallet address against known phishing, scam, and malicious databases

/alert [token] [condition]Set price alerts: get notified when a token hits your target via DM

Auto: Link ScanningEvery URL shared in protected groups is silently scanned in real time

Auto: Wallet AlertsFlagged wallet addresses detected and warned before funds move

Security Engine

AZUKA's security engine runs continuously across all protected communities. It maintains a growing database of flagged URLs, malicious wallet addresses, known phishing patterns, and scam signatures.

When a threat is detected: whether it's a phishing link, an impersonator, or a flagged wallet: IronClaw acts immediately: the message is flagged, the community is warned, and the threat is logged for future reference. Community members can also submit reports via the /report command or the Telegram bot.

Phishing Detection

Real-time URL scanning against known threat databases

Wallet Screening

Cross-reference addresses with flagged wallet registries

Impersonation Detection

Pattern matching against admin names and profile signatures

Community Reporting

Crowdsourced threat intel via /report command

On-Chain Governance

AZUKA is fully governed by its token holders. Anyone who stakes $IRONCLAW tokens gains voting power proportional to their stake. Governance proposals can modify IronClaw's behavior in real-time: no team intervention required.

01

Stake $IRONCLAW

Lock tokens in the staking contract to earn yield and gain voting power.

02

Submit a Proposal

Propose a new mission, AI prompt update, or capability change. Types include: prompt_update, mission_update, config_change, and general.

03

Community Votes

72-hour voting window. Voting power equals staked amount across all pools. 51% quorum required to pass.

04

Auto-Execution

Passed proposals are executed on-chain. A governance listener picks up the event and updates IronClaw's active prompt or mission file automatically.

Staking & Yield

AZUKA uses a MasterChef-style staking mechanism designed for NEAR Protocol. Once the $IRONCLAW token launches, stakers will earn real yield from protocol revenue: not inflation.

Revenue from AZUKA subscriptions, premium features, and ecosystem fees flows into the reward pool. Rewards are distributed per-block proportional to each staker's share of the pool. Stakers can also earn bonus points through contests and community participation.

Contract

TBA: will be deployed at launch

Reward Source

Protocol revenue (real yield, not inflation)

Distribution

Per-block, proportional to stake

Governance Power

Voting power = total staked across all pools

Contests & Earn

AZUKA runs community contests (missions) where participants can earn points and climb the leaderboard. Missions range from bug bounties and security reports to content creation and community engagement.

When you participate in a contest, you submit proof of your work (a link, screenshot, or description). Submissions are reviewed by admins. Approved submissions earn you points that determine your tier and leaderboard rank.

01

Browse Missions

Visit the Earn page to see active contests with descriptions, rewards, and difficulty levels.

02

Submit Proof

Click Participate, provide a proof link (URL to your work), optional notes, and an optional screenshot.

03

Admin Review

Submissions are reviewed. Approved entries earn points; rejected ones include feedback.

04

Climb the Leaderboard

Points accumulate across all contests. Higher scores unlock tiers: Bronze, Silver, Gold, Diamond.

Submissions are stored in the AZUKA database and accessible via the admin panel (Dashboard Settings in the footer) and the backend API at /api/contests/:id (includes all submissions with user data).

Technical Architecture

AZUKA is a full-stack decentralized application combining a static frontend hosted on IPFS via NEAR's web4, a Node.js backend with PostgreSQL, a Telegram bot, and a Rust smart contract on NEAR mainnet.

Frontend

Next.js 16 + React 19, static export to IPFS via web4-deploy

Backend API

Express.js on port 3001: contests, leaderboard, governance, security endpoints

Database

PostgreSQL: users, wallets, contests, submissions, proposals, votes, flagged URLs/wallets

AI Engine

NEAR AI Cloud API (cloud-api.near.ai): LLaMA 3.1 70B for all agent tasks

Telegram Bot

node-telegram-bot-api: polling mode for dev, webhook for production

Smart Contract

Rust (near-sdk v5.1.0): MasterChef staking, NEP-141 rewards, on-chain governance (deploying at launch)

Hosting

IPFS via NEARFS, served at ironshield.near.page

Governance Listener

Polls chain for executed proposals, auto-updates agent prompt/mission

$IRONCLAW Token

$IRONCLAW is the native NEP-141 token of the AZUKA ecosystem on NEAR Protocol. It serves three core functions: governance voting power, staking yield, and access to premium features.

Token holders who stake $IRONCLAW earn real yield from protocol revenue and gain proportional voting power in governance. The token is the backbone of the community-controlled AI agent model.

Standard

NEP-141 (NEAR fungible token)

Chain

NEAR Protocol (mainnet)

Utility

Governance votes, staking yield, premium access

Contract

TBA: deploying at token launch

Community & Links

AZUKA is built by and for the NEAR community. Join us to participate in governance, earn rewards through contests, and help protect Web3 communities.

Telegram Community X (Twitter)AZUKA Bot NEAR Protocol Live App

THE AGENT MODEL

What Is IronClaw?

A community-governed autonomous agent operating on three core principles. The agent takes its orders from holders, executes without intermediaries, and evolves through on-chain governance.

Mission-Based Operation

The community assigns targets and objectives. The agent receives clear directives directly from token holders: security audits, alpha hunting, content production, and beyond.

Fully Autonomous Execution

No manual hand-holding. The agent executes approved missions independently, around the clock, and reports back with on-chain proof of work.

Community Prompt Control

Token holders vote on prompt updates. Agent behavior evolves under transparent, on-chain prompt versioning: governed, not dictated.

SPECIALIZATIONS

Six modes. One agent.

The community decides which modes IronClaw runs and when.

Security Auditor

Scam detection, rug protection, honeypot identification across NEAR dApps and tokens.

Alpha Hunter

Researches protocols, finds opportunities, and surfaces high-conviction insights to the community.

Treasury Manager

Manages community funds with risk parameters voted by holders. Performance is on-chain.

Content Engine

Produces ecosystem reports, threads, and explainers based on governance-approved direction.

Bounty Coordinator

Hunts bugs and inefficiencies across the NEAR dApp landscape and coordinates fixes.

Deal Flow Scout

Surfaces early-stage projects, grant opportunities, and partnership openings before they go public.

ARCHITECTURE

How It's Built

Three layers: governance, agent, revenue: connected by on-chain anchors. Off-chain only where speed matters; on-chain everywhere trust matters.

Governance Layer

On-Chain

Mission Registry Contract

Active missions, voting state, completion criteria

Prompt DAO Contract

Prompt versions, voting on updates, execution triggers

Staking Contract

Token staking, delegation, reward distribution

Agent Core

Off-Chain · On-Chain Anchored

LLM Engine

Base model with custom system prompts

Mission Executor

Parses approved missions, executes autonomously

Reporting Module

Logs outputs, results, and metrics back on-chain

Prompt Manager

Pulls active prompt version from on-chain governance

Revenue Layer

On-Chain

Treasury Contract

Holds protocol revenue, manages distributions

Fee Splitter

Automates revenue share to stakers, contributors, treasury

API Gateway Contract

Manages paid data access, rate limiting

EXECUTION FLOW

From proposal to payout

1

Mission Proposal

User submits mission proposal with parameters
Token holders vote (quorum + approval threshold)
Approved missions enter Mission Registry

2

Agent Execution

Agent polls Mission Registry for active tasks
Fetches current prompt version from Prompt DAO
Executes mission autonomously
Logs results on-chain (hash + summary)

3

Revenue Distribution

Revenue enters Treasury Contract
Fee Splitter allocates per tokenomics
40 % stakers · 25 % contributors · 20 % reserves · 15 % proposers

4

Prompt Updates

Community submits prompt improvement proposals
Token-weighted voting with time-lock
Approved prompts deployed after delay
Agent pulls new prompt on next execution cycle

SECURITY MODEL

Defense in depth

On-Chain Security

Multi-sig on treasury operations (3-of-5 minimum)
Time-locks on prompt updates (48-hour minimum delay)
Quorum requirements & vote escrow against governance attacks

Off-Chain Security

Agent runs in isolated execution environment
No direct wallet access: only signs pre-approved tx types
Rate limiting on external API calls and audit logging

Prompt Safety

Prompt proposals reviewed by security council pre-vote
Automated + manual harmful-prompt detection
Rollback mechanism for compromised prompts

TOKENOMICS DEEP DIVE

Money Flow, Fees & Parameters

Every dollar of revenue, every governance lever, every parameter: fully spec'd and on-chain.

Revenue Distribution Model

40%

25%

20%

15%

40% · Staker Rewards

Pro-rata to staked $IRONCLAW

25% · Contributor Rewards

Work-to-earn: prompt improvements, data, bug reports

20% · Treasury Reserves

DAO-controlled for ops, dev, emergencies

15% · Mission Proposers

Bonus for successful mission completion

Fee Structure

Service

Fee

Distribution

Premium Group Subscription

$50500 / month

100% Treasury → split per model

API Access (Data)

$0.001 per call

100% Treasury → split per model

Performance Fee (Alpha/Treasury)

10% of profits

100% Treasury → split per model

Staking Mechanics

Base Staking

Stake $IRONCLAW to earn share of protocol revenue
No lock-up required for base staking
Rewards accrue in real-time, claimable anytime

Boosted Staking

Active governance participants earn a multiplier
Voting in 80%+ of proposals → 1.5× multiplier
Submitting approved proposals → additional bonus

Mission Staking

Stake on specific missions you believe will succeed
Mission succeeds → earn up to 3× on staked amount
Mission fails → lose stake (redistributed to treasury)

Governance Parameters

Parameter

Value

Changeable By

Proposal Threshold

100,000 $IRONCLAW (0.01%)

Governance vote

Quorum

4% of circulating supply

Governance vote

Approval Threshold

60% of votes

Governance vote

Voting Period

5 days

Governance vote

Time-lock (Prompt Updates)

48 hours

Governance vote

Time-lock (Treasury)

72 hours

Multi-sig + Governance

Deflationary Mechanisms

Buyback & Burn

5% of treasury revenue used for market buybacks
Bought tokens are burned permanently
Reduces supply over time

Mission Slash Burns

Failed mission stakes are 50% burned
Remaining 50% returns to treasury
Creates a cost for low-quality mission proposals

LAUNCH SCOPE

Everything Ships at Launch

No phased rollout. No "coming soon." The full agent, full governance, full revenue stack: live on day one.

Core Infrastructure

Smart contracts on NEAR mainnet (Mission Registry, Prompt DAO, Staking, Treasury, Fee Splitter)
Agent infrastructure fully operational
LLM engine integrated with custom prompt system
On-chain anchoring for all agent actions

Governance System

Token-weighted voting live
Mission proposal and approval flow
Prompt update governance with time-locks
Quorum and threshold enforcement

Revenue & Earnings

Staking and revenue distribution live
Work-to-earn contribution rewards
Governance yield multipliers
Mission staking with success/slash mechanics

Agent Capabilities

All 6 specializations available (Security, Alpha, Treasury, Content, Bounty, Deal Flow)
Autonomous mission execution
Reporting and logging on-chain
Premium features and API access

Ecosystem

Data API for protocols and traders
Telegram + Discord integration for groups
Documentation and developer resources
Community channels (Telegram, Discord, X)

Security

Multi-sig treasury (3-of-5)
Time-locks on sensitive operations
Prompt safety review system
Audit logging and rollback mechanisms

Loading…