- Established
- 2
- Needs proof
- 9
- Hard risk
- 4
- Live / context
- 0
Conditional protocol-growth thesis
Place up to four reviewed assets on the same six research axes. Coverage, hard stops, freshness, and exit boundaries remain visible without manufacturing one universal winner.

Status colors reproduce each review's published evidence tone. They are not scores or probabilities.
Conditional protocol-growth thesis
Speculative only
Conditional infrastructure thesis
Is the exact asset, chain, and contract route clear?
Match the full mint in wallet, venue, explorer, stake pool, and swap route. Reject ticker-only identification.
Match network, chain ID, address, and venue withdrawal network before every transfer.
Match chain ID, denom or denom trace, destination chain, bridge, wallet, and venue. Reject ticker-only identification.
Is the relevant product or network operating and observable?
Measure product-specific volume, active liquidity, fees, retention, and competitive share rather than treating feature count as value.
Treat product existence as an input, not proof that value flows to SHIB holders.
Credit the design only within its published assumptions; separately assess execution, settlement, sequencers, bridges, and storage.
What creates asset-specific demand or value capture?
Reconcile fee generation, conversion, RAY accumulation, custody, emissions, and treasury policy without calling buybacks dividends.
Reject any thesis that substitutes ecosystem activity for a SHIB-specific demand mechanism.
Track paid blobs, unique durable users, fees in TIA and USD, retention, concentration, subsidies, and pricing over multiple periods.
Which issuance, fee, reward, or distribution path changes exposure?
Refresh total, circulating, reserve, treasury, staking, and annual emission figures before valuation.
Do not model passive income until the live interface and current detailed documentation confirm rewards.
Refresh current total supply and inflation. Compare issuance with actual fee demand and do not call nominal staking rewards real yield.
Which authority, contract, governance, or security dependency remains?
Verify current authorities, thresholds, timelocks, pending changes, config admins, and program hashes on-chain.
Use official URLs, small test transfers, limited approvals, and a tested return path.
Map every audit to the exact deployed version and integration. An audit list is not a guarantee against protocol, bridge, client, or operational failure.
Can the intended position enter, exit, and settle within written limits?
Test the exact network round trip, then stress-quote the full intended position and preserve an independent exit route.
Check the actual pair and order size immediately before entry and exit.
Test a minimal native round trip, then validate the full intended exit size and self-custody recovery path.
Decode both mints, token programs, extensions, authorities, and maximum fee settings before swapping or providing liquidity.
Open full reviewReject any thesis that substitutes ecosystem activity for a SHIB-specific demand mechanism.
Open full reviewRequire a credible archival and state-reconstruction plan for every rollup counted as durable demand.
Open full reviewThe workspace preserves category differences and makes missing publication coverage explicit.
Review pages, Evidence Operations, JSON feeds, and this workspace share stable review IDs and current publication states.
More sources or a completed migration cannot average away failed identity, control, custody, liquidity, or exit evidence.
The result is a proof queue and route to deeper research, not a recommendation, point forecast, or personalized allocation.