@tetherto/wdk-wallet-evm 1.0.0-beta.12 → 1.0.0-beta.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tetherto/wdk-wallet-evm",
3
- "version": "1.0.0-beta.12",
3
+ "version": "1.0.0-beta.13",
4
4
  "description": "A simple package to manage BIP-32 wallets for evm blockchains.",
5
5
  "keywords": [
6
6
  "wdk",
@@ -46,13 +46,13 @@
46
46
  "typescript": "5.8.3"
47
47
  },
48
48
  "overrides": {
49
- "brace-expansion": "1.1.13",
50
- "cookie": "1.0.2",
49
+ "brace-expansion": "1.1.15",
50
+ "cookie": "1.1.1",
51
51
  "immutable": "4.3.8",
52
52
  "picomatch@2": "2.3.2",
53
53
  "serialize-javascript": ">=7.0.5",
54
- "tmp": "0.2.5",
55
- "undici": ">=7.24.0",
54
+ "tmp": "0.2.6",
55
+ "undici": "8.3.0",
56
56
  "uuid": "14.0.0"
57
57
  },
58
58
  "exports": {
@@ -118,11 +118,15 @@ export default class WalletAccountEvm extends WalletAccountReadOnlyEvm {
118
118
  /**
119
119
  * The account's key pair.
120
120
  *
121
+ * The uint8 arrays are bound to the wallet account, so any external change will reflect to the internal representation. For this reason,
122
+ * it's strongly recommended to treat the key pair as a read-only view of the keys. While it's still technically possible to alter their
123
+ * content, client code should never do so.
124
+ *
121
125
  * @type {KeyPair}
122
126
  */
123
127
  get keyPair () {
124
128
  return {
125
- privateKey: this._account.privateKeyBuffer,
129
+ privateKey: this._account.privateKeyBuffer ?? null,
126
130
  publicKey: this._account.publicKeyBuffer
127
131
  }
128
132
  }
@@ -37,6 +37,10 @@ export default class WalletAccountEvm extends WalletAccountReadOnlyEvm implement
37
37
  /**
38
38
  * The account's key pair.
39
39
  *
40
+ * The uint8 arrays are bound to the wallet account, so any external change will reflect to the internal representation. For this reason,
41
+ * it's strongly recommended to treat the key pair as a read-only view of the keys. While it's still technically possible to alter their
42
+ * content, client code should never do so.
43
+ *
40
44
  * @type {KeyPair}
41
45
  */
42
46
  get keyPair(): KeyPair;