Skip to content

Commit

Permalink
uip 7: ignore deprecated use_compat_address field
Browse files Browse the repository at this point in the history
  • Loading branch information
redshiftzero committed Dec 11, 2024
1 parent 73c716a commit 3e9976c
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions uips/uip-7.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ This diversified basepoint is used to to derive the transmission key $pk_d$:

$pk_d = [ivk] B_d$

The new address format, the *transparent address*, consists only of the 32 byte transmission key. It is encoded using the `tpenumbra` human-readable prefix.
The new address format, the _transparent address_, consists only of the 32 byte transmission key. It is encoded using the `tpenumbra` human-readable prefix.

The transmission key for the transparent address is derived using the diversifier
corresponding to all zero bytes. Note that during scanning, the wallet scans
Expand Down Expand Up @@ -80,17 +80,20 @@ Transparent addresses are incompatible with the FMD feature of the Penumbra prot
The `Ics20Withdrawal` action is modified to:

1. Add a new boolean field `use_transparent_address`

2. Deprecate the existing `use_compat_address` field

When the `use_transparent_address` field is true:

* The `return_address` field MUST be set to the transparent address.
* The `use_compat_address` field MUST be set to false.

## Rationale

The design prioritizes:
1. Maximum external compatibility through fixed-size 32-byte addresses

2. Seamless conversion to full Penumbra addresses

3. Minimal changes to the core protocol

The tradeoff of having only one transparent address per wallet is
Expand Down

0 comments on commit 3e9976c

Please sign in to comment.