# PLW003v2 | Pali Wallet v3.5 [Jag/Fer] | QA Report [2] #718
Unanswered
function0xMarki
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🔗 References: # PLW003v1 | Pali Wallet v3.5 [Jag/Fer] | QA Report [1]
In reference to PLW003v1 QA Report [1], no general performance degradation has been observed in Pali Wallet; however, this latest version shows a significant decline in stability, particularly during chain switching between UTXO and EVM. A sharp increase in interface freezes has been detected during this process, along with frequent and unexpected PIN prompts, which directly affect user experience and workflow fluidity.
While there is still an improvement in the reduction of arbitrary console errors compared to previous versions, new errors have emerged directly tied to the aforementioned issues—partially offsetting those previous gains.
It has also been confirmed that Ledger integration, which previously worked correctly for EVM (though not for UTXO), has been entirely removed in this version, with no option to re-enable it from the advanced settings. In addition, the Trezor linking process—which previously functioned correctly for EVM (but had issues with UTXO)—is now fully non-functional.
Overall, while the graphical interface has improved noticeably, presenting a more polished and professional appearance, these visual upgrades do not compensate for the regression in core functionality. The loss of stability, decreased compatibility with hardware wallets, and emergence of new errors make this version unsuitable for production. It is strongly recommended that future development focus on stabilizing this base before introducing any new features.
✅ Solved
⛔ Not Solved
Regarding PLW003v1-IP01: ---
Regarding PLW003v1-IP02, about the Improvement of change of Trezor account from UTXO to EVM, and due to a new problem reported later, it has not been proven, therefore it will be considered until then, not been resolved.
Regarding PLW003v1-ER03, about the Pali Wallet's connection with the BlockScout, has not been resolved.
Regarding PLW003v1-ER04, in this new version, the option of deactivating the auto-lock was eliminated, showing only the time option to perform the auto-lock, however, it has not been resolved. Pali Wallet still does not respect the time options established by the user. This incident was reported on GitHub on November 21, 2024, under the identifier [UX-012] | ], name changed for PLW003v1-ER04
Regarding PLW003v1-ER05, about several issues that were identified while testing the Trezor linking functionality, it has not been resolved. In fact, the problems have become more complex, therefore a new error code [PLW003v2-ER06] will be described later.
💡 Suggestions:
⚙️ Improvements:
While the user interface has significantly improved in indicating insufficient wallet funds—and access to the faucet is now clearer and more visually user-friendly—it is important to highlight a critical issue: the provider that previously offered faucet services for the NEVM and Rollux networks has ceased operations without prior notice.
As a direct consequence, all previously available methods for obtaining test funds are now non-functional: the faucet website, the Telegram bot, and the direct integration within Pali Wallet all relied on that provider. As of now, there is no working mechanism to request faucet funds for NEVM and Rollux from these sources, including the “now non-functional” integration in Pali Wallet.
PLW003v2-IP02:
During the transaction-sending process on the UTXO chain, a UI issue has been identified concerning the verification icon that checks whether the destination address is a valid UTXO address. This icon, which should appear aligned with the corresponding text input field, is visually misaligned.
PLW003v2-IP03:
When importing a token, Pali Wallet displays a warning message labeled “Allow” to prompt user confirmation. However, the design of this message presents a visual accessibility issue: the text appears in black over a dark blue background, making it nearly unreadable. This lack of contrast hinders message comprehension, as it can only be read if the user is already aware of its presence and manually highlights the text to reveal it.
PLW003v2-IP04:
When Pali Wallet attempts to connect to a web3 application, it displays a screen prompting the user to select the account they wish to connect with. However, in this interface, the text appears in black on a dark blue background, resulting in insufficient contrast and making the text difficult or even impossible to read.
❌ Errors:
Issues with Trezor integration. In the previous version, specifically with report PLW003v1-ER05, linking worked correctly with EVM accounts, though not with UTXO. However, in the current version, Trezor integration is completely non-functional.
Multiple connection attempts have been made. On four consecutive occasions, when trying to link a UTXO account with Trezor, the process hangs at the final step—right when the Trezor account should be displayed. At that point, Pali Wallet freezes on a black screen, locking up the entire web browser, which must be forcibly closed from the operating system. Upon restarting the browser, Pali acts as if nothing happened: there's no trace of the attempted linking nor any error messages.
On a fifth attempt, the browser also froze and had to be force-closed. However, after restarting, an account appeared to be linked—but it was entirely incorrect. Despite the attempt being made with a UTXO account, the wallet registered it under Rollux. Furthermore, the displayed address was not a valid EVM address, but an XPUB belonging to the UTXO system, indicating a critical misassignment of account types.
This issue also occurs if the user tries to link from a UTXO address as if it were an EVM.
After completing the installation and starting account creation tests, the process proceeds normally up to the step where Pali Wallet prompts the user to confirm they have correctly noted the provided seed phrase. Once this verification is completed, the wallet should automatically open and display the generated accounts.
However, during the first two tests, abnormal behavior was observed. After confirming the seed phrase, the Pali Wallet interface went completely black and became unresponsive. After several attempts to disable and re-enable the extension, Pali Wallet prompted for the user-defined unlock PIN. Upon entering it, multiple console errors appeared along with a “Something went wrong” message on the main interface.
After several more attempts to restart the extension, one instance did not display the error message. Nonetheless, the information shown in Pali Wallet was inconsistent and incomplete.
Critical issues have been identified during the account import process using a seed phrase.
After entering the seed and the user-defined unlock password, Pali Wallet becomes stuck at the final stage of the process, displaying a button with an indefinite loading animation and console errors. At this point, the wallet becomes unresponsive and does not proceed to the next step.
After multiple attempts disabling and re-enabling the extension—using the exact same seed phrases—one of the repeated tests eventually completed the import process and displayed the accounts. However, while the derived EVM addresses are correct, the generated UTXO addresses are not. The displayed UTXO addresses had never been used before and showed no transaction history, despite the seed being associated with previously active QA accounts.
Upon inspecting the XPUB shown by Pali Wallet in Blockbook, it was found that the XPUB recorded no historical transactions. When cross-referenced with the correct XPUB corresponding to the seed, it was confirmed that although the displayed XPUB is technically correct, none of the derived addresses under the path m/84'/57'/0'/... matched the previously used UTXO addresses—indicating an incorrect or inconsistent derivation of the hierarchical structure.
During the automated token import process from BlockScout—both on the NEVM and Rollux networks—anomalous behavior has been observed in Pali Wallet: Some imported tokens are displayed with names different from those defined in their smart contracts.
For example, when importing the SuperDapp token ("SUPR"), Pali Wallet displays it as "Supra", even though the contract clearly defines the name as "SuperDapp".
This issue also occurs with other tokens: the PSYS token is shown as "Operating System".
The UNO token appears as "JUNO", etc…
Similar discrepancies have been detected across multiple contracts.
When manually importing a token in Pali Wallet, it has been observed that the application no longer retrieves the Token Symbol or Token Decimals fields automatically from the provided contract address. These fields are not auto-filled, forcing the user to enter them manually. Previously, this information was queried and populated automatically via calls to the token contract.
Beta Was this translation helpful? Give feedback.
All reactions