TON Connect

[tolya-yanot]

The Tonkeeper team has done a great job. They studied what's been done in other blockchains, took the best approaches and improved the weaknesses.

If you like comparisons, TON Connect can be seen as an improved and most importantly decentralized version of WalletConnect.

Many TON dapps and wallets already support TON Connect. With the upcoming updates of the TON Connect SDK and UI, it's going to be pretty good. Let's have a final discussion about the protocol to make it a network-wide standard.

If you see any flaws or omissions of the protocol, please describe them here.

[AndreyDodonov-EH]

Which methods of authorization are implied here?
Usually local authorization is done in wallet itself (fingerprint, pin, password).

Is it supposed to be something other than just private key (or complete seed phrase) + local authorization?

E.g. some types of 2FA to sacrifice some decentralization in favor of security?

[Gusarich]

@AndreyDodonov-EH
Authorization in this context means proving to the app backed that user really owns the wallet.
It is also shown in docs: https://ton.org/docs/develop/dapps/ton-connect/integration#logging-out-and-requesting-tonproof

[AndreyDodonov-EH]

Thanks a lot!
I'll try to go through the docs thoroughly.

[stels-cs]

Add way to abort transaction sent via connector.sendTransaction

like abortable fetch in browser api https://developer.chrome.com/blog/abortable-fetch/ its use AbortSignal https://developer.mozilla.org/ru/docs/Web/API/AbortSignal

If the user changes his mind about sending a transaction, he should be able to exit of the UI. Like on screen.
It's may happen after call connector.sendTransaction, in this case dapp can hide own UI, but can't abort transaction in wallet UI

Of course, this does not affect the blockchain, only UI

[Gusarich]

@stels-cs user can just cancel the tx in his wallet UI. What's the problem with that?

[stels-cs]

@stels-cs user can just cancel the tx in his wallet UI. What's the problem with that?

This is not convenient when you use a computer and a wallet in your phone.

[tvorogme]

Currently, connector.sendTransaction returned signed boc. For better API calls, I suggest to return transaction hash (wallet is 100% sure that the transaction is processed, so it must have a hash of it?). It's quite hard to find a transaction by signed boc on scale of 100k+ users.

[tolya-yanot]

Currently, connector.sendTransaction returned signed boc. For better API calls, I suggest to return transaction hash (wallet is 100% sure that the transaction is processed, so it must have a hash of it?). It's quite hard to find a transaction by signed boc on scale of 100k+ users.

Maybe it can be done as a separate event - immediately at the time of sending, return a message or message hash, and then send an event with a hash of the transaction

[tolya-yanot]

Since some wallets (hardware wallets or custom wallets such as a lockup wallet) will probably never support multiple messages in one SendTransaction, the parameter maxMessages: number added to the Feature SendTransaction.

The Feature format has also been changed so that the wallet can return more information if required.

before:

type Feature = 'SendTransaction' | 'SignData';

after:

type Feature = { name: 'SendTransaction', maxMessages: number } | { name: 'SignData' };

For some time in the process of transition, wallets can return both format features = [ 'SendTransaction', 'SignData', { name: 'SendTransaction', maxMessages: number }, { name: 'SignData' } ] for backward compatibility.

[tolya-yanot]

Add way to abort transaction sent via connector.sendTransaction

like abortable fetch in browser api https://developer.chrome.com/blog/abortable-fetch/ its use AbortSignal https://developer.mozilla.org/ru/docs/Web/API/AbortSignal

If the user changes his mind about sending a transaction, he should be able to exit of the UI. Like on screen. It's may happen after call connector.sendTransaction, in this case dapp can hide own UI, but can't abort transaction in wallet UI

Of course, this does not affect the blockchain, only UI

NOTE: the response to the request to cancel sendTransaction must contain information whether the transaction signing was cancelled or whether the user has already sent it.

[tolya-yanot]

I think that it would be nice to implement the proposals #115 (comment) and #115 (comment) in one of the next versions of TON Connect protocol.