tonkeeper / ton-connect Goto Github PK

Is it ok to use this? to auth the users of our dApp with tonkeeper, need to ask to respect your opinion, since there isn´t a license

Bug Type

Functional

Reproduction steps

When running npm run compile or yarn compile the job fails
with the output

Actual result

➜  sdk git:(main) npm run compile

> [email protected] compile
> ttsc

src/ton-connect/core/models/index.ts:2:41 - error TS2307: Cannot find module './transaction-request' or its corresponding type declarations.

2 export type { TransactionRequest } from './transaction-request';
                                          ~~~~~~~~~~~~~~~~~~~~~~~

src/ton-connect/core/models/index.ts:3:34 - error TS2307: Cannot find module './sign-request' or its corresponding type declarations.

3 export type { SignRequest } from './sign-request';
                                   ~~~~~~~~~~~~~~~~

src/widget/widget-controller.ts:30:9 - error TS2322: Type 'SendTransactionResponse' is not assignable to type 'boolean'.

30         return this.connector.sendTransaction(tx);
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/widget/widget-controller.ts:41:9 - error TS2322: Type 'SignMessageResponse' is not assignable to type 'string'.

41         return this.connector.sign(signRequest);
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Found 4 errors in 2 files.

Errors  Files
     2  src/ton-connect/core/models/index.ts:2
     2  src/widget/widget-controller.ts:30
     
     ```

### Expected result

Should be compile typescript

### Suggested Severity

Critical

### Device

Node.js  Version
v17.8.0

### Additional Context

_No response_

UPDATE: Ton connect 2.0 is moved to a separate github org: https://github.com/ton-connect

Use-cases to focus on

Primary: mobile dapps serverless or via Telegram bots (TWA) working together with mobile native wallets.

Secondary:

• server applications,
• desktop web- or standalone apps with mobile wallets,
• web dapps running as extensions within the mobile wallet.

Tertiary: web-apps working with a chrome extension, and non-native wallets.

Architecture

1. Each wallet provides a bridging service for the app to connect with. User selects a wallet explicitly in the "Connect with TON" prompt.
2. SSE and POST requests over the bridge.
3. Sessions can be re-started at whim by the dapp.
4. Single SDK to initiate connections.
5. Separate starting points for connecting a wallet (passing over the unauthenticated wallet address) & signing in.

Checklist

• Define the JS API for initiating connections and setting up the prompt.
• Define the format for wallets' descriptions with their bridge addresses, icons and names.
• Ton Connect prompt design and layout (buttons, modal window with wallet buttons, pending confirmation window). Moved to a separate library; we'll focus on pure API in initial release.
• Message encoding connect requests and responses: connect, sign in, sign tx.
• Define a mechanism for attaching TON.DNS records immutably - as DNS items or via a separate registry. Serverless dapps don't have their own backend and do not use DNS authentication.