Proposal to simplify transfer of all assets for end users

[ChrisHoltDesign]

Currently transfers are broken down into

• IBC Transfers
• Internal inter account transfers
• Transfers to other accounts or namada users

This creates three transfer streams and three different transfer modules relying on end users knowing what IBC is vs a normal transfer, knowing that IBC is the way to shield from external wallets. + that shielding can also take place internally.

Confusing if you are not crypto native

---

Proposal!
We break transfers down into user Actions not assumptions of what they do and do not know

SHIELD / UNSHIELD / SEND

SHIELD

• Assets can be shielded via IBC or by sending from a users transparent account to shielded.
• The UI will determin whether it's an IBC transfer or an internal transfer based on the users selected actions

The module would just state whether the transfer is IBC vs Internal

e.g I want to shield some assets. I select to shield some osmo from keplr in the transfer UI = powered by IBC transfer
e.g I want to shield some assets. I select the ATOM from my transparent address in the UI = powered by Internal Namada transfer.

The tech that is used for each transfer is under the hood, the user doesn't care how the asset was shielded just that it happend

The same principle applies for unshielding just in the reverse on the destination input

Also for sending assets away from namada to other parties or wallets. A user could specify IBC vs non to send assets

UI wise then we have three distinct call to actions for users

And UI that just calls out IBC under the hood when IBC is necessary to facilitate a users action

Small tweaks will be outlined to the transfer modules in due course.

[euharrison]

I loved this proposal! 👏