We have a major objective of writing our packages in such a way that allows for third-party wallets (Keplr, Leap, etc) to easily integrate the view service into their own codebase.
Given how deeply integrated the view service is in our code, it's challenging to know if it indeed could work with other wallet extension infra. For instance, we should assume they handle custodying completely different. Think we should do three things:
Complete the end-to-end third party integration documentation. Should give a step-by-step tutorial on how it can be done.
Add a proof-of-concept extension to /apps that serves as an integration guide. Should be heavily stripped down and not require any styling. Should display block sync progress & balances.
Add a proof-of-concept web app to /apps that has a button to issue a simple send transaction and display wallet id.
turbocrime
commented
10 months ago
We have a major objective of writing our packages in such a way that allows for third-party wallets (Keplr, Leap, etc) to easily integrate the view service into their own codebase.
We wrote a third-party integration guide in the past and have taken the beginning steps to update it based on the new message passing system.
Given how deeply integrated the view service is in our code, it's challenging to know if it indeed could work with other wallet extension infra. For instance, we should assume they handle custodying completely different. Think we should do three things:
/appsthat serves as an integration guide. Should be heavily stripped down and not require any styling. Should display block sync progress & balances./appsthat has a button to issue a simple send transaction and display wallet id.