Trading activity:
Reported 24-hour volume equals 0.01% of market capitalization. The local markets snapshot lists Sushiswap V3 (Hemi) among venues with observed trading activity.
Values are descriptive and should be read together rather than as a price forecast.
Read the YearBull methodology.
Snapshot date: 2026-05-12.
Methodology responsibility:
YearBull’s analytical methodology and presentation rules are developed and maintained by
Alan Zelvin, Founder & Lead Crypto Researcher.
This note identifies responsibility for the methodology; it does not attribute authorship of this data snapshot.
Rank history is still being collected.The rank timeline will appear after two valid daily YearBull Rank snapshots are available.
Rank change (daily snapshots).
Reading rule: rank #120 sits higher than rank #200.
7d window: current rank not available.
30d window: current rank not available.
YearBull Rank is a relative placement score used on YearBull to compare a coin against peers within the same dataset. Lower values mean higher placement in the YearBull ordering.
Phase read: If the 30d is noisy, increase the lookback to avoid over-reading. a stable phase often tightens the rank range.
Trading footprint: If the line breaks range, confirm it across a longer window. a new route can show up as a step change.
Liquidity note: If the curve improves and holds, it is usually more structural. rank can move when liquidity redistributes across the cohort.
Volatility posture: If it is flat for long, the coin may be tracking the cohort. big jumps can be data-driven, but also rotation-driven.
Editorial note:
This analysis was prepared by the YearBull research team under the direction of
Alan Zelvin,
Founder and Lead Crypto Researcher.
The assessment follows YearBull’s internal research methodology and editorial standards.
Methodology ·
Editorial Policy
We use cookies and similar technologies to improve site functionality, analyze usage, and enhance user experience.
By continuing to use YearBull, you agree to our use of cookies as described in our
Privacy Policy.
Comments