@eos3/connect 0.1.1 → 0.1.2
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 +7 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -50,11 +50,17 @@ await eosConnect.checkWallet();
|
|
|
50
50
|
`network` can be `testnet` or `mainnet`. It selects browser signing RPC
|
|
51
51
|
failover list, chain id metadata, and balance asset. The SDK does not include a
|
|
52
52
|
hosted wallet API or a Telegram bot. If `apiBaseUrl` is omitted, requests use
|
|
53
|
-
same-origin paths such as `/api/tg-wallet/me`.
|
|
53
|
+
same-origin paths such as `/api/tg-wallet/me`. `apiBaseUrl` points to the EOS
|
|
54
|
+
Passkey API or to your same-origin proxy for that API; it is not the passkey bind
|
|
55
|
+
page URL.
|
|
54
56
|
When `botUsername` is set, the SDK sends it as `x-telegram-bot-username` so a
|
|
55
57
|
shared backend can choose the correct Telegram bot token for `initData`
|
|
56
58
|
verification.
|
|
57
59
|
|
|
60
|
+
`connectTelegram()` opens the `bindUrl` returned by the API. The API should
|
|
61
|
+
generate that URL from its `WEB_BASE_URL`, so users leave the Mini App and finish
|
|
62
|
+
passkey authentication on the hosted passkey binding page.
|
|
63
|
+
|
|
58
64
|
## Connect a Telegram Wallet
|
|
59
65
|
|
|
60
66
|
```ts
|