@meshsdk/wallet 1.9.0-beta.26 → 1.9.0-beta.27

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/dist/index.cjs CHANGED
@@ -986,7 +986,7 @@ var BrowserWallet = class _BrowserWallet {
986
986
  return wallets;
987
987
  }
988
988
  /**
989
- * This is the entrypoint to start communication with the user's wallet. The wallet should request the user's permission to connect the web page to the user's wallet, and if permission has been granted, the wallet will be returned and exposing the full API for the dApp to use.
989
+ * This is the entrypoint to start communication with the user's wallet. The wallet should request the user's permission to connect the web page to the user's wallet, and if permission has been granted, the wallet will be returned and exposing the full API for the app to use.
990
990
  *
991
991
  * Query BrowserWallet.getInstalledWallets() to get a list of available wallets, then provide the wallet name for which wallet the user would like to connect with.
992
992
  *
@@ -1192,7 +1192,7 @@ var BrowserWallet = class _BrowserWallet {
1192
1192
  /**
1193
1193
  * Submits the signed transaction to the blockchain network.
1194
1194
  *
1195
- * As wallets should already have this ability to submit transaction, we allow dApps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the dApp to track. The wallet can return error messages or failure if there was an error in sending it.
1195
+ * As wallets should already have this ability to submit transaction, we allow apps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the app to track. The wallet can return error messages or failure if there was an error in sending it.
1196
1196
  *
1197
1197
  * @param tx
1198
1198
  * @returns a transaction hash
@@ -1890,7 +1890,7 @@ var MeshWallet = class {
1890
1890
  /**
1891
1891
  * Submits the signed transaction to the blockchain network.
1892
1892
  *
1893
- * As wallets should already have this ability to submit transaction, we allow dApps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the dApp to track. The wallet can return error messages or failure if there was an error in sending it.
1893
+ * As wallets should already have this ability to submit transaction, we allow apps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the app to track. The wallet can return error messages or failure if there was an error in sending it.
1894
1894
  *
1895
1895
  * @param tx - a signed transaction in CBOR
1896
1896
  * @returns a transaction hash
package/dist/index.d.cts CHANGED
@@ -112,7 +112,7 @@ declare global {
112
112
  /**
113
113
  * Browser Wallet provides a set of APIs to interact with the blockchain. This wallet is compatible with Mesh transaction builders.
114
114
  *
115
- * These wallets APIs are in accordance to CIP-30, which defines the API for dApps to communicate with the user's wallet. Additional utility functions provided for developers that are useful for building applications.
115
+ * These wallets APIs are in accordance to CIP-30, which defines the API for apps to communicate with the user's wallet. Additional utility functions provided for developers that are useful for building applications.
116
116
  * ```javascript
117
117
  * import { BrowserWallet } from '@meshsdk/core';
118
118
  *
@@ -145,7 +145,7 @@ declare class BrowserWallet implements IWallet {
145
145
  */
146
146
  static getInstalledWallets(): Wallet[];
147
147
  /**
148
- * This is the entrypoint to start communication with the user's wallet. The wallet should request the user's permission to connect the web page to the user's wallet, and if permission has been granted, the wallet will be returned and exposing the full API for the dApp to use.
148
+ * This is the entrypoint to start communication with the user's wallet. The wallet should request the user's permission to connect the web page to the user's wallet, and if permission has been granted, the wallet will be returned and exposing the full API for the app to use.
149
149
  *
150
150
  * Query BrowserWallet.getInstalledWallets() to get a list of available wallets, then provide the wallet name for which wallet the user would like to connect with.
151
151
  *
@@ -240,7 +240,7 @@ declare class BrowserWallet implements IWallet {
240
240
  /**
241
241
  * Submits the signed transaction to the blockchain network.
242
242
  *
243
- * As wallets should already have this ability to submit transaction, we allow dApps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the dApp to track. The wallet can return error messages or failure if there was an error in sending it.
243
+ * As wallets should already have this ability to submit transaction, we allow apps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the app to track. The wallet can return error messages or failure if there was an error in sending it.
244
244
  *
245
245
  * @param tx
246
246
  * @returns a transaction hash
@@ -673,7 +673,7 @@ declare class MeshWallet implements IWallet {
673
673
  /**
674
674
  * Submits the signed transaction to the blockchain network.
675
675
  *
676
- * As wallets should already have this ability to submit transaction, we allow dApps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the dApp to track. The wallet can return error messages or failure if there was an error in sending it.
676
+ * As wallets should already have this ability to submit transaction, we allow apps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the app to track. The wallet can return error messages or failure if there was an error in sending it.
677
677
  *
678
678
  * @param tx - a signed transaction in CBOR
679
679
  * @returns a transaction hash
package/dist/index.d.ts CHANGED
@@ -112,7 +112,7 @@ declare global {
112
112
  /**
113
113
  * Browser Wallet provides a set of APIs to interact with the blockchain. This wallet is compatible with Mesh transaction builders.
114
114
  *
115
- * These wallets APIs are in accordance to CIP-30, which defines the API for dApps to communicate with the user's wallet. Additional utility functions provided for developers that are useful for building applications.
115
+ * These wallets APIs are in accordance to CIP-30, which defines the API for apps to communicate with the user's wallet. Additional utility functions provided for developers that are useful for building applications.
116
116
  * ```javascript
117
117
  * import { BrowserWallet } from '@meshsdk/core';
118
118
  *
@@ -145,7 +145,7 @@ declare class BrowserWallet implements IWallet {
145
145
  */
146
146
  static getInstalledWallets(): Wallet[];
147
147
  /**
148
- * This is the entrypoint to start communication with the user's wallet. The wallet should request the user's permission to connect the web page to the user's wallet, and if permission has been granted, the wallet will be returned and exposing the full API for the dApp to use.
148
+ * This is the entrypoint to start communication with the user's wallet. The wallet should request the user's permission to connect the web page to the user's wallet, and if permission has been granted, the wallet will be returned and exposing the full API for the app to use.
149
149
  *
150
150
  * Query BrowserWallet.getInstalledWallets() to get a list of available wallets, then provide the wallet name for which wallet the user would like to connect with.
151
151
  *
@@ -240,7 +240,7 @@ declare class BrowserWallet implements IWallet {
240
240
  /**
241
241
  * Submits the signed transaction to the blockchain network.
242
242
  *
243
- * As wallets should already have this ability to submit transaction, we allow dApps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the dApp to track. The wallet can return error messages or failure if there was an error in sending it.
243
+ * As wallets should already have this ability to submit transaction, we allow apps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the app to track. The wallet can return error messages or failure if there was an error in sending it.
244
244
  *
245
245
  * @param tx
246
246
  * @returns a transaction hash
@@ -673,7 +673,7 @@ declare class MeshWallet implements IWallet {
673
673
  /**
674
674
  * Submits the signed transaction to the blockchain network.
675
675
  *
676
- * As wallets should already have this ability to submit transaction, we allow dApps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the dApp to track. The wallet can return error messages or failure if there was an error in sending it.
676
+ * As wallets should already have this ability to submit transaction, we allow apps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the app to track. The wallet can return error messages or failure if there was an error in sending it.
677
677
  *
678
678
  * @param tx - a signed transaction in CBOR
679
679
  * @returns a transaction hash
package/dist/index.js CHANGED
@@ -1017,7 +1017,7 @@ var BrowserWallet = class _BrowserWallet {
1017
1017
  return wallets;
1018
1018
  }
1019
1019
  /**
1020
- * This is the entrypoint to start communication with the user's wallet. The wallet should request the user's permission to connect the web page to the user's wallet, and if permission has been granted, the wallet will be returned and exposing the full API for the dApp to use.
1020
+ * This is the entrypoint to start communication with the user's wallet. The wallet should request the user's permission to connect the web page to the user's wallet, and if permission has been granted, the wallet will be returned and exposing the full API for the app to use.
1021
1021
  *
1022
1022
  * Query BrowserWallet.getInstalledWallets() to get a list of available wallets, then provide the wallet name for which wallet the user would like to connect with.
1023
1023
  *
@@ -1223,7 +1223,7 @@ var BrowserWallet = class _BrowserWallet {
1223
1223
  /**
1224
1224
  * Submits the signed transaction to the blockchain network.
1225
1225
  *
1226
- * As wallets should already have this ability to submit transaction, we allow dApps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the dApp to track. The wallet can return error messages or failure if there was an error in sending it.
1226
+ * As wallets should already have this ability to submit transaction, we allow apps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the app to track. The wallet can return error messages or failure if there was an error in sending it.
1227
1227
  *
1228
1228
  * @param tx
1229
1229
  * @returns a transaction hash
@@ -1937,7 +1937,7 @@ var MeshWallet = class {
1937
1937
  /**
1938
1938
  * Submits the signed transaction to the blockchain network.
1939
1939
  *
1940
- * As wallets should already have this ability to submit transaction, we allow dApps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the dApp to track. The wallet can return error messages or failure if there was an error in sending it.
1940
+ * As wallets should already have this ability to submit transaction, we allow apps to request that a transaction be sent through it. If the wallet accepts the transaction and tries to send it, it shall return the transaction ID for the app to track. The wallet can return error messages or failure if there was an error in sending it.
1941
1941
  *
1942
1942
  * @param tx - a signed transaction in CBOR
1943
1943
  * @returns a transaction hash
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@meshsdk/wallet",
3
- "version": "1.9.0-beta.26",
3
+ "version": "1.9.0-beta.27",
4
4
  "description": "Wallets - https://meshjs.dev/apis/wallets",
5
5
  "main": "./dist/index.cjs",
6
6
  "browser": "./dist/index.js",
@@ -35,9 +35,9 @@
35
35
  "typescript": "^5.3.3"
36
36
  },
37
37
  "dependencies": {
38
- "@meshsdk/common": "1.9.0-beta.26",
39
- "@meshsdk/core-cst": "1.9.0-beta.26",
40
- "@meshsdk/transaction": "1.9.0-beta.26",
38
+ "@meshsdk/common": "1.9.0-beta.27",
39
+ "@meshsdk/core-cst": "1.9.0-beta.27",
40
+ "@meshsdk/transaction": "1.9.0-beta.27",
41
41
  "@simplewebauthn/browser": "^13.0.0"
42
42
  },
43
43
  "prettier": "@meshsdk/configs/prettier",