ZHC Financial Layer

Giza

Autonomous Yield Agent

Giza Protocol 的自主 DeFi Agent 基础设施,旗舰产品为 ARMA。

GIZAOfficial tokenGovernance: L3

Official Giza Protocol token used across autonomous DeFi-agent infrastructure, staking, rewards, and cross-chain token mechanics.

Project Overview

Giza builds autonomous agents for on-chain capital management. Its flagship ARMA product lets users activate non-custodial agents that monitor markets, execute yield strategies, rebalance positions, and compound returns around the clock. The protocol combines an agent authorization framework, smart accounts, strategy optimization, and a token/staking system around GIZA. Public protocol revenue is tracked by DeFiLlama as performance fees, while Giza's token repository documents deterministic deployments, staking, cross-chain transfers, and reward distribution. Giza is one of the more mature DeFAI projects in this dataset, but holder counts and usage figures vary sharply by source, so ZHCs.AI uses conservative on-chain/market snapshots.

Contract Address

0x590830dFDf9A3F68aFCDdE2694773dEBDF267774

Price
$0.006131
24h
-1.94%
Market Cap
$2M
Holders
2,084
Cumulative Revenue
$125,104
Annualized Revenue
$126,842
P/S
16.45x

Research Notes

A compact research lens for why this project matters and what to watch next.

01

Why it matters

Giza is tracked as ZHC Financial Layer with a core function of Autonomous Yield Agent. Its research value is whether it makes Zero-Human Company formation, operation, financing, compute, or distribution more real.

02

Current traction

Visible revenue or protocol-fee signals are tracked: total revenue $125,104 and annualized revenue $126,842.

03

Key metric to watch

Watch whether P/S remains reasonable as revenue and market cap change, and whether revenue sources continue to update.

Share this project

A concise share card for X, Telegram, or research notes.

Share on X
Share text
Giza on ZHCs.AI

Market cap: $2M
Total revenue: $125,104
Annualized revenue: $126,842
P/S: 16.45x

Track the ZHC stack by real traction, revenue, and capital efficiency.
https://www.zhcs.ai/projects/giza

Research Coverage

A concise view of what is actively tracked and how strongly the record is supported.

Market data
Live / refreshed
Revenue data
Verified
Source trail
Strong source trail

Data Sources & Methodology

Where each metric comes from, how it is refreshed, and how ZHCs.AI calculates derived values.

Market data
Verified
15 minutes
Matched by official Base contract address. Pair-level price and market cap are only accepted when the token is the base asset.
Holders
Curated
Periodic review
Maintained from verified token contract pages or official market sources when available.
Cumulative Revenue
Verified
Daily / weekly review
DeFiLlama protocol revenue snapshot for Giza performance fees.
Annualized Revenue
ZHCs.AI
Curated
Calculated
Annualized revenue = cumulative revenue since launch or revenue start date / active days * 365.
P/S
ZHCs.AI
Curated
Calculated
P/S = current market cap / rankable annualized revenue. Projects without reliable revenue are excluded from this multiple.

Spot an issue?

If market data, revenue, links, or methodology look wrong, send a correction with sources.

Suggest a correction

Operational Metrics

Cumulative revenue
$125.1K
DeFiLlama protocol revenue snapshot.
TVL
~$4.9M
DeFiLlama/CoinGecko TVL context.
Performance fee
10%
DeFiLlama describes Giza fees as performance fees on generated yield.
Token supply
1B
GIZA max/total supply from market pages and token repo.
Deployments
Ethereum/Base
Giza token repo lists the same token address on Ethereum and Base.
Product
ARMA
Autonomous DeFi yield agent product.

Methodology

Annualized revenue = cumulative revenue since project start / active days * 365. Only dashboard or protocol-fee-backed revenue is ranked.

P/S = Market Cap / rankable annualized revenue. Projects with only private/model proxies are excluded.

Launch Date: 2025-05-21

Revenue Age: 360 days

Revenue Basis: DeFiLlama protocol revenue snapshot for Giza performance fees.

User-supplied holder count was not used because market/explorer sources currently show a much lower token-holder count. Revenue is protocol-fee backed, not audited GAAP revenue.

Source