refactor: remove unused entry points and direct stack trace output

[halibobo1205]

User description

Summary

• Remove unused main methods from PedersenHashCapsule and test utilities.
• Delete the obsolete TronTest debug class.
• Replace direct printStackTrace() calls in production code with contextual SLF4J logging.

Motivation

Unused entry points add maintenance noise, while direct stack trace output can expose internal implementation details through standard error. These changes keep exception reporting within the configured logging system.

Testing

• Compiled the affected common, chainbase, actuator, and framework modules.
• Ran framework:checkstyleMain.
• Ran framework:checkstyleTest.
• Confirmed that no printStackTrace() calls remain under production src/main code.

---

CodeAnt-AI Description

Replace direct console errors with controlled logging and remove obsolete debug entry points

What Changed

• JSON-RPC, file-reading, transaction parsing, address extraction, and actuator errors now use contextual application logging instead of printing stack traces directly.
• Removed unused command-line entry points and the obsolete network-debug test utility.
• Error handling continues to return existing fallback results or propagate failures while keeping diagnostics in the configured logging system.

Impact

✅ Cleaner service output without raw stack traces
✅ Consistent error reporting through application logs
✅ Fewer obsolete debug entry points

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	167bc38	Jul 28, 2026 · 08:11	08:14

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn