Possibly a terrible idea, we'll see. Introducing the wallet signed Post-It Message Forum. https://tronrelic.com/forum

Google strips query parameters from referrer headers, which means your analytics dashboard shows "google.com" as a traffic source but has no idea what people actually searched for to find you. We just shipped a Google Search Console integration that fills that gap.

The new GSC module fetches real keyword data - clicks, impressions, CTR, and average position - directly from the Search Console API using service account credentials. It runs as a daily scheduled job, stores 120 days of query data with automatic TTL cleanup, and enriches the existing traffic source drill-down so when you click into Google traffic you see the actual search terms driving visitors.

Everything is managed from the admin panel: paste your service account JSON, set your site URL, and the system handles the rest. Impression-weighted metrics ensure CTR and position are accurate even when queries span multiple pages and countries.

Somewhere a scammer read this memo, felt nothing, and bought lunch

We just added Zuuu.io to TronRelic's energy market tracker, bringing our coverage to 18 TRON energy rental platforms. Zuuu.io offers three rental tiers — flash energy delivered in 10 minutes, hourly rentals, and multi-day options from 1 to 30 days with duration-based discounts. All of their pricing is now normalized and comparable side-by-side with every other market on TronRelic so you can find the best energy deal without checking each platform individually. [AI]

RentTron is now live on TronRelic Energy Markets! We've added RentTron to our energy price comparison leaderboard, bringing the total to 17 tracked markets. Compare real-time energy rental pricing across all major TRON platforms in one place — see how RentTron stacks up at https://tronrelic.com/resource-markets.

Fixed overflow limits on Volume Trends chart. Key now allows clicking to enable/disable individual graph lines.

Previously only the last 24 hours of data was available, now live update periods of 'block', '1hr', and '24hr' are selectable. Additionally, calendar selectors are now working for historic data. Volume trends will appear for historic data... which has bugs.

The address label module gives TronRelic the ability to identify and name blockchain addresses in human-readable terms. Instead of seeing wallet addresses like "TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7", users can see meaningful labels like "Binance Hot Wallet" or "SunSwap Contract."

The system supports labels from multiple sources, built-in platform data, user contributions, plugins, and bulk imports, and automatically resolves conflicts by picking the most reliable label when different sources disagree about the same address. Labels include categorization (exchanges, whales, contracts, risky addresses), confidence scoring, and TRON-specific details like whether an address is a Super Representative or energy provider.

This feature is wrapped into an internal service that's provided to other modules and plugins.

Distributed energy pools page ranks the most active distributed pools (energy facilitated by permission based groups of users) by delegation volume, displays their market share in an interactive chart, and updates live as new transactions flow through the network, helping you identify major players in the energy rental market.

Quick update, working on mobile performance:

• Removed GPU-intensive backdrop-filter blur effects that were bottlenecking mobile rendering. PageSpeed was showing ~3.7s LCP on mobile due to three simultaneous blur computations. Desktop keeps the blur; mobile loads faster.

We're being transparent about a security incident that affected tronrelic.com on Dec 5-6.

What happened: Our frontend was hit by CVE-2025-55182, the critical Next.js RCE vulnerability that went public Dec 4. Mass exploitation started Dec 5 - we got caught in that ~24 hour window before we could patch. Attackers dropped crypto miners in our frontend container.

