You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
iip: 49
title: ICON Provider JS API
author: Fidel (github.com/FidelVe), Ben (github.com/bkbooth), Eric (github.com/han-so1omon)
discussions-to: https://github.com/icon-project/IIPs/pull/49
status: Draft
type: Standards Track
category: IRC
created: June 25, 2022
Abstract
To allow communication between software wallets and web applications is necessary for these software wallets to expose an API via Javascript in the web page. For the wallets and web apps to communicate it is necessary the creation of dispatching and listening events using Javascript in the browser.
Motivation
To ensure seamless user experience and avoid implementation of several API communication protocols in each web application to support several software wallets, it is necessary to implement a standardized protocol for all software wallets and web applications to adhere to.
Procedure
Please review PR #49 and discuss here. Some discussions have taken place prior to raising the Pull Request in this Community Forum post. Please review the preceding discussion as well. Thanks!
The text was updated successfully, but these errors were encountered:
Abstract
To allow communication between software wallets and web applications is necessary for these software wallets to expose an API via Javascript in the web page. For the wallets and web apps to communicate it is necessary the creation of dispatching and listening events using Javascript in the browser.
Motivation
To ensure seamless user experience and avoid implementation of several API communication protocols in each web application to support several software wallets, it is necessary to implement a standardized protocol for all software wallets and web applications to adhere to.
Procedure
Please review PR #49 and discuss here. Some discussions have taken place prior to raising the Pull Request in this Community Forum post. Please review the preceding discussion as well. Thanks!
The text was updated successfully, but these errors were encountered: