You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: advanced/multichain/rpc-reference/bitcoin-rpc.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -181,6 +181,10 @@ Assuming the dapp monitors all returned addresses for balance changes, a new req
181
181
182
182
The example below specifies a response from a static wallet. The returned address is used for both change and payments. It's the only address with UTXOs.
183
183
184
+
<Note>
185
+
Hardware wallets utilizing `bip32` are also supported.
Copy file name to clipboardExpand all lines: advanced/multichain/rpc-reference/sui-rpc.mdx
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,6 @@ description: Sui JSON-RPC Methods
5
5
6
6
These are the methods that wallets should implement to handle Sui transactions and messages via WalletConnect.
7
7
8
-
<Notetype="warning">
9
-
**Please note:** The SUI RPC standard is still under review and specifications may change. Implementation details and method signatures are subject to updates.
10
-
</Note>
11
-
12
8
## sui_getAccounts
13
9
14
10
This method returns an Array of public keys and addresses available to sign from the wallet.
@@ -47,7 +43,9 @@ This method returns an Array of public keys and addresses available to sign from
47
43
### Session Properties
48
44
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.
49
45
50
-
46
+
:::warning
47
+
This method is **required** for all wallets to implement in order to connect to applications using Sui Dappkit. Wallets that do not implement `sui_getAccounts` will not be able to establish connections with dapps using the Sui Dappkit SDK.
@@ -5,65 +5,81 @@ description: Tron JSON-RPC Methods
5
5
6
6
These are the methods that wallets should implement to handle Tron transactions and messages via WalletConnect.
7
7
8
-
<Notetype="warning">
9
-
**Please note:** The TRON RPC standard is still under review and specifications may change. Implementation details and method signatures are subject to updates.
10
-
</Note>
8
+
## Session Properties
9
+
10
+
To enable the new simplified transaction structure, wallets should include `tron_method_version: "v1"` in their `sessionProperties` during the connection handshake:
11
+
12
+
```json
13
+
{
14
+
"sessionProperties": {
15
+
"tron_method_version": "v1"
16
+
}
17
+
}
18
+
```
19
+
20
+
When `tron_method_version` is set to `"v1"`, the transaction structure is simplified to remove the nested `transaction.transaction` format. If not set, the legacy nested format is used for backward compatibility.
11
21
12
22
### tron_signTransaction
13
23
14
24
Sign a Tron transaction without executing it.
15
25
16
26
#### Parameters
17
27
18
-
1.`transaction` (object) - The transaction to sign:
28
+
- The transaction to sign:
19
29
-`address` (string) - The sender's Tron address
20
30
-`transaction` (object) - The transaction object to sign
21
31
22
32
#### Returns
23
33
24
-
`object`- The signed transaction:
25
-
-`txID` (string) - The transaction ID (deterministically derived from raw transaction)
26
-
-`signature` (array) - Array of signature strings
27
-
-`raw_data` (object) - The raw transaction data
28
-
-`raw_data_hex` (string) - The hex-encoded raw transaction data
29
-
-`visible` (boolean) - Whether addresses are in visible format
34
+
- The signed transaction:
35
+
-`txID` (string) - The transaction ID (deterministically derived from raw transaction)
36
+
-`signature` (array) - Array of signature strings
37
+
-`raw_data` (object) - The raw transaction data
38
+
-`raw_data_hex` (string) - The hex-encoded raw transaction data
39
+
-`visible` (boolean) - Whether addresses are in visible format
30
40
31
-
#### Example
41
+
<AccordionGroup>
42
+
<Accordiontitle="Legacy Format">
43
+
#### Example (Legacy Format)
32
44
45
+
- Request with the nested `transaction.transaction` format
@@ -30,6 +31,12 @@ For a full of list of RPC sources used by `wagmi/viem`, please refer to [Viem's
30
31
31
32
</Note>
32
33
34
+
<Note>
35
+
36
+
**Cross-Origin-Opener-Policy for Social Login Security**: The `Cross-Origin-Opener-Policy: same-origin-allow-popups` header is essential when using AppKit's social login features (Google, X, GitHub, Discord, Apple, Facebook, Farcaster). This header helps prevent tabnabbing attacks during OAuth flows by controlling how popup windows can interact with your application. Without this header, malicious sites could potentially hijack the authentication flow and redirect users to phishing pages.
0 commit comments