Skip to content

Commit

Permalink
markdown lints
Browse files Browse the repository at this point in the history
  • Loading branch information
hdevalence committed Nov 24, 2024
1 parent 8eda4da commit da49592
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions uips/uip-5.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
| title | Outbound Packet Forwarding Middleware Support |
| description | Add configurable memo field to Ics20Withdrawal to support outbound multi-hop ICS20 transfers using Packet Forwarding Middleware |
| author | Ava Howell |
| discussions-to | https://forum.penumbra.zone/t/pre-uip-outbound-packet-forwarding-middleware-support/121 |
| discussions-to | [Penumbra Forum](https://forum.penumbra.zone/t/pre-uip-outbound-packet-forwarding-middleware-support/121) |
| status | Draft |
| type | Standards Track |
| consensus | No |
Expand Down Expand Up @@ -64,6 +64,7 @@ impl From<Ics20Withdrawal> for pb::FungibleTokenPacketData {
```

The `ics20_memo` field:

- MAY contain any valid UTF-8 string
- MAY be empty

Expand All @@ -76,7 +77,6 @@ There are two major parts of Packet Forwarding Middleware support:

This UIP implements (1), using a minimal protocol change (adding the configurable memo field). This gives the majority of end-user benefit from PFM support, notably that users can experience superior UX in withdrawing from the Penumbra chain, while avoiding complex protocol development work and assurance. A separate UIP for implementing (2) in the Penumbra IBC stack could be considered in the future.


## Backwards Compatibility

This UIP adds an additional field to the Ics20Withdrawal struct, which would be a breaking change and require a protocol upgrade.
Expand Down

0 comments on commit da49592

Please sign in to comment.