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: bip-0329.mediawiki
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,6 +62,9 @@ Each JSON object must contain 3 or 4 key/value pairs, defined as follows:
62
62
|-
63
63
| <tt>origin</tt>
64
64
| Optional key origin information referencing the wallet associated with the label
65
+
|-
66
+
| <tt>spendable</tt>
67
+
| One of <tt>true</tt> or <tt>false</tt>, denoting if an output should be spendable by the wallet
65
68
|}
66
69
67
70
The reference is defined for each <tt>type</tt> as follows:
@@ -110,6 +113,7 @@ For security reasons no private key types are defined.
110
113
* An importing wallet may ignore records it does not store, and truncate labels if necessary. A suggested default for maximum label length is 255 characters, and an importing wallet should consider warning the user if truncation is applied.
111
114
* Wallets importing public key records may derive addresses from them to match against known wallet addresses.
112
115
* Wallets importing extended public keys may match them against signers, for example in a multisig setup.
116
+
* Wallets importing outputs should respect the <tt>spendable</tt> state, defaulting to <tt>true</tt> if none is found
113
117
114
118
==Backwards Compatibility==
115
119
@@ -124,7 +128,7 @@ The following fragment represents a wallet label export:
0 commit comments