Skip to content

Commit 1ad8fed

Browse files
authored
Merge branch 'main' into feat/clarify-messages-order-handling
2 parents a45c83d + eb0343c commit 1ad8fed

File tree

3 files changed

+211
-47
lines changed

3 files changed

+211
-47
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ If no SDK for your language, take the [JS SDK](https://github.com/ton-connect/sd
1515

1616
## Protocol specifications
1717

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.
1919

2020
* [Protocol workflow](workflows.md): an overview of all the protocols.
2121
* [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
2525

2626
## Q&A
2727

28-
#### I am building an HTML/JS app, what should I read?
28+
#### I am building an HTML/JS app. What should I read?
2929

3030
Simply use the [TON Documentation](https://docs.ton.org/develop/dapps/ton-connect/overview) manuals and do not worry about the underlying protocols.
3131

@@ -41,22 +41,22 @@ JS SDK does that for you; just get wallets list `connector.getWallets()` and che
4141

4242
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.
4343

44-
#### How to implement backend authorization with tonconnect?
44+
#### How to implement backend authorization with TON Connect?
4545

4646
[See an example of dapp-backend](https://github.com/ton-connect/demo-dapp-backend)
4747

4848
#### How do I make my own bridge?
4949

50-
You don’t need to, unless you are building a wallet.
50+
You don’t need to unless you are building a wallet.
5151

5252
If you build a wallet, you will need to provide a bridge. See our [reference implementation in Go](https://github.com/ton-connect/bridge).
5353

5454
Keep in mind that the wallet’s side of the bridge API is not mandated.
5555

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.
5757

5858
#### I make a wallet, how do I add it to the list of wallets?
5959

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.
6161

62-
Apps may also add wallets directly through the SDK.
62+
Apps may also add wallets directly through the SDK.

bridge.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -97,11 +97,10 @@ Parameter **ret** (optional) specifies return strategy for the deeplink when use
9797
- 'none' means no jumps after user action;
9898
- 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.
9999
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, ...).
101102
```
102-
https://<wallet-universal-url>?ret=back
103-
```
104-
103+
https://<wallet-universal-url>?id=<to_hex_str(A)>&ret=back
105104

106105
The link may be embedded in a QR code or clicked directly.
107106

0 commit comments

Comments
 (0)