Skip to content

feat(tron,ton): sign-message support and honest TRON fees - #350

Closed
BitHighlander wants to merge 1 commit into
feature/715-08-tendermint-chainsfrom
feature/715-09-tron-ton
Closed

feat(tron,ton): sign-message support and honest TRON fees#350
BitHighlander wants to merge 1 commit into
feature/715-08-tendermint-chainsfrom
feature/715-09-tron-ton

Conversation

@BitHighlander

Copy link
Copy Markdown
Owner

7.15 review stack position 09/17.

This PR is intentionally one coherent commit, based on feature/715-08-tendermint-chains, for individual auditing.
The full stack is linear from the clean fork develop at 1af2ffe.

Review scope: feat(tron,ton): sign-message support and honest TRON fees.

The preserved pre-restage candidate remains available at preserve/alpha-2026-08-05.

TRON:
- TIP-191 message signing (SignMessage/MessageSignature), so a TRON dapp login
  no longer requires signing a fabricated transaction.
- USDT transfers carry a fee_limit ceiling and show a simulated fee instead of
  presenting an unbounded limit the user cannot evaluate.
- unittests/firmware/tron.cpp covers the message prefix, the fee ceiling and
  contract parameter decoding.

TON:
- Address derivation uses sha256 over the StateInit cell rather than over the
  public key, which is what actually produces the wallet address.
@BitHighlander

Copy link
Copy Markdown
Owner Author

Superseded by the smaller audit-ready 7.15 stack: #359 release foundation, #360 authenticated clear-signing, #361 recovery and entropy, #362 Zcash Orchard, #363 chain integrations, and #364 Bitcoin/release security. All release changes remain preserved in the replacement branches and preservation tags. The replacement aggregate was tree-verified against the prior release and passed the local CI-equivalent container suite (405 firmware, 2 board, 18 crypto, and 7 Pallas constant-time tests). GitHub-hosted checks have been explicitly dispatched and are currently queued.

@BitHighlander
BitHighlander deleted the feature/715-09-tron-ton branch August 9, 2026 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant