CD / ET ROBINHOOD GIGADASH TERMINAL / EVIDENCE-BOUND
G GIGADASHGIGADEX ANALYTICS WORKBOOK
INDEXED ROBINHOOD · 4663
DOCS ↗

DOCS CONTRACTS

/runtime code live

VERIFIED SOURCE

Blockscout artifacts

OBSERVED POOLS

CL · classic

TOKEN PHASE

docs state loading

UPGRADEABLE CORE

transparent proxies

CHAIN HEAD

snapshot loading

ONCHAIN ANALYTICS WORKBOOKSCHEMA 03 · ROBINHOOD CHAIN

GigaDEX by the numbers.

A Dune-inspired analytical surface for GigaDEX: protocol volume, fees, active trader addresses, first-seen cohorts, retention, Robinhood Chain market share, liquidity, pools, and the evidence underneath every metric.

DATASET PASSPORTSCHEMA V3
HISTORYlaunch → snapshot
INITIATOR COVERAGERPC-hydrated tx.from
COMPLETE THROUGHUTC calendar day
MARKET UNIVERSEDEX families tracked
EVIDENCE-BOUND00 · current UTC minute

01 / EXECUTIVE OVERVIEW

Protocol pulse

Complete UTC data loading…
INDEXED TVLofficial indexer
24H VOLUMErolling · official indexer
7D VOLUMEcomplete UTC days
24H FEESgross indexed fees
DAILY ACTIVE TRADERSlatest complete day
WEEKLY ACTIVE TRADERSunique tx initiators
CHAIN VOLUME SHARE24h · DefiLlama
ACTIVE POOLSrolling 24 hours

TIME SERIES

Daily volume

UTC DAILY

02 / USERS & RETENTION

Who arrives.
Who comes back.

Address-level cohorts use each transaction initiator’s first observed GigaDEX swap day. Retention is an exact UTC-day return—not a rolling-window approximation.

D1 RETENTIONmature cohorts
D7 RETENTIONmature cohorts
D14 RETENTIONmature cohorts
D30 RETENTIONnot yet observable
RETURNING SHARElatest complete day
OBSERVED TRADERSsince indexed launch

ACTIVE TRADER MIX

New vs returning

NEW RETURNING
HEIGHT = ACTIVE ADDRESSES

COHORT HEATMAP

First-seen trader retention

Cells show the share of each daily cohort active again exactly 1, 7, 14, or 30 UTC days later.

03 / MARKET SHARE

GigaDEX against
the whole chain.

Numerator and denominator both come from DefiLlama’s DEX volume adapters. Official-indexer volume remains a separate operating lens and is never mixed into these percentages.

24H SHAREprotocol volume
7D SHAREprotocol volume
30D SHAREprotocol volume
24H FAMILY RANKtracked families

24H DEX FAMILIES

Chain leaderboard

04 / POOLS & LIVE FLOW

Money in the machine.
Traffic on the wire.

Pool state and swap events come from the public indexer used by the official GigaDEX interface. The rolling window is pinned to the verified chain snapshot; swap legs and unique transactions are shown separately.

INDEXED TVL ESTIMATE

pricing coverage loading

24H VOLUME

priced swap legs

24H FEES

gross indexed fees

SWAP LEGS

transactions

SWAP SENDERS

event-level addresses

VOLUME / TVL

rolling capital turn

ROLLING VOLUME TAPE

24 hourly bins

window loading INDEXED
WINDOW STARTHEIGHT = USD VOLUMESNAPSHOT END

LIQUIDITY SURFACE

Pools carrying the protocol

pricing evidence loading

POOLTYPE / FEETVL24H VOLUME24H SWAPS

05 / PROTOCOL ENGINE

The DEX is live.
The token is next.

Launch begins with a six-week points program. The revenue-weighted allocation engine below is the documented GIGA-era design; exact normalization and manipulation controls remain undisclosed.

FEES
60 MIN
GIGA
01
Trades create the signal

Swaps across stable, volatile, and concentrated pools generate fees. Only gauged pools participate in GIGA emissions.

06 / POST-GENESIS ADVERSARIAL MODEL

When could fake revenue
buy real emissions?

Illustrative future-state stress model only. Inputs are hypothetical and are not current GigaDEX revenue, fees, emissions, points, or volume.

MODEL OUTPUT

Incremental emission value
Self-trade fee cost
Modeled net incentive
CALCULATING

Simplified model: pool share = pool eligible revenue ÷ all eligible revenue. It excludes gas, price impact, rebates, hedging, detection, caps, penalties, and any unpublished controller logic.

07 / GENESIS ARCHITECTURE

A fixed billion.
Waiting offstage.

The token is not live at launch. At GIGA Genesis, LP emissions, Treasury, and the protocol-owned GIGA Machine account for 79% of fixed supply.

08 / DEPLOYMENT SURFACE

Twenty-two contracts.
Every one accounted for.

Live bytecode and explorer verification are checked at dashboard refresh. Verification is not an audit.

09 / WHAT CAN BREAK

The code is live.
The history is young.

Risk ranking reflects disclosure and mechanism uncertainty at the snapshot, not an exploit claim or audit verdict.

PROVENANCE

Docs claims. RPC code. Explorer metadata. Official indexer.
Every number keeps its evidence boundary.

Latest snapshot loading…