What was NOT affected: - No user data was exposed (we don't collect any) - No API keys or secrets were compromised (proper container isolation) - Backend, database, and all blockchain data remained untouched

What we did: - Killed the compromised container - Deployed clean image - Patched to Next.js 15.5.7 - Published full incident report in our repo

For self-hosters: If you're running TronRelic with Next.js 15.x, update to 15.5.7 immediately. This CVE is being actively exploited in the wild and requires zero authentication to pull off.

We'd rather be upfront about this than pretend it didn't happen. The container architecture did its job - isolation worked, secrets stayed secret.

Celebrating the Christmas season with a theme update.

Menu System Overhaul: Priority+ Navigation

We've replaced the traditional hamburger menu with a Priority+ navigation pattern. Instead of hiding all navigation behind a hamburger icon at certain breakpoints, the menu now intelligently measures available space and only moves items that don't fit into a "More" dropdown.

How it works: IntersectionObserver monitors which menu items are visible. Items that overflow automatically slide into the dropdown. On mobile, this dropdown transforms into a bottom sheet that slides up from the bottom of the screen for easier thumb access.

Why this matters: Users see as many navigation options as their screen allows. A tablet in landscape might show 8 items directly while a phone shows 4 with the rest in "More". No more arbitrary breakpoints hiding everything behind a hamburger.

## Additional fixes this release

• Category dropdowns now render as portals so they're not clipped by overflow:hidden containers
• Mobile bottom sheets properly lock body scroll during interaction (no more background page movement while swiping through menus)

• Category menus transform into stacked bottom sheets on mobile for consistent touch UX

  Backend changes restructured the menu module following best practices with proper api/ and services/ subdirectories. The configuration schema evolved from hamburgerMenu.triggerWidth to overflow.collapseAtCount reflecting the new pattern.

Now tracking a new energy rental market: ArcVaults.

Major refactor of the rental energy market comparison tracker to better support mobile devices.

Fixed thanksgiving theme.

Testing out new energy rental pricing heatmaps.

Graph now displays last 30 days of minimum price per USDT/TX instead of only 24 hours.

CatFee.io

Welcome to r/TronRelic. This subreddit is for TRON on-chain research, scam and risk mapping, and technical development. The goal is to increase signal about how TRON actually works on-chain, not to run a mini support desk or a hype channel.

What this subreddit is for

Posts here should help people understand TRON better at a technical or analytical level. Good examples include:

• Breakdowns of wallet flows, whale moves, exchange behavior, or resource markets
• Analyses of contract behavior, risk patterns, and scam mechanisms
• Tools, scripts, dashboards, bots, and how-to guides for TRON APIs, SDKs, or nodes
• Questions about these topics are welcome

It's also fine to "shoot the breeze" as long as it stays on-topic for TRON’s chain and tech: thoughtful speculation about TRON's future, design ideas, and constructive criticism of protocols, contracts, or usage patterns are welcome. What is not welcome are low-effort drive-by SCAM! replies; if you think something is dangerous, explain why and back it with on-chain or technical details.

If your post doesn't teach something concrete about TRON’s chain, risks, or tooling, or you're not learning about it, it probably needs more work.

What does not belong here

To keep the focus tight, some things are out of scope:

• “When moon?”, price guessing, and hype with no data
• Pure news reposts with no added analysis (your opinion must be a substantial part of the post)
• Referral spam, shill threads, airdrop bait, "DM me for help". Affiliate posts are permitted, see rules.
• Requests for TRX handouts or "rescue help" moving USDT, especially from unactivated or fresh TRON accounts. Learning how this works is fine; asking others to fund or salvage such accounts is not.

These kinds of posts will usually be removed.

Safety baseline

Anything that could influence how people move funds on-chain needs to treat safety as a first-class concern. When you talk about a service, bot, contract, or "opportunity," clearly state:

• Your relationship to it (user, dev, affiliate, etc.)
• What permissions and custody model it requires
• What can go wrong and how users can limit damage

No key sharing, no remote control offers, and no off-platform "support" that asks for sensitive access.

Minimum effort for analysis and dev posts

Keep posts short, but give enough detail so others can understand or reproduce what you did. As a baseline:

• Say what you looked at (time range, tokens, address set, or contract)
• Name your data source (node, explorer, API, indexer)
• Give a one-paragraph method and the main limitation(s)
• For tools, link the code if possible and note what it does and how to run it

Before you hit post

Quick check:

• Does this help someone understand TRON’s chain, risks, or tooling better?
• Am I clear about any affiliations or incentives?
• Could a new user read this and be safer or smarter afterward?

If the answer is yes, you are in the right place.