did-beta-bch 2.0.0 → 2.0.1
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/README.md +8 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -89,6 +89,14 @@ For WalletConnect, the adapter maps this call to `bch_signMessage` with the
|
|
|
89
89
|
message in its params. WizardConnect needs a separate wallet-side signing action
|
|
90
90
|
and adapter; neither is implemented in this package.
|
|
91
91
|
|
|
92
|
+
The signer is supplied by the integrating wallet, so this library does not
|
|
93
|
+
require users to connect to Selene, Paytaca, or any other external wallet. A
|
|
94
|
+
wallet can pass its own non-custodial BCH signer directly. For example, Cashlet
|
|
95
|
+
uses its own BCH keys by default; its optional WalletConnect adapter is only for
|
|
96
|
+
users who choose to bind an address held by another compatible wallet. In either
|
|
97
|
+
case, the BCH key signs the proof while a separate Nostr key signs the published
|
|
98
|
+
event.
|
|
99
|
+
|
|
92
100
|
### Key derivation (NIP-06)
|
|
93
101
|
|
|
94
102
|
```ts
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "did-beta-bch",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.1",
|
|
4
4
|
"description": "Decentralised identity protocol binding BCH addresses to Nostr public keys",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|
|
@@ -49,4 +49,4 @@
|
|
|
49
49
|
"esbuild": "^0.28.2",
|
|
50
50
|
"typescript": "^5.4.0"
|
|
51
51
|
}
|
|
52
|
-
}
|
|
52
|
+
}
|