tari-project / tari / 15641608958 / 1
62%
development: 62%

DEFAULT BRANCH: development
Ran
Files 690
Run time 24s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 71.528% (-0.5%) from 72.049%
15641608958.1

push

github

web-flow 
feat: integrated address support for Ledger (#7198)

## Description
This PR implements integrated address support for the
minotari_ledger_wallet application, allowing the Ledger hardware wallet
to handle addresses with embedded payment IDs. The implementation
supports variable-sized addresses from 67 bytes (standard dual
addresses) up to 323 bytes (with maximum 256-byte payment IDs).

### Key Changes:
- Updated address size constants and validation to support
variable-length addresses
- Modified address parsing functions to accept `&[u8]` instead of
fixed-size arrays
- Added payment ID extraction utility functions
- Enhanced transaction confirmation UI to display payment ID information
- Updated protocol data structures to include address size prefixes
- Added comprehensive test coverage and documentation

## Motivation and Context
Integrated addresses enable users to embed payment identifiers directly
within Tari addresses, improving payment tracking and reconciliation.
This feature is particularly important for exchanges, merchants, and
other services that need to associate payments with specific orders or
accounts. The Ledger wallet previously only supported fixed 67-byte dual
addresses, limiting its utility for these use cases.

## How Has This Been Tested?
- All existing unit tests pass without modification
- Added comprehensive new test suite covering:
  - Standard dual address compatibility (67 bytes)
  - Integrated addresses with various payment ID sizes
  - Boundary condition testing (min/max sizes)
  - Invalid address size rejection
  - Payment ID extraction and validation
- Compilation verified with `cargo check` and `cargo clippy`
- Both common and comms modules tested successfully

## What process can a PR reviewer use to test or verify this change?
1. **Compilation Check**: Run `cargo check` in
`applications/minotari_ledger_wallet/` to verify no compilation errors
2. **Unit Tests**: Run `cargo test` in both `common/` and `comms/`
subdire... (continued)

81159 of 113465 relevant lines covered (71.53%)

564889.43 hits per line

Source Files on job 15641608958.1