chore: move serialization to method spec

Author: tomiir

advanced/multichain/rpc-reference/bitcoin-rpc.mdx

@@ -33,13 +33,6 @@ If the wallet user changes to account 1 we get path `m/84'/0'/1'/0/0` with ident
 - `m/86'/0'/1'/change/address_index`
 
 
-## Connection
-### Session Properties
-
-In a connection request, all wallets **should** serialize the connected accounts in `session.sessionProperties.bip122_getAccountAddresses`. This allows dapps to consume an active session without requiring a context switch to re-request all addresses and associated public keys and paths from the wallet.
-
-## RPC Methods
-
 ## sendTransfer
 
 This method is used to sign and submit a transfer of any `amount` of Bitcoin to a single `recipientAddress`, optionally including a `changeAddress` for the change amount and `memo` set as an OP_RETURN output by supporting wallets. The transaction will be signed and broadcast upon user approval.
@@ -119,6 +112,10 @@ We recognize that there are two broad classes of wallets in use today:
     - `path` : `String` - _(Optional)_ Derivation path of the address e.g. "m/84'/0'/0'/0/0".
     - `intention` : `String` - _(Optional)_ Intention of the address, e.g. "payment" or "ordinal".
 
+### Session Properties
+In a connection request, it is recommended to serialize the response to `getAccountAddresses` in `session.sessionProperties.bip122_getAccountAddresses`. This allows dapps to consume an active session without requiring a context switch to re-request all addresses and associated public keys from the wallet.
+
+
 ### Example: Dynamic Wallet
 
 The example below specifies a result from a dynamic wallet. For the sake of this example, receive and change addresses with index 3-4 are considered unused and addresses with paths `m/49'/0'/0'/0/7` and `m/84'/0'/0'/0/2` are considered to have UTXOs.

advanced/multichain/rpc-reference/stacks-rpc.mdx

@@ -4,14 +4,6 @@ description: Stacks JSON-RPC Methods
 ---
 
 
-## Conection
-
-### Session Properties
-
-In a connection request, all wallets **should** serialize the connected accounts in `session.sessionProperties.stacks_getAddresses`. This allows dapps to consume an active session without requiring a context switch to re-request all addresses and associated public keys from the wallet.
-
-## RPC Methods
-
 These are the methods that wallets should implement to handle Stacks transfers and messages via WalletConnect.
 
 ## stx_transferStx
@@ -96,4 +88,43 @@ For signing a message with wallet users private key.
 }
 ```
 
-- `signature` - The signature of the message
+- `signature` - The signature of the message
+
+
+
+
+## stx_getAddresses
+
+For requesting the wallet addresses
+
+### Request
+
+```json
+{
+  "id": 1,
+  "jsonrpc": "2.0",
+  "method": "stx_getAddresses",
+}
+```
+
+### Response
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 1,
+  "result": {
+    "accounts": [
+      { 
+        "address": "SP23....",
+        "publicKey": "ab12031..."
+      }
+    ]
+  }
+}
+```
+
+- `accounts`: The connected accounts with their address and publicKey
+
+
+### Session Properties
+In a connection request, it is recommended to serialize the response to `getAddresses` in `session.sessionProperties.stacks_getAddresses`. This allows dapps to consume an active session without requiring a context switch to re-request all addresses and associated public keys from the wallet.

advanced/multichain/rpc-reference/sui-rpc.mdx

@@ -3,21 +3,12 @@ title: "Sui"
 description: Sui JSON-RPC Methods
 ---
 
+These are the methods that wallets should implement to handle Sui transactions and messages via WalletConnect.
 
 <Note type="warning">
 **Please note:** The SUI RPC standard is still under review and specifications may change. Implementation details and method signatures are subject to updates.
 </Note>
 
-## Conection
-
-### Session Properties
-
-In a connection request, all wallets **should** serialize the connected accounts in `session.sessionProperties.sui_getAccounts`. This allows dapps to consume an active session without requiring a context switch to re-request all addresses and associated public keys from the wallet.
-
-## RPC Methods
-
-These are the methods that wallets should implement to handle Sui transactions and messages via WalletConnect.
-
 ## sui_getAccounts
 
 This method returns an Array of public keys and addresses available to sign from the wallet.
@@ -53,7 +44,12 @@ This method returns an Array of public keys and addresses available to sign from
 }
 ```
 
-### sui_signTransaction
+### Session Properties
+In a connection request, it is recommended to serialize the response to `getAccounts` in `session.sessionProperties.sui_getAccounts`. This allows dapps to consume an active session without requiring a context switch to re-request all addresses and associated public keys from the wallet.
+
+
+
+## sui_signTransaction
 
 Sign a Sui transaction without executing it.