From 1ce2934371744d98666de522a5c0f4db8a7174c1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?NB=F0=9F=98=88?= Date: Tue, 25 Jul 2023 10:08:13 +0200 Subject: [PATCH] fix docs establishing connection --- sdk/apps/docs/docs/application/connect.md | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/sdk/apps/docs/docs/application/connect.md b/sdk/apps/docs/docs/application/connect.md index 5b163956..daee9d0e 100644 --- a/sdk/apps/docs/docs/application/connect.md +++ b/sdk/apps/docs/docs/application/connect.md @@ -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 @@ -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 -} ```