Skip to content

Next Steps Jan 2023

Jump to bottom
Nikolaus Heger edited this page Jan 27, 2023 · 2 revisions

What's next

Client App

  • Full implementation of the SSR standard, with identity request
  • Push notification SSR requests
  • Transaction list on chains that support this - if this is a standard, we can implement it for all chains, if it is not a standard we could abstract it out so pieces and parachains can be added over time
  • Support for all native tokens on chain. if there is a standard, use it. If not, allow parachains to be added gradually as plug-ins.

Replace Polkadot JS browser solution

  • Native implementation of WS connection to substrate nodes -- Query data (api.query...) -- Metadata -- Sign and send (api.pallet.extrinsic + [parameters] ) -- Key management -- SCALE encoding / decoding This could potentially be achieved with parity signer Rust libraries which may do some of these things already.

The reason is that using PolkadotJS inside a hidden browser window in a mobile app creates many problems, and it is overall difficult to control, difficult to reconnect, and difficult to maintain. As one has to maintain JS libraries, package them with webpack, manage browser global variables and so on. We could also gradually remove these, only using JS for sign and send for example.

Backend support

  • Node JS based JS backend implementing identity authentication
  • UAL like library that allows other implementations of authentication, so it can be used on any website and any auth service, such as AWS cognito, and so on.
  • UAL client that pops QR codes just like Anchor has
  • Anchor-Link like implementation to send requests directly to the wallet

Clone this wiki locally