Skip to content

Commit

Permalink
fix docs establishing connection
Browse files Browse the repository at this point in the history
  • Loading branch information
NorbertBodziony committed Jul 25, 2023
1 parent 966d685 commit 1ce2934
Showing 1 changed file with 2 additions and 12 deletions.
14 changes: 2 additions & 12 deletions sdk/apps/docs/docs/application/connect.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,11 +23,10 @@ The other peer needs just to scan the QR code on its device. Extension wallets a

### Connect

Server sends a request to connect with the client. On the client side all information passed from application regarding the request will be displayed (website name, url, data).
Application builds a connection using `build()` or `buildLazy()` function that returns interface to communicated with remote user. App should define `AppMetadata` so wallets will be able to show it to user.

Application builds a connection using `build()` function that returns interface to communicated with remote user.
To start sending request like `signTransaction` user first need to connect to session.
Once user establishes connection, application will get public key and the connection is now confirmed.
Once user establishes connection, application will get public key and the connection will be confirmed.

API of application client is fit to match currently existing standards of corresponding blockchains

Expand All @@ -39,15 +38,6 @@ interface AppMetadata {
icon?: string; // Url of app image
additionalInfo?: string;
}

interface AppBaseInitialize {
appMetadata: AppMetadata;
network?: Network;
url?: string; // Relay endpoint default nc2.nightly.app
timeout?: number;
persistentSessionId?: string; // Apps can reuse old connection to skip connect step.
persistent?: boolean; // Makes session valid for 14 days
}
```

<Tabs>
Expand Down

0 comments on commit 1ce2934

Please sign in to comment.