A common convention in the TON web application (“DApp”) ecosystem is for key
page. This object is called “the Provider”.
The Provider implementations can have conflicting interfaces and behaviors between
wallets. This TIP formalizes an TON Provider API to promote wallet interoperability. The
API is designed to be minimal, event-driven, and agnostic of transport. Its functionality
is easily extended by defining new methods and message event types.
Offer for all providers to make available their features as window.ton in web browsers
Many teams have created their own solutions during recently conducted the 1st round of Contest on TON wallet as Chrome web extension. This proposal sets as the main aim to work
out an agreement for the Web3 like provider interface to avoid any artificial situation
when DApp developers can be forced to use only the one wallet on the market. Offer to
introduce the uniform Web3 like provider interface and implement its on 3rd stage the
contest to allow users using any wallet solution for decentralized applications (DApp)
The last co-worked result will be posted here after resolving all proposals.