From 27ab09dc7ec7ef7994963f9444c71c09768b2149 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 09:50:09 +0200 Subject: [PATCH 01/12] Update terms-of-use.mdx --- landing/tos/terms-of-use.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/landing/tos/terms-of-use.mdx b/landing/tos/terms-of-use.mdx index 3b26109..3bc2066 100644 --- a/landing/tos/terms-of-use.mdx +++ b/landing/tos/terms-of-use.mdx @@ -9,7 +9,7 @@ Welcome to Particle Network and/or Dashboard. Particle Network (the “**Site** ### 1. Use of the Site -You must be of legal age to enter into contracts where you reside to use our Site. We do not knowingly collect or solicit personally identifiable information from individuals under 18. If you are under 18, please do not attempt to use the Services or send any personal information about yourself to us. If we learn we have collected personal information from an individual under 18, we will delete that information as quickly as possible. You will comply with all applicable laws, rules, and regulations in connection with your use of the Site. You will not violate or attempt to violate the security of the Site or Particle Network’s systems or network security, including, without limitation by (i) accessing data not intended for users of the Site or gainning unauthorized access to an account, server or any other computer system(ii) attempting to probe, scan or test the vulnerability of a system or network or to breach security or authentication measures;(iii) attempting to interfere with the function of the Site, host or network. You may not “**crawl**,” “**scrape**,” or “**spider**” any portion of the Site (through the use of manual or automated means);(iv) attempt to access another user’s private key or other login information to a digital asset wallet without such user’s explicit consent subject to a previously disclosed privacy policy;(v) framing or mirroring any part of the Site without our express prior written consent; or(vi) impersonating or pretending to be anyone else but you, falsely stating, or otherwise misrepresenting your affiliation with any person or entity in connection with the Site, or expressly or implicitly suggesting that we endorse any statement you make. +You must be of legal age to enter into contracts where you reside to use our Site. We do not knowingly collect or solicit personally identifiable information from individuals under 18. If you are under 18, please do not attempt to use the Services or send any personal information about yourself to us. If we learn we have collected personal information from an individual under 18, we will delete that information as quickly as possible. You will comply with all applicable laws, rules, and regulations in connection with your use of the Site. You will not violate or attempt to violate the security of the Site or Particle Network’s systems or network security, including, without limitation by (i) accessing data not intended for users of the Site or gaining unauthorized access to an account, server or any other computer system(ii) attempting to probe, scan or test the vulnerability of a system or network or to breach security or authentication measures;(iii) attempting to interfere with the function of the Site, host or network. You may not “**crawl**,” “**scrape**,” or “**spider**” any portion of the Site (through the use of manual or automated means);(iv) attempt to access another user’s private key or other login information to a digital asset wallet without such user’s explicit consent subject to a previously disclosed privacy policy;(v) framing or mirroring any part of the Site without our express prior written consent; or(vi) impersonating or pretending to be anyone else but you, falsely stating, or otherwise misrepresenting your affiliation with any person or entity in connection with the Site, or expressly or implicitly suggesting that we endorse any statement you make. ### 2. Information Not Confidential @@ -33,7 +33,7 @@ THE SITE, INCLUDING, WITHOUT LIMITATION, THE SITE AND ALL CONTENT AND FUNCTIONAL ### 7. Limitation of Liability -TO THE GREATEST EXTENT PERMITTED UNDER APPLICABLE LAW, IN NO EVENT WILL PARTICLE NETWORK, ITS AFFILIATES (INCLUDING AFFILIATED FUNDS) OR ANY OF ITS OR THEIR RESPECTIVE DIRECTORS, OFFICERS, EMPLOYEES, AGENTS, SUPPLIERS OR LICENSORS (THE “**PARTICLE NETWORK PARTIES**”), BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES ARISING FROM OR IN CONNECTION WITH THE USE OF, OR THE INABILITY TO USE, THE SITE OR THE CONTENT, EVEN IF ANY PARTICLE NETWORK PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY SO SOME OF THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU.IN NO EVENT WILL THE TOTAL LIABILITY OF ANY PARTICLE NETWORK PARTY TO YOU FOR ALL DAMAGES, LOSSES, AND CAUSES OF ACTION (WHETHER IN CONTRACT OR TORT, INCLUDING, BUT NOT LIMITED TO, NEGLIGENCE OR OTHERWISE) ARISING FROM OR RELATED TO THE TERMS, THE CONTENT, AND/OR YOUR USE OF THE SITE, EXCEED, IN THE AGGREGATE, \\$100.00. +TO THE GREATEST EXTENT PERMITTED UNDER APPLICABLE LAW, IN NO EVENT WILL PARTICLE NETWORK, ITS AFFILIATES (INCLUDING AFFILIATED FUNDS) OR ANY OF ITS OR THEIR RESPECTIVE DIRECTORS, OFFICERS, EMPLOYEES, AGENTS, SUPPLIERS OR LICENSORS (THE “**PARTICLE NETWORK PARTIES**”), BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES ARISING FROM OR IN CONNECTION WITH THE USE OF, OR THE INABILITY TO USE, THE SITE OR THE CONTENT, EVEN IF ANY PARTICLE NETWORK PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY SO SOME OF THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. IN NO EVENT WILL THE TOTAL LIABILITY OF ANY PARTICLE NETWORK PARTY TO YOU FOR ALL DAMAGES, LOSSES, AND CAUSES OF ACTION (WHETHER IN CONTRACT OR TORT, INCLUDING, BUT NOT LIMITED TO, NEGLIGENCE OR OTHERWISE) ARISING FROM OR RELATED TO THE TERMS, THE CONTENT, AND/OR YOUR USE OF THE SITE, EXCEED, IN THE AGGREGATE, \\$100.00. ### 8. General Information From 8c1e05fbfa37a68b00a32659094e31b329abf1e6 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 09:54:44 +0200 Subject: [PATCH 02/12] Update flutter-quickstart.mdx --- .../wallet-as-a-service/waas/connect/flutter-quickstart.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/guides/wallet-as-a-service/waas/connect/flutter-quickstart.mdx b/guides/wallet-as-a-service/waas/connect/flutter-quickstart.mdx index 6e7cff6..f9f9564 100644 --- a/guides/wallet-as-a-service/waas/connect/flutter-quickstart.mdx +++ b/guides/wallet-as-a-service/waas/connect/flutter-quickstart.mdx @@ -28,7 +28,7 @@ flutter pub add particle_connect -After adding and installing the SDK, you're ready to move onto configuration; this will differ depending on the platform you intend on using (iOS or Android). +After adding and installing the SDK, you're ready to move on to configuration; this will differ depending on the platform you intend on using (iOS or Android). But beforehand, you'll need to retrieve three key values from the [Particle dashboard](https://dashboard.particle.network): your project ID, client key, and app ID. These are used to authenticate your instance of Particle Connect and connect your project to the dashboard; these are required to properly initialize the SDK, regardless of platform. @@ -174,7 +174,7 @@ With these requirements set, you'll need to open an exported iOS project and fin - At the root of your Xcode project, create a new file, `ParticleNetwork-Info.plist` . Ensure this is marked under "Target Membership." + At the root of your Xcode project, create a new file, `ParticleNetwork-Info.plist`. Ensure this is marked under "Target Membership." From here, with a fresh `ParticleNetwork-Info.plist` file, go ahead and fill it in with the values previously retrieved from the [Particle dashboard](https://dashboard.particle.network): @@ -410,4 +410,4 @@ ParticleWallet.setSupportChain(chainInfos); ParticleWallet.navigatorWallet(); ``` - To implement account abstraction within your Flutter project, integrate the `particle_aa` SDK and refer to this [documentation](/api-reference/aa/sdks/mobile/flutter). Additionally, a demo repository can be found [here](https://github.com/Particle-Network/particle-flutter/tree/master/particle-aa/example). \ No newline at end of file + To implement account abstraction within your Flutter project, integrate the `particle_aa` SDK and refer to this [documentation](/api-reference/aa/sdks/mobile/flutter). Additionally, a demo repository can be found [here](https://github.com/Particle-Network/particle-flutter/tree/master/particle-aa/example). From 91f38eb3867e5c19de2b89e7b3688366b42f59e6 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 09:55:47 +0200 Subject: [PATCH 03/12] Update android-quickstart.mdx --- guides/wallet-as-a-service/waas/auth/android-quickstart.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/wallet-as-a-service/waas/auth/android-quickstart.mdx b/guides/wallet-as-a-service/waas/auth/android-quickstart.mdx index 876ccc1..a0b19ad 100644 --- a/guides/wallet-as-a-service/waas/auth/android-quickstart.mdx +++ b/guides/wallet-as-a-service/waas/auth/android-quickstart.mdx @@ -14,7 +14,7 @@ For complete documentation covering the implementation of Particle Auth on Andro --- -Before we begin installing and configuring the SDK, you'll need a project that meets the prerequisites listed below (otherwise you may face compatability issues). +Before we begin installing and configuring the SDK, you'll need a project that meets the prerequisites listed below (otherwise you may face compatibility issues). ### Prerequisites From a4669063faf8dfa0c060ddfce4ed0cc0c5423070 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 09:56:52 +0200 Subject: [PATCH 04/12] Update biconomy.mdx --- guides/integrations/partners/biconomy.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/integrations/partners/biconomy.mdx b/guides/integrations/partners/biconomy.mdx index fa1c691..337226f 100644 --- a/guides/integrations/partners/biconomy.mdx +++ b/guides/integrations/partners/biconomy.mdx @@ -50,7 +50,7 @@ Particle Auth Core is configured exclusively through `AuthCoreContextProvider`, - `projectId`, `clientKey`, and `appId`. Each of these are required values retrieved from the [Particle dashboard](https://dashboard.particle.network). Without them, your application will throw an error. Your project ID, client key, and app ID essentially link your application with the dashboard, thereby authenticating API requests, allowing you to track users, etc. Retrieve these values even if you aren't configuring `AuthCoreContextProvider`, as you'll be using them for `SmartAccount` in a moment. - `erc4337`, containing `name` and `version`. In this example, we're using a Biconomy V2 smart account, thus `name` can be set to "BICONOMY" and `version` can be set to "2.0.0." -Beyond these parameters, there are numerous other (mostly visual) customizations that can be made, including determining whether the embedded wallet modal is visible or not (and if so, what chains it supports). An example of the constructed `index` file used for this example isincluded below: +Beyond these parameters, there are numerous other (mostly visual) customizations that can be made, including determining whether the embedded wallet modal is visible or not (and if so, what chains it supports). An example of the constructed `index` file used for this example is included below: ```typescript TypeScript import React from 'react' @@ -248,4 +248,4 @@ To learn more about the utilization process of `@biconomy/particle-auth` (with a Particle Network aims to provide developers with a modular, open account abstraction stack where any infrastructure provider can be used directly with Particle Auth or Particle Auth Core to facilitate AA-enabled social logins. With Biconomy being one of these core providers, there are various options for using its infrastructure with Particle, specifically when it comes to a native integration (as Biconomy is the only natively supported Paymaster provider outside of Particle’s own [Omnichain Paymaster](/guides/integrations/aa/paymaster)). -To dive into the example shown within part 1, see its [`particle-biconomy-example` demo repository](https://github.com/TABASCOatw/particle-biconomy-example). Additionally, the full repository for the `@biconomy/particle-auth` example shown here is also available through [`particle-biconomy-sdk-demo`](https://github.com/TABASCOatw/particle-biconomy-sdk-demo). \ No newline at end of file +To dive into the example shown within part 1, see its [`particle-biconomy-example` demo repository](https://github.com/TABASCOatw/particle-biconomy-example). Additionally, the full repository for the `@biconomy/particle-auth` example shown here is also available through [`particle-biconomy-sdk-demo`](https://github.com/TABASCOatw/particle-biconomy-sdk-demo). From a37edaaaf6cdbe7a6ef1b57926fb6b17e04a22bf Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 09:58:58 +0200 Subject: [PATCH 05/12] Update jwt.mdx --- guides/configuration/auth/jwt.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/configuration/auth/jwt.mdx b/guides/configuration/auth/jwt.mdx index 5ea2e98..bb03ec6 100644 --- a/guides/configuration/auth/jwt.mdx +++ b/guides/configuration/auth/jwt.mdx @@ -400,7 +400,7 @@ export const decodeJWT = async (token: string): Promise => { ### Integrating JWT Handling within your dApp's UI -After the above, you can integrate integrate the login and JWT handling functionality with your dApp's UI. These are contained in `page.tsx`, which includes an input field for the username and a login button to trigger login logic. +After the above, you can integrate the login and JWT handling functionality with your dApp's UI. These are contained in `page.tsx`, which includes an input field for the username and a login button to trigger login logic. ```tsx src/app/page.tsx // Handle user login From c80e5176f01af560cded338ac21a01ede7dba6a4 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:03:05 +0200 Subject: [PATCH 06/12] Update unity.mdx --- api-reference/connect/mobile/unity.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/api-reference/connect/mobile/unity.mdx b/api-reference/connect/mobile/unity.mdx index 93cac50..d64310c 100644 --- a/api-reference/connect/mobile/unity.mdx +++ b/api-reference/connect/mobile/unity.mdx @@ -47,8 +47,8 @@ Your **Unity** project must meet several requirements to avoid compatibility iss - compileSdkVersion, targetSdkVersion **34** or higher. - JavaVersion **17**. - [Jetpack (AndroidX)](https://developer.android.com/jetpack/androidx/migrate?authuser=0). - - Android Gradle Plugin Version : 8.5.1 or higher. - - Gradle Version : 8.9 or higher. + - Android Gradle Plugin Version: 8.5.1 or higher. + - Gradle Version: 8.9 or higher. ### Setting up the Particle dashboard @@ -193,9 +193,9 @@ An example of the above process can be found below. | Field | Type | Description | | ----------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `chainInfo` | `ChainInfo` | The primary chain to be used within your application. This should be indicated by an overall blockchain, followed by a specific network. Within this example, it's `.Ethereum`(alternatively it could be `.EthereumSepolia`, and so on.) | -| `dAppData` | `DAppMetadata` | Metadata that describes your application and should be provided as an instance of `DAppMetadata` with the following parameters: `walletConnectProjectId`, the WalletConnect project ID retrieved from the [WalletConnect dashboard](https://cloud.walletconnect.com), `name`, the name of your project. `icon`, a URL linking to the icon of your project; this should be 512x512, ideally. `url`, the URL of your project's website. `description`, the description of your project, `redirect`, optional, a redirect universal link to you project, `verifyUrl`, optional. | +| `dAppData` | `DAppMetadata` | Metadata that describes your application and should be provided as an instance of `DAppMetadata` with the following parameters: `walletConnectProjectId`, the WalletConnect project ID retrieved from the [WalletConnect dashboard](https://cloud.walletconnect.com), `name`, the name of your project. `icon`, a URL linking to the icon of your project; this should be 512x512, ideally. `url`, the URL of your project's website. `description`, the description of your project, `redirect`, optional, a redirect universal link to your project, `verifyUrl`, optional. | | `rpcUrl` | `RpcUrl?` | Customize the RPC URL. | -| `env` | `Env` | The specific environmennt to be used. This can be either `.DEV`, `.STAGING`, `.PRODUCTION`, this should be set to `.PRODUCTION` when released. | +| `env` | `Env` | The specific environment to be used. This can be either `.DEV`, `.STAGING`, `.PRODUCTION`, this should be set to `.PRODUCTION` when released. | ```csharp var metadata = new DAppMetaData(TestConfig.walletConnectProjectId,"Particle Connect", From 6538a7ec50c7efcb3350bf7aebb391b35061c105 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:07:15 +0200 Subject: [PATCH 07/12] Update flutter.mdx --- api-reference/auth/mobile-sdks/flutter.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/api-reference/auth/mobile-sdks/flutter.mdx b/api-reference/auth/mobile-sdks/flutter.mdx index f389a2e..b71d438 100644 --- a/api-reference/auth/mobile-sdks/flutter.mdx +++ b/api-reference/auth/mobile-sdks/flutter.mdx @@ -43,8 +43,8 @@ flutter pub add particle_auth_core - compileSdkVersion, targetSdkVersion **34** or higher. - JavaVersion **17**. - [Jetpack (AndroidX)](https://developer.android.com/jetpack/androidx/migrate?authuser=0). -- Android Gradle Plugin Version : 8.5.1 or higher. -- Gradle Version : 8.9 or higher. +- Android Gradle Plugin Version: 8.5.1 or higher. +- Gradle Version: 8.9 or higher. If you're building an Android application with Flutter, follow the steps below to configure Particle Auth. To begin, you'll need to go ahead and open your `build.gradle` file, often found at the following file path: `${project name}/android/app/build.gradle` @@ -271,7 +271,7 @@ If you need the same message to return a unique signature each time, use the `Ev | Field | Type | Description | | --------- | -------- | --------------------------------------------------------------------------------- | -| `message` | `String` | On Evm requires a hexadeciaml string, on Solana, requires a UTF-8/readable string | +| `message` | `String` | On Evm requires a hexadecimal string, on Solana, requires a UTF-8/readable string | ```dart final messageHex = "0x${StringUtils.toHexString("Hello Particle")}"; @@ -316,7 +316,7 @@ This will propose a signature (on both EVM and Solana) and then immediately push | Field | Type | Description | | ------------- | -------- | ------------------------------------------------------------------------- | -| `transaction` | `String` | On Evm requires a hexadeciaml string, on Solana, requires a base58 string | +| `transaction` | `String` | On Evm requires a hexadecimal string, on Solana, requires a base58 string | ```dart final signature = await Evm.sendTransaction(transaction); @@ -540,7 +540,7 @@ final result = await EvmService.readContract(publicAddress, contractAddress, met | `from` | `String` | The user's public address. | | `data` | `String` | The transaction's data. | | `value` | `BigInt` | The native amount. | -| `to` | `String` | If you send a erc20, erc721, erc1155 or interact with a contract, this is the contract address, if you send native, this is receiver address. | +| `to` | `String` | If you send an erc20, erc721, erc1155 or interact with a contract, this is the contract address, if you send native, this is receiver address. | | `gasFeeLevel` | `GasFeeLevel` | (Optional) the gas fee level, `high`, `medium` or `low`, default is `high`. | ```dart @@ -693,7 +693,7 @@ final result = await SolanaService.getPrice(tokenAddresses, currencies); ### Get Transactions by address -To retrieve transactions executed by a specific a address, call `SolanaService.getTransactionsByAddress`. +To retrieve transactions executed by a specific address, call `SolanaService.getTransactionsByAddress`. ```dart final result = await SolanaService.getTransactionsByAddress(address); From e6794326f09828a983f4d56f19acd24add94830a Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:10:14 +0200 Subject: [PATCH 08/12] Update unity.mdx --- api-reference/auth/mobile-sdks/unity.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/api-reference/auth/mobile-sdks/unity.mdx b/api-reference/auth/mobile-sdks/unity.mdx index 46b380a..b784b89 100644 --- a/api-reference/auth/mobile-sdks/unity.mdx +++ b/api-reference/auth/mobile-sdks/unity.mdx @@ -27,8 +27,8 @@ Your Unity project needs to meet several requirements to avoid any compatibility - compileSdkVersion, targetSdkVersion **34** or higher. - JavaVersion **17**. - [Jetpack (AndroidX)](https://developer.android.com/jetpack/androidx/migrate?authuser=0). - - Android Gradle Plugin Version : 8.5.1 or higher. - - Gradle Version : 8.9 or higher. + - Android Gradle Plugin Version: 8.5.1 or higher. + - Gradle Version: 8.9 or higher. ### Setting up the Particle dashboard @@ -81,7 +81,7 @@ You'll also need to configure your Podfile if you haven't already. If you don't

Copy our example Podfile

- You can copy our examole + You can copy our example [Podfile](https://github.com/Particle-Network/particle-unity/blob/main/ios-build/Podfile), it will always use the latest version.

@@ -131,7 +131,7 @@ installer.pods_project.targets.each do |target| end ``` -Also you can copy the example [Podfile](https://github.com/Particle-Network/particle-unity/blob/main/ios-build/Podfile) . +Also, you can copy the example [Podfile](https://github.com/Particle-Network/particle-unity/blob/main/ios-build/Podfile) . With your Podfile set, you'll need to run `pod install` and open your `.xcworkspace` file, such as is shown below: @@ -513,12 +513,12 @@ var result = (string)JObject.Parse(rpcResult)["result"]; | `gasFeeLevel` | `GasFeeLevel` | (Optional) the gas fee level, `High`, `Medium` or `Low`, default is `High`. | ```csharp -var transaction = await EvmService.CreateTransaction(from, data, value, reciver); +var transaction = await EvmService.CreateTransaction(from, data, value, receiver); ``` ### Estimate Gas -Given a standard transaction structure (detached set of values, as shown below), gas estimations can be ran to simulate and retrieve the volume of gas to be consumed by a specified transaction (wrapper for `eth_estimateGas`). This is done through `EvmService.EstimateGas`. +Given a standard transaction structure (detached set of values, as shown below), gas estimations can be run to simulate and retrieve the volume of gas to be consumed by a specified transaction (wrapper for `eth_estimateGas`). This is done through `EvmService.EstimateGas`. ```csharp final result = await EvmService.EstimateGas(from, to, value, data); @@ -585,7 +585,7 @@ await SolanaService.GetTokensAndNFTs(publicAddress, true); `SolanaService.SerializeSOLTransaction` facilitates the construction of a SOL transaction object. -These transactions, once constructed , can be passed for in-UI proposal with `ParticleAuthCore.Instance.SolanaSendTransaction`. +These transactions, once constructed, can be passed for in-UI proposal with `ParticleAuthCore.Instance.SolanaSendTransaction`. ```csharp string receiver = ""; From 81bf7116daad52405fc62f741123816dae8bab03 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:12:32 +0200 Subject: [PATCH 09/12] Update faq.mdx --- api-reference/auth/faq.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/api-reference/auth/faq.mdx b/api-reference/auth/faq.mdx index 48f9af2..fd2c456 100644 --- a/api-reference/auth/faq.mdx +++ b/api-reference/auth/faq.mdx @@ -9,10 +9,10 @@ description: 'Find Frequently Asked Questions about Particle Auth.' **Answer:** Due to the unique characteristics of Multi-Party Computation (MPC), the signature result for the same message can vary each time, unlike traditional private key wallets such as MetaMask. - To address scenarios requiring a consistent signature result, we provide the `uniq` parameter. This parameter ensures that the signature remains consistent every time you sign the same message. + To address scenarios requiring a consistent signature result, we provide the `unique` parameter. This parameter ensures that the signature remains consistent every time you sign the same message. ```tsx App.tsx - // Sign a message with the uniq flag + // Sign a message with the unique flag const result = await signMessage(message, true); ``` @@ -195,4 +195,4 @@ description: 'Find Frequently Asked Questions about Particle Auth.' **Still need help?** [Open a ticket](https://t.me/particle_developer_bot) with Particle's Developer Relations team through the dedicated Telegram support bot. - \ No newline at end of file + From 45174ac1b85a862970453b6b451262a4f30bee95 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:18:23 +0200 Subject: [PATCH 10/12] Update ios.mdx --- api-reference/wallet/mobile/ios.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/api-reference/wallet/mobile/ios.mdx b/api-reference/wallet/mobile/ios.mdx index 9a88699..1906393 100644 --- a/api-reference/wallet/mobile/ios.mdx +++ b/api-reference/wallet/mobile/ios.mdx @@ -169,9 +169,9 @@ let result = try await ParticleWalletAPI.getEvmService().getTransactionsFromDB(b | Field | Type | Description | | ---------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `from` | `String` | The user's public address, which to sign the transaction. | -| `to` | `String?` | If you send a erc20, erc721, erc1155 or interact with a contract, this is the contract address, if you send native, this is receiver address, if you want to deploy a contract, this to should be `nil` | +| `to` | `String?` | If you send an erc20, erc721, erc1155 or interact with a contract, this is the contract address, if you send native, this is receiver address, if you want to deploy a contract, this to should be `nil` | | `value` | `String?` | Native value, default is nil, expressed as a hex string. | -| `data` | `String` | If you send a erc20, erc721, erc1155 or interact with a contract, this is the data field, if you send native, this should be `0x`, default value is `0x` | +| `data` | `String` | If you send an erc20, erc721, erc1155 or interact with a contract, this is the data field, if you send native, this should be `0x`, default value is `0x` | | `contractParams` | `ContractParams?` | You can use this object to describe a write contract function | | `type` | `String` | Default is 0x2. Support EIP1559, you can ignore this parameter | | `gasFeeLevel` | `gasFeeLevel` | The specific gas fee level to be used. This can be either `.low`, `.medium`, `.high`, default is `.medium` | @@ -259,7 +259,7 @@ Specifically, four key parameters are available within `ParticleWalletAPI.getEvm | `params` | `[Encodable]` | The parameters of the method, each parameter requires a hexadecimal string. | | `abiJsonString` | `String?` | (Optional) The ABI JSON string for the method. | -Here is a abiJsonString example. +Here is an abiJsonString example. ```swift let abiJsonString = "[{\"inputs\":[{\"internalType\":\"uint256\",\"name\":\"quantity\",\"type\":\"uint256\"},{\"internalType\":\"uint256\",\"name\":\"amount\",\"type\":\"uint256\"}],\"name\":\"mint\",\"outputs\":[],\"stateMutability\":\"nonpayable\",\"type\":\"function\"}]" @@ -526,7 +526,7 @@ The specific parameters that can be used within `PNRouter.navigatorBuy` are list | `fixFiatAmt` | `bool` | (Optional) Lock selection of fiat amount in the buy menu, default is false. | | `fixCryptoCoin` | `bool` | (Optional) Lock selection of crypto coin in the buy menu, default is false. | | `theme` | `String` | (Optional) The buy page theme, `dark` or `light`, default is current appearance. | -| `language` | `Language?` | (Optional) The buy page lanuage, default is current language. | +| `language` | `Language?` | (Optional) The buy page language, default is current language. | | `modalStyle` | `IOSModalPresentStyle?` | (Optional) Control iOS presentation style, default is `pageSheet`. | ```swift @@ -571,8 +571,8 @@ if let url = URL(string: "app.uniswap.org") { } ``` -### (Optional) Custom WalletConnect Projcet ID +### (Optional) Custom WalletConnect Project ID ```swift ParticleWalletConnect.setWalletConnectV2ProjectId("WalletConnect project ID") -``` \ No newline at end of file +``` From 45de7411a9c2d65c12f722bfe0701b04e77f8aa4 Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:21:00 +0200 Subject: [PATCH 11/12] Update react.mdx --- api-reference/wallet/mobile/react.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/api-reference/wallet/mobile/react.mdx b/api-reference/wallet/mobile/react.mdx index e67098a..1d8ac7d 100644 --- a/api-reference/wallet/mobile/react.mdx +++ b/api-reference/wallet/mobile/react.mdx @@ -294,7 +294,7 @@ The specific parameters that can be used within `ParticleWallet.navigatorBuyCryp | `fixFiatAmt` | `boolean` | (Optional) Lock selection of fiat amount in the buy menu, default is false. | | `fixCryptoCoin` | `boolean` | (Optional) Lock selection of crypto coin in the buy menu, default is false. | | `theme` | `string?` | (Optional) The buy page theme, `dark` or `light`, default is curreny appearance. | -| `language` | `Language?` | (Optional) The buy page lanuage, default is current language. | +| `language` | `Language?` | (Optional) The buy page language, default is current language. | ```typeScript const config = { @@ -430,21 +430,21 @@ Particle Wallet can also undergo additional customization, specifically regardin - `setBridgeDisabled`, whether or not the "Bridge" functionality is displayed within the interface. This takes one parameter, either `true` or `false`, with the default being `false`. -- `setDisplayTokenAddresses`, an synchronous function to set specific token addresses to be displayed in the Particle Wallet. It takes an array of token addresses as a parameter, `tokenAddresses`. +- `setDisplayTokenAddresses`, a synchronous function to set specific token addresses to be displayed in the Particle Wallet. It takes an array of token addresses as a parameter, `tokenAddresses`. -- `setDisplayNFTContractAddresses`, an synchronous function for setting specific NFT contract addresses to be displayed in the Particle Wallet. This function accepts an array of NFT contract addresses, `nftContractAddresses`. +- `setDisplayNFTContractAddresses`, a synchronous function for setting specific NFT contract addresses to be displayed in the Particle Wallet. This function accepts an array of NFT contract addresses, `nftContractAddresses`. -- `setPriorityTokenAddresses`, an synchronous function that prioritizes certain token addresses to appear at the top of lists within the Particle Wallet. It requires an array of token addresses, `tokenAddresses`. +- `setPriorityTokenAddresses`, a synchronous function that prioritizes certain token addresses to appear at the top of lists within the Particle Wallet. It requires an array of token addresses, `tokenAddresses`. -- `setPriorityNFTContractAddresses`, an synchronous function to prioritize specific NFT contract addresses in the Particle Wallet, making them appear at the top of lists. It takes an array of NFT contract addresses, `nftContractAddresses`. +- `setPriorityNFTContractAddresses`, a synchronous function to prioritize specific NFT contract addresses in the Particle Wallet, making them appear at the top of lists. It takes an array of NFT contract addresses, `nftContractAddresses`. -- `setShowLanguageSetting`, an synchronous function to toggle the visibility of the language setting option in the Particle Wallet. It takes a Boolean value, `true` or `false`. +- `setShowLanguageSetting`, a synchronous function to toggle the visibility of the language setting option in the Particle Wallet. It takes a Boolean value, `true` or `false`. -- `setShowAppearanceSetting`, an synchronous function that controls the display of the appearance setting in the Particle Wallet. It accepts a Boolean parameter, either `true` or `false`. +- `setShowAppearanceSetting`, a synchronous function that controls the display of the appearance setting in the Particle Wallet. It accepts a Boolean parameter, either `true` or `false`. -- `setSupportAddToken`, an synchronous function to toggle the option to add tokens in the Particle Wallet. It takes a Boolean value of `true` or `false`. +- `setSupportAddToken`, a synchronous function to toggle the option to add tokens in the Particle Wallet. It takes a Boolean value of `true` or `false`. -- `setSupportWalletConnect`, an synchronous function set whether WalletConnect is supported on the wallet page. It takes a boolean value, `true` or `false`. +- `setSupportWalletConnect`, a synchronous function set whether WalletConnect is supported on the wallet page. It takes a boolean value, `true` or `false`. - `setSupportDappBrowser`, configures the availability of the dApp browser feature. It accepts a boolean parameter, `true` or `false`. From 14d32f43713b0c6b3b1f2078d1660329fd0ab00c Mon Sep 17 00:00:00 2001 From: mcisb <83702309+KyryloKilin@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:23:20 +0200 Subject: [PATCH 12/12] Update web.mdx --- api-reference/btc/desktop/web.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/api-reference/btc/desktop/web.mdx b/api-reference/btc/desktop/web.mdx index 891c39c..aa0518d 100644 --- a/api-reference/btc/desktop/web.mdx +++ b/api-reference/btc/desktop/web.mdx @@ -274,7 +274,7 @@ Below is the full list of functions derived from `useETHProvider`: - `switchChain`, for forcibly changing the EVM chain used through the smart account. This takes a specific `chainId` (should be one of the aforementioned supported chains). - `provider`, the EIP-1193 provider object associated with the smart account. - `getFeeQuotes`, for retrieving fee quotes (a collection of UserOperation structures based upon different fee payment mechanisms); this is equivalent to [getFeeQuotes](/api-reference/aa/rpc/getfeequotes). -- `buildUserOp`, to build a execution-ready UserOperation with a standard transaction object. +- `buildUserOp`, to build an execution-ready UserOperation with a standard transaction object. - `sendUserOp`, for sending UserOperations (either objects derived from `getFeeQuotes`/`buildUserOp`, or standard transaction objects). - `publicClient`, the [viem](https://github.com/wevm/viem) `PublicClient` object for making standard JSON-RPC requests.