AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 47 Bitcoin

Merge release v3.0.6 (#2290)

Public commit record

What the developer wrote

Authored by github-actions[bot]

76/100 · Adequate
Merge release v3.0.6 (#2290)

* feat(solana): support V1 transaction messages

* chore: update ci

* fix(solana): paginate transaction details for large messages

* chore: update version and changelog

---------

Co-authored-by: Soralit <44085950+soralit@users.noreply.github.com>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This firmware update adds support for Solana's new V1 transaction format and changes how oversized or malformed transaction details are displayed. The code introduces a dedicated parser for V1 messages with strict size and structure checks, and it prevents malformed V1 messages from being silently treated as ordinary text messages. It also paginates long transaction detail screens so users can scroll through large transactions instead of the UI breaking or truncating.

Recommended action

Treat this as a routine feature/security-hardening release. Review the new V1 parser's bounds and test coverage for edge cases such as zero-length instructions, maximum account indexes, and boundary sizes including signatures. Verify that the pagination UI correctly displays all instructions and does not hide attacker-controlled fields. No immediate incident response is indicated by the diff alone.

Security signals we found

01

New parser enforces hard limits on V1 message fields and rejects malformed 0x81-prefix payloads instead of falling back to message signing

02

Compute-budget instructions in V1 are explicitly ignored to prevent fee-display spoofing

03

UI pagination change for large transaction details reduces truncation risk

04

Error message generalization obscures the previous 'hidden trailing data' wording

Risk score

Why this scored 47/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 6/15
Affected reach 10/15
Confidence 7/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.