Merge branch 'merge-v0.7.x' of https://github.com/WalletConnect/walletconnect-docs into v0.7.x

Author: pedrouid

README.md

@@ -18,8 +18,7 @@ To reference all the Bridge API calls go to [Bridge API](bridge-api.md)
 
 Share your experience, contribute or ask questions with the WalletConnect Community
 
-* Github: [https://github.com/walletconnect](https://github.com/walletconnect)
-* Telegram: [https://t.me/walletconnect](https://t.me/walletconnect)
-* Forum: [https://discuss.walletconnect.org](https://discuss.walletconnect.org)
-* Discord: [https://discord.walletconnect.org](https://discord.walletconnect.org)
-
+- Github: [https://github.com/walletconnect](https://github.com/walletconnect)
+- Telegram: [https://t.me/walletconnect](https://t.me/walletconnect)
+- Forum: [https://discuss.walletconnect.org](https://discuss.walletconnect.org)
+- Discord: [https://discord.walletconnect.org](https://discord.walletconnect.org)

SUMMARY.md

@@ -1,7 +1,6 @@
 # Table of contents
 
-* [WalletConnect v0.7.x](README.md)
-* [Quick Start](quick-start.md)
-* [Technical Specification](tech-spec.md)
-* [Bridge API](bridge-api.md)
-
+- [WalletConnect v0.7.x](README.md)
+- [Quick Start](quick-start.md)
+- [Technical Specification](tech-spec.md)
+- [Bridge API](bridge-api.md)

assets/walletconnect-accounts-diagram.png

@@ -1,137 +0,0 @@
-# Bridge API
-
-## For Dapps
-
-### Create a new Session
-
-```bash
-  POST https://bridge.walletconnect.org/session/new
-
-  Response:
-  Status: 200
-  Content-Type: application/json; charset=utf-8
-  Body:
-  {
-    "sessionId": <someSessionId>
-  }
-```
-
-### Get Session details \(short-polling\)
-
-```bash
-  GET https://bridge.walletconnect.org/session/<sessionId>
-
-  Response (when details exist):
-  Status: 200
-  Content-Type: application/json; charset=utf-8
-  Body:
-  {
-    "encryptionPayload": <encryptedSessionPayload>
-  }
-
-  Response (when details do not yet exist):
-  Status: 204
-```
-
-### Create new Call Request
-
-```bash
-  POST https://bridge.walletconnect.org/session/<sessionId>/call/new
-  Content-Type: application/json
-  Body:
-  {
-    "encryptionPayload": <encryptedCallRequestPayload>,
-    "dappName": <ExampleDappName>
-  }
-
-  Response:
-  Status: 200
-  Content-Type: application/json; charset=utf-8
-  Body:
-  {
-      "callId": <callId>
-  }
-```
-
-### Get Call status \(short-polling\)
-
-```bash
-  GET https://bridge.walletconnect.org/call-status/<callId>
-
-  Response (when status does exist):
-  Status: 200
-  Content-Type: application/json; charset=utf-8
-  {
-    "encryptionPayload": <encryptedCallStatus>
-  }
-
-  Response (when status does not yet exist):
-  Status: 204
-```
-
-## For Wallets
-
-### Update Session details
-
-```bash
-  PUT https://bridge.walletconnect.org/session/<sessionId>
-  Content-Type: application/json
-  Body:
-  {
-    "encryptionPayload":<someEncryptedSessionPayload>,
-    "push": {
-      "type": <pushType>,
-      "token": <pushToken>,
-      "webhook": <pushWebhook>
-    }
-  }
-
-  Response:
-  Status: 200
-```
-
-### Get Call Request details
-
-```bash
-  GET https://bridge.walletconnect.org/session/<sessionId>/call/<callId>
-
-  Response:
-  Status: 200
-  Content-Type: application/json; charset=utf-8
-  Body:
-  {
-    "encryptionPayload": <encryptedCallRequest>
-  }
-```
-
-### Get All Call Requests available
-
-```bash
-  GET https://bridge.walletconnect.org/session/<sessionId>/calls
-
-  Response:
-  Status: 200
-  Content-Type: application/json; charset=utf-8
-  Body:
-  {
-    <callId>: {
-      "encryptionPayload": <encryptedCallRequest>
-    },
-    ...
-  }
-```
-
-### Add Call Status
-
-```bash
-  POST https://bridge.walletconnect.org/call-status/<callId>/new
-  Content-Type: application/json
-  Body:
-  {
-    "encryptionPayload": <encryptedCallStatus>
-  }
-
-  Response:
-  Status: 200
-```
-

assets/walletconnect-transaction-diagram.png

@@ -331,4 +331,3 @@ const signedMessage = await web3.eth.sign(msg)
  */
 const signedTypedData = await web3.eth.signTypedData(msg)
 ```
-

bridge-api.md

@@ -23,17 +23,17 @@ The core of the design is enable data to be realyed between a desktop Dapp and a
 
 The session data includes 3 parameters:
 
-* Session ID
-* Bridge Url
-* Symmetric Key
+- Session ID
+- Bridge Url
+- Symmetric Key
 
 Provided with the symmetric key the Dapp and the Wallet can now relay data in and end-to-end encrypted communication. From the Bridge viewpoint it is simply relaying encrypted payload between two parties. The Wallet will also be notified about Dapp requests that require User consent thus it can optionally share push notification data with the Bridge to trigger notifications on the User's device
 
 The push notification data includes:
 
-* Push Type
-* Push Token
-* Push Webhook
+- Push Type
+- Push Token
+- Push Webhook
 
 Given the technical overview of the core design, in the next section we will describe the detailed communication between the Dapp and the Wallet.
 
@@ -43,8 +43,8 @@ The WalletConnect protocol has fundamentally 2 types of communications that are
 
 The 2 types of communication are:
 
-* Session Requests
-* Call Requests
+- Session Requests
+- Call Requests
 
 Session requests are similar to when a Dapp requests Metamask the User's accounts with the difference that instead of prompting the User to unlock Metamask, the User is prompted to scan the WalletConnect QR Code with the mobile Wallet. Analogous to the EIP 1102, the User can approve or reject the session request to expose the User's accounts from the Wallet to Dapp.