Closed otoole-brendan closed 10 months ago
@samsiegart could you please provide a quick estimate on this? Also if you can check it's viability by confirming it works with Keplr? How do we think offer legibility would work with this, especially with the cross-chain swaps with Skip API?
@samsiegart could you please provide a quick estimate on this? Also if you can check it's viability by confirming it works with Keplr? How do we think offer legibility would work with this, especially with the cross-chain swaps with Skip API?
Quick estimate is 5 points
It should work in Keplr, yea. I asked the leap team in discord and they pointed me to https://cosmos.leapwallet.io/transact/bridge as an example that uses elements and it did work with Keplr
Offer legibility wouldn't be applicable with the swaps unfortunately, since it's not going through Zoe
@samsiegart let's sync to understand how much we can customize. For example, can we determine what assets users can use Kado to onboard to (we'd want to limit to IST, BLD, Inter assets, PSM assets). Similarly - we shouldn't let users send non-supported assets to Agoric chain if there is no use for them there. There are also performance considerations.
Allow listed assets we should let them send to Agoric chain (and be onboardable via Kado):
What would be the process to update later when future assets are added as Vault collateral for example?
It would be better to replace the entire deposit flow with Leap elements than the currently non-working statom desposit flow
@zmanian Thats the plan. When they hit 'Deposit stATOM' in app it'll bring up the Leap Elements modal instead of bringing them to Wallet UI where they can only IBC transfer to Agoric chain
Trying to integrate leap elements as documented:
Buffer
to be polyfilled, but I run into an endo error when doing socosmos-kit
, I can get the modal to pop up and prompt keplr to sign an IBC transaction, but it never gets broadcast to chain and the IBC flow just hangs. Presumably something wrong with how I'm returning the signed message from Keplr, but there's no errors visible and the source code is minified and the repo is not public, so hard to debug.Have reviewed the UX/design and looks good. Note - Kado are fixing issue to make Agoric destination available. Kado can be added later but for the sake of the Vaults deposit funds flow - it's not critical (users who are trying to open a vault are locking up other assets and are not looking to buy IST with credit card)
What is the Problem Being Solved?
A user's experience/journey to get a supported PSM or collateral asset over to the Agoric chain in order to be able to use Inter apps is not intuitive, is confusing and requires broad knowledge of IBC infrastructure and it's nuances (differnt ibc denoms etc for assets coming from different chains).
This experience makes it painful and frustrating to easily interact with Inter apps - resulting in user drop-off and ultimately loss of business/TVL.
Note this is a part of the Product's End User UX and Asset Onboarding project/rock for Q4
Current Flow
Description of the Design
This user onboarding/onramp can be massively improved upon by integrating Leap Elements or the Skip API. Leap elements is a FE SDK that provides several one-click solutions depending on the user's status - it can be easily integrated on our FE and utilizes Skip API, Squid and Kado.
A full Skip API integration offers the cross-chain swap utility similar to Leap Elements and Post-route actions (read: open a vault in same transaction as cross-chain swap). While this is an even greater simplification for the user - this integration is more expensive - plus it wouldn't include Kado and Squid so we'd likely have to integrate those separately.
Given this Leap Elements seems to be offer the highest value for the cheapest cost.
New Flow with Leap Elements:
Security Considerations
TBC
Test Plan
TBC