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
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ If no SDK for your language, take the [JS SDK](https://github.com/ton-connect/sd
15
15
16
16
## Protocol specifications
17
17
18
-
If you implement an SDK, a wallet or want to learn more how Ton Connect works, please read below.
18
+
If you implement an SDK, a wallet or want to learn more about how TON Connect works, please read below.
19
19
20
20
*[Protocol workflow](workflows.md): an overview of all the protocols.
21
21
*[Bridge API](bridge.md) specifies how the data is transmitted between the app and the wallet.
@@ -25,7 +25,7 @@ If you implement an SDK, a wallet or want to learn more how Ton Connect works, p
25
25
26
26
## Q&A
27
27
28
-
#### I am building an HTML/JS app, what should I read?
28
+
#### I am building an HTML/JS app. What should I read?
29
29
30
30
Simply use the [TON Documentation](https://docs.ton.org/develop/dapps/ton-connect/overview) manuals and do not worry about the underlying protocols.
31
31
@@ -41,22 +41,22 @@ JS SDK does that for you; just get wallets list `connector.getWallets()` and che
41
41
42
42
Like with embedded apps (see above), JS SDK detects it for you via `injected` property of the corresponding `connector.getWallets()` list item. If you build your own SDK you should check that `window.[targetWalletJsBridgeKey].tonconnect` exists.
43
43
44
-
#### How to implement backend authorization with tonconnect?
44
+
#### How to implement backend authorization with TON Connect?
45
45
46
46
[See an example of dapp-backend](https://github.com/ton-connect/demo-dapp-backend)
47
47
48
48
#### How do I make my own bridge?
49
49
50
-
You don’t need to, unless you are building a wallet.
50
+
You don’t need to unless you are building a wallet.
51
51
52
52
If you build a wallet, you will need to provide a bridge. See our [reference implementation in Go](https://github.com/ton-connect/bridge).
53
53
54
54
Keep in mind that the wallet’s side of the bridge API is not mandated.
55
55
56
-
For a quick start you can use the common TON Connect bridge https://bridge.tonapi.io/bridge.
56
+
For a quick start, you can use the common TON Connect bridge https://bridge.tonapi.io/bridge.
57
57
58
58
#### I make a wallet, how do I add it to the list of wallets?
59
59
60
-
Submit a pull request for the [wallets-list](https://github.com/ton-blockchain/wallets-list) repository and fill our all the necessary metadata.
60
+
Submit a pull request for the [wallets-list](https://github.com/ton-blockchain/wallets-list) repository and fill out the wallet manifest.
61
61
62
-
Apps may also add wallets directly through the SDK.
62
+
Apps may also add wallets directly through the SDK.
Copy file name to clipboardExpand all lines: bridge.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,11 +97,10 @@ Parameter **ret** (optional) specifies return strategy for the deeplink when use
97
97
- 'none' means no jumps after user action;
98
98
- a URL: wallet will open this URL after completing the user's action. Note, that you shouldn't pass your app's URL if it is a webpage. This option should be used for native apps to work around possible OS-specific issues with `'back'` option.
99
99
100
-
`ret` parameter should be supported for empty deeplinks -- it might be used to specify the wallet behavior after other actions confirmation (send transaction, sign raw, ...).
100
+
The `id` parameter should be supported even in empty deeplinks -- it might be used by wallets to identify the application.
101
+
`ret` parameter should also be supported for empty deeplinks -- it might be used to specify the wallet behavior after other actions confirmation (send transaction, sign raw, ...).
0 commit comments