refactor(crypto): remove unused SM2 and SM3 support

[Federico2014]

What does this PR do?

Remove SM2/SM3 implementations, runtime engine selection, and Toolkit --sm2 options. Simplify signing and hashing APIs to ECKey/secp256k1 and SHA-256, and update their callers and tests across the dependent modules.

Retain a startup-only compatibility check before storage or keystore initialization: an absent crypto.engine uses the default suite; explicit eckey is accepted with a deprecation warning; all other values, including sm2, null, and non-string values, fail with migration guidance. Add configuration and FullNode startup regression tests and document the migration requirements.

Why are these changes required?

The unused engine switch spans consensus-critical hashes, signatures, addresses, and Merkle roots. Removing it simplifies the cryptographic path, while the startup check prevents an existing SM2 deployment from silently switching algorithms against incompatible chain data. Implements the compatibility requirements discussed in tronprotocol#6959.

This PR has been tested by:

• Focused configuration and FullNode startup tests passed, covering default startup, explicit eckey, unsupported values, and rejection before database-directory creation or keystore initialization.
• ./gradlew test :framework:checkstyleMain :framework:checkstyleTest --continue --console=plain passed: 3,437 tests passed, 27 skipped, zero failures; both framework Checkstyle tasks passed.
• Manual live-node testing was not performed.

Follow up

Existing SM2/SM3 deployments must remain on a compatible release until a separate migration is completed. Changing the configuration does not convert chain data or keys.

Extra details

Targets release_v4.8.3. The cross-module changes are required by the removal of shared engine-selecting APIs. This breaks those Java APIs and removes SM2/SM3 support; the default ECKey/SHA-256 path is retained.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 3b2fe5dd-4531-4d7c-948b-26d3204ebc1b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

All reported issues were addressed across 97 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>