Particle Auth FAQ
Find Frequently Asked Questions about Particle Auth.
How can I ensure the signature result is consistent each time?
How can I ensure the signature result is consistent each time?
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.
How can I silently log in and sign messages/transactions?
How can I silently log in and sign messages/transactions?
Answer: Currently, silent login and signing are not directly supported. However, this functionality can be achieved using the following approaches:
-
Session Keys with Biconomy V2: Session keys enable silent signing by creating temporary keys with limited permissions and expiration, allowing you to bypass frequent authentication popups.
-
Enabling Blind Signatures with Particle Auth: Blind signing (signing without a confirmation popup) is possible in Particle Auth if specific conditions are met:
- Authentication Method: The user must be authenticated via JWT or Telegram.
- Master Password Requirement:
- The user has entered their master password, or
- The user has not set a master password.
- No Payment Password: The user has not set a payment password.
- Disable Payment Password Prompt: Configure
AuthCoreContextProvider
with the parameterpromptPaymentPasswordSettingWhenSign
set tofalse
.
When these conditions are satisfied, blind signing is enabled.
How do I determine if an account is new?
How do I determine if an account is new?
Answer: When you retrieve UserInfo
, either through the connect
method or via the userInfo
object from useAuthCore
, a field provide the relevant information:
- Account Creation: The
created_at
field indicates the timestamp when the account was created.
How can I check the status of the main password and payment password settings?
How can I check the status of the main password and payment password settings?
Answer: The userInfo
object contains a security_account
property, which includes two fields:
has_set_master_password
: Indicates if the master password is set.has_set_payment_password
: Indicates if the payment password is set.
Why does Google login prompt me that I do not comply with the policy?
Why does Google login prompt me that I do not comply with the policy?
Answer: This issue typically occurs when using Google login within a WebView environment.
How to add support for a new EVM chain?
How to add support for a new EVM chain?
Answer: Our team needs to implement support for integrating a new EVM chain on our platform. Once we have added support for the chain, developers can use it within their applications.
What are the options for chain_name returned by the backend API?
What are the options for chain_name returned by the backend API?
Answer: The chain_name
values returned by the backend API include evm_chain
and solana
. Additionally, for Tron, the chain_name
is also represented as evm_chain
.
These values indicate the blockchain network associated with the account.
How do I fix webpack 5 polyfills error when creating a new React application?
How do I fix webpack 5 polyfills error when creating a new React application?
Answer: When using create-react-app
version 5 or above, you might encounter issues due to the lack of NodeJS polyfills, which are no longer included by default. To fix this, you can use react-app-rewired
and install the necessary polyfill modules.
-
Step 1: After creating a new application with
CRA
, installreact-app-rewired
and the required polyfill packages.If you’re using Yarn:
If you’re using NPM:
-
Step 2: Create a
config-overrides.js
file in the root of your project and add the necessary configuration to include the missing polyfills. This file will override the default Webpack configuration provided bycreate-react-app
.config-overrides.js -
Step 3: Modify the
scripts
section in yourpackage.json
to usereact-app-rewired
instead of the defaultreact-scripts
:
After making these changes, your React application should build successfully without encountering NodeJS polyfill errors.
How do I fix the '__wbindgen_add_to_stack_pointer' error in a React app using Vite?
How do I fix the '__wbindgen_add_to_stack_pointer' error in a React app using Vite?
Answer: If you’re encountering the error "Cannot read properties of undefined (reading '__wbindgen_add_to_stack_pointer')"
in your React app using Vite, it likely relates to issues with loading a WebAssembly (Wasm) module.
To resolve this, you can use the Particle Network WASM plugin with a customized Vite configuration. Here’s how to set it up:
- Install the Vite Plugin: Ensure you have the necessary WASM files and the plugin configured.
- Update your
vite.config.ts
: Add the following configuration to correctly handle the WebAssembly module in development mode:
This configuration helps ensure that the WebAssembly module is correctly copied and accessible during development, preventing the __wbindgen_add_to_stack_pointer
error from occurring.
Still need help?
Open a ticket with Particle’s Developer Relations team through the dedicated Telegram support bot